Atch-3_ExhibitA_CDRL.pdf

TM-86-01Q

21 November 2019_jsr

Air Force Technical Manual Contract Requirements (TMCR) for

Contractor Logistics Support (CY21)

CONTRACT: _______________________

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS

1. TMCR Tailoring. This TMCR has been tailored by the program office, including the associated tables, matrices and Specification/Standard Interface Records (SIRs). 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) for consideration. The tailored TMCR shall be attached to the Contract Data Requirements List (CDRL) for Technical Order

(TO) delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal

Statement of Work (SOW). Air Force (AF) TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management, located at http://www.tinker.af.mil/Home/TechnicalOrders.aspx. A copy may also be obtained from the Program

TO Manager. Any terms or procedures found in this document may be researched there.

2. TO Program Scope. The Contractor shall develop and deliver technical manual updates in accordance with (IAW) this TMCR, the The current S1000D Interactive Electronic Technical Manual(s)

(IETM) functionality requirements, and approved Business Rules (BRs) that support the Contractor

Logistics Support (CY20) requirements for technically usable manuals. The Contractor shall use current fielded content to build from when developing data updates of similar content. The Contractor may recommend additional Section 2 tailoring to propose new TO types (Table 1) and source data and TO updates (Table 2) required to support the Contractor Logistics Support (CY20) program’s objectives.

3. S1000D Technical Manual Content and Product Plan. The Contractor shall develop and deliver a

Technical Manual Content and Product Plan IAW the requirements specified within this TMCR. This plan shall be developed in the Contractor’s format and will specify the development/update of the IETM incorporating all applicable Business Rule requirements and 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 shall also detail the total technical content coverage for each system, subsystem, equipment, and major components including a preliminary Data

Module 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 shall also reference the proposed DM schema type each module is written against. The plan shall 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 shall be identified within the plan. Conflicts between standards and guidance documents shall 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 shall be provided. The Contractor shall 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 shall 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 http://www.tinker.af.mil/Home/TechnicalOrders.aspx this IETM. The Contractor shall also detail their approach to managing the relationship between content and weapon system/equipment applicability.

3.2. Product Coverage. The plan shall 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 shall include external and internal links and references within the plan.

Additionally, the plan shall 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 shall propose, within the plan, alternative recommendations for certain technical manual types that may not readily conform to the provided functionality requirements and proposed program BRs. Additionally, the Contractor shall 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. Commercial Manuals. Contractors shall recommend the use of existing commercial manuals to the maximum extent possible without impairing program support objectives. All proposed commercial manuals are subject to Government review and approval. Contractors shall use Data Item Description

(DID) DI-TMSS-80067C, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or

Contractor Furnished Equipment (CFAE/CFE) Notices, to provide recommendation data. A copy is available through ASSIST at http://quicksearch.dla.mil/qsSearch.aspx.

4.1. The AF requests the ability to electronically store, print, distribute, update and decollate the commercial manual to allow for printing.

4.2. Approved COTS Manuals shall be delivered with an Identifying TO Publication Sheet (ITPS), IAW Military Performance Specification (MIL-PRF)-32216. All PDF files of commercial data shall be non-password protected to allow the AF to decollate the manual for printing.

4.3. If the proposed COTS data is found to be insufficient after review by the Government, the

Contractor shall prepare supplemental data for the COTS manual as required IAW Military Standard

(MIL-STD)-38784. If the COTS data cannot be supplemented sufficiently the Contractor may be tasked to develop new TM data IAW the applicable TMSS listed in Section 2 Table 1.

4.4. If the Government accepts the proposed COTS manual, the Contractor shall propose if and how the manual will be incorporated and distributed as part of the IETM within the Technical Manual

Content and Product Plan.

5. 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 Document Type Definition (DTD) or XML schema structure located in Section 2, Table 1.

5.1. Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the PCO and Matthew Harwedel, AFLCMC/WII, Bldg

560 Wright-Patterson AFB OH 45433 Phone 937-255-3243. Deficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

http://quicksearch.dla.mil/qsSearch.aspx

6. Subsequent TO/Data Requirements. When new TO requirements are identified the Contractor shall 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 shall require Government review and approval of recommended additional requirements prior to developing additional data. When approved, the Contractor shall incorporate the requirements within the Technical Manual Content and Product Plan where applicable.

7. TO Update Development. TOs/Contractor Source Data shall be written to a scope and depth of coverage to support the Contractor Logistics Support (CY20) requirements.

7.1. TO/Contractor Source data shall 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 Business Rule Decision Points for MIL-STD-3048 are included in the SIR found in Section

3 of this document. All delivered graphics shall conform to the approved graphic creation and format guidelines listed in Attachment 1, Graphics Format Guidelines. If needed, the Contractor shall contact the PCO and TOMA to request guidance from the Air Force PA, AFLCMC/HIAM, Technical Data Section, 4170 Hebble Creek Rd, Bldg. 280, Door 15, WPAFB OH 45433-5653.

7.2. Standard Generalized Markup Language (SGML) tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible. All delivered graphics shall conform to the approved graphic creation and format guidelines listed in Attachment 1, Graphics Format Guidelines. For assistance with illustration requirements contact AF TMSS via (e-mail: SGMLSupport@us.af.mil).

7.3. Page-oriented Military Specification (MIL-SPEC) TO/Contractor Source Data shall be formatted with text, graphics and delivered according to the TMSS specified in Section 2. The

Contractor shall develop TO files (tagged instances) using SGML according to the DTDs referenced in the appendix to MIL-STD-38784 and each applicable military detail specification (MIL-DTL).

Multiple SGML file instances for a single TO document are not authorized

8. TO Numbering. (Reserve)

9. Data Rights. Contractors shall comply with 10 U.S.C. 2320 and cognizant Defense Federal

Acquisition Regulation Supplement (DFARS) provisions and clauses in providing Unlimited Rights for all source data, TO publications, and TO updates prepared specifically for the contract. Government rights in data are specified in the 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. The Government shall be given Unlimited Rights for all Government-funded business rules (tailoring and application methods and procedures), documented business processes developed for use in TO development, the common source database, transformation style sheets, and other tools or products used to author or display technical data developed under the contract. For all data delivered to the Government with other than

Unlimited Rights, the Contractor shall assert their data rights IAW DFARS 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions. The Contractor shall pass through and enforce all requirements in this TMCR to all sub-Contractors.

10. Classification, Distribution, Destruction, Disclosure, Export Control Notices, and Cyber Security.

Contractors shall recommend the correct markings and controls for classified and restricted distribution mailto:SGMLSupport@us.af.mil data and TOs IAW the program’s Security Classification Guide and Department of Defense Manual

(DODM) 5200.01, Department of Defense Instruction (DODI) 5230.24, Department of Defense

Directive (DODD) 5230.25, Air Force Instruction (AFI) 16-1404, and MIL-STD-38784 (available at http://www.e-publishing.af.mil/ or https://assist.dla.mil/online/start/index.cfm). The markings and notices shall be reviewed during In-Process Reviews (IPR). The Contractor shall also apply policy and procedures for Cyber Security Protection IAW AFI 33-200, Information Assurance (IA) Management, AFMAN 17-1301, Computer Security (COMPUSEC), and MPTO 00-33B-5008, Remanence Security for Information Systems. NOTE: Distribution limitations will be determined on a case-by-case basis as

TOs are developed, dependent upon TO content.

11. TO Quality. The Contractor shall 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 shall maintain a Technical Manual Quality Assurance (TMQA) Program Plan for this effort.

The TMQA Program Plan shall be available for review at the TO Guidance Conference. The TMQA

Program Plan shall 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.

11.1. Initial Technical Order Guidance Conference (TOGC). (Reserved)

11.2. In-Process Reviews. (Reserved)

11.3. TO Delivery Requirements for In-Process Reviews. (Reserved)

11.4. TO Certification. The Contractor shall 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 shall 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 shall submit a letter to the TOMA through the

Government PCO and PM stating that certification has been completed, the certification method used, Equipment model and serial number, 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 shall notify the Government at least 180 days prior to the need date of any Government Furnished

Information/Government Furnished Equipment (GFI/GFE) required to perform certification tasks.

Technical Order 00-5-1 and 00-5-3 shall be referenced for additional information on TO certification requirements.

11.5. Verification Support. The Contractor shall support Government verification activities as required by the TOMA and the program Technical Order Life Cycle Verification Plan (TOLCVP).

The Contractor shall maintain a master mark-up of the TM or list of approved changes and record minute items during the Government verification process. The Contractor shall also support all post verification reviews and ensure availability until 100% task verification is attained by the

Government.

11.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 shall provide technical support and http://www.e-publishing.af.mil/ https://assist.dla.mil/online/start/index.cfm common source database maintenance personnel required for changes resulting from verification.

11.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 shall prepare and deliver copies of TOs and TO updates in MIL-SPEC compliance for the PPR as shown in the delivery matrix. The TOs for PPR shall be approved by the Contractor’s QA, be in compliance with the MIL-SPECs/STDs, and incorporate all verification comments and corrections approved by the TOMA or program management office representative.

11.7. Technical Data Assessment (TDA). The Contractor shall submit in-work samples of each specified TM type deliverable to the Government for specification and standardization compliance review.

11.7.1. MIL-SPEC (SGML) Data Files. The Contractor shall submit an SGML tagged TO file, associated graphics files, a PDF rendition of the SGML tagged TO file composed by the

Contractor and any associated companion files necessary for PDF creation. During assessment, the

SGML tagged TO file will be parsed against the appropriate TMSS DTD (and optionally run through the Tagging Utilization Tool (TUT)) to determine DTD compliance and correct tag usage.

The SGML tagged TO file and associated graphics will be composed by the program office and the rendered PDF will be compared with the submitted PDF to check for completeness, indexing, and

MIL-SPEC/STD compliant formatting.

11.7.2. S1000D (XML) Data Files. The Contractor shall 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.

11.7.3. Error Resolution. Errors found during the TDA shall be corrected prior to each IPR.

Additional TDAs may be necessary based on the amount of errors found during the initial TDA.

Successful TDAs in no way relieves the Contractor from fixing errors found during future reviews.

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

12.1. MIL-SPEC (SGML) Tagged Files. The Contractor shall parse all SGML files required for the

TOs prior to Government delivery and shall verify the SGML is compliant with the appropriate

DTD. NOTE: The Government will parse the files prior to acceptance using the public domain

SGML parser (http://www.jclark.com/sp/).

12.2. S1000D Source Files. The Contractor shall parse and deliver everything necessary to properly generate and view the data in the current approved IETM viewer. 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.

13. Source Data Maintenance. Contractors shall maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. The Contractor shall provide the Government a Configuration Control Management Plan. The Contractor will provide a minimum of annual updates throughout the life of the contract unless the Government determines otherwise. Maintenance includes preparation of source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes. Additionally, the http://www.jclark.com/sp/

Contractor shall 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.227-7025, Limitations on the Use or Disclosure of

Government Furnished Information Marked with Restrictive Legends.

14. TO Maintenance. Contractors shall 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 shall 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 AFTO FORM 22, 252, or other approved change request form. 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. These times start at AFTO iniation and continue until solution is fielded.

15. Schedules. The Contractor shall develop and maintain an Integrated TM 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 shall be to the system/book or TCTO level and cover all major milestones of development. Any changes to the TM Schedule and Status shall be coordinated with and approved by program TOMA and PCO.

16. Time Compliance Technical Orders (TCTOs). The Contractor shall prepare TCTOs, ITCTOs and resulting TO updates as required in support of Contractor Logistics Support (CY20) 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 Contractor Logistics Support (CY20). Costs for TCTO package development must be IAW with AFI 65-601Vol.1.

16.1. The Contractor shall deliver certified drafts of Immediate Action TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor shall deliver drafts with comments incorporated within 24 hours of receipt of comments.

16.2. The Contractor shall deliver initial certified drafts of Urgent Action TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor shall deliver final drafts with “final” customer comments incorporated, within 96 hours of receipt of comments.

16.3. The Contractor shall deliver initial certified drafts of routine safety TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor shall deliver final drafts with “final” customer comments incorporated, within 5 business days of receipt of comments.

16.4. The Contractor shall deliver certified drafts of routine TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor shall deliver final drafts with “final” customer comments incorporated, within 10 business days of receipt of comments.

17. Information Technology (IT) Requirements. The Contractor shall develop IETM requirements utilizing the designated Air Force TO System infrastructure.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

Mark the TM Type Selection Tables indicating the applicable TO types and related specifications.

LINEAR TM TYPE (PUBLICATION) SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE Contractor Logistics Support (CY20) Program

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-DTL-5096

a. Inspection and Maintenance Requirements (-6) Manual

b. Acceptance and Functional Check Flight (FCF) Procedures (-6CF)

Manual

c. Acceptance and Functional Check Flight (-6CL) Checklist

d. Inspection Workcards (-6WC)

e. Maintenance/Operations Checklists

2. Cargo Aircraft Loading and Offloading TOs MIL-DTL-5288

a. Loading Instructions Manual

b. Nuclear Weapon Cargo Loading Manual

c. Checklists

3. Weight and Balance (Aircraft) MIL-DTL-5920

a. Loading Data Manual

b. Sample Basic Weight Checklists

4. Flight Manuals MIL-DTL-7700

a. Flight Manual

b. Performance Data Manual

c. Mission Crew Manual

d. Supplemental Manual

e. Abbreviated Flight Crew Checklist

5. List of Applicable Publications MIL-DTL-8031

6. Structural Repair Manuals (for Aircraft) MIL-DTL-9854

7. Munitions/Weapons Loading Procedures, Non- nuclear and Nuclear TOs MIL-DTL-9977

a. Nuclear Weapons Basic Information and Loading Procedures

b. Nuclear Weapons Loading Procedures

c. Non-nuclear Munitions Basic Information

d. Non-nuclear Loading Procedures

e. Non-nuclear Munitions Loading Standard Data Packages (SDPs)

f. Loading Procedures Checklist

g. Single Loading Procedures Checklist

h. Integrated Loading Procedures Checklists

i. Family Group Loading Procedures Checklist

j. Nuclear Weapons Loading Procedure Checklists

k. Functional Check Procedures Checklist

l. NATO Stage B Cross-Servicing Checklists

m. End of Runway (EOR) Procedures Checklist

8. Space Operations and Support Documentation TOs

-- MIL-SPEC (Intercontinental Ballistic Missiles)

-- MIL-SPEC (Space)

MIL-PRF-38311

MIL-PRF-38314

a. Operations Manual

b. Operations Checklists

c. Technical Manuals and Related Checklists

9. Nuclear and Non-nuclear Weapon Delivery and Aircrew Procedures

Manuals and Checklists

MIL-DTL-38384

a. Non-nuclear Weapon Delivery Manual

b. Aircrew Nuclear Bomb Delivery Manual (Strategic Bomber Aircraft)

c. Aircrew Nuclear Missile Delivery Manual (Strategic Bomber Aircraft)

d. Aircrew Nuclear Bomb Delivery Manual (Tactical Aircraft)

e. Non-nuclear Weapon Delivery Checklist

f. Nuclear Weapon Delivery Checklist (Strategic Bomber Aircraft)

g. Aircrew Nuclear Bomb Delivery Checklist (Tactical Aircraft)

h. Non-nuclear Weapon Delivery Source Data Packages

10. Work Unit Code Manual

a. Standard WUC Manual

b. Two Chapter Manual

c. Three Chapter Manual

MIL-DTL-38769

11. Calibration Procedures MIL-DTL-38793

12. Time Compliance Technical Orders (TCTOs)

a. TCTO

b. TCTO Supplement

MIL-DTL-38804

13. Aircraft Battle Damage Assessment and Repair TOs MIL-DTL-87158

14. Illustrated Parts Breakdown MIL-DTL-38807

15. On-Equipment Organizational Maintenance Manual Set MIL-DTL-83495

a. General Equipment (GE) Manual

b. General System (GS) Manuals

c. Combined GE & GS Manual

d. Job Guide (JG) Manuals

e. Fault Reporting (FR) Manual

f. Fault Isolation (FI) Manual

g. Wiring Data (WD) Manual

h. Schematic Diagram (SD) Manual

16. Operation and Maintenance Instructions in Work Package Format MIL-DTL-87929

a. Maintenance Manuals

(1) Organizational Maintenance

(2) Intermediate Maintenance

(3) Depot Maintenance

(4) Combined (I&D) Maintenance

(5) On Condition Maintenance

b. Operation & Maintenance Instruction Manuals

c. Special Manuals

(1) Aircraft Engine Testing and Trending Procedures

(2) Aircraft Power Package Testing Procedures

(3) Static Firing of Missile Motors

(4) System Peculiar Corrosion Control

(5) Nondestructive Inspection (NDI)

(6) Aircraft Structural Integrity Program (ASIP)

(7) ATE Operator Test Procedures

(8) Special Requirements for Storage and Maintenance Procedures;

AUR Munitions/Launchers and Associated Support Equipment, Conventional Components and CMBR Agents

(9) Parachute Packing Procedures

(10) Operators Instructions (Hand-Held Flight Computers)

(11) Installation-Engineering Facility (Ground C-E Equipment)

d. Checklists (IAW MIL-DTL-5096)

e. With Illustrated Parts Breakdown

17. Commercial Manuals (Evaluate according to MIL-PRF-32216)

18. Aircraft Cross-servicing Guide MIL-DTL-22202

TABLE 2

TM PUBLICATION UPDATE TYPE SELECTIONS (SUSTAINMENT/MODIFICATION/CONVERSION)

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

Supple-ment

Supple-mental

TM

Source

Data

S1000D

Conver

-sion

1. 1Q-9(M)A-2 MIL-PRF-5096

2. 1Q-9(M)A-2-4 MIL-PRF-5096

3. 33D1-8-2-2-1 (RAMTS) MIL-PRF-5096

4. 33D1-8-2-2-2 (RAMTS) MIL-PRF-5096

5. Flight Manuals

6. 1Q-9(M)A-1 MIL-DTL-7700

7. 1Q-9(M)A-1-1 MIL-DTL-7700

8. 1Q-9((M)A-1-2 MIL-DTL-7700

9. 1Q-9(M)A-1-3 MIL-DTL-7700

10. 1Q-9(M)A-1-4 MIL-DTL-7700

11. 1Q-9(M)A-1CL-1 MIL-PRF-5096

12. 1Q-9(M)A-1CL-3 MIL-PRF-5096

13. 1Q-9(M)A-1CL-4 MIL-PRF-5096

14. 1Q-9(M)A-6CF-1 MIL-PRF-7700

15. 1Q-9(M)A-6CL-1 MIL-PRF-5096

16. 1Q-9(M)A-34-1-1 MIL-PRF-7700

17. 1Q-9(M)A-34-1-1CL-1 MIL-PRF-5096

18. 1Q-9(M)A-34-1-1-1 MIL-PRF-7700

19. 1Q-9(M)A-34-1-1-1CL-1 MIL-PRF-5096

20. GCS Maintenance TOs

21. 33D1-8-2-2-1 MIL-PRF-83495

TO Number, Title, or

Type of Manual

Specification

Change

Revision

Supple-ment

Supple-mental

TM

Source

Data

S1000D

Conver

-sion

22. 33D1-8-2-2-2 MIL-PRF-83495

23. 1Q-1(M)B-2-2 MIL-PRF-83495

24. 1Q-1(M)B-2-2-1 MIL-PRF-83495

25. 1Q-1(M)B-2-2-12-1 MIL-PRF-83495

26. 1Q-1(M)B-2-2-12-2 MIL-PRF-83495

27. 1Q-1(R)B-2-1 MIL-PRF-83495

28. 12P6-4-2-1 MIL-PRF-83495

29. 31R2-2TSC184-1 MIL-DTL-7700

30. 31R2-4-546-1 MIL-DTL-7700

31. 31R2-4-1943-1 MIL-PRF-83495

32. 10A9-4-2 MIL-PRF-83495

33. 1Q-1(M)B-2-2CL-1 MIL-PRF-5096

34. GCS COTS Manuals

35 1Q-1(R)B-2-4 MIL-PRF-83495

36. 35C1-2-1352-1 MIL-PRF-83495

37. Weapons

38. 1Q-9(M)A-1-2CL-1 MIL-PRF-5096

39. 1Q-9(M)A-34-1-1-2 MIL-PRF-5096

40. 1Q-9(M)A-34-1-1-2CL-1 MIL-PRF-5096

41.

42.

43.

44.

45.

TABLE 3 – LINEAR TM (PUBLICATION) DELIVERY REQUIREMENTS

FOR Contractor Logistics Support (CY20)

NOTES:

For all other media types indicate (Y)es or (N)o

TCTO requirements are specified in the contract vehicle approving the TCTO.

If “Other” is selected, define media type and quantities: n/a

DELIVERY SCHEDULE

Event Number of days data required prior to event

In Process

Review(s)

(10 Days)

Verification

(15 Days)

Prepublication

Review

(10 Days)

Final TO

Deliverable

Enter physical mailing address, electronic delivery location or web access point

AFLCMC/WIIL

2530 Loop Rd, West Bldg 560

Wright Patterson AFB OH 45433

Paper/

SGML/

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML /1

Other/

CTOCU

1004 Perimeter Rd, Rm 15900

Creech AFB

Indian Springs, NV 89018

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

ATTN: FMM

AFLCMC/WII/ DET 3

14200 Kirkham Way

Poway CA 92064

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

AFLCMC/WII/ Det 3

14200 Kirkham Way

Poway CA 92064

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

Other/

Paper/

SGML/

PDF / 1

XML / 1

Other/

Total Copies Required: 4 4 4 4

TABLE 4 – S1000D TM DELIVERY REQUIREMENTS

FOR CLS CY 2020

For all other media types indicate (Y)es or (N)o

TCTO requirements are specified in the contract vehicle approving the TCTO.

DELIVERY SCHEDULE

Enter physical mailing address, electronic delivery location or web access point

AFLCMC/WIIL Attn: TOMA

2530 Loop Rd West, Bldg 560

WPAFB, OH 45433-7106

Event Number of days data required prior to event

PDR

(Preliminary

Design

Review)

CDR

(Critical

Design

Review)

In Process

Review(s) Verification

Prepublication

Review

Final

Delivery

( 10 Days) (10 Days) (10 Days) ( 15 Days) ( 10 Days)

Deliverable

Common Source Data

Base (CSDB)

Businesss Rules

Exchange (BREX) files

Data Management

Requirements List

(DMRL)

Stylesheets

Output Generation

Tools/Files

Multimedia Files

Graphic Files

Authoring Guide(s)

Technical Manual

Content and Product

Plan

Configuration Control

Management Plan

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

All TMSS applicable to this contract shall have an appropriately tailored SIR attached to this section.

SIRs included in the untailored TMCR format represent the minimum tailoring requirements that must be included in the final contract, unless the entire SIR is not applicable; e.g., if MIL-DTL-22202D is not required, the entire SIR can be deleted.

Utilize the TMCR S1000D Decision Support Tool located at https://techdata.wpafb.af.mil/tmss/index.html for the MIL-

STD-3048 SIR by selecting all applicable project functionality requirements, project business rules, and the desired tailoring options expressed in paragraphs 6.2. Attach the three S1000D Decision Support Tool spreadsheet outputs in the specified sections listed below.

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from

Acquisition Streamlining and Standardization Information System (ASSIST) web page, https://assist.dla.mil/online/start/index.cfm.

TMSS entries designated with A, F, M or N refer to Army, Air Force, Marine Corps or Navy requirements.

Comments (recommendations, additions, deletions) and any pertinent data which may be in use in improving Air Force

TMSS documents should be submitted to AFLCMC/HIAM, 4170 Hebble Creek Road, Bldg. 280, Door 15, Area A, Wright-Patterson AFB, Oh 45433-5653 or by email to; SGMLsupport@us.af.mil. Do not include the street address, a building number or a zip+4.

Specification/Standard Interface Record for MIL-STD-3048A 29 April 2016

Air Force Business Rules for the Implementation of S1000D

PROJECT FUNCTIONALITY REQUIREMENTS

PROJECT BUSINESS RULE REQUIREMENTS:

Project Tailored 6.2 Options:

https://techdata.wpafb.af.mil/tmss/index.html https://assist.dla.mil/online/start/index.cfm mailto:SGMLsupport@us.af.mil

ATTACHMENT 1

Graphics Format Guidelines

GENERAL GUIDELINES

Single column graphics should not exceed 51 Picas High by 20 Picas Wide. (Paper only)

Full page graphics should not exceed 51 Picas High by 42 picas Wide. (Paper only)

Fold Out graphics should not exceed 51 Picas High (width on foldouts is not important). (Paper only)

Encapsulated Post Script (EPS):

Raster based images will not be saved as EPS.

EPS files shall not be a mix of vector and raster images. Vector only.

Any source data (photos used for tracing etc.); used in aiding of creation of EPS (templates, etc.)

will be deleted from illustration prior to saving/exporting.

If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

Tagged Image File Format (TIFF):

Black and white raster images should only be saved as Bitmap and not Grayscale, RGB or

CMYK.

Grayscale or Color images (screenshots, etc.) will be saved as such (Grayscale, RGB or CMYK) and will not be bitmap converted using a halftone screen.

To further aid in file size reduction for storage purposes, images should be compressed using

Group 4 compression when saving/exporting.

Computer Graphics Metafile (CGM):

Raster based images will not be saved as CGM.

Any source data used in aiding of creation of CGM (templates, etc.) will be deleted from illustration prior to saving/exporting.

CGM files shall not be a mix of vector and raster images. Vector only.

If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

Unless Version 4 is specifically required for hotspots and/or hyper linking, CGMs should be exported as version 3 to increase cross platform compatibility.

DWG File Format:

Raster based images will not be saved as DWG.

DWG files shall not be a mix of vector and raster images. Vector only.

Any source data used in aiding of creation of DWG (templates, etc.) will be deleted from illustration prior to saving/exporting.

If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

Joint Photographic Expert Group (JPEG):

JPEG File format should be used as last resort. Color screenshots/photos should be saved as

TIFFs due possible system compatibility issues.

B&W Bitmaps should not be saved as JPEGs.

Portable Network Graphics (PNG):

Used for raster graphics

Supports lossless data compression

Bitmap (BMP):

Used for raster graphics

Scalable Vector Graphics (SVG):

Two-dimensional vector and mixed vector/raster graphics

ATTACHMENT 2

REQUEST FOR TECHNICAL ORDER NUMBER

1. *PRIME SYSTEM APPLICATION (If Applicable or N/A)_______________________________

2. *CONTRACT NUMBER/PURCHASE REQUEST (PR) NUMBER: _____________________

3. *MISSION DESIGN SERIES/NOMENCLATURE (Name Of Equipment) __________________

4. *FEDERAL STOCK CLASS:_______________________________________________________

5. *PART NUMBER(s):______________________________________________________________

6. *NSN/FSN: (or temp NSN) __________________________________________________________

7. *PUBLICATION TYPE (Opn & Maint with IPB, Overhaul, WUC, IPB, LOAP, etc.)

8. *SUGGESTED TECHNICAL ORDER NUMBER:_____________________________________

9. *RECOMMENDED TITLE OF MANUAL (Leave Blank if Classified) ____________________

10. *CLASSIFICATION OF MANUAL: ________________________________________________

11. *CLASSIFICATION OF TITLE: ___________________________________________________

12. *KIND OF EQUIPMENT (Airborne / Ground / Not Applicable):___________________________

13. *TEST EQUIPMENT? Yes / No

14. PROGRAM ELEMENT CODE (PEC): ________________________________________________

15. LEAD COMMAND: _______________________________________________________________

16. DOES MANUAL EXIST FOR SAME/SIMILAR EQUIPMENT? Yes / No

17. EXISTING MANUAL TO NUMBER: _________________________________________________

18. COMMERCIAL OFF THE SHELF (COTS) ITEM: Yes / No

19. CONTRACTOR INFORMATION: (If Applicable)

a. NAME OF VENDOR: _____________________________________________________

b. ADDRESS: _____________________________________________________________

c. MANUFACTURER'S CODE: ______________________________________________

d. POINT OF CONTACT: ____________________________________________________

20. FOREIGN MILITARY SALES (FMS) YES ___ NO ____ (If YES, complete item 21)

21. COUNTRY CODES (For CSTO/FMS manuals): (See TO 00-5-19) __________________________

22. COMMENTS:______________________________________________________________________

* = Mandatory Field

Functionality Requirements for Program: Contractor Logistics Support (CY20) 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.

No exception, Login/Logout via Common Access Card (CAC)

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

NO exception, 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.

Yes

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.

No

Functionality Category - 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.

no wire trace, exception

Functionality Category - External Processes

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

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.

System/subsystem navigation 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

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.

Search 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

Functionality Category - Special Content 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

Animated graphics support

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

Yes

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

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.

Functionality Category - User Operation Mode

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.

no can we do this

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

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 Physical media delivery/distribution

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

Yes exception, 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

Project Business Rules for Program:

Contractor Logistics Support (CY20)

BRPD# Business Rule Decision Point Title/Definition Project Decision Additional Comments S1000D, Issue 4.0.1, Chapter 1.3 -

How to use the specification

BRDP-S1-00001 Use of "I" and "O":

Decide whether and when to use the alpha characters "I" and "O".

Additional info: This decision is referring to use of those characters in data module codes, publication module codes, and scorm package codes.

The use of alpha characters "I" and "O" is allowed as appropriate.

However, authors must ensure fonts used in the publication allow for the end user to easily distinguish "I" and "O" from "1" and "0".

BRDP-S1-00002 List of permitted CAGE codes and/or names of the originator companies to be used for the technical publications:

Create a list of permitted CAGE codes and/or names of the originator companies

The project shall create and maintain a list of permitted commercial and government entity (CAGE) codes and/or names of the originator companies. This list will be created after contract award.

S1000D, Issue 4.0.1, Chapter 2.5.1

- Business rules - Categories and layers

BRDP-S1-00003 Issue of S1000D to be used:

Decide which issue or issues of S1000D to be used.

S1000D issue 4.0.1 shall be used.

BRDP-S1-00004 Information sets to be used:

Decide which information sets, given in S1000D and/or project specific, to be used.

The selected information sets (i.e. the technical content requirements to be covered) are defined in the TMSS listed in the table at the end of this spreadsheet. These information sets are to be used in place of the information sets defined in chapter 5 of S1000D.

BRDP-S1-00005 Publications to be produced:

Decide which publications to be produced.

The program shall coordinate with the contractor after contract award and collaborate in the contractor's creation of the Data Management Requirement List (DMRL). The DMRL shall list all data modules and publications desired by the program to be produced and delivered by the contractor.

BRDP-S1-00006 Schemas to be used:

Decide which Schemas to be used and in which information set they are to be used.

Only the promulgated S1000D schemas for issue 4.0.1, available at http://www.s1000d.org shall be used. The contractor shall use the schema that best fits the technical data being authored (i.e.

descriptive data uses the descript schema, troubleshooting data uses the fault schema, etc.) with final approval by the program.

BRDP-S1-00007 Use of optional elements and attributes:

Decide whether and how to use each optional element and attribute in its structural context

Optional elements and attributes shall be used as necessary to support program functionality requirements and as dictated by Air Force and project business rules.

BRDP-S1-00008 Possible deliverables:

Decide on the possible deliverables, such as:

- S1000D objects (eg, data modules, publication modules, illustration sheets and multimedia objects, data management lists) using file based transfer.

- Page-oriented publications and/or interactive electronic technical publications.

All deliverables are be listed in the TMCR.

BRDP-S1-00009 Frequency of data exchanges:

Decide on the frequency of data exchanges.

Frequency of data exchanges are specified in the TMCR as part of the delivery schedule.

S1000D Chapter 3.4 - Information generation - Zoning and access

BRDP-S1-00010 Zone and access point identification system:

Decide whether to use a zoning and access identification system.

A zoning and access identification system shall be used.

BRDP-S1-00011 Method for zoning and identifying access points:

Decide which method to use for zoning and identifying access points.

The contractor shall select the most appropriate method for zoning and identifying access points by following S1000D guidelines (see chapter 3.4.1 in S1000D). The program shall give final approval of the method selected.

S1000D Chapter 3.6 - Information generation - Security and data restrictions BRDP-S1-00012 Define security classification values and terms (attribute securityClassification):

Decide which values to use for the attribute securityClassification and allocate suitable definitions. Refer to Chap 3.9.6.1.

The following values for the attribute securityClassification shall be used:

- 01 unclassified

- 02 not allowed

- 03 confidential

- 04 secret

- 05 top secret

- 06-50 - not allowed

- 51-99 not allowed

BRDP-S1-00013 Use and markings of security classifications (attribute securityClassification):

Determine how the security classifications will be used.

Security classifications shall be marked in accordance with DoD information security program instructions/directives.

BRDP-S1-00014 Application of caveats:

Determine if the policies that apply to security marking, instructions, etc, and how those markings are required to be applied within the given project.

The application of caveats shall be in accordance with DoD information security program instructions/directives. Neither commercial classification nor national caveat shall be used as an alternative to security classification.

BRDP-S1-00015 Retention of security classifications:

De…