820   Mandatory ACSI services

Created: 08 Feb 2012

Status: In Force (green)

Part: Part 7-2 (2010; Edition 2)

Links: #1439 GI is not optional in BRCB/URCB , #1202 GI not optional

Page: 191

Clause: A.3


Category: Issue for edition 2 of this part


Considering the flexibility in client systems and server devices I recommend to state that all ACSI services are optional/conditional. In the UCAIUG we use "conformance blocks" concept. Only within a specific conformance block we can define mandatory services.


Set all services to either OPTIONAL or CONDITIONAL. For example c1) basic services (associate and server), c2) [dynamic]dataset, c3) substitution, c4) setting group [editing], c5) unbuffered reporting and c6) for buffered reporting. c9) GOOSE, c12) DOns control, c13) timesynch c14) file transfer.

Discussion Created Status
02 May 12 In Force (green)
the _final attachement correct the typos +
Client emits either Abort or Release Request. Cleient must understand Abort Request from Server.
08 Mar 12 Ballot Period
there are certainly some issues here.
Attached is the final proposal, where 8-1 is aligned with 7-2. And 7-2 is aligned with use cases.
A similar tissue exists in 8-1 with the same document as resolution.
Table A1 first applies, then table a2.
finally table a3 states about the minimun conformant implementation for a given functionality.
28 Feb 12 Ballot Period


Privacy | Contact | Disclaimer

Tissue DB v.