Checking SCL Files for Improved Interoperability

1. Checking SCL Files for Improved Interoperability • Joe Stevens • Triangle MicroWorks • jstevens@trianglemicroworks.com

2. Agenda • Background on SCL Files • What is SCL, how is it defined, and how is it used? • Why Check? • The benefits of checking SCL Files • What Should Be Checked? • Important checks that should be covered • Resources for Checking SCL Files • How you can check your SCL Files

3. Background on SCL Files • System Configuration description Language (SCL) • XML based, self-describing language • Configures all IEC 61850 devices in the system • SCL Definitions Include: • IED Capabilities - Services, Control Blocks, Sampled Values, GOOSE • Object Models for IED’s – Logical Nodes, Data Objects, Data Attributes, Enums • Communication configuration – addressing, Data Sets, GOOSE publishing, External References • Substation configuration – voltage levels, bays, equipment, electrical connectivity

4. Why Check? • The Benefits of Checking SCL Files • Improve the interoperability of devices • Reduce time spent testing and debugging • Help streamline the engineering process IEC 61850 Engineering Process • Specification • SSD • System Configuration • SCD • IED Configuration • CID • IED Template • ICD

5. What Should Be Checked? Level 5 – Vendor Specific Many different levels to checking SCL: Level 4 – Substation Level Level 3 – Communication Configuration Level 2 – Object Model Resolution Level 1 – Schema Validation Essential for parsing by devices Easiest to discover with many tools Important for system level communications Only a portion can be checked by tools Checking tools can automate Models are large and the standard is long Important for upfront system specification Checked by Vendor Tools They are all important!

6. Resources for Checking SCL Files How can you check your SCL Files? Vendor Tools: System Configuration Tools, IED Configuration Tools Third Party Tools: SCL Editors, Configuration Tools, Testing Tools Specific SCL Checking Tools Free Web Based Checking at TriangleMicroWorks.com

7. SCL Consistency and Completeness Check • Overview of Checking Performed: • Schema Validation • Object Model Resolution • Consistency Across Entire File • Completeness Compared to the Standard • Communication Section • GOOSE and Sampled Value Control Blocks • Match Access Points and Logical Devices to IED • Check for Mismatches in Control Blocks and Services

8. SCL Consistency and Completeness Check • Object Model Checks Performed: • Ensures that the entire Object Model fully resolves • Verifies the Object Model is consistent with the standards • Check that mandatory elements are present • Check type and functional constraints • Find any name, order, and type inconsistencies for LN’s, DO’s, DA’s, Enums • Verifies all instance data in IED section: • Path is correct and found in object model • Initial value is valid based on given type in the object model • Verifies that Data Set paths resolve in the Object Model • Verify that Control Blocks refer to an existing Data Set in the model • IEC 61850 -6, -7-3, -7-4, -7-410 (Hydro), -7-420 (DER), 61400-25 (Wind Turbines)

9. TriangleMicroWorks.com/SCLWebCheck