PWS - SATCOM ISEA_dtd 6 March 2019.docx

SECTION C – DESCRIPTION/SPECS/WORK STATEMENT

SPECIFICATIONS/STATEMENT OF WORK/PERFORMANCE WORK STATEMENT

Work under this performance-based contract will be performed in accordance with the following description/ specifications/ statement of work (SOW) which herein will be referred to as Performance Work Statement (PWS):

SHORT TITLE: Satellite Communication (SATCOM) Capability-Base (CB) In-Service Engineering Activity (ISEA) Support

1.0 PURPOSE

1.1 SCOPE

The Satellite Communication (SATCOM) Capability-Base (CB) In-Service Engineering Activity (ISEA) PWS provides deployment, logistics, system engineering, life cycle sustainment engineering, integration, and production support for Department of Defenses (DoD) and Navy qualified systems and subsystems to Government customers. While most of the work addresses the Navy’s requirements, SATCOM CB-ISEA also supports Marine Corps, Coast Guard, Army, Air Force and Department of Homeland Security customers and programs.

This PWS covers Technical Sustainment Support (TSS), Sustainment Engineering (SE), Modernization Support (MS), Logistic Support (LS), and other SATCOM Technical Support Service. Specific tasking performed under this service contract are described in this PWS and required both the knowledge and demonstrated experience of several C4ISR current and future systems and supporting systems under the cognizance of the SPAWAR community on surface ships, submarines, and shore sites.

This support encompasses the entire spectrum of the SATCOM CB-ISEA services aforementioned across multiple systems and associated needs for delivery of fully operational and sustainable C4ISR systems and supporting systems to the war-fighters.

The SATCOM systems and all associated variants to be supported in individual Task Orders (TOs) are listed below (not all inclusive) in order of anticipated performance and priority:

· Navy Multiband Terminal (NMT): AN/WSC-9, AN/FSC-138, AN/BSC and Advanced TDMA Interface Processor (ATIP) including Teleports, IPV and DISA gateways;

· Commercial Broadband Satellite Program (CBSP): AN/USC 69(V)1,2,3 surface and shore;

· Global Broadcast Service (GBS): AN/USR-10A V(1-7), AN/USR-10B, AN/TSR-9, AN/TSR-11, AN/PRS-11, AN/PRS-12;

· Super High Frequency (SHF): AN/WSC-6 V7,7A,B,C, V9A,B,C,D,E,F,G;

· Naval Senior Leadership Carrier Aircraft (NSLC-A);

· Wideband SATCOM On The Move (WBSOTM);

· Commercial Wideband SATCOM Program (CWSP): AN/WSC-8;

· Mobile User Objective System (MUOS): AN/PRC-155, AN/ARC-210, AN/PRC-117G;

· Ultra High Frequency (UHF);

· Extremely High Frequency (EHF): Navy EHF Satellite Program (NESP), AN/USC-38;

· Wideband SATCOM Systems;

· TV-Direct to Sailor (TV-DTS);

· Environmental Satellite Receiver Processor (ESRP);

· Other corresponding equipment managed by the Communications and GPS Navigation Program Office (PMW/A 170), Shore and Expeditionary Integration Program Office (PMW 790), and the Fleet Readiness Directorate (FRD) 100;

· Other SATCOM systems, subsystems, and ancillary equipment.

NOTE: Website and e-mail addresses referenced within the PWS and CDRL forms are subject to change. For any website and e-mail address not working during time of performance, the contractor shall contact the Contracting Officer’s Representative (COR) or Contracting Officer for latest website and e-mail address. An incorrect website or e-mail address does not alleviate a contractor from required reporting or access requirements.

1.1.1 Multiple Funding

This contract is funded with multiple appropriations as delineated on specified contract line item numbers (CLINs). The applicable PWS task(s) associated with each funding CLIN is outlined in Section B and Section G. This contract will allow multiple appropriation on a single task order; funding specifics will be specified at TO level.

2.0 PLACE(S) OF PERFORMANCE

The work shall be performed at Government sites and/or at the contractor’s site, as delineated in the Task Order (TO).

2.1 GOVERNMENT FACILITIES

The Government will provide facilities (i.e., office space, computer hardware/software, or lab space) to those labor categories that would otherwise adversely affect the work performance if they were not available on-site. Labor categories and Government location of those personnel with supplied Government facilities will be identified at the TO level.

2.1.1 Training Requirements

Contractor personnel working full-time or partially at a Government facility shall complete all applicable mandatory training requirements as specified under Security Training, PWS Para 8.0.

2.2 CONTRACTOR FACILITIES

The contractor shall have a facility (i.e., office space, laboratory space, staging and storage areas, with or without classified storage) in order to accomplish task order objectives. Depending on the type of support required at the TO level, contractor shall be required to possess or establish facilities at specific locations. Any necessary contractor facilities requirements will be identified at the TO level.

3.0 PERFORMANCE REQUIREMENTS

The following paragraphs list all required non-personal services tasks that will be required throughout the contract. The contractor shall provide necessary resources with knowledge and demonstrated experience as cited in the personal qualification clause to support the listed tasks. Contractors shall perform requirements in accordance with Federal Acquisition Regulation (FAR) and/or Defense Federal Acquisition Regulation Supplement (DFARS) which do not include performance of inherently Government functions. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and resources.

The contractor shall provide functional and technical expertise supporting a wide range of SATCOM systems, subsystems, and ancillary equipment as defined in individual TOs.

3.1 PROJECT MANAGEMENT

The contractor shall establish a management structure sufficient to effectively manage the primary focus areas of this contract and its TOs. The contractor shall provide progress visibility of all assigned TOs ensuring timely completion of contract requirements with an emphasis on risk, cost, and schedule.

The contractor is required to support daily operation of the SATCOM CB-ISEA and to formally report on progress through Contract Data Requirements Lists (CDRLs) and attend program and technical reviews, upon government request, to be held at locations specified in the individual TO.

Specific Operations Support Activities that are required of the contractor include but are not limited to the following: Provide recurring status/progress reports; track and manage contract costs; conduct and attend program/technical reviews; create and provide support data for program office briefings; create and manage Contractor Work Breakdown Structures (CWBS); perform Management of Contractor and subcontractor staff and efforts to ensure conformance with TO requirements; create and maintain Program/Project Level Integrated Master Schedule (IMS); manage efforts to ensure timely delivery of data associated with Contract Data Requirements Lists. Operation Support Documentations (CDRL A001) will be defined in the task order level.

3.2 TECHNICAL SUSTAINMENT SUPPORT

The contractor shall provide support to fleet customers by providing timely information and technical assistance through established processes relative to government’s request as defined in the individual TO. The contractor shall maximize resource capacity and availability to deliver subservices including Distance Support, Onsite Support, and Proactive Systems Support.

3.2.1 Distance Support

The contractor shall assist fleet customers via distance support by creating, tracking, and timely resolving incident tickets as defined in the individual TO.

3.2.2 On-site Support

The contractor shall plan and execute on-site restorative actions as defined in the individual TO. The contractor shall support testing/studies, equipment grooms, and other of Fleet events anywhere in the world. The contractor’s personnel shall also be capable of riding the ship for extended periods.

3.2.3 Proactive Support

The contractor shall assist in identifying proactive sustainment tripwires, to include the proactive method of data collection, key metric and measure, tripwire implementation, tripwire monitoring, customer engagement, and documentation of proactive efforts and effectiveness, as defined in the individual TO.

3.2.4 Technical Sustainment Support Documentation

The contractor shall develop, review, and modify Technical Sustainment Documentation (CDRL A002) as defined in individual task order.

3.3 ENGINEERING SUPPORT

3.3.1 Sustainment Engineering Support

The contractor shall provide support to fleet customers by providing timely data analysis, development, and implementation of engineering changes and tech advisories relative to customer’s service request. The service robustly delivers baseline changes through three subservices to include Maintenance Engineering, Lifecycle Engineering, and Lifecycle Testing.

3.3.1.1 Maintenance Engineering

The contractor shall assist with developing documentation for technical accuracy and adequacy, updates maintenance inspection criteria and procedures for repair and overhaul of systems and equipment, assists in design reviews, and evaluates and validates maintenance actions and their frequency, as defined in the individual TO.

3.3.1.2 Lifecycle Engineering

The contractor shall collect, analyze, and report performance and maintenance data for C4ISR systems. The contractor shall determine reliability, maintainability, and availability and develops Engineering Changes, as defined in the individual TO.

3.3.1.3 Lifecycle Testing

The contractor shall provide proofing support for engineering changes and field changes. The contractor shall recommend improvements to test procedures, General and Special Purpose Test Equipment, tools, jigs, and fixtures. The contractor shall also review the adequacy of test equipment storage, shipboard electronic workshops, standard workshop plans, tool allowances, and recommend improvements, as defined in the individual TO.

3.3.2 Engineering Development Support

The contractor shall provide engineering support in enhancing capabilities and in the development of future SATCOM systems and sub-system.

3.3.2.1 System Evaluations and Trade Study Support

The contractor shall perform system evaluations, requirements reviews or trade studies to determine changes to correct deficiencies, achieve cost savings, or improve operations and maintenance as defined in the individual TO.

3.3.2.2 Design Analysis Support

The contractor shall provide plans, design analysis and recommendations for the following: Information Systems; Safety; Human Factors; Reliability; Maintainability; EMI/EMC; TEMPEST; Transportability; Survivability; Weight or Weight Distribution; Heating /Cooling; Control of electrostatic discharge and mercury contamination; Power or Power Distribution; RF interference; spread-spectrum technique; Carrier-in-Carrier compression; IP Based transmission technologies and encryption; Assured communication; Frequency Hopping; Anti Jamming; and other advanced technologies, as defined in the individual TO.

3.3.2.3 Prototyping Support / New Developmental Items

The contractor shall provide prototyping support to include the engineering, integration, documentation and fabrication of subassemblies and assemblies that constitute either parts of or an entire system as required to support the design validation and documentation verification and validation process prior to full production as defined in the individual TO.

3.3.2.4 Environmental Qualification Testing (EQT) Support

The contractor shall assist in operating and maintaining requirements associated with EQT services. Assistance will include EQT procedures, conducting the EQT, providing test results, and providing technical support services as defined in individual TO.

3.3.2.5 Engineering Test and Evaluation

The contractor shall participate in the test and evaluation efforts in support of engineering, integration and developmental supports as defined in the individual TO.

3.3.3 Engineering Support Documentation

The contractor shall develop, review, and modify Engineering Documentation (CDRL A003) as defined in individual task order.

3.4 LOGISTIC SUPPORT

The contractor shall provide high operational readiness logistics support that enables platforms/sites supportability through four subservices to include: Supply Support, Maintenance of Technical Data and Documentation, Configuration Management, and Training. The contractor shall also provide other logistics support to future SATCOM systems as required.

3.4.1 Supply Support

The contractor shall assist in management actions, procedures and techniques necessary to acquire, catalog, receive, store, transfer, issue, ship, and dispose of spares, repair parts, kits, equipment, Integrated Logistics Support (ILS) products and supplies as defined in the individual TO.

3.4.2 Maintenance of Tech Data and Documentation

The contractor shall conduct requirements analysis, development, review, revision, and/or update of technical documents in support of modifications and upgrades of supported equipment or systems necessary to operate, maintain, and return such equipment or system to a serviceable state as defined in the individual TO.

3.4.3 Configuration Management (CM) for Fielded Systems

The contractor shall plan and assist the government in the management of the configuration identification, configuration change control, configuration status accounting, configuration verification and audit, and data management of installed systems. The contractor shall ensure the operational equipment/systems hardware, technical documentation, and computer software program are consistent and are properly controlled and managed. The contractor shall ensure the CB-ISEA has accurate configuration data it needs to resolve issues/problems, and meet Shipboard/Shore Installation requirements. The contractor shall also assist in the development, reviews, updates, submission, and maintains the configuration and logistics records in the Configuration Data Manager Database - Open Architecture (CDMD-OA), as defined in the individual TO.

3.4.4 Training Services

The contractor shall assist in the development and maintaining the accessories and aids necessary to accomplish the objectives of training. The contractor shall also develop and maintain curriculum/training courses for installation, formal schoolhouse training, and training services, as defined in the individual TO.

3.4.5 Logistic Support Documentation

The contractor shall develop, review, and modify Logistic Documentation (CDRL A004) as defined in individual task order.

3.5 MODERNIZATION SUPPORT

The contractor shall load, configure, and verify operation and capabilities of installed/modernized C4SR systems.

3.5.1 System Installation and Turn-Over Support

The contractor shall provide support for afloat and shore pre-installation, on-site software installation, and system turnover processes as described in SPAWAR M-4720.14 and SPAWAR M-4720.1. Service includes pre-installation production/assembly and testing of systems, staging and shipping of installation materials, on-site installation and System Operational Verification Testing (SOVT), training, and operational cutover. The contractor shall provide support service as defined in the individual TO.

3.5.2 Optical Blockage Alignment Survey (OBAS) and Leveling Support

The contractor shall perform OBAS and leveling support to establish Radio Frequency blockage zones for SATCOM antenna onboard naval vessels and at shore facilities worldwide. The contractor shall also build and update the blockage data file as defined in the individual TO.

3.5.3 Fabrication Support

The contractor shall procure and fabricate SATCOM systems, subsystems, components, and ancillary devices as defined in the individual TO.

3.5.4 Installation Planning and Design Support

The contractor shall assist with afloat and shore installation planning and design documentation for installation as described by SPAWAR M-4720.14 and SPAWAR M-4720.1 respectfully. Support includes:

3.5.4.1 Installation Planning

The contractor shall assist in developing Fielding Plans, Ship Change Documents (SCDs), Justification Cost Forms (JCFs), Ship Alteration Records (SARs), Planning of Action and Milestones (POA&Ms), Installation IMS, Installation Requirements Drawings (IRDs), System SOVTs, Installation Work Scopes, installation cost estimates, SPAWAR PEO Integrated Data Environment and Repository (SPIDER) Work Plans, Fleet Readiness Certification Board (FRCB), tasking statements, and Site Survey Reports. The contractor shall provide support service as defined in the individual TO.

3.5.4.2 Installation Drawing Support

The contractor shall conduct site surveys, develop, validate and maintain drawing packages, drawing trees (interrelationship of engineering drawings and associated lists), “As-Built” drawings, red-line drawings, and block diagrams (schematic and functional, including all interfaces), cable running sheets, and Ship Installation Drawing (SID). The contractor shall provide support service as defined in the individual TO.

3.5.4.3 Installation Design Planning (IDP) Support

The contractor shall assist in the development/review of IDP as defined in the individual TO.

3.5.4.4 Base Electronic Systems Engineering Plan (BESEP)

The contractor shall assist in the development of BESEP as defined in the individual TO.

3.5.5 Modernization Support Documentation

The contractor shall develop, review, and modify Modernization Documentation (CDRL A005) as defined in individual task order.

4.0 INFORMATION TECHNOLOGY (IT) SERVICES REQUIREMENTS

4.1 INFORMATION TECHNOLOGY (IT) GENERAL REQUIREMENTS

The contractor shall adhere to the following requirements when the IT support services and/or supplies are applicable to the requirement:

4.1.1 Ensure that no production systems are operational on any research, development, test and evaluation (RDT&E) network.

4.1.2 Follow DoDI 8510.01 when deploying, integrating, and implementing IT capabilities.

4.1.3 Migrate all Navy Ashore production systems to the Navy, Marine Corps Intranet (NMCI) environment where available.

4.1.4 Work with Government personnel to ensure compliance with all current Navy IT & cybersecurity policies, including those pertaining to Cyber Asset Reduction and Security (CARS).

4.1.5 Follow SECNAVINST 5239.3C & DoDI 8510.01 prior to integration and implementation of IT solutions or systems.

4.1.6 Register any contractor-owned or contractor-maintained IT systems utilized on contract in the Department of Defense IT Portfolio Registry (DITPR)-DON.

4.1.7 Ensure all software recommended, procured, and/or developed is compliant with Section 508 of the Rehabilitation Act of 1973, 26 CFR Part 1194 and pursuant to SPAWARINST 5721.1B.

4.1.8 Only perform work specified within the limitations of the basic contract and TO, if applicable.

4.2 SECURITY IT POSITION CATEGORIES

Pursuant to DoDI 8500.01, DoD 8570.01-M, SECNAVINST 5510.30B, SECNAV M-5239.2, SECNAV M-5510.30, and applicable to unclassified DoD information systems, a designator is assigned to certain individuals that indicates the level of IT access required to execute the responsibilities of the position based on the potential for an individual assigned to the position to adversely impact DoD missions or functions. As identified in SECNAV M-5510.30, two DoN IT levels/Position categories require personnel to meet specific security requirements:

The contractor PM shall assist the Government Project Manager or Contracting Officer’s representative (COR) in determining the appropriate IT Position Category assignment for all contractor personnel based on the level of IT access needed. Contractor personnel whose duties meet the criteria for IT-I or IT-II position designation shall have a successful Single-Source Scope Background Investigation (SSBI), Tier 5 (T5) or Tier 3 (T3), respectively, with 5 year reviews and shall have a U.S. citizenship unless a waiver request is approved by CNO (N09N2). All required SSBI, SSBI Periodic Reinvestigation (SSBI-PR), and National Agency Check (NAC) adjudication will be performed Pursuant to DoDI 8500.01 and SECNAVINST 5510.30B. Requests for investigation of contractor personnel for fitness determinations or IT eligibility without classified access are submitted by SPAWARSYSCEN Atlantic Security Office, processed by the Office of Personnel Management (OPM), and adjudicated by Department of Defense Consolidated Adjudications Facility (DoD CAF). Contractor personnel identified as needing privileged access shall complete a privileged user agreement, all privileged user training for their level, 8570 certification, and a System Authorization Access Request – Navy (SAAR-N) form in accordance with the applicable IT position category. Investigative requirements for each category vary, depending on the role and whether the individual is a U.S. civilian contractor or a foreign national.

4.3 CYBERSECURITY SUPPORT

Cybersecurity (which replaced the term Information Assurance (IA)) is defined as prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. Contractor personnel shall perform tasks to ensure Navy applications, systems, and networks satisfy Federal/DoD/DON/Navy cybersecurity requirements.

4.3.1 Cyber IT and Cybersecurity Personnel

4.3.1.1 The Cyberspace workforce elements addressed include contractors performing functions in designated Cyber IT positions and Cybersecurity positions. In accordance with DFARS Subpart 5239.71, DoDD 8140.01, SECNAVINST 5239.20A, and SECNAV M-5239.2, contractor personnel performing cybersecurity functions shall meet all cybersecurity training, certification, and tracking requirements as cited in DoD 8570.01-M and subsequent manual [DoD 8140] when applicable prior to accessing DoD information systems. Proposed contractor Cyber IT and cybersecurity personnel shall be appropriately qualified prior to the start of the contract performance period or before assignment to the contract during the course of the performance period.

4.3.1.2 Contractors that access Navy IT shall also follow guidelines and provisions documented in Navy Telecommunications Directive (NTD 10-11) and are required to complete a System Authorization Access Request (SAAR) – Navy form as documented in Para 8.2.2.4(b).

4.3.1.3 Contractor personnel with privileged access shall acknowledge special responsibilities with a Privileged Access Agreement (PAA) IAW SECNAVINST 5239.20A.

4.3.2 Design, Integration, Configuration or Installation of Hardware and Software The contractor shall ensure any equipment/system installed or integrated into Navy platform will meet the cybersecurity requirements as specified under DoDI 8500.01. The contractor shall ensure that any design change, integration change, configuration change, or installation of hardware and software is in accordance with established DoD/DON/Navy cyber directives and does not violate the terms and conditions of the accreditation/authorization issued by the appropriate Accreditation/Authorization official. Contractors that access Navy IT are also required to follow the provisions contained in DON CIO Memorandum: Acceptable Use of Department of the Navy Information Technology (IT). Use of blacklisted software is specifically prohibited and only software that is registered in DON Application and Database Management System (DADMS) and is Functional Area Manager (FAM) approved can be used as documented in Para 4.2.2. Procurement and installation of software governed by DON Enterprise License Agreements (ELAs) – Microsoft, Oracle, Cisco, Axway, Symantec, ActivIdentity, VMware, Red Hat, NetApp, and EMC shall be in accordance with DON CIO Policy and DON ELAs awarded.

4.3.3 Cybersecurity Workforce (CSWF) Report

In accordance with DFARS clause 252.239-7001 and DoD 8570.01-M, the contractor shall identify cybersecurity personnel, also known as CSWF and Cyber IT workforce personnel. The contractor shall develop, maintain, and submit a monthly CSWF Report (CDRL A006) identifying CSWF individuals who are IA trained and certified. Utilizing the format provided in CDRL A006 Attachment 1of Exhibit A, the prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor personnel. See applicable DD Form 1423 for additional reporting details and distribution instructions. Although the minimum frequency of reporting is monthly, the COR can require additional updates at any time. Contractor shall verify with the COR or other Government representative the proper labor category CSWF designation and certification requirements. The primary point of contact (POC) for all related CSWF questions is the Command CSWF Program Manager (PM) in the office of the SPAWARSYSCEN Atlantic Information Systems Security Manager (ISSM).

4.3.4 Cybersecurity Workforce (CSWF) Designation

CSWF contractor personnel shall perform cybersecurity functions. In accordance with DoD 8570.01-M Information Assurance Workforce Improvement Program Manual, the CSWF is comprised of the following categories: IA Technical (IAT) and IA Management (IAM)); and specialties: Computer Network Defense Service Providers (CND-SPs) and IA System Architects and Engineers (IASAEs). Based on the IA function provided by the individual, an IA designator is assigned that references an IA category or specialty. Labor category IA designator and level/positions will be identified at the TO level.

5.0 CONTRACT ADMINISTRATION

Administration of the work being performed is required; it provides the Government a means for contract/TO management and monitoring. Regardless of the level of support, the ultimate objective of the contractor is ensuring the Government’s requirements are met, delivered on schedule, and performed within budget.

5.1 CONTRACTING OFFICER REPRESENTATIVE (COR) DESIGNATION

The COR will be specified at the TO level.

5.2 CONTRACTOR LIAISON

The contractor shall assign a technical single point of contact, also known as the Program Manager (PM) who shall work closely with the Government Contracting Officer and COR. The contractor PM, located in the contractor’s facility, shall ultimately be responsible for ensuring that the contractor’s performance meets all Government contract requirements within cost and schedule. PM shall have the requisite authority for full control over all company resources necessary for contract and TO performance and be available to support emergent situations. The PM shall ultimately be responsible for the following: personnel management; management of Government material and assets; and personnel and facility security. In support of open communication, the contractor shall initiate periodic meetings with the COR.

5.3 CONTRACTOR MONITORING AND MAINTENANCE

The contractor shall have processes established in order to provide all necessary resources and documentation during various times throughout the day including business and non-business hours in order to facilitate a timely contract/TO response or modification in particular during urgent requirements.

5.3.1 Contract Administration & Documentation

Various types of administration documents are required throughout the life of the contract. At a minimum, the contractor shall provide the following documentation:

5.3.1.1 Task Order Status Report (TOSR)

The contractor shall develop a Task Order Status Report (TOSR) (CDRL A007) and submit it monthly, weekly, and/or as cited in the requirements of each TO. The prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor reports. The TOSR include the following variations of reports:

(a) Monthly TOSR – the contractor shall develop and submit a TO status report monthly at least 30 days after TO award on the 10th of each month for those months the TO is active. The contractor shall report on various TO functions: performance, schedule, financial, business relations, and staffing plan/key personnel; see applicable DD Form 1423 for additional reporting details and distribution instructions. The contractor shall indicate the progress of work and the status of assigned tasks, cost reports, burn rate reports, and details on existing or potential problem areas. This CDRL includes a Staffing Plan (CDRL A007 Attachment 1 of Exhibit A), Personnel Listing (CDRL A007 Attachment 2of Exhibit A), and Government-furnished property (GFP) Template (CDRL A007 Attachment 3 of Exhibit A) necessary for additional data collection as applicable.

(b) Weekly TOSR – the contractor shall develop and submit a weekly status report which is e-mailed to the COR no later than close of business (COB) every Friday. The first report is required on the first Friday following the first full week after the TO award date. The contractor shall ensure the initial report includes a projected Plan Of Action and Milestones (POA&M). In lieu of a formal weekly report, larger, more complex TOs require an updated Earned Value Management report. At a minimum, the contractor shall include in the weekly report the following items and data:

(c) Data Calls – the contractor shall develop and submit a data call report which is e-mailed to the COR within six working hours of the request. The contractor shall ensure all information provided is the most current. Cost and funding data will reflect real-time balances. Report will account for all planned, obligated, and expended charges and hours. At a minimum, the contractor shall include in the data call the following items and data:

5.3.1.2 Contract/Task Order Closeout Report

The contractor shall develop a contract/task order closeout report (CDRL A008) and submit it no later than 15 days before the contract/TO completion date. The prime contractor shall be responsible for collecting, integrating, and reporting all subcontracting information. See applicable DD Form 1423 for additional reporting details and distribution instructions.

5.3.1.3 Enterprise-wide Contractor Manpower Reporting Application Pursuant to NMCARS 5237.102-90, the contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the DoD via a secure data collection website – Enterprise-wide Contractor Manpower Reporting Application (eCMRA). The Product/Service Codes (PSC) for contracted services excluded from reporting are as follows:

The contractor shall completely fill-in all required data fields using the following web address: https://www.ecmra.mil/. Reporting inputs consists of labor hours executed during the task order period of performance within each Government fiscal year (FY) which runs from October 1 through September 30. While inputs may be reported any time during the FY, the contractor shall report all data in the applicable FY no later than October 31 of each calendar year. The contractor shall send notice to the COR and Contracting Officer after the applicable eCMRA data has been successfully entered. For reporting questions, contractors may contact the help desk email accessible through the eCMRA login webpage.

5.3.1.4 WAWF Invoicing Notification and Support Documentation Pursuant to DFARS clause 252.232-7003 and 252.232-7006, the contractor shall submit payment requests and receiving reports using DoD Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) application (part of the Wide Area Work Flow (WAWF) e-Business Suite) which is a secure Government web-based system for electronic invoicing, receipt, and acceptance. The contractor shall provide e-mail notification to the COR when payment requests are submitted to the iRAPT/WAWF and the contractor shall include cost back–up documentation (e.g., delivery receipts, time sheets, & material/travel costs, etc.) to the invoice in iRAPT/WAWF. When requested by the COR, the contractor shall directly provide a soft copy of the invoice and any supporting invoice documentation (CDRL A009) directly to the COR within 24 hours of request to assist in validating the invoiced amount against the products/services provided during the billing cycle.

5.3.1.5 Labor Rate Limitation Notification

For all cost-type, level of effort (LOE), time and material, labor-hour, fixed-price LOE service task orders over the Simplified Acquisition Threshold (SAT), the contractor shall monitor labor rates as part of the monthly CSR/TOSR (see CDRL A007 Attachment 2of Exhibit A – Personnel Listing). The contractor shall deliver required notification if specified criteria and threshold values are met. The ability of a contractor to monitor labor rates effectively will be included in the contract/TO Quality Assurance Surveillance Plan (QASP).

(a) Fully burdened labor rates per individual (subcontractor included) – If the fully burdened rate (including fee, which also extends to prime contractor fee on subcontractor labor) of any individual in any labor category exceeds the threshold amount of $200.00/hour and the individual’s rate was not disclosed in pre-award of the contract/TO, the contractor shall send notice and rationale (CDRL A010) of the individual labor rate to the COR who will then send appropriate notification to the Contracting Officer. If the number of hours anticipated to be billed for an individual within one labor category is equal to or less than 200 labor hours for any given period of performance (e.g., base period, option year 1, or option year 2) for this effort, the hours to be billed for the individual are excluded from the CDRL notification.

(b) Negotiated versus actual average labor rates variance – If the actual average labor rate (inclusive of fee) (total actual fully burdened labor costs “divided by” total number of hours performed) is greater than 20% of the negotiated average labor rate (total negotiated fully burdened labor costs “divided by” total number of hours negotiated), the contractor shall send notice and rationale (CDRL A010) of the rate variance to the COR who will then send appropriate notification to the Contracting Officer. The contractor shall annotate the monthly percentage rate variance between the actual average labor rate versus the negotiated average labor rate in the CSR/TOSR. If a negotiated versus actual average labor rate variance occurs only due to the specific composition of the monthly labor mix (rather than actual labor rates invoiced exceeding negotiated labor rates by greater than 20%), then the variance is excluded from the CDRL notification.

5.3.1.6 ODC Limitation Notification

For all cost-type service task orders over the SAT, the contractor shall monitor Other Direct Costs (ODCs) as part of the monthly CSR/TOSR. For this monitoring purpose, ODCs include incidental material, travel, and other non-labor costs (excluding subcontracting and consultant labor cost) required in performance of the service. For any given period of performance, if the cumulative total cost of ODCs exceeds the awarded total cost of ODCs (regardless of any modifications to the awarded amount) by 110% of the original ODC, the contractor shall send notice and rationale (CDRL A010) for exceeding cost to the COR who will then send a memorandum signed by the PM (or equivalent) to the Contracting Officer documenting the reasons justifying the increase of ODC. CDRL notification is not needed if the revised ODC total is below 10% of the total labor value or $3M, whichever is lower. The ability of a contractor to monitor ODCs will be included in the TO QASP.

5.4 CONTRACTOR PERFORMANCE MANAGEMENT

Contractor performance standards and requirements are outlined in the contract/TO QASP. The ability of a contractor to perform to the outlined standards and requirement will be captured in the Contractor Performance Assessment Reporting System (CPARS). In support of tracking contractor performance, the contractor shall provide the following documents: Cost and Schedule Milestone Plan (CDRL A011) submitted 10 days after contract award and CPARS Draft Approval Document (CDAD) Report (CDRL A012) submitted monthly.

5.5 EARNED VALUE MANAGEMENT (EVM)

Earned Value Management (EVM) implementation will be determined at the TO level since this IDIQ contract is utilized by multiple users and multiple programs. The Government will specify EVM requirements, if any, prior to TO award. For contracts supporting multiple programs, requiring EVM is not based on the cumulative contract or TO amounts but on the single program effort over the life of the contract. Pursuant to DFARS clause 252.234-7001 (DEVIATION 2015-O0017) (SEP 2015) and 252.234-7002 (DEVIATION 2015-O0017) (SEP 2015), the contractor is required to have an Earned Value Management System (EVMS) which is determined by the dollar value of the single program effort. For contract program dollar values less than $20M, EVM is not required. In lieu of EVM, the contractor shall develop and maintain, as applicable to the TO, a Contract Funds Status Report (CFSR) (CDRL A013) to help track cost expenditures against performance. For program dollar values equal to or exceeding $20M, the contractor shall have an EVMS that complies with EIA-748C. For program dollar values equal to or exceeding $100M, contractors shall ensure their EVMS is formally validated and accepted by the Cognizant Federal Agency (CFA) (i.e., DCMA). For work requiring EVM, the contractor shall ensure their EVMS is capable of the following:

5.5.1 Relate resource planning to schedules and technical performance requirements

5.5.2 Integrate technical performance, cost, schedule, and risk management

5.5.3 Provide the integrated management information to plan the timely performance of work, budget resources, account for costs, and measure actual performance against plans and by the Work Breakdown Structure (WBS) and Contract Work Breakdown Structure (CWBS) elements in accordance with MIL-STD-881C. The contractor shall be able to sort, report, and account for tasking and expenditures by the WBS elements assigned in the TO (i.e., CWBS). The contractor shall ensure the EVMS has the capability to predict, isolate, and identify variances and the factors causing the variances.

5.5.3.1 The contractor shall develop and maintain a contract WBS (CWBS) and CWBS dictionary (CDRL A014) in accordance with DID DI-MGMT-81334D and the tasking assigned to support the program WBS as specified at the TO level. The contractor shall ensure the Government approved CWBS is written to the lowest level needed for adequate management and control of the contractual effort. The contractor shall ensure the CWBS includes all the elements for the products (hardware, software, data, or services) which are the responsibility of the contractor, and the CWBS reflects all work to be accomplished and facilitate management, data collection, and reporting. The contractor shall keep the CWBS dictionary current at all times and provide updates to the Government as specified. In accordance with DID DI-MGMT-81334D, changes to the CWBS or associated definitions at any reporting level, require Government approval.

5.5.3.2 The contractor shall provide a monthly Integrated Program Management Report (IPMR) (CDRL A015) which combines the Contract Performance Report (CPR) with the Integrated Master Schedule (IMS) into a single report [reference ASD/OUSD AT&L Memorandum – Integrated Program Management Report (IPMR) Data Item Description (DID) dtd 19 Jun 12]. Specific requirements are noted in CDRL DD Form 1423 and DID DI-MGMT-81861 where IPMR formats 1-7 are required but formats 2, 3, & 4 are optional for program values $20M -$100M.

5.5.4 For program dollar values equal to or exceeding $20M, Schedule Risk Assessment is optional. For program dollar values equal to or exceeding $100M, Schedule Risk Assessment is required.

5.5.5 The contractor shall engage jointly with the Government’s program manager in Integrated Baseline Reviews (IBRs) to evaluate the risks inherent in the contract’s planned performance measurement baseline. The contractor shall ensure the initial IBR occurs as soon as feasible but not later than six months after contract award, and subsequently, following all major changes to the baseline. The contractor shall verify during each IBR that the contractor uses a reliable performance measurement baseline, which includes the entire contract scope of work, is consistent with contract schedule requirements, and has adequate resources assigned. Each IBR should also record any indications that effective Earned Value Management (EVM) is not being used. The contractor shall conduct IBRs on subcontracts that meet or exceed the EVM threshold. The prime contractor shall lead the subcontractor IBRs, with active participation by the Government.

6.0 DOCUMENTATION AND DELIVERABLES

6.1 CONTRACT DATA REQUIREMENTS LIST (CDRL)

The following listing identifies the data item deliverables required under this contract and the applicable section of the PWS for which they are required. Section J includes the DD Form 1423s that itemize each Contract Data Requirements List (CDRL) required under the basic contract. The contractor shall establish a practical and cost-effective system for developing and tracking the required CDRLs generated under each task. The contractor shall not develop any CDRL classified TOP SECRET with SCI.

Classification

6.2 NON-DATA DELIVERABLES

Non-data deliverables, as applicable, will be specified at the TO level.

6.3 ELECTRONIC FORMAT

At a minimum, the contractor shall provide deliverables electronically by e-mail; hard copies are only required if requested by the Government. To ensure information compatibility, the contractor shall guarantee all deliverables (i.e., CDRLs), data, correspondence, and etc., are provided in a format approved by the receiving Government representative. The contractor shall provide all data in an editable format compatible with SPAWARSYSCEN Atlantic corporate standard software configuration as specified below. Contractor shall conform to SPAWARSYSCEN Atlantic corporate standards within 30 days of contract award. The initial or future upgrades costs of the listed computer programs are not chargeable as a direct cost to the Government.

6.4 INFORMATION SYSTEM

6.4.1 Electronic Communication

The contractor shall have broadband Internet connectivity and an industry standard email system for communication with the Government. The contractor shall be capable of Public Key Infrastructure (PKI) client side authentication to DOD private web servers. Unless otherwise specified, all key personnel on task shall be accessible by e-mail through individual accounts during all hours.

6.4.2 Information Security

Pursuant to DoDM 5200.01, the contractor shall provide adequate security for all unclassified DoD information passing through non-DoD information system including all subcontractor information systems utilized on task. The contractor shall disseminate unclassified DoD information within the scope of assigned duties and with a clear expectation that confidentiality is preserved. Examples of such information include the following: non-public information provided to the contractor, information developed during the course of the TO, and privileged TO information (e.g., program schedules and TO-related tracking).

6.4.2.1 Safeguards

The contractor shall protect Government information and shall provide compliance documentation validating they are meeting this requirement in accordance with DFARS clause 252.204-7012. The contractor and all subcontractors shall abide by the following safeguards:

(a) Do not process DoD information on public computers (e.g., those available for use by the general public in kiosks or hotel business centers) or computers that do not have access control.

(b) Protect information by at least one physical or electronic barrier (e.g., locked container or room, login and password) when not under direct individual control.

(c) Sanitize media (e.g., overwrite) before external release or disposal.

(d) Encrypt all information that has been identified as controlled unclassified information (CUI) when it is stored on mobile computing devices such as laptops and personal digital assistants, or removable storage media such as portable hard drives and digital optical disks, using DoD Authorized Data-at-Rest encryption technology. NOTE: Thumb drives are not authorized for DoD work, storage, or transfer. Use GSA Awarded DAR solutions (GSA # 10359) complying with ASD-NII/DOD-CIO Memorandum, “Encryption of Sensitive Unclassified Data-at-Rest on Mobile Computing Devices and Removable Storage.” The contractor shall ensure all solutions meet FIPS 140-2 compliance requirements.

(e) Limit information transfer to subcontractors or teaming partners with a need to know and a commitment to at least the same level of protection.

(f) Transmit e-mail, text messages, and similar communications using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and Transport Layer Security (TLS). Encrypt organizational wireless connections and use encrypted wireless connection where available when traveling. If encrypted wireless is not available, encrypt application files (e.g., spreadsheet and word processing files), using at least application-provided password protection level encryption.

(g) Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.

(h) Do not post DoD information to Web site pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to Web site pages that control access by user identification or password, user certificates, or other technical means and provide protection via use of TLS or other equivalent technologies. Access control may be provided by the intranet (vice the Web site itself or the application it hosts).

(i) Provide protection against computer network intrusions and data exfiltration, minimally including the following:

1. Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.

2. Monitoring and control of inbound and outbound network traffic as appropriate (e.g., at the external boundary, sub-networks, individual hosts) including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services.

3. Prompt application of security-relevant software patches, service packs, and hot fixes.

(j) As applicable, comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, critical program information (CPI), personally identifiable information, export controlled).

(k) Report loss or unauthorized disclosure of information in accordance with…