2025 SPSE.HmnPrs should have constraint Omulti

Created: 28 Jan 2026

Status: Drafting Implementation

Part: Part 90-6 (2018)

Links:

Page: 263

Clause: 7.2.9.8

Paragraph: Table 40

Issue

LN: Presence monitoring Name: SPSE
jDocBuilder validation reports
LNGroupS_90_6::SPSE [constraint 'Omulti' for inexisting 'HumPrs'] IEC61850 classes that have constraints with siblings that do not exist

Proposal

Update model
Associate constraint 'Omulti' with data object HmnPrs

This allows multiple sensor inputs within a single instance of SPSE

Discussion	Created	Status
As discussed in Feb 2026 WG 17 meeting	23 Jul 26	Drafting Implementation
SPSE are expected to be able to have inputs from multiple sensors, modelled by multiple HmnPrs data objects For example these could be micro-switches on doors for different cabinets containing the automation, battery backup etc The sensors are not modelled in detail. The location or type of the sensor is unknown unless documented in descriptive text.	23 Jul 26	Discussion (red)
Discussed in Feb 2026 meeting	23 Jul 26	Accepted
what is the purpose of having Omulti Prs SPS? I think the AiPrs, DrnPrs would most likely need to have a presence condition O and not Omulti. Only one single considered area is observed here, is it not?	04 Feb 26	Triage

Privacy | Contact | Disclaimer

Tissue DB v. 26.8.15.1