Name of intervening person Brief description of the changes introduced Rev # Document sent To Date Joe Zhou, Stuart Creating the outline draft for TF review V0.1 Joe Zhou, Stuart Laval Updating outline draft for TF meeting on May 1st 2015 V0.2 Joe Zhou, Stuart Laval Updating outline draft for TF as the result of NAESB call on 05/15/2015 at NREL. V0.3 Terry Saxton Updated the formatting to follow the ESPI NAESB book example V0.4 Office 6-24-2015 Saxton Updated writing assignments V0.4 NAESB Office 6-26-2015 Larry Lackey Added text for Sect. 3, model business practices, Terry Saxton 7-9-2015 Terry Saxton Updated descriptions for contents of some sections V0.5 NAESB Office 7-9-2015 LL/SL Updated model business practices 7-23-2015 LL/SL Logical architecture; update model business practices; JW systems architecture 8-7-2015 Terry Saxton Incorporated SH updates 4.5, 4.6, 5; minor edits; accepted all changes V0.6 Authors 8-30-2015 Joe Zhou, David Fulmer Update and comment throughout the document V0.6 Authors 9-10-2015 Jim Waight updated figures in the Architecture sections V0.6 Authors 9-11-2015 Larry Lackey Revised cross-cutting; added interaction patterns and some definitions; other edits V0.6 Authors 9-12-2014 Terry Saxton Overall edit of all sections V0.6 Authors and NAESB Office 9-13-2015 Terry Saxton Incorporated all updates from 9/14 meeting and renumbered some sections, updated Fig 4.3-1 V0.7 Authors and NAESB Office 9-18-2015 Larry Lackey Revised introduction and cross-cutting; misc edits V0.7 Authors 9-22-2015 Terry Saxton Incorporated changes agreed to from 9/25 meeting V0.7 Authors 9-27-2015
The interaction modeling approach focuses on integration design for the requirements identified. Each message integration line identified in use case is detailed in a UML . A describes between message pro and consumers is a sample the Recloser Status message exchange. In the , such as The ef box at the bottom of the diagram above leads to a generic sequence diagram as shown below RMQ.26.6.3. OpenFMB Profile Platform Independent Approach The information collected in the modeling process drives the data model design. OpenFMB data models are created primarily based on the IEC Common Information Model (CIM). The CIM model is a comprehensive utility industry UML model that encompasses all aspects of utility operations and planning need for distribution (IEC 61968), transmission (IEC 61970), and market communications (IEC 62325) standards. The model is used as a reference from which necessary classes, attributes, and associations are selected and transformed into OpenFMB model. Note the Platform Independent Model (PIM) approach itself does not exclude other standards as reference models.
bindings to C++ and Java for source code portability between different DDS implementations. Roles With a data-centric model DDS is useful for maintaining distributed state knowledge. Topic Names IDL identifiers start with an alphabetic character which may only be followed by alphanumeric or the underscore “_” characters. Following the approach for platform specific topic names, the format for OpenFMB DDS topic names is: Literal “OpenFMB” without quotes Literal “_” without quotes Profile Module name terminates with “Module” Literal “_” without quotes Profile name which terminates with “Profile” For example: OpenFMB_Module_Profile Publishers and Subscribers associated with all Topics use the default Partition. Quality of Service (QoS) Parameters Default DDS Quality of Service values are specified in the table on page 92, Section 2.2.3 of the DDS specification. ppropriate Quality of Service parameters at the platform independent level have been defined for different interaction patterns utilized in the sequence diagrams. Parameters for each interaction pattern are defined using combinations of reusable QoS profiles. For interoperability between participating components, the so-called RxO (Request-Offered) QoS settings are important because they require to be selected consistently on a system-wide scale. The relevant RxO QoS settings with non-default values are summarized as follows for the different profiles: Reading Interaction Pattern Data distributed with DDS under this pattern has the following DDS QoS settings attached: DDS QoS policy name Policy value applied RELIABILITY BEST_EFFORT