No abstract

No abstract

PREFACEThis document provides a summary of the talks and working sessions during the "Modeling and Simulation for Emergency Response" workshop. We elected to provide a summary including the key points of the talks instead of including the presentation materials. We believe the readers will find this more useful. Based on their interest, readers can access the specific presentation through the workshop website: www.nist.gov/simresponse.For the four working sessions, we have included the summaries as provided by moderators and scribes for the sessions. Care has been taken to present the material as collected from workshop breakout session attendees by the moderators and scribes and we have refrained from adding any material. A number of acronyms have been expanded in this material for better readability. The acronyms and abbreviations are also listed in Appendix C for reference.While we have made every effort to summarize the talks and working sessions without losing the key message, readers and presenters are invited to send their comments, and/or suggestions for improvement of this document to mser_report_feedback@cme.nist.gov by January 31, 2004. An updated version of this report may be prepared by March 2004, if the feedback received warrants such a revision.Appendix A and B of this document respectively include relevant standards and modeling and simulation tools for emergency response. The information on standards and tools has been collected using Internet searches and information provided by attendees of the workshop. The information presented for each tool and standard has been adapted from referenced websites. Readers are invited to send information on additional tools, standards, and suggested revisions on the information currently included to mser_report_feedback@cme.nist.gov by February 29, 2004. We would like to release an updated version of these appendices next year.We would like to thank all the speakers who shared their valuable knowledge and time, all the participants in the workshop for providing their contribution through the working sessions, and the facilitators and scribes of the working sessions for capturing the discussions and presenting them to all attendees. We thank the vendors who provided displays of relevant tools and techniques during the workshop. We would also like to thank all the sponsors of this workshop including: NIST, NIST Manufacturing Engineering Laboratory, NIST Building and Fire Research Laboratory, NIST Advanced Technology Program, NIST Systems Integration for Manufacturing Applications program, Advanced Technology Institute (ATI), Association for Enterprise Integration (AFEI), and Oak Ridge National Laboratory. Many people contributed to the success of the workshop and it will be hard to list everyone. We would specifically like to acknowledge the efforts of the workshop organization committee who worked with the authors including: Jack Corley of ATI, David Cheeseborough of AFEI, and the following people from NISTSharon Kemmerer, Swee Leong, Mark Carlisle, and Cynthi...

• the identification of types of systems that perform, or support human agents in performing, the activities within a given domain, and• the identification of the nature and content of the interfaces required among those systems. Accordingly, the reference architecture has three parts:• Part 1 -the Activity Model -provides a model of the generic activities involved in the manufacturing process, and the information flows required to support those activities.• Part 2 -the Systems Model -identifies the manufacturing application systems, both human and automated, which perform these activities, and the interfaces required for those systems to support the identified information flows.• Part 3 -the Information Models -define formally and in detail the objects and information which appear in the interfaces.This document is Part 1 -the Activity Model. It represents the first step toward the goal of the SIMA architecture project -to identify the functions and interfaces required of manufacturing applications software systems. It is intended to provide a frame of reference for SIMA projects and similar industrial projects, which are developing "standard interface specifications". As a frame of reference, it permits such specification projects to name and "locate" the interfaces they intend to specify and assists those projects in defining the scope of those interface specifications, by identifying the functions the interface is intended to support.Companion documents will provide the other parts of the reference architecture and define a corresponding "engineering architecture" specifying for each interface the means of information exchange to be used and the representation forms for the information. Multiple engineering architectures which correspond to the reference architecture, but use different mechanisms or forms for interchange, are possible.

No abstract