ATTACHMENT_0001_-_PERFORMANCE_WORK_STATEMENT.pdf

Request For Proposals No. W56KGY-16-R-0004 Attachment No. 0001

Performance Work Statement Systems Engineering and Technical Assistance (SETA) Support for

Product Manager Radars Counter-Rocket, Artillery, Mortar Program Directorate

Program Executive Office, Missiles and Space

4 March 2016

Prepared by Product Manager Radars

Counter-Rocket, Artillery, Mortar (C-RAM) Program Directorate Program Executive Office Missiles and Space

Building 6006, Aberdeen Proving Ground, MD 21005

Attachment No. 1 i

This page left blank intentionally ii

Product Manager Radars

Table of Contents

1.0 Scope

1.1 Period Of Performance / Place Of Performance

1.2 Hours of Operation

1.3 Government Furnished Equipment / Materials / Facilities

1.4 Identification/Authority of Contractor Employees

2.0 Applicable Documents

3.0 Requirements

3.1 Program Security

3.2 Contractor-Provided Services

4.0 Data Item Deliverables

4.1 Monthly Status Report, CDRL A001 (DI-MGMT-80368A)

4.2 Conference, Working Group and Trip Reports, CDRL B001 (DI-ADMN-81308A)

4.3 Program Technical Assessments, CDRL C001 (DI-MISC-80508B)

5.0 Travel or Material Requirements

6.0 Contractor Performance Outside Of the United States

6.1 Contractor performance within the U.S. Central Command (CENTCOM) Area of Responsibility

6.2 Contractor performance within the Republic of Korea

6.3 Contractor performance within the Federal Republic of Germany

7.0 Deployment Requirements (As Governed By AR 525-93)

7.1 Legal

7.2 Standard Identification Cards

7.3 Tour of Duty/Hours of Work

7.4 Allowable Cost and Reimbursable

iii

8.0 Organizational Conflict Of Interest

9.0 Contractor Manpower Reporting Requirements

Appendix A: Contractor Non-Disclosure Agreement

Appendix B: Contractor Employee Personal Financial Interest / Protection of Sensitive Information Agreement

Appendix C: Acronyms

Product Manager Radars

1.0 Scope

Product Manager (PdM) Radars’ portfolio of systems consists of the AN/TPQ-53 Radar, FIREFINDER Family of Equipment (AN/TPQ-36/37), the Lightweight Counter Mortar Radar (LCMR) Family of Systems (AN/TPQ-48, AN/TPQ-48A and AN/TPQ-50), and related Foreign Military Sales (FMS). This performance work statement (PWS) establishes the requirements for contractor-provided services to support PdM Radars, in the following areas: programmatic, technical, engineering, testing, logistics, training, integration, business management, administrative, and operational program support. These services shall assist PdM Radars in the successful product development, acquisition, sustainment, supportability, fabrication, overhaul and fielding, training, de-fielding, and day-to-day administration.

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources (except for those identified as Government Furnished Property (GFP) or assistance) to perform the work under this PWS. Contractor employees performing services under this contract shall be controlled, directed and supervised at all times by management personnel of the contractor. The contractor’s management shall ensure that employees properly comply with the performance standards outlined in this Performance Work Statement and as required by the contracting officer or the contracting officer’s representative (COR). Contractor employees shall perform independent of and without the supervision of any Government official. Actions of contractor employees may not be interpreted or implemented in any manner that results in any contractor employee creating or modifying Federal policy, obligating the appropriated funds of the U.S. Government, overseeing the work of Federal employees, providing direct personal services to any Federal employee or otherwise violating the prohibitions set forth in Parts 7.5 and 37.1 of the Federal Acquisition Regulation (FAR). The Government shall control access to the facility and shall perform the inspection and acceptance of completed work and tasks.

1.1 Period Of Performance / Place Of Performance

1.1.1 Period of Performance (PoP). The PoP consists of 12-month base period and two 12 month option periods.

1.1.2 Place of Performance. Work shall be primarily performed at offices and facilities at PdM Radars, Aberdeen Proving Ground (APG), MD.

1.1.3 Temporary Duty (TDY), less than 180 days, Within the Continental United States (CONUS). Locations include New York, New Jersey, Alabama, Oklahoma, Washington D.C., Arizona, Pennsylvania, and other locations as may be required based on future need. All TDY will be conducted in accordance with (IAW) the Joint Travel Regulation (JTR).

1.1.4 TDY, less than 180 days, Outside CONUS (OCONUS). Locations include Germany, Canada, and Thailand. Performance in Afghanistan, Iraq, Kuwait, England, Korea, Israel, or other locations may be required based on future need. All TDY will be conducted IAW the JTR.

1.1.5 CONUS TDY, 180 days or more. Locations include Yuma Proving Ground (YPG), Yuma AZ; Letterkenny Army Depot (LEAD), Chambersburg PA; Tobyhanna Army Depot (TYAD), Tobyhanna PA; Lockheed Martin Corp. (LM), Syracuse NY; and SRCTec, North Syracuse NY). Other locations may be required based on future need. All TDY will be conducted IAW the JTR.

1.1.6 OCONUS TDY, 180 days or more. Locations may be required based on future need, to include contingency theater of operations such as Iraq, Ukraine, Afghanistan, Korea, and other locations as necessary. All TDY will be conducted IAW the JTR.

1.2 Hours of Operation

The contractor is responsible for providing CONUS services, between the hours of 0800-1700, Monday through Friday, except federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The contractor shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the workforce are essential.

Performance of OCONUS services is further discussed in paragraph 7.3, Tour of Duty/Hours of Work.

1.3 Government Furnished Equipment / Materials / Facilities

Subject to space constraints, the Government will provide office space for CONUS contractor personnel at Government locations. Personnel at these locations will have access to information concerning acquisition management, weapon systems, programs, processes, and schedules to facilitate the contractor’s review and analysis. The Government will also provide desks, chairs, telephone and telecommunications services, lights, heating, air conditioning, electric power, standard office equipment (software, hardware) and connectivity, e.g., non-secure internet protocol router network (NIPRNET) and internet access. Secure means of communication (secret internet protocol router network (SIPRNET) and joint worldwide intelligence communications system (JWICS)) access will be available as determined by the Government as necessary to support required contractor performance.

1.4 Identification/Authority of Contractor Employees

1.4.1 Identification of Contractor Employees. Contractor personnel attending meetings, giving briefings/presentations, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as contractors to avoid creating an impression in the minds of members of the public that they are Government officials. All documents or reports produced by contractors must be suitably marked as contractor products. All other contractor participation must be appropriately disclosed.

1.4.2 Limitation of Contractor Employee Authority. Contractor personnel can make recommendations only to the assigned Government lead. Approvals and other decision-making authority shall be retained by the Government and shall not be delegated to the contractor under any circumstances.

1.5 Periodic Progress Meetings

The Contracting Officer, Contracting Officer’s Representative (COR) and the appropriate Government technical lead may meet periodically with the contractor to review the contractor's performance under this contract IAW the Quality Assurance Surveillance Plan (QASP), which is an attachment to the contract. At these meetings the Contracting Officer will apprise the contractor of how the Government views the contractor's performance. Appropriate action shall be taken to resolve outstanding issues.

2.0 Applicable Documents

a. Army Directive 2014-05 (Policy and Implementation Procedures for Common Access

Card Credentialing and Installation Access for Uncleared Contractors)

b. Army Regulation (AR) 190-11 (Physical Security of Arms, Ammunition, and Explosives)

c. AR 350-1 (Army Training and Leader Development)

d. AR 380-5 (Department of Army Information Security Program)

e. AR 380-67 (Personal Security Program)

f. AR 700-127 (Integrated Logistics Support)

g. Department of the Army (DA) Pamphlet (PAM) 700-127 (Integrated Logistics Support Managers Guide)

h. AR 700-142 (Type Classification, Materiel Release, Fielding and Transfer)

i. DA PAM 700-142 (Instructions for Materiel Release, Fielding and Transfer)

j. AR 70-47 (Engineering for Transportability)

k. AR 70-1 (Army Acquisition Policy)

l. DA PAM 70-1 (Instructions for Army Acquisition Policy)

m. AR 530-1 (Operations Security)

n. AR 525-13 (Anti-Terrorism)

o. AR 750-1 (Army Materiel Maintenance Policy)

p. AR 750-10 (Army Modification Program)

q. DA PAM 700-56 (Logistics Supportability Planning and Procedures in Army Acquisition)

r. AR 700-138 (Army Logistics Readiness and Sustainability)

s. Office of the Secretary of Defense (OSD) Supportability Guide (Designing and Assessing Supportability in DOD Weapon Systems: A Guide to Increased Reliability and Reduced Logistics Footprint)

t. AR 25-50 (Preparing and Managing Correspondence)

u. AR 25-1 (Army Information Technology)

v. AR 25-2 (Information Assurance)

w. Department of Defense Instruction (DoDI) 5000.02 (Operation of the Defense Acquisition System)

x. DoD Directive (DoDD) 7045.14, Change 1 (The Planning, Programming, Budgeting and Execution System)

y. DoD 8570.01-M (Information Assurance Workforce Improvement Program)

z. DoDI 5230.24 (Distribution Statements on Technical Documents)

aa. PdM Radars Acceptable Use Policy (AUP)

bb. AR 525-93 (Army Deployment and Redeployment)

cc. AR 381-12 [Threat Awareness and Reporting Program (TARP)]

dd. Product Manager Radars System Fielding Standard Operating Procedure

ee. Security/Program Classification Guides

ff. Chairman of the Joint Chiefs of Staff (CJCS) Instruction and CJCS Manual 6000 Series

gg. Committee on National Security Systems Instruction (CNSS) No 1253 (Security Categorization and Control Selection for National Security Systems)

hh. Defense Information Systems Agency Security Technical Implementation Guides

ii. Federal Information Security Management Act

jj. Joint Travel Regulation

kk. National Institute of Standards and Technology 800 Series Special Publications

ll. National Security Agency Guides

3.0 Requirements

3.1 Program Security

Security requirements applicable to the contract are set forth in the DD Form 254, Contract Security Classification Specification, which is an attachment to the contract. The PdM Radars

Government Security Officer is the point of contact for clarification of any referenced security-related documents or guidelines.

3.1.1 Facility Clearance. The contractor shall maintain a top secret facility clearance. The contractor shall not store any classified information at the contractor facility. The contractor shall require access to communications security (COMSEC) information and information designated For Official Use Only (FOUO), and up to and including top secret (TS) non-sensitive compartmented information (SCI) intelligence information. The contractor shall also require access to Security/Program Classification Guide(s) (SCG), the SIPRNET, Joint Personnel Adjudication System (JPAS), and provide security support as required.

3.1.2 Access Authorization. The contractor will have access to classified information overseas and will be authorized to use the Defense Technical Information Center (DTIC). Hand-carry of classified materiel must be approved by the PdM Radars Government Security Manager, who will verify the proper courier authorization credentials. The contractor shall provide courier authorization briefings and courier authorization credentials to contractor employees.

3.1.3 Security Clearance. At a minimum, contractor personnel performing work on this contract shall have and maintain a clearance at the SECRET level to support this effort, however, the contractor must have the ability to upgrade identified personnel security clearances to top secret, as needed.

3.1.4 Security Training. All contractor employees with access to a Government information system (IS) must be registered annually in the Army Training Certification Tracking System (ATCTS) at commencement of services. For each required security training course identified in this PWS, the contractor shall provide the COR with a list of employees that have completed the training, to include date of completion. The list shall be submitted as a supplement to the Monthly Status Report required by Contract Data Requirements List (CDRL) A001, unless required to be submitted earlier by the PWS. A spreadsheet or other contractor format is acceptable.

3.1.4.1 Department of Defense (DoD) Information Assurance (IA) Awareness Training.

Prior to gaining IS access, all contractor employees, to include subcontractor employees, must successfully complete the DOD Information Assurance Awareness Training within 30 days after commencement of services, and then annually thereafter.

3.1.4.2 Anti-Terrorism (AT) Level I Training. All contractor employees, to include subcontractor employees, requiring access to Government installations, facilities, and controlled access areas shall complete AT Level I Awareness training within 30 calendar days after commencement of services. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR within seven calendar days after completion of training by all employees and subcontractor personnel. AT level I Awareness training is available at the following website: https://jkodirect.jten.mil.

3.1.4.3 AT Awareness Training for Contractor Personnel Traveling Overseas. The contractor employees and associated subcontractor employees shall receive Government-provided area of responsibility (AOR) specific AT awareness training as directed by AR 525-13.

https://jkodirect.jten.mil/

Specific AOR training is directed by the combatant commander with the unit ATO being the local point of contact.

3.1.4.4 iWATCH Training. The contractor employees and all associated subcontractors employees shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days after contract award, or for employees commencing performance subsequent to contract award, within seven calendar days of their reporting for duty. Verification of training shall be reported to the COR not later than 60 calendar days after completion of training.

3.1.4.5 Operations Security (OPSEC) Awareness Training. Per AR 530-1, all contractor employees, to include subcontractor employees requiring access to Government installations, facilities and controlled access areas, shall complete Level I OPSEC Awareness training within 30 calendar days after contract award, and annually thereafter. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter. The contractor shall submit certificates of completion of training to the COR for each affected contractor employee and subcontractor employee. OPSEC Awareness training is available at the following website:

http://cdsetrain.dtic.mil/opsec/.

3.1.4.6 Cyber/IA Training and Support

3.1.4.6.1 Compliance. The contractor shall adhere to IA regulations and security policies including the Federal Information Security Management Act (FISMA); AR 25-1 Army Information Technology; AR 25-2 Information Assurance; any applicable DoD 8500 series Directives and/or Instructions and their associated references (Cyber Security); National Institute of Standards and Technology (NIST) SP 800 series Special Publications (SP) and their associated references; CNSSI No. 1253 Security Categorization and Control Selection for National Security Systems; Chairman of the Joint Chiefs of Staff Instruction (CJCSI) and Chairman of the Joint Chiefs of Staff Manual (CJCSM) 6000 Series; National Security Agency (NSA) Guides; Defense Information Systems Agency (DISA) Security Technical Implementations Guides (STIGs). The Contractor shall provide cybersecurity support to PdM Radars systems to include authorization efforts under the DoD Risk Management Framework (RMF), with a level of effort necessary to obtain and maintain all Cybersecurity approvals, such as an Interim Authority to Operate (IATO), or an Authority To Operate (ATO). New accreditations will be conducted under the Army RMF accreditation process.

3.1.4.6.2 DoD Cyber Awareness Training. All contractor employees and associated subcontractor employees must complete the DoD Cyber Awareness training before issuance of network access and annually thereafter. Verification of the annual DoD Cyber Awareness shall be provided to the COR. DoD Cyber Awareness training is available at the following website:

https://ia.signal.army.mil/DoDIAA/.

http://cdsetrain.dtic.mil/opsec/ https://ia.signal.army.mil/DoDIAA/

3.1.4.7 TARP Training. Per AR 381-12, contractor employees must receive annual TARP training by a counter-intelligence (CI) agent or other trainer as specified in 2-4b.

3.1.5 Performance or Delivery in a Foreign Country. The Defense Federal Acquisition Regulation Supplement (DFARS) 252.225-7043 applies to both contingencies and non-contingency support.

3.1.6 Access and General Protection/Security Policy and Procedures. Contractor and all associated subcontractor employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures. The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services or Security Office. In addition to the contract clause entitled, “Personal Identity Verifications of Contractor Personnel” [Federal Acquisition Regulation (FAR) 52.204- 9], Contractor workforce must comply with all personal identity verification requirements as directed by DoD, DA, and/or local policy. Should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes in accordance with the Security Requirements or Changes clauses of this contract.

3.1.7 Common Access Card (CAC). Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following:

a. Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely;

b. Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or

c. Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more.

At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the Federal Bureau of Investigation fingerprint check and a successfully scheduled NACI at the Office of Personnel Management (OPM).

3.1.8 Information Technology. Contractor personnel performing Information Technology (IT) sensitive duties are subject to investigative and assignment requirements in accordance with AR 25-2, AR 380-67 and affiliated regulations.

3.1.8.1 DoD and IA Certification. Per DoD 8570.01-M, DFARS 252.239.7001 and AR 25-2, the contractor employees supporting IA/IT functions shall be certified with the proper and current DoD approved IA certifications.

3.1.8.2 PdM Radars Acceptable Use Policy. The contractor shall ensure understanding and compliance with the PdM Radars AUP regarding personnel responsibilities and limitations in using organizational or DoD IS. The AUP is an attachment to the contract. The contractor shall provide explicit acknowledgment by reviewing, signing and delivering the AUP form to the PdM Radars Security Officer.

3.1.9 Key Control and Lock Combinations. The contractor shall ensure that all Government issued keys/key cards and lock combinations, issued to the contractor, are not lost or misplaced and are not used by unauthorized persons. The contractor shall not duplicate keys/key cards issued by the Government. The contractor shall comply with procedures covering key/key card control and lock combinations in accordance with AR 190-11. Such procedures shall include turn-in of any issued keys/key cards by personnel who no longer require access to locked areas.

The contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the PdM Radars Government or contractor Security Manager.

3.1.10 Access to Planning, Programming, Budgeting, and Execution System (PPBES)/Future Years Defense Plan (FYDP). In accordance with DoDD 7045.14 Change 1, dated 28 July 1990 (paragraphs 4.7 and 4.8) contractors are not allowed access to PPBES documents and supporting databases without explicit authorization of a relevant Government official, and individuals requiring such access must have the appropriate clearance.

3.1.11 Marking of Materials. The contractor shall ensure that all their personnel understand the contents of each of the PdM Radars SCG(s) (there is one SCG per radar system). Contractor personnel shall properly mark, store and handle all material they acquire, generate or create in accordance with AR 380-5, in conjunction with the applicable SCG.

3.1.11.1 Marking Technical Documents.

All technical documents shall be marked U//FOUO at a minimum, or up to and including SECRET as appropriate, with the content of the information and IAW with each SCG. Examples of technical documents include, but are not limited to:

a. Technical manuals/documentation

b. Maintenance manuals/documentation

c. Hardware/software configuration items/documents

d. Contract deliverables ordered via CDRLs

e. Software version description

f. System/architectural designs

g. Engineering drawings

h. System specifications

i. Technical data packages

j. Program security documents

k. Reports

l. Test plans and test reports

m. User guides and standing operating procedures

n. Acquisition and logistic support documents

3.1.11.2 Unclassified/FOUO Documents and Media. All unclassified and FOUO documents and media shall be marked with the following statement:

DISTRIBUTION STATEMENT D

Distribution authorized to the Department of Defense and U.S. DoD contractors.

Only for Administrative or Operational Use, (Date). Other requests shall be referred to Product Manager Radars SFAE-MSL-CRR

3.1.11.3 Export Controlled Technical Data. All documents that contain export-controlled technical data shall also be marked IAW DoD Instruction 5230.24 ---

WARNING -- This document contains technical data whose export is restricted by the Arms Export Control Act 22 U.S.C. Sec 2751 et seq.) or the Export Administration Act of 1979, as amended, 50 U.S.C. app. 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

3.1.11.4 FOUO Material Transmitted Outside of DoD. All FOUO material and technical documents transmitted outside DoD shall be marked as follows:

This document contains information

EXEMPT FROM MANDATORY DISCLOSURE

Under the Freedom of Information Act

3.2 Contractor-Provided Services

The services to be provided by the contractor under this PWS are described in the following paragraphs.

3.2.1 Project/Acquisition Management

3.2.1.1 The contractor shall continually monitor, synthesize, analyze and integrate data generated by personnel supporting PdM Radars in the areas of programmatics, engineering, test and evaluation, configuration and data management, systems integration support, field support and logistics. The contractor shall formulate recommendations, based on its assessment of this data that will assist the PdM Radars in the management of its programs. The contractor shall make recommendations regarding

a. Systems life cycle performance requirements

b. Acquisition strategies and plans

c. The development, maintenance and tracking of acquisition program baseline documents

d. The development of spend plans and spreadsheets

e. Long range plans and program accomplishments in relation to program objectives, taking into account any known or potential budgetary, schedule or technical constraints

f. Compliance with DoDI 5000.02 and all acquisition streamlining reform initiatives.

Additionally, the contractor shall act as liaison with the U.S. Army Training and Doctrine Command (TRADOC) community and U.S. Army Forces Command (FORSCOM) units.

3.2.1.2 The contractor shall support the planning/preparation for and execution of program reviews and milestone decisions, to include Congressional Reviews, DA system reviews, Milestone Decision Authority (MDA) reviews and decisions, Program Executive Officer (PEO) level In-Process Reviews (IPRs), Overarching Integrated Product Teams (OIPTs), and Army Systems Acquisition Review Council (ASARC) and Defense Acquisition Board (DAB) reviews.

The contractor shall assist the Government in updating program documentation in support of Milestone Decisions and/or reviews to support PdM Radars programs. The contractor shall prepare and analyze data for compliance with the DoD 5000 series publications and the FAR and DFARS requirements for final review and approval by PdM Radars.

3.2.1.3 The contractor shall provide input and recommendations in the development of strategic business plans and processes, including implementation and direct support of Integrated Product Teams (IPTs) and process management.

3.2.1.4 The contractor shall provide contract management support for the procurement of equipment and services for PdM Radars. This shall include, but not be limited to the planning, preparation, and development of acquisition requirement packages (ARP). This equates to approximately 150 contract actions annually, and includes new contracts, delivery orders, task orders, and modifications. The contractor shall understand the unique contract requirements for critical and urgent contingency operations and FMS. The contractor shall coordinate with technical and logistics functional area experts to assist in defining requirements, and translating user needs to contract documents. The contractor shall assist in market research through the development of Requests for Information (RFIs), Sources Sought Announcements (SSA), Synopsis, and Industry Days. The contractor shall assist in the preparation of PWS’s; CDRLs;

DD Form 254; AT/OPSEC Cover Sheets; Quality Assurance Surveillance Plans (QASPs);

Government-furnished equipment (GFE) list; Theater Business Clearances (TBC); Justifications and Approval (J&A); Acquisition Plans (APs); and Service Acquisition Strategies (SAS). The contractor shall coordinate for approval through the PdM; PD C-RAM; PEO; Small and Disadvantaged Business Utilization (SDBU) Office; Legal; Competition Advocate; and the Army Contracting Command (ACC). The contractor shall provide program and management analysis support to FMS team. The contractor shall coordinate meetings, prepare and maintain status reports, and provide input to briefings. The contractor shall actively participates in weekly IPT meetings and quarterly Program Management Reviews (PMRs). The contractor shall prepare detailed after action reports and track action items through closure. The contractor shall receive, distribute and track all CDRL items for all PdM Radars’ managed contracts. The contractor shall update and or prepare contract strategies and identify contract inchstones for all contract actions.

3.2.2 Engineering

The contractor shall assist the Government by providing systems engineering and software engineering expertise to analyze system concepts, system design, and interoperability. The contractor shall provide independent evaluations of technical and operational performance and progress of weapon systems for PdM Radars’ portfolio of systems as described in the following paragraphs.

3.2.2.1 Systems Engineering. The contractor shall provide systems engineering support for requirements generation and baseline configuration management, including but not limited to:

a. Requirements/capabilities gap analysis

b. Input to user capability needs in accordance with the Joint Capabilities Integration and Development System (JCIDS) process (e.g., systems’ Capabilities Production Document (CPD) updates)

c. Analyses and translation of user capability needs/requirements into performance specifications for all systems

d. Management of system specifications, such that traceability of requirements to test plans, procedures and reports are ensured. System access to the U.S. DoD data repository utilizing IBM’s Data Object Oriented Requirements System (DOORs) systems engineering tools will be provided by the Government to appropriate contractor employees.

e. Configuration management support using PTC’s Windchill product lifecycle management software for configuration data management and configuration change process control and workflow automation. System access will be provided by the Government to appropriate contractor employees.

3.2.2.2 Test. The contractor shall provide test and evaluation (T&E), Quality Engineer (QE), Reliability Engineer (RE), Product Assurance (PA), and Production Engineer (PE) support to PdM Radars in all phases of the weapon system life cycle. This shall include but not be limited to review of test plans and procedures for accuracy and adequacy; assisting with design tests to include support to the Government for planning test resource requirements; witnessing tests and providing technical support; assisting with the preparation of Government-coordinated test plans IAW appropriate Army regulations; and analyzing/evaluating test results. The contractor shall ensure data collected from tests are adequate to support engineering, developmental, operational and acceptance test requirements. Test events are typically conducted at YPG, AZ. Test support is primarily required at APG, YPG and at radar original equipment manufacturers (OEM) (LM and SRCTec) facilities in Syracuse and North Syracuse, NY.

3.2.2.3 General Engineering. The contractor shall provide

a. Input to, and analysis of, system architectures for the current and future PdM Radars systems evaluation of detailed designs, drawings, equipment lists and interconnect diagrams

b. Support of design reviews and provide input to the Government in the design approval process

c. Configuration management, including support of engineering change proposal (ECP) process and conduct of physical and functional configuration audits

d. Integration, assembly and test support in areas of production management, logistics, product assurance, safety, acceptance testing and on-site integrated system testing and handover to units.

General Engineering shall include expertise in electrical, mechanical, software, production, maintainability, and radar/radio frequency engineering. General Engineering services shall be provided primarily at APG with on-site services to be provided through the life of the contract at the AN/TPQ-53 and AN/TPQ-50 radar OEM (LM and SRCTec) facilities in Syracuse and North Syracuse, NY.

3.2.2.4 IA/Cyber. The contractor shall provide qualified Information Assurance Managers (IAM) with Cybersecurity expertise to manage the implementation of IA/Cyber requirements for PdM Radars programs. Expertise with the DoD Risk Management Framework (RMF) is required. The IA/Cyber support will oversee the implementation of IA/Cyber requirements by OEM contractors and Government depot facilities to include detailed knowledge of all standards/policies shown in paragraph 3.1.4.6, Cyber/IA Training and Support. All persons providing contract support under this paragraph must have and maintain current IA/Cyber Certified Information Systems Security Professional (CISSP) certifications (or equivalent) in accordance with DoD 8570.01-M.

3.2.2.5 Radar Operations. The contractor shall review and assess whether the OEM’s engineering solutions are designed in a manner which are optimized to meet the needs of the soldier operators and maintainers and are able to be utilized in relevant tactical environments.

3.2.3 Acquisition Support

3.2.3.1 The contractor shall provide input to new program development, and development of program alternatives/strategies including market surveys, trade-off analyses, best technical approach, and cost effectiveness analyses.

3.2.3.2 The contractor shall provide programmatic and program system engineering technical support for the PdM Radars; and functional support divisions and teams. The contractor shall provide all labor, and services necessary to perform programmatic support in monitoring, https://www.isc2.org/cissp/default.aspx assessing, coordinating, analyzing and integrating component programs/activities, including briefings/presentations and agendas for the total life cycle of the above programs/systems. In addition, the contractor shall provide support for deployments, exercises, Advanced Technology Demonstrations (ATDs), Advanced Concept Technology Demonstrations (ACTDs), Non- Developmental Items (NDIs), Commercial Off-The-Shelf (COTS) and other acquisition streamlining initiatives.

3.2.3.3 The contractor shall provide programmatic assessments for technology transition into PdM Radars platforms and related Command and Control (C2) systems. Assessments shall include technologies being developed (or under development) in supporting research and development organizations such as Communications-Electronics Research Development and Engineering Center (CERDEC). Assessments, analyses, and technical documentation shall be provided to the Government in accordance with CDRL C001, DI-MISC-80508B (Technical Report-Study/Services).

3.2.3.4 Product Coordination. The contractor shall assist the Government and provide input in the preparation/writing and coordination of documentation required for program reviews;

milestone decisions; program and budget submissions; cost estimates, including Program Office Estimates (POEs); cost, schedule and performance risk evaluations; Office of Management and Budget (OMB) reports (e.g., Capital Investment Report); Congressional inquiries; audits; other programmatic documentation, program schedules, information papers and briefings. All data input, documentation and coordination shall be submitted to a Government official for review and approval.

3.2.4 Logistics (Other Than Fielding / New Equipment Training / De-fielding)

3.2.4.1 The contractor shall support the Government management of its logistics program for all PdM Radar Products during the development, production and sustainment phases of the life cycle. The contractor shall provide services sufficient to perform the full range of integrated logistics support (ILS) functions and tasks to those defined and described in AR 700-127 (Integrated Logistics Support), DA PAM 700-127 (Integrated Logistics Support Managers Guide), AR 700-142 (Type Classification, Materiel Release, Fielding and Transfer), DA PAM 700-142 (Instructions for Materiel Release, Fielding and Transfer), AR 70-47 (Engineering for Transportability), AR 350-1 (Army Training and Leader Development), AR 70-1 (Army Acquisition Policy), DA PAM 70-1 (Instructions for Army Acquisition Policy), AR 750-1 (Army Materiel Maintenance Policy), AR 750-10 (Army Modification Program), DA PAM 700-56 (Logistics Supportability Planning and Procedures in Army Acquisition), AR 700-138 (Army Logistics Readiness and Sustainability), and the OSD Supportability Guide (Designing and Assessing Supportability in DOD Weapon Systems: A Guide to Increased Reliability and Reduced Logistics Footprint) in support of any and all PdM Radars managed programs during all stages of the Army acquisition life cycle. The contractor shall provide services sufficient to assess, comment, document and resolve ILS issues pertaining to, but not limited to, ILS documentation, manpower/personnel integration (MANPRINT), technical manuals, training, training materials, materiel fielding, total package fielding, new equipment training (NET), provisioning, configuration audits, and technical data packages (TDPs) for PdM Radars systems, major assemblies, subassemblies, and replenishment parts.

3.2.4.2 The contractor shall assist the Government in identifying training requirements and in reviewing third-party training programs of instructions (POI's) for platforms, systems, subsystems and/or critical items as required by the applicable contracts for weapon system development contracts. The contractor shall assist the Government in reviewing third party manuals and documentation to support all weapon systems programs required. The contractor shall be familiar with training applications such as video teleconferencing and computer-based training in order to provide recommendations to the Government in reviewing third party training proposals. The contractor shall conduct training for Government personnel or foreign national personnel, if directed by the Government, to ensure proper operation, repair, maintenance and testing of platforms, systems, subsystems or items.

3.2.4.3 The contractor shall be familiar with and provide input and recommendations using the Repair Data Program Management Tools for analysis of logistics, product assurance, total asset visibility, configuration management, prime and subcontractor manufacturing data.

3.2.4.4 The contractor shall support the Government in the review of logistics documents and provide input in the preparation/writing and coordination of documentation required for PdM Radars program reviews.

3.2.4.5 The contractor shall provide logistics support to LEAD, TYAD, APG, YPG and any additional sites that might be authorized to be utilized by PdM Radars in support of field operations, maintenance activities, shipping, material handling, inventory, retrofit transportation and accountability of BII, GFE and associated support items of equipment (ASIOE). The contractor shall support the Government in performing research regarding GFE sourcing, maintenance and operation of said equipment.

3.2.5 Financial Management

3.2.5.1 Program Budget Support. The contractor shall assist the Government in the preparation of budgetary documentation in support of PdM Radars programs’ annual budget of $300M. All documentation (over 300 transactions annually) shall be entered into the Government’s budgeting software systems to include the Standard Operation and Maintenance Army Research and Development System (SOMARDS), the General Fund Enterprise Business System (GFEBS), the Logistics Modernization Program (LMP), Defense Travel System (DTS), etc. and be approved and signed by the Government. The contractor shall maintain financial records for multiple appropriations FMS. The contractor shall assist the Government in providing program and budget documentation support to include (but not be limited to) the preparation of program milestones with estimated cost and manpower requirements, justification for costs and manpower, justification for delays in program spending, modifications to program budget submittals and back-up data/charts to support the estimates for weapon systems.

3.2.5.2 Cost Estimating and Analysis Support. The contractor shall provide input and recommendations for cost estimating and/or budget activities for PdM Radars programs/systems, inclusive of all program life cycle phases, in accordance with applicable DOD Directives, Army regulations, and policies. Tasks include the development and maintenance of POEs utilizing automated cost modeling software. Additionally, the contractor shall provide input for life cycle cost analyses, operations and support (O&S) cost reduction analyses, cost risk evaluation, and PPBES preparation efforts.

3.2.6 Operations

3.2.6.1 Administrative Support. The contractor shall:

a. Provide assistance to the Government in preparing, reviewing, and updating PdM Radars administrative documentation. This documentation shall include but not limited to reviews and updates of weekly suspense reports, major event calendars, and good news reports.

b. Control and track documents being staffed through PdM Radars, PD C-RAM and PEO Missles & Space (M&S).

c. Provide technical/administrative support to include preparation of briefing notes and action items for program reviews, user conferences, and other meetings.

d. Provide support to Project Managers, Product Managers, Product Directors, functional team leaders and their staffs for development of briefings, schedules, hardware/software requirements, and “what-if” budget and programmatic exercises.

e. Assist in coordination of the day-to-day activities of PdM Radars (i.e., procurement of office supplies, set up and scheduling of conference and training classrooms, ect…)

f. Create graphs and charts from data for use in presentations to targeted audiences (i.e. PD C- RAM, PEO M&S, Army staff elements and OSD).

g. Provide for planning, analyzing, and developing all audio visual products and services for PdM Radars to include posters, business cards, websites, program-related products, presentation editing, and staff call support.

3.2.6.2 Resource Management Support. The contractor shall provide data collection and analysis support to PdM Radars programs/systems for integration, fielding, demonstration, experiments, exercises, and testing and shall provide recommendations for resource management initiatives. The contractor shall develop and maintain resource management related software models to support the status of PdM Radars programs/systems and shall develop and maintain specialized computer programs, databases and data storage and retrieval systems to support the development, testing and fielding of PdM Radars programs/systems.

3.2.6.3 Schedule Development/Assessment Support. The contractor shall perform and/or provide input and recommendations in the following activities:

a. Developing and maintaining program schedules including logic-based networks for PdM Radars programs/systems

b. Assessing planned (Government and/or prime contractor) schedules against contract dates and other known and/or conflicting schedule events

c. Performing critical path analysis on both contractor and Government schedules

d. Conducting schedule risk assessments on both contractor and Government schedules

e. Modifying, developing, and maintaining software programs for the development, maintenance, and recurring assessment of schedules

f. Developing schedule assessment techniques

g. Evaluating COTS software scheduling/assessment tools

3.2.6.4 IT Support. The contractor shall support and maintain, process, and troubleshoot, computer systems, networks, hardware and software. The contractor shall provide customer and network administrative services and operations.

3.2.7 Logistics (Fielding / NET / De-fielding)

3.2.7.1 General

3.2.7.1.1 The contractor shall be capable of fully supporting materiel fielding and NET requirements within 30 days of contract award. The contractor shall support initial issue, materiel fielding and NET requirements at locations specified by PdM Radars, including but not limited to:

a. Support the preparation and conduct of briefings

b. Review of training material, technical manuals or updates thereof due to engineering changes, modification work orders, configuration changes and variant changes to the end item;

the review of training material, technical manuals or updates thereof may occasionally include incidental correction of format, punctuation or other minor errors

c. System installation and checkout

d. Configuration of software fielding

e. Post-fielding assessments for CONUS and OCONUS locations

3.2.7.1.2 The contractor shall:

a. Integrate training of separate sub-system, testing, quality assurance, configuration management, logistics, engineering, production, transportation, maintenance and logistics support for all PdM Radars products

b. Coordinate all special training actions necessary to support the program’s acquisition strategy, conduct all necessary coordination between stakeholders and resolve training related issues

c. Assist PdM Radars in managing the fielding/NET, displaced equipment training (DET), delta training, new software training (NST), down-sizing of Operation Enduring Freedom (OEF) and de-fielding efforts.

d. Schedule, track, and coordinate, via the Total Package Fielding (TPF) concept outlined in AR 700-142, to ensure all PdM products are delivered

e. Provide data and briefings to PdM Radars leadership

3.2.7.2 On-Site Fielding/NET Support. The contractor shall provide experienced, fully cross-trained and technically proficient personnel possessing appropriate security clearances and certifications to serve as fielding/NET team members to conduct initial fielding, training, field support, and support of operational exercises and any developmental or operational testing.

Fielding/NET team members are subject matter experts (SMEs) on all aspects of planning, coordination, integration, training, testing, fielding, sustainment, repair, and logistics activities for PdM Radars’ portfolio of systems. Fielding/NET Team members serve as the liaison between the PdM Radars, the gaining unit, Force Modernization, TYAD, and the OEM FSR for all radar fielding efforts. Fielding/NET team members receive direction from the Government Fielding Chief who serves as the single point of contact during a fielding event. Fielding/NET team members:

a. Provide technical, tactical, and logistical insight for the reliability, maintainability, and supportability of PdM Radars’ portfolio of systems

b. Collect data from Army units for the fielding requirements, facilities, manpower support, shipping info, and points of contact

c. Develop installation and new equipment training schedule

d. Conduct new equipment and sustainment training at unit locations

e. Coordinate assets and resources to ensure adherence to fielding schedules

f. Coordinate with PdM Radars in response to system integration requirements and the integration of engineering change orders into previously fielded systems

g. Develop and facilitate New Material Introductory Briefs (NMIB) to gaining units, prior to materiel fieldings

3.2.7.3 Contractor Fielding Coordinator. The fielding coordinator:

a. Coordinates and conducts pre-fielding inventories of radar systems end items to include component of end item (COEI), additional authorization list (AAL), and basic issue items (BII)

b. Coordinates and conducts pre-fielding performance testing of radar systems prior to hand-off to unit

c. Coordinates and conducts hand-off procedures for systems to be added to the gaining units’ property book via Property Book Unit Supply Enhanced (PBUSE) through the Brigade (BDE) Property Book Officer (PBO)

d. Serves as the on-site liaison and single point of contact for PdM Radars, to address and resolve all concerns with all parties involved

3.2.7.4 Daily Fielding Report to Government. The contractor shall maintain daily contact with the PdM Radars Fielding Lead on the fielding progress, status, and completion. The dialogue shall provide complete details on the fielding to include the name and number of systems fielded, the recipient of the fielded equipment, the date(s), and the names of contractors’ personnel involved in the fielding, and any incidents or problems.

3.2.7.5 Staffing/Surge Support Staffing. On a quarterly basis, the contractor shall meet with the COR and the PdM Radars Fielding Team Lead to discuss current or potential mission needs, in order that the contractor may adjust the staffing of contractor personnel as necessary. The contractor shall also support short-notice fielding, training and testing events. The contractor shall have the necessary technical depth and appropriate certifications to support such surge events, as well as surge requirements for studies, reviews, technology insertions and capability integrations into PdM Radars’ portfolio of systems, without affecting current fielding/NET support. Contractor SMEs shall be available to travel on short-notice to CONUS and OCONUS locations to support surge requirements. The contractor shall respond to PdM Radars’ requests for surge support within 24 hours’ notice of request. Response and support shall directly address the Government’s request.

3.2.7.6 Contractor Operation of Government Vehicles/Equipment. Contractor employees assigned to operate either Government owned or leased equipment to include tactical vehicles in the performance of this contract shall be certified, by the contractor and at the contractors’ expense, as being fully qualified to operate the vehicles/equipment associated with PdM Radars and shall possess the required licenses and insurances to operate all vehicles or equipment necessary to perform under the contract. . The contractor shall document all operator qualifications.