IEEE 1730 1-2013 en Recommended Practice for Distributed Simulation Engineering and Execution Process Multi-Architecture Overlay (DMAO) (IEEE Computer Society)《.pdf

1、 IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process Multi-Architecture Overlay (DMAO) IEEE Std 1730.1-2013 IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process Multi-Architecture Overlay (DMAO) Sponsor Simulation Interoperability

2、Standards Organization (SISO) of the IEEE Computer Society Approved 23 August 2013 IEEE-SA Standards Board Abstract: A recommended practice for applying the Distributed Simulation Engineering and Execution Process (DSEEP) to the development and execution of distributed simulation environments that i

3、nclude more than one distributed simulation architecture is described. The distributed simulation architectures to which the recommended practice applies include Distributed Interactive Simulation (DIS), High Level Architecture (HLA), and Test and Training Enabling Architecture (TENA). The DSEEP Mul

4、ti-Architecture Overlay (DMAO) identifies and describes multi-architecture issues and provides recommended actions for simulation environment developers faced with those issues. The DMAO also augments the DSEEP lists of inputs, recommended tasks, and outcomes with additional inputs, recommended task

5、s, and outcomes that apply to multi-architecture simulation environments. This document is an overlay to the DSEEP, which is a separate recommended practice. Keywords: DIS, Distributed Interactive Simulation, distributed simulation, Distributed Simulation Engineering and Execution Process, DMAO, DSE

6、EP, High Level Architecture, HLA, IEEE 1730, IEEE 1730.1, multi-architecture, systems engineering methodology, TENA, Test and Training Enabling Architecture The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2013 by The Institute of Elec

7、trical and Electronics Engineers, Inc. All rights reserved. Published 1 November 2013. Printed in the United States of America. IEEE is a registered trademark in the U.S. Patent fitness for a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness of mat

8、erial. In addition, IEEE disclaims any and all conditions relating to: results; and workmanlike effort. IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.” Use of an IEEE standard is wholly voluntary. The existence of an IEEE standard does not imply that there are no other ways to p

9、roduce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments rece

10、ived from users of the standard. In publishing and making its standards available, IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity nor is IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utili

11、zing any IEEE Standards document, should rely upon his or her own independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE standard. IN NO EVENT SHALL IEEE BE

12、LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT L

13、IABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE. Translations The IEEE consensus development process involve

14、s the review of documents in English only. In the event that an IEEE standard is translated, only the English version published by IEEE should be considered the approved IEEE standard. Official statements A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Bo

15、ard Operations Manual shall not be considered or inferred to be the official position of IEEE or any of its committees and shall not be considered to be, or be relied upon as, a formal position of IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on

16、IEEE standards shall make it clear that his or her views should be considered the personal views of that individual rather than the formal position of IEEE. Comments on standards Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of membership affilia

17、tion with IEEE. However, IEEE does not provide consulting information or advice pertaining to IEEE Standards documents. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Since IEEE standards represent a consensus o

18、f concerned interests, it is important that any responses to comments and questions also receive the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to comments or question

19、s except in those cases where the matter has previously been addressed. For the same reason, IEEE does not respond to interpretation requests. Any person who would like to participate in revisions to an IEEE standard is welcome to join the relevant IEEE working group. Comments on standards should be

20、 submitted to the following address: Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USA Laws and regulations Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not imply compl

21、iance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these docu

22、ments may not be construed as doing so. Copyrights IEEE draft and approved standards are copyrighted by IEEE under U.S. and international copyright laws. They are made available by IEEE and are adopted for a wide variety of both public and private uses. These include both use, by reference, in laws

23、and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making these documents available for use and adoption by public authorities and private users, IEEE does not waive any rights in copyright to the documents. Photocopies Su

24、bject to payment of the appropriate fee, IEEE will grant users a limited, non-exclusive license to photocopy portions of any individual standard for company or organizational internal use or individual, non-commercial use only. To arrange for payment of licensing fees, please contact Copyright Clear

25、ance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. Updating of IEEE Standards documents Users of IEEE Standar

26、ds documents should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the documen

27、t together with any amendments, corrigenda, or errata then in effect. Every IEEE standard is subjected to review at least every ten years. When a document is more than ten years old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of some value

28、, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE standard. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda

29、, or errata, visit the IEEE-SA Website at http:/ieeexplore.ieee.org/xpl/standards.jsp or contact IEEE at the address listed previously. For more information about the IEEE SA or IEEEs standards development process, visit the IEEE-SA Website at http:/standards.ieee.org. Errata Errata, if any, for all

30、 IEEE standards can be accessed on the IEEE-SA Website at the following URL: http:/standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata periodically. Patents Attention is called to the possibility that implementation of this standard may require use of sub

31、ject matter covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has filed a statement of assurance via an Accepted Letter of Assuranc

32、e, then the statement is listed on the IEEE-SA Website at http:/standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without compensation or under reasonable rates, with reasonable ter

33、ms and conditions that are demonstrably free of any unfair discrimination to applicants desiring to obtain such licenses. Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not responsible for identifying Essential Patent Claims for which a license m

34、ay be required, for conducting inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of

35、 this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. Copyright 2013 IEEE. All rights reserved. vi Parti

36、cipants At the time this IEEE recommended practice was completed, the DSEEP Multi-Architecture Overlay (DMAO) Product Development Group (PDG) Working Group had the following membership: Robert Lutz, Chair * Roy Scrudder, Vice Chair * Martin Adelantado William Beebe Jake Borah * Dannie Cutts Nico de

37、Reus Michael Egnor Sarah Epps * John Fay Dan Gregory Paul Gustavson * Frank Hill Jean-Louis Igarza Kurt Lessman Jennifer Lewis Wayne Lindo * Paul Lowe William Luebke Lance Marrou James McCall Bjorn Mller Katherine L. Morse * Eckehard Neugebauer Mikel D. Petty * Richard Reading * John Rutledge Steven

38、 Sheasby Edward Shen Robert Siegfried * Marcy Stutzman Cam Tran Grant Tudor Tom van den Berg * Denotes member of the PDG Drafting Group. The following members of the individual balloting committee voted on this recommended practice. Balloters may have voted for approval, disapproval, or abstention.

39、Tom Berg Jake Borah Juan Carreon Keith Chow Paul Croll Sarah Epps David Fuschi Randall Groves Frank Hill Werner Hoelzl Noriyuki Ikeuchi Yuri Khersonsky Murray Little Greg Luri Robert Lutz Edward McCall James McCall Bjorn Mller Katherine L. Morse Charles Ngethe Richard Reading Robert Robinson Christo

40、pher Rouget Peter Ryan Randy Saunders Bartien Sayogo Roy Scrudder Steven Sheasby Gil Shultz Thomas Starai Eugene Stoudenmire Walter Struppler Gerald Stueve Marcy Stutzman Cam Tran Thomas Tullia John Vergis Jingxin Wang Daidi Zhong Copyright 2013 IEEE. All rights reserved. vii When the IEEE-SA Standa

41、rds Board approved this recommended practice on 25 August 2013, it had the following membership: John Kulick, Chair David J. Law, Vice Chair Richard H. Hulett, Past Chair Konstantinos Karachalios, Secretary Masayuki Ariyoshi Peter Balma Farooq Bari Ted Burse Wael William Diab Stephen Dukes Jean-Phil

42、ippe Faure Alexander Gelman Mark Halpin Gary Hoffman Paul Houz Jim Hughes Michael Janezic Joseph L. Koepfinger* Oleg Logvinov Ron Petersen Gary Robinson Jon Walter Rosdahl Adrian Stephens Peter Sutherland Yatin Trivedi Phil Winston Yu Yuan *Member Emeritus Also included are the following nonvoting I

43、EEE-SA Standards Board liaisons: Richard DeBlasio, DOE Representative Michael Janezic, NIST Representative Don Messina IEEE Standards Program Manager, Document Development Michael Kipness IEEE Standards Program Manager, Technical Program Development Copyright 2013 IEEE. All rights reserved. viii Int

44、roduction This introduction is not part of IEEE Std 1730.1-2013, IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process Multi-Architecture Overlay (DMAO). Modeling and simulation (M the mix of ground-truth (simulation) data with non-ground-truth (operational or live)

45、data; and time, space, and position information (TSPI) updates. The capabilities provided by todays distributed simulation architectures are designed to address such issues and allow coordinated runtime interaction among participating simulations. Three distributed simulation architectures are in co

46、mmon use in the M design activities for member application modifications and/or new member applications are performed; required functionalities are allocated to the member applications; and a plan is developed for development and implementation of the simulation environment. Step 4: Develop simulati

47、on environment. The simulation data exchange model (SDEM) is developed; simulation environment agreements are established; and new member applications and/or modifications to existing member applications are implemented. Step 5: Integrate and test simulation environment. All necessary integration ac

48、tivities are performed, and testing is conducted to verify that interoperability requirements are being met. Step 6: Execute simulation. The simulation environment is executed and the output data from the execution is preprocessed. Step 7: Analyze data and evaluate results. The output data from the

49、execution is analyzed and evaluated, and results are reported back to the user/sponsor. In the DSEEP document, each of these seven steps is further decomposed into a set of interrelated lower-level activities. Each activity is characterized according to a set of required activity inputs, one or more activity outcomes, and a list of recommended specific tasks. Although these activity descriptions are identified in a logical sequence, the DSEEP emphasizes that iteration and concurrency are to be expected, not only across activities within a step but across steps as well. A