ServiceAssociation

Package: PowerOperationsOpenAPIModels · Source: Operations/Associations/ServiceAssociation.json

Links a service to one component that contributes to it. One record per (service, member) pair: the many-to-many reserve-participation relation is normalized here rather than carried as a list on either side, so each membership is an individually addressable row. The type of either side is resolved through the entity registry rather than duplicated here, matching the shape of PlantAssociation and SupplementalAttributeAssociation. entity_id may name a Device (the reserve case), a Branch (TransmissionInterface), or another Service (GroupReserve), so no member-type discriminator is needed. The data model library stores the same relation on the device side as Device.services.

Properties

Property	Type	Required	Unit	Description
service_id	integer	yes	—	ID of the service the membership belongs to.
entity_id	integer	yes	—	ID of the contributing member: a Device, a Branch, or another Service.