1265   BCR counter representation

Created: 16 May 2014

Status: In Force (green)

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

Links:

Page: 30

Clause: 7.3.9

Paragraph:

Category: Issue for edition 2 of this part

Issue

The current conditions at BCR are beneath a simple counter specifically defined for energy counting, especially with the additional freezing feature. There exist further possibilities to implement counters, e.g. a pure periodically frozen value, different freezing conditions etc. Especially for the mandatory LCCH.TxCnt.actVal (dchg) will the inclusion into an event based report be deadly. The typical application here is just to have frVal, frPd, frRs. Similarly it is worthwhile to have LCCH.RxCnt and RedRxCnt synchronized, i.e. additionally strTm with same value.

Proposal

Modify the existence conditions of the data attributes as follows:
actVal no longer mandatory, but at least one of actVal / t and frVal/frTm shall exist. q applies to both or to the chosen value.
pulsQty optional (default is 1 if missing)
frEna conditional(frVal) optional - freezing might not be switchable.
strTm conditional (frVal) optional - synch of period might not be needed.
frPd / frRs conditional (frVal) mandatory - specify freezing period and counter reset handling at freeze, even if actVal (dchg) not visible.

Discussion Created Status
22 Nov 15 In Force (green)
to apply for Ed 2.1
Final proposal to support
1. counters that only have the frozen value and no actual value
2. freezing that is not synchronized to a start time:

1) actVal no longer mandatory, but at least one of the pairs actVal/t and frVal/frTm shall exist.

2) Change strTm to optional (Forbidden if frVal not present)

However, pulsQty remains M and frEna presence condition remains as is and can be valKind=RO if its change is not allowed over the communication channel
21 Oct 15 Ballot Period
final proposal for Ed2.1

1) actVal no longer mandatory, but at least one of actVal / t and frVal/frTm shall exist.

2) pulsQty remains M

3) frEna presence condition remains and can be valKind=RO if its change is not allowed over the communication channel
25 Sep 15 Discussion (red)
The usefulness of requiring an Attribute in SCL to be set as the Standard defines it in the model is questionable. If I have no choice - why do I need to repeat it in SCL - no surprise that the SCL files get large, if we have them full of superfluous information.

But ok under that fact that actVal no longer mandatory, but at least one of actVal / t and frVal/frTm shall exist.

I still suggest the following Points:
2. I do not think it is worth to declare pulsQty optional with a Default 1. We can set it to 1.

3. frEna can be read only through valKind - no change of condition required

25 Jun 15 Discussion (red)
back to red.
Support of Trigger option is not optional.
Device model and its description in SCL must follow it.
Therefore, not setting the dChg to true in SCL is not an option.
12 May 15 Discussion (red)
Observe that with the proposed solutionalso a statement is needed that here dchg is optional. Currently all data model validations demand that it is set as defined in the CDC definition! probably it is then easier to make actVal optional... 28 Apr 15 Ballot Period
1. First of all, I would not recommend to configure a Report with data Change on the data object LCCH.TxCnt.actVal.

However, to prevent that possibility, the instantiated data model can exclude the Trigger Option for this data object through SCL by Setting the SCL Attribute "dchg" to FALSE for that DA (or by omitting it, since Default FALSE).

So in my opinion no need to make actVal optional.

2. I do not think it is worth to declare pulsQty optional with a Default 1. We can set it to 1.

3. frEna can be read only through valKind - no chnage of condition required

4. Agreed to make strTm optional

So my proposal:
Change strTm to optional (Forbidden if frVal not present)

24 Apr 15 Ballot Period
It makes sense to me.
BCR in Ed2 have been wider used in the logical node class and the presence condition should be adapted so that application have a better dealing with the different counters.
19 May 14 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1