Pro / Service workflow
An observation needs a next step.
The intended portal brings equipment observations into a service review list. These illustrative tables show the workflow direction, using fictional records. They are not live account views or evidence of delivered alerts.
The current Signal firmware samples locally. End-to-end device delivery, notifications and the complete contractor workflow still need integration and qualification.
/portal/queue| Observation | Equipment | Review step | Flag | Reference |
|---|---|---|---|---|
| Dedicated float contact changed | Example attic unit | Review context and contact the site | WATCH | EXAMPLE-042 |
| Temperature difference changed | Example split system | Compare operating conditions | NOTE | EXAMPLE-051 |
| Call input returned to idle | Example heat pump | Retain for service context | CLEAR | EXAMPLE-058 |
/portal/devices| Device | Location | Intended status | Review step |
|---|---|---|---|
| EXAMPLE-MON-01 | Air handler | Recent observation | Inspect available record |
| EXAMPLE-MON-02 | Garage system | No recent observation | Check device and connection |
/portal/releases| Stage | Question | Record |
|---|---|---|
| Bench | Does the hardware behave as intended? | Measured electrical and fault tests |
| Installation | Does the qualified design fit this system? | Wiring, access and compatibility review |
| Follow-up | Is the observation useful in service? | Technician review and next action |
The service decision
Context before a conclusion.
A changed reading is the beginning of a review. The intended workflow brings the observation, device context and a technician’s next action together.
The contractor decides what the observation means for the actual equipment. A software flag is not a diagnosis or an emergency response service.
Start a conversation
What would make this useful at your desk?
Tell us about your equipment, your service work and what you would want to learn from a prototype evaluation.