NWSS-M003 — Service delivery status per period

Pre-release. This site describes standard version 0.1.0-dev, which is in development and may change before version 1.0.0.

Provisional. Usable pending approval; a project-proposed concept only by the project that proposed it.

Derivation of each eligible service point’s service status for each service period from the service outcomes collectors record on their visits, the scheduled service day and the time of reading, and the counts and rates over those statuses: service visits by outcome, eligible service points by status, households actively served and service coverage. Applies to every recurring household or communal collection service under NWSS.

underlying principles and assumptions

A service outcome is a claim the collector makes at a visit; a service status is derived from outcomes and never captured (ADR-0005). One frame: service points eligible on the period’s scheduled service day; points outside it are reported alongside, never mixed in. One visit serves one period. A period closes when its carry-forward window has passed, and its statuses are then fixed; a record submitted after closure is a late observation and changes nothing. A service is delivered when the collector reached the service point and recorded collected or no waste presented; an access failure is the household’s barrier, counted apart. A visit is attributed to the collector named on its record. Evidence of collection is the recorded outcome, not mass.

methods and procedures

On each service day the collector visits the service points of the round, scans the service point or container tag, and records the service outcome; where a tag cannot be scanned the collector records the outcome without a scan. The project design sets each zone’s service frequency and scheduled service day. After each period’s carry-forward window, derive and fix the statuses of the period; compute the indicators over closed periods.

data requirements and inputs

Collection round records carrying service outcome observations, each at a service point (resolved from the scanned tag under the scan resolution rule of ADR-0003, a container tag through the deployment that placed the container), with collector, observedAt and outcome; the platform’s submission time of each record; stage, eligibility and household counts from NWSS-M002; the zones each round serves and each zone’s scheduled service day. From the project design: the service period, service frequency, carry-forward window, newly-placed window and eligibility criteria.

calculation and transformation rules

A visit is one service point x on one local date; of several outcomes recorded at x that date, the first present in the order collected, collected without a tag scan, no waste presented, no access to the container, no access to the service point is the visit’s outcome. A scan that resolves to no service point is not a visit and is reported alongside as unresolved. (1) Service visits recorded = count of visits dated in the reporting period by outcome and by the collector on the record. For each service period p, let d be x’s scheduled service day in p and W the project parameter carry-forward window (default 8 days); p closes at d + W. A visit at x dated from the start of p to d + W is assigned to the earliest such period of x that has no assigned visit with outcome collected, collected without a tag scan or no waste presented; each visit is assigned to one period only. (2) The status of x in p, first match: newly placed if x’s first successful deployment under its enrolment in force is dated less than the project parameter newly-placed window (default 8 days) before d and no visit is assigned to p; served if an assigned visit is collected or collected without a tag scan; no waste presented if an assigned visit is no waste presented; access failure if an assigned visit is no access to the container or to the service point; not yet due if the reading time is before d + W; else missed. The frame is the x eligible at d. (3) Eligible service points by service status = count of (x, p) by status over closed p in the reporting period; (x, p) not yet due are reported alongside, never counted; a month holds the periods that start in it; served visits made without a tag scan, distinct x served, and ineligible x with a status are reported alongside. Missed and newly placed statuses carry no collector. (4) Households actively served = sum over eligible x with status served or no waste presented in at least one closed p of the reporting period of H(x), the latest valid household count observed at x up to the period’s end; alongside: the count of such x, their person count, and those without a household count. (5) Service coverage = 100 × (S + N) / (S + N + M) over closed periods, where S, N and M are the eligible (x, p) served, no waste presented and missed; access failures, newly placed and not yet due are reported alongside.

outputs and units of measure

Service visits recorded (count, NUM) by service outcome and collector; eligible service points by service status per period (count, NUM); households actively served (count, NUM) with service points and people alongside; service coverage (PERCENT) with access failures and newly placed alongside; each by period, service area and zone. The status of each (service point, period) feeds NWSS-M005 and NWSS-M007.

validation and verification approach

Validation: a reviewer with Knowledge and Skills Reputation in household waste service operations checks that the project design sets a service frequency and scheduled service day for every zone and declares or accepts the carry-forward and newly-placed windows. Verification of service delivery: a reviewer in that domain who never collected on the rounds verified (ADR-0012) samples closed service point-periods and checks each status against its visits and their evidence (tag scan, and the collector’s location trail in the evidence store), compares the period’s missed statuses with the follow-ups of NWSS-M007, and compares coverage with the participants’ reports under NWSS-M005.

limitations and applicability boundaries

Outcomes are recorded by the collector, whose work a bounty pays for; tag scans, follow-ups and participants’ reports are the checks, not proof. A visit recorded without a tag scan rests on the collector’s report alone and is counted as served with its share reported. Statuses of an open period change as visits arrive. Attribution of missed periods to collectors needs round assignments, which belong to the operational layer, so missed statuses are attributed to zones only.

rationale

The dashboard behind this methodology counted different populations on different screens, carried a collection forward so that one late visit made two weeks look collected, and let re-reading change past weeks. One eligible frame, one visit per period and fixed closed periods give a service status that every surface reports alike and a verifier can check point by point.

Indicators it serves

Activity types

  • Collection round

Knowledge domains a reviewer needs

  • Data and evidence quality
  • Household waste service operations

Variables

Variable Role Unit Description
Eligible DerivedOutput UNITLESS True when the service point meets the eligibility criteria parameter at a date; never captured.
Eligible service points by service status DerivedOutput NUM Count of eligible (service point, period) pairs by status over closed periods; not yet due reported alongside.
Household-days served (HD) DerivedOutput NUM Sum over the service periods of the reporting period of households actively served in the period times the days of the period.
Households actively served DerivedOutput NUM Sum of H over eligible service points served or with no waste presented in at least one closed period of the reporting period.
Service coverage DerivedOutput PERCENT 100 x (served + no waste presented) / (served + no waste presented + missed), eligible, closed periods.
Service point stage DerivedOutput UNITLESS Exited, equipped, enrolled or enumerated, derived from dated acts by the NWSS-M002 ladder; never captured.
Service status DerivedOutput UNITLESS The status of an eligible service point in a service period by the NWSS-M003 ladder; fixed once the period closes.
Service visits recorded DerivedOutput NUM Count of service point-dates with a visit outcome dated in the period, by outcome and collector.
Visit outcome DerivedOutput UNITLESS The outcome of a service point-date: the first present of collected, collected without a tag scan, no waste presented, no access to the container, no access to the service point.
Collector (k) MeasuredInput UNITLESS The agent in the collector role named on a record, resolved from the collector tag at observedAt under the scan resolution rule of ADR-0003.
Household count (H) MeasuredInput NUM Households at a service point as observed; the latest valid count is in force.
Observed at (t) MeasuredInput UNITLESS The instant the observation or record was made; its local date in the project’s time zone is the record’s date.
Person count MeasuredInput NUM People in the households at a service point as observed.
Restated record MeasuredInput UNITLESS The earlier record a record replaces; of a record and its restatements only the latest counts (ADR-0006).
Service outcome MeasuredInput UNITLESS What the collector recorded at a visit.
Service point (x) MeasuredInput UNITLESS The service point a record or observation is about.
Service zone MeasuredInput UNITLESS The zone a service point is assigned to.
Tag assigned to MeasuredInput UNITLESS The entity a tag bore under an assignment; a scan resolves to it while the assignment is valid, and in a gap after it unless the code was next assigned to a different entity (ADR-0003).
Tag assignment valid from MeasuredInput UNITLESS Start of a tag assignment’s validity window.
Tag assignment valid until MeasuredInput UNITLESS End of a tag assignment’s validity window; open while the assignment is not superseded.
Withdrawn record MeasuredInput UNITLESS The record a withdrawal declares never happened; a withdrawn record never counts (ADR-0006).
Zone served by a round MeasuredInput UNITLESS A zone a service round serves; a service point in such a zone may be eligible.

Monitoring requirements

  • Statuses fixed at period closure: A service period’s statuses are derived and fixed once its carry-forward window has passed; records submitted later are late observations and are reported, not applied.

This page explains the standard and does not decide conformance: only the released corpus does. It describes methodologies/methodologies.ttl, methodologies/variable-registry.ttl at standard version 0.1.0-dev.