This part of IEC 61850, which is a Technical Report, describes scheduling for devices using IEC 61850.<\/p>\n
The parameters, which identify this new namespace, are:<\/p>\n
Namespace Version: 2017<\/p>\n<\/li>\n
Namespace Revision: A<\/p>\n<\/li>\n
UML model file which reflects this namespace edition: wg10uml02v17-wg18uml02v11bwg17uml02v18- jwg25uml02v04c.eap, UML model version WG17UML02v18<\/p>\n<\/li>\n
Namespace release date: 2017-06-12<\/p>\n<\/li>\n
Namespace name: “(Tr)IEC61850-90-10:2017A”<\/p>\n<\/li>\n<\/ul>\n
The namespace “(Tr)IEC61850-90-10:2017A” is considered as “transitional” since the models are expected to be included in the next editions of IEC 61850-7-4xx and IEC 61850-7-3. Potential extensions\/modifications may happen if\/when the models are moved to International Standard status. Only the new data objects and CDCs that are not said inherited from existing LNs will be tagged with this namespace name. The others should still refer to the namespace where they are primarily defined.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions 3.2 Abbreviated terms 4 Requirements for schedules 4.1 Schedules for establishing time-based behaviour Tables Table 1 \u2013 Normative abbreviations for data object names <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 4.2 Relation between schedules and directly set values and parameters of the DER system 5 Principles for modelling schedules 5.1 Schedule controllers and their schedules <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 5.2 Scheduling and direct control \/ setting 5.2.1 General 5.2.2 Case when the scheduled entity is of type “controllable data object” 5.2.3 Case when the scheduled entity is of type “setting” Figures Figure 1 \u2013 Scheduling principle <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 5.3 Schedule behaviour <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 5.4 Schedule structure Table 2 \u2013 Expected behaviour of a schedule <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 5.5 Managing schedules 5.5.1 Overview 5.5.2 The state machine of the schedule Table 3 \u2013 Structure of a schedule <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | Figure 2 \u2013 State diagram for schedule <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | Figure 3 \u2013 Flow chart for transition out of running state <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 5.5.3 The role of the schedule controller <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 5.5.4 Relations between schedule controller, schedule and scheduled entity Figure 4 \u2013 Handling priorities of schedules todetermine the Active one <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 5.6 Configuration of schedules 6 IEC 61850 LNs and CDCs 6.1 CDCs of supported scheduled entities Figure 5 \u2013 Relation between schedule controller, schedulesand entity controlled <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 6.2 Package CommonDataClasses_90_10 6.2.1 General <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 6.2.2 Package CDCStatusInfo Figure 6 \u2013 Class diagram CDCStatusInfo::CDCStatusInfo90_10 <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | Table 4 \u2013 Attributes of TCS Table 5 \u2013 Attributes of ORS <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 6.3 Logical node classes 6.3.1 General Figure 7 \u2013 Class diagram LogicalNodes_90_10::LogicalNodes_90_10 <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 6.3.2 Package LNGroupF Figure 8 \u2013 Class diagram LNGroupF::LNGroupF <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | Table 6 \u2013 Data objects of FSCC <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | Table 7 \u2013 Data objects of FSCH <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 6.4 Enumerated data attribute types 6.4.1 General 6.4.2 Schedule states (ScheduleStateKind enumeration) 6.4.3 Schedule states (ScheduleEnablingErrorKind enumeration) Figure 9 \u2013 Class diagram DOEnums_90_10::DOEnums_90_10 Table 8 \u2013 Literals of ScheduleStateKind Table 9 \u2013 Literals of ScheduleEnablingErrorKind <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 6.5 SCL enumerations (from DOEnums_90_10) 6.6 Schedule implementation examples <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | Annex A (informative)Impact of Mode (Mod) on the schedule status and onthe controllable entity <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Annex B (informative)Conditions for element presence Table B.1 \u2013 Conditions for presence of elements within a context <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | Annex C (informative)Abstract classes used as a basis for new LNs\/CDCs C.1 General C.2 <> Common attributes for primitive CDC (BasePrimitiveCDC) C.3 <> LN: Domain Name: DomainLN Table C.1 \u2013 Attributes of BasePrimitiveCDC <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | Table C.2 \u2013 Data objects of DomainLN <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | Annex D (informative)Time setting related CDC and attributes D.1 General D.2 Calendar time definition (CalendarTime) Figure D.1 \u2013 Interpretation of calendar time settings <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | D.3 Time setting CDC (TSG) D.3.1 General Figure D.2 \u2013 Class diagram TSG::TSG Table D.1 \u2013 Attributes of CalendarTime <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | D.3.2 <> Time setting (TSG) D.3.3 Time setting (FC=SP) (TSG_SP) D.3.4 Time setting (FC=SG) (TSG_SG) Table D.2 \u2013 Attributes of TSG Table D.3 \u2013 Attributes of TSG_SP <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | D.3.5 Time setting (FC=SE) (TSG_SE) D.3.6 Month (MonthKind enumeration) Table D.4 \u2013 Attributes of TSG_SG Table D.5 \u2013 Attributes of TSG_SE <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | D.4 Occurrence (OccurrenceKind enumeration) D.5 Period (PeriodKind enumeration) Table D.6 \u2013 Literals of MonthKind Table D.7 \u2013 Literals of OccurrenceKind <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | D.6 Week day (WeekdayKind enumeration) Table D.8 \u2013 Literals of PeriodKind Table D.9 \u2013 Literals of WeekdayKind <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | Annex E (informative)Scheduling example Figure E.1 \u2013 LN instances and relationships involved in theimplementation of the schedule example <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | Figure E.2 \u2013 Timelines associated to the example <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Communication networks and systems for power utility automation – Models for scheduling<\/b><\/p>\n |