Lesson 2.1

Trace, classify, hand off

JCI's field programming (CCT-class tools) presents module/block system diagrams — 401's vocabulary in JCI dialect; read from the output backwards, always.
Loops are loops: SP, PV, output, tuning — your 401 health-shapes read JCI trends identically.
State tables and interlocks express 402's machinery in vendor form — find the mode logic and the sequence emerges.
BACnet priorities rule commanding: a point that won't obey has a higher-priority writer, same as anywhere (306).
Uncertified but professional: navigate, trend, trace, verify field-side, classify (303) — program changes hand off.

Service boundary: program modifications on Metasys belong with JCI-certified techs and tools — your value is evidence-rich diagnosis and clean handoff (304's boundary craft).

LAB — the mixed-building drill

Identification: from the evidence pack (photos, screens, board labels), identify the Johnson Controls (Metasys) generation and architecture present.
Navigation: on the demo/simulated front end, locate a given point, its trend, its schedule, and its override state within a time box.
Reading: trace one supplied program excerpt against its sequence (expected/observed/delta per 303) and classify the seeded deviation: equipment vs programming vs design.
Handoff: write the service note a Johnson Controls (Metasys)-certified tech could act on immediately.

Pass: identification correct; navigation within the box; deviation classified with reasoning; handoff note professional.

LAB DEMO VIDEO

Instructor walkthrough — navigating the Johnson Controls (Metasys) front end + one trace

[ ~12 min ]

The Metasys ecosystem map — tiered architecture: site portal → network engines → BACnet MS/TP field controllers + legacy N2 trunk branch; generation-recognition badges; room devices strip