CO₂ rising in occupied zone while outdoor-air quality is degraded
Current CO₂, occupancy and outdoor-air observations are available; the ventilation recommendation is technically reasonable.
TA-14 RESPONSE SHOWROOM · SMART BUILDINGS · CONTROLS · CYBERSECURITY
PROMPTED BY A PUBLIC ENGINEERING PROPOSITION FROM GREGORY FITZPATRICK · RECC
Design the integration.
Then govern the consequence.
Gregory Fitzpatrick argues that engineers should understand the owner, systems, use cases, cybersecurity, interoperability, responsibilities, commissioning and acceptance requirements before designing an integrated controls system. TA-14 accepts that proposition here as the starting point—not as an endorsement of TA-14—and asks what comes next when the finished integration is operating in changing reality.
THE NEXT QUESTIONAfter the integration is designed, commissioned, secured and connected — what determines whether a particular consequence is permitted to occur now?
01 · THE ENGINEERING SEQUENCE
“The goal is simple: design the integration before you specify the components.”
PUBLIC POST · GREGORY FITZPATRICK · QUOTED AS THE PROPOSITION THAT PROMPTED THIS TA-14 RESPONSE
01OWNER GOALS02SYSTEMS03USE CASES04INTEGRATION DRAWING05IT + CYBER06DATA + INTEROPERABILITY07ROLES08COMMISSIONING + ACCEPTANCE
This showroom does not claim Gregory Fitzpatrick, RECC, Ken Sinclair or AutomatedBuildings.com adopts TA-14. It examines a question TA-14 sees immediately downstream of the published engineering sequence.
02 · WHERE TA-14 ENTERS
Commissioning can establish a baseline.
Runtime still has a consequence boundary.
CURRENT STEP · 01OWNER INTENT
Necessary engineering work can establish the designed system, its intended relationships and its accepted baseline. TA-14 does not treat completion of this step as unlimited future execution authority.
THE HANDOFF · COMMISSIONING → RUNTIME
Commissioning established that the system was acceptable under the conditions examined then.
Runtime asks whether the proposed consequence has standing under the conditions that exist now.COMMISSIONED ONCE ≠ AUTHORIZED FOREVER.CONNECTION ≠ AUTHORITY.CAPABILITY ≠ AUTHORITY.
03 · INTERACTIVE INTEGRATED BUILDING
Everything can be connected.
The answer can still be HOLD.
Select a building system, then run one of three runtime conditions. The point is not to simulate a complete controls specification. It is to expose the seam between successful integration and permission for a particular physical consequence.
INTEGRATION LAYERCONNECTEDINTEROPERABLECOMMAND CAPABLE
SELECTED SYSTEM
BAS
Coordinates HVAC sequences, schedules, setpoints and equipment commands.
CONNECTED — YESINTEROPERABLE — ASSUMED FOR THIS TESTCOMMAND CAPABLE — YES
Increase outside-air ventilation
A technically routable command is now approaching the consequence boundary.
CONVENTIONAL INTEGRATION CHECKS
CONNECTED ✓INTEROPERABLE ✓AUTHENTICATED ✓COMMAND VALID ✓CYBER CHECK PASSED ✓
AUTHORIZED NOW?Five green lights establish important conditions. None, by itself, answers the consequence question below.
TA-14 · CONSEQUENCE BOUNDARY
Does this proposed consequence have sufficient Admissible Evidence, Applicable Authority, and Established Standing to become reality NOW?
ADMISSIBLE EVIDENCE
Current CO₂, occupancy and outdoor-air observations are available; the ventilation recommendation is technically reasonable.
APPLICABLE AUTHORITY
The BAS is permitted to modulate ventilation, but the applicable operating envelope must account for the competing outdoor-air condition.
ESTABLISHED STANDING
Standing for this specific increase is not yet established until the current outdoor-air constraint and operating limit are resolved.
04 · CYBERSECURITY AND AUTHORITY
Secure transport answers an essential question.
It does not answer every question.
Can we trust the connection, identity, integrity and permitted technical relationship?
Those controls are essential. TA-14 does not replace them.
May this bounded consequence become reality under present conditions?
That requires the evidence, authority and standing applicable to the actual consequence now.
AUTHENTICATED ≠ AUTHORIZED FOR EVERY CONSEQUENCE · SECURELY DELIVERED ≠ ADMISSIBLE TO EXECUTE
05 · FROM REALITY TO OUTCOME
The integration carries the command.
Governance carries the burden of consequence.
01Reality
02Record
03Continuity
04Admissibility
05Binding
06Commit
07Execution
08Outcome
A proposed action can be technically possible, correctly addressed and securely transmitted while still lacking what is required to cross Commit. TA-14 preserves that distinction explicitly.
06 · AN OPEN TECHNICAL INVITATION
Gregory gave us the first half of the sentence.
Design the integration before you specify the components.
↓TA-14 asks: after the integration is designed, commissioned, secured and connected, what determines whether a particular consequence is permitted to occur now?
This room is an independent TA-14 technical response to that question. If Gregory Fitzpatrick or RECC sees a missing assumption, a better test case, or a boundary TA-14 has drawn incorrectly, the useful next step is examination—not attribution by implication.
DESIGN ≠ RUNTIME STANDINGCONNECTION ≠ AUTHORITYUNDERSTANDING ≠ PERMISSIONNO ADMISSIBLE EVIDENCE. NO ADMISSIBLE EXECUTION.