Feature #407
"Vendor/User” and “Vendor/Vendor” Interoperability list
0%
PICS can be used as part of requirements specification as well as the services section of an SCL file as described in Part 6, Table 11.A user neeeds to make sure that they receive ICD files that include the service section.
(1) To my knowledge, the PICS in 60870-5-101 / -104 are more or les the same like the pics in 61850. A vendor can use that list to declare what his device is supporting, and a user can include that list in his requirement specification.
Description
"Vendor/User” and “Vendor/Vendor” Interoperability list (structure of User “mandatory” fields, an agreement between two parties what is required and fulfilled (Data types, LNs, services, modeling, comm. requirements, etc)) as in IEC 60870-5-101/104. This is not fulfilled by PICS (Protocol Implementation Conformance Statements that contain information (could typically be optional parts, specific restrictions, or add-ons) regarding the ACSI). PICS are Vendor statements of what IED is capable of.
There should be User document to correlate to Vendors specifications and mitigate implementation problems.
These types of lists/tables latter allow describing the communication between subsystems.
Updated by Carlos Rodriguez del Castillo about 3 years ago
- Subject changed from "Vendor/User” and “Vendor/Vendor” Interoperability list (structure of User “mandatory” fields, an agreement between two parties to "Vendor/User” and “Vendor/Vendor” Interoperability list
- WG10 Proposal changed from PICS can be used as part of requirements specification as well as the services section of an SCL file as described in Part 6, Table 11. A user neeeds to make sure that they receive ICD files that include the service section. to PICS can be used as part of requirements specification as well as the services section of an SCL file as described in Part 6, Table 11.A user neeeds to make sure that they receive ICD files that include the service section.