Systems Software Integration (SSI) - Placeholder Domain
Systems Software Integration
Systems Software Integration (SSI) is the placeholder domain for this study guide. It covers how software-driven building and life-safety systems exchange data, execute shared cause-and-effect logic, and remain testable after configuration. Expect questions that ask you to trace a signal from sensor to annunciator, distinguish a protocol gateway from a control function, and verify that an integrated sequence behaves as designed-not merely that devices communicate.
Core rules
- Start with an interface inventory: every connection should list source, destination, protocol, direction, supervised status, and responsible party.
- Put life-safety logic in the listed control equipment, not in a gateway, dashboard, or building automation system (BAS). Gateways translate; they do not become the authority for alarm, supervisory, or trouble decisions.
- Treat each integration point as either supervised or unsupervised. An unsupervised path can fail silently; document the compensating test or monitoring method.
- Define cause and effect in testable terms: input condition, logic delay, output action, and reset method.
- Control configuration versions. Record firmware, point mapping, and sequence revision so a retest reflects the installed system.
Worked example
A fire alarm control unit sends an alarm to a BAS through a protocol gateway. The BAS should start stairwell pressurization fans and release a lobby door. First verify the fire alarm control unit output is programmed and supervised. Then confirm the gateway maps the exact alarm point, not a general “fire” status. Next prove the BAS receives the point and executes the fan and door commands within the specified delay. Finally test failure: disconnect the gateway and confirm a trouble or documented alternative, then restore and retest.
Traps
Do not accept “the screen changed” as proof; test the physical output. Do not let a gateway perform life-safety logic. Do not test only normal conditions; include loss of network, power, and point failure. Do not omit version records; a firmware change can break point mapping. Do not confuse annunciation with control.