DRAFT Techincal Manual Contract Requirements (TMCR).docx

TM-86-01R 01 May 2020 1-02: S1000D/IETM

TM-86-01

Date: 2025-05-06

Air Force Technical Manual Contract Requirements (TMCR)

FOR

Common Armament Tester - Fighter (CAT-F)

SOLICITATION NUMBER FA8533-25-R-0002

CONTRACT TYPE: Firm Fixed Price / Cost Plus Fixed Fee (CPFF)

New Acquisition

TMCR TYPE: S1000D

CLINs Exhibit Data Item No Period of Performance

4014 E E008 OPTION IV

Section 1. Technical Order (TO) Program Requirements – S1000D/IETM

1. TMCR Tailoring. The Contractor may propose and submit, in writing, additional tailoring to the Technical Order Manager Agency/Agent (TOMA), Government Program Manager (PM) and Procuring Contracting Officer (PCO) as required by Section L of the RFP. The contractor may also submit additional Section 2 tailoring to propose new TO types (Table 1) and source data and TO updates (Table 2) required to support the Common Armament Tester - Fighter (CAT-F) program’s objectives. Modifications to contracts can continue to utilize the existing format until renegotiated/replaced. The acceptance of any contractor tailored TMCR will be at the discretion of the government and is not in effect until accepted in writing by the PCO or specified in the contract.

2. TO Program Scope. The Contractor must develop and deliver technical manuals in accordance with (IAW) this TMCR, the attached S1000D Decision Point Tool (section 3), and supplied Business Rules (BRs) that supports the Common Armament Tester - Fighter (CAT-F) requirements for technically usable manuals.

3. S1000D Technical Manual Content and Product Plan. The Contractor must develop and deliver a Technical Manual Content and Product Plan IAW the requirements specified within this TMCR. This plan must be developed in the Contractor’s format incorporating all applicable Business Rule requirements and the preliminary functionality requirements. For the purposes of this contractual document, the term IETM is considered synonymous with the S1000D term Interactive Electronic Technical Publication (IETP). The plan must also detail the total technical content coverage for each system, subsystem, equipment, and major components including a preliminary Data Management Requirement List (DMRL) listing all Data Modules (DMs) and Publication Modules (PMs) to be developed in support of the weapon system/equipment and a List of Applicable Publications if the DMs are to be a part of more than one Technical Publication or IETM. The DMRL must also reference the proposed DM schema type each module is written against. The plan must document the solution architecture requirements necessary for IETM development, to include solution diagrams, solution test cases, and applicable testing documentation.

3.1. Additional Content Information. Problems regarding requirements, interpretation, and application must be identified within the plan. Conflicts between standards and guidance documents must be highlighted. An explanation or initial demonstration of how the technical content information will be rendered on the display device and an overview of how the user will access the technical information must be provided. The Contractor may propose opportunities for data (text, graphics, other media) re-use across data types (including training data), weapons system/equipment configurations and foreign military sales. The plan must include a list of re-use objects with future potential to be used across DoD, as well as those items that are unique to the system addressed in the listed IETM(s). The Contractor must also detail their approach to managing the relationship between content and weapon system/equipment applicability. Prior to award, guidance will be outlined in Section L of the RFP, as referenced for development of the IETM(s) guidance. Upon award, opportunities or recommended new language should not be incorporated unless unique and original. The acceptance of any contractor tailored content will be at the discretion of the government and is not in effect until accepted in writing by the PCO or specified in the contract.

3.2. Product Coverage. The plan must include Contractor recommendations for the packaging of the IETM content, (i.e., single IETM or multiple IETM products), based on the defined maintenance concept. The Contractor must include external and internal links and references within the plan. Additionally, the plan must include the use of Commercial-Off-The-Shelf (COTS) and/or other TMs listed within Section 2, Table 2 of this TMCR, and other manuals as applicable.

3.3. Alternative Recommendations. The Contractor may propose, within the plan and as outlined in Section L of the RFP, alternative recommendations for certain technical manual types that may not readily conform to the provided functionality requirements and proposed program BRs. Additionally, the Contractor may propose alterations and alternative IETM constructs for paper-based requirements to better optimize page output and minimize print cost. Alterations will be in compliance with AF TMSS requirements.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. AF TMSS tailoring options and some Joint Service TMSS have been documented in preliminary Specification/Standard Interface Records (SIRS) included in Section 3. These preliminary SIRs provide the starting point for further tailoring. Contractors may recommend additional tailoring of the Joint Service TMSS SIRs and provide recommended SIRs for other TMSS as applicable. Tailoring must not change or delete mandatory requirements which are part of the XML schema structure or Document Type Definition (DTD) located in Section 2, Table 1.

NOTE: TMSS requirements marked “(F)” are specifically for Air Force use; “(A)” is for Army, “(M)” is Marine Corps and “(N)” is Navy. Comply with all unmarked and “(F)” TMSS requirements as modified by the tailoring options in each TMSS.

4.1. Questions concerning TMSS requirements may be submitted in writing with suggestions for resolution and supporting information to the PCO and DAVID SEEGER, AFLCMC/ROA, 320 RICHARD RAY BLVD Robins AFB GA 31098, 478-222-1963. Deficiencies and suggested improvements may be submitted to the TMSS Preparing Activity (PA). Recommendations, corrections and clarifications approved by the PCO, if any, will be maintained with contract documentation.

5. Subsequent TO/Data Requirements. When new TO requirements are identified the Contractor must notify the Government utilizing DI-TMSS-80067C, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, or approved Contractor formats. This process must require Government review and approval of recommended additional requirements prior to developing additional data. When approved, the Contractor must incorporate the requirements within the Technical Manual Content and Product Plan where applicable.

6. TO Development. TOs must be written to a scope and depth of coverage to support the Common Armament Tester - Fighter (CAT-F) operations and maintenance concepts.

6.1. TO data must be developed IAW ASD/AIA S1000D, International Specification for Technical Publications Utilizing a Common Source Database, and MIL-STD-3048, Air Force Business Rules for the Implementation of S1000D. For S1000D, this includes program tailored functionality requirements and Project Business Rules when implemented. The Government tailored functionality requirements and Business Rule Decision Points for MIL-STD-3048 are included in the SIR found in Section 3 of this document. All delivered graphics must conform to the approved graphic creation and format guidelines listed in Attachment 1, Graphics Format Guidelines. If needed, the Contractor must contact the PCO and TOMA to request guidance from the Air Force PA, AFLCMC/GBS, Technical Data Section, 4170 Hebble Creek Rd, Bldg. 280, Door 15, WPAFB OH 45433-5653.

7. TO Numbering. Contractors must notify the Government, in writing, of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by the Contractor’s own personnel. Requests for new TO numbers must be submitted to the TOMA utilizing the TO numbering worksheet. (Attachment 2, Request for Technical Order Number)

8. Data Rights. Contractors must comply with 10 U.S.C. 2320 and Defense Federal Acquisition Regulation Supplement (DFARS) provisions and clauses. The Government’s rights in technical data are specified in DFARS 252.227-7013, Rights in Technical Data-Noncommercial Items, 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, and 252.227-7015, Technical Data-Commercial Items and other applicable provisions and clauses from DFARS 227, 252.227, and DFARS 252.227-7018 Rights in Noncommercial Technical Data and Computer Software – Small Business Innovation Research (SBIR). In accordance with those clauses and provisions, the Contractor grants the Government Unlimited Rights, as defined therein, in all source data, TO publications, TO updates, and TO-related documents prepared specifically for the contract. The Contractor also grants the Government Unlimited Rights in all Government-funded business rules (tailoring and application methods and procedures) and documented business processes developed under the contract for the purpose of or for use in TO development. The contractor is required to deliver TO data with the data rights license required by the applicable DFARS clauses. Contractor must identify any data to be delivered to the Government with other than Unlimited Rights IAW DFARS 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions and must mark such data only in accordance with the applicable DFARS clause. The Contractor must pass through and enforce all requirements in this TMCR to all sub-Contractors.

8.1. The Government shall have unlimited rights in technical data that are data pertaining to an item, component, or process which has been or will be developed exclusively with Government funds; studies, analyses, test data, or similar data produced for this contract, when the study, analysis, test, or similar work was specified as an element of performance; created exclusively with Government funds in the performance of a contract that does not require the development, manufacture, construction, or production of items, components, or processes; form, fit, and function data; necessary for installation, operation, maintenance, or training purposes (other than detailed manufacturing or process data); corrections or changes to technical data furnished to the Contractor by the Government; otherwise publicly available or have been released or disclosed by the Contractor or subcontractor without restrictions on further use, release or disclosure, other than a release or disclosure resulting from the sale, transfer, or other assignment of interest in the technical data to another party or the sale or transfer of some or all of a business entity or its assets to another party; data in which the Government has obtained unlimited rights under another Government contract or as a result of negotiations; or data furnished to the Government, under this or any other Government contract or subcontract thereunder, with Government purpose license rights or limited rights and the restrictive condition(s) has/have expired; or Government purpose rights and the Contractor's exclusive right to use such data for commercial purposes has expired.

9. Classification, Distribution, Destruction, Disclosure, Export Control Notices, and Cyber Security. Contractors must recommend the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide and Department of Defense Manual (DODM) 5200.01V2 AFMAN 16-1404V2, Department of Defense Instruction (DODI) 5230.24, Department of Defense Directive (DODD) 5230.25, DoDI 5200.48, Controlled Unclassified Information, DAFI 61-201, Management of Scientific and Technical Information (STINFO), and MIL-STD-38784 (available at https://www.esd.whs.mil/dd/dod-issuances/, http://www.e-publishing.af.mil/ or https://quicksearch.dla.mil/qsSearch.aspx). The markings and notices must be reviewed during In-Process Reviews (IPR). The Contractor must also apply policy and procedures for Cybersecurity Program Management IAW AFI 17-130, AFMAN 17-1301, Computer Security (COMPUSEC) NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO content.

10. TO Quality. The Contractor must ensure prepared TOs are: a) technically accurate and safe; b) written to a scope and depth of coverage to support the operations and maintenance concepts; c) properly classified and marked with export control and distribution limitation statements. The Contractor must maintain a Technical Manual Quality Assurance (TMQA) Program Plan for this effort. The TMQA Program Plan must be available for review at the TO Guidance Conference. The TMQA Program Plan must be sufficiently detailed to support TO certification to include actual performance of procedures or desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be reserved for those procedures which would activate explosive devices or present a hazard to personnel or equipment.

10.1. Initial Technical Order Guidance Conference (TOGC). Working through the TOMA, the Contractor must co-host and participate in a guidance conference for this effort. The TOGC will be held within 60 calendar days after contract award. The Technical Manual Schedule and Status will be formalized at this conference. The Contractor must present a briefing on their interpretation of the basic contract, SOW/Performance Work Statement, CDRLs, Data Item Descriptions (DIDs), MIL-SPEC, MIL-DTL, MIL-STD, SIRs, this document and the planned preparation and delivery of the TOs and related data. The Contractor must also provide their S1000D Technical Manual Content and Product Plan for review and approval.

10.2. In-Process Reviews. The Contractor must participate and co-chair In-Process Reviews (IPR) of the data developed for this effort IAW the TOMA-provided IPR checklists. In-Process Reviews are to ensure that data being developed as part of this effort is adequate and accurate and IAW contract requirements and cited specifications. The Contractor must ensure that all appropriate personnel required to execute a successful TO program will either attend or participate in the IPR. IPRs will be held IAW with TO 00-5-3 or as defined by the program office. During the IPRs the Contractor will be responsible to maintain a master markup or documented list of approved changes for the content being reviewed. The Contractor must develop meeting minutes after each review documenting all approved changes and concurrent agreements for Government review and approval. This master markup or documented list of approved changes will be made available at the next scheduled review. A copy of the markup will be provided to the TOMA or designated individual at the conclusion of the review. The Contractor must ensure all comments from previous IPRs have been incorporated prior to the next scheduled IPR. With prior approval of the TOMA, IPRs may be combined.

10.3. TO Delivery Requirements for In-Process Reviews. IPR TO data must be technically edited and reviewed according to the TMQA Program Plan. Manuscript (handwritten) data is not acceptable for any data to be reviewed. The TMQA Program Plan checklists must be available for review by the Government during the IPRs. IPRs subsequent to the initial review may be accomplished using the approved IETM viewing presentation system and as specified within the Government provided IPR checklist. Delivery requirements are contained in Section 2 of the TMCR.

10.4. TO Certification. The Contractor must certify that new TO procedures and data developed to support the program are safe, accurate, adequate, current, and usable for their intended purpose. The Government may witness the certification activities. The Contractor must incorporate comments generated by the certification process into the TOs prior to submitting the TOs for verification. At the completion of the certification, the Contractor must submit a letter to the TOMA through the Government PCO and PM stating that certification has been completed, the certification method used, and that any deficiencies identified during the process have been corrected. The Contractor will ensure all necessary changes and corrections to affected manuals are accomplished in time to meet contract delivery schedule requirements. The Contractor must notify the Government, as identified in the contract, at least 180 days prior to the need date, of any Government Furnished Property (GFP), Government Furnished Information (GFI), and/or Government Furnished Equipment (GFE) as required, to perform certification tasks. Technical Order 00-5-1 and 00-5-3 must be referenced for additional information on TO certification requirements.

10.4.1. The Contractor must propose opportunities to perform TO certification activities in conjunction with Government verification IAW TO 00-5-3, where applicable.

10.5. Verification Support. The Contractor must support Government verification activities as required by the TOMA and the program Technical Order Life Cycle Verification Plan (TOLCVP). Contractor verification support will consist of on station technical writing and engineering support. The Contractor must maintain a master mark-up of the TM or list of approved changes and record meeting-minute items during the Government verification process. The Contractor must also support all post verification reviews and ensure availability until 100% task verification is attained by the Government.

10.5.1. Verification of IETMs requires unique processes and procedures to verify the content. Verification results can be incorporated using traditional pre-publication review methods or updated in real-time during the verification. The Contractor must provide technical support and common source database maintenance personnel required for changes resulting from verification.

10.6. TO Prepublication Reviews (PPR). PPRs are examinations of TOs that ensure incorporation of agreed upon changes from previous reviews and verification activities. The Contractor must prepare and deliver copies of TOs and TO updates in contract compliance for the PPR as shown in the delivery matrix. The TOs for PPR must be approved by the Contractor’s QA, be in compliance with the contract specification/DTLs/STDs, and incorporate all verification comments and corrections approved by the TOMA or program management office representative.

10.7. Technical Data Assessment (TDA). The Contractor must submit in-work samples of each specified TM type deliverable to the Government for specification and standardization compliance review. TDAs may be accomplished by using organic TO sustainment environments with the assistance of AFLCMC/GBS (AF TMSS Office, SGMLSUPPORT@us.af.mil).

10.7.1. S1000D (XML) Data Files. The Contractor must submit S1000D XML tagged DMs, all layered BREX and all referenced graphics for assessment. During assessment, these DMs will be evaluated against the TMSS S1000D Validation Tool to parse/validate each DM to confirm all submitted DMs are S1000D compliant.

10.7.2. Error Resolution. The Contractor must correct any errors found during the TDA prior to each IPR. Additional TDAs may be necessary based on the amount of errors found during the initial TDA. Completion of a TDA in no way relieves the Contractor from the requirement to fix errors found during future reviews.

11. TO Delivery. TO file delivery requirements are located in Section 2, Table 3 and Table 4 of this document.

11.1. S1000D Source Files. The Contractor must parse and deliver everything necessary to properly generate and view the data in the approved IETM viewer or produce the desired presentation to the user. This includes all DMs, database files, BREX, XSL, cascading style sheets (CSS), conversion scripts (such as Java or Perl), graphics, XML, viewer software, referenced HTML/PDF files, native source data files, process and training documentation, etc.

NOTE: For this program the approved IETM viewer in section 11.1 will be the Air Force Live Content Viewer.

12. Source Data Maintenance. Contractors must maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. The Contractor must provide the Government a Configuration Control Management Plan. The Contractor will provide a minimum of annual updates frequently throughout the life of the contract as directed in writing from the PCO. Maintenance includes preparation of source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes. Additionally, the Contractor must ensure the accuracy, currency, and configuration of applicable data provided by their sub-Contractors as it effects the technical baseline.

NOTE: Contractors will protect GFI provided for the purposes of TO development IAW DFARS 252.204-7000 Disclosure of Information and DFARS 252.227-7025, Limitations on the Use or Disclosure of Government Furnished Information Marked with Restrictive Legends.

13. TO Maintenance. Contractors must maintain TOs by preparing emergency, urgent, routine changes/revisions or supplements and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes IAW TO 00-5-3. The Contractor must assist the Government, where applicable, by incorporating and delivering approved changes to the technical data in the field NLT the specified time limits within TO 00-5-3 for Urgent, Work Stoppage, or Emergency changes originating from an approved Recommended Change (RC) process and/or Publication Change Request (PCR) in the Enhanced Technical Information Management System (ETIMS). In the event of non-ETIMS access, AFTO FORM 22, 252 policy or other approved change request forms processes will be adhered to (IAW TO 00-5-1). The specified time limits upon receipt of specified change requests is 40 calendar days for urgent changes/revisions, 72 hours for work stoppage changes/revisions, and 48 hours for emergency changes/revisions.

14. Schedules. The Contractor must develop and maintain an Integrated Technical Manual Schedule and Status throughout the period of performance for all TO development activities associated with this order for the life of the contract. The schedule must be to the system/book or TCTO level and cover all major milestones of development. Any changes to the Integrated Technical Manual Schedule and Status after the TO Guidance Conference must be coordinated with and approved by program TOMA and PCO.

15. Time Compliance Technical Orders (TCTOs). The Contractor must prepare TCTOs, ITCTOs and resulting TO updates as required in support of Common Armament Tester - Fighter (CAT-F) IAW TO 00-5-15 and MIL-DTL-38804 content requirements. TCTOs will be used to document all permanent modifications, initiate special “one time” inspections, or impose temporary restrictions on systems or equipment within specified time limits effecting Common Armament Tester - Fighter (CAT-F). Costs for TCTO package development must be IAW with DAFI 65-601Vol.1.

15.1. The Contractor must deliver Immediate Action TCTO drafts with comments incorporated within 24 hours of receipt of comments.

15.2. The Contractor must deliver Urgent Action TCTO final drafts with “final” customer comments incorporated, within 48 hours of receipt of comments.

15.3. The Contractor must deliver routine safety TCTO final drafts with “final” customer comments incorporated, within 5 working days of receipt of comments.

15.4. The Contractor must deliver routine TCTO final drafts with “final” customer comments incorporated, within 5 working days of receipt of comments.

16. Information Technology (IT) Requirements. The Contractor must develop IETM requirements utilizing the designated Air Force TO System infrastructure. The Contractor, thru the TOMA and program management office, must acquire the appropriate licenses and network access permissions for operation on the AF approved Technical Order Authoring and Publishing (TOAP) solution. (IAW TO 00-5-3, para. 3.25)

16.1. The contractor must obtain and maintain an active Air Force Portal account.

16.2. All requests for existing technical manuals required for the contract will only be obtained from the TOMA via an ETIMS library setup for the Contractor.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

TECHNICAL MANUAL TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE Common Armament Tester - Fighter (CAT-F) Program

a. TCTO

b. TCTO Supplement

a. Maintenance Manuals

1) Organizational Maintenance

2) Intermediate Maintenance

3) Depot Maintenance

b. Operation & Maintenance Instruction Manuals

c. Special Manuals

1) ATE Operator Test Procedures

d. With Illustrated Parts Breakdown

TABLE 2

SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS

NOTES:

· Check all applicable boxes.

· For existing manuals not being updated to latest specification requirements, enter “Same style and format” under the specification heading.

TO Number, Title, or Type of Manual

Specification

Change

Revision

Supplement Supplemental TM

Source Data

1. 1A-10C-2-15JG-2-1-WA-1:

JOB GUIDE - ORGANIZATIONAL MAINTENANCE - WINDOWS 7 SOFTWARE LOADING PROCEDURES UTILIZING PORTABLE AUTOMATED TEST STATION (PATS) ON A-10C AIRCRAFT, USAF SERIES A-10C AIRCRAFT (VOLUME 1)

2. 1A-10C-2-15JG-2-2-WA-1:

JOB GUIDE - ORGANIZATIONAL MAINTENANCE - WINDOWS 7 SOFTWARE LOADING PROCEDURES UTILIZING PORTABLE AUTOMATED TEST STATION (PATS) ON A-10C AIRCRAFT, USAF SERIES A-10C AIRCRAFT (VOLUME 2)

3. 1A-10C-8-1-WA-1:

SOFTWARE CONFIGURATION MANUAL - USAF SERIES A-10C AIRCRAFT

4. 1A-10C-4-2-WA-1:

ILLUSTRATED PARTS BREAKDOWN - ANCILLARY EQUIPMENT, USAF SERIES A-10C-AIRCRAFT

5. 1A-10C-2-40TS-7-WA-1:

TROUBLESHOOTING AVIONICS INTEGRATED SYSTEMS - ORGANIZATIONAL MAINTENANCE - LASTE SYSTEM, USAF SERIES A-10C AIRCRAFT

6. 1A-10C-2-94JG-10-WA-1:

JOB GUIDE - ORGANIZATIONAL MAINTENANCE - FIRE CONTROL HEAD UP DISPLAY LASTE SYSTEM, USAF SERIES A-10C AIRCRAFT

7. 1A-10C-2-94JG-11-WA-1:

JOB GUIDE - ORGANIZATIONAL MAINTENANCE - FIRE CONTROL, AN/AAQ-28 TARGETING POD SYSTEM, USAF SERIES A-10C AIRCRAFT

8. 1A-10C-2-94JG-3:

JOB GUIDE - ORGANIZATIONAL MAINTENANCE - DISPLAYS, USAF SERIES A-10C AIRCRAFT

9. 1A-10C-2-94TS-1:

ORGANIZATIONAL MAINTENANCE - TROUBLESHOOTING - DISPLAYS AND IMAGE RECORDING, USAF SERIES A-10C AIRCRAFT

10. 11L1-2-29-2-WA-1:

MAINTENANCE INSTRUCTIONS WITH ILLUSTRATED PARTS BREAKDOWN - INTERMEDIATE DEPOT - LAU-105/A GUIDED MISSILE LAUNCHER, PN 8523895-10

11. 33D9-54-7-42-WA-1:

TEST PROCEDURES (CHECKOUT/TROUBLESHOOTING) WITH ILLUSTRATED PARTS BREAKDOWN - TESTER, DETENT PN D7448-14

12. 1F-15A-2-94FI-00-6-WA-1:

FAULT ISOLATION - WEAPONS SYSTEM SSSN 94-31-00 (AE24T-198())

14. 1F-15A-2-94JG-31-6-WA-1:

JOB GUIDE - WEAPONS SYS, WEAPONS, SUSPENSION, MISSILES. SSSN 94-31-65 THRU END (AE24T-198A) (F15A-D)

15. 1F-15A-2-94JG-32-6-WA-1:

JOB GUIDE - WEAPONS SYS, WEAPONS, SUSPENSION, BOMBS, SSSN 94-32-65 THRU END (F15A-D)

16. 1F-15A-2-94JG-50-3-WA-1:

JOB GUIDE - WEAPONS SYSTEM - GUN SSSN 94-50-20 THRU END (MCDONNELL)

17. 1F-15E-2-94FI-00-4-WA-1:

FAULT ISOLATION WEAPONS SYSTEM SSSN 94-10-00 THRU 94-31-00 USAF SERIES F-15E AIRCRAFT

18. 1F-15E-2-94FI-00-5-WA-1:

FAULT ISOLATION WEAPONS SYSTEM SSSN 94-32-00 USAF SERIES F-15E AIRCRAFT

19. 1F-15E-2-94FI-00-6-WA-1:

WEAPONS SYSTEM SSSN 94-50-00 THRU END USAF SERIES F-15E AIRCRAFT

24. 1F-15E-2-94JG-32-10:

WEAPONS SYSTEM - GUN (F-15E) S/S/SN 94-50-20 THROUGH END (T-198)

33. 1F-15EX-33-1-2-WA-1:

NONNUCLEAR MUNITIONS LOADING PROCEDURES (F-15E) (T-199)

34. 1F-15EX-33-1-2CL-1-WA-1:

USAF SERIES

F-15EX

AIRCRAFT

FUNCTIONAL CHECKS

35. 1F-15EX-2-94JG-31-1:

WEAPONS SYSTEM - WEAPONS

SUSPENSION - MISSILES

S/S/SN 94-31-01 THRU 94-31-11

36. 1F-15EX-2-94JG-32-1-WA-1:

SUSPENSION - BOMBS

S/S/SN 94-32-01 THRU 94-32-09

37. 1F-15EX-2-94JG-32-2-WA-1:

SUSPENSION - BOMBS

S/S/SN 94-32-16 THRU 94-32-27

38. 1F-15EX-2-94JG-32-3-WA-1:

SUSPENSION - BOMBS

S/S/SN 94-32-28 THRU 94-32-31

39. 1F-15EX-2-94JG-50-1-WA-1:

WEAPONS SYSTEM - GUN

S/S/SN 94-50-01 THRU 94-50-08

40. 1F-15EX-2-94FI-00-1-WA-1:

FAULT ISOLATION

WEAPONS SYSTEM

S/S/SN 94-10-00 THRU 94-31-00

41. 1F-15EX-2-94FI-00-2-WA-1:

FAULT ISOLATION

WEAPONS SYSTEM

S/S/SN 94-32-00 THRU 94-99-00

TABLE 3

IETM FUNCTIONALITY REQUIREMENTS

Specification/Standard Interface Record for MIL-STD-3048C (15 May 2023) Air Force Business Rules for the Implementation of S1000D

PART I: B-1 Mandatory Functionality Requirements

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.

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.

Technical data shall be delivered/distributed via network such as Internet, Intranet, or LAN and shall use approved transfer protocols (FTP, HTTPS).

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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).

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).

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).

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.

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.

The IETM shall have a "Help" option which provides users with documentation and guidance on how to use the IETM and all its options.

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.

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.

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.

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.

PART II: B-2 Optional Functionality Requirements

The IETM shall provide users the capability to login and logout with their CAC.

The IETM shall provide users the capability to login and logout.

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.

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.

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.

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.

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.

Technical data shall be delivered/distributed via physical media such as DVD or hard drive.

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.

Diagnostics and Prognostics 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.

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.

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.

External Processes Parts ordering integration The IETM shall interface with the supply system to allow users to order parts from within the IETM.

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.

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.

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.

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

The IETM shall have the capability to play audio files contained within the technical content for the user.

The IETM shall have the capability to play video files contained within the technical content for the user.

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.

PART III: S1000D Decision Point Tool The S1000D Decision Point Tool will be used to provide outputs of both the Project’s Functionality Requirements, the Project’s Business Rules, and tailored SIRs. Utilize the TMCR S1000D Decision Point Tool located at https://techdata.wpafb.af.mil/tmss/index.html for the MIL-STD-3048 SIR, Air Force Business Rules for the Implementation of S1000D, by selecting all applicable project functionality requirements, project business rules, and the desired tailoring options expressed in paragraphs 4. Attach the completed S1000D Decision Point Tool spreadsheet.

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.

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.

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.

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.

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.

Yes

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.

Yes

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.

Yes

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.

Deficiency/improvement reporting

The IETM shall provide users the capability to report errors/improvements to the technical data, by initiating the Recommended Change (RC)/Publication Change Request (PCR) from within the IETM.

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, RC/PCR 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.

Yes

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