D3 CNTRLS.ai

DDC programming · drawings · integration

Programming and drawings for the platforms the building already runs.

D3 CNTRLS LLC designs, programs, and hands off direct digital control. The work covers sequences, point lists, schematics, and graphics. We work with Niagara 4 and Niagara AX, Distech Controls, and Honeywell WEBs, plus the BACnet and Modbus devices those supervisors already talk to.

Ask D3See the platforms

Virtual Operator explains a station you already have. It does not program one. If you are still bidding the controls, D3 PointScope reads the set first.

Platforms

Three platforms. The same documentation standard.

Most plants are already committed to a supervisor. We meet that platform instead of asking you to rip it out for the sake of a new graphic.

Niagara

Niagara 4 and Niagara AX.

We program supervisor-level logic on Niagara-based systems: network layout, histories, operator graphics (including Px views), and the sequences your operators will run. D3 works with Niagara. The supervisor stays the system of record.

  • Niagara 4 and Niagara AX development
  • Supervisor configuration for a building or a portfolio
  • BACnet/IP, BACnet MS/TP, and Modbus network design
  • Haystack tagging when the project asks for a normalized point model
  • Operator graphics, histories, and alarm routing
  • Tracer SC and Tracer Summit integration where those front ends are already in the plant

Distech Controls

ECY supervisors, EC-BOS controllers, and Allure.

We program the Distech lineup from ECY supervisors through EC-BOS and EC-Net controllers and Allure communicating sensors. The logic is commented so the next technician can maintain it.

  • ECY-S1000 and ECY series supervisor programming
  • EC-BOS and EC-Net controller logic
  • Allure sensor and display configuration
  • Envysion graphics and operator views
  • Third-party BACnet and Modbus devices on the same trunk
  • Sequences written to follow ASHRAE Guideline 36 when the specification calls for it

Honeywell WEBs

WEBs, Spyder, and ComfortPoint.

We program WEBs-AX and WEBStation supervisors and the Spyder, ComfortPoint, and XL50 controllers under them. Legacy migrations and new installs get the same drawing set, so the points are not lost between the old job and the new one.

  • WEBs-AX and WEBStation supervisor programming
  • Spyder, ComfortPoint, and XL50 controller logic
  • Migrations onto a Niagara-based supervisor
  • Central plant and air-handler sequencing
  • Lighting or access points when they already land on the WEBs supervisor
  • Trends, alarms, and energy reports the operator can actually find

Control drawings

A set the installer and the operator can both use.

Code without a drawing is a liability on the next service call. The package runs from the sequence down to the point name on the wire, and it ships with the programming so the two do not drift apart.

Ask D3

Sequences of operation

Plain-language sequences from the mechanical drawings, the specification, and the design intent, written so a programmer can implement them on the platform of record.

Point lists and I/O

Hardware points, network points, and the equipment they belong to. Each point is named and documented for the person who will load the controller.

Control schematics

Wiring, power supplies, and network topology, produced so an electrician can build from the sheet.

Operator graphics

Floor plans and system graphics aimed at status, alarms, and the points an operator checks first.

Programming

From one terminal to a campus.

Scope follows the equipment schedules and the specification, not a generic library dropped onto a controller.

Sequence programming

Air handlers, plants, terminals, and the specialty equipment the specification actually lists. Guideline 36 is followed when the project requires it.

Central plants

Chiller, boiler, and pump sequencing with lead/lag, staging, and a written fallback when a piece of equipment faults.

Air-side control

Discharge-air control, duct-static reset, outdoor-air control, and VAV coordination, tuned to the sequence rather than to a default block.

More than one protocol

BACnet/IP, BACnet MS/TP, Modbus TCP and RTU, and LonWorks, brought to one supervisor with the network shown on the drawings.

Trends, alarms, histories

Trend intervals, alarm text, and categories chosen so the operator sees a signal instead of a wall of repeated messages.

Functional testing and handoff

Engineers witness points, check trends, and walk sequences against the design intent with your team before handoff. This is field work, not a software product.

Process

Visible from the first drawing review to handoff.

  1. 01

    Discovery and design review

    We read the mechanical drawings, the specification, and what is already installed before any logic is written.

  2. 02

    Sequences and drawings

    Sequences, point lists, and schematics are produced together so the logic and the wire land on the same point name.

  3. 03

    Programming

    Controllers are programmed on the platform of record, with comments a later technician can follow.

  4. 04

    Functional testing and handoff

    Point checks, trend checks, alarm checks, and time with the operators. You leave with the drawings and a system your staff can run.

Send the platform, the scope, and the drawings.

We will come back with what the programming includes, what stays with others, and a quote for the engineering. The quote is a separate document. It is not computed in the browser.

Ask D3