flowchart TB
sp_s1["Enumerate the service point"]
sp_s2["Enrol a participant"]
sp_s3["Deploy containers"]
sp_s4["Eligible for service"]
sp_s5["Collect each service period"]
sp_s6["Follow up a missed service"]
sp_s7["Evaluate per the monitoring plan"]
sp_s8["Maintain tags"]
sp_s9["Service exit"]
sp_s1 --> sp_s2
sp_s2 --> sp_s3
sp_s3 --> sp_s4
sp_s4 --> sp_s5
sp_s5 --> sp_s6
sp_s6 --> sp_s7
sp_s7 --> sp_s8
sp_s8 --> sp_s9
NWSS Service Point Lifecycle Workflow
The service a service point receives, from its registration at enumeration to its exit. The eligibility criteria are a project parameter (ADR-0010). The standard’s four legs are the default, which the project design may replace: equipped, a signed enrolment in force, an occupancy in force that is neither vacant nor unknown (a communal point is exempt from this leg), and in a zone a service round serves. The checks here implement the default; a design that declares other criteria replaces the eligibility check by refinement (novaOS ADR-0003).
- Enumerate the service point
- Enrol a participant
- Deploy containers
- Eligible for service
- Collect each service period
- Follow up a missed service
- Evaluate per the monitoring plan
- Maintain tags
- Service exit
The process graph
Every workflow, step and check the file states, and how they connect.
Open the interactive view on its own page. Drag to move, scroll to zoom, hover for details.
1. Enumerate the service point
Seat: an enumerator. The service point is registered once, in a service area a filed project design declares, with its point, label, type and an occupancy observation. Enumeration may precede registration, since validation samples it.
Prerequisite checks
The service point lies in a service area that a project design, not withdrawn, declares
Smart function check.
Completion checks
An enumeration record of the service point, not withdrawn, carries an occupancy observation of it
Smart function check.
2. Enrol a participant
Seat: a recruiter. Only a signed decision by a respondent who may consent enrols the service point; other decisions and failed contacts are kept as records. An enrolment ended by a service exit no longer counts; a later signed enrolment restarts service (ADR-0006).
Prerequisite checks
Completion checks
A signed enrolment of the service point by a respondent who may consent is not withdrawn and not ended by a service exit that is not withdrawn
Smart function check.
3. Deploy containers
Seat: a placement agent. A deployment dated after the latest signed enrolment, while that enrolment is in force, meets the deployment success criterion. The criterion is a project parameter (ADR-0010); its default, which the checks here implement, is at least one container placed with its tag assigned.
Prerequisite checks
Completion checks
The latest signed enrolment of the service point by a respondent who may consent, not withdrawn, is not ended by a service exit that is not withdrawn, and a deployment record at the service point dated after it, not withdrawn, placed a container that has a tag assignment (the default deployment success criterion)
Smart function check.
4. Eligible for service
A derived gate with no record and no instrument. Default criteria, which the project design may replace (ADR-0010): the service point is equipped, has a signed enrolment in force, has an occupancy in force that is neither vacant nor unknown, and lies in a zone a service round serves. A communal point is exempt from the occupancy leg. The occupancy in force is the latest dated occupancy observation, except that a signed enrolment followed by a later successful deployment, both dated after that observation, is evidence of occupancy.
Prerequisite checks
Completion checks
Default eligibility criteria: the service point is equipped (a successful deployment dated after its latest signed enrolment, which is in force), lies in a zone a service round serves, and, unless it is a communal point, its occupancy in force is neither vacant nor unknown: its latest occupancy observation is not vacant or unknown, or that enrolment is dated after the observation
Smart function check.
5. Collect each service period
Seat: a collector. Recurring: each visit on a collection round leaves a service outcome for the service point. What counts as a collection is the standard’s (a service outcome on a round record, resolved to the service point or its container); the service period, frequency and carry-forward window are project parameters, and the per-period service status is derived, never captured (ADR-0005).
Prerequisite checks
Completion checks
A collection round record, not withdrawn, by a named collector carries a service outcome for the service point or for a container a deployment record there, not withdrawn, placed
Smart function check.
6. Follow up a missed service
Seat: an evaluator or supervisor. Applies when the ledger shows a missed service: a round that serves the service point’s zone left no outcome for it or its containers after it was equipped, while no service exit was in force. An access failure (no access to the container or the service point) is not a missed service; it is reported alongside (NWSS-M003, NWSS-M007). A follow-up after the latest miss records the reason. The follow-up window is a project parameter (default 7 days) the operational layer uses for due dates. Conditional: holds vacuously where no miss is recorded.
Prerequisite checks
Completion checks
Where a missed service is recorded (a round after a deployment, while no service exit is in force, with no outcome for the service point or a container a deployment there, not withdrawn, placed), a follow-up record at the service point, not withdrawn and dated after the latest miss, carries the service failure reason; any other service point passes
Smart function check.
7. Evaluate per the monitoring plan
Seat: an evaluator who did not collect the service point’s round. Applies when the monitoring plan has issued a scheduled visit for the service point; the latest such visit that is neither cancelled nor superseded is completed by an evaluation, by an evaluator who never collected on a round serving the service point’s zone, that reached a suitable respondent at the right service point. Attempts are kept as records. An evaluation matched to no scheduled visit is kept and marked unscheduled, never refused, and does not count toward plan compliance. Conditional: holds vacuously where no visit is scheduled, or every scheduled visit is cancelled or superseded.
Prerequisite checks
Completion checks
Where a visit is scheduled, the latest scheduled visit neither cancelled nor superseded is fulfilled by an evaluation record at the service point, not withdrawn, whose visit outcome is completed and whose observer never collected on a round serving the service point’s zone; any other service point passes (the visit window and the missed status are the operational layer’s)
Smart function check.
Marking checks
Marks an evaluation record at the service point, not withdrawn, that fulfils no scheduled visit in force (neither cancelled nor superseded) as an unscheduled observation
Smart function check.
8. Maintain tags
Seat: a placement agent or supervisor. Applies when a record at the service point notes a tag issue for it or its containers; a new tag assignment, superseding the old one and valid after the latest issue, closes it. History is never rewritten (ADR-0003). Conditional: holds vacuously where no issue is recorded.
Prerequisite checks
Completion checks
9. Service exit
Seat: a supervisor. Terminal. Applies when the latest signed enrolment is ended by an exit that is not withdrawn, so an exit followed by a later signed enrolment no longer applies. An exit recorded in error is withdrawn, never reversed by a second exit, and a later signed enrolment restarts service (ADR-0006). Not vacuous: a service point in service has not exited.
Prerequisite checks
The service point has a signed enrolment that is not withdrawn, in force or since ended
Smart function check.
Completion checks
The service point’s latest signed enrolment that is not withdrawn is ended by a service exit that is not withdrawn
Smart function check.
Review requirements
No review requirement in the corpus names a record this workflow produces.