RFP_Attch_5_Awardable Task.pdf
PDF 172 KB Posted
- Solicitation number
- FA8530-24-R-B001
About this file
This document is an Awardable Task under Request for Proposal (RFP) FA8530-24-R-B001 for the Technical Data Support Services Enterprise (TDSSe3) contract. It outlines the technical data support services required, including Technical Order (TO) management, editorial support, engineering data support, and technical content management support. The contractor will be required to provide a comprehensive proposal for the services detailed in the performance work statement, including their understanding of the work, proposed labor skills mix, and quality assurance processes. Key requirements include managing approximately 635 TOs, processing publication change requests, tracking and publishing TO updates, developing new TO numbers, and providing editorial and engineering data support services. The government will provide hardware, software, and funding for travel. Responses to this awardable task will be evaluated as part of the overall TDSSe3 contract solicitation, which is being competitively awarded within the 8(a) Small Business Development Program as an IDIQ contract with a 9-year period of performance.
View the file
Other files
Show all 49
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFP FA8530-24-R-B001 Attch_5_Awardable_Task
Awardable Task
1. 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.
2. REQUIREMENTS
TDSSe³ candidates will provide a written proposal for services outlined in section 4 of this document. Offeror will provide a comprehensive narrative that identifies their understanding of the work and outlines how their proposed solution will be implemented and managed with minimal government intervention. Offeror will provide their proposed labor skills mix and hours required to accomplish services effectively, efficiently, and successfully. Offeror will provide a detailed narrative of how and when they will apply technical quality assurance processes to meet
PWS technical content accuracy requirements.
3. ASSUMPTIONS/CLARIFICATIONS
Services will be predominately performed off-base. The government will provide computer hardware and software required to access government systems. Any travel associated with this effort will be fully funded by the government.
TDSSe candidates will assume responsibility for the interpretation of all information in the following paragraphs.
4. SERVICES
4.1 TECHNICAL ORDER MANAGEMENT AGENCY (TOMA) SUPPORT:
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 for Hanscom
AFB, MA. Support shall include the daily administration of requirements such as acquisition, sustainment, verification, reinstatement, content and format reviews, update, storage, and distribution of TOs and related technical data in accordance with duties outlined in AFPD 63-
1/AFPD 20-1, AFI 63-101/20-101 and associated military standards.
4.1.1.1 Approximately 25 percent (25%) of TOs do not currently adhere to Air Force TMSS.
They are maintained in various source data formats such as contractor customized SGML, unstructured FrameMaker files and editable/non-editable PDFs. Some TOs are rescinded and will require reactivation. Updates to non-compliant Air Force TMSS TOs will be brought up to the latest standards with content edits provided by the government as redlines.
4.1.2 The Contractor shall participate in weekly Multi-Functional Team (MFT) meetings (or as requested) to establish priorities and processes in support of TO management activities.
4.1.2.1 MFT meetings will be attended by Contractor leads in support of Program Office (PO) representative(s) and Contracting Officer Representative (COR).
4.1.3 The Contractor shall review approximately 132 approved Publication Change Request
(PCR) received from the Technical Content Manager/Equipment Specialist (TCM/ES) annually to determine if information provided is adequate and complete for incorporation into the TO. The
Contractor shall provide disposition and expected completion date to the PO on submitted PCRs within the timelines below. If conflicts occur, work priority decisions will be reviewed by COR during weekly meetings.
• 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, process, publish and distribute approximately 106 updates in ETIMs annually. For routine TCTOs, TO changes, revisions, and supplements, the following delivery requirements are established from Contractor receipt to final distribution:
• 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.4.1 The Contractor shall coordinate completed editorial packages with TCM for approval.
TCM approved editorial updates shall be posted to appropriate TO distribution systems for final disposition.
4.1.5 The Contractor shall manage and track approximately 20 Preliminary Technical Order
(PTO) change packages annually to support activities, such as equipment modifications and enhancements.
4.1.6 The Contractor shall develop on average 20 Contractor Furnished Equipment Notices
(CFEN) from gap analysis of commercial manuals and develop on average 10 COTS Identifying
Technical Publication Sheets (ITPS) annually, to include indexing, archiving, and distributing
COTS TOs IAW MIL-PRF-32216.
4.1.7 The Contractor shall establish on average 10 TO numbers for new TOs and assist with
30%/60%/90% In-Progress Reviews (IPRs) on newly developed TOs annually. IPRs may be performed via local tabletop review or as part of an on-site verification team.
• Contractor shall document and coordinate findings, on an AFTO Form 158, within 30 calendar days from receipt or time of verification.
4.1.8 The Contractor shall be responsible for maintaining configuration control of data residing in TO management 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.
4.1.8.1 The Contractor shall act as the Weapon System TOMA in all TO systems and maintain continuous coordination, communication, and agreement with the Program Office on precedence and prioritization of system requirements.
4.1.8.2 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.9 The Contractor shall evaluate TO health and recommend priority to convert TOs that would enhance readability and sustainability. Contractor shall convert TOs based on agreed prioritization to meet any gaps in annual editorial production requirements. PCR package production will take precedence over conversion efforts.
4.1.10 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 annually.
4.1.11 The Contractor shall be required to review and determine disposition of on average 30 sponsor approvals monthly. 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.12 The Contractor shall be responsible for creating and coordinating new TO contract documents 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.13 The Contractor shall provide Quality Assurance (QA) support for TO updates and new
TOs. Contract QA will perform 100% quality assurance inspection of all updated and new documents to ensure content and format accuracy prior to final publishing. Technical manual pages/documents produced shall meet requirements for 100% content accuracy.
4.1.14 The Contractor shall be responsible for coordinating and reporting monthly quality assurance activities to the COR, 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 unclassified Air Force TOs in TOAP and in accordance with Department of Defense (DoD) and Air Force TMSS standards.
4.2.2 Contractor shall be responsible for maintaining skilled personnel that can support all editorial functions and average monthly work quantities. Editorial source data quality, work complexity, type, and government priorities may fluctuate from day-to-day. Contractor shall ensure PO is informed of all impediments to production in a timely manner.
4.2.3 The Contractor shall establish weekly cadenced meetings with TCM, PO and COR to review and prioritize current and incoming editorial workload. The Contractor shall document resulting priority and process decision in accordance with applicable CDRL.
4.2.4 The Contractor shall complete on average 1,000 unclassified TO sustainment supplements, changes, revisions/conversions or TCTO pages monthly based on priorities established during weekly cadenced meetings. The estimated average workload per year is 30% illustration and
20% text as follows:
• Annual Editorial Production Pages: 12,000 o Routine PCR Packages: 65 o Urgent PCR Packages: 10 o Emergency PCR Packages: 5 o TCTOs/Supplements: 30 o Conversions/Revisions: 26
NOTE: An estimated 20% of pages worked will require illustration updates from bitmap to vector format.
4.2.5 The Contractor shall evaluate TO health 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.6 The following delivery requirements are established from Contractor receipt of editorial package, for routine TCTOs, TO changes, revisions, and supplements, to delivery for TOMA
Final QA.
• 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 meetings
4.2.7 The Contractor shall maintain the following quality assurance standards throughout the editorial support activity:
• Shall not have more than five minor errors per 100 pages (minor errors on no more than
5% of total page)
• Individual editorial packages shall not be rejected more than two times
• Editorial packages rejected shall be corrected within seven calendar days of notification
4.2.8 TO Editorial status, production and quality metrics shall be reported monthly in accordance with applicable CDRL.
4.3 ENGINEERING DATA SUPPORT
4.3.1 The contractor shall provide engineering data support for the creation, modification, conversion, validation, and management of engineering design data and associated lists in accordance with applicable Government and Industry standards.
4.3.2 The contractor shall review and perform quality assurance procedures on all received/delivered data to ensure data integrity is verified and maintained prior to delivery and/or uploading to associated system.
4.3.3 The contractor shall be skilled in 2-dimensional (2D) and 3-dimensional (3D) computer aided design (CAD) software such as AutoCAD, Inventor, NX, CATIA, CREO, and Solidworks to enable effective creation, modification, and management of engineering data.
4.3.3.1 The contractor shall be responsible for the quality inspection of drawings, models, metadata, associated documents/lists, including Technical Data Packages (TDPs). Contractor shall validate the accuracy of all data and metadata as required to accurately upload into the appropriate engineering data repository.
4.3.4 The contractor shall be responsible for the review, coordination, validation, and implementation of approximately 450 design/drafting service requests annually. Service request will be annotated using government approved AFMC Form 199s and processed in accordance with AFMCI 21-401.
4.3.4.1 The contractor shall convert an estimated 250 legacy 2D TDPs to 3D TDPs as designated by AFMC Form 199s. The contractor shall create and deliver a fully defined product level 3D
TDP which shall contain fully annotated 3D Model Based Definition (MBD) digital models, including dimensions, tolerances, materials, finishes and other notes to specify a complete product definition as defined in ASME Y14.41 and in accordance with DI-SESS-82351A.
4.3.4.2 The contractor shall create approximately 150 2D TDPs and 50 3D TDPs annually from government approved source data via approved AFMC Form 199s. All 2D and 3D TDPs shall be created in accordance with MIL-STD-31000 and DI-SESS-82351A. The contractor shall include
3-Dimensional Intelligent (3Di) PDFs as identified. 3D TDPs generated from Form 199s are separate from those generated as part of the conversion process.
4.3.5 The contractor shall support the Engineering Order (EO) process in accordance with
AFMCI 21-401, ensuring proper documentation management and data validation. The contractor shall implement approximately 500 EOs annually within the following schedule.
• Routine updates will be accomplished in 30 days from receipt of EO.
• Urgent updates will be accomplished in 10 days from receipt of EO.
• Emergency updates will be accomplished in 5 days from receipt of EO.
4.3.5.1 The contractor shall create and/or update approximately 200 3D model-based definition
(MBD) models annually from EOs. 3D MBD models shall be created in accordance with ASME
Y14.41, ASME Y14.47, and MIL-STD-31000. Only one native 3D MBD model shall define a given product, and all native 3D MBD models shall be monodetail, legible, and fully text searchable. 3D MBD model complexity will vary and will be submitted at various hierarchical levels.
4.3.5.2 The contractor shall create and/or update approximately 300 2D drawings and associated lists annually, in accordance with ASME Y14.100, including appendices B through E. Geometric
Dimensioning and Tolerancing (GD&T) definitions shall be in accordance with ASME Y14.5.
4.3.10 Contractor shall have a thorough understanding of how to store, index and manage engineering data within an Air Force owned Teamcenter Product Lifecycle Management (PLM) environment. The contractor shall export model/technical data from PLM, including but not limited to requirements, design, production, test, and sustainment information in a format compatible with Teamcenter as requested.
4.3.11 Contractor shall ensure all types and formats of engineering data display the appropriate distribution statement in accordance with DoDI 5230.24 to indicate controlling DoD office and the pre-approved secondary distribution. The distribution statement shall be displayed on the cover, title page, and all pages or digital displays to the maximum extent.
4.3.12 The contractor shall ensure all engineering and technical data is marked, maintained, stored, distributed, and managed in accordance with applicable policy including MIL-STD-130 and DoDI 5200.48.
4.4 TECHNICAL CONTENT MANAGEMENT SUPPORT
4.4.1 Contractor shall provide TCM support and assist Government TCM functions with processing and coordination of TO updates.
4.4.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.4.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.4.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 activities.
4.4.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-1, 00-5-3, and program guidelines.
4.4.6 The Contractor shall review and assess an estimated 20 newly developed TOs annually 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.4.7 The Contractor shall review and recommend disposition of approximately 30 sponsor approvals monthly in support of TOMA requirements.
4.4.8 The Contractor shall review and develop Publication Change Requests (PCRs) such as
ETIMS-Generated Special Handling 252s, AFTO Form 158s, Engineering Change Orders
(ECO), and TCTOs, for approval by engineering office or designated content manager. The estimated average workload per year, is as follows:
• Annual Recommended Changes: 80 o Routine: 65 / Urgent: 10 / Emergency: 5
• TCTOs/Supplements: 30
• Conversions/Revisions: 26
4.4.9 Contractor shall coordinate disposition recommendation(s) with responsible engineering office or designated content managers.
4.4.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.4.11 Upon return of corrective action, such as TO change, supplement, revision or TCTO, the
Contractor shall review technical source data, such as PCRs, Discrepancy Reports (DR), 252s, TCTO Forms and ECOs to ensure changes incorporated into TOs and drawings are 100% technically accurate.
• Final disposition shall be accomplished within 10 business days from date of receipt.
4.4.12 The Contractor shall be responsible for coordinating and reporting monthly activities to the COR, to include identification of trends associated with document quality problems and services/actions required to mitigate problems identified.
File details come from the government source that posted it. Updated .