Draft notes on conference call 17-Jan-2012
Attendees have not read the document tables 84-88
Table 84: is import/export
SSH1 does not verify graphical view
Table 85 is modifications
Table 86 is SCD export, with DTT section allowing sharing types between IEDs, includes in SSe1 export of 2003 version
Table 87 is SCD import
Table 88 is SED file handling with handling of flows

Discussion of CC_57_1162
CH-03 - need to review test bits: Wolfgang/Roman to discuss with Klaus-Peter
8.3.1 and Figure 6 is confusing because IED might not allow direct input from time source:
Perhaps examples of PPS and/or GPS or IRIG-B or DF-77 as option 1 and SNTP(or PTP future) as option 2
Veselin: 90-4 already mentions PTP with IEEE 37.238 (need to check??) 
IEEE 1588-V2 (PTP) is now IEC 61588 V2 as dual-logo. 


Need to remove notes about backup time master in 8.3.1 because part 6 does not specify concept of priority of time sources

CN-1 and CN-2: Accepted in principle, covered by dedicated GOOSE performance tests

JP-2 : will split Figure 2 into server and client
JP-4 add reference to PIXIT
JP-5, and -7 and -8 Not accepted, CID file check can only verify that it validates with schema
JP-6 PIXIT needs to specify how to force a ConfirmEditSGValues negative response. For example, an inconsistent group of settings (this may not be possible in some devices!)
At least one vendor thinks that checking upon activation is too late
JP-9 : Veselin says one vendor did not equally space the SV messages (sometimes latency was large). There is an existing test for excessive latency ( > 3 milliseconds) so this test is not needed. we agree to not accept this comment. Performance is in SV conformance tests
Report performance test is not needed?? Do we specify a maximum latency? Does the maximim rate of reports need to be specified?
JP-11: The existing GOOSE performance tests only use Ping-Pong method. 
Maybe need additional test of GOOSE receive time directly to trip output if high-speed output is available? 
Need to report both worst-case and average time from GOOSE-in to trip output.
JP-12: if 10 double-points are not available, use 10 double, 30 boolean instead. Richard to write something
JP-14: Reject, need to follow 61850-5
JP-15 and 16: scan cycle definition is wrong. It is the inverse of number of scans per second

Richard to update comment resolution and circulate. Also discuss in Porto. 


Next meeting 7-February-2012 at 15:00 UTC

Meeting ended 16:37 UTC