The file's text, extracted by GovTribe without its formatting.
Functionality Matrix
| Functionality Requirements for Program: | DEGRADED VISUAL ENVIRONMENT SYSTEM (DVES) | 0 |
| Functionality Name/Definition | Required: Yes/No | Additional Comments |
| IETM Functionalities | | |
| Functionality Category - Access | | |
| Login/Logout | | |
| The IETM shall provide users the capability to login and logout. | Yes |
| Login/Logout via Common Access Card (CAC) |
| The IETM shall provide users the capability to login and logout with their CAC. | Yes |
| Login/Logout via username and password |
| The IETM shall provide users the capability to login and logout with a username and password. | No |
| IETM tailoring via user roles/profiles |
| The IETM shall be customizable based on user roles. Examples of customization include enabling/disabling menu options and allowing/disallowing access of certain data modules. | No |
| Suspend/Restart |
| The IETM 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. | No |
| Functionality Category - Annotations |
| Action complete indicators |
| The IETM shall provide users the capability to indicate that actions called for by the technical data have been completed. This is normally represented as a checkbox. | Yes |
| Global data annotations |
| The IETM shall have the capability to enter, store, and display globally applicable supplemental data. Globally means it applies at the Air Force level and can be seen by all users of the IETM, whether it's an Air Force Instruction, policy memo, urgent change, or supplemental data to the IETM. | Yes |
| Local data annotations |
| The IETM shall have the capability to enter, store, and display locally applicable supplemental data. Local can mean either wing level, base level, MAJCOM level or any similar level and can be seen by the applicable users of the IETM at the specified level, whether it's a local instruction or policy. | Yes |
| Personal annotations |
| The IETM shall provide users the capability to add supplemental information or notes to the data. Personal annotations can be added or deleted at the end user's discretion but is not retained at the end of the user session. | Yes |
| Redlining text |
| The IETM 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. | Yes |
| Redlining graphics |
| The IETM shall provide users the capability to redline/annotate graphics using markings for deletions, insertions, and changes. These markings are saved as feedback to correct/improve the publication during development and verification. | Yes |
| Functionality Category - Diagnostics and Prognostics |
| Software driven diagnostics |
| The IETM shall guide the user (via software) through troubleshooting by analyzing maintainer inputs, fault codes, and their correlations to display the appropriate starting point/action for fault isolation instead of the maintainer using a predefined fault tree. This will require a logic engine and one or more process data modules. | No |
| Dynamic diagnostics |
| The IETM shall interface with the product to utilize onboard monitoring devices (e.g. Built-In Test) and support/test equipment for fault detection/isolation. Troubleshooting is based on results returned from the product rather than inputs received from the maintainer. This may require external software and the product must also support this functionality. | No |
| Wire/Fluid system tracing |
| The IETM shall provide users the capability to select wires, fluid, pneumatic or (HVAC) line in a graphic (diagram or schematic) and have continuity highlighted thru the circuit or schematic. | No |
| System simulation |
| The IETM shall have the capability to represent the behavior or characteristics of the system function/malfunction to determine or reenact the problem. System simulation allows the user to introduce stimulus (such as pressure, valve positions, temperatures, voltages, sensor inputs, switch positions) and present the results in a manner that models the system behaviors. This can be used to model hydraulic, fuel, pneumatic and other systems. | No |
| Functionality Category - External Processes |
| Parts ordering integration |
| The IETM shall interface with the supply system to allow users to order parts from within the IETM. | No |
| Deficiency/improvement reporting |
| The IETM shall provide users the capability to report errors/improvements to the technical data by initiating the AFTO 22 process from within the IETM. | Yes |
| Maintenance data collection integration |
| The IETM shall have the capability to capture and transmit configuration change data (i.e. removed and installed part number information), tasks authorized, tasks performed, results of that work, etc. This information would be transmitted to Air Force maintenance data collection systems (such as REMIS). | No |
| Other external system integration |
| If there are any other external systems beyond the ones already listed (parts ordering, AFTO 22 change process, maintenance data collection) that should be integrated into the IETM, then these will be listed in the "Additional Comments" field. | No |
| Functionality Category - Graphics Functionality |
| Pan and zoom |
| At a minimum, the IETM shall provide users the capability to pan and zoom graphics. Other graphic manipulation capabilities, such as rotating or magnifying glass view, may be included. | Yes |
| 3D modeling |
| The product and it's components shall be modeled using 3D, solid object graphical figures and are displayed by the IETM. The use of 3D models can allow virtual assembly, disassembly, removal and installation of parts of the product using animation, simulation and/or virtual reality concepts. | No | 0 |
| Functionality Category - Linking | |
| Hot reference (tool tips) | |
| The IETM 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. | Yes |
| Functionality Category - Navigation and Tracking |
| Next and previous |
| 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. | Yes |
| History of traversed links |
| The IETM shall provide the capability to display to the user a history of all links traversed by the user. | Yes |
| User creation of bookmarks |
| The IETM shall provide the capability to allow the user to create their own bookmarks or navigational links to specific locations in the data. This would require login functionality as the bookmarks are tied to the specific user login. | Yes |
| System/subsystem navigation |
| The IETM shall provide users the capability to navigate through the technical content via the product's system/subsystem breakdown. User's would start at the highest level of the product (such as the aircraft itself), and would then navigate down through the system structure (such as airframe, cockpit) to find the appropriate data. | Yes |
| Restore initial navigation view |
| The IETM 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. | Yes |
| Audit trail |
| The IETM shall track and log all user interactions during a session. These interactions can then be retrieved to recreate the session in case an audit is needed. | Yes |
| Graphical navigation |
| The IETM shall provide users the capability to navigate the technical data via graphical representations of the product's system/subsystem breakdown. Heavy use of hotspotting is required on the graphics. For example, from a graphical overview of the aircraft, the user selects a wing. A graphical overview of the wing is presented. The user then selects the flaps. A graphical overview of the flaps is presented. The user selects the actuator. Information on the actuator is presented. | No |
| Dialog driven navigation |
| The IETM shall prompt the user for input and would then jump to the appropriate location based on the response. This requires the use of one or more process data modules. | No |
| Voice activated commands |
| The shall provide users the capability to navigate through the technical content via voice commands. | No |
| Filter content per applicability |
| The IETM shall filter the content displayed to the user based on applicability criteria given by the user. For example, the user specifies the tail number of the aircraft and only information relevant to that particular aircraft is shown. Filtering criteria are displayed in the "Additional Comments" field. At a minimum, both tail number and TCTO (pre and post) filtering options shall be provided. | Yes |
| Simultaneous display of multiple content objects |
| The IETM shall provide the users the capability to display technical content text and any tables or graphics simultaneously. This can be accomplished either through separate panes on the IETM interface, separate pop-up windows, or a combination of both. | Yes |
| Search |
| The IETM shall provide users the capability to search the technical content for specific characters, words, or phrases. 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 the entire IETM. | Yes |
| Functionality Category - Printing |
| 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). | Yes |
| 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). | Yes |
| Printing data module and linked data |
| The IETM shall provide users the capability to print the current data module 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). TO policy must be followed with regards to printing excerpts (such as printing distribution and security statements). | No |
| Functionality Category - Special Content |
| Warning and caution acknowledgement |
| The IETM shall require acknowledgement from the user for each warning and caution encountered in the technical data. The user must acknowledge the warning or caution via a button or dialog prompt before being allowed to proceed. | No |
| Emergency procedure quick access |
| The IETM 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. | Yes |
| Audio file support |
| The IETM shall have the capability to play audio files contained within the technical content for the user. | No |
| Motion video file support |
| The IETM shall have the capability to play video files contained within the technical content for the user. | No |
| Animated graphics support |
| The IETM shall have the capability to display animated graphic contained with in the technical content for the user. | No |
| Help documentation |
| The IETM shall have a "Help" option which provides users with documentation and guidance on how to use the IETM and all its options. | Yes |
| Link to external training |
| The IETM shall include built-in links to external training sites for relevant maintainer/operator training courses/data. | No |
| Functionality Category - Updates |
| Active change indications and markings |
| 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. | Yes |
| Functionality Category - User Operation Mode |
| Web browser viewable |
| The IETM technical content shall be viewable in a standard web browser that is part of the Air Force standard desktop. Web browser plug-ins or helper applications may be used to enable additional IETM functionalities that are not possible with the standard browser. | Yes |
| Disconnected mode |
| The IETM shall be able to operate entirely in a stand-alone or disconnected mode where the IETM is not connected to any network or Internet. | Yes |
| Connected mode |
| The IETM shall be able to access the network and/or the CSDB wirelessly during use. This functionality is necessary for integrating with external applications such as parts ordering or maintenance data collections. | Yes |
| IETM and PDF Functionalities |
| Functionality Category - Linking |
| Hot spotting |
| Graphics shall contain hot spots/embedded links to related information as needed. The most common example are parts illustrations where the callouts are linked to the appropriate parts listing. | Yes | 0 |
| Internal and external links | |
| 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. | Yes | Only within the IETM. No external linking required |
| Functionality Category - Navigation and Tracking | |
| Text, graphic, and table searchability | |
| All text in the technical content shall be searchable, including all text located in graphics and tables. | Yes |
| PDF Functionalities |
| Functionality Category -Annotations |
| PDF action complete indicators |
| The PDF shall provide users the capability to indicate that actions called for by the technical data have been completed. This is normally represented as a checkbox. | Yes | 0 |
| Other Functionalities | |
| Functionality Category - Delivery and Distribution | |
| Paper delivery/distribution | |
| Technical data shall be delivered/distributed via printed paper publications. | No | 0 |
| Physical media delivery/distribution | |
| Technical data shall be delivered/distributed via physical media such as DVD or hard drive. | Yes | 0 |
| Network delivery/distribution | |
| Technical data shall be delivered/distributed via network such as Internet, Intranet, or LAN and shall use approved transfer protocols (FTP, HTTPS). | Yes | 0 |
| Functionality Category - Publishing | |
| Complete page-based PDF technical manual publishing | |
The publishing system shall be able to publish fully formatted, linear, page-based technical manuals as a PDF from authored S1000D data modules. This would be a complete publication, not an excerpt or a single data module. No 0
