B-52 S1000D SOW 16 Aug 2024.pdf

DRAFT

SOW

16 Aug 2024

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (contract award date). Other request for this document shall be referred to AFLCMC/WBDIT.

Statement of Work For

Conversion of B-52 Technical Manuals to an Interactive Electronic Technical Manual (IETM)

In accordance with S1000D 4.1 and MIL-STD 3048B Specifications

Purchase Request:

SOW

16 Aug 2024

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (contract award date). Other request for this document shall be referred to AFLCMC/WBDIT.

Signature Page

Office Name Signature

QAPC

AFLCMC/WBD PK

AFLCMC/WBD TOMA

AFLCMC/WBD PM

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

AFLCMC/WLS.

1. DESCRIPTION OF SERVICES

1.1. Objective(s):

This Statement of Work (SOW) describes the services required to convert B-52 Technical Manuals (TMs) to formats necessary to produce an Interactive Electronic Technical Manual (IETM) in accordance with (IAW) S1000D 4.1 and MIL-STD-3048B specifications, and project decisions made/documented by AFLCMC/WBD (see Appendix B). The delivered S1000D based IETM shall support the functions outlined within the Functionality Matrix (see Appendix C). Services include conversion of the existing technical manuals from Standard General Markup Language (SGML)-tagged files to Extensible Markup Language (XML)-tagged files, creation/utilization of a Common Source Database (CSDB) for management of the IETM content and rendering of IETM output that is functional within the Air Force approved IETM viewer. The contractor shall prepare all XML IAW the tagging requirements of the Air Force Technical Order Authoring and Publishing (TOAP) “SGML Best Practices” guidelines.

The contractor shall ensure tagging requirements are met to produce a specification compliant output within the TOAP system for all identified TOs. The Government will furnish property incidental to the place of performance, when requested by the contractor, including office space and equipment, i.e., computer equipment. A primary goal of the data conversion effort is to create as much intelligent data as possible as specified in MIL-STD-3048B, paragraph 4.4.2. Intelligent data within the IETM is critical to the enabling of enhanced diagnostics and fault reporting when used in conjunction with the future AF Product Lifecycle Management (PLM) and Maintenance, Repair and Overhaul (MRO) systems. In all instances where tabular data and flow data is presented as graphics in the existing TM, this data shall be converted to XML-tagged data using the appropriate S1000D data module (DM) schema.

The work will consist of approximately 355 Technical Manuals to be converted to a SNS/SSSN data base to support the conversion of the SGML-tagged files to XML-tagged files following the S1000D Version 4.1 data module specifications. This amounts to approximately 120,000 pages in the current formats. Additionally, approximately 40,000 illustrations will require conversion from current format (SVG, GGM, CALS, GIF, PDF, TIFF, JPEG, etc.) to a standard SVG format. This effort will result in approximately 15,000 Data Modules. All data must be developed using a structured System, Sub-System, Sub-Sub-System Numbering (SSSN) schema and updating the Technical Manual numbering using MIL-STD-1808. The B-52 Work Unit Code Manual will require an update to include a reference for all SSSN codes to link to their respective Work Unit Codes. Approximately 640 B-52 S1000D Project Business Rules will be used, and if changed during the program, the contractor will be required to update the Business Rules. After verification of the data contained in each Data Module, the entire database will be required to be validated against a contractor-developed Business Rules Exchange (BREX) Data Module to ensure all Project Business Rules are met and the overall work meets all Functionality Matrix requirements.

1.2. Background:

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

AFLCMC/WLS.

The B-52 System Program Office (B-52 SPO) in conjunction with Air Force Global Strike Command/A4 (AFGSC/A4) has established the requirement to convert B-52 TMs to formats necessary to render an IETM IAW S1000D 4.1 and MIL- STD- 3048B specifications and project decisions made by AFLCMC/WBD.

2. SERVICES SUMMARY

Performance Objective Reference Performance Threshold

Reporting Loss of Government Property

3.6

The Contractor shall submit IAW A001 within 10 days of discovery of loss for each loss of government property.

Program Management Plan

(PMP)

4.1 The contractor shall refer to the B-52 SPO

PMP and shall provide detailed information explaining how the Contractor plans to manage all aspects of the contract, to include cost, schedule, performance, and sub contract management. The Contractor shall deliver any exceptions to the Program Management Plan (PMP) to the Government at least three (3) business days prior to the Post-Award meeting and shall present the annex PMP during the Post- Award meeting. Any changes or corrections noted by the Government shall be incorporated and the updated document shall be delivered to the Government within five (5) business days after the completion of the meeting.

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

Risk Management Plan 4.2 The contractor shall refer to the B-52 SPO RMP and shall outline any S1000D major risks to execution of the proposed program and the Contractor’s proposed risk mitigation strategies. The Contractor shall deliver an annex to the Risk Management Plan (RMP) to the Government at least three (3) business days prior to the post- Award meeting and shall present the RMP during the Post-Award meeting. Any changes or corrections noted by the Government shall be incorporated and the updated document shall be delivered to the Government within five (5) business days after the completion of the meeting.

Risk Status Reports 4.2 The Contractor shall prepare a Risk Management Status Report each month outlining any effort made towards reducing or avoiding risk and shall submit report monthly in conjunction with the Monthly Status Report.

Integrated Master Schedule

(IMS)

4.3 The IMS shall outline the conversion

schedule for all TMs to be converted by system/sub-system/sub-sub-system. The Contractor shall deliver an Integrated Master Schedule (IMS) to the Government at least three (3) business days prior to the Post-Award meeting and shall present the IMS during the Post- Award meeting. Any changes or corrections noted by the Government shall be incorporated and the updated document shall be delivered to the Government completion of the meeting.

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

Configuration Management Control Plan (CMCP)

4.4 The Contractor shall refer to the B-52

SPO Configuration Management Control Plan (CMCP) and shall deliver an annex with contract specific exceptions. The Contractor shall outline how they will meet the requirements of the configuration management control plan to include how they will track and manage data utilizing methods that ensure support of aircraft applicability filtering. The Contractor shall deliver the annex to the B-52 SPO CMCP to the Government at least three

(3) business days prior to the Post-Award meeting and shall present the CMCP annex during the Post-Award meeting.

Any changes or corrections noted by the Government shall be incorporated and the updated document shall be delivered to the Government within five (5) business days.

Quality Control Plan (QCP) 4.5 The QCP shall address processes to be utilized to address detection of quality program problems and defects, identification of root causes for quality related problems or defects, correction of root causes related to detected problems or defects, and follow-up actions necessary to ensure quality related problems and defects do not reoccur. The Contractor shall deliver a Quality Control Plan (QCP) to the Government at least three (3) business days prior to the Post-Award meeting and shall present the QCP during the Post-Award meeting. Any changes or corrections noted by the Government shall be incorporated and the updated document shall be delivered to the Government completion of the meeting

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

Technical Order Guidance Conference (TOGC)

The Contractor shall develop with the Government the requirements for the TM- 86-01 Technical Manual Contract Requirements (TMCR). The requirements shall be determined through coordination and delivered 3 days before the TOGC.

The Contractor shall conduct a TOGC within 45 day of contract award and the TMCR requirements shall be finalized in that meeting.

Post-Award Conference 4.6.1 The purpose of the Post-award conference is to ensure the Contractor possesses a clear understanding of the contract requirements and can demonstrate that understanding to the Government. The Contractor shall ensure the appropriate personnel attend the meeting. The contractor shall schedule the post-award conference within 10 days after award.

The Contractor shall deliver a proposed agenda to the Government at least five (5) business days prior to the planned conference. The Contractor shall be responsible to take and compile notes from the meeting and to complete action item listings for incorporation into the action item list. The meeting minutes and action item list shall be delivered to the Government within five (5) business days after concluding the meeting. The government shall provide feedback to the contractor within ten business days.

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

Technical Interchange Meetings

(TIM)

4.6.2 The Contractor shall ensure the

appropriate personnel attend each meeting. The Contractor shall prepare agenda items for meetings in conjunction with the Government Program Manager.

The Contractor shall deliver a proposed agenda to the Government at least five (5) business days prior to the planned conference. The Contractor shall be responsible to take and compile notes from the meeting and to complete action item listings for incorporation into the action item list. The minutes, action items, and meeting materials shall be submitted to the government within five (5) business days of the completion of the meeting.

Program Management Reviews

(PMR)

4.6.3 The Contractor shall ensure the

appropriate personnel attend each meeting. The quarterly PMR shall demonstrate contractor understanding of contract execution status and shall cover contract cost, schedule, and performance status, as well as issues/risks affecting each of those program categories. The Contractor shall deliver a proposed agenda to the Government at least five (5) business days prior to the planned conference. The minutes, action items, and meeting materials shall be submitted to the Government within five (5) business days of the completion of the meeting.

Technical Manual Schedule and Status Report

4.6.4 The Contractor shall submit a Technical

Manual Schedule and Status (TMSS) Report on the tenth (10th) business day of each month during the contract performance period. The TMSSR shall contain information outlining efforts accomplished toward achievement of the contract objectives, and any difficulties encountered during the month covered by the TMSSR.

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

Data Conversion 4.7 The conversion shall result in delivery of converted data meeting the specific requirements of the TMCR: Standard Numbering System/System Subsystem Sub-subsystem Number SNS/SSSN, XML-tagged content, and graphics, and a rendered IETM containing the functionality outlined within the associated functionality matrix. The Contractor shall deliver all converted DMs, to include all appropriate graphics, to the Government for Verification and Validation. The Contractor shall provide a complete and accurate traceability matrix supporting SNS with SSSN, 3rd subsystem level of data, with all data converted into S1000D format as it relates back to the original source documents utilized.

TO Life Cycle Validation Plan (TOLCVP) and Validation Sessions

4.12.1 The Contractor shall refer to the B-52

SPO TOLCVP and shall develop an annex by exception to be delivered to the Government at least 20 business days prior to completion of any Data Modules.

The Government shall review the annex and notify the contractor of any errors or acceptance. If errors are noted, the contractor shall correct and return the document to the government within 10 business days. In accordance with the TOLCVP, and TOs 00-5-1 and 00- 5-3, the Contractor shall support the Government during a tabletop validation/verification (V/V) of the converted data. The agenda shall be delivered to the Government at least ten business days prior to the planned sessions. During the sessions, the contractor shall record thorough notes and document all issues for inclusion into the meeting minutes or action item listing.

Deployment Validation/Verification

4.12.2 The purpose of the session is to verify

usability prior to a system deployment decision and Government acceptance of the final deliverables. The deliverables shall be 100% accurate for content and meet all functionality matrix requirements.

The agenda shall be delivered to the

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

Government at least ten (10) business days prior to the planned sessions. During the sessions, the contractor shall record thorough notes and document all issues for inclusion into the meeting minutes or action item listing.

Familiarization Training Plan and Material

4.12.3 The contractor shall conduct and support

familiarization training for up to 20 students. The Contractor shall prepare a Technical Training Plan and Training Materials to ensure maximum use of training time. The Training Plan shall be delivered to the Government at least 20 business days prior to the beginning of training. The Government shall review the Plan and provide any corrections or comments to be incorporated. The contractor shall deliver the corrected version of the Plan within five (5) business days.

Final Deliverables 4.14 The final deliverables of the IETM will consist of the database in SNS format with SSSN 3rd level of fidelity, Data Module Requirements List (DMRL), Business Rules Exchange (BREX), Publication Module, Applicability Cross-reference table, Conditions Cross-reference Table and Product Cross-reference Table, all data modules and graphics compliant with S1000D Issue 4.1, MIL-STD-3048B and project decision points, as well as the CSDB, by posting on DOD SAFE or by storing all deliverables on a government provided laptop computer. The IETM shall meet all requirements as delineated in TM-86- 01 TMCR. The contractor shall prepare all XML IAW the tagging requirements of the Air Force Technical Order Authoring and Publishing(TOAP) “SGML Best Practices” guidelines. The contractor shall ensure tagging requirements are met to produce a specification compliant output within the TOAP system for all identified TOs. The Contractor shall deliver a proposed agenda to the Government at least five

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

(5) business days prior to the planned conference. The minutes, action items, and meeting materials shall be submitted to the Government within fifteen (15) business days of the completion of the meeting.

Quality of CDRL deliverable

4.17 The Government will reject a deliverable

if two (2) technical errors or three

(3) minor errors are found within the deliverable. There shall be no more than three (3) total rejection(s) of deliverables per Quarter. The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of Government rejection.

Receipt of CDRL deliverable 4.18 CDRL deliverables shall be submitted directly to the Multifunctional Team (MFT) member identified on the CDRL.

There shall be no more than one (1) late submission(s) of deliverables per month.

The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Travel and Trip Reports 5.3 Travel requests for Contractor/sub-contractor personnel shall be submitted for approval to the Contracting Officer prior to costs being incurred and a minimum of 10 business days in advance of departure.

Each traveler shall submit a travel report within five (5) business days after conclusion of travel.

Safety and Health Plan 5.7.1 The Contractor shall submit a Safety and Health Plan to the MFT or as indicated by CDRL instructions.

Mishap Notifications 5.7.2 The Contractor shall ensure they notify the Contractor Officer Representative (COR) within four (4) hours of any mishaps that occur within a government facility. They shall also ensure the Safety Office and the Purchasing Contracting Officer (PCO) are notified.

The Contractor shall cooperate with

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

Government safety investigations.

3. GOVERNMENT PROPERTY:

3.1. Contractor Responsibility:

The Contractor shall be responsible for Government property provided to support this effort in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract. All data provided by the Government to the Contractor will always remain the property of the Government. Technical data input and processed during the performance of this contract must always be maintained in a readable and readily retrievable format. Technical data received, created or edited during performance of the contract requirements shall be the property of the Government and shall be made available to the government upon request at any point during the contract period of performance.

3.2. Government Property to be provided:

Government property to be provided includes B-52 technical data as specified in the TMCR and Technical Orders Listing in Attachment 1.

3.3. Base Support:

For portions of the effort to be performed on an Air Force installation, the Government will furnish meeting space.

3.4. Reporting of Government Property:

The Contractor shall create and maintain records of all Government property accountable to the contract.

3.5. Loss of Government Property:

Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.6. Reporting Loss of Government Property:

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

The Contractor shall report loss of Government property using Defense Contract Management Agency (DCMA) / Access to eTools. The Contractor shall submit IAW A0XX within 10 days of discovery of loss for each loss of government property. (CDRL A0XX DI-MGMT-80269 Government Property Damage or Loss Report)

3.7. Return or Retention of Government Property:

All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but not later than upon completion of the contract, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract becomes the property of the Government and shall be returned to the Government as directed, but not later than upon completion of the contract, unless the PCO directs the Contractor to retain the material for continued use under a successor contract. Upon completion of all deliveries required by this contract, the contractor shall return any original data storage media provided by the Government.

4. TECHNICAL REQUIREMENTS

4.1. Program Management Plan

The contractor shall refer to the B-52 SPO PMP and shall provide a detailed annex explaining how the Contractor plans to manage all aspects of the contract, to include cost, schedule, performance, and sub contract management. The Contractor shall deliver the annex to the Program Management Plan (PMP) to the Government at least three (3) business days prior to the Post-Award meeting and shall present the information during the Post-Award meeting. Any changes or corrections noted by the Government shall be incorporated and the updated document shall be delivered to the Government within five (5) business days after the completion of the meeting. The B-52 SPO PMP shall provide detailed information explaining how the Contractor is to manage all aspects of the contract, to include cost, schedule, performance, and sub-contract management. The Contractors annex to the PMP shall provide details as to how the Contractor shall incorporate various tasks within the overall program to assure a fully integrated approach for all technical aspects and program elements. The PMP shall demonstrate a clear plan and understanding of how the Contractor may subcontract with other companies to establish capability to meet diverse contractual requirements. If a sub-contractor is to be used, the PMP annex shall clearly delineate how the Contractor intends to disseminate portions of this contract workload to contract team members. (CDRL A0XX – DI- MGMT-81797 – Program Management Plan)

4.2. Risk Management Plan and Status Reports

The contractor shall refer to the B-52 SPO RMP and shall outline any S1000D major risks to execution of the proposed program and the Contractor’s proposed risk mitigation strategies.

The Contractor shall deliver a Risk Management Plan (RMP) annex to the Government at least three (3) business days prior to the Post-Award meeting and shall present the information during the Post-Award meeting. Any changes or corrections noted by the Government shall be

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to incorporated and the updated document shall be delivered to the Government within five (5) business days after the completion of the meeting. The RMP annex shall outline the major risks to execution of the proposed program and the Contractor’s proposed risk mitigation strategies. The Contractor shall prepare a Risk Management Status Report each month outlining any effort made towards reducing or avoiding risk and shall submit report monthly in conjunction with the Monthly Status Report. The report shall include any newly identified risk and provide mitigation strategies.. (CDRL A0XX, DI- MGMT-81808 Risk Management Plan and CDRL A0XX, DI-MGMT-81809 Risk Management Status Report)

4.3. Integrated Master Schedule

The Contractor shall deliver an Integrated Master Schedule (IMS) to the Government at least three (3) business days prior to the Post-Award meeting and shall present the IMS during the Post-Award meeting. Any changes or corrections noted by the Government shall be incorporated and the updated document shall be delivered to the Government within five (5) business days. The IMS shall outline the conversion schedule for all TOs to be converted by system/sub-system. The IMS shall provide detail down to the TO and Data Module level indicating the expected start date, actual start date, planned completion date, and actual completion date for conversion of a particular TO and creation to finish of each Data Module. The schedule shall maintain all data in order to provide a detailed view of completed TO conversions and how each conversion is progressing during the conversion process. The monthly IMS update shall be submitted by the Contractor in conjunction with the monthly status report. (CDRL A0XX - DI- MGMT-81650 – Integrated Master Schedule)

4.4. Configuration Management Control Plan

The Contractor shall refer to the B-52 SPO Configuration Management Control Plan (CMCP) and shall deliver an annex with contract specific exceptions. The Contractor shall deliver an annex to the Government at least three (3) business days prior to the Post-Award meeting and shall present the CMCP annex information during the Post- Award meeting. Any changes or corrections noted by the Government shall be incorporated and the updated document shall be delivered to the Government within five (5) business days. The Contractor shall prepare and publish a plan to maintain configuration control of all source data and shall manage data utilizing methods that ensure support of aircraft applicability filtering. The plan shall specifically address how current TCTO completion data shall be incorporated into the S1000D Applicability Modules and meet the intent of AFI 21-101, paragraph 14.3.2. (CDRL A0XX - DI- SESS-80858C – Configuration Management)

4.5. Quality Control Plan

The Contractor shall deliver a Quality Control Plan (QCP) to the Government at least three (3) business days prior to the Post-Award meeting and shall present the QCP during the Post-Award meeting. Any changes or corrections noted by the Government shall be incorporated and the updated document shall be delivered to the Government within five (5) business days. Any changes or corrections noted by the Government

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to shall be incorporated and the updated document shall be delivered to the Government within five (5) business days. The QCP shall address processes to be utilized to address detection of quality program problems and defects, identification of root causes for quality related problems or defects, correction of root causes related to detected problems or defects, and follow-up actions necessary to ensure quality related problems and defects do not reoccur. The Contractor shall ensure quality of services through utilization of a quality and/or inspection system and shall identify the Quality Management System (QMS) to be utilized by the Contractor within the QCP, which shall include the schedule of quality assurance/control inspections planned by the Contractor. A compliance rate of 100 percent with regard to the QCP/QMS is required. The Contractor must obtain approval of the QCP from the Contracting Officer Representative (COR) prior to initiation of any data conversion work. The Government reserves the right to require necessary changes to the plan and to Contractor operations in order to obtain the required level of quality. If changes to the plan are necessary, the COR must approve the changes prior to implementation. See paragraph 4.18 and 4.19 for additional details concerning delivery of CDRLs. (CDRL A0XX, DI-QCIC-81722 Quality Control Plan)

4.6. Meetings and Reports Overview

The Contractor shall participate in and functionally support meetings and reviews. The Contractor shall coordinate agenda items with the Government Program Manager and/or COR and provide a published agenda to the Government. The Contractor shall appoint an individual to record minutes and provide conference documents, to include the minutes, action items lists, and all material presented by the Contractor during the meeting. The action item list shall include all action items opened, postponed or changed, and closed during the meeting. The action item list shall be considered a living document and shall require continuous update throughout the contract performance period, with all items (regardless of status) remaining on the list throughout the contract performance period. The action item listing shall be a part of the meeting minutes.

4.6.1. Post-Award Conference

A Technical Order Guidance Conference will be held no later than 45 calendar days after contract award or, as scheduled by the Government, at a contractor facility located at or near Tinker AFB, Oklahoma. The purpose of the TOGC Post-award meeting is to review the TMCR and ensure the Contractor possesses a clear understanding of the requirements. The post-award conference will also provide an opportunity for introduction of the Contractor’s Management team, and presentation of the PMP, IMS, RMP, and QCP to the Government. All key Contractor personnel should attend this meeting. The PCO will notify Contractor of the specific date, location, and proposed agenda items within 10 calendar days after contract award. The Contractor shall deliver a proposed agenda to the Government at least five (5) business days prior to the planned conference. The Contractor shall be responsible to take and compile notes from the meeting and to complete action item listings for incorporation into the action item list.

The meeting minutes and action item list shall be delivered to the Government within five (5) business days after concluding the meeting. (CDRL A008 – DI-ADMN- 81249B – Conference Agenda) (CDRL A009 – DI-ADMN-81250B Conference

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

Minutes)

4.6.2. Technical Interchange Meetings

Technical Interchange Meetings (TIMs) shall meet twice a year during the contract Period of Performance (POP) and shall be held at a Government approved location. The Contractor shall coordinate the date and location with the Government COR. The Contractor shall deliver a proposed agenda to the Government at least five (5) business days prior to the planned conference. The Contractor shall be responsible to take and compile notes from the meeting and to complete action item listings for incorporation into the action item list. (CDRL A0XX

– DI-ADMN-81249B – Conference Agenda) (CDRL A0XX – DI-ADMN-81250B Conference Minutes)

4.6.3. Program Management Reviews

A Program Management Reviews (PMR) shall be held quarterly throughout the POP, at a minimum, with increased frequency based on the discretion of the Program Manager (PM) and Procurement Contracting Officer (PCO). The purpose of PMRs is to review contract execution status and shall cover contract cost, schedule, and performance status, as well as issues/risks impacting each of those program categories. Scheduled PMRs shall be depicted in the IMS and all key Contractor personnel shall attend. The Contractor shall deliver a proposed agenda to the Government at least five (5) business days prior to the planned conference. The Contractor shall be responsible to take and compile notes from the meeting and to complete action item listings for incorporation into the action item list. (CDRL A0XX – DI-ADMN-81249B – Conference Agenda) (CDRL A0XX – DI-ADMN-81250B Conference Minutes)

4.6.4. Technical Manual Schedule and Status Reports

The Contractor shall submit a monthly Technical Manual Schedule and Status Report (TMSS) on the fifth (5th) business day of each month during the contract POP. The TMSS shall contain information outlining efforts accomplished toward achievement of the contract objectives, and any difficulties encountered during the month covered by the TMSS. The TMSS shall specifically compare planned goals with achieved goals and budgeted resources with actual resource usage. The report shall provide the Government with a means to gauge Contractor performance. (CDRL A0XX - DI-MGMT-80368A – Status Report)

4.7. Data Conversion

The Contractor shall convert SGML-tagged technical content to XML-tagged format using the S1000D specification (version 4.1), the business rules contained in MIL- STD-3048B, and applicable project rules provided specifically for this effort. The conversion shall result in delivery of converted data meeting the specific requirements of the TMCR (XML-tagged content and graphics), and a rendered IETM containing the functionality outlined within the associated functionality matrix. The conversion approach shall ensure conversion of technical manuals by system (i.e., hydraulics), not by type (i.e., illustrated parts breakdowns), with the full conversion effort consisting of

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

21 systems. Upon completion of each system conversion effort, data shall be incorporated with the system(s) previously converted, growing the IETM throughout the conversion effort until final delivery. Each converted system/sub-system delivery shall include, in addition to the data modules and graphics, an updated Data Module Requirements List (DMRL), BREX (Business Rules Exchange), Publication Module, Applicability Cross-reference table, Conditions Cross-reference Table, Product Cross-reference Table, and Process data modules. The Contractor shall provide a report to the government outlining any recommended changes to the business rules or project decisions. All recommended changes shall be reviewed, and approval must be granted by the Government prior to being incorporated into the project. The Contractor shall number and map the existing technical data listed in the TMCR to the Data Module Requirements List (DMRL) and shall convert approximately 40,000 graphics from current format to Scalable Vector Graphics (SVG) version 1.1 format. After initial mapping of TMs to the DMRL, the Contractor shall provide documentation to the Government of any DM that should be added, deleted, or modified. The documentation shall indicate the specific DM and corresponding source data, the reason for the change, and the recommended new DM. The Government will approve, disapprove, or recommend an alternate to the Contractor’s proposed change within 10 business days of receipt from the Contractor. Upon approval from the Government, the approved DM shall be incorporated into the DMRL by the Contractor within five business days. Procedural steps within graphics shall be mapped in accordance with the S1000D specifications. The Contractor shall deliver all converted DMs, to include all appropriate graphics, to the Government for Verification and Validation. The Contractor shall provide a complete and accurate traceability matrix of all data converted into S1000D format as it relates back to the original source documents utilized. Appendix C provides an example of the structure for the DRML. (CDRL B0XX, TM-86-01 Technical Manuals Contract Requirement (TMCR))

4.8. Data Freeze Date

In order to limit changes to technical content during the data conversion effort, source data to be utilized for conversion of each specific system will be limited to those Technical Manuals published 30 calendar days prior to the start of conversion of each specific system. The date 30 days prior to start of the conversion effort for each system will be considered the data ‘freeze date’ for that system conversion effort. If the conversion for a specific system is to exceed one year, the contractor shall incorporate changed/updated technical content data, not to exceed 12,500 pages quarterly, into the conversion process for that system. The Contractor shall develop a baseline IETM based upon the publications published prior to the freeze date.

4.9. Conversion of Fault Isolation Manuals

The conversion of the Fault Isolation Manuals shall consist of two distinct steps. First, the Contractor shall deliver the fault isolation manuals tagged into Standard Generalized Markup Language (SGML) IAW MIL-DTL-83495. This allows for the data to continue to be housed and sustained within the Air Force enterprise Technical Order Authoring and Publishing (TOAP) system without any negative impact to the maintainer.

The Contractor shall convert the newly SGML- tagged Fault Isolation Manual files into

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

XML-tagged files in S1000D DM format. (CDRL B0XX, TM-86-01 Technical Manuals Contract Requirement (TMCR))

4.10. Support of Off-Equipment PDF Manuals

Manuals for support equipment and operational (flight) manuals will remain in Type I (One) structured page-orientated format. The Contractor shall include links in the IETM DM to link from the IETM to the non-converted off-equipment manuals. This shall be a “one-way” link. The link shall be in the IETM and “point” to the appropriate location in the off-equipment technical manual. There is no requirement for the off-equipment technical manuals to have links back to the IETM, except to allow the user to return to the area of the IETM from which the link was selected by the user.

4.11. Validation/Verification

4.11.1. TO Validation Plan and Validation Sessions

The contractor shall develop and publish a Technical Order Validation Plan (TOVP) document to clearly detail the method to ensure each TO is converted to S1000D Data Modules with 100 percent accuracy. The TOVP shall be written in the contractor’s format and include the required data according to appropriate CDRL. The TOVP shall be delivered to the Government at least 20 business days prior to completion of any Data Modules. The Government shall review the TOVP and notify the contractor of any errors or acceptance. If errors are noted, the contractor shall correct and return the document to the government within 10 business days. In accordance with the TO Validation Plan, and TOs 00-5-1 and 00-5-3, the Contractor shall support the Government during a tabletop validation/verification (V/V) of the converted data. The agenda for V/V of the converted data should delineate the specific TOs that will be subject to V/V for each V/V session. The agenda shall be delivered to the Government at least ten business days prior to the planned sessions. The V/V sessions shall be planned and documented in the IMS to ensure the amount of material covered by each V/V session can be adequately performed within three business days. During the sessions, the contractor shall record thorough notes and document all issues for inclusion into the meeting minutes or action item listing. (CDRL A0XX DI-TMSS-81818 TM Validation Plan) (CDRL A0XX – DI-ADMN-81249B – Conference Agenda) (CDRL A0XX – DI-ADMN-81250B Conference Minutes)

4.11.2. Deployment Validation/Verification

The Contractor shall support and conduct up to four (4) trips of five (5) business days (includes travel days) each for V/V sessions for selected delivered systems data using the S1000D Live Content toolset at an AMC Lead Base. The agenda shall be delivered to the Government at least ten business days prior to the planned sessions. The purpose of the session is to verify usability prior to a system deployment decision and Government acceptance of the final deliverables. The deliverables shall be 100% accurate for content and meet all functionality matrix requirements. This delivered data/IETM capabilities will be representative of the actual production S1000D final

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to deliverable. During the sessions, the contractor shall record thorough notes and document all issues for inclusion into the meeting minutes or action item listing. (CDRL A0XX – DI-ADMN-81249B – Conference Agenda) (CDRL A0XX – DI-ADMN- 81250B Conference Minutes)

4.11.3. Familiarization Training Plan and Material

The Contractor shall provide a training plan and all necessary training material to support user familiarization training which will allow the Government to gain understanding of the usability, functionality, and technical content presentation of the IETM during V/V. The contractor shall provide the training materials to the government for future use. The Training Plan shall be delivered to the Government at least 20 business days prior to the beginning of training. The Government shall review the Plan and provide any corrections or comments to be incorporated. The contractor shall deliver the corrected version of the Plan within five (5) business days. The Contractor shall present familiarization training for 20 students on utilization of the content within the SDL LiveContent Viewer, and other required subjects necessary to enable utilization of the IETM within the viewer. (CDRL A0xx DI-MGMT-81955 Tech Training Plan, CDRL A013 DI-ILSS-80872 – Training Materials)

4.12. Final Deliverables

The final deliverables of the IETM will include the SNS/SSSN database, DMRL, BREX, Publication Module, Applicability Cross-reference Table, Conditions Cross-reference Table and Product Cross-reference Table, all data modules and graphics compliant with S1000D Issue 4.1, MIL-STD-3048B and project decision points, as well as the CSDB and on a DVD-ROM or similar device capable of storing all deliverables on a single device. The contractor shall prepare all XML IAW the tagging requirements of the Air Force Technical Order Authoring and Publishing (TOAP) “SGML Best Practices” guidelines. The contractor shall ensure tagging requirements are met to produce a specification compliant output within the TOAP system for all identified TOs.

The Contractor shall coordinate with the PM prior to determining a delivery storage media type to ensure compatibility with Government systems. The Contractor shall also deliver any software or materials purchased, procured, or developed, to include source code and documentation of developed products, in support this effort. The Contractor shall provide a final update to include new technical data and TCTO information within 30 calendar days of government acceptance of the final delivery. (CDRL B00X, TM- 86-01 Technical Manuals Contract Requirement (TMCR)

4.13. CONTRACT DATA REQUIREMENTS LIST(S) (CDRL)

CDRL DID Title PWS Reference

A00 DI-MGMT-

80269 Government Furnished Equipment Damage/ Loss

3.6

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to

Report

A00 DI-MGMT-

81797

Program Management Plan

4.1

A00 DI-MGMT-

81808

Risk Management Plan

4.2

A00 DI-MGMT-

81809

Risk Management Status Report

4.2

A00 DI-MGMT-

81650

Integrated Master Schedule

4.3

A00 DI-SESS-

80858C

Configuration Management

4.4

A00 DI-QCIC-81722 Quality Control Plan

4.5

A00 DI-ADMN-

81249B

Conference Agenda

4.6.1, 4.6.2, 4.6.3, 4.12.1,4.12.2

A00 DI-ADMN-

81250B

Conference Minutes

4.6.1, 4.6.2, 4.6.3, 4.12.1,4.12.2

A0 DI-MGMT-

80368A

Status Report 4.6.4

A0 DI-TMSS-81818 TM Validation Plan

4.12.1

A DI-MGMT-

81955

Tech Training Plan

4.12.3

A DI-ILSS-80872 Training Materials

4.12.3

A0 DI-MISC-81943 Trip Report 5.3 A DI-ENVR-81375 Environmental

Health/Safety 5.7.1

A0 DI-SAFT-81563 Accident/Inciden t Report 5.7.2

B0 TM-86-01 Technical Manuals Contract Requirement

(TMCR)

4.7,4.9,4.10, 4.14

4.14. Quality of CDRL Deliverable:

The Government will reject a deliverable if it does not meet the requirements identified in the DID, or if two (2) or more technical errors or three (3) or more minor errors are found within the deliverable. A technical error is defined as the format not being in

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to accordance with the DID or the content not being accurate and complete in accordance with the CDRL, DID, SOW, or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. There shall be no more than three (3) total rejection(s) of deliverables per Quarter. The contractor shall notify the TOMA and TCM of any existing errors to technical content identified during the conversion. The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of Government rejection.

4.15. Receipt of CDRL Deliverable:

The CDRL deliverables shall be submitted through the Government identified CM/DM system, to be determined at the start of the contract. There shall be no more than one (1) late submission(s) of deliverables per month. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

5. GENERAL INFORMATION

5.1. Continuation of Mission-Essential Services During a Crisis:

The Functional Commander or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2. Holidays and Facility Closings:

Contractor employees and sub-contractor employees are only permitted access to Government facilities when Government personnel are present. Therefore, Contractor/sub-contractor personnel shall observe holidays and facility closings as authorized for government personnel when work is normally performed at an Air Force facility.

5.3. Travel:

Travel requests for Contractor/sub-contractor personnel shall be submitted for approval to the Contracting Officer prior to costs being incurred and a minimum of 10 business days in advance of departure. All travel conducted by contract employees shall be in accordance with the Joint Travel Regulations (JTR). Receipts associated with travel shall be presented with the invoice for reimbursement of actual travel costs. Each traveler shall submit a travel report to the Government within five business days after conclusion of travel. (CDRL A0xx DI-MISC-81943 Trip Report)

5.4. Security Requirements:

5.4.1. Security Regulations:

The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure Contractor/sub-contractor personnel who perform work on a Government facility

Distribution Statement: DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative use. (5/14/2019). Other request for this document shall be referred to comply with the security requirements of the facility. The Contractor shall comply with the following security regulations: DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM); DoDD 5205.03 and DoD Operations Security (OPSEC) Program.

5.4.2. Operations Security (OPSEC):

The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall comply with DoDD 5205.03 to protect United States (U.S.) Government interests. The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

5.4.3. Communications Security (COMSEC):

The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with DoD 5220.22-M. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

5.4.4. Security Clearance:

There will be requirements for Contractor personnel to access classified data as part of this requirement.