Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

SPIFFY I Process Design
D-6
109759—Distributed Systems Network Management (DSNM) Subsystem Interface
Development Guide
Sample I Process Program Code
SPIFFY I Process Design
To develop an I process, you must map the states of subsystem objects to DSNM states,
and a sequence of subsystem commands to the DSNM commands.
State Mapping
To map the many possible states of subsystem objects to DSNM states requires detailed
subsystem knowledge. The mapping should represent the operating state of the
subsystem object. The DSNM states GREEN, RED, YELLOW represent good, poor,
and transitional or borderline operational health. Suppose you enlisted the aid of a
SPIFFY subsystem expert, who tells you that:
•
REACTOR objects cannot have a state; they only exist (or not).
•
BOILER, VALVE, and CHAMBER operation depends only on temperature, which
must be neither too high nor too low.
•
ASSEMBLY, COGWHEEL, and GEAR operation depends only on the SPIFFY
state at the moment.
The following state mapping is assigned:
Object Type Operating Condition
DSNM State
Assigned
REACTOR N.A. NULL
Temperature
BOILER / 0-297 Too low to operate RED
VALVE / 298-595 Low but operable YELLOW
CHAMBER 596-893 Optimum operating range GREEN
894-1191 High but operable YELLOW
1192-up Too high to operate RED
State
ASSEMBLY STOPPED Inoperable RED
GOING Operable GREEN
COGWHEEL / LOCKED Unusable RED
GEAR IDLE Inoperable RED
COASTING Marginally operable YELLOW
ROTATING Operable GREEN
Note. Within a subsystem, it is possible for more than one set of conditions to map to the
same DSNM state. Also, not all DSNM states need be present for every object type.