1. TitleIEEE Standard for Mostly RESTful Orchestration Interface Protocol (mREST) for Orchestrating Software-Controlled Assets via Web Services ScopeThe mREST protocol defines a framework for exchanging orchestration-related information among software-controlled assets. It is largely based on the principles of Representational State Transfer (REST). It specifies a method for service discovery, constraints for defining resource relationships, and a basic set of resource definitions for achieving orchestration. The framework is customizable and extensible for multiple application domains with mechanisms for generating representations in domain-specific XML languages. PurposeThe purpose of mREST is to provide a standardized framework for a loosely-coupled, plug-and-play web services orchestration interface that can be extended to accommodate application-domain specific orchestration of software-controlled assets. The intent is that the interface be lightweight and easily implementable on a variety of new and existing otherwise heterogeneous assets. NeedThe standard will provide an open alternative to the variety of proprietary standards that exist today. Having such a standard will allow equipment developers to include standard software-controlled orchestration capabilities that may be customized to their particular industry or domain while at the same time achieving a level of uniformity with other application domains. Availability of assets with standard open web-based orchestration interfaces will enable efficient large scale coordination and data synthesis. StakeholdersAnticipated users of the mREST framework are: Developers of software-controlled assets who are interested in providing an orchestration interface Integrators of existing equipment who want to add a standard orchestration interface for integration into a larger system Developers of domain-specific orchestration protocols Developers of orchestration or monitoring software who want to coordinate software-controlled assets This standard will be referenced by IEEE Standard for Test Orchestration Interface (TOIF) for Orchestrating Resources, Observations, and Information via Web Services. The TOIF is an example of a domain-specific application of mREST – specifically in the area of test automation. 1

2. 2 TitleIEEE Standard for Test Orchestration Interface (TOIF) for Orchestrating Resources, Observations, and Information via Web Services ScopeTOIF defines a standard data interface for observing and controlling state variables in testing environments. The TOIF protocol is built on the mREST orchestration framework and can be considered a test-domain specific application of mREST. It provides a web services-based protocol for message passing, data collection, and test execution using data exchange formats defined in IEEE Automatic Test Markup Language (ATML). PurposeThe purpose of the standardized TOIF is to provide an automation interface to support scalable plug- and-play integration of heterogeneous equipment and software to perform test operations that produce archive-quality documentation. NeedThe ATML standard provides standard data exchange formats but no standard exists for using ATML in an open-standards resource-based web services environment. The standard provides a modern and more scalable alternative to the recommendations in IEEE-Std-1671-2010 Appendix D, ATML Runtime Services. StakeholdersBroadly, the end-product users of instrumentation who need to combine disparate software-controlled products on a variety of scales and produce archive-quality documentation. Specifically, NASA DoD MoD There may be others, as this technology can be used in commercial aviation or for broader applications like industrial statistical process control.

3. 3 TitleIEEE Standard for Automatic Test Markup Ontology (ATMO) for Exchanging Automatic Test Equipment and Test Information via OWL/RDF ScopeATMO defines a standard exchange medium for sharing information between components of ATSs. This information includes test data, resource data, diagnostic data, and historic data. The exchange medium is defined using RDF. This standard specifies the framework for the family of ATMO standards, and is the first in a series of ontology-based standards that will be formulated in part from reusable ontologies intended as the basis for consistency, semantic precision, interoperability, and machine-intelligible representations of standards. Any number of formats may be generated from the OWL/RDF-based specification. PurposeThe purpose of ATMO is to support TP, test asset, and UUT interoperability within an automatic test environment. ATMO accomplishes this through a standard medium for exchanging UUT, test, and diagnostic information between components of the test system. The purpose of this standard is to provide an overview of ATMO goals, define the ATMO family of standards, and specify common data elements and structures for the ATMO family of standards. NeedATML is near maturity and for schedule reasons needs to enter production. But the ultimate goal is an AI- friendly information representation, and ultimately ATML will be superseded by an ontology. While ATML begins implementation, this PAR will provide a separate track for preliminary investigation and development of a set of component ontologies which will compose the standard. ATMO is not intended as a contemporary competitor to ATML, but as a natural progression to model-based standards, with an additional focus on establishing semantic interoperability between other relevant standards. StakeholdersElements within NASA are interested in beginning an investigation of ontology for automated testing. Ultimately, DoD will become interested as well. Anticipated users of the ATMO family of standards include the following: Product (e.g., UUT) developers Product (e.g., UUT) maintainers TPS developers TPS maintainers ATE system developers ATE system maintainers Instrumentation developers Developers of ATML-based tools and systems Developers of prime mission equipment that use the supported UUT as a component

4. 4 TitleStandard for Test Orchestration Interface (TOIF) for Orchestrating Resources, Observations, and Information via Web Services ScopeThis standard defines the Test Orchestration Interfaces (TOIF) data interface for observing and controlling state variables in testing environments. The TOIF protocol is built on a Representational State Transfer (REST) framework that provides a web services-based protocol for message passing, data collection, and test execution using data exchange formats defined in IEEE Std 1671™ and IEEE Std 1636.1™. PurposeThe purpose of this standard is to provide an automation interface to support scalable plug-and-play integration of heterogeneous equipment and software to perform test operations that produce archive-quality documentation. NeedThe IEEE Std 1671™ and IEEE Std 1636.1™ standards provide standard data exchange formats. However there is no standard for using these formats in an open-standards resource-based web services environment. StakeholdersThe stake holders will include end-product users of instrumentation who need to combine disparate software-controlled products on a variety of scales and produce archive-quality documentation. Specifically, Military Aerospace Commercial aviation And could also be used for broader applications such as industrial process control.