Performance_Work_Statement___Fuel_Vent_Control_Valve.pdf
PDF 686 KB Posted
- Attached to
- Engineering Services
- Solicitation number
- FA8118-19-R-0049
About this file
PWS
View the file
Other files
| File | Type | Posted |
|---|---|---|
| J&A_Redacted.pdf | ||
| FA8118-19-R-0049.pdf | ||
| Contract_Data_Requirements_List.pdf | ||
| DIDs_Package_(12_total).pdf |
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
UNCLASSIFIED
Performance Work Statement (PWS)
In Support of: Consolidated Sustainment Activity Group (CSAG) Engineering Assignment
423 SCMS Commodities/Aircraft Technical Services (CATS) Consolidated Sustainment Activity Group (CSAG) Engineering Assignment for B-2 Fuel Vent Valve
Phase I, Obsolescence Solution Analysis
NSN: 4810-01-380-9046
P/N: 2880001-105
Prepared by:
Ms. Dena Jenkins
423 SCMS/GUEA
Tinker AFB, OK 73145
28 SEP 2018
Revision History
Revision Date POC Summary of Changes
- 28 SEP 2018 Dena Jenkins Initial release of document.
Table of Contents
1 INTRODUCTION
1.1 Purpose
1.2 Scope
1.3 Background
2 REFERENCE DOCUMENTS
2.1 Government Documents
2.2 Other Documents
3 CONTRACTOR TASKING / REQUIREMENTS
3.1 Program Management
3.1.1 Monthly Status Report
3.1.2 Program Management Review
3.1.3 Technical Interchange Meeting
3.1.4 Integrated Master Schedule
3.1.5 Contract Closure Letter
3.2 Baseline Configuration Identification
3.2.1 Project Kickoff Meeting
3.2.2 Program Management Plan
3.2.3 Reliability/Maintainability Program Plans
3.2.4 Counterfeit Prevention Plan
3.2.5 Lead-Free Control
Lead-Free Control Plan
Lead-Free Electronics Risk Management
Lead-Free Configuration Management
Manufacturing Processes
Lead-Free Electronics Program Management
3.2.6 Baseline Configuration Identification Report
3.3 Parts Obsolescence Assessment
3.3.1 Parts Obsolescence Report
3.3.2 Piece Part Testing
3.3.3 Analysis of Alternatives
3.4 Obsolescence Solution
3.4.1 Obsolescence Solution Report
3.4.2 Procurement Specification Update
3.4.3 Test and Evaluation Program Plan
3.4.4 System Requirements Technical Interchange Meeting
3.4.5 Updated Technical Data Package
3.4.6 Follow-on Cost Estimate
4 PERIOD OF PERFORMANCE AND DELIVERY SCHEDULE
4.1 Period of Performance
4.2 Delivery Schedule for Contract Data Requirements Lists
5 SPECIAL CONSIDERATIONS
5.1 Data Marking
5.1.1 Asserted Rights in Technical Data
5.1.2 Removal of Unjustified and Nonconforming Markings
5.1.3 Distribution Code
5.1.4 Export Control Warning Label
5.1.5 Destruction Notice for Unclassified Documents
5.1.6 Classification
5.1.7 General Marking Guidance, DFARS 252.227.7013(f)
5.2 Security
5.2.1 Safeguarding of Unclassified Controlled Technical Information
5.2.2 Release or Removal of Information
5.2.3 Access to Confidential, Proprietary and/or Sensitive Information
5.2.4 Security Clearance
5.2.5 Common Access Cards
5.2.6 Base or Area Badges and Access to Facilities
5.2.7 Standards of Conduct
5.3 Government Furnished Equipment, Materials, Property and Software
5.4 Software
5.5 Base Support - Government Provided Office Space
5.6 Government Program and Contract Management
5.6.1 Government Program Management
5.6.2 Government Contract Management
5.7 Safety Requirements
5.7.1 Safety Standards
5.7.2 Damage to Government Property and/or Base Support
5.7.3 Major Mishap
5.7.4 Investigation
6 TRAVEL REQUIREMENTS
6.1 Travel Anticipated
6.2 Travel Pre-Approval
6.3 Travel Expenses
6.4 Post-Trip Report
7 SERVICES SUMMARY
8 CONTRACTING OFFICER REPRESENTATIVE
9 CONTINUATION OF ESSENTIAL SERVICES DURING CRISIS
10 IAW DFARS 252.237-7023, this requirement is not considered mission essential
ABBREVIATIONS, ACRONYMS, AND INITIALISMS
List of Attachments Attachment I – TDP Option Select Worksheet Attachment II – Nondisclosure Agreement Attachment III – Common Access Cards (CAC) Listing For Contractor Personnel
List of Tables Table 2-1: Government Document References Table 2-2: Other Document References Table 4-1: CDRL Schedule Table 7-1: Performance Objectives and Thresholds ................... Error! Bookmark not defined.
Table 11-1: Abbreviations, Acronyms, and Initialisms
1 INTRODUCTION
1.1 Purpose
The purpose of this Performance Work Statement (PWS) is to identify piece part obsolescence within the latest configuration of the B-2 Fuel Vent Valve, herein referred to as the Fuel Vent, determine a detailed solution for each obsolete part, complete testing of piece part solutions and establish qualification requirements concurrence across the B-2 enterprise. This analysis and associated solutions will be used as the basis for a follow on buy with Non-Recurring Engineering (NRE) contract that will execute the qualification plan to fully qualify the obsolescence solutions and then deliver the required spares.
1.2 Scope
This PWS is designed to determine the obsolescence resolutions necessary for full supportability of the Fuel Vent. The scope of this engineering assignment includes identification of the full Bill of Material (BOM), support equipment, and documentation needed to produce additional spare Fuel Vent. It includes identification of piece parts obsolescence and projected near-term obsolescence, clarification of applicable qualification requirements (e.g., TEMPEST, Cyber Security, etc.), analysis of specifications revision applicability, development of a revised a procurement specification (P-Spec) if needed, and a solution for each obsolete part or next higher assembly. The scope also includes Analysis of Alternatives (AoA) meeting, follow on buy with an NRE cost estimation, Parts Testing, a Test and Evaluation Program Plan (TEPP), System Requirements Technical Interchange Meeting (TIM), a Program Management Plan (PMP) inclusive of Integrated Master Schedule (IMS), and a draft Technical Data Package (TDP). A Kickoff Meeting and a quarterly Program Management Review (PMR) will also be required.
1.3 Background
The B-2 Fuel Vent is a device that functions as a pressure control to limit both positive and negative pressure differentials encountered during ascent or descent by a closed vent fuel tank. The Fuel Vent is listed under national stock number (NSN): 4810-01-380-9046, part number (P/N): 2880001-105.
The Fuel Vent consists of dual five inch diameter butterfly valves. Each value is independently controlled by a transducer/controller/motor combination. When the valve is commanded, each controller sets the vane angle of the valve it controls, independently of the other control unit.
The two independent differential pressure transducers share a common pressure port in the top of the valve. The other port is remote from the valve and extends from the valve to the fuel surge tank. Each vane in the valve is controlled by a separate actuator and controller circuit board. Power is supplied by two independent sources and the vent control valve operates on 28 VDC. It maintains pressures at 5.5 to 6.0 psi positive and 0.7 to 1.2 psi negative.
The Fuel Vent is arranged as a top level Valve Assembly with two primary subassembly modules, the Actuator Assembly and a Circuit Board Assembly.
The Valve Assembly also contains other minor assemblies including the Transducer Assembly and a Flexible Wiring Assembly. Numerous parts on the unit have nuclear hardness requirements.
2 REFERENCE DOCUMENTS
2.1 Government Documents
Table 2-1: Government Document References
Document Number Document Title Description
PVTO 6J15-3-172-3
CHG 3 12 MAY 2010
Technical Manual, Overhaul Instructions with Illustrated Parts Breakdown, Depot Maintenance Valve Assembly, Vent Control 2880001-10X
D-Level Repair TO
AFSCI 61-201
DFARS
252.227.7013
DODI 5230.24
DI SESS 81000E
Attachment I, MIL
STD 31000A
TDP Option Selection Worksheet
2.2 Other Documents
Table 2-2: Other Document References
Document Number Document Title Description DAA3272P021-105 Procurement
Specification
GEIA-STD-0005-1
GEIA-STD-005-2
GEIA-STD-0006
IPC-J-STD-609
3 CONTRACTOR TASKING / REQUIREMENTS
All products developed under this contract shall be considered Government work and shall have no license encumbrances. All data shall be developed and provided in accordance with the data right clauses in the basic contract and as identified in this task order. Unless the Contractor has expressed a claim to providing data to the Government with less than unlimited data rights, the Government will assume unlimited data rights (see DFARS clause 252.227- 7013 of this task order for definition of data rights). Under this PWS the Contractor shall accomplish a supportability analysis of the Fuel Vent based on the latest BOM and latest available and projected piece part availability, and identify solution options for the identified obsolescence. The supportability analysis and solutions shall include both proprietary and non-proprietary components within the BOM.
The Contractor shall ensure that the revised configuration resulting from this engineering project is Form, Fit, and Function (F3) with the existing configuration.
Classified data created under this task shall be in accordance with DoD 5220.22-M and B-2 classified procedures and delivered through an appropriate B-2 classified channel.
All deliverables shall be submitted electronically in Microsoft Word or Excel format (with the exception of the draft TDP). Duplicate delivery in Portable Document Format (PDF) format is also acceptable. The Contractor shall retain all analysis and solution data and artifacts developed under this task, in support of the contemplated buy with NRE implementation task.
3.1 Program Management
3.1.1 Monthly Status Report
The Contractor shall submit the Contractor’s Progress, Status, and Management Report (CDRL A039) in accordance with Para 4.2 herein.
CDRL A039, Contractor’s Progress, Status, and Management Report – DI-MGMT-80227
3.1.2 Program Management Review
The Contractor shall attend regular (quarterly) program status reviews, as approved by the Government Program Manager. The purpose of these meetings shall be to brief the progress of the project from a programmatic perspective, and to solicit input and concurrence of work performed. The Contractor shall generate presentation materials as required to aid in the discussion of programmatic issues. The Contractor shall provide conference agendas, meeting minutes, and track Action Items (AI) associated with the aforementioned meetings/reviews.
CDRL.A001 Conference Agenda – DI-ADMN-81249B CDRL A002 Conference Minutes – DI-ADMN-81250B
3.1.3 Technical Interchange Meeting
The Contractor shall attend regular (quarterly) TIMs, as approved by the Government Program Manager. The purpose of these meetings shall be to brief the progress of each assigned task, and to solicit input and concurrence of work performed. The Contractor shall generate presentation materials as required to aid in the discussion of technical issues and shall support TIMs/Reviews. The Contractor shall provide conference agendas, meeting minutes, and track AIs associate with the aforementioned meetings/reviews.
CDRL A001 Conference Agenda – DI-ADMN-81249B CDRL A002 Conference Minutes – DI-ADMN-81250B
3.1.4 Integrated Master Schedule
The IMS will initially be delivered with the PMP per Table 4-1 Updates will be provided each month via the Monthly Status Report (MSR) in the format outlined in the Program Management section of this document.
3.1.5 Contract Closure Letter
The Contractor shall submit a Contract Closure Letter (CDRL A089) in accordance with the delivery schedule in Para 4.2. This letter shall be submitted on the Contractor’s letterhead, and shall be delivered to the Procurement Contracting Officer (PCO).
CDRL A089, Contract Summary Report – DI-ADMN-80447A
3.2 Baseline Configuration Identification
3.2.1 Project Kickoff Meeting
The Contractor shall conduct a Kickoff Meeting with Government participation. The purpose of the meeting will be to establish communication points of contact (POCs), complete a review of known Fuel Vent specification requirements, ensure verification of completeness of data and documentation, identify project risks, and complete a review of the program approach and objectives with the Government Program Management, Engineers, and Equipment Specialists.
The Contractor shall facilitate delivery of the Conference Agenda (A001) and Minutes (A002) in accordance with the delivery schedule in Para 4.2 herein. The following will be required for the Kickoff Meeting:
• All applicable drawings and specifications will be made available, verifying the confirmed configuration
• Security requirements, operational and support requirements will be identified
• A Risk Register, updated and manageable to execute program, will be provided
• Cost schedule and performance, IMS all executable
• Program planning completed
• Meeting materials complete
• Meeting conducted, AIs assigned and completed
• Proper technical disciplines represented at review
• Government Program Manager approves briefing materiel
CDRL A001, Conference Agenda – DI-ADMN-81249B CDRL A002, Conference Minutes – DI-MGMT-81250B
3.2.2 Program Management Plan
The Contractor shall deliver a PMP, DI-MGMT-81797 (CDRL A086). The PMP shall include a project Integrated IMS, an Integrated Master Plan (IMP), a Risk Management Plan (RMP) and a Contractor Work Breakdown Structure (CWBS). The Contractor shall maintain and update the CWBS throughout the contract and use a CWBS structure for contract reporting. Prior approval from the Government is required for any changes to the CWBS structure at the reporting level. The first submission shall be made with the PMP. Subsequent submissions shall be made upon revision. The PMP, IMS, IMP, RMP, and CWBS shall be submitted in electronic format as agreed by both parties. The Contractor shall facilitate the delivery of the
PMP.
CDRL A086, Program Management Plan (PMP) – DI MGMT-81797
3.2.3 Reliability/Maintainability Program Plans
Contractor shall develop and deliver a draft Reliability and Maintainability (R&M) Program Plan that is consistent with the B-2 Enterprise R&M Plan. The Contractor shall report status of the R&M program at Design Reviews and TIMs. The draft R&M Program Plan shall be in the Contractor’s format. The Plan shall identify and describe the planned Contractor activities for implementation of the R&M Plan up to and including Customer Design Review. R&M Program Plan shall also include:
• Monitoring and control of Subcontractors/Suppliers
• Maintainability design criteria
• Software design documentation as needed
• Environmental Stress Screening as needed
• Reliability Development Growth Testing as needed
• R&M design review information (AoA, TIM)
CDRL A094, Reliability and Maintainability (R&M) Program Plan - DI-SESS-81613A
3.2.4 Counterfeit Prevention Plan
Contractors that supply electronic parts or systems that contain electronic parts shall share established policies and procedures to avoid, detect, mitigate and disposition counterfeit electronic parts to prevent such parts from entering the United Stated Air Force (USAF)/Department of Defense (DoD) supply chain. These policies and procedures shall be documented in a Counterfeit Prevention Plan (CPP) for Government review and approval. DI- MISC-81832 is applicable to Parts, Material, and Processes Selection (PMPS) associated with delivery of systems and assemblies to the USAF and DoD. The requirements established by DI-MISC-81832 also apply to electronics components procured in sustainment of such systems and assemblies.
The requirements of the recently DoD-adopted SAE 5553, Aerospace Standard, Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and Disposition shall also apply.
The Contractor shall report in writing to the Procuring Activity within 30 calendar days of determining any end item, component, part, or material contained in supplies purchased by the DoD, or purchased by a Contractor for delivery to, or on behalf of, the Department, contains counterfeit electronic parts or suspect counterfeit electronic parts for the purpose of investigation and notification of the Air Force Office of Special Investigations (AFOSI). The PCO shall coordinate reporting to the appropriate Program Management/Item Management, System Engineering Management, the Air Force Materiel Command (AFMC) Discrepant Materiel Reporting Program (DMRP) Office in 406 SCMS/GULAB, and the AFOSI.
Additionally, the Contractor shall within the same 30 calendar day’s period ensure all suspected or confirmed counterfeit items are entered into the Government-Industry Data Exchange Program (GIDEP) system, which will serve as the DoD central reporting repository.
(Ref. AS5553, paragraph 4.1.7, appendix G).
The Contractor shall provide appropriate training and shall require all personnel working procurement within their company, to include at a minimum their supply chain management specialists, receiving inspectors, and engineers, to complete said training. The Contractor shall determine the appropriate training required. Training may be developed in-house or may be other Industry accepted training. The CPP shall describe and list the training provided by the Contractor to their personnel.
CDRL A090, Counterfeit Prevention Plan - DI-MISC-81832
3.2.5 Lead-Free Control
The Contractor shall ensure that the risks associated with lead-free (Pb-free) solder and finishes are fully considered and effectively mitigated. All requirements related to Pb-free Tin (Sn) items also apply to Pb-free Zinc and other metallurgical alloys known to demonstrate whisker formation, when used for electronic soldering or electronic component finish. Lead-free is defined as less than 0.1% by weight of lead in accordance with Waste Electrical and Electronic Equipment (WEEE) guidelines. Pb-free Tin is defined to be pure tin or any tin alloy with <3% lead (Pb) content by weight. This means that some Pb-free finishes other than pure tin, such as tin-bismuth and tin-copper, are considered to be "tin" for the purposes of this Standard. Many of these alloys have not been assessed for whiskering behavior. The Contractor shall avoid the use of alloys known to be susceptible to whisker formation in electronic soldering and finishing. The Contractor shall comply with GEIA-STD-0005-1, GEIA- STD-005-2, GEIA-STD-0006 and IPC-J-STD-609 to assure the performance, compatibility, reliability, safety and verifiability of Pb-free product(s). This compliance requirement shall include special design considerations, manufacturing process controls, test and qualification requirements, quality inspection and screening, marking and identification, maintenance and repair processes, and other steps taken to mitigate risks to ensure the reliability and quality of hardware for the intended application. The Contractor shall establish a technical requirement for GEIA-STD-0005-2 control level into all configuration item level specifications.
Lead-Free Control Plan The Contractor shall develop, deliver and upon Government approval, implement a Lead-Free
Control Plan (LFCP). The LFCP shall encompass all the requirements of GEIA-STD-0005-1 and GEIA-STD-005-2. The LFCP shall meet the requirement set forth in GEIA-STD-0005-2 for Control Level 2B. As part of the LFCP, the Contractor shall provide a plan for monitoring materials in their product in accordance with GEIA-STD-0005-2. This Plan shall include a level of active inspection techniques (e.g., XRF or EDS) as outlined in of GEIA-STD-0005-2.
CDRL A091, Lead-Free Control Plan - DI-MGMT-81772
Lead-Free Electronics Risk Management The Contractor shall manage the risks inherent with Pb-free soldering and finishing technologies to ensure that reliability is not adversely impacted should the use of Pb-free become unavoidable. Any adverse behavior shall be reported during risk management reviews and all major technical and programmatic reviews. The Contractor shall conduct risk assessments associated with the introduction of Pb-free solder and finishes into critical piece parts, assemblies, and subsystems to identify potential risks per GEIA STD-0005-2. The Contractor shall implement appropriate mitigation measures chosen from GEIA-STD-0005-2 or supply alternative measures with equal or better reliability. The Contractor shall incorporate GEIA-STD-0006 “Requirements for Using Solder Dip to Replace the Finish on Electronic Components” (or equivalent), when this technique will be utilized as a mitigation technique.
Lead-Free Configuration Management The Contractor shall submit Engineering Change Proposals (ECP) for all changes to the TDP that involve material changes from Pb alloys to Pb-free alloys. The ECPs shall include a complete package of drawing revision sheets, Notices of Revision (NOR), Specification Change Notices (SCN), revised parts lists, and other necessary TDP change pages to document the proposed change. The Contractor shall identify Pb-free components, connectors, and assemblies in technical documents including Weapons Specifications, Item Specifications and technical drawings per GEIA-STD-0005-2. The Contractor shall specify the approved/validated solder types on drawings, including industry standard designations for alloy content. The Contractor shall mark and label approved Sn solder or Sn finish components, Printed Circuit Boards (PCBs) and Print Circuit Board Assemblies (PCBAs) using industry standard IPC-J-STD-609 per GEIA-STD-0005-1. The Contractor shall use only component suppliers that comply with IPC-J-STD-609. The Contractor shall implement IPC-J-STD-609 “Marking and Labeling of Components, PCBs and PCBAs to Identify Lead (Pb), Pb-Free and Other Attributes” to ensure identification of the interconnect metallurgy throughout the lifecycle.
The Contractor shall provide a written Certificate of Conformance (CoC) as a part of the As- Built Configuration Data Lists (ABCL).
CDRL A007, Engineering Change Proposal, DI-SESS-80639D
Manufacturing Processes The Contractor shall use, whenever possible, Sn-Pb based solders and Sn-Pb part surface finishes (minimum 3% Pb by weight) for the assembly of electronics hardware (Components, Boards, Card Cages, Cabinets, Connectors and other electrical assemblies) for Weapons Systems Electronics per GEIA-STD-0005-2. The Contractor shall avoid the use of pure Sn (or other pure metals and alloys prone to whisker formation) piece part termination finishes to the greatest extent practical. In the event that pure Sn (or other pure metals and alloys prone to whisker formation) piece part termination finishes are used, the Contractor shall identify the affected parts to the Government and describe rationale for its use and associated risks. The Contractor shall ensure piece parts being procured for assembly, rework, or repair are of the correct metallurgy intended. The Contractor shall use Standard Microcircuit Drawing Sn-Pb piece parts to the fullest extent practicable. The Contractor shall comply with the latest revisions of Soldering and Electronic Assembly standards for Class 3 Electronics as defined in IPC-A-610 and J-STD-001. The Contractor shall ensure that all technicians are certified and that they follow the approved standards. The Contractor shall use eutectic Sn-Pb solder for all rework and repair actions where the solder alloy cannot be verified as Pb-free through approved documentation and/or analysis. The Contractor shall manage repair, rework maintenance and sustainment activities to assure that Pb-free solder, finishes, or processes are properly applied and controlled to ensure that the end product continues to meet all requirements. The Contractor shall use Pb-free solder alloys only in rework actions where positive identification of the Pb-free alloy can be confirmed through approved documentation and/or analysis.
Lead-Free Electronics Program Management The Contractor shall present to the Government Pb-free risks and issues at all technical reviews. The Contractor shall flow down applicable requirements of this PWS to Contractors, Subcontractors, Suppliers and Grantees as outlined in GEIA-STD-0005-2. The Contractor shall provide support to the Government on surveys, audits, product inspections, qualification testing, risk assessments, and production line certifications to verify the capability and qualification of supply sources. The results of surveys, audits and product inspections performed by other centers, other Government agencies, accredited third-party organizations, or the private sector may be utilized on a risk-informed basis as supplement to, or a substitute for direct surveillance.
3.2.6 Baseline Configuration Identification Report
The Contractor shall develop a full baseline of the Fuel Vent and supporting factors needed for production. A Baseline Configuration Report, CDRL A045, shall be delivered in accordance with (IAW) Table 4-1.
At minimum the Baseline Configuration Report shall include: the full BOM, a listing of all production test/support equipment, and a complete listing all legacy documentation required for new production.
CDRL A045, Technical Report – Study/Services - DI-MISC-80508B
3.3 Parts Obsolescence Assessment
The Contractor shall evaluate the full BOM, all test/support equipment, and documentation per the Baseline Configuration Report for obsolescence and availability.
3.3.1 Parts Obsolescence Report
The Parts Obsolescence Assessment Report shall identify parts that are presently obsolete and that are projected to be obsolete within 3 years. Test and support equipment required for production shall be evaluated for availability and expected functionality for the expected production phase. All required production documentation shall be determined available or unavailable and shall include reasons for the unavailable items. All findings shall be compiled and delivered in an Obsolescence Assessment Report, CDRL A088. This report will be an extension of the Baseline Configuration Report and shall be submitted IAW Table 4-1.
CDRL A045, Technical Report – Study/Services - DI-MISC-80508B
3.3.2 Piece Part Testing
Based on the obsolescence solutions recommended, the Contractor shall determine what parts require further testing to assure feasibility of the proposed solutions. These parts will be procured and tested as needed. This may include material samples, fitment prototypes, nuclear Hardness Critical Item (HCI) parts testing, and other electronic testing as required for part validations.
The results of these tests shall be briefed as they become available through existing technical and programmatic meetings as well as the MSR (CDRL A039). The Obsolescence Solution Report shall be revised if needed to maintain the accuracy of the overall solution and Delivered with the final MSR (CDRL A039). Formal part testing reports are not required beyond what is required for part approval.
CDRL A045, Technical Report – Study/Services - DI-MISC-80508B
3.3.3 Analysis of Alternatives
The Contractor shall conduct an AoA review TIM in accordance with the schedule in paragraph
4.2 herein. This review shall detail each possible solution path for obsolescence issues where multiple, significantly differing solutions exist. It shall recommend a primary path and be reviewed at an associated TIM. Following the TIM the Government shall provide concurrence with the recommended solutions or direct one of the alternate solution paths for each item.
The AoA shall address current known obsolescence, and shall also address parts that have projected obsolescence (i.e. lack of existing approved manufacturing sources). Based on the list of current and projected piece part obsolescence, the Contractor shall identify and evaluate proposed alternatives for long term sustainment. Aircraft-level F3 shall be maintained.
Alternatives shall include obsolescence resolution, replacement electronics, replacement
Circuit Card Assemblies (CCA) and/or modules in the current LRU. New component vendors and substitute items shall be considered, on a case-by-case basis, for continued component support. The Contractor shall provide alternative solutions to Class I changes (where possible) for resolving current obsolescence through the following options:
• Substitute component parts, new sources for existing components, replacement components, re-spinning current configuration components and component redesign
• Circuit card or module redesign (taking into consideration circuit card commonality within the LRU), re-spinning current configuration circuit cards/modules or replacement circuit cards/modules
• Additional Class II alternatives are also encouraged The Contractor shall review all the documentation in the current TDP of the applicable LRU, which may include, but may not be limited to, the drawings, BOM, Parts Lists, Data Lists, repair procedures, and Illustrated Parts Breakdown (IPB) to ensure alternative solution compliance. The Contractor shall meet all current configuration specifications and requirements.
The AoA Review will address testing requirements for implementation of the proposed solution(s) into the LRU and the B-2 aircraft. Testing requirements may include, but are not limited to, bench test, component test, LRU level test, sub-system level test, system level test, and environmental test.
The AoA Review will address other issues aside from obsolescence that makes the LRU no longer procurable. This may include, but is not limited to, obsolete support for test equipment, obsolete manufacturing methodologies, obsolete raw materials, obsolete manufacturers or vendors, insufficient or missing technical data, and new laws and regulations.
CDRL A001, Conference Agenda – DI-ADMN-81249B CDRL A002, Conference Minutes – DI-MGMT-81250B
3.4 Obsolescence Solution
The Contractor shall develop and deliver a top level target solution for all parts that are identified as currently obsolete or parts projected to be unsupportable or at risk of being unsupportable in the near future. All solutions must be F3 at the LRU and be backward compatible at the Shop Replaceable Unit (SRU) with legacy LRU configurations. Design engineering activity to determine and verify suitability of each solution will be accomplished under para 3.3.1 and 3.3.2 herein. Target solutions shall fall into one of the following categories, in order of preferred approach below.
• Logistics piece part substitution – Substitute part available which meets the original part specifications.
• New Source Development/Qualification – Development and/or qualification of source to develop the original part.
• Complex piece part substitution – Selection and qualification of substitute part to satisfy specification requirements of original part.
• Use of IC adapters to allow for an equivalent component available in a different package to be used.
3.4.1 Obsolescence Solution Report
The Obsolescence Solution Report shall include an updated BOM listing from 3.3.1and 3.3.2, adding the applicable target solution approach for each obsolete and projected unsupportable piece part. The Solution Report shall also include a CCA assessment, containing the piece part details, in order to provide an initial basis of determination between piece part substitute and CCA redesign. The Obsolescence Solution Report shall be delivered in accordance with the delivery schedule in Para 4.2 herein.
CDRL A045, Technical Report – Study/Services - DI-MISC-80508B
3.4.2 Procurement Specification Update
The Contractor shall review the most current version of the P-Spec and determine if updates are required. This decision will be based on the proposed engineering changes, identified obsolescence, and superseded standards. If an entirely Class II solution is available, a P-Spec revision may not be needed. If revised, updated standards will be incorporated into the P- Spec, where applicable. The Government will have 30 calendar days to review the revised P- Spec and provide comments to the Contractor.
CDRL A045, Technical Report – Study/Services - DI-MISC-80508B
3.4.3 Test and Evaluation Program Plan
The Contractor shall create a TEPP based on the proposed design changes. The TEPP shall include the requirements for qualification during the follow-on buy with NRE effort and be reviewed and approved by the Contractor, any pertinent Subcontractors, and all applicable B-2 Enterprise functions. A Government review and approval of the TEPP is also required. TIMs, Engineering Review Boards (ERB), and Engineering & Technical Review Boards (ETRB) will be held as needed to ensure Enterprise approval of the TEPP. The TEPP shall be submitted in accordance with the delivery schedule in Para 4.2 herein. The Government will provide approval within 30 calendar days. The approval will include comments and direction for any instances of non-concurrence on a listed Requirement or Specification.
CDRL A050, Test and Evaluation Program Plan - DI-NDTI-81284
3.4.4 System Requirements Technical Interchange Meeting
The Contractor shall conduct a System Requirements TIM to include Government participation. The TIM shall ensure adequate project planning and preparation, and accurate accounting of all applicable drawings and specifications. The TIM shall ensure that the Contractor is ready to proceed with proposed system design changes and validate that system requirements, as defined in the P-Spec, are being met. The Government will have 10 days to provide approval. The Contractor shall deliver a Conference Agenda prior to the TIM and Meeting Minutes following the TIM. The following criteria are required:
• System requirements defined to support system definition, functional decomposition and test and evaluation.
• Completed system procurement/performance specification (if required).
• All applicable drawings and specifications available, with confirmed configuration.
• Security requirements, operational and support requirements.
• Risk Register updated and manageable to execute program.
• Draft Software Requirement Spec defined with verification requirements (if needed).
• Initial software architecture design been defined (if needed).
• Program Staffing requirements, baseline vs. actual.
• Cost schedule and performance, IMS all executable.
• Program planning completed.
• Program execution plans updated.
• System requirements captured for review.
• Draft R&M will be available.
• Test and Evaluation Program Plan will be available.
• System Engineering Management Plan available.
• Meeting materials complete.
• Meeting conducted, action items assigned and completed.
• Proper technical disciplines represented at review.
• Government Program Manager approves briefing materiel.
CDRL A001, Conference Agenda – DI-ADMN-81249B CDRL A002, Conference Minutes – DI-MGMT-81250B
3.4.5 Updated Technical Data Package
The Contractor shall develop and shall deliver a draft TDP to include, but not limited to, a Fuel Vent parts list, functional block diagrams, and schematics covering the modifications proposed to the Fuel Vent configuration for use on the contemplated follow-on effort. Draft mechanical drawings shall be included in TDP as required. The TDP shall be in accordance with DI-SESS- 81000E and Attachment I, MIL STD 31000A, TDP Option Selection Worksheet. The Government will have 30 calendar working days to review the draft TDP and provide comments to the Contractor. The TDP shall have data rights that are not more restrictive than data rights on the current legacy LRU configuration. The Government shall have full/unlimited rights to changed/new drawings or data submitted as part of the TDP or created under this contract. The Contractor shall ensure the Government has sufficient data rights to allow the contract deliverables to be used for future fabrication and testing of prototypes and the remaining tasks. The Contractor shall invoke these same requirements with its Subcontractors or vendors at any tier requiring the delivery of technical data, except contractual instruments for commercial items or commercial components. This shall include pre-notification of rights in data and shall ensure that Subcontractors and vendors are required to provide the same depth of data that the prime is obligated to provide to the Government. Subcontractor or vendor data may be provided directly to the Government if rights limitations preclude their being provided by the way of the prime Contractor. Any deviation in Subcontractor and vendor data content must be approved by the Government procuring agency. The TDP shall be delivered on CD- ROM. Note that the final TDP will be completed and delivered under Phase II. The TDP shall be delivered in accordance with the delivery schedule in Para 4.2 herein.
CDRL A080, Product Drawings/Models and Associated Lists – DI-SESS-81000E
3.4.6 Follow-on Cost Estimate
The Contractor shall develop and deliver a Phase II cost estimate as a Contractor formatted Technical Report with cost factors. The report shall contain cost estimates for the follow-on effort based on the AoA and the expected qualification effort up to and including first article, if required. Additionally, an expected cost per unit for spares will be included.
CDRL A045, Technical Report – Study/Services - DI-MISC-80508B
4 PERIOD OF PERFORMANCE AND DELIVERY SCHEDULE
4.1 Period of Performance
The period of performance for this task shall be for 24 months following award. Early completion and delivery is acceptable and encouraged, but without additional monetary compensation or reward.
4.2 Delivery Schedule for Contract Data Requirements Lists
The following table summarizes the deliverables and their respective due dates. The Contractor shall develop a finalized IMS. The Contractor shall maintain the IMS and deliver the evolving IMS and an updated Contract Data Requirements List (CDRL) delivery schedule in the MSR (CDRL A039) to capture any changes to delivery dates. The MSR shall also address and provide a get-well plan for spending that is more than 10% over budget as defined in PMP.
Approval of changes to the delivery schedule will be accomplished by approval of the MSR and the adjusted IMS. All schedules are specified in terms of calendar days.
Table 4-1: CDRL Schedule
Paragraph Description CDRL Delivery Schedule
3.1.2, 3.1.3, 3.2.1, 3.3.3, 3.4.4
Meeting Agendas A001 5 Calendar Days Prior to Meeting
Meeting Minutes A002 5 Calendar Days After Meeting
3.1.1, 3.3.2, 4.2 Contractor’s Progress, Status, and Management Report A039 15th day of each month
3.1.2 Program Management Reviews N/A Quarterly
3.1.3 Technical Interchange Meetings N/A Quarterly
3.1.4, 3.2.2 Program Management Plan w/IMS A086 45 Calendar Days ARO
3.1.5 Contract Closure Letter A089 30 Calendar Days Prior
to Contract Closeout
3.2.1 Project Kick Off Meeting N/A 45 Calendar Days ARO
3.2.3 Reliability and Maintainability Program Plan A094 120 Calendar Days ARO
3.2.4 Counterfeit Prevention Plan A090 120 Calendar Days ARO
3.2.5.1 Lead‐Free Control Plan A091 120 Calendar Days ARO
3.2.5.3 Engineering Change Proposal A007 As Required
3.2.6 Baseline Configuration Identification Report A045 180 Calendar Days ARO
3.3.1 Parts Obsolescence Assessment Report A045 270 Calendar Days ARO
3.3.2 Parts Testing Report A045 As Required
3.3.3 Analysis of Alternatives TIM N/A 360 Calendar Days ARO
3.4.1 Obsolescence Solution Report A045 390 Calendar Days ARO
3.4.2 Revised Procurement Specification (if required) A045 540 Calendar Days ARO
3.4.3 Test and Evaluation Program Plan A050 540 Calendar Days ARO
3.4.4 System Requirements TIM N/A 600 Calendar Days ARO
3.4.5 Draft Technical Data Package A080 700 Calendar Days ARO
3.4.6 Follow-on Cost Estimate A045 400 Calendar Days ARO
5 SPECIAL CONSIDERATIONS
5.1 Data Marking
The following references govern how artifacts containing technical data shall be marked.
• DODI 5230.24, Distribution Statements on Technical Documents
• AFI 61-201, Scientific, Research And Development Management of Scientific and
Technical Information (STINFO)
• DFARS 252.227-7013, Rights in Technical Data--Noncommercial Items
5.1.1 Asserted Rights in Technical Data
Mark all technical data to be delivered to the Government IAW DFARS 252.227.7013(f) Technical data delivered or otherwise provided under a contract without restrictive markings shall be presumed to have been delivered with unlimited rights and may be released or disclosed without restriction.
5.1.2 Removal of Unjustified and Nonconforming Markings
IAW DFARS 252.227.7013(h), Proprietary markings shall be considered non-conforming and not authorized. The words "unlimited rights" shall be considered non-conforming and not authorized. All nonconforming markings will require removal and redelivery of the artifacts within 60 calendar days.
5.1.3 Distribution Statements
Mark STINFO to be delivered to the Government IAW DODI 5230.24 and AFI 61-201.
Descriptions and examples of each applicable Distribution Statement are listed below.
Distribution Statement A Distribution Statement A shall be used for technical data with asserted license rights of Unlimited where Export Control is not required. A Destruction Notice is not required.
DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited.
Distribution Statements D and E Distribution Statements D and E shall be used for the following instances:
• Distribution Statement D shall be used for technical data with asserted license rights of Unlimited where Export Control is required.
• Distribution Statement E shall be used for technical data with asserted license rights of Limited.
• Distribution Statement E shall be used for technical data with asserted license rights of Government Purpose.
• Distribution Statement E shall be used for technical data that contains proprietary information.
Distribution Statements D and E are expressed in a standard format comprising four components presented in the following order and as applicable to this PWS:
1. Authorized Audience – Department of Defense and DoD contractors or DoD Components only.
2. Reason for Control - More than one reason or justification for non-release of controlled technical information may apply. Therefore, more than one reason may be used in a Distribution Statement. Applicable reasons are:
a. Administrative or Operational Use.
b. Critical Technology.
c. Export Controlled – All artifacts found to contain export controlled technical data, must specify “Export Controlled” as a reason for limitation in addition to all other reasons that apply.
d. Proprietary Information – For technical data, note the Government’s license rights i.e. “Proprietary Information (DFARS Limited Rights)”. For non-technical data, such as financial information, state “Proprietary Information” without the Government’s license rights.
3. Date of Determination – Date contract was awarded.
4. Controlling Office - 423 SCMS/GUEA, 3001 Staff Drive, Tinker AFB, OK 73145.
DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S.
DoD contractors only; Critical Technology and Export Controlled; 23 August 2018. Other requests shall be referred to 423 SCMS 423 SCMS/GUEA, 3001 Staff Drive, Tinker AFB, OK 73145.
DISTRIBUTION STATEMENT E. Distribution authorized to DoD Components only; Proprietary Information (DFARS Limited Rights) and Export Controlled; 23 August 2018. Other requests shall be referred to 423 SCMS/GUEA, 3001 Staff Drive, Tinker AFB, OK 73145.
5.1.4 Export Control Warning Label
Mark all STINFO determined to contain export controlled data to be delivered to the Government IAW DODI 5230.24. The Export Control Warning shall be placed directly below the Distribution Statement. All documents assigned a Distribution Statement other than A shall be marked on every page with the following statement:
WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.
5.1.5 Destruction Notice for Unclassified Documents
Mark all limited-released (marked with a Distribution other than A) STINFO to be delivered to the Government IAW DODI 5230.24 and AFI 61-201. The Destruction Notice illustrated below, shall be placed directly underneath the Export Control Warning.
DESTRUCTION NOTICE - Destroy by any method that will prevent disclosure of contents or reconstruction of the document.
5.1.6 Classification
Mark all data to be delivered to the Government with classification markings representing the highest classification of the document.
The Contractor may mark all unclassified technical data to be delivered to the Government with ”UNCLASSIFIED” typed on the footer and header of each page.
5.1.7 General Marking Guidance
• All markings shall be conspicuously electronically fixed as to not interfere with other markings contained within the document.
• All markings shall be legible when viewed at normal 100 percent viewing resolutions.
• All markings shall be electronically fixed to the footer of every page of the electronic document.
• Coversheets shall not be used unless coversheet page numbering is sequentially consistent with the document.
• Portions or pages of a document may have different distribution statements that would govern their distribution if separated from the main document. The most restrictive distribution on its parts applies to the document as a whole.
5.2 Security
5.2.1 Safeguarding of Unclassified Controlled Technical Information
DFARS clause 252.204-7012, Safeguarding of unclassified Controlled Technical Information, is applicable to this effort. The Contractor shall control information IAW this clause, other sections of this PWS, and terms and conditions of the contract.
5.2.2 Release or Removal of Information
Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to Dena Jenkins, 423 SCMS/GUEA.
5.2.3 Access to Confidential, Proprietary and/or Sensitive Information Contractor personnel may be required to access Confidential, Proprietary and/or Sensitive Information held by the USAF relating to tasks performed under this Task Order. This information may belong to other Contractors, other third parties, or the USAF. Contractor personnel shall provide a completed copy of the Nondisclosure Agreement (Attachment II) to the Government Program Manager, Contracting Officer Representative (COR), and Contracting Officer (CO) prior to performing work that involves Confidential, Proprietary, and/or Sensitive Information held by the USAF relating to the tasks to be performed under this Task Order.
It should be noted that Confidential, Proprietary, and/or Sensitive Information shall not include information that the Contractor personnel or the Contractor can demonstrate:
• was known by the Contractor personnel or the Contractor without restriction as to further disclosure when received or was developed independently by the Contractor by individuals who had no direct or indirect access to such information,
• was obtained from a source other than the USAF, its employees, agents, or Contractors through no breach of confidence,
• was in the public domain when received or thereafter enters the public domain through no breach of confidence by Contractor or Contractor personnel, or
• was used or disclosed with the prior written approval of the USAF.
5.2.4 Security Clearance
All Contractor employees shall possess appropriate security clearances to support the B-2 platform. Refer to the DD Form 254 attached to the contract for additional security instructions, guidance, policies, and restrictions.
5.2.5 Common Access Cards
For base and data system access, a Common Access Card (CAC) is required in support of this effort and the Security Clearance level is expected to be CLASSIFIED, the following instructions shall apply. It should be noted that this process may take a minimum of 4 weeks to complete. It is critical that Contractors consider these instructions before award and prior to changing Contractor personnel after award.
For issue of CACs to Contractors (Contractor Verification System), the Contractor must have favorable or higher adjudication based on a National Agency Check with Inquiries (NACI) or higher investigation.
Also, AFSSI 8522, Communications and Information, Chapter 3, Access to Information Systems and Networks, states:
Favorable Background Investigation. CSAs, in coordination with the security manager, will verify proper security clearance and background investigation checks (National Agency Check with written Inquiries [NACI], Single Scope Background Investigation) are submitted prior to granting a network user access to the AF-GIG.
Upon successful completion of initial IA awareness training and verification of favorable background check, the user is authorized use of the network and is granted access to authorized network resources.
Contractors shall ensure CACs are obtained by all Contractor or Subcontractor personnel who meet one of both of the following criteria:
• Require logical access to DoD computer networks and systems in either:
1. The unclassified environment; or
2. The classified environment where authorized by governing security directives.
• Perform work, which requires the use of a CAC for installation entry control or physical access to facilities and buildings.
Contractor shall provide a listing of personnel who require a CAC to the Program Manager, COR, and CO. A sample template of the CAC listing for Contractor personnel is provided in PWS Attachment III. Refer to AFFARS clause 5352.242-9001, CACs for Contractor Personnel for additional information.
5.2.6 Base or Area Badges and Access to Facilities
423 SCMS/GUEA or the Government Program Manager will assist Contractor personnel in processing the necessary DoD forms to obtain base or area badges for access to Government facilities and property. Access to Government facilities is limited. Therefore, the Contractor shall coordinate required access/usage times and dates through 423 SCMS/GUEA at least 15 working days prior to the need date. Control of the facilities shall remain with the Government.
5.2.7 Standards of Conduct
The Contractor shall not divulge any information regarding files, data, processing activities/functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standards of conduct.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it.