Appendix_F__-_CLIN_0001_Tasks.pdf

APPENDIX F

Anticipated Year 1 Tasks under CLIN 0001

IAW PWS paragraphs 3.2.1.1 – 3.2.1.8

PWS Paragraph 3.2.1.1 – Analysis of new TO mandates The Government does not expect any Technical Order driven mandates for year one.

PWS Paragraph 3.2.1.2 – Engineering and Logistics Support The Government expects the following task:

Distribution Server : The Contractor shall develop or utilize a commercial off the shelf product which allows the Government and Contractor to submit large amounts of data through a secure means. The correspondence going back and forth can include AFTO 252 TO changes, final products, and BCU updates. The distribution server shall allow for electronically sent data packages to be sent to and from the Government and Contractor team. This is a one-time effort, but may require upkeep to ensure the server is working properly.

PWS Paragraph 3.2.1.3 – Technical Support Required for Technical Order Improvement Projects The Government expects the following tasks:

Intelligent Wire Development: The Contractor shall develop interactive graphics files in support of intelligent wire/signal tracing products derived from existing A-10 technical order wiring schematics included in 1A-10C-2-110-1 and 1A-10C-2-110-1-1. Functionality will be IAW S1000DIss4. This task shall be a phased approach, potentially 3-4 phases throughout the life of the contract.

Moving Baseline Electronic Technical Order Repository: The Contractor shall design, develop and deliver an Electronic Technical Order Repository for the A-10 program. The Government has a need for 1) a centrally managed repository that supports preliminary TO review by stakeholders impacted by future modification and sustaining schedules and 2) an automated system that enables the Government to assign and de-conflict change assignment by TOs in real time to reflect modification and sustainment Block Cycle Release schedule changes. As part of this effort, the Contractor shall develop a formal requirements document for Government approval. The system will be Government owned. Top level requirements include the following:

Access controls inclusive of Government and contractor access with Government-required approval; computing security controls; version management that allows the Government to schedule and reserve future TO change releases to individual modification programs;

configuration change management to support published, working, and reserved TO change assignments; check-in/check-out capability for changes published and in-work; redline markup interchange capability for working TO changes. The Government's permissions will include the ability to assign and reserve TO changes; modify change level assignments to reflect modification and sustainment schedule changes; grant or remove user access. (One time occurrence)

PWS Paragraph 3.2.1.4 – Trade Studies The Government expects the following task:

V8a DTD Upgrade Study: The Contractor shall perform impact analysis of migrating the existing published baseline to the BV8 DTDs. The current A-10C Technical Orders are published using Standard Generalized Markup Language (SGML) Document Type Definitions (DTDs) based on

38784STD-BV6 specification. The analysis should include a cost/benefit analysis to migrate from the existing published A-10 TO baseline, inclusive of transformation costs, distribution costs, and sustainment cost impacts. (One time occurrence)

PWS Paragraph 3.2.1.5 – Technology Roadmaps The Government does not plan to utilize this task for year one.

PWS Paragraph 3.2.1.6 – Data and Software Analysis The Government expects to use this task two times in year one. The Contractor shall provide engineering and design expertise in supporting USAF TMSS implementations, and shall provide recommendations on A-10 TMSS use cases representing Air Force interests. The Contractor will provide data and software analysis associated with PWS technical elements including document type definition (DTD) analysis, formatted output specification instance (FOSI) analysis, schema analysis, and GFI eTO software analysis. Design data and calculations used for software analysis shall be documented and provided to the Government.

PWS Paragraph 3.2.1.7 – Familiarization The Government expects to use this task twice in year one to train the Government on the two (2) improvement projects.

PWS Paragraph 3.2.1.8 – Source Data Review The Government expects to use this task five times in year one. The Contractor shall assess the source data provided in support of A-10 aircraft modifications for technical accuracy, engineering completeness, schedule viability, and specification conformance. Schedule viability will be assessed against the publishing schedule (Integrated Master Plan), required reviews, and the associated modification schedule. Engineering completeness will be assessed on the source data against the anticipated operation and modification concept for the fielded TOs. The Contractor will prepare a report to the TOMA either identifying adequacy or identifying concerns with quality of the package including itemized deficiencies.