A02 NGLD-M IDIQ PWS_FINAL_02 Dec 2020.docx

PROCUREMENT SENSITIVE

Next Generation Load Device – Medium (NGLD-M) IDIQ Base Performance Work Statement (PWS)

Performance Work Statement For Next Generation Load Device-Medium (NGLD-M)

Indefinite Delivery Indefinite Quantity (IDIQ) Contract

In support of U.S. Army Program Executive Office for Command, Control, Communications – Tactical (PEO C3T) Project Manager Tactical Radios (PM TR)

Table of Contents

PERFORMANCE WORK STATEMENT (PWS)

03 April 2020

1. Contracting Officer’s Representative (COR)

MANDATORY - ALL REQUESTED INFORMATION MUST BE COMPLETED

a. Primary COR.

Name:

Organization:

Department of Defense Activity Address Code (DODAAC):

(refer to the DODAAC web site at https://dodaac.wpafb.af.mil for additional information)

Phone Number:

Fax Number:

E-Mail Address:

b. Alternate COR.

Name:

Organization:

Phone Number:

Fax Number:

E-Mail Address:

2. Contract Next Generation Load Device-Medium (NGLD-M) Engineering Development and Production

2.1 TYPE OF CONTRACT: This requirement is for a Multiple Award, Indefinite Delivery, Indefinite Quantity (IDIQ) contract. Individual Task Orders (TOs) and Delivery Orders (DOs) shall be used to perform individual tasks as defined in this Performance Work Statement (PWS). This effort will be a hybrid-task contract consisting of Cost-Plus Fixed-Fee (CPFF), Firm-Fixed Price (FFP), and/or Fixed-Price Incentive Fee (FPIF) Successive Target Contract Line Item Numbers (CLINs). The FPIF Successive Target may be used for Production DOs if they cannot be competitively awarded.

3. GENERAL SCOPE: Project Manager Tactical Radios (PM TR) currently provides a product and services that provide National Security Agency (NSA) certified Cryptographic Key Load Devices including the Simple Key Loader (SKL). These devices fill, transfer, issue, and manage cryptographic keys to End-Cryptographic Units (ECUs). In 2013, the Army signed a Capabilities Production Document (CPD) for the Next Generation Load Device (NGLD) Family to replace the aging fleet of SKL devices. Program Executive Office (PEO) Command, Control, Communicate – Tactical (C3T) is the Milestone Decision Authority (MDA) for the NGLD-Medium (NGLD-M) and has delegated execution authority to PM TR as an Acquisition Category III (ACAT III) Program of Record (POR).

The NGLD-M provides the functionality of legacy fill devices while providing network connectivity to support Over the Network Key (OTNK) distribution. The NGLD-M will meet NSA certification requirements while providing a reprogrammable crypto subcomponent to meet future modernization requirements. The NGLD-M will also be capable of interfacing with the Management Client (MGC), NSA’s Key Management Infrastructure (KMI), and specific Mission Planning Management Support Systems (MPMSS). The NGLD-M is a KMI aware and Product Delivery Enclave-Enabled (PDE-Enabled) device capable of connecting and receiving key material, applications, and other cryptographic products necessary to complete required operational missions. Key distribution should be accomplished by connection to DoD networks and will contain standard interfaces including a audio fill ports, RJ45 Ethernet ports, and standard Universal Serial Bus (USB).

The NGLD-M shall be engineered, designed, tested, and certified to meet specific Army and customer requirements. These requirements are based on the 22 April 2013 CPD as signed by the TRADOC Capability Manager Networks and Services (TCM N&S) and include production quantities based on the needs of the Army. Additionally, requirements from the National Security Agency (NSA) including the Technical Security Requirement Document (TSRD) and Information Assurance Security Requirements Document (IASRD), as well as others from other services including the Navy, Air Force, Other Government Agencies (OGA), and foreign military sales. OGAs include the Federal Bureau of Investigation (FBI), Department of Homeland Security (DHS), and state/local entities. The Army is the executing agent of this effort, but other participants mentioned above will be key stakeholders in the requirements generation, management, and test planning and execution.

Concurrently with the NGLD-M platform development, the government is developing NGLD-M User Application Software (UAS) through a separate effort. The contractor is encouraged to use the Government developed UAS, however, the contract has the option to develop their own UAS for the NGLD-M.

If the contractor does not opt to use the government developed UAS, the contractor will develop the NGLD-M in its entirety to include hardware, underlying software (e.g. Operating System (OS), firmware etc.), and the UAS as defined in the NGLD-M requirements documents. The NGLD-M System Requirements traceability matrix allocates each requirement to either UAS, Hardware or both.

If the contractor opts to use the government developed UAS, the government will define UAS API(s) that contractor(s) shall integrate with the NGLD-M platform designed under the multiple IDIQ contract. The contractor shall design the NGLD-M to meet the hardware requirements including underlying software (e.g. OS, firmware etc.) and integrate the government developed UAS with the contractor developed NGLD-M platform.

The REprogrammable Single Chip Universal Encryptor (RESCUE) Technical Data Package (TDP) is available to industry offerors as an option to meet the crypto subcomponent requirements for the NGLD-M platform, but the Government is not requiring the use of the RESCUE. The government is not responsible for any modifications required to RESCUE to meet the NGLD-M crypto subcomponent requirements.

4. Objectives The contract requires the development, management and production/sustainment of the NGLD-M to meet to the intended requirements outlined in the CPD for the medium variant NGLD Family. Further objectives of this effort are to acquire from the contractor, through this base contract, additional TOs and DOs in the following:

1. Management: Management is included and incorporated within any TOs or DOs that outlines the management services for that Period of Performance.

2. Engineering Development: Engineering development outlines specific engineering tasks for the developmental phase. The engineering development includes the delivery of Low Rate Initial Production (LRIP) units.

3. Sustainment : Based on the NGLD-M solution, the Government will development a TO that defines the required sustainment services that shall not exceed the scope of the base IDIQ contract.

4. Production: Deliveries of individual units will be directed by individual DOs. The production DOs will produce NGLD-M In Accordance With (IAW) the government agreed upon design and meet Full-Rate Production (FRP) capacity.

5. Scope The NGLD-M effort shall be divided into four (4) distinct functions that include, but not limited, to Program Management (applies to all portions of this PWS), Development and Engineering Services, Production, and Sustainment Services as outlined below:

Program Management

· Contractual Reports

· Work Breakdown Structure (WBS)

· Integrated Master Schedule (IMS)

· Monthly reporting

· Risk Management

· Meetings and Conferences

· Program Protection

· Information Assurance (IA) and Risk Management Framework (RMF)

· Configuration Management

· Property Management

· Manpower and Personnel Management

· Computer Resources Development and Engineering Services

· Engineering Support Services

· Testing and Test Support

· Technical Data Package (OPTION to buy)

· Operations and Maintenance Manual and Training Development

· New Equipment Training (NET)

· Quality Assurance/Quality Control

· Information Assurance (IA) and Risk Management Framework (RMF)

· NSA Certification

· Engineering Design Models (EDMs)

· Pre-Production Units (PPUs)

· Safety Assessment

· Support Equipment Production

· Low-Rate Initial Production (LRIP)

· Full Rate Production

· Quality Assurance/Quality Control

· Packaging, Handling, Storage, Transport

· Inspection and Acceptance

· Parts, Spares, Components,

· Certified IUID markings

· Long-Lead Items Sustainment Services

· Hardware and Software Sustainment

· Product Support

· Obsolescence Management

· Maintenance and Repairs

· Operator and Maintenance Manuals Management

· Warranty Repairs

· Operations and Maintenance Training and Training Material Management

· Sustainment Product Management

· Support Equipment Management This PWS provides for general requirements applicable to all TOs and DOs. Specific requirements will be defined in subsequent, individual TOs and DOs. For production DOs, quantities and ship locations shall be outlined in the individual DO. Engineering and sustainment specific requirements will be outlined in the individual TOs.

The Government may require production surge during the base or any option period. Production surge will not exceed 10% of the total production quantity. Any acceleration of the rate of delivery called for under this contract, at the price or cost established before the contract award or to be established by negotiation. The contractor shall provide within 30 days of award a delivery schedule showing the maximum sustainable rate of delivery for the units.

5.1 Applicable Documents Applicable documents are cited throughout this PWS and will be cited as necessary in the individual TOs or DOs. The most current version of documents at the time of the TO or DO issuance will take precedence.

Table 1

A separate DD Form 1423 Contract Data Requirements List (CDRLs) for applicable Data Item Descriptions (DID) shall be in both this PWS and/or itemized in individual TOs or DOs.

6. Performance Requirements The contractor shall provide the required materials and services under the base PWS, along with the requirements within each TO and DO. Follow-on TOs may include any combination of the tasks or subtasks defined in the paragraphs below. All tasks will be specifically defined in each subsequent DO and TO.

The government will provide technical direction and clarification if conflicts between the contract and specifications arise. In addition, the contractor shall immediately identify to the Contracting Officer (KO) any outdated specifications and a proposed revised or replacement specification, if required with the understanding that any changes made may require the KO to do a contract modification.

6.1 Program Management

The contractor shall manage all aspects of the contractor’s responsibilities as defined in the base contract and all TOs and DOs. The contractor shall appoint a Program Manager (PM) who shall have full authority over supporting staff for the Program (the Program Team) and shall be responsible for the day-to-day management, planning, resourcing, scheduling, monitoring, and controlling of the work to be performed. Program management will apply to all phases of this effort. The PM shall be the primary Point of Contact (POC) between the Government and the contractor concerning all program matters.

The contractor shall provide overall management and technical direction to include program planning, management control and reporting, quality management, schedule management and control, configurations management and control, risk management, data control, coordination, reporting and administration to ensure the performance of the efforts delineated in this PWS. The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The performance information reported by subcontractors shall be incorporated and integrated into the contractor's management system. The contractor shall review and assure the validity of all subcontractors reporting.

The contractor shall maintain continuity of operations during the duration of the base contract and awarded options.

The contractor shall provide any contractor prepared brochures, advertisements, or other marketing materials concerning the work developed under this contract at least 60 days prior to distribution for approval by the Government.

6.1.1 Integration Management Control Planning The contractor shall provide the technical and functional activities as required for integration of all tasks specified within this PWS. The contractor shall include productivity and management methods such as quality assurance/quality control, progress/status reporting and program reviews. The contractor shall provide the centralized administrative, clerical, documentation and related functions.

6.1.2 Task Order Management The contractor shall prepare a TOs and DOs Management Plan describing the technical approach, organizational resources and management controls to be employed to meet the cost, performance, and schedule requirements throughout contract execution. The contractor shall provide a plan that will deliver monthly status reports monitoring the quality assurance, progress, status and program reviews throughout contract execution.

6.1.3 Contractor’s Progress, Status and Management Report The contractor shall provide a Monthly Progress/Status Report. The program management and controls system employed will provide the Government with in-depth, accurate, and timely visibility into the contractor’s technical, schedule cost performance, and status IAW this PWS. The Contractor shall submit reports detailing the overall summary of the program health along with any risk and issues should any arise during the course of program execution. Monthly reporting requirements include:

· Problems and corrective actions taken. Also, include issues or concerns and proposed resolutions to address them

· Personnel gains, losses, and status (security clearance, etc.)

· Schedule (show major tasks, milestones, and deliverables; planned and actual start and completion dates for each)

· Summary of trips taken, conferences attended, etc. (attach Trip Reports to the monthly status report (MSR) for the reporting period)

· Accumulated invoiced cost for each CLIN up to the previous month

· Projected cost of each CLIN for the current month

· Monthly Report for cost expenditures (planned and executed) to include percent disbursed to date and average monthly burn rate

6.1.4 Status Report The contractor shall provide a Status Report. The funds and manpower report shall be submitted monthly to provide Government visibility into contractor expenditures for labor, materials, travel, and other contract charges. The report tracks these expenditures against baseline values and provides to completion estimates. The contractor shall provide to the Government a monthly spend plan (spreadsheet) that provides both actual costs and projected costs on a month to month basis for the entire Period of Performance (PoP). This spend plan shall be a living document that shall be updated and adjusted based upon costs incurred and projected out.

6.1.5 Program Management Reviews (PMRs) The contractor shall prepare for and present to the Government, Program Management Reviews (PMRs). PMRs will be held on a quarterly basis. The Government will use the PMRs to assess the status of the program against the approved program plan. The contractor shall provide their Integrated Program Management Reports (IPMR) and Integrated Master Schedules (IMS) as indicated in the individual CDRLs. The contractor shall present the following information at PMRs in Microsoft Word and Microsoft PowerPoint:

· Accomplishments since last review

· IMS Review

· Four-level Work Breakdown Structure with allocated resources to each level

· Current program schedule compared to the program MP IMS

· Budgeted Cost for Work Performed (BCWP)*

· Budgeted Cost for Work Scheduled (BCWS)*

· Actual Cost of Work Performed (ACWP)*

· Actual Cost of Work Scheduled (ACWS)*

· Budget at Completion (BAC)*

· Contractor Estimate at Completion (EAC)*

· Cost and Schedule Variances (CV)* and (SV)*

· Status against individual incremental funding allotments

· Cost and Schedule Efficiencies

· Overall Statuses: Percent Schedule, Percent Complete, Percent Spent

· Cost and Hours Expenditure status

· Risks and mitigations

· Accomplishments planned for next review

*These items are traditionally required for Earned Value Management (EVM). These items are required within this PWS, but note that no certified EVM system is required for this effort.

PMRs shall be conducted at the contractor's facility or via Video Teleconference (VTC), as determined by the Government Program Management Office (PMO). Dates of these reviews shall be mutually established between the contractor and the Government. The contractor shall take minutes and shall prepare a report on meetings with the Government, to include significant decisions made via telephone. The report shall include a list of attendees, meeting results, open/closed action items, and copies on all presentations materials.

The contractor shall review the overall program status to include technical progress, schedule, and data items as depicted on a prearranged agenda established by the contractor, in coordination with the Government. The reviews shall address significant technical accomplishments or failures to achieve progress, results of trips and meetings, major issues, status of action items, status of overall contracted effort, and upcoming critical events. The final status review and report shall summarize the entire program, including the major technical and schedule accomplishments of all phases of the program.

6.1.6 Integrated Master Schedule (IMS) Contractor Milestone schedule and IMS shall be incorporated into contract award. Any post award deviations or time extensions necessary shall be provided to the Government with justification for approval.

The contractor shall prepare and maintain an IMS which indicates start dates, completion dates and dependencies for all critical project tasks and sub-tasks described in this PWS. Microsoft Office Project 2013 or software compatible file shall be used to develop the IMS. Microsoft Office PowerPoint 2013 shall be used to develop the Milestone schedule to show high level program activities. Schedule slips shall be a consideration in all program decisions, and the contractor shall notify the Government of possible adverse schedule variances. The IMS shall contain activity names, durations, start and finish dates, and coding to identify the type of activity (e.g., design, test, material procurement, fabrication, hardware delivery) and index to the WBS. The IMS shall be used in conjunction with the Monthly Performance Report, and shall be updated and submitted to the Government on a quarterly basis for review and comment.

6.1.7 Risk, Opportunity, and Issue Management Plan The contractor shall implement a formal risk, opportunity, and issue management process for the scope of the base contract and options. This process will be closely integrated with existing cost, schedule, and technical performance. The contractor shall conduct and maintain a Risk, Opportunity, and Issue Management Plan as part of the NGLD-M program using best-practices from, “Department of Defense Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs,” January 2017 or most recent version. Risks, opportunities, and issues shall be identified and categorized for both probability and consequence. The risk, opportunity, and issue management program shall consider all performance and schedule elements relating to this effort.

6.1.8 Risk, Opportunity, and Issue Management Report The contractor shall provide a monthly Risk, Opportunity, and Issue Management Status Report using best-practices from, “Department of Defense Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs,” January 2017 or most recent version.

6.1.9 Work Breakdown Structure (WBS) The contractor shall provide an overall WBS with a minimum of four (4) levels. The intent of the WBS is to document the contractor’s deliverable products and contract scope of work. MIL-HDBK – 881 serves as the basis for developing the WBS.

6.1.10 Meetings and Conferences The contractor shall attend and participate in meetings, conferences, program status, design and production reviews in support of this effort as required and approved by the Government. The contactor shall prepare in advance technical documentation for formal briefings to the designated Government representative. The briefing material shall provide the Government with the necessary information, data, and presentation materials to conduct a formal or informal briefing for this requirement.

6.1.11 Meeting/Conference Minutes The contractor shall provide meeting/conference minutes. The purpose of the minutes is to provide a summary of the meeting that may include documenting technical information discussed, decisions made, and agreements reached at meetings.

6.1.12 Conference Agenda The contractor shall submit to the Government, a conference agenda that provides information concerning the purpose, location, and schedule of conferences required to manage the acquisition of systems, equipment, related items, and services. The contractor shall update the conference agenda on an as needed basis as additional conferences are added.

6.1.13 Contract Kick-Off Meeting The contractor shall schedule, coordinate and host a Contract Kick-Off meeting IAW FAR 42.501 at the location approved by the Government 30 calendar days after contract award. The meeting will provide an introduction between the contractor personnel and the Government personnel who will be involved with this contract. The meeting will provide the opportunity to discuss technical, management, security issues, travel authorization and reporting procedures. At a minimum, the attendees shall include vital contract personnel, representatives from the directorates, other relevant Government personnel, Contracting Officer (KO) and the Contracting Officer Representative (COR).

6.1.14 Foreign Military Sales (FMS) Products purchased through FMS will be rendered via the DoD FMS Case Managers through PM TR. All requests for FMS purchased products will be documented and approved by the NSA in a FMS Letter of Acceptance. The contractor shall repair FMS purchased systems under warranty.

6.1.15 Small Business Participation Plan

The contractor shall provide to the Government their small business utilization achievements in awarding meanighful and innovative work to small business. The contractor shall report actual small business utilization acheivements relative to proposed small business participation in performance of this contract. This shall include subcontracting dollars/percentages relative to total contract value/ total subcontracting. This utilization includes tier one (1) subcontracting as well as through the use of competition of the components, parts (includes hardware and software),

6.1.16 Contractor Manpower Reporting The Office of Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor will report ALL contractor manpower (including subcontractor manpower) in accordance (IAW) PAL-80-05. The contractor is required to completely fill in all required data fields using the following web address: http://www.sam.gov.

The reported inputs will be for the labor executed during the PoP during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk at help desk at: http://www.sam.gov/ The required information includes the following:

· Contracting Office, Contracting Officer, COR

· Contract number, including task and delivery order number

· Beginning and ending dates covered by reporting period

· Contractor’s name, address, phone number, e-mail address, identity of contractor employee entering data

· Estimated direct labor (including sub-contractors)

· Estimated direct labor dollars paid this reporting period (including sub-contractors)

· Total payments (including sub-contractors)

· Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different

· Estimated data collection cost

· Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information)

· Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website)

· Presence of deployment or contingency contract language

· Number of contractor and sub-contractor employees deployed in theater this reporting period (by country) As part of this submission, the contactor shall provide the estimated cost (if any) incurred to comply with this reporting requirement

Contractors may use a direct Extensible Markup Language (XML) data transfer to the database server or fill in the fields on the website. The specific formats for the XML direct transfer may be downloaded from the website

6.1.17 Program Protection Implementation Plan (PPIP) The contractor shall assist and support the Government in performing a Critical Program Information (CPI) assessment on the system. The CPI Assessment is a structured approach to identify the technical know-how in the areas of Concept, Material, Design, Manufacturing, and Integration that enables the hardware and/or software elements to meet the threshold of CPI as defined in DoDI 5200.39, 28 May 2015, incorporating Change 3, 15 October 2018 or most recent version. If CPI is identified, the Government will prepare a Program Protection Plan (PPP). The Government will provide the contractor with written guidance referencing the implementation of countermeasures to protect CPI. The contractor shall provide a countermeasures Implementation Plan to the Government within one (1) month of receiving any countermeasures during the PoP and shall provide periodic countermeasure and implementation status to the Government. The countermeasures Implementation Plan is a subset of the PPIP and will be addressed separately. The contractor shall support the execution of Program Protection Surveys. The contractor shall implement Government-specified Supply Chain Risk Management (SCRM) countermeasures to safeguard critical function components identified by the Government.

The contractor shall assist and support the Government in performing a Critical Functionality Analysis (CFA) and a SCRM analysis of the system.

The contractor shall provide technical support for the Government’s PPP process performed in accordance with DoD 5200.1-M, DoDI 5200.39, DoDI 5200.02, DA PAM 70-3, and Key Practices and Implementation Guide for the DoD Comprehensive National Cyber Security Initiative.

6.1.18 Configuration Management The Contractor shall manage the baseline configuration of the platforms, systems, subsystems and items acquired under this contract as required by applicable TOs. Such support includes:

· Collection, review, tracking and archiving of Configuration Control Documents

· Development of automated databases to track hierarchical components

· Maintenance of Product Data

· Support to Configuration Control Boards

· Performance of Functional Configuration Audits and Physical Configuration Audits

6.1.19 Government Furnished Property (GFP)/Government-Furnished Equipment (GFE)/ Government-Furnished Information (GFI) / Government Furnished Material (GFM) Government property, equipment, information, and material will be provided to the contractor when required for performance of this PWS and approved by the COR in accordance with FAR 52.245-1. GFP/GFE/GFI/GFM may include but not limited to the following items:

· Equipment storage

· Government Off-The-Self/Commercial Off-The Shelf (GOTS/COTS) equipment

· Storage space

· Network communication access and services

· Access to commercial telephone networks Electronic mail

· Computer equipment

· Computer software applications The contractor shall request and coordinate specific GFP/GFE requirements during transition-in periods. This coordination must include a date when equipment is required. Unless directed otherwise, the contactor will be responsible for returning all GFP/GFE and GFI from the contractor’s place of performance back to the Government.

The contractor shall have the oversight responsibility to make available, track, and maintain accountability of GFP/GFE/ GFI/GFM provided to support this acquisition and will supply the COR with a Monthly Status Report insuring property accountability that reflect the results of surveys and inventories.

The GFP/GFE/ GFI/GFM will be made available to the contractor throughout the duration of the contract.

All GFP/GFE/ GFI/GFM shall be maintained and accounted for in accordance with the contractor-prepared GFP/GFE Inventory List Report template.

The contractor shall provide based upon the individual deliverables of GFP/GFE/GFI/GFM Inventory Report. The contractor shall conduct inventory inspection of a random sampling of 10% of all GFP/GFE/GFI/GFM on a monthly basis. The contractor shall include a complete list of all GFP within the contractor's Monthly Status Report for verification by the COR and/or Property Administrator. The list shall include Item name, Item Description, NSN, Cage, Part #, Model #, Serial #, UII, QTY, Unit of Measure, Unit Cost, and indication of Use As Is. It is mandatory that the form be completed to the maximum extent possible.

The contractor shall also maintain copies of warranty records for contractor acquired equipment purchased under this contract for use on this contract and provide the records and the property to the Government when requested, or at the conclusion of the contract.

GFP/GFE/ GFI/GFM used in support of this contract must be maintained and managed IAW AR 735-5.

The contractor shall review and confirm GFP inventory upon request by the Government.

The contractor shall be responsible for security keys and access cards provided by the Government.

The contractor shall be responsible for all damage incurred to GFP/GFE/ GFI/GFM while in their possession except in the case of normal operational use.

GFP/GFE/ GFI/GFM put on contract must be managed in the Defense Property Accountability System (DPAS). Contractor personnel will assist the DPAS admin and should coordinate closely with the COR to ensure proper accountability

6.2 Engineering and Developmental Support

The contractor shall develop, integrate, test, support NSA certify new equipment technology and architecture as required by applicable TOs. The initial TO will consist of development efforts for the NGLD-M that are outlined by the System Requirement Document SRD. This initial TO will culminate in a final design with PPUs that will be used for initial testing and support of a Programmatic Milestone C decision. Upon favorable Milestone C decision, the Government will allow the contractor to proceed to the LRIP production phase of this effort. Subsequent TOs will document the requirements for support of production items. . These efforts may include Engineering Change Proposals (ECPs) to enhance or extend the useful life of fielded products, obsolescence monitoring, and minor capability upgrades.

The contractor must meet specific requirements as set forth by the NSA as well as meet NSA requirements in the DRAFT Memorandum of Agreement (MOA) between the NSA and PEO C3T/PM TR Concerning the NGLD-M under the User Partnership Agreement (UPA).

6.2.1 Engineering, Development, Test, and Certification The contractor shall provide engineering services to support the development, test and certification of the NGLD-M design. The design effort will include supportability required to operate the designed system in the operational environment. Following design approval, the contractor shall continue development, test, and NSA certification of the design. NSA reviews will be conducted including a series of Risk-Assessment Panels (RAP) and system will require coordination with network administrators to determine connectivity to DoD/Government networks and systems. Testing shall be conducted against the SRD and CPD requirements. The contractor shall develop the system to meet requirements for RMF including Authorities to Connect (ATC) and Authorities to Operate (ATO) on DoD networks. The effort is further outlined in the Engineering Development PWS as supplied along with this PWS. Favorable Milestone C decision will result in the Government approving the LRIP production effort. Follow-on engineering efforts will be required and utilize portions of the below sub-tasks and will be further defined in specific TOs.

6.2.2 System Engineering The contractor shall submit any number of documentation which may include but not limited to:

· Software/Hardware Design Description (SHDD)

· Preliminary Design Review (PDR)

· Critical Design Review (CDR)

· Test Readiness Review (TRR)

· Interface Design Description (IDD)

· Interface Control Documents (ICD)

· Reliability and Maintainability Predictions Report

· Security Evaluation Document

· Product Drawings/Models and Associated Lists

· Key and Certificate Management Architecture (KCMA)

· Key and Certificate Management Plan (KCMP)

· Engineering Change Proposals

6.2.3 Software Development Process The contractor shall document their software development processes, standards and practices (such as Capability Maturity Model Integration (CMMI), Maturity level 3 or equivalent).

6.2.4 Test and Evaluation The contractor shall define and develop test programs, plans, and procedures, conduct testing, and evaluate and document results as required by each TO. Such testing may include but not limited to:

· Hardware and software component testing

· Subsystem and system level development testing

· System compatibility testing

· NSA Security Testing

· Developmental Test

· First Article Testing (FAT)

· Support to Joint Interoperability Test Command (JITC) Certification

· Operational Test Support

· Acceptance testing

· Functional testing

· Integration testing

· Full qualification testing

· Field-testing and evaluation

· Environmental tests and stress screening

· Electromagnetic interference testing, electromagnetic compatibility testing and TEMPEST

· Security (Cryptographic) Verification Testing (SVT)

The contractor shall conduct testing in total or shall support Government test personnel as specified by applicable TOs. For contractor conducted tests, the contractor shall ensure that all hardware, software, test equipment, instrumentation, supplies, facilities, and personnel are available and in place to conduct or support each scheduled test.

6.2.5 Certification The contractor shall obtain commercial and/or military certifications/authorizations for new or modified parts, subsystems, platforms, designs, equipment or installations in accordance with applicable DoD standards. These include but are not limited to NSA certification and ATOs for operating the NGLD-M system on DoD networks.

6.2.6 Product Support The contractor shall address product support considerations for fielding of the NGLD-M including software licensing, warranty strategy, manpower and personnel, technical data management, support equipment, computer resources, packaging, handling, storage, transportation, facilities, infrastructure, maintenance planning and management, design interface, sustaining engineering, supply support, training, and training support. The contractor shall submit plans for each of these for approval of the Government. All items that are required by the contractor will be addressed with and approved by the Government in either the initial development TO or during the sustainment services TOs.

6.2.7 Training and Training Materials The contractor shall provide NGLD-M operator training as specified in individual TOs. This training shall be provided on the features of the NGLD-M as well as periodic new releases either in software or hardware.

6.2.8 Operator and Maintenance Manuals The contractor shall provide to the Government both an Operator Manual Type I and Maintenance Manual Type II. The contractor shall write the manuals IAW MIL-STD-40051-2 (latest version). The contractor shall support Government reviews of the Technical Manuals (TMs) at 30%, 75% and 100% completion points. The contractor shall provide copyright release to the Government for TMs developed under this contract.

6.2.9 Reliability Prediction and Documentation of Supporting Data: The contractor shall deliver both reliability prediction test plans and reports in support of NGLD-M reliability requirements. The report documents contractor qualitative predictions of NGLD-M unit reliability operating in the ground mobile and airborne uninhabited fighter environments per MIL-HDBK 217F (2). The report is intended as support for identification of potential problems, logistics support planning, life-cycle cost studies, determination of data deficiencies, tradeoff decisions, allocation (apportionment) or performance requirements, and criteria for reliability growth.

6.2.10 Level of Repair Analysis (LORA) The contractor shall provide a Level of Repair Analysis (LORA) using the Computerized Optimization Model for Predicting and Analyzing Support Structure (COMPASS) provided by the Government. The results of the LORA will allow the Government to make life-cycle sustainment decision. Following the initial LORA, the Government may require additional LORAs on TO basis.

6.2.11 Provisioning Parts List (PPL) The contractor shall deliver the draft PPL prior to LRIP and a final version prior to the FRP decision. The PPL will be is used to determine the range and quantity of support items required to maintain the NGLD-M. Contractor format for this report is acceptable. The contractor shall deliver the draft PPL prior to LRIP and a final version prior to the FRP decision.

6.2.12 Technical Data Package The contractor shall review, develop and/or submit product data in accordance with applicable TOs. Product data may define one or more configuration items, associated manufacturing processes and associated test procedures. Various types of Product Data, including engineering drawings, specifications, software configuration documentation, interface control documentation, quality assurance provisions, and/or commercial item descriptions may be required. Furthermore, product data may provide but not limited to:

· Drawings and Associated Parts Lists

· Executable Software, Source Code, and Executable Files

· Manufacturing Process Information

· Complete design disclosure

· Form, fit and function requirements

· Performance specifications

· A combination thereof

6.2.13 Prototypes The contractor shall provide to the Government a specified number of uncertified Engineering Development Models (EDMs). The total number of EDMs will be identified in accordance with the TOs. These units will be used for system integration, testing, functional testing, early TEMPEST evaluations and ECU interoperability testing.

The contractor shall provide certified PPUs based on quantities defined in the TOs. These PPU systems will be used for final system integration, NSA Certification Testing Security Verification (SVT), TEMPEST, and Physical Configuration Audit (PCA), and production verification testing.

6.2.14 General Engineering Following the completion of the Initial Engineering, Development, Test, and Certification phase, efforts will be required to support production items and test equipment. Some examples of types of efforts may include ECPs to enhance or extend the useful life of fielded products, obsolescence monitoring, and minor capability upgrades. The Government shall provide additional TOs if additional General Engineering is necessary..

The contractor shall provide support to the Government when necessary for various tasks which may include items such as but not limited to:

· Engineering Change Proposals

· Drawing updates

· Various verification testing, both Hardware and Software

· Analysis and or Evaluation

· Failure Analysis

6.3 NGLD-M Production The contractor shall initiate the production effort for NGLD-M based on the Government approved design as defined during Initial Engineering, Development, Test, and Certification. The initial phase shall be the LRIP phase. Following the approved Government decision, the contractor shall initiate FRP. Further quantities will be defined in the individual DOs during the PoP of the IDIQ contract. Total expected production numbers for NGLD-M are expected to be 265,000 units. FRP unit numbers will be identified in the various DOs. Production items will support the US Army, Navy, Air Force, US Other Government Agencies, and FMS. Individual requirements for shipping and deliveries will be specified in the DOs to include specific locations both domestic and foreign.

6.3.1 Production Readiness Review (PRR) The contractor shall provide any manufacturing risks and issues throughout the program acquisition cycle. To identify any poor quality and low yields of key manufacturing processes, inability to support production rates, any cost increases, and schedule delays while production capable processes are being adopted prior to executing LRIP and prior to executing FRP.

6.3.2 Low-Rate Initial Production (LRIP) The contractor shall execute a LRIP of representative items. The LRIP is intended to result in completion of manufacturing development to ensure manufacturing capabilities meet production requirements, and to produce the minimum quantity necessary to provide production or production-representative articles for Government testing. LRIP quantities shall not exceed 10% of total quantity or approximately 26,500 NGLD-M units.

6.3.3 Materials The contractor shall provide parts, components, accessories, and related materials required to produce NGLD-M IAW the TDP, spares, and for repair of the NGLD-M. NGLD-M material deliveries shall commence no later than one-hundred eighty (180) Days After Receipt of Order (DARO). Delivery for spares shall commence no later than one-hundred eighty (180) DARO at quantities specified in individual Delivery Orders.

Material or parts used in the repair of these systems shall conform to the TDP and/or Original Equipment Manufacturer (OEM) specifications. Rebuilt components or assemblies in the repair of equipment, when such use is standard industry practice, and when the rebuilt component or assembly carries the same warranty as the new assembly. Any rebuilt components that the contractor intend to use shall meet specification equivalents of a new component. In addition, the contractor shall require the Government’s approval prior to its usage.

6.3.4 Full-Rate Production Deliveries Production delivery schedules will be set forth in each individual DO. The Government may require surge support during the base or any option period. The Government will provide to the contractor sixty (60) days’ notice of intent to increase production delivery quantities based upon surge requirements. Projected Quantities, approximately 238,500.

Production surges could occur at any time but no two (2) surges could be executed simultaneously.

Each Delivery Order shall provide the total number of production units required. NGLD-M deliveries shall commence no later than one-hundred eighty (180) days DARO. Contractor shall have a minimum monthly production capacity of four-thousand (4,000) units per month, no later than one-hundred eighty (180) days after DARO. The contractor shall execute multiple DOs concurrently within the previously required total production rate (minimum 4,000 per month). The contract shall develop, maintain and modify a delivery schedule based on Government set priorities. Production capacity does not denote a Government guarantee for monthly production numbers.

The contractor shall support unit pricing and quantity ranges for NGLD-M production and any spare parts identified after the competition of the Engineering Development TO.

6.3.5 Production Delivery Reporting The contactor shall maintain continuous accountability of all production units. The production deliveries database shall be a web-based application capable of being exported in Microsoft Excel 2013 that will enable the contractor and the Government the ability to track all production and repairs for each NGLD-M production unit. The contractor shall include but is not limited to delivery order numbers, quantity, Sub- Line Item Numbers (SLINs), customer name, Item Unique Identification (IUID), National Stock Number (NSN), Part Numbers (PN), and Serial Numbers (SN) within the tracking information.

6.3.6 Quality approach The contractor’s quality approach shall be responsible for assuring/monitoring that all manufacturing operations/processes are accomplished under controlled conditions.