RMQ.26.5.2.1 OpenFMB Management Services Layer Through the Management Services Layer, authorized and authenticated updates with new or revised information can be downloaded by an OpenFMB Node and implemented. These functions include: OpenFMB Node operating system updates and rollback of updates OpenFMB Component initial installation and updates and rollback of updates Other functions performed by the Management Services Layer include: OpenFMB Node auditing OpenFMB Node’s computing resources (e.g. CPU, RAM, storage) and communications health monitoring and alerting Management Services Plug-ins are software components from any supplier that supplement standard Management Services functions. A Management Services Plug-in could include intrusion remediation, status of devices behind the OpenFMB Node, or policy-based device configuration rules and information. Both the Management Service Layer and Management Service Plug-ins utilize the Interface Layer and Publish-Subscribe Middleware Layer with the same functionality as described for the operational logical architecture. RMQ.26.5.2.2 OpenFMB Management Services Administration The Management Services Administration stages updates with new or revised information for the OpenFMB Nodes that it administers. It also receives audit information and alerts and performs near-real-time OpenFMB Node health monitoring. The remote Management Services Administration communicates with OpenFMB Nodes through the Interface Layer and Publish-Subscribe Middleware Layer with the same functionality as described for the operational logical architecture.
Figure B.2.1-16 Load Forecast Data Profile Key requirements for the Data Profile are: schedule MW value time interval version Date/Time schedule mRID associated load B.2.1.4.3 Load Reading Data Profile The Load Reading Data Profile data structure is shown in the Figure B.2.1-17 UML diagram. EnergyConsumer and Reading are its primary elements. Figure B.2.1-17 Load Reading Data Profile Key requirements for the Data Profile are: load mRID current MW current MVAR current power factor current Voltage current Operating Limits quality data/time B.2.1.4.4 Load Status Data Profile The Load Status Data Profile data structure is in the Figure B.2.1-18 UML diagram. EnergyConsumer and StringMeasurement are its primary elements.
<xs:element name="end" type="xs:dateTime" minOccurs="0"> <xs:annotation> <xs:documentation>Market end time.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="localTimeZone" type="xs:string" minOccurs="0"> <xs:annotation> <xs:documentation>Local time zone.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="start" type="xs:dateTime" minOccurs="0"> <xs:annotation> <xs:documentation>Market start time.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="status" type="xs:string" minOccurs="0"> <xs:annotation> <xs:documentation>Market Status 'OPEN', 'CLOSED', 'CLEARED', 'BLOCKED'</xs:documentation> </xs:annotation> </xs:element> <xs:element name="timeIntervalLength" type="xs:float" minOccurs="0"> <xs:annotation> <xs:documentation>Trading time interval length.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="tradingDay" type="xs:dateTime" minOccurs="0"> <xs:annotation> <xs:documentation>Market trading date</xs:documentation> </xs:annotation> </xs:element> <xs:element name="tradingPeriod" type="xs:string" minOccurs="0"> <xs:annotation> <xs:documentation>Trading period that describes the market, possibilities could be for an Energy Market: Day Hour