HAF_A4L Interactive Electronic Technical Manual (IETM) Framework.pdf

Unclassified

Classification Marking

HAF/A4L Interactive Electronic

Technical Manual (IETM) Framework

04 December 2024

Version #0.1

Unclassified

RELEASABILITY: There are no releasability restrictions on this publication

OPR: HAF/A4LM

CERTIFIED BY: HAF/A4L

JEFFREY R. KING, Maj Gen, USAF

Director of Logistics

DCS/Logistics, Engineering & Force Protection

Table of Contents

1. Purpose and Scope

1.1 Compatibility

1.2 Printing

1.3 Web Browser Viewable

1.4 Access

1.5 Role Based Access

1.6 User Interface

1.7 IETM Filtering and Configuration Control Capability

1.8 Privacy Act Notification

1.9 Maintenance of User Configurations

1.10 Bookmarking

1.11 User Feedback Tool

1.12 Graphical User Interface (GUI)

1.13 Hot Reference (Tool Tips)

1.14 Voice Activated Commands

1.15 Review and Verification

1.16 Technical

2. Capability Requirements – Content Management System (CMS)

2.1 Storage and Accessibility

2.2 Data Segregation

2.3 Graphical User Interface (GUI)

2.4 Authentication and Access Control

2.5 Compliance and Compatibility

2.6 Object History and Retention

2.7 Editing and Validation

3. Interoperability Requirements

3.1 Systems Integration

3.2 Key aspects of interoperability:

4. Glossary

1. Purpose and Scope

This document establishes capability needs to support an Air Force unified vision and strategic alignment behind a salient Interactive Electronic Technical Manual (IETM). The objective is to digitally transform technical order capability, including improved aircraft maintenance forms documentation processes and data entry, standardized formatting, and integral analytic capabilities. Additional objectives include facilitation of interoperability in sortie generation activities between Air Force Mission Designated Series (MDS) and interoperability between joint forces and partner nations aircraft generation activities.

Current efforts to modernize and link our tech data manuals, maintenance information systems, and decision-making tools are isolated, experience limited success, and lack further Logistics

Information Technology (Log IT) connectivity. Additionally, limited resources and insuffient strategic alignment has limited significant implementation of solutions across the United States

Air Force (USAF) fleet. Industry’s rapid advancement in data management, software development, and application programming interface technology now illuminates new opportunities for establishing and implementing a unified integrated IETM. A holistically designed solution will serve as the starting point to achieve an expandable integrated capability across our Maintenance and Logistics systems. This capability is both a highly desired field-level demand and supported by our weapon system program offices.

This document includes a combination of baseline requirements defined in the MIL-STD-3048, Department of Defense Standard Practice: Air Force Business Rules for the Implementation of

S1000D, as well as additional identified capabilities intended to establish a seamless maintenance user experience.

1.1 Compatibility

1.1.1 Viewer Application must be compatible with the S1000D version identified in the most current MIL-STD-3048.

1.1.2 Viewer Application must meet requirements for accreditation on the Air Force

Network (AFNet).

1.1.3 Viewer Application must be configurable to integrate within the Enhanced

Technical Information Management System (ETIMS) and Technical Order Authoring and Publishing (TOAP) framework and be capable of presenting in digital format in accordance with (IAW) TO 00-5-1 and TO 00-5-3.

1.1.4 Viewer Application must be software and hardware agnostic (i.e., compatible with multiple Operating Systems (OS)/iOS/Android/PC devices), and be compatible with Air

Force Standard Desktop Configuration (SDC).

1.1.5 Viewer Application must include a Content Management System (CMS) capability to manage, author, and publish TO software source content data, enforcing authoring and publishing Technical Manual Standards and Specifications (TMSS) compliance.

1.1.6 Viewer Application must be capable of being delivered on standard removable storage devices.

1.1.7 Viewer Application must be viewable as a standalone executable file, meaning operating with full functionality when not connected to the internet.

1.2 Printing

1.2.1 Viewer Application must print in compliance with requirements defined in most current MIL-STD-3048.

1.2.2 Print screen. The IETM shall provide users the capability to print the screen currently being viewed. TO policy must be followed with regards to printing excerpts

(such as printing distribution and security statements).

1.2.3 Data module printing. The IETM shall provide users the capability to print the current data module being viewed. TO policy must be followed with regards to printing excerpts (such as printing distribution and security statements).

1.2.4 Printing data module and linked data. The IETM shall provide users the capability to print the current data module (as well as checklists, associated figures) being viewed as well as any data referenced by the data module. Printed linked data shall be limited to one level of linking (i.e., any referenced data in the linked data shall not also be printed).

1.2.5 Figure printing. The IETM shall provide users the capability to print the current figure being viewed.

1.3 Web Browser Viewable

1.3.1 The IETM technical content shall be viewable in a standard web browser that is part of the Air Force SDC. AFNET approved web browser plug-ins or helper applications may be used to enable additional IETM functionalities that are not possible with the standard browser.

1.4 Access

1.4.1 Login capability

1.4.1.1 Must be able to log in with a Common Access Card (CAC) or equivalent authentication process.

1.5 Role Based Access

1.5.1 Viewer Application shall be customizable based on user roles. Examples of customization include:

1.5.1.1 Verification events

1.5.1.2 Enabling/disabling menu options

1.5.1.3 Allowing/disallowing access of certain data modules

1.5.1.4 Administrative functions such as user management

1.5.1.5 Retrieval of user activity reports

1.5.1.6 Organic authoring capability

1.6 User Interface

1.6.1 Global and Local announcements

1.6.1.1 Viewer Application must be able to display advisories, notifications, supplements, time compliance technical orders (TCTO), and other “pop up” information upon login to the viewer application and display real time announcements when in connected mode (e.g., connected to the network).

1.6.2 Global, Local, and User annotations

1.6.2.1 Global - Air Force Instruction, policy memo, emergency or urgent information, or supplemental data can be seen by all users.

1.6.2.2 Local – Wing level, base level, MAJCOM level or any similar level and can be seen by the applicable local users at the specified level, whether it's a local instruction or policy.

1.6.2.3 User – Can be added or deleted at the end user's discretion and is retained after the user session.

1.7 IETM Filtering and Configuration Control Capability

1.7.1 Viewer Application must have complete and real time filtering capability to render product, system and configuration information to the user based on, but not limited to asset tail number, pre and post TCTO completion, organization, health, software, and weapon component configuration and applicability. In addition, the viewer should have the ability to display unfiltered content with applicability tags or a quick reference listing displayed on the contents.

1.8 Privacy Act Notification

1.8.1 Viewer Application must have a Privacy Act Statement on the access request page

IAW DODI 5400.11-R. The statement will cite the Federal statute or Executive Order that authorizes collection, the purpose of collection, the routine use of the collected information, its mandatory use, and that failure to provide the information will result in refusal of access to the viewer. The Government will assist with the final wording of the statement.

1.9 Maintenance of User Configurations

1.9.1 Viewer Application will maintain user selected aircraft tail number/serial number, and the selected configuration until user selects another tail number/serial number or the current session ends. User configurations shall be retained when switching between individual manuals or returning to the home screen.

1.10 Bookmarking

1.10.1 Viewer Application shall enable the user to bookmark data modules for easy future access. The icon to access the bookmark shall be on a persistent toolbar. The list of bookmarks shall be on a modal or equivalent to allow access without leaving the currently displayed technical data. Viewer application shall enable bookmarks to be tied to a specific user login.

1.11 User Feedback Tool

1.11.1 Viewer Application shall provide an easily identifiable persistent feedback option in top menu that captures the user’s identity, current viewed Data Module (DM) Code, the aircraft tail/serial number, and the selected configuration.

1.11.2 The feedback tool shall include a field for user input regarding the perceived discrepancy.

1.11.3 The tool shall include a method by which the user can indicate whether an ETIMS

Recommended Change has or has not been submitted.

1.11.4 Upon feedback submittal a notification shall be sent to users assigned to a

“feedback receiver” role, with a link to the entered feedback.

1.12 Graphical User Interface (GUI)

1.12.1 Viewer Application must allow scaling of GUI without losing functionality.

1.12.2 Viewer Application shall provide users the capability to restore the IETM interface to a default view. Frames and other parts of the IETM interface that have been resized, moved, or hidden will be reset to the IETM's default setting.

1.12.3 Viewer Application will allow user to toggle from Light Mode to Dark Mode.

1.13 Hot Reference (Tool Tips)

1.13.1 Viewer Application shall display tool tips to the user on relevant “mouse overs”.

At a minimum, all IETM menu options shall have tool tips as well as all acronyms and footnotes displayed in the technical data.

1.14 Voice Activated Commands

1.14.1 Viewer Application may provide users the capability to navigate through the technical content via voice commands.

1.15 Review and Verification

1.15.1 Redlines for In-Process Reviews (IPR), Verification Pre-Publication Review

(PPR)/Final Verification.

1.15.1.1 Viewer Application shall provide users the capability to redline/annotate text using markings for deletions, insertions, and changes. These markings are saved as feedback to correct/improve the publication during development and verification.

1.15.1.2 Viewer Application must support IPR, verification, PPR actions to allow for the capture of redline discrepancies/deficiencies in technical content and attaching comments to the redlines. Viewer application must capture all redlines, generate a report of all pertinent data (redlines, and deficiency failure codes compiled per category with the sum of each code), and an AF Form 158 or equivalent. The report and AF Form 158 must be capable of print and digital delivery.

1.16 Technical

1.16.1 Maximize Use of Entire Screen

1.16.1.1 Viewer Application must be designed to maximize the amount of screen that can be used for viewing the technical content and figures, while still providing accessibility to the features documented in the functionality matrix.

1.16.2 External References

1.16.2.1 Viewer application must be able to use external reference publication links in Data Modules to open the referenced publications.

1.16.3 Help Documentation

1.16.3.1 The IETM shall have a "Help" option which provides users with documentation and guidance on how to use the IETM, which allows for self-instruction.

1.16.3.2 This help section shall be available in offline mode.

1.16.4 Data Collection Updates

1.16.4.1 Viewer Application must deliver collected data immediately upon connection/reconnection to the network from disconnected (standalone) mode.

1.16.5 Support for Condition Based Maintenance

1.16.5.1 Viewer application must capture critical user data and maintenance transactional data in a non-proprietary format to support USAF analytics and prognostics software.

1.16.6 Dashboard Analytic Capabilities

1.16.6.1 Viewer Application and associated software shall support role-based advanced analytic capabilities and rendering configurable metrics in dashboards.

1.16.7 Active Change Indications and Markings

1.16.7.1 The IETM shall display appropriately authored change markers in the technical data and provide users with the capability to toggle the display of change markers on/off.

1.16.8 Wire/Fluid system tracing and illumination (User Task: Perform flow-tracing during troubleshooting)

1.16.8.1 Viewer Application shall provide users the capability to select wires, fluid, pneumatic, signal or (HVAC) line in a graphic (diagram or schematic) and have continuity highlighted thru the circuit or schematic.

1.16.8.2 Tracing. Viewer Application uses the Extensible Markup Language

(XML) data to dynamically create graphical representation of the path based on user selection for start and/or end points.

1.16.8.3 Illumination. Viewer Application uses the XML data to dynamically highlight the path on the existing wire/fluid illustration (separate part wirings, parts grouping with multiple colors linking each part to the details part illustration).

1.16.9 Presentation and Search Functionality

1.16.9.1 Provide targeted presentation of only the matched information that is defined by the user in the search tool.

1.16.9.2 Provide user with focused search-term form display.

1.16.9.3 Equipment Results: Search display should include Reference Designator, Nomenclature, Location, Diagram, and Associated Wires. Results should be hyperlinked to applicable artifacts.

1.16.9.4 Wire Results: Search display should include Wire Number, Reference

Designator and Pin for both From and To Terminations, and Diagram.

Results should be hyperlinked to applicable artifacts.

1.16.10 Fault Isolation

1.16.10.1 Viewer Application shall provide fault isolation capabilities.

1.16.11 Table of Contents

1.16.11.1 Viewer Application shall have a Table of Contents (TOC) that expands to provide selection of the technical content using the System, Subsystem, Subject Number (SSSN) architecture from the highest level down to the lowest subject number. The TOC will be designed to maximize the amount of visible SSSN selections for easier navigation.

The TOC shall provide the option to display the Data Module (DM) title, DM Code, or both. Viewer Application shall also have an option allowing the user to hide or display the TOC as required.

1.16.11.2 The TOC should update dynamically as the user navigates through the

IETM.

1.16.12 Side by Side Viewing

1.16.12.1 Viewer Application must display text of the data module, and the figure associated with the text in side-by-side windows. The figures shall auto advance to maintain the appropriate figure for the text that is displayed.

In addition, the viewer application shall enable a tear off function for individual figures.

1.16.12.2 Viewer Application must display two or more manuals in side-by-side windows within the viewer. The side-by-side windows shall only display the text of the manual. Figures for the side-by-side manuals shall be available as hyperlinks that open a pop-up window.

1.16.13 Search Capability

1.16.13.1 Viewer Application shall provide users the capability to perform a global search for a single term or all terms in a string. The results shall be presented in separate lists for DM titles and DM content. The Viewer shall also have the capability to search within just the TOC or to search within a data module.

1.16.13.2 By default, Viewer Application shall enable dynamic search function.

1.16.13.3 Users shall be able to specify whether whole or partial matches should be returned and whether to search a single data module, a range of data modules, or an entire IETM.

1.16.13.4 All text in the technical content shall be searchable, including all text located in graphics and tables.

1.16.13.5 Search feature shall support full text, context (categorical), and Boolean searches. The categories for context searches shall include TOC Titles, Figure Titles, Table Titles, Part Numbers, Part Nomenclature (S1000D only), Cage Code, Fault Code, Data Module Codes (S1000D only), and

Data Module Titles (S1000D only).

1.16.14 Session Navigation

1.16.14.1 The IETM shall include "Next" and "Previous" navigation functions.

These functions shall act in an equivalent manner to the "Forward" and

"Back" arrows of web browsers. Previous returns the user to a step they visited previously.

1.16.15 Action complete and Missed Step Indicators

1.16.15.1 Viewer Application shall provide users the capability to indicate actions called for by the technical data have been completed. This is normally represented as a checkbox. (Smart Checklist)

1.16.15.2 Viewer Application shall provide indicators informing the user if a step has been missed during task performance.

1.16.16 Graphics

1.16.16.1 Viewer Application shall optimize 3D images to maximize functionality without degrading graphic manipulation and fidelity.

1.16.16.2 Viewer Application must enable navigation through a system using hotspots or links within a figure.

1.16.16.3 Viewer Application shall enable manipulation of a figure with zoom, rotate, exploded view of systems and sub-systems within capability (e.g., display an engine and be able to separate it out into its sub-systems and individual components).

1.16.16.4 At a minimum, the Viewer Application shall provide users the capability to pan and zoom graphics. Other manipulation capabilities such as rotating and magnifying glass view may be included.

1.16.16.5 Users will have the ability to turn off 3D image rendering to save bandwidth and/or hardware processing.

1.16.17 Suspend/Restart

1.16.17.1 Viewer Application shall provide users the capability to suspend their current session and to restart the session at a future time at the point where they left off.

1.16.18 Software Driven Diagnostics

1.16.18.1 Viewer Application include troubleshooting and dynamic diagnostic capabilities.

1.16.19 System Demonstration

1.16.19.1 Viewer Application shall have the capability to represent the maintenance system operation, behavior, or characteristics to demonstrate functionality. This can be used to model hydraulic, fuel, pneumatic and other mechanical systems.

1.16.19.2 The IETM shall have the capability to display animated graphic contained within the technical content for the user.

1.16.20 Emergency Procedure Quick Access

1.16.20.1 Viewer Application shall provide users quick (one click) access to associated emergency procedures. The IETM shall also provide users quick (one click) access to a listing of all emergency procedures.

1.16.21 Audio File Support

1.16.21.1 Viewer Application shall have the capability to play audio files contained within the technical content for the user.

1.16.22 Motion Video File Support

1.16.22.1 Viewer Application shall have the capability to play video files contained within the technical content for the user.

1.16.23 Link to External Training

1.16.23.1 The IETM shall include built-in links to external training sites for relevant maintainer/operator training courses/data.

1.16.24 Internal and External Links

1.16.24.1 All references, both internal to the document/data module and external to other documents/data modules, shall be hyperlinked and take the user to the referenced material when clicked.

2. Capability Requirements – Content Management System (CMS)

2.1 Storage and Accessibility

2.1.1 The CMS must be capable of storing XML, graphics, and other document types associated with an S1000D Common Source Database (CSDB).

2.1.2 The objects must be stored in a manner that makes the source data accessible and consumable by other Air Force systems.

2.2 Data Segregation

2.2.1 The CMS must provide a method for data segregation.

2.3 Graphical User Interface (GUI)

2.3.1 The CMS must include a Graphical User Interface (GUI) through which users can access and manage data in the CSDB.

2.3.2 The GUI must include toolsets that allow users to effectively manage all objects within the CSDB.

2.3.3 The GUI must be able to connect to multiple databases and/or repositories to facilitate data and user group segregation.

2.4 Authentication and Access Control

2.4.1 The CMS must support login capabilities.

2.4.1.1 The CMS must support login with a Common Access Card (CAC).

2.4.1.2 The CMS may support login with a username and password, or other personally identifiable means (e.g., biometric authentication), and may support two-factor authentication.

2.4.2 The CMS must support role-based access controls.

2.5 Compliance and Compatibility

2.5.1 The CMS must comply with current Department of Defense (DoD) Cybersecurity policies.

2.5.2 All components of the system should be compatible with AF-approved cloud platforms.

2.6 Object History and Retention

2.6.1 The CMS must retain the history of each object to comply with current AF retention policies.

2.7 Editing and Validation

2.7.1 The CMS must include a WYSIWYG (What You See Is What You Get) editor for

S1000D XML objects.

2.7.2 The CMS must interface with ETIMS (Enhanced Technical Information

Management System).

2.7.3 The CMS must have the ability to validate the objects stored therein against any applicable Business Rule Exchange (BREX).

2.7.4 The CMS must have the ability to validate reference tags utilized in the S1000D

XML.

3. Interoperability Requirements

Interoperability requirements are the specifications and protocols that enable different systems or components to communicate and work together effectively. These requirements are essential for ensuring that systems can exchange and use information seamlessly, regardless of the underlying technology or platform. The Viewer Application and CMS must allow for an interface with Air

Force approved Log IT systems to facilitate the following:

3.1 Systems Integration

3.1.1 Disconnected Operations

3.1.1.1 The system shall be able to able to continue functioning and providing services even when disconnected from the network.

3.1.1.2 The system shall have an offline mode that can be activated manually or automatically in case of network failure.

3.1.1.3 The system shall be able to synchronize data and settings with the network when it reconnects, without any data loss or inconsistencies.

3.1.2 Supply System Integration

3.1.2.1 In connected and disconnected operations, the IETM shall enable users to initiate parts ordering from within the viewer application via a supply system interface.

3.1.3 Maintenance Information System Integration

3.1.3.1 In connected and disconnected operations, the IETM shall have the capability to capture and transmit configuration change data (e.g., removed and installed part number information), tasks authorized, tasks performed, results of that work, etc. This information would be transmitted to the most current Air Force maintenance data collection and automated forms systems.

3.1.4 Engineering Data Integration

3.1.4.1 The IETM shall have the capability to communicate with the current AF

Product Lifecycle Management (PLM) solution for recommended change/publication change request (RC/PCR) and TO source data management.

3.1.5 Maintenance Digital Ecosystem Integration

3.1.5.1 Tech Order content and Tech Order source content shall be accessible to enable more mission planning applications in the Maintenance Digital

Ecosystem.

3.1.5.2 The Viewer application shall apply a Modular Open System Approach

(MOSA) architecture to ensure undefined requirements will be easily implemented.

3.1.5.3 The Viewer Application shall ensure all interfaces comply with current

DoD Cybersecurity policies.

3.1.5.4 The Viewer Application shall ensure interfaces and security strategies include DevSecOps and supply chain risk management as recommended by the Joint Federated Assurance Center and the Cyber Resilience Office for Weapon Systems (CROWS).

3.2 Key aspects of interoperability:

3.2.1 Data formats: Systems must use compatible data formats to exchange information effectively. This might involve using standard data formats, such as XML or JavaScript

Object Notation (JSON) or defining custom data formats that are specific to the application or domain.

3.2.2 Communication protocols: Systems must use compatible communication protocols to exchange information. This might involve using standard protocols, such as HTTP or

MQTT, or defining custom protocols that are specific to the application or domain.

3.2.3 Security and privacy: Interoperability requirements must address security and privacy concerns, such as authentication, authorization, and encryption, to ensure that sensitive information is protected during transmission and storage.

3.2.4 Compatibility: Interoperability requirements must ensure that systems are compatible with each other, considering factors such as software versions, hardware configurations, and network topologies.

3.2.5 Performance: Interoperability requirements must ensure effective data exchange under different conditions, such as high volumes of traffic, low bandwidth, or high latency.

4. Glossary

AFTO Form 158. Technical Order Review Comment Sheet.

AF Product Lifecycle Management (PLM). AF PLM provides a common, integrated system for managing all the data and information related to USAF weapon systems. This includes data on the design and configuration of the systems, as well as data on their maintenance, repair, and overhaul. PLM is a process for managing the entire lifecycle of a product, from its initial design and development through to its retirement and disposal.

Business Rule Exchange (BREX) S1000D. The S1000D Business Rules Exchange (BREX) is a specification for exchanging business rules and other related information between different systems and organizations. The BREX specification defines a common format for representing business rules, which can include rules for data validation, data exchange, and workflow management. By using a common format, organizations can more easily share and reuse business rules, reducing the need for manual data entry and improving the consistency and accuracy of technical publications.

Condition Based Maintenance. The application and integration of appropriate processes, technologies, and knowledge-based capabilities to improve the reliability and maintenance effectiveness of DoD systems and components. A maintenance strategy that involves using real-time data and predictive analytics to monitor the condition of equipment and predict when maintenance should be performed. The goal of CBM+ is to optimize maintenance schedules and reduce the need for unplanned maintenance, which can help to improve equipment availability and reduce maintenance costs.

Content Management System (CMS). A software application that helps companies create, edit, organize, and publish digital content. CMSs are used to store content in a database and display it in a presentation layer, such as a website. They can also help keep content organized and accessible so it can be used and repurposed effectively.

Common Source Database (CSDB). A database that is used to store and manage the source data for a publication or other type of document. The CSDB typically includes a data model that defines the structure and format of the data, as well as tools for importing, exporting, and validating the data. It may also include version control and change management features, which can help to track changes to the data and ensure that all contributors are working with the most recent version.

Cyber Resilience Office for Weapon Systems (CROWS). Established by the Department of

Defense (DoD) to improve cyber resilience of DoD weapon systems. CROWS works closely with DoD acquisition, test, and evaluation communities to ensure cyber security and resilience are considered throughout the acquisition process. CROWS also works with the operational community to help ensure weapon systems are operated and maintained in a secure and resilient manner.

DevSecOps. The software automated tools, services, and standards that enable programs to develop, secure, deploy, and operate applications in a secure, flexible, and interoperable fashion.

Disconnected Mode. Mode of operation when an eTool or Commercial Mobile Device (CMD) is operating without a network connection.

Enhanced Technical Information Management System (ETIMS). Designated AF Defense

Business System for all TO and Computer Program Identification Number (CPIN) management.

The overall ETIMS Enterprise Capability is provided by four (4) major components:

Government Cloud Service Provider Platform (Cloud One), ETIMS software, electronic

Technical Order (eTO) Content Management (ECM) software, and external interfaces. ETIMS provides capabilities to create and index catalog data, manage library accounts, manage paper printing and distribution, manage TO change process, manage, archive, and distribute eTO content to support viewing eTO on eTools. ETIMS contains metadata records that define the existence of TOs and CPINs in the Air Force Enterprise, and exchanges metadata and metadata transaction information/status with the Security Assistance Technical Order Data System

(SATODS), the Technical Order Authoring and Publishing (TOAP) System, Reliability &

Maintainability Information System (REMIS), Advancing Analytics (Advana)/Basing and

Logistics Analytics Data Environment (BLADE), and the Defense Logistics Agency’s Document

Services Online (DSO) for managing subscriptions and requisitions.

Interactive Electronic Technical Manual (IETM). Technical Manual authored in a non-linear fashion for the purpose of non-linear display. IETM organization facilitates easy user access to technical information while the display device provides interactive procedural guidance, navigational directions, and supplemental information. An IETM facilitates the interchange of maintenance manual information with logistic support data supplemental to maintenance, such as maintenance data collection, training documentation, supply interface and data presentation control.

Maintenance Digital Ecosystem. The creation of a hub and spoke, Application Programming

Interface (API) integrated architecture that creates transactional data exchanges between formerly disparate IT systems.

MIL-STD-3048. Department of Defense Standard Practice Air Force Business Rules for the

Implementation of S1000D. The military standard that establishes business rules for technical content, style, format, and functionality requirements USAF technical publications prepared using the S1000D specification. These rules provide the requirements for the implementation of

S1000D for the preparation, development, and delivery of all technical publications for paper, page-oriented, and screen-based Interactive Electronic Technical Manuals (IETMs), irrespective of architecture or display devices. Managed under Technical Manual Specifications and

Standards (TMSS).

Modular Open System Approach (MOSA). A systems engineering approach used to design, develop, and maintain complex systems. It is based on the use of open systems architecture, which is a modular and scalable approach to system design that allows for the integration of different components and subsystems from different vendors. MOSA can improve the maintainability of a system, as it allows for the replacement or upgrade of individual components and subsystems without affecting the rest of the system.

Technical Order Authoring and Publishing (TOAP). TOAP is the mandatory use, organic TO authoring and publishing component of the AF Standard TO Management System. TOAP utilizes

Contenta to provide AF enterprise capabilities to manage, author, and publish TO publication source content data, enforces authoring and publishing compliance, and provides a free to use

IETM (S1000D) viewer.

Viewer – Viewer Application. A viewer is a software program that allows technical data to be displayed, but not changed. Viewers are often freely distributable and platform independent, even when the editor application is not. This characteristic allows authors to create technical publications with an editor application and make the viewer, which displays the technical publication, available to other users.

Technical Management Specifications & Standards (TMSS). A set of guidelines and requirements for the preparation and production of technical manuals. It is used by organizations to ensure that their technical manuals are clear, concise, and consistent, and that they provide the necessary information to support the operation, maintenance, and repair of their products. TMSS covers a wide range of topics, including document structure, language and style, illustrations and graphics, formatting and layout, and content and organization.