IEC 61850 Tissue Database

Every status a technical issue can be in, and the steps the workflow allows between them. The status this tissue is in now is the box drawn in bold.

Hide the workflow

TissueDB status workflow back to Discussion Batch Triage Accepted Discussion Drafting Implementation Verify Draft Implementation Analysis Of Compatibility Conformance Test Preparation Conformance Test Verification Ballot Period Solution Accepted Must Implement In Force Approval (N/A) Approval (Duplicate) Approval (Editorial) Approval (Future Improvement) Not Applicable Duplicate Future Improvement Editorial Must Implement (Editorial) In Force (Editorial) Legend normal route of a technical solution accepted or released → in force classification branch (working group approval) back to Discussion for rework (lines are bundled) reaching the final state
The route a technical solution takes from Triage to In Force, the working group approvals that close an issue instead, and the ways back to Discussion for rework. Opens full size in a new tab.

1143 Cooperating Clients in BRCB

Created
01 Aug 2013
Status
Not ApplicableClosed: the issue falls outside the scope of the standard. No further comments are taken. Hide the workflow
Part
Part 7-2 (2010; Edition 2)
Links
None
Page
96
Clause
17.2.2.1
Paragraph
Before Figure 24
Category
No impact on this part

Issue

The text before figure 24 reads: "The use of a particular instance of a BRCB (for example which remote clients can actually use the SetBRCBValues service on a particular BRCB) is typically pre-configured locally. The means of performing this configuration is a local issue. However, it is assumed that one or more cooperating clients (for example primary and secondary SCADA systems) may be allowed to have access to a single BRCB."

The definition that it "may be allowed that one or more cooperating client have access to a single BRCB" could be interpreted in several ways. One could be that an enabled BRCB could be used by client 1 and client 2: client 1 enables and later client 2 enables without going through client 1 disables, BRCB is disabled, client enables again ... It is nowhere defined what this statement means and how we could interoperability with such a definition.

Proposal

Define what "cooperating client" means.

DiscussionCreated
Not Applicable Not accepted. According to the definition of the BRCB handling at the server the described scenario can not happen (an enabled BRCB can by writing only be disabled). Cooperating just means that the two clients 'share' the BRCB according to the server BRCB rules, which are important for interoperability. For which reason this 'sharing' is done is purposely left open - it could be redundancy (hot-standby),different maintenance tools etc. 13 Aug 13