Attach_5-_Awardable_Task.docx

RFP FA8530-19-R-0001, Attch 5

Awardable Task

SCOPE

This sample awardable task provides an outline of technical data support services via a sample task order Performance Work Statement (PWS) similar to those that will be initiated at the task order level. Awardable task proposal is to be in accordance with the basic contract PWS and all applicable regulations, specifications and standards.

Requirements TDSSe candidates will provide a written proposal for services outlined in section 4 of this document. Offeror shall provide a comprehensive proposal response that identifies their understanding and outlines how a proposed solution will be implemented, and managed with minimal government intervention. Offeror will provide an appropriate labor skills mix and hours required to effectively and efficiently accomplish services. Offeror will provide a detailed technical quality assurance process

ASSUMPTIONS/CLARIFICATIONS

The government will provide work space, computer hardware, and software required for performance of services. There will be no travel or material cost associated with this effort.

Candidate will assume responsibility for the interpretation of materials that are not clear or legible and where no clarification has been provided. Clarification, of any type, should be assumed by the TDSSe² candidate and the package should be completed with the information given.

Outline of Services (Sample PWS)

4.1 TECHNICAL ORDER MANAGEMENT AGENCY SUPPORT (TOMA):

4.1.1 The Contractor shall provide TOMA support for approximately 635 Technical Orders (TO) (Approximately 130K pages) in multiple media formats and stages of development. Support shall include the daily administration of requirements such as acquisition, sustainment, verification, reinstatement, content and format reviews, storage and distribution of TOs and related technical data in accordance with duties outlined in AFPD 63-1/AFPD 20-1, AFI 63-101, and 00-5-series TOs.

Approximately 5 percent (5%) of TOs do not currently adhere to Air Force TMSS. They are maintained in various source data formats such to include contractor customized SGML, unstructured FrameMaker files and editable/non-editable PDFs. Some TOs are rescinded and will require reactivation/updates be accomplished through TO redlines.

4.1.2 The Contractor shall participate in Multi-Functional Team (MFT) meetings (as required) to establish priorities and processes in support of TO management activities.

Note: MFT meetings will be attended by Robins AFB Program Office (PO) representative(s), the Contracting Officer Representative (COR), and Contractor leads from each functional area.

4.1.3 The Contractor shall review approved Publication Change Request received from the Technical Content Manager (TCM) to determine if information provided is adequate and complete for incorporation into the TO. The Contractor shall provide disposition and expected completion date to Robins AFB PO on submitted PCRs. If conflicts occur, work priority decisions will be reviewed by COR.

· Routine PCRs shall be dispositioned within 3 business day of receipt.

· Urgent PCRs shall be dispositioned within 1 business day of receipt.

· Emergency PCRs shall be dispositioned 1 calendar day of receipt.

4.1.4 The Contractor shall track, manage, and process receipt of AFTO 22s/252s for routine TCTOs, TO changes, revisions, and supplements until publication. The following delivery requirements are established from Contractor receipt:

· 50 pages or less – NLT 45 business days (9 weeks) from date of receipt

· 51 – 100 pages – NLT 65 business days (10 weeks) from date of receipt

· 101 – 350 pages – NLT 75 business days (12 weeks) from date of receipt

· 351 pages or more – as agreed upon during weekly meeting NOTE: Government process times will not be included in required contractor process times.

4.1.5 The Contractor shall assemble source information into data packages and submit to editorial support for all approved PCRs.

· On average, 106 Source Data Packages will be submitted for TO updates each year.

4.1.6 The Contractor shall review and coordinate completed editorial packages with TCM for approval. TCM approved editorial updates shall be posted to appropriate TO distribution systems within 2 business days of final disposition.

4.1.7 The Contractor shall manage and track the preliminary change packages for Preliminary Technical Order (PTO) Change Packages required to support activities, such as equipment modifications and enhancements.

4.1.8 The Contractor shall establish Contractor Furnished Equipment Notices (CFEN) on average 20 contractor developed manuals for gap analysis and develop on an average 10 COTS Identifying Technical Publication Sheets (ITPS), index, archive, and distribute COTS TOs IAW MIL-PRF-32216, supplementing as required.

4.1.9 The Contractor shall establish on average 10 TO numbers for new TOs and assist with an estimated 30 30%/60%/90% In-Progress Reviews (IPRs) on newly developed TOs annually. IPRs may be performed via local table top review or as part of an on-site verification team.

· Contractor shall document and coordinate finding, on an AFTO Form 158, within 30 calendar days from receipt or time of verification.

4.1.10 The Contractor shall transition TOs into Air Force TO content management, archive and distribution systems as part of the TO update process when TO does not adhere to current military style and format. TOs shall be converted, updated and sustained within Technical Order Authoring and Publishing System (TOAP), indexed and managed in Enhanced Technical Information Management System (ETIMS), archived in Central Technical Order Repository (CTOR) and printed via Technical Order Distribute and Gateway (TODPG).

4.1.11 The Contractor shall be responsible for maintaining configuration control of data residing in TO management systems such as, but not limited to ETIMS, TODPG, and/or other systems utilized by the Government for the configuration management and sustainment of TOs. The Contractor shall populate TO management systems/metadata for TOs not yet indexed and update each time a publication review is accomplished.

a) The Contractor shall act as the WS TOMA in all TO systems and maintain continuous coordination, communication and agreement with the Robins AFB PO on precedence and prioritization of system requirements.

b) The Contractor shall establish and index TO numbers for all TOs supported within this PWS. Newly indexed TOs shall be coordinated with Robins AFB PO so users can establish initial distribution requirements.

c) The Contractor shall maintain a ninety-nine percent (99%) data accuracy rate within all TO management systems. Errors identified shall be corrected within 1 business day of identification.

4.1.12 The Contractor shall establish and index TO numbers for all TOs supported within this PWS. Newly indexed TOs shall be coordinated with Robins AFB PO so users can establish initial distribution requirements.

NOTE: Approximately 2% TOs are un-numbered and some paper distribution TOs are not indexed.

4.1.13 The Contractor shall provide system user subject matter expert support for technical data management systems. This function may operate as a help desk, assisting users with indexing and distribution of technical data, workflow management, as well as notifying users of system issues, and assisting users as required to meet their mission needs. The Contractor shall also provide or assist with training for functional system users. The Contractor shall also support resolution of TO process deficiencies as identified by TO program metrics and policy evaluations such as those generated by DDRs.

4.1.14 The Contractor shall assist TODOs and TODAs with the establishment of accounts as TOs are transitioned and distributed within TO sustainment systems. Contractor shall assist TODO and TODA personnel with questions, identify training and administrative requirements to establish account as well as assist with meeting requirements outlined in TO 00-5-1. The Government estimates that 10 new TODO/TODA accounts will be established quarterly.

4.1.15 Distribution encompasses publication and deployment of approved TOs for specific systems or commodities.

NOTE: The assigned TOMA will complete distribution for TOs published in WA only format.

· TO Initial Distribution (ID) Packages Submitted for Distribution: 75 monthly

· All routine approved PCRs shall be incorporated into the TO and the updates submitted to distribution function within 275 calendar days of ES Supervisor approval and TOMA start time.

· Urgent, Emergency, and Special Handling timelines are defined in TO 00-5-1 and TO 00-5-3.

4.1.16 The Contractor shall be required to review and determine disposition of sponsor approvals. Sponsor approval shall be coordinated with TCM for approval. Contractor shall approve or reject sponsor approvals within 7 business days of request. The Contractor shall approve or reject emergency requisition sponsor approvals within two (2) business days of receipt.

4.1.17 The Contractor shall be responsible for creating and coordinating TO management documentation such as Technical Manual Contract Requirements (TMCR), Preliminary Technical Order (PTO) waiver letters, TMSS Data Item Descriptions (DID), Technical Order Life Cycle Management Plan (TOLCMP), Technical Order Life Cycle Verification Plan (TOLCVP).

4.1.18 The Contractor shall review TO policy documents such as TO 00-5-1, TO 00-5-3, and TO 00-5-15 to ensure the sustainment and management of supported TOs are in compliance. Contractor shall provide recommendations to program on any policy changes and include anticipated impacts and recommended solutions.

4.1.19 The Contractor’s processes and products shall comply with AFI 90-201, The Air Force Inspection System and Standardized Air Force Self-Assessment/ Unit Effectiveness Inspection (UEI) checklist, the Management Internal Control Toolset (MICT) and applicable Air Force policy.

4.1.20 The Contractor shall provide Quality Assurance (QA) support for TO updates. Contract QA will perform 100% quality assurance inspection of new documents to ensure content and format accuracy. Technical manual pages/documents produced shall meet requirements for 100% content accuracy.

· Identified discrepancies shall be annotated on an AFTO Form 158, uploaded to a working level information system (i.e. Contenta) and returned to the Editorial source for correction. A copy of the AFTO Form 158 shall be provided to Government when the TO is delivered.

· The Contractor shall be responsible for coordinating and reporting of quality assurance activities to the COR for the TO management organization, to include identification of trends associated with document quality problems and services/actions required to mitigate problems identified.

4.2 EDITORIAL SUPPORT

4.2.1 Editorial management services shall include developing, editing, composing, illustrating, converting and performing quality assurance of classified and unclassified Air Force TOs in TOAP and in accordance with Department of Defense (DoD) and Air Force TMSS standards.

4.2.2 With concurrence from the Robins AFB PO or COR, the Contractor may maintain current style and format when processing PCRs on TOs, that have not been converted into a sustainable MIL-STD format, in order to meet contractual timelines.

4.2.3 Contractor shall be responsible for maintaining skilled personnel to support all editorial functions identified within this PWS. Average monthly work quantities, editorial source data quality as well as work complexity, type and priorities may fluctuate from day-to-day. Contractor shall ensure that government editorial representative is informed of all impediments to production in a timely manner.

4.2.4 The Contractor shall establish weekly cadenced meetings with TCM, Robins AFB PO and COR to review and prioritize current and incoming workload. The Contractor shall document resulting priority and process decision in accordance with CDRL A007, DI-ADMN-81505

4.2.5 The Contractor shall complete on average 1,000 classified and unclassified TO sustainment supplements, changes, revisions/conversion or TCTO pages monthly based on priorities established during weekly cadenced meetings. The estimated average workload per year, based on historical changes, is as follows:

Annual Editorial Production Pages: 12,000

· Routine PCR Packages: 87

· Avg. Pages Changed/Package: 20

· Urgent PCR Packages: 12

· Avg. Pages Changed/Package: 10

· Emergency PCR Packages: 7

· Avg. Pages Changed/Package: 4

· TCTOs/Supplements: 30

NOTE: An estimated 20% of pages worked will require illustration updates (in .tif file format).

Table- 3 and Table-4 below provide a program level breakdown of anticipated annual work quantities for routine, urgent, and emergency PCRs:

Table-3 Routine PCRs

System

Routine PCR Packages Routine Avg. Pages Changed/Package:

TCTOs/ Supplements

Table-4 Urgent/Emergency PCRs

System

Avg. Pages Changed/Package:

Emg PCR Packages Emg Avg. Pages Changed/Package:

4.2.6 The Contractor shall develop preliminary change packages to establish Preliminary Technical Order (PTO) Change Packages required to support activities, such as equipment modifications, enhancements, test and evaluations.

4.2.7 The Contractor shall evaluate and recommend priority to convert TOs that have not been converted, into a sustainable MIL-STD format within TOAP. Contractor shall convert TOs based on agreed prioritization to meet annual editorial production requirements. PCR package production will take precedence over conversion efforts.

4.2.8 The following delivery requirements are established from Contractor receipt of PCR for routine TCTOs, TO changes, revisions, and supplements.

· 50 pages or less – NLT 25 business days (5 weeks) from date of receipt

· 51 – 100 pages – NLT 35 business days (7 weeks) from date of receipt

· 101 – 350 pages – NLT 45 business days (9 weeks) from date of receipt

· 351 pages or more – as agreed upon during weekly meeting

4.2.9 The following delivery requirements are established by Contractor receipt of PCR for urgent and emergency TCTOs, TO changes, revisions, and supplements:

· Urgent PCRs – NLT 10 business days from receipt for less than 100 pages and NLT 15 business days of receipt for 101 or more pages

· Emergency PCRs – NLT 24 hours from receipt

· Emergency (work stoppage) - NLT two business days from receipt

4.2.10 The Contractor shall maintain the following quality assurance standards throughout the editorial support activity:

· Shall not have more than five errors per 100 pages

· Individual editorial packages shall not be rejected more than two times

· Editorial packages rejected by the customer shall be corrected within seven calendar days of notification

4.2.11 TO Editorial status, production and quality metrics shall be reported monthly in accordance with CDRL A002, DI-MGMT-80368A.

4.3 TECHNICAL CONTENT MANAGEMENT SUPPORT

4.3.1 Contractor shall provide TCM support and assist Government TCM functions with processing and coordination of TO updates. This support will reside within the Robins Air Force Base PO.

4.3.2 Contractor shall provide TCM support to ensure accuracy, adequacy, and classification of TO procedures, source data, engineering data and related technical content as outlined in TO 00-5-1, TO 00-5-3, TO 00-5-15 and AFI 63-101.

4.3.3 Contractor shall be proficient in their ability to manage technical data TCM processes and responsibilities as it applies to modifying and interpreting TOs, validating and verifying TOs/TCTOs, and incorporating TCTO data into applicable TOs and drawings.

4.3.4 Contractor shall provide TO content analysis and assessment of all content to ensure sustainment weapon system baseline infrastructure is accurately reflected. This assessment shall include all acquisition, modification, verification and sustainment TO activity.

4.3.5 Contractor shall ensure Scientific and Technical Information (STINFO) is applied in accordance with program security classification guidelines and all content is adjudicated and coordinated with the Foreign Disclosure Office (FDO), as required IAW 00-5-3 and program guidelines.

4.3.6 The Contractor shall review and assess newly developed TOs to ensure OSS&E compliance. The Contractor shall provide a recommended data content approach to the Government to ensure the accuracy of data is achieved. Development of new TOs require a 30/60/90 government process timeline establishing 30% as the outline, 60% with 75% content and 90% with 100% content of the TO. The Contractor shall coordinate (with TOMA), review and adjudicate any submittals in support of new development and/or content within 30 business days from receipt. Findings and recommendations shall be documented and presented to the appropriate engineering authority with recommendation for approval or disapproval.

4.3.7 The Contractor shall review and determination of disposition of sponsor approvals in support of TOMA requirements within this PWS.

4.3.8 The Contractor shall review AFTO Form 22s and develop Publication Change Request (PCRs) such as, AFTO 252s, AFTO 158s, ECOs, and TCTOs for approval by engineering office or designated content manager. The estimated average workload per year, based on historical changes, is as follows:

• Annual AFTO 22/252ss reviewed: 106

· Routine: 87 / Urgent: 12 / Emergency: 7

• Annual AFTO 22/252s pages referenced: 311

· Routine: 269 / Urgent: 32 / Emergency: 10

• Annual PCR pages updated: 705

· Routine: 576 / Urgent: 116 / Emergency: 13

4.3.9 Contractor shall coordinate recommendation(s) with responsible engineering office or designated content managers for disposition based on the following deliver requirements.

· Routine AFTO 252s: 5 business days from date of receipt

· Urgent AFTO 252s: 2 business days from date of receipt

· Emergency AFTO 252s: NLT 24 hours from receipt

4.3.10 Upon final determination of PCRs from the appropriate engineering authority the Contractor shall initiate necessary TO update actions, within 3 business days, to TOMA for correction of content deficiencies.

4.3.11 Upon return of corrective action, such as TO change, supplement, revision or TCTO. The Contractor shall review technical source data, such as AFTO Form 22s, Discrepancy Reports (DR), AFTO Form 252s, TCTO Forms and Engineering Change Orders (ECOs) to ensure changes incorporated into TOs and drawings are 100% technically accurate.

· Final disposition of change shall be accomplished within 10 business days from date of receipt.

4.4 Technical Order Library Support

4.4.1 The Contractor shall be responsible for posting all TOs within five (5) workdays from date received by the library custodian as specified in TO 00-5-1. Routine posting errors shall not exceed 5% per month and errors shall be corrected within three (3) working days of discovery. The organization library custodian responsible for posting changes to technical data shall publish and provide a list of changes by location, TO number, and quantity of copies to the Contracting Officer's Representative (COR) for monitoring purposes every seven (7) calendar days.

· Average total paper TO inventory for library and satellites: 80

· Average total Digital (WA) TO inventory for library and satellites: 120

· Average changes, sups WA monthly: 20

· Average number of changes, supplements, TCTOs, revisions, and new TOs received monthly for library and satellites: 10

4.5 Interactive Electronic Technical Manuals (IETM) Support:

4.5.1 The Contractor shall be required to integrate TMSS compliant legacy technical data into a TMSS compliant S1000D IETM. The Contractor shall integrate pre-approved TMSS compliant SGML/XML data IAW MIL-STD-3048 and convert graphics from existing source format to CGM. Procedural steps within graphics will be mapped to S1000D MIL-STD-3048. All data, current and any changes, must be in S1000D MIL-STD-3048 format. The Contractor shall provide a spreadsheet for government review containing the TO Number and/or Data Module Code, System, Subsystem, Sub-Sub System when integrating new data. This spreadsheet will contain the TO Number and/or Data Module Code, the procedure location within said TO and what System, Sub-System, Sub-Sub System that procedure will go to within the Mil-Std-3048. The Contractor must provide a complete and accurate traceability matrix of all data integrated into S1000D as it relates back to the original source documents utilized.

4.5.2 The Contractor shall integrate two SGML-based, PDF output TOs into an existing S1000D data set. The two TOs contain approximately 350 total pages of which 15% are .tif format illustrations.

· Contractor shall deliver data files in TMSS compliant XML S1000D Data Modules

· Contractor shall deliver illustration files in TMSS compliant CGM 4.0 or higher

· Contractor shall support a Government led tabletop verification of the integrated data to ensure that all data is converted from the original source data into MIL-STD-3048 compliant S1000D data modules

· Contractor shall provide data that is compliant with the SDL Live Content Toolset

· Contractor shall distribute an updated and field ready S1000D dataset that includes all newly incorporated technical data and the most current TCTO information within 15 days of Government acceptance

S100D IETM data integration Data Modules

Monthly Routine Updates