Attachment 21 - Task Order 0001 Statement of Work.docx
DOCX document 146 KB Posted
- Attached to
- DRAFT RFP for Integrated Battle Command System (IBCS) LRIP/FRP Federal contract opportunity
- Solicitation number
- W31P4Q-20-R-0015
About this file
This is a draft Request for Proposal (RFP) for the Integrated Battle Command System (IBCS) Low Rate Initial Production/Full Rate Production (LRIP/FRP) hardware segment. The RFP seeks proposals to produce IBCS hardware end items such as Engagement Operations Centers, Engagement Center Trailers, and Integrated Collaborative Environments in accordance with supplied Technical Data Packages and Critical Item Development Specifications. Engineering changes may be required for obsolescence, new capabilities, and export considerations. In addition to hardware production, proposals are also sought for maintaining approved software and firmware updates, cybersecurity, and Authority to Operate on existing hardware components. The Department of the Army Materiel Command Contracting Command at Redstone Arsenal is the issuing agency. This draft RFP is for comment only and the government is not currently seeking proposals based on the posted information.
View the file
Other files for this federal contract opportunity
Show all 50
DRAFT RFP for Integrated Battle Command System (IBCS) LRIP/FRP has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
FOR OFFICIAL USE ONLY
W31P4Q-20-R-0015 LRIP/FRP
Task Order 0001 Statement of Work
For The
Integrated Battle Command System (IBCS) Low Rate Initial Production/Full Rate Production (LRIP/FRP)
W31P4Q-20-D-0015 / Task Order 0001
Date
PREPARED BY:
IAMD Project Office
ATTN: SFAE-MSL-IA
Redstone Arsenal, AL 35898-5710
Table of Contents
| 1 | Scope | 7 |
| 2 | Documents | 7 |
| 3 | General Requirements | 7 |
| 4 | Detailed Requirements | 7 |
| 4.1 | Production Hardware End Items | 7 |
| 4.2 | Engagement Operations Center (EOC) | 7 |
| 4.3 | Engagement Center Trailer (ECT) | 7 |
| 4.4 | Integrated Collaborative Environment (ICE) | 8 |
| 4.5 | Integrated Fire Control Network (IFCN) Relay | 8 |
| 4.6 | First Article Inspection (FAI) | 8 |
| 4.7 | Production Meetings, Reviews and Metrics | 8 |
| 4.7.1 | Startup Meeting | 8 |
| 4.7.2 | System Metrics | 9 |
| 4.7.3 | Manufacturing Management Program (MMP) | 9 |
| 4.7.4 | Integrated Program Reviews (IPRs) | 10 |
| 4.8 | Quality | 10 |
| 4.8.1 | Quality Assurance (QA) Program | 10 |
| 4.8.2 | Program Product Assurance Plan | 10 |
| 4.8.3 | Corrosion Prevention and Control | 10 |
| 4.9 | GFE Management. | 10 |
| 4.9.1 | Property Records | 11 |
| 4.9.2 | Property Accountability | 11 |
| 4.9.3 | Disposition of Property | 11 |
| 4.10 | Configuration Management System & Audits | 11 |
| 4.10.1 | CM Program | 11 |
| 4.10.2 | Configuration Change Management | 11 |
| 4.10.3 | Request for Variance (RFV) | 12 |
| 4.10.4 | Serialization, Lot and Block Control | 12 |
| 4.10.5 | Failure Reporting, Analysis, and Corrective Action System & Failure Review Board | 12 |
| 4.10.6 | Configuration Audits and Reviews | 12 |
| 4.10.6.1 | Physical Configuration Audit (PCA) | 12 |
| 4.10.6.2 | Configuration Status Accounting (CSA) | 12 |
| 4.10.7 | Data Management | 13 |
| 4.10.8 | Data Accession List | 13 |
| 4.10.9 | Data Item Master Schedule | 13 |
| 4.11 | Manufacturing | 13 |
| 4.11.1 | Parts, Materials and Processes (PMP) | 13 |
| 4.11.2 | PMP Plan | 13 |
| 4.11.3 | PMP Program | 14 |
| 4.11.4 | Commercial Off-the-Shelf (COTS) Management Plan | 14 |
| 4.11.5 | Lead Free Control Plan (LFCP) | 14 |
| 4.11.6 | Non-Conforming Material | 15 |
| 4.11.7 | Counterfeit Parts Prevention | 15 |
| 4.11.8 | Environmental Stress Screening (ESS) | 15 |
| 4.11.9 | Manufacturing Readiness Assessments | 16 |
| 4.11.10 | Production Line Validation (PLV) Planning | 16 |
| 4.11.11 | Production Line Validation (PLV) Execution | 17 |
| 4.12 | Vendor and Subcontractor Control | 17 |
| 4.13 | Qualification | 17 |
| 4.14 | Product Acceptance | 17 |
| 4.14.1 | Configuration Acceptance | 17 |
| 4.14.2 | Acceptance Test Plan & Procedures | 17 |
| 4.14.3 | SIE/STE Validation | 18 |
| 5 | Production Engineering Support | 18 |
| 5.1 | ECP Process | 18 |
| 5.1.1 | Class 1 ECPs | 19 |
| 5.1.2 | Potential Class I ECP Candidates. | 19 |
| 5.1.3 | Class II ECP Process | 19 |
| 5.1.4 | Test Documentation | 20 |
| 5.1.5 | ECP Testing | 20 |
| 5.1.6 | Post Test Reviews | 20 |
| 5.2 | Hardware Control System (HCS). | 20 |
| 5.2.1 | HCS Configuration | 20 |
| 5.2.2 | HCS Purpose | 20 |
| 5.2.3 | HCS Prove Out | 21 |
| 5.3 | IBCS Synchronization | 21 |
| 5.3.1 | IBCS synchronization Plan | 21 |
| 5.3.2 | Agile Software | 21 |
| 5.3.3 | New IBCS software versions and required IBCS software related inputs. | 22 |
| 5.3.4 | IBCS configuration control | 22 |
| 5.3.5 | Firmware configuration for the production line | 22 |
| 5.3.6 | OIV/FCN Software Reliability | 22 |
| 5.4 | Field Engineering Services (FES) | 22 |
| 5.4.1 | Field Service Representatives (FSRs) | 22 |
| 5.4.2 | Operational Service Representatives (OSRs) | 23 |
| 5.4.3 | Government-Systems Integration Laboratory (G-SIL) Support - (RSA, AL) | 23 |
| 5.4.4 | Tactical Systems Integration Laboratory (T-SIL) Support - (Ft. Bliss, Texas) | 23 |
| 5.4.5 | Mission Integration Laboratory (MIL) Support - (Andover, MA) | 24 |
| 5.4.6 | IAMD Testbed Operations and Readiness Support - (White Sands Missile Range, NM) | 24 |
| 5.4.7 | Laboratory and Testbed Operations Updates | 24 |
| 5.5 | Obsolescence | 24 |
| 5.5.1 | Known Obsolete Parts | 24 |
| 5.5.2 | Resolution of Known Obsolete Parts Issues prior to First Delivery. | 25 |
| 5.5.3 | Electronic Parts Lists (EPLs) | 25 |
| 5.5.4 | DMSMS Reporting | 25 |
| 5.5.5 | DMSMS Case Summary | 25 |
| 5.5.6 | Obsolescence Risk Management | 26 |
| 5.5.7 | Hardware integration | 26 |
| 6 | Logistics | 26 |
| 6.1 | Logistics Planning | 26 |
| 6.1.1 | Spares Analysis | 26 |
| 6.1.2 | Logistics Product Data | 27 |
| 6.1.3 | LPD Database | 27 |
| 6.1.4 | Level of Repair Analysis | 27 |
| 6.1.5 | Electronic Technical Manuals (ETMs) | 28 |
| 6.1.6 | Interactive Electronic Technical Manual (IETM) and Electronic Technical Manual (ETM) | 28 |
| 6.1.7 | Technical Manual Verification | 28 |
| 6.1.8 | Troubleshooting Procedures | 28 |
| 6.1.9 | Maintenance Allocation Chart (MAC) | 28 |
| 6.1.10 | Repair Parts and Special Tools List (RPSTL) | 29 |
| 6.1.11 | Illustrations. | 29 |
| 6.1.12 | Extensible Markup Language (XML) Requirements | 29 |
| 6.1.13 | Source and Delivery Data Quality | 29 |
| 6.2 | Reliability and Maintainability (R&M) | 30 |
| 6.2.1 | AMD Performance Based Logistics Program Support | 30 |
| 6.2.2 | Logistics Maintainability Demonstration (LMD) | 30 |
| 6.2.3 | R&M Models, Allocations and Predictions | 30 |
| 6.2.4 | R&M Program | 31 |
| 6.2.5 | Failure Modes, Effects, and Criticality Analysis (FMECA) | 31 |
| 6.2.6 | RAM Scoring | 31 |
| 6.2.7 | Warranty Management | 32 |
| 6.2.8 | Packaging | 32 |
| 6.2.9 | Shipment and Delivery | 32 |
| 6.2.10 | Shipment Guidelines | 32 |
| 6.2.11 | Special Packaging Instructions (SPI's) | 33 |
| 6.2.12 | Hazardous Material Shipping & Handling | 33 |
| 6.2.13 | Item Unique Identification (IUID) | 33 |
| 6.2.14 | Technical Manual Data Rights Requirements | 34 |
| 6.3 | Temporary Storage of IBCS Hardware End Items | 34 |
| 6.4 | Hardware Risk Management | 34 |
| 7 | Program Management, Financial Reporting, Mandatory Requirements | 34 |
| 7.1 | Earned Value Management System (EVMS) | 34 |
| 7.2 | Project Status Report | 35 |
| 7.3 | Contractor Cost Data Report (CCDR) | 35 |
| 7.4 | Contract Funds Status Report (CFSR) | 35 |
| 7.5 | Contractor Manpower Reporting | 35 |
| 7.6 | Subcontracting Opportunities | 36 |
| 7.6.1 | Subcontracting Plan | 36 |
| 7.6.2 | Subcontracting Report | 36 |
| 7.6.3 | Identification of Subcontractor Change | 36 |
| 7.6.4 | Identification of Subcontracting Opportunities | 37 |
| 7.6.5 | Competition in Subcontracting | 37 |
| 7.7 | Commercial and Government Entity (CAGE) | 37 |
| 7.8 | Use of Existing Data | 37 |
| 7.9 | Environmental, Safety, Occupation and Health | 37 |
| 7.9.1 | IBCS Safety and Health Support | 37 |
| 7.9.2 | Environmental Activities | 38 |
| 7.9.3 | Environmental Reporting | 38 |
| 7.9.4 | Hazardous Material Reporting | 38 |
| 7.9.5 | Ozone Depleting Chemical/Ozone Depleting Substance | 38 |
| 7.10 | Security | 39 |
| 7.10.1 | Program Protection | 39 |
| 7.10.2 | Anti-Terrorism (AT) Level I training | 39 |
| 7.10.3 | Access and General Protection/Security Policy and Procedures | 39 |
| 7.10.4 | Common Access Card (CAC) Access | 40 |
| 7.10.5 | Non-CAC, DoD Facility or Installation Access | 40 |
| 7.10.6 | IWATCH Training | 40 |
| 7.10.7 | Army Training Certification Tracking System (ATCTS) | 40 |
| 7.10.8 | OPSEC Program | 40 |
| 7.10.9 | OPSEC Training | 41 |
| 7.10.10 | Information Assurance (IA)/Information Technology (IT) Training | 41 |
| 7.10.11 | IA/IT Certification | 41 |
| 7.10.12 | Handling/Access to Classified Information | 41 |
| 7.10.13 | Threat Awareness Reporting Program (TARP) | 41 |
| 7.10.14 | Cybersecurity | 41 |
| 7.10.15 | STIGs/STICs Baseline and Updates | 42 |
| 7.10.16 | Cybersecurity Assessment Support | 42 |
| 8 | Deliverables | 42 |
| 9 | Delivery Schedule | 46 |
W31P4Q-08-C-0418 Attachment 0001-IBCS SOW
FOR OFFICIAL USE ONLY
W31P4Q-20-R-0015 LRIP/FRP
Pursuant to the provision of Indefinite Delivery/Indefinite Quantity (IDIQ) contract W31P4Q-20-R-0015 set forth in Section H entitled “Task Order Process,” the following Task Order is defined.
Task Order (TO) Number 0001
1. Scope The purpose of this TO is to define requirements for Task Order 0001 of the IBCS LRIP/FRP program.
Documents Applicable top level documents cited in this TO are identified by number, version, title, date, and category in the Document Summary List (DSL). The document versions specified on the DSL take precedence over the generic references (without revision letters) cited in the TO.
General Requirements The contractor shall perform tasks to ensure efficient, effective accomplishment of this TO. Except as specifically stated herein, the contractor is responsible for all labor, travel cost, supervision, equipment and maintenance, tools, supplies, and materials needed to fulfill this CET.
Detailed Requirements
Production Hardware End Items The contractor shall provide engineering support for production, integration, test, environmental stress screening, and software load test activities, including maintenance of automation and tools used in these activities. The contractor shall provide engineering subject matter expertise to isolate, analyze and fix hardware defects.
Engagement Operations Center (EOC) The Contractor shall fabricate, assemble, integrate, test and deliver 12 EOCs, Part Number ALH-216012-001, IAW the provided product TDP included as part of the data library. Testing shall include execution of the attached Acceptance Test Procedures (ATP) IAW Attachment 04. The contractor will notify the Government no less than 5 days before the ATP testing begins. The contractor will include a copy of all inspection and test results as a part of the DD250 and maintain all inspection and test records associated with the end item and subassemblies.
Engagement Center Trailer (ECT) The contractor shall use Tobyhanna Army Depot via a Public/Private Partnership subcontract to build 12 ECTs. The contractor shall utilize Part Number ALH-215170-001, IAW the provided product TDP included as part of the data library. The government will provide the Environmental Control Unit (ECU), Generator, and Trailer as shown in Attachment 03 (GFE List). The contractor shall notify the Government no less than 5 days before ECT final inspection at Tobyhanna. Testing will be conducted IAW Acceptance Test Procedure (Attachment 4). The contractor will include a copy of all inspection and test results as a part of the EOC DD250 and maintain all inspection and test records associated with the end item and subassemblies.
Integrated Collaborative Environment (ICE) The Contractor shall fabricate, assemble, integrate, test and deliver 12 ICEs, Part Number ALH-216012-003, IAW the provided product TDP included as part of the data library. The ICE shall be accepted and delivered as part of the EOC. Testing shall include execution of the attached Acceptance Test Procedures (ATP) IAW Attachment 04. It shall be tested IAW the Acceptance Test Procedure (Attachment 04). The contractor shall notify the Government no less than 5 days before ATP begins. The contractor will include a copy of all inspection and test results as a part of the EOC DD250 and maintain all inspection and test records associated with the end item and subassemblies.
Integrated Fire Control Network (IFCN) Relay The Contractor shall fabricate, assemble, integrate, test and deliver 24 IFCN Relays, ALH-216012-005, IAW the provided product TDP included as part the data library. Testing will include execution of the attached Acceptance Test Procedures (ATP) Attachment 04.The contractor will notify the Government no less than 5 days before ATP testing begins. The contractor will include a copy of all test results as a part of the DD250 and maintain all records associated with the delivered end item and subassemblies.
First Article Inspection (FAI) The contractor shall conduct a FAI on the first deliveries of Major End Items (MEI) deliveries made to the government. The contractor shall implement and maintain an FAI Plan IAW DI-NDTI-81307 (CDRL A001) IAW SAE AS9102. The contractor shall notify the Government at least fifteen days prior to conducting any FAI, so the Government may participate in the activity. The contractor shall prepare an FAI Report IAW DI-MISC-80508 (CDRL A002). The FAI Report shall include AS9102 referenced forms stamped by the supplier quality engineer and address the results and findings of the inspection.
Production Meetings, Reviews and Metrics
Startup Meeting The contractor shall conduct a program start up meeting NLT 60 days ACA IAW DID DI-ADMN-81249B, Conference Agenda, (CDRL A003), using existing start up procedures and policies for the contractor. No policies or procedures shall be waived without government approval. The startup meeting shall establish the baseline for the program. Special emphasis shall be placed on RAID (Risks, Assumptions, Issues and Dependencies) log, review milestones. The contractor shall provide a conference report to include all artifacts NLT 5 days after the conclusion of the startup meeting IAW DI-ADMN-81308A, (CDRL A004).
System Metrics The contractor shall develop and implement a plan for managing this contract using quantifiable metrics. All reporting of metrics will be shown as trends with planned versus actual data points. All metrics will be updated as a minimum monthly. All metrics required in the SOW shall also be included in the plan. The plan shall have metrics for both production and new development efforts. The plan shall contain sample presentations of all metrics. The plan shall also contain a matrix showing the metric, the source of all data, the owner of the metric, frequency and level of review by the contractor IAW DI-MISC-80508 (CDRL A005). For a 12 month moving window forward and a 6 month moving window into the past, production metrics shall include schedule and quality metrics to monitor the effectiveness of the contractor’s manufacturing, quality, and subcontractor/supplier management programs. As a minimum, production metrics shall include below:
· IBCS Hardware System Line of Balance (LOB)
· IBCS Hardware System second order LOB
· Touch Labor
· Support to touch labor
· GFE delivery LOB
· ATP discrepancies and resolution
· Production and Quality Metrics
· Waivers and deviations
· SCARS and CARS by vendor
· Contractors internal metrics for production
Manufacturing Management Program (MMP) The contractor shall develop and implement a MMP that meets the requirements of Society of Automotive Engineers (SAE) standard AS6500. The contractor shall document this program as part of their MMP IAW DI-MGMT-81889 (CDRL A006). The contractor shall include its plan for Manufacturing Readiness Assessments (MRAs) in the MMP. In accordance with AS6500, the contractor shall maintain a manufacturing surveillance process.
Integrated Program Reviews (IPRs) The contractor shall conduct IPRs with Government program personnel on a quarterly basis (location). The reviews shall cover the latest status of overall contract effort with emphasis on problems and achievements in all program areas to include the following: program metrics, costs, schedules, and risk. The contractor shall provide Review Packages (CDRL A007) IAW DI-ADMN-81373 and Meeting Minutes (CDRL A008) IAW DI-ADMN-81505 for all reviews.
Quality Quality Assurance (QA) Program The contractor shall maintain a quality system IAW current versions of ISO 9001, AS 9100, or equivalent system as agreed between the contractor and the Government. Any exclusion to the contractor’s quality management system shall be agreed to between the contractor and the Government. The contractor shall make available, for review by the Government, quality system procedures, planning, and all other documentation and data that comprise the contractor's quality system. The Government may perform any necessary inspections, audits, or evaluations to confirm conformance to requirements and adequacy of the quality system. Quality system procedures, planning, and all other documentation and data that comprise the contractor's quality system shall be made available to the Government via the contractor’s CSA system.
Program Product Assurance Plan The Contractor shall develop and implement a Government approved Program Product Assurance Plan (PPAP) IAW DI-QCIC-81722 (CDRL A009), that provides for effective application and integration of Quality Assurance, Reliability, and Parts Management principles and integration with other disciplines such as configuration and data management, systems engineering, design, test and logistics, to maintain the integrity of SoS Products. The PPAP shall describe the methodology used throughout all phases of the program (development, fabrication, test, delivery, and post-delivery support) to meet the quality requirements for this program. The contractor shall provide a quality program, and all inspections/tests required by the contract requirements are contained in the contractor’s production planning and manufacturing methods.
Corrosion Prevention and Control The contractor shall implement a Corrosion Prevention and Control Plan (CPCP) as a part of the PPAP (CDRL A009), using the DOD Corrosion Prevention and Control Planning Guidebook (https://www.corrdefense.org/Default.aspx) as guidance to ensure Corrosion Prevention and Control is addressed as part of the design of MEI improvements.
GFE Management.
The contractor shall manage the integration of GFE onto the production line and identify any potential GFE shortages 90 days before the need date on the production line. The contractor shall identify work arounds for any late or deficient GFE that will still allow for delivery of the MEI.
Property Records The contractor shall create and maintain records of all property accountable to the contract, clearly identifying between Government Furnished Materiel (GFM) and Contractor Acquired Property (CAP).
Property Accountability The contractor shall perform property administration IAW FAR 52.245-1, Government Property, to manage and account for Government property accountability. The contractor shall identify and inventory Government property accountable to the contract IAW DI-MGMT-80441 (CDRL A010).
Disposition of Property The contractor shall account for all excess or shortages of GFM and request disposition instructions via the Plant Clearance Automated Reutilization Screening System (PCARSS) IAW DFARS 252.245.7004.
Configuration Management System & Audits CM Program The contractor shall establish and implement a CM program IAW EIA-649-1 to manage the configurations provided under this contract. The program shall consist of configuration identification, configuration change control, configuration audits and reviews, configuration status accounting and data management. The contractor shall prepare and deliver CM Plan (CMP) IAW DI-SESS-80858 (CDRL A011).
Configuration Change Management The contractor shall only change the Government-controlled CD as a result of a Government approved Engineering Change Proposal (ECP). ECPs apply to hardware and firmware changes. The contractor shall prepare an ECP only after the Government has authorized preparation by an approved Change Request or by Government direction. The contractor shall prepare and deliver ECPs IAW DI-SESS-80639 (CDRL A012) with Notices of Revision (NORs) prepared IAW DI-SESS-80642 (CDRL A013). The contractor shall document all revised Government-controlled CD on an Engineering Release Records approved by the Government. The contractor shall prepare and deliver ERRs IAW DI-SESS-80463 (CDRL A014). The contractor shall update and deliver any TDP updates IAW DI-SESS-80776 (CDRL A015) and the associated TDP Selection Option Worksheet. The contractor shall prepare and deliver updates to interface control documents (ICDs) IAW DI-SESS-81248 (CDRL A037). The contractor shall prepare and deliver updates to system and subsystem specifications IAW DI-IPSC-81431 (CDRL A038).
Request for Variance (RFV) The contractor shall prepare an RFV IAW DI-SESS-80640 (CDRL A016) against Government controlled documentation for any deviations.
Serialization, Lot and Block Control The contractor shall develop and implement a system for serialization and lot control IAW the approved IBCS CMP (CDRL A011). The contractor shall use this program for manufacturing, identification of required hardware, and lot and block control of hardware to be delivered under this contract. Furthermore, the contractor shall develop and register DoD Item Unique Identification (IUID) data IAW MIL-STD-130, and deliver via Wide Area Workflow by submitting an XML file or flat file through the Global Exchange Service or manually via the IUID Web Entry Site at http://www.bpn.gov/iuid.
Failure Reporting, Analysis, and Corrective Action System & Failure Review Board The contractor shall maintain/implement a FRACAS. All suppliers shall develop and implement a compatible FRACAS that supports the contractor’s FRACAS. The contractor shall track all hardware, firmware, and OIV/FCN failures to include Government Furnished Equipment (GFE), and shall include Government generated Failure Reports (FR) in the FRACAS. The contractor shall participate in a weekly Failure Review Board (FRB), jointly conducted by the contractor and the IAMD Project Office. The joint FRB will review and assign failures, and the contractor shall present associated failure trend data. Within 45 days after notification from the IAMD Project Office, the contractor shall perform failure analysis on each failure, excluding GFE, and respond to the IAMD Project Office with identification of root cause, a corrective action recommendation, a corrective action implementation and verification plan, and any associated schedule impacts. The contractor shall support the IAMD executive FRB. The contractor shall apply the FRACAS results into the design, production, and logistics processes. The planned FRACAS approach shall be included in the PPAP (CDRL A009).
Configuration Audits and Reviews Physical Configuration Audit (PCA) The contractor shall conduct PCAs / Delta PCAs for all major subassemblies at the time of the first article inspection to validate the PBL documentation. The contractor shall conduct an IBCS system level PCA to validate the final PBL documentation for each end product. The contractor shall prepare an IBCS PCA Plan IAW DI-SESS-81646 (CDRL A017).The contractor shall prepare a PCA Report IAW DI-SESS-81022 (CDRL A018). The Government may choose to co-chair all audits as a voting member.
Configuration Status Accounting (CSA) The contractor shall perform a CSA function IAW the contractor's Government approved IBCS CMP. The CSA data and information shall be recorded and reported for all CD. The CSA system shall depict the as-designed, as-built, and as-modified configurations and shall be indexed for ready reporting and retrieval. The contractor shall provide the Government with on-line access to the CSA system.
Data Management The contractor shall implement a data management program to control and track the delivery of data items required by the CDRL, DD Form 1423. The contractor shall host a Government accessible website to use for the on-line delivery of all CDRL items and deliver CDRLs formally to the Government via a Government hosted website.
Data Accession List The contractor shall prepare a Data Accession List (DAL) IAW DI-MGMT-81453 (CDRL A019) of all documentation developed as part of the effort. The contractor’s CM office shall provide individual documents listed on the DAL at the Government’s request. Upon notification from the Procuring Contracting Officer, the contractor shall furnish a copy of any DAL Requested Documentation IAW DI-MISC-80508 (CDRL A020).
Data Item Master Schedule The contractor shall provide a Schedule for Data Items IAW DI-MISC-80508 (CDRL A021). The schedule shall detail the previous month's submittals and data items forecasted to be delivered for the following month.
Manufacturing The contractor shall develop and maintain production facilities and tooling necessary to meet a minimum production capacity of 12 EOC/ECT, 12 ICE, and 24 Relays per year on a 1/8/5 basis. The contractor shall provide a Production Capacity Plan to surge up to a maximum production capacity of 68 EOC/ECT, 43 ICE, and 58 Relays per year. Contractor generated, maintained, or implemented producibility analysis documentation conducted during the IBCS program shall be available for Government review.
Parts, Materials and Processes (PMP) The contractor shall implement, and maintain, or comply with and maintain, a program that defines the criteria, procedures, and processes for the management and control of PMP.
PMP Plan The contractor shall develop and execute a PMP Plan IAW DI-STDZ-81993 (CDRL A022). The PMP Plan shall address the requirements of MIL-STD-11991 and describe the parts and materials selection process, responsibilities for the evaluation, documentation and notification of part changes, manufacturing processes, and material changes. This process shall address allocation of system performance requirements to parts and materials requirements, consideration for performance tolerances, and define parts and materials qualification requirements that assure meeting system performance and reliability requirements. In addition, the Plan shall include flow-down requirements for parts and materials to suppliers for assemblies procured. The use of any of the problem PMPs listed in MIL-STD-11991, Appendix C, shall require Government approval.
PMP Program The PMP program shall ensure that the following: Parts performance, reliability, quality, and safety meet system performance requirements for the worst case system non-operating and operating environments over the system life cycle IAW the applicable CIDS found in the data library. Parts shall not be used outside vendor specifications without prior Government approval. Materials used shall produce equipment that meets system hardware performance requirements IAW the applicable CIDS for each respective delivered end item found in the data library. The PMP program shall include the necessary design effort, selection of materials, delineation of applicable finishes, techniques for deterioration prevention, and appropriate test programs to verify deterioration control. Finishes and coatings shall be applied as necessary to provide corrosion/deterioration protection. The paint system shall provide Chemical Agent Resistant Coating (CARC) characteristics. Manufacturing processes used to manufacture electronic hardware shall yield assemblies and equipment that meet system performance requirements of the CIDS. The PMP program shall describe the materials, methods, and verification criteria for producing quality electrical interconnections and assemblies and shall use process control methodologies for the planning, implementation, and evaluation of the manufacturing processes. Soldering shall comply with J-STD-001, class 3, and IPC-A-610, class 3. Cable and wire harness assembly workmanship shall meet the IPC/WHMA-A-620, class 3 standard, at a minimum.
Commercial Off-the-Shelf (COTS) Management Plan The contractor shall prepare, or update an existing, Commercial Off-the-Shelf (COTS) Management Plan for submittal and approval as a portion of the PMP Plan. The Plan shall meet the requirements of EIA-933.
Lead Free Control Plan (LFCP) The contractor shall prepare, or update an existing, Lead Free Control Plan (LFCP) for submittal and approval as a portion of the PMP Plan. The requirement for a Lead Free Control Plan shall be flowed down to suppliers of equipment that may include lead-free materials. The LFCP shall be IAW GEIA-STD-0005-1, “Performance Standard for Aerospace and High Performance Electronic Systems Containing Lead-Free Solder” or its equivalent. In addition, the LFCP shall also include tin whisker mitigation plans in accordance with GEIA-STD-0005-2, “Standard for Mitigating the Effects of Tin Whiskers in Aerospace and High Performance Electronic Systems” or its equivalent, at control level 2C or equivalent. The contractor shall include in the LFCP any 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.
Non-Conforming Material The contractor shall notify and request approval from the Government via the Procuring Contracting Officer (PCO) for acceptance or use of nonconforming material (variances from contractor drawings and specifications). The contractor shall use a Material Review Board (MRB) process to document, evaluate, and recommend disposition of nonconforming material. The contractor shall prepare Standard Repair Procedures if so desired with approval by the Government IAMD Performance Management Directorate (PMD) Director prior to use. The non-conformance process shall include analyses of nonconforming material to determine root cause, recommendations for and preventive/corrective actions through implementation, and the tracking of nonconforming material dispositions that require a Request for Variance (RFV). The contractor shall include IAMD Project Office (PO) or designee representation on the MRB and shall notify the Government five (5) working days prior to the scheduled MRB. The contractor shall not give a disposition of “use as is” or “repair” through contractor action without Government approval of a RFV. The contractor shall control the identification, documentation, evaluation, disposition, and segregation requirements of non-conforming products. The contractor shall upon discovery, immediately notify the PCO and IAMD PO of any nonconforming material that exists in previously delivered products. Notification shall include a description of the suspected nonconforming material, potential risk or product impact, contract number, Part Number, National Stock Number (NSN), affected serial numbers, and/or lot numbers when applicable.
Counterfeit Parts Prevention The contractor shall prepare, or update an existing, Counterfeit Risk Management Plan IAW DI-MISC-81832 (CDRL A023). The Counterfeit Risk Management Plan shall meet the requirements of SAE AS5553 for electronic items and SAE AS6174 for non-electronic items. The contractor shall procure parts from original manufacturers or the original manufacturers’ franchised distributors. The contractor shall report counterfeits and suspected counterfeits to the Government and in the Government Industry Data Exchange Program (GIDEP), in accordance with the GIDEP Operations Manual, SO300-BT-PRO-010 and track using a risk mitigation plan or countermeasure to eliminate the problem.
Environmental Stress Screening (ESS) The contractor shall implement and maintain a manufacturing ESS program that includes ESS profiles (temperature cycling, vibration/shock, and power on/off cycling) and the metrics used for evaluating ESS effectiveness. The contractor shall develop an initial list of LRU’s requiring 100% ESS on electrical, electronic, and high failure rate components to include timing units, servers, and uninterruptible power supplies. ESS requirements for COTS vendors shall be determined by the contactor, with Government approval, for COTS vendors without an ESS program as part of their existing manufacturing process. The contractor may request Government approval to reduce to ESS sampling or discontinue ESS with supporting rationale. ESS for COTS hardware may be performed at the original equipment manufacturer production facility. GFE, at the standalone level, is not required to receive ESS. The Government may recommend performing ESS at the MEI level. The ESS Plan shall be included as part of the PPAP (CDRL A009).
Manufacturing Readiness Assessments The contractor shall conduct assessments of manufacturing readiness in accordance with AS6500 with the Manufacturing Readiness Level (MRL) 9 evaluation criteria to take place approximately 120 days prior to Full Rate Production Decision at the contractor’s facility. The contractor shall provide all required resources to demonstrate that they meet the criteria of an MRL 9. The contractor shall lead the assessments at subcontractors/suppliers to include government participants. The contractor shall notify the Government at least 15 working days prior to the activity at each of the subcontractors/suppliers. The contractor shall identify high risk sources of supply, long-lead items, obsolescence issues, as well as other manufacturing risks. The selection of subcontractors/suppliers to be reviewed will approved by the Government. The contractor shall develop and implement manufacturing maturation plans or their equivalent for areas in which the MRL is lower than the target MRL 9 for full rate decision. The contractor shall monitor and provide status at all program reviews for in-house and supplier MRLs and shall re-assess MRLs in areas for which design, process, source of supply, or facility location changes have occurred that could impact the MRL. The contractor shall be responsible for the closure of all issues identified during the MRAs at their facility and the subcontractor/supplier facilities. The contractor shall document findings of the MRAs in the Assessment of Manufacturing Risk and Readiness IAW DI-SESS-81974 (CDRL A024). All MRA findings shall be closed by the Production IPT, or accepted as a risk by the Government NLT 30 days prior to full rate production decision
Production Line Validation (PLV) Planning The contractor shall prepare and deliver a Production Line Validation Plan IAW DI-MISC-80508 (CDRL A025). The PLV plan shall be used to verify and demonstrate manufacturing planning and prove out the manufacturing processes, tooling, test equipment, work instructions, and test procedures. The PLV Plan shall include a procedure and associated criteria for the conduct of prime/subcontractor/vendor PLVs. The contractor shall correct manufacturing issues identified in order to reduce the risk. These corrections are defined as either improving upon the existing processes, implementing an alternate process, or identifying the issue as an acceptable risk per the contractor’s analysis to proceed forward without changing. This plan shall include any portion of the supply chain, including the prime contractor, meeting the conditions for PLV, which are defined as significant changes that effect personnel, facilities, equipment, tooling, and test equipment used for fabrication of the hardware, or a lapse in production of 12 months or more. In the event of a significant change occurring subsequent to the initial PLV Plan submittal, the contractor shall provide a recommendation to address the change, and the Government/contractor team will mutually agree to a path forward. The contractor shall prepare a report with the detailed manufacturing and process data supporting the PLV and submit IAW DI-MISC-80508 CDRL (A026).
Production Line Validation (PLV) Execution The contractor shall conduct PLVs using the production hardware to record the processes, documentation, tooling, and test equipment used during fabrication of the production hardware. The contractor shall notify the Government at least 15 business days in advance when major production line validation, demonstration, and prove out activities are scheduled so the Government may participate. The contractor shall conduct PLV activities at critical vendor facilities and prime contractor’s facilities. The contractor shall maintain PLV documentation as baseline documentation and it shall be available for Government review upon request. PLV criteria shall be defined and governed by the PLV procedure documented in the PLV Plan.
Vendor and Subcontractor Control The contractor shall develop, implement, and maintain a supplier quality control program to include supplier scorecard and describe subcontractor and vendor quality provisions as part of the PPAP (CDRL A009). The contractor shall assure the qualification of all suppliers and maintain an Approved Vendor List (AVL), or equivalent, with the procedures for additions to the AVL described in the PPAP (CDRL A009).
Qualification The contractor shall verify all hardware and firmware items are fully qualified and suitable for production and fielding to requirements IAW the applicable CIDS for each respective delivered end item found in the data library. The Government will deliver qualified IBCS software for the contractor to use in the hardware qualification. For changes to the qualified baseline, the contractor shall notify the Government as a part of the ECP process. The contractor shall prepare a qualification test plan and report IAW DI-NDTI-80566 (CDRL A027) and DI-NDTI-80809 (CDRL A028) that defines the contractor’s plan to qualify hardware at the LRU and MEI level. New designs or redesigns (hardware), process changes, a break in production of greater than 12 months, the move of the production line, or new vendor constitute a change to the qualified baseline.
Product Acceptance Configuration Acceptance Prior to conducting the acceptance test for any hardware, the hardware end items configuration has been validated on the HCS by meeting all the requirements of Attachment 04 and Attachment 05.
Acceptance Test Plan & Procedures The Acceptance Test Procedures are included as Attachment 04. The contractor shall update the Acceptance Test Procedures IAW DI-NDTI-80603 (CDRL A029). The contractor shall develop and maintain Acceptance Test equipment for each MEI and include this approach in the Acceptance Test Plan (ATP) IAW DI-QCIC-80553 (CDRL A030). The contractor shall perform acceptance testing on all hardware end items using the Acceptance Test Equipment, Acceptance Test Procedures, and Acceptance Test Plan prior to delivery to the Government. For vendor/subcontractor supplied COTS items that are to be used as spares, Certificates of Conformance and test reports/records from the supplier are acceptable to satisfy acceptance test requirements. The contractor shall request Government approval for changes to the Acceptance Test Plans, Acceptance Test Procedures, and associated equipment, to include SIE/STE. The contractor shall notify the Government at least five (5) working days prior to conduct of each Acceptance Test event in order for the Government to witness the testing.
The MEI Acceptance Test event shall:
| 1) identify that the hardware component is built according to the TDP, to include Government approved changes |
| 2) integrate the IBCS software (provided as GFS) configuration items (tactical SW, OIV, FCN) correctly by exercising system functionality as defined in the MEIs’ Acceptance Test Procedures. Attachment 04. |
The Acceptance Test Procedure results/reports, including supporting documentation and data that comprise the report, shall be made available to the Government via the CSA system.
SIE/STE Validation All SIE/STE and associated software and documentation will be validated by the Government prior to use for accepting End items and LRUs. The contractor shall verify the SIE/STE is ready for validation and notify the IAMD Performance Management Directorate a minimum of five (5) working days prior to scheduled validation. If SIE/STE is used by the contractor, the contractor shall develop an SIE/STE Validation Plan IAW DI-MISC-80759 (CDRL A031).
4.15 LOGISTICS FOR PRODUCTION
Production Engineering Support The contractor shall execute product engineering services by direction of a TO/DO and negotiated on a case-by-case basis based on the information contained in the contractor’s CLASS I Engineering Change Proposal (ECP) response prior to production. ECPs shall include program management, systems engineering (to include safety and cybersecurity), operations and support labor, IBCS hardware end items modifications, integration, component replacement, manufacturing readiness, test, logistics, and IBCS support in response to changes deemed necessary to achieving a LRIP and FRP decision or an exportable configuration.
ECP Process Preliminary ECP Preliminary ECPs shall be prepared and submitted to the Government in accordance with DI-SESS-80639 (CDRL A012).Preliminary ECPs must be dispositioned (approved or disapproved) before development of a Formal Class I ECP by a properly constituted Government Configuration Control Board (CCB) chaired by the IFMC Chief Technical Officer or their designated Government representative. Preliminary ECPs shall at a minimum address all applicable “Effects on Engineering, Support, and Other Product Attributes” as identified on page 3 of the ECP DD Form 1692 to include, but not limited to: the resourced loaded IMS, cost estimate, and design concept.
Class 1 ECPs The contractor shall use content in “DD Form 1692” or equivalent for assigning a Major (Class I) or Minor (Class II) classification to an ECP. Class 1 ECPs shall be prepared and submitted to the Government in accordance with the configuration management requirements of the SOW paragraph 4.10.2. Class I ECPs must be dispositioned (approved or disapproved) for implementation by a properly constituted Government Configuration Control Board (CCB) chaired by the IFMC Project Manager or their designated Government representative. Class 1 ECPs shall at a minimum address all applicable “Effects on Engineering, Support, and Other Product Attributes” as identified in DD Form 1692 to include, but not limited to: recommended design, recommended material, recommended supply source, recommended configuration documentation updates, safety and cybersecurity, recommended logistics documentation update, training device updates, recommended logistics package and support, IP associated with design, delivery schedule, tests, tests documentation, evaluation and operational advantages of design, non-reoccurring engineering cost, labor mix and cost, material cost, unit cost and design reviews.
Upon auditing, fact-finding, and/or negotiating the final price associated with the ECP, the Government will issue a separate TO/DO by which the contractor shall implement the proposed change. Upon approval of the formal Class I ECP the contractor shall update the existing government logistic products as required in Section 6 (Logistics) of this SOW.
Potential Class I ECP Candidates.
The contractor shall submit preliminary ECPs for the Network Enclosure Assembly (NEA) Design Approach, Cooperative Aviation Surveillance System (CASS) to Passive Detection and Reporting System (PDRS) Design Approach, and Joint Tactical Terminal Senior (JTT SR) to JTT Integrated Broadcast System (JTT IBS) Design Approach. Per Attachment 14 (Preliminary Class I ECP Candidates). These new capabilities shall be addressed in the production start up meeting and at all Program Reviews.
Class II ECP Process Unless otherwise specified within the SOW, the government administrative contracting officer or plant representative serves as the dispositioning authority for Class II ECPs.
Test Documentation The contractor as part of the ECP deliverable shall provide a test plan IAW DI-NDTI-80566 (CDRL A027) and a test report IAW DI-NDTI-80809 (CDRL A028) documenting the testing and results.
ECP Testing The contractor shall conduct tests, analyses, inspections, or demonstrations to verify all of the ECP requirements. The contractor shall sufficiently identify all planned component level performance and qualification testing and conduct them in accordance with the most current versions of applicable MIL-STDs. The contractor shall coordinate with the Government for all test schedules and notify the Government of all contractor test readiness reviews and testing events at least 5 days prior to occurrence. The Government will reserve the right to witness all contractor conducted testing. All Test Incident Reports (TIRs) written by the contractor during Contractor testing will be provided as part of each Test Report to include resulting failure analysis and/or corrective action.
Post Test Reviews The contractor shall support Post Test Reviews (PTR)s after the completion of contractor led test activities, with preliminary reviews held within 72 hours of test completion and a detailed PTR held 30 days after test completion.
Hardware Control System (HCS).
The HCS consist of Government provided EOC, ICE and Relay. The HCS is the approved initial HW baseline. The contractor shall demonstrate and evaluate all proposed form, fit, function changes on the HCS prior to implementation.
HCS Configuration The government provided system, as defined in Attachment 03, shall always be maintained in the current production hardware and software configuration, this includes firmware. The contractor shall maintain a DCSA accreditation for the HCS. The contractor shall be the configuration manager of the HCS.
HCS Purpose The purpose of the HCS is to enable system synchronization, performance testing of new parts to replace obsolete parts, prove out of new capability, validation of the IBCS Hardware End Items (EOC/ECT, ICE, Relay, B-Side Processor) level ATP, and prove out of software. The Government will provide the latest software version to the contractor.
HCS Prove Out IBCS Hardware and software Prove Out. Within 30 days after acceptance of the HCS the contractor shall demonstrate that the IBCS Software (IBCS application, OIV, and FCN) can be loaded and be functional on the HCS in accordance with Attachment 05 (Software Installation Instructions) and attachment 04 (ATP). The test report shall be prepared IAW DID DI-NDTI-80809B (CDRL A028). All discrepancies shall be resolved prior to Government acceptance of any hardware from the production line.
IBCS Synchronization System synchronization is the management of IBCS hardware and software integration to ensure consistency in product acceptance, support of fielded systems, implementing new capability growth and support of Government simulation labs.
IBCS synchronization Plan The contractor shall develop and execute an IBCS Synchronization Plan IAW DI-MISC-80508, (CDRL A033) for IBCS hardware and software integration to ensure consistency in product acceptance, support of fielded systems, implementing new capability growth and support of Government simulation labs. The content of the plan shall at a minimum address: membership, frequency of meetings, charter, roles, responsibilities, and authorities, methodology and metrics for tracking hardware and software configuration for IBCS. The contractor shall have metrics for both production and new development efforts. All metrics will be shown as trends with planned vs. actual data points and updated at least monthly. Metrics will show the source of all data, the owner of the metric, the frequency and level of review.
Agile Software The contractor shall support the Government’s agile software development. The contractor shall integrate Government Furnished IBCS software configuration items onto the hardware configuration items prior to delivery. Functional testing shall be accomplished with the HCS. For discrepancies between the contractor provided hardware and the Government Furnished IBCS software configuration items, the contractor shall support and aid in the troubleshooting process for integrated system functionality. The contractor shall provide support to the Government IAMD PO SAFe Agile process. The contractor will support work in a team-based SAFe Agile environment. The Government will create and maintain system roadmaps, project plans, and product and release backlogs. The contractor shall provide Level-of-Effort (LoE) support to the Government in the creation of system roadmaps, project plans, and product and release backlogs. The contractor shall apply cadence and synchronization in alignment with the Government's SAFe Agile process to provide weekly meeting support and participation. Contractor shall plan to support a quarterly Performance Improvement Planning meeting in Huntsville AL as well as a weekly teleconference. The support is limited to the contractor providing status on IBCS HW development, progress, troubleshooting assistance, and sprint and system level demonstrations that may or may not affect the Governments SAFe Agile development process.
New IBCS software versions and required IBCS software related inputs.
Prior to incorporation of new IBCS software into the IBCS hardware production line, the software shall be validated on the HCS in accordance with Attachment 04 and Attachment 05. The government will provide all new software versions to the contractor. No software version will be provided that contains level 1 software trouble reports. The government will provide all IBCS software related inputs required by the contactor to satisfy the requirements of the TO1 SOW. Updates will be provided by the Government monthly. The contractor shall assist the government in assuring that any new software versions may be run on all previous hardware configurations.
IBCS configuration control The contractor shall document the current configurations, both hardware (includes firmware) and software, of the previously developed government IBCS systems and all production systems delivered under this contract. The contractor shall document the configuration of fielded systems based upon Government input.
Firmware configuration for the production line The contactor shall notify the Government of any replacement or new part that contains firmware and the respective firmware version. The Government will notify the contractor of any firmware changes required prior to the HCS testing.
OIV/FCN Software Reliability The contractor’s reliability predictions shall include all OIV/FCN software components in the system as identified in the reliability model. The contractor shall use industry accepted OIV/FCN software reliability prediction models. The government will provide the contractor monthly updated software reliability model inputs to be used in the reliability model.
Field Engineering Services (FES) The contractor shall provide FSRs and OSRs to support IBCS equipment at the Government-Systems Integration Laboratory (G-SIL) on Redstone Arsenal (RSA), Mission Integration Lab (MIL) in Andover, MA, Tactical Systems Integration Laboratory (T-SIL) at Tobin Wells (Ft. Bliss), and IAMD Testbed Operations at WSMR, NM during the period of performance.
Field Service Representatives (FSRs) The contractor shall provide FSRs based on system density, including IBCS equipment at the G-SIL, MIL, T-SIL and Testbed Operations during the period of performance. Each FSR shall assist customers with supply, maintenance, transportation, system modifications to include retrofit actions, trouble hotline manning, and other logistics-related issues. FSRs shall be able to operate hardware, troubleshoot, and maintain the IBCS laboratories and testbed equipment. The FSRs shall be the interface between the customer, Government, and contractor ensuring that parts flow to the customer and that retrograde flows back to repair locations. The FSRs shall provide unit operational integration assistance and training as required. When requested, FSRs will teach and/or assist Government and contractor personnel in March Order and Emplacement (MO&E) of MEIs.
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. Updated .