Utility Service Point
Describe one persistent utility service interface and its evidence-backed point-specific bindings.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 12 findings · 36 questions
Identity and service classification Proposed service-point context for identity and service classification.
Persistent point identity
A service point is a persistent, authority-qualified interface record for one utility service. Meter serials, customer accounts and street addresses are aliases or links, not substitute root identities.
Persistent point identity
A service point is a persistent, authority-qualified interface record for one utility service. Meter serials, customer accounts and street addresses are aliases or links, not substitute root identities.
- Which authority and namespace identify this service point independently of its current meter or account? identity
- Which utility service and physical or planned interface class does the point represent? classification
- What evidence distinguishes a duplicate record from a replacement or split service point? exception
Usage and aggregation boundary
A measurement usage point can be physical or virtual. Link virtual aggregates and settlement groupings explicitly; do not materialize a new physical connection from an exchange identifier alone.
Usage and aggregation boundary
A measurement usage point can be physical or virtual. Link virtual aggregates and settlement groupings explicitly; do not materialize a new physical connection from an exchange identifier alone.
- Does the mapped usage point denote this interface or a logical aggregation? definition
- Which component points contribute to a grouped usage reference and during what interval? composition
- What mapping evidence prevents duplicate counting of root and submetered usage? interoperability
Location and connection boundary Proposed service-point context for location and connection boundary.
Served place and recognition
Keep the served place separate from the physical connection location and recognition evidence. An address match alone is insufficient to identify an interface. Geometry precision and restricted views are adopting-profile decisions.
Served place and recognition
Keep the served place separate from the physical connection location and recognition evidence. An address match alone is insufficient to identify an interface. Geometry precision and restricted views are adopting-profile decisions.
- Where is the interface located relative to the served premises or building? spatial
- Which survey, label or approved drawing supports recognition of the point? evidence
- Which places are served by this point over each effective interval? relationship
Network and responsibility demarcation
Reference network nodes and connection assets with profile-qualified cardinality. Distinguish asset title, operation, maintenance and data stewardship at the boundary. Split ownership does not force a single responsible party.
Network and responsibility demarcation
Reference network nodes and connection assets with profile-qualified cardinality. Distinguish asset title, operation, maintenance and data stewardship at the boundary. Split ownership does not force a single responsible party.
- Which external network node and connection assets establish the interface? relationship
- Where does each responsibility change and who is assigned to each side? ownership
- Which connection material or arrangement remains unknown or disputed? quality
Service properties and capability Proposed service-point context for service properties and capability.
Declared interface envelope
Record service-specific design and allowed operating envelopes as qualified assertions. Electric import or export, water delivery, thermal supply and return, and sewer discharge require distinct units and direction semantics. This draft supplies no engineering limits.
Declared interface envelope
Record service-specific design and allowed operating envelopes as qualified assertions. Electric import or export, water delivery, thermal supply and return, and sewer discharge require distinct units and direction semantics. This draft supplies no engineering limits.
- What rated capacity and interface properties apply under the selected utility profile? measurement
- Which permitted directions and operating limits constrain service at the interface? constraint
- What evidence distinguishes an approved envelope from an observed operating value? validation
Condition and observation context
Point observations retain feature, property, procedure, time and evidence. A recent observation is not permanent proof of condition. Safety assessments and work execution remain external; only their references and resulting point assertions belong here.
Condition and observation context
Point observations retain feature, property, procedure, time and evidence. A recent observation is not permanent proof of condition. Safety assessments and work execution remain external; only their references and resulting point assertions belong here.
- Which condition was observed at the point using which method and unit? measurement
- When did the observed condition apply and when was the result recorded? temporal
- What limitation or contrary evidence qualifies the condition assessment? quality
Metering and usage evidence Proposed service-point context for metering and usage evidence.
Meter and channel assignments
Device and channel bindings have effective intervals and distinct masters. Allow unmetered or multiple-channel profiles without fabricating devices; exchange of a meter does not automatically create a new point. Device maintenance stays outside this model.
Meter and channel assignments
Device and channel bindings have effective intervals and distinct masters. Allow unmetered or multiple-channel profiles without fabricating devices; exchange of a meter does not automatically create a new point. Device maintenance stays outside this model.
- Which meters and channels are assigned to the point for the relevant interval? composition
- How is a meter exchange linked to prior and replacement assignments? lifecycle
- What approved basis describes an unmetered, shared-meter or temporarily missing-meter arrangement? exception
Reading and correction references
Reference measurement records with interval, quantity semantics, quality and correction lineage. Preserve distinctions among cumulative registers, interval usage and derived estimates. The local index neither calculates bills nor certifies settlement quantities.
Reading and correction references
Reference measurement records with interval, quantity semantics, quality and correction lineage. Preserve distinctions among cumulative registers, interval usage and derived estimates. The local index neither calculates bills nor certifies settlement quantities.
- What quantity, unit, scale and direction does each linked reading express? measurement
- Which interval and time convention bind the reading to the point assignment? temporal
- Which source, quality flag and supersession evidence qualify a corrected or estimated reading? provenance
Service continuity and external terms Proposed service-point context for service continuity and external terms.
Service state and transitions
Separate point registration, physical availability and contractual service state. Record authorized evidence of commissioning, interruption, restoration or retirement with time and reason. A local state update never operates a switch or valve.
Service state and transitions
Separate point registration, physical availability and contractual service state. Record authorized evidence of commissioning, interruption, restoration or retirement with time and reason. A local state update never operates a switch or valve.
- What registration and physical availability states are currently asserted for the point? state
- Which evidenced event changed a service state and when did it take effect? event
- Which role and external authorization support the recorded transition? authority
Party and commercial bindings
Attach time-qualified operator, served-party, contract and tariff references only where applicable. These are proposed record bindings, not claims of universal market rules. Account, tariff, supplier-switch and entitlement lifecycles remain externally mastered.
Party and commercial bindings
Attach time-qualified operator, served-party, contract and tariff references only where applicable. These are proposed record bindings, not claims of universal market rules. Account, tariff, supplier-switch and entitlement lifecycles remain externally mastered.
- Which operator, customer or other responsible role is bound to this point during the stated interval? ownership
- Which external agreement or tariff revision applies to each service or usage component? relationship
- What unresolved overlap or gap prevents treating a commercial binding as authoritative? constraint
Evidence and controlled exchange Proposed service-point context for evidence and controlled exchange.
Disclosure context and retention
Proposed local governance separates point topology, customer links and usage payloads. Disclosure requires a profile-defined purpose and authority; consent is one possible basis rather than a universal rule. Aggregation alone does not establish anonymity.
Disclosure context and retention
Proposed local governance separates point topology, customer links and usage payloads. Disclosure requires a profile-defined purpose and authority; consent is one possible basis rather than a universal rule. Aggregation alone does not establish anonymity.
- Which recipient may access each point, customer-link or usage scope for which purpose? access
- What evidence permits release of a derived usage view without exposing restricted linked data? privacy
- Which retention rule, hold or disposal decision governs each local record and payload? retention
Revision and exchange assurance
Bind every exchange to source identity, model revision, transformation and loss report. Preserve disputed assertions until authorized resolution, subject to retention policy. Conceptual alignment is not executable schema conformance.
Revision and exchange assurance
Bind every exchange to source identity, model revision, transformation and loss report. Preserve disputed assertions until authorized resolution, subject to retention policy. Conceptual alignment is not executable schema conformance.
- Which source revision and responsible role support the current point assertions? provenance
- What checks and unresolved errors qualify this exported view? validation
- How are local identifiers, virtual usage points and time values mapped without changing their meaning? interoperability
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- entity
- Navigation path
- NAV.PHY.BLT.UTL
- Domain
- PHY.BLT.UTL
- Industry
- Cross-industry
- Tags
- utilityservicepointphy.blt.utl
- Also called
- U5
What it is Filled
A proposed entity for one authority-qualified water, heat, electricity or sewage service interface between a network and served place, including planned or retired points. The root is neither a meter, asset, billing account, virtual aggregate nor executable utility controller.
In scope
- Identity, service class, location, recognition evidence and network demarcation
- Qualified properties, metering assignments, reading references and service-state evidence
- Time-bounded party and terms references, disclosure context and revision assurance
Out of scope
- Network topology computation, pipe and cable asset lifecycle, building and premises lifecycle
- Meter hardware maintenance, measurement master storage, billing, tariff calculation and settlement
- Physical actuation, switching, disconnection authorization, safety certification and operational work execution
- Virtual portfolio aggregates as root instances; gas and telecommunications extensions require separate evidence
Why it exists Filled
Describe one persistent utility service interface and its evidence-backed point-specific bindings.
Distinguishing features Derived, awaiting review
- Unlike WM-BLT-002: Served premises and occupancy remain externally mastered; carry only point-to-place bindings.
- Unlike WM-BLT-001: Building master and structural lifecycle stay external; legacy U1 is mapped specifically to Building / Structure, not every shared-alias row.
- Unlike WM-BLT-003: Network and asset masters own topology and maintenance; local references do not recalculate flow or control equipment.
- Unlike WM-PER-001: Person identity and lifecycle stay external; store purpose-limited party references.
- Unlike WM-ORG-001: Organization identity stays external; local operator and steward role bindings convey no corporate ownership claim.
- Unlike External meter, measurement, work-order, agreement and tariff masters: Profile must pin these bindings before runtime use. Local records carry references and applicability only.
- Unlike ESPI UsagePoint: Partial alignment: virtual aggregates are not equivalent to physical interfaces; versioned mapping and tests required.
- Unlike INSPIRE Utility Networks: Align external network link semantics without owning network nodes, pipes or cables.
- Unlike SOSA/SSN and PROV-O: Conceptual observation and assertion-lineage alignment; no RDF implementation or conformance claim.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- Deny by default; evaluate recipient, purpose, authority, field scope and time in the external adopting access service.
Only with a human decision
- Consent is not asserted to be the sole lawful basis.
May
- Register point evidence: Proposed unimplemented local record operation: register point evidence.
- Record interface bindings: Proposed unimplemented local record operation: record interface bindings.
- Record metering assignment change: Proposed unimplemented local record operation: record metering assignment change.
- Index observation or reading: Proposed unimplemented local record operation: index observation or reading.
- Record evidenced service transition: Proposed unimplemented local record operation: record evidenced service transition.
- Prepare scoped review projection: Proposed unimplemented local record operation: prepare scoped review projection.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Derived, awaiting review
- Consent is not asserted to be the sole lawful basis.
- Current legal, engineering safety, licensing, privacy and operational applicability are not determined.
- Legacy consent-only access and claimed conformance are not carried forward; authority and conformance require separate evidence.
Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.
Owners Filled
Steward
Owner archetype: utility service-point steward; identify the accountable role and authority in the adopting Dimension.
Roles
- Service-point steward
- Govern identity, boundary and binding revisions.
- Utility evidence contributor
- Supply authorized observations and work evidence without expanding access.
- Measurement data steward
- Resolve channel attribution, quality and correction references.
- Data access reviewer
- Review recipient scope, purpose, release risks and retention decisions.
- Model reviewer
- Check mappings, omissions and draft holds before adoption.
Links to other meta-models Filled
references
- WM-BLT-002 - Served premises and occupancy remain externally mastered; carry only point-to-place bindings.
- WM-BLT-001 - Building master and structural lifecycle stay external; legacy U1 is mapped specifically to Building / Structure, not every shared-alias row.
- WM-BLT-003 - Network and asset masters own topology and maintenance; local references do not recalculate flow or control equipment.
- WM-PER-001 - Person identity and lifecycle stay external; store purpose-limited party references.
- WM-ORG-001 - Organization identity stays external; local operator and steward role bindings convey no corporate ownership claim.
- External meter, measurement, work-order, agreement and tariff masters - Profile must pin these bindings before runtime use. Local records carry references and applicability only.
aligned
- ESPI UsagePoint - Partial alignment: virtual aggregates are not equivalent to physical interfaces; versioned mapping and tests required.
- INSPIRE Utility Networks - Align external network link semantics without owning network nodes, pipes or cables.
- SOSA/SSN and PROV-O - Conceptual observation and assertion-lineage alignment; no RDF implementation or conformance claim.
neighbor
- WM-BLT-002 - Served premises and occupancy remain externally mastered; carry only point-to-place bindings.
- WM-BLT-001 - Building master and structural lifecycle stay external; legacy U1 is mapped specifically to Building / Structure, not every shared-alias row.
- WM-BLT-003 - Network and asset masters own topology and maintenance; local references do not recalculate flow or control equipment.
- WM-PER-001 - Person identity and lifecycle stay external; store purpose-limited party references.
- WM-ORG-001 - Organization identity stays external; local operator and steward role bindings convey no corporate ownership claim.
- External meter, measurement, work-order, agreement and tariff masters - Profile must pin these bindings before runtime use. Local records carry references and applicability only.
- ESPI UsagePoint - Partial alignment: virtual aggregates are not equivalent to physical interfaces; versioned mapping and tests required.
- INSPIRE Utility Networks - Align external network link semantics without owning network nodes, pipes or cables.
- SOSA/SSN and PROV-O - Conceptual observation and assertion-lineage alignment; no RDF implementation or conformance claim.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier with issuing namespace
- Governed global identifier or IRI
- UUID or ULID assigned by adopting Dimension
Direct properties required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Register point evidence: Proposed unimplemented local record operation: register point evidence.
- Record interface bindings: Proposed unimplemented local record operation: record interface bindings.
- Record metering assignment change: Proposed unimplemented local record operation: record metering assignment change.
- Index observation or reading: Proposed unimplemented local record operation: index observation or reading.
- Record evidenced service transition: Proposed unimplemented local record operation: record evidenced service transition.
- Prepare scoped review projection: Proposed unimplemented local record operation: prepare scoped review projection.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- PROV-O: The PROV Ontology
- RFC 3339: Date and Time on the Internet: Timestamps
Context of use required Filled
- NMI procedure evidence is specific to the Australian NEM; the index marks v7.5 as future relative to this run.
- EPA inventory examples do not establish current universal material reporting duties.
- INSPIRE distinguishes utility network types; the proposed service-point root is a local design, not an INSPIRE class.
Sources Filled
- Metering procedures, guidelines and processes - Australian Energy Market Operator
- Planning and Developing a Service Line Inventory - United States Environmental Protection Agency
- INSPIRE Data Specification on Utility and Government Services - Technical Guidelines - INSPIRE Maintenance and Implementation Group
- Semantic Sensor Network Ontology - World Wide Web Consortium
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Aggregated Data with Green Button - Green Button Alliance
- [FB_01] Usage Data Common - Green Button Alliance
- RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force
Open questions
- Verify exact source editions, direct retrieval, source licensing and utility-specific applicability before closing the source hold.
- Develop pinned utility profiles and test virtual aggregates, shared meters, meter exchanges, corrected readings, split responsibility and restricted historical usage.
- Restore independent external review before any canonical or publishable-draft promotion.
- Executable nested data schemas, pinned external master bindings and adversarial instance fixtures.
- Detailed thermal return, sewer discharge, unmetered allocation, multi-feed and embedded-network mappings require domain review.
- Current legal, engineering safety, licensing, privacy and operational applicability are not determined.
- IEC CIM and DLMS/COSEM wildcard imports from U5 are deferred until exact editions, licensing and mappings are reviewed.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-blt-004-utility-service-point/spec.yaml