A02_NGLD-M_Program Management SOW_FINAL.docx

Procurement Sensitive NGLD-M Management TO

Statement of Work For Next Generation Load Device-Medium (NGLD-M) Program Management Support Services

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

Contents

NGLD-M Management Task Order (TO) 9 April 2020

1. Contracting Officer’s Representative (COR

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 Type This Statement of Work (SOW) shall be a Firm Fixed Price.

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 Capabilities Production Document (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, 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 include hardware, underlying software (e.g. approved Operation 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 under Multiple Award Contract (MAC), Indefinite Delivery Indefinite Quantity (IDIQ) contract. The contractor shall design the NGLD-M to meet the hardware requirements including underlying software (e.g. approved 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. 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 objective of this SOW is to provide overarching program management support services for the base period of the multiple IDIQ contract.

5. Scope.

The contractor shall provide program management services including, but not limited to, the following:

· Contract Management Planning

· In-Process Reviews (IPRs) and Program Management Reviews (PMRs)

· Monthly Status Reporting

· Integrated Master Scheduling (IMS)

· Risk, Opportunity, and Issue Management

· Work Break-down Structure (WBS) Management

· Meetings, Minutes, and Agendas

· Contractor Manpower Reporting

· Program Protection

· Program Protection Plan

· Cyber Security Plan

· Information Assurance (IA)

· Risk Management Framework (RMF)

· Property Management

· Contractor Furnished Equipment (CFE)

· Government Furnished Equipment (GFE), Government Furnished Property (GFP), and Government Furnished Information (GFI)

· Government Furnished Material (GFM)

· Laptops (for access to Government networks)

· Transition-In

· Supply Chain Risk (SCR)

· Travel Reporting

· Configuration Management

· Training

· Computer Resources

5.1 Applicability

This SOW is within scope of the NGLD-M IDIQ contract.

5.2 Applicable Documents

Applicable documents are cited throughout this SOW. All Data Items Descriptions (DIDs) and other necessary documents relevant to the performance of this contract are cited in this SOW. Any Government approved updates to these documents throughout the Period of Performance (PoP) shall supersede previous versions.

Table 1

6. PERFORMANCE REQUIREMENTS.

6.1 Program Management

The contractor shall manage all aspects of the contractor’s responsibilities as defined in the base contract and all aspects of each TO. The contractor shall also 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-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 contractor shall provide services, personnel, planning, direction, coordination, and control necessary to provide the services required within the PoP of this SOW.to ensure the successful administration, operation, and maintenance of services. The contractor shall establish a project organization/staff structure that facilitates effective overall program management of the work.

The contractor shall hire and retain highly-qualified personnel to meet the requirements under this SOW management, development, and other DOs and TOs,. The contractor may provide additional appropriately cleared personnel to receive on-the-job training for any function for which personnel substitution may be anticipated. However, in no case shall such training interfere with performance of any service.

The contractor shall provide management services as outlined in the scope of work listed in section 5 of this SOW. Further definition of each of these subtasks are listed in subsequent subtasks in section 6 of this SOW.

6.1.1 Kick-Off Meeting

The contractor(s) shall schedule, coordinate, and host a Kick-Off meeting at the location approved by the Government no later than 30 calendar days after award. The meeting will provide an introduction between the contractor personnel and Government personnel who will be involved with the 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 contractor personnel, representatives from the directorates, other relevant Government personnel, Contracting Officer (KO) and the Contracting Officer Representative (COR). The contractor shall provide the following at the Project Kick-Off meeting:

· Points of contact information

· Program scope highlights

· Outline of Design Concept

· Integrated Master Schedule (IMS) overall and against individual task orders

· Planned activities

· Risk and Opportunity Management Plan (RMP)

6.1.2 Contract Management Plan

The contractor shall prepare a Management Plan (MP) for this effort including a description of the technical approach, an Integrated Master Schedule (IMS), a Work Break-down Structure (WBS) with at least four (4) levels, baseline costs for both the development PWS and the Program Management SOW organizational resources and management controls to be employed to meet the cost targets, Technical Performance Measures (TPMs) and planned processes for conducting future program management and reviews. The contractor shall establish the program management baseline and the baseline shall be adjusted as a living document.

Deliverable: Management Plan DI-MGMT-81797 CDRL (E001)

6.1.3 Program Management Reviews

The contractor shall prepare and present quarterly Program Management Reviews (PMRs) to update the Government on contract cost, schedule, and performance against the approved MP of the MAC. This update should include all TOs/DOs covered under the IDIQ contract in the base period and include the following information, at a minimum.

· Accomplishments since last review

· Integrated Master Schedule (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 TO, but note that no certified EVM system is required for this effort.

6.1.4 Contractor’s Progress, Status and Management Report

The contractor shall prepare the Contractors Progress, Status and Management Report for the contract on a monthly basis. This report shall include all data associated with the base period of the IDIQ contract and each TO. The report shall provide total expenses incurred during the report month, total cumulative expenses to date, and percentage of total awarded amount. Each report will clearly list the total man-hours expended against each labor category, material expenses, and travel expenses. The report shall also include: A summary of technical efforts performed on each phase of the task; major difficulties encountered and plans to overcome them; any anticipated events that may cause significant changes to the program; a summary of future plans, recommendations, and proposals for both the next reporting period and for any long term plans. This report shall include all subcontractor data.

Deliverable: Contractor’s Progress, Status Report (DI-MGMT-81928), CDRL (E002)

6.1.5 Status Reports

The contractor shall submit status reports (spreadsheet) on a monthly basis. The monthly status report will include an itemized man-hour and cost report in the form of a spend plan and as such shall provide both actuals and projections (living document) for the entire base PoP. Included as attachments to the monthly status reports will be updated and detailed schedules and milestone charts. The status report shall provide Government visibility into contractor expenditures for labor, materials, travel, and any other contract charges. This report shall also include all subcontractor information.

Deliverable: Status Report (DI-MGMT 80368A), CDRL (E003)

6.1.5.1 Integrated Master Schedule (IMS)

The contractor shall provide a Milestone Schedule/IMS. This schedule shall be submitted to the Government at the time of proposal. This schedule will become part of the contract upon award. Any 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.. Microsoft Office Project 2013 or software compatible file shall be used to develop the IMS. Schedule impact 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.

Deliverable: Integrated Master Schedule (DI-MGMT-81650), CDRL (E004)

6.1.5.2 Risk, Opportunity, and Issue Management Plan

The contractor shall implement a formal risk, opportunity, and issue management process. 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 resent version. Program risks, opportunities, and issues shall be identified and categorized for both probability and consequence. The risk, opportunity, and issue management process shall consider all performance and schedule elements relating to this effort.

Deliverable: Contractor’s Risk Management Plan (DI-MGMT-81808), CDRL (E005)

6.1.5.3 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.

Deliverable: Risk Management Status Report (DI-MGMT-81809), CDRL (E006)

6.1.5.4 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.

Deliverable: Contract Work Breakdown Structure (DI-MGMT-81334D), CDRL (E007)

6.1.6 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 contractor shall prepare for and present a program kick-off meeting, support weekly Technical Interchange Meetings (TIMs), and Quarterly PMRs. The contractor shall provide minutes with action items for all Meetings/Conferences/ Reviews. This includes but is not limited to design reviews. The contactor shall prepare in advance technical documentation for formal briefings to the designated Government representative. The briefing material shall be provided to the Government with the necessary information, data, and presentation materials to conduct a formal or informal briefing for this requirement.

Deliverable: Briefing Materials (DI-MGMT-81605), CDRL (E008)

6.1.6.1 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 conference agenda will be updated on an as needed basis as additional conferences are added.

Deliverable: Conference Agenda (DI-ADMN-81249B), CDRL (A001)

6.1.6.2 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. The minutes will include the purpose of the meeting, who was at the meeting, when the meeting was held and where, any technical details provided, and decisions/agreements that are considered final.

Deliverable: Conference Minutes (DI-ADMN-81250B), CDRL (A002).

6.1.7 Small Business Participation Plan

The contractor shall provide to the Government their small business utilization achievements in awarding meaningful and innovative work to small business. The contractor shall report actual small business utilization achievements 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), Deliverable: Small Business Utilization Report (DI-MGMT-82041B), CDRL (R001))

6.1.8 Enterprise Contractor Manpower Reporting (eCMR)

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) required for performance of this contract PAL-80-05. eCMR is required at the end of each fiscal year. The contractor is required to completely fill in all the information in the format using the following web address: www.sam.gov.

The information required for CMR includes:

· Contract Number

· Fiscal Year (FY that the work was performed)

· Order Number (Delivery Order, Task Order, or Purchase Order Number)

· Requiring Activity Unit Identification Code

· Command (Command of the Requiring Activity that would be performing the mission if not for the contractor)

· Contractor Name

· Total Invoiced Amount (the total dollar amount invoiced during the fiscal year, at the Delivery Order and/or Task Order level. This is the responsibility of the contractor)

· Questions about Contract Performance (Contractors: Indicate if the contract/order includes the above services)

· Government Supervision (Are contractor personnel subject to relatively continuous supervision and control by a Government employee or officer)

· Governments Tools and Equipment (Does the Government furnish the principal tools and equipment needed for contract performance)

· Government Facility (Are some or all of the contractor employees provided with a workspace in a Government facility for use on a regular basis?)

· Contracting Officer (First Name, Last Name, Phone Number, and Email)

· COR/COTR (First Name, Last Name, Phone Number, and Email)

· Contractor (First Name, Last Name, Phone Number, and Email)

· Location Information (Federal Supply Code (FSC), City of Installation or Services, State, Zip, and Country)

· Direct Labor Hours

· Direct Labor Dollars

· Fund Cite

6.1.9 Configuration Management

The contractor shall conduct Configuration Control Board (CCB) meetings for their design, for significant configuration changes. During the CCB meeting, the contractor shall provide the required documentation for Government review and approval prior changing the product baseline.

The contractor shall provide engineering documentation clearly documenting a repeatable, producible design of the NGLD-M per MIL STD 3046. The contractor shall manage the configuration of design documentation IAW the Configuration Management Plan. The engineering documentation information shall include four (4) parts:

· Document Description Record (DDR)

· Part Description Record (PDR)

· Structure Record (STR)

· Manufacturer’s Description Record (MDR) Deliverable: Engineering Documentation Information (DI-EDRS-80410), CDRL (D001). (NSA) Configuration Management Plan (DI-SESS-81875), CDRL (M020)

6.1.10 Program Protection

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 or most recent version, incorporating Change 3, 15 October 2018. 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 countermeasures and shall provide periodic countermeasure and implementation status to the Government. 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 DoDI 5200.44, DoDI 5200.39, DA PAM 70-3, and Key Practices and Implementation Guide for the DoD Comprehensive National Cyber Security Initiative.

6.1.10.1 Program Protection Implementation Plan (PPIP)

The CPI Assessment supports the Government PPP. The following five (5) tasks shall be performed in addition to any other Program Protection tasks listed within this TO. These five (5) tasks shall be performed by the contractor as described and shall flow down to any sub-contractors engaged by the contractor.

· The contractor shall assist and support the U.S. Government in performing all CPI assessments 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. This requirement shall flow down to all subcontractors

· The contractor shall provide support for all CPI Assessments to include system engineers, software engineers, hardware engineers, and integration engineers and logistics analysts. The contractor shall provide all program documentation required by the Program Management Office (PMO) for each CPI Assessment. This requirement shall flow down to all subcontractors.

· If CPI is identified, the Government will prepare a PPP. The Government will provide the contractor with written guidance reference implementation of countermeasures to protect CPI. The contractor shall provide a Program Protection Implementation Plan (PPIP) to the Government within sixty (30) days of receiving countermeasures and provide periodic countermeasure and implementation status to the PMO. This requirement shall flow down to all subcontractors.

· The contractor shall provide technical support for the Government’s PPP process performed IAW DoDI 5200.39, DoDI 5200.02, and DA PAM 70-3. This shall include support for a CFA of the acquisition program. This requirement shall flow down to all subcontractors.

· In accordance with Federal Acquisition Regulation (FAR) Part 25.004 and 41 U.S.C. 10a, the contractor shall assist and support the Government in performing SCRM analysis of the system. The contractor shall identify suppliers of logic-bearing devices and software/firmware modules to the Program Office. The contractor shall identify who is designing, building, testing and distributing critical components and where this work occurs. Data will include company name, address, CAGE Code and a supplied item description. This requirement shall flow down to all subcontractors.

Deliverable: Program Protection Implementation Plan DI-ADMN-81306 CDRL (A003)

6.2 Property Management Support

6.2.1 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 TO 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

· GOTS/COTS

· Storage space

· Network communication access and services

· Access to commercial telephone networks Electronic mail

· Laptops, desktops, monitors Servers for DMI users

· 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.

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.

The Government shall provide the contractor records of all GFM/GFP/GFI/GFE (other than real property) that are managed or supported under this TO.

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

The Government will consider but is not obligated to provide any End Cryptographic Units (ECU) in support of this contract, but may be capable of providing access to laboratories or facilities to the contractor to test interoperability between the NGLD-M and the ECU.

The contractor shall provide based upon the individual deliverables of GFP/GFE/GFI/GFM Inventory Report. This report will certify and ensure that at least 10% of all GFP/GFE/GFI/GFM is physically accounted for monthly and 100% accounted for annually.

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/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.

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

The Government shall provide GFI to the contractor in the performance of this contract as defined in FAR 252.227-7025. GFI shall be controlled within specified restrictive rights such as “limited rights”,” Government purpose rights”. All GFI shall be marked with limited rights, restrictive rights, or Government Purpose rights as defined in FAR 252.227-7014.

GFM-GFE-GFP-GFI as Defined

GFM consists of property furnished by the Government to a contractor that may be incorporated into or attached to a deliverable end item or that may be consumed or expended in performing a contract. (I.e. cryptographic cards, RESCUE chip). GFM may also include assemblies, components, parts, raw and processed material and small tools and supplies that be consumed in normal use in performing a contract

GFE consist of various property in the possession of the Government and delivered to the contractor for use under this contract. GFE consists of tangible asset that is functionally complete for its intended purpose, durable, non-expendable and is not intended for sale or not to become a part of another article.

GFP consists of property furnished by the Government or contractor acquired property which shall be such as spares, parts for repair, maintenance, overhaul, or modification.

GFI consists of any information owned by the Government such as technical specifications, manuals, drawings, test data, source code that will be shared with the contractor in the performance of the TO.

Deliverables: Status of Government Furnished Equipment (GFE); DI-MGMT-80269 CDRL (E009)

6.2.1.1 Laptops and Mobile Devices will follow the following GFP process The GFP provided to the contractor may include, but is not limited to, laptops and mobile devices to perform the services needed under this contract/order. The contractor shall manage GFP in accordance with Federal Acquisition Regulation (FAR) Part 45 and Defense FAR Supplement (DFARS) Part 245 and associated clauses incorporated in this contract. 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 format be completed to the maximum extent possible.

6.2.1.2 Handling of GFM GFP, GFE, GFM, and GFI

The contractor shall protect from unauthorized disclosure any materials or information made available by the Government, or that the contractor has access to by virtue of the provisions of this order, that are not intended for public disclosure.

The materials and information provided to the contractor by the Government, or that the contractor had access to in completing work under this order, are the exclusive property of the Government. Upon completion or termination of this contract, the contractor shall return all information and materials (copies included) that were provided to the contractor by the Government. Any other materials/information developed or delivered by the contractor in performance of this contract shall be delivered in accordance with FAR 52.227-14.

If required, the GFM and GFE may be provided in support of this contract. The Government will provide the contractor records of all Government-owned property (other than real property) and equipment that are under warranty and used, managed, or supported under this contract that will be transferred to the contractor in support of this TO. The contractor shall maintain records regarding the transfer of equipment to any sub-contractor or Government being responsible for the proper disposition and/or transfer of equipment. The contractor shall maintain accountability in accordance with AR 735-5 Policies and Procedures for Property Accountability.

6.2.2 Engineering Database and Configuration Management (CM) Information The contractor shall develop and maintain the Engineering Database and Configuration Management Information current with any authorized change or updates to the NGLD-M baseline.

Deliverables: Engineering Database and Configuration Management Information (EDCMI), (DI-SESS-81694), CDRL (M001) Product Drawings/Models and Associated Lists, (DI-SESS-81000F), CDRL (M002)

The TSRD further clarifies relationships between Configuration Control Documentation and the Configuration Item Database.

6.2.3 Diminishing Manufacturing Sources and Material Shortages (DMSMS)/Obsolescence Analysis The contractor shall develop and deliver a Diminishing Manufacturing Sources and Material Shortages (DMSMS)/Obsolescence Analysis outlining potential issues and risks associated with specific items and parts.

Deliverable: DMSMS/obsolescence analysis (DI-MGMT-81948), CDRL (E012)

6.2.4 Counterfeit Components

The contractor shall provide an overview of its supply chain management process to address and eliminate the introduction of counterfeit components into the supply chain and system during production and during repair.

Deliverable: Counterfeit Prevention Plan; (DI-MISC-81832 CDRL (G001)

6.3 Information Assurance (IA) and Risk Management Framework (RMF) The contractor shall support Risk Management Framework (RMF), Government Cybersecurity and Assessment and Authorization (A&A), and Connectivity or Interconnectivity activities as required, including providing A&A documentation, upon request, in a format acceptable to DoD RMF, Cybersecurity and A&A activities. The contractor shall report all Information Assurance Vulnerability Alert (IAVAs), Security Technical Implementation Guides (STIG), Security Requirements Guide (SRG) and Bulletins within a system Plan of Action and Milestone (POA&M) at least monthly and provide a list outlining which were implemented, those not implemented and why they were not and how mitigated if mitigation required.

The contractor shall perform manual scans and provide to the Government at least monthly to ensure the system is compliant with Federal Information Security Management Act (FISMA) and STIG/SRG Updates, Incident Reporting and Vulnerabilities Management.

6.3.1 Risk Management Framework (RMF)

Upon successful receipt of the Authority to Operate (ATO) and Government receipt of the Authorities to Connect (ATC) for the NGLD-M under the Development Task Order for this contract, the contractor shall continue to manage and provide input to the RMF process to maintain a consistent ATO for the NGLD-M item. The contractor shall provide the required documentation to support PM TR’s re-submissions for a network (ATO IAW NIST SP-800-53, Risk Management Framework Controls. The ATO will be reviewed by the US Army’s Network Command (NETCOM) review, Authorizing Officer (AO) approval within PEO C3T, and any other required approval authorities. The NGLD-M will be categorized as Confidentiality, Integrity, and Availability, “High, High, High,” as designated by PEO C3T.

7. Performance Standards

Performance Standards Acceptable Quality Levels Methods of Calculation

Program Management – Personnel Management

Staff the contract in accordance with approved staffing plan.

Minimum Acceptable:

1. All personnel are qualified to perform assigned tasks

2. No more than 10% Personnel turnover per contract

Monthly or as required

Measurement Period:

. Monthly for the prior month Source of Measurement Data:

Monthly Status Report, Spend plan, Method of Surveillance:

Government review. 100 % Inspection Timing of Measurement:

.Monthly Reporting Frequency:

Reporting to commence upon Contract Award and continue throughout the Period of Performance.

1. Exceptional

2. Very Good

3. Satisfactory

4. Marginal

5. Unsatisfactory

Program Management – Cost, Schedule, Performance

Establish and Manage a Project Cost;

Target Criteria:

Project immediately starts after Kickoff Meeting for Government

Minimum Acceptable:

Outcome of meeting allows immediate kick-off of project with Minimal clarification

Monthly or as required Measurement Period:

Monthly Source of Measurement Data: Monthly Status Report Method of Surveillance:– Government review 100% Inspection Timing of Measurement:

Monthly Reporting Frequency:

Reporting to commence upon Contract Award and continue throughout the Period of Performance.

1.Exceptional 2.Very Good 3.Satisfactory 4.Marginal 5.Unsatisfactory

Program Management Cost Control

1. Submit Option Year Schedule for Government Approval by Task/Sub-Task and Organization at least 60 days Prior to Expiration of Current contract Year

2. Ensure all Schedule Baseline Changes are Approved by the Government Through a Formal Change Process

3. Provide an Updated Schedule Status in the Monthly Status Report (MSR) Minimum Acceptable:

1. Schedule Changes are Requested Prior to Missing Expectations

2. All Services are Performed Within Government Approved Schedule Monthly Schedule Status Updates Are Accurate

Monthly or as required Measurement Period:

Monthly Source of Measurement Data: Monthly Status Report Method of Surveillance:– Government review Periodic Inspection Timing of Measurement:

Monthly Reporting Frequency:

Reporting to commence upon Contract Award and continue throughout the Period of Performance.

1.Exceptional 2.Very Good 3.Satisfactory 4.Marginal 5.Unsatisfactory

Submit Base Period Schedule by Task/Sub-Task and Supported Organization within 10 days after TO

Minimum Acceptable:

Schedule Submissions are Accepted by the Government

Monthly or as required Measurement Period:

Monthly Source of Measurement Data: Monthly Status Report and various CDRLS Method of Surveillance:– Government review Periodic Inspection Timing of Measurement:

Monthly Reporting Frequency:

Reporting to commence upon Contract Award and continue throughout the Period of Performance.

1. Exceptional

2. Very Good

3. Satisfactory

4. Marginal 5.

6. Unsatisfactory

Submit 100% of contract deliverables listed in section 11 of the TO on time and accurate. COR and PdL COMSEC must approve all changes prior to the due date Minimum Acceptable:

95% of all deliverables accepted without change

Dependent on Deliverable.

Measurement Period:

Dependent on Deliverable.

Source of Measurement Data: Government review. CO/COR will have final decision on measurement.

Method of Surveillance – Government review. 100% Inspection Timing of Measurement:

Dependent on deliverable.

Reporting Frequency:

Dependent on Deliverable

1. Exceptional

2. Very Good

3. Satisfactory

Submit 100% accountability on a yearly basis with 10% accountability on a monthly basis Minimum Acceptable:

90% accuracy on all property

Monthly/Annually Measurement Period:

Monthly Source of Measurement Data: Government review of Monthly Report; Annual onsite 100% property assessment by COR/Gov’t Rep. CO/COR will have final decision on measurement.

Method of Surveillance – Government review.

Timing of Measurement:

Monthly/Annually Reporting Frequency:

Reporting to commence upon Contract Award and continue Monthly throughout the Period of Performance

1. Exceptional

2. Very Good

3. Satisfactory

4. Marginal

5. Unsatisfactory

100% baseline configuration maintained error free and on schedule per task order event

Minimum Acceptable:

95% of configuration baseline maintained without error and on schedule per task order event

As required by event Measurement Period:

Interval between events Source of Measurement Data:

Configuration Management Documentation Method of Surveillance:– Government review Periodic Inspection Timing of Measurement:

As required by event Reporting Frequency:

Reporting to commence upon contract award thru the Period of Performance as required by event

1. Exceptional

2. Very Good

3. Satisfactory

8. Incentives This Program Management SOW is a FFP effort and any incentives are embodied in the performance of the effort. The contractor can maximize profit through effective performance

8.1 Positive Incentive

The Government may submit positive remarks in the Contractor Performance Assessment Reporting System (CPARS) report when the contractor’s performance is at standard or above standard as defined in the Quality Assessment Surveillance Report (QASP).

8.2 Negative Incentive

The Government may submit negative remarks in the CPARS report when the contractor’s performance is unacceptable or does not meet standards as set forth in the QASP.

Unacceptable performance will be documented as a non-conformance and inform the KO for resolution. The COR will document by submitting to the KO a Contractor Discrepancy Report and document any unacceptable performance in the CPARS report.

9. Place of Performance Place of Performance shall be primarily at the contractor’s facility. Additional places of performance are defined in the NGLD-M IDIQ PWS.

10. Period of Performance The PoP shall begin immediately upon award. The PoP for this SoW shall align with the NGLD-M Engineering Development PWS.

DELIVERABLES:

11. Delivery Schedule.

During the execution of this TO, the contractor shall submit a reply to each CDRL as required for this effort and shall comply with the specific requirements as outlined in each CDRL on the DD1423. All specific details regarding the deliverables will be found in both the DID and the DD1423. All days are in calendar days. All Government comments shall be addressed and adjudicated. All final deliverable CDRLs shall be approved by the Government...

All days indicated in the deliverables shall be calendar days.

6.2.4

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the KO 1 copy of the transmittal letter with the deliverable to the Primary COR.

12. Security Requirements This section shall be considered a supplement to Block 13 of the Government provided DD Form 254, Contract Classification Specification as required by the TO. The security section identified here is in reference to the base contract security section and the base DD254.