PWS_W56KGY-16-R-0004_SETA_24_Dec15_('draft').pdf

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

Attachment No. 1

Systems Engineering and Technical Assistance (SETA) Support for

Product Manager Radars

Counter-Rocket, Artillery, Mortar Program Directorate

Program Executive Office, Missiles and Space

PERFORMANCE WORK STATEMENT

24 December 2015

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.

1.1 PERIOD OF PERFORMANCE / PLACE OF PERFORMANCE

1.1.1 The Period of Performance entails one 12-month base period and two 12-month option periods.

1.1.2 Work shall be primarily performed at offices and facilities at PdM Radars, Aberdeen

Proving Ground, MD.

1.1.3 CONUS Temporary Duty (i.e., less than 180 days) Locations include: New York; New

Jersey; Alabama; Oklahoma; Washington D.C.; Arizona; Pennsylvania and other locations as required.

1.1.4 OCONUS Temporary Duty Locations include: Afghanistan, Iraq, Kuwait England, Germany, Korea, Israel and other locations as required.

1.1.5 CONUS (180 days or more) Locations include: Yuma Proving Ground, AZ and other locations as required.

1.1.6 OCONUS (180 days or more) Locations include: contingency theater of operations as required such as Iraq, Ukraine, Afghanistan, Korea and other locations as necessary, as determined by applicable Joint Travel Regulations (JTR), dated 01Nov14.

1.2 HOURS OF OPERATION

The Contractor is responsible for providing 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.

1.3 GOVERNMENT FURNISHED EQUIPMENT / MATERIALS / FACILITIES

Subject to space constraints, the Government will provide office space for 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 Employees’ 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 Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. 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. These meetings shall be at no additional cost to the Government. See also paragraph 3.2.6.10.

2.0 APPLICABLE DOCUMENTS

a. AR 700-127 (Integrated Logistics Support)

b. DA PAM 700-127 (Integrated Logistics Support Managers Guide)

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

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

e. AR 70-47 (Engineering for Transportability)

f. AR 70-1 (Army Acquisition Policy), DA PAM 70-1 (Instructions for Army Acquisition

Policy)

g. AR 750-1 (Army Materiel Maintenance Policy), AR 750-10 (Army Modification

Program)

h. DA PAM 700-56 (Logistics Supportability Planning and Procedures in Army

Acquisition)

i. 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)

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

k. AR 25-2 (Information Assurance)

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

m. DoDI 5000.02 (Operation of the Defense Acquisition System)

n. DoDI 5230.24 (Distribution Statements on Technical Documents)

o. PdM Radars Acceptable Use Policy

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

q. AR 381-12 (Threat Awareness and Reporting Program (TARP))

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 (DD-254), 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 have a Top Secret facility clearance. The contractor shall not store any classified information at the contractor facility. The Contractor will require access to COMSEC information and information from For Official Use Only (FOUO), up to and including, TS Non-SCI intelligence information. The contractor will also require access to Security/Program Classification Guide(s) (SCG), the SIPRNET, 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 (CDRL A001), unless required to be submitted earlier by the PWS.

Simple spreadsheet or other contractor format is acceptable.

3.1.4.1 DOD Information Assurance 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 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 7 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 sub-contractor employees shall receive Government-provided area of responsibility (AOR) specific AT awareness training as directed by AR 525-13. 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 sub-contractors 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 https://jkodirect.jten.mil/ 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 7 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 Per AR 530-1, Operations Security (OPSEC) Awareness Training: 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/Information Assurance (IA) Training and Support

3.1.4.6.1 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. All contractor employees and associated sub-contractor 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 Threat Awareness Reporting Program (TARP): 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: DFARS Clause 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 sub-contractor 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” (FAR 52.204-9), Contractor workforce must comply with all personal identity verification requirements as directed by DoD, HQDA, 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 Requiring a 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: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2)

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

(3) 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 FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

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. 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. The contractor shall ensure understanding and compliance with the PdM Radars

Acceptable Use Policy (AUP) regarding personnel responsibilities and limitations in using organizational or DoD Information Systems. 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 System Future Years Defense Plan

(PPBS/FYDP): In accordance with DoD Directive Number 7045.14, Change 1 dated 28 July

1990, paragraphs 4.7 and 4.8, contractors are not allowed access to PPBS 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 all PdM Radars related 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.12 Marking of Documents

3.1.12.1 All PdM Radars 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 in accordance with the SCG. Examples of program technical documents are:

• Technical Manuals/documentation

• Maintenance Manuals/documentation

• HW/SW Configuration Items/Documents

• Contract Data Requirements List

• Software Version Description

• System/Architectural Designs

• Engineering Drawings

• System Specifications

• Technical Data Packages

• Program Security Documents

• Reports and document deliverables

• Test Plans/Reports

• User Guides/SOP

• Acquisition/Logistical support documents

3.1.12.2 Program Technical and/or acquisition documents listed above and the like, shall be marked as follows:

3.1.12.2.1 For all unclassified and FOUO documents and media ---

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.12.2.2 For all technical documents that are determined to contain export-controlled technical data shall also be marked in accordance with 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.12.2.3 For all FOUO material and technical documents transmitted outside the DoD ---

This document contains information

EXEMPT FROM MANDATORY DISCLOSURE

Under the FOIA

3.2 CONTRACTOR-PROVIDED SERVICES

The services to be provided by the contractor under this PWS are described in the subparagraphs that follow.

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; specifically, the

Contractor shall make recommendations regarding: systems life cycle performance requirements;

acquisition strategies and plans; the development, maintenance and tracking of acquisition program baseline documents; the development of spend plans and spreadsheets; long range plans and program accomplishments in relation to program objectives, taking into account any known or potential budgetary, schedule or technical constraints; and general compliance with DoDI

5000.02 and all acquisition streamlining reform initiatives. Additionally, the Contractor shall act as liaison with the TRADOC community and 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, Department of the Army 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 Federal Acquisition Regulation (FAR) and Defense Federal

Acquisition Regulation Supplement (DFARS) guidance for final review and approval by the

PdM Radars for the Government. The contractor shall provide support in planning and preparing

Acquisition Requirements Packages (ARPs) for contracts on PdM Radars systems. The contractor shall provide input to contract documents such as: performance work statements, performance specifications, system architectures, delivery schedules, contracting documentation and Government Furnished Equipment List.

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 Process

Teams (IPTs) and Process Management.

3.2.2 ENGINEERING

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

3.2.2.1 Test Support. 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, to include review of test plans and procedures for accuracy and adequacy; assist with design tests to include support to the

Government for planning test resource requirements; witness tests and provide technical support;

assist with the preparation of government coordinated test plans in accordance with appropriate

Army regulations; and analyze/evaluate test results.

3.2.2.2 Requirements Generation and Baseline Configuration Support. The Contractor shall provide engineering support to PdM Radars systems to include: requirements/capabilities gap analysis; providing input to user capability needs in accordance with the Joint Capabilities

Integration and Development System (JCIDS) process (e.g., systems’ Capabilities Production

Document (CPD)); analyses and translation of user capability needs/requirements into performance specifications for all program systems; providing 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; support of design reviews and provide input to the Government in the design approval process; configuration management, including support of engineering change proposal (ECP) process and conduct of physical and functional configuration audits; 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. The Contractor shall 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 technical risk evaluations; Office of Management and Budget (OMB) reports (e.g., Capital

Investment Report/Exhibit 300); Congressional inquiries; audits; other programmatic documentation, program schedules, information papers and briefings.

3.2.2.3 Acquisition Support.

3.2.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.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, 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.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 LOGISTICS — Other Than FIELDING / NEW EQUIPMENT TRAINING /

DEFIELDING

3.2.3.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 integrated logistics issues pertaining to, but not limited to, documentation supporting integrated logistics support, MANPRINT, technical manuals, training, training materials, materiel fielding, total package fielding, New Equipment Training

(NET), provisioning, configuration audits, and technical data packages for PdM Radars systems, major assemblies, subassemblies, and replenishment parts.

3.2.3.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 may conduct training for Government personnel or foreign national personnel, if directed by the Government in the appropriate Letter of Agreement, to ensure proper operation, repair, maintenance and testing of platforms, systems, subsystems or items.

3.2.3.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.3.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 FINANCIAL MANAGEMENT

3.2.4.1 Program Budget Support. The Contractor shall assist the Government in the preparation of budgetary documentation in support of all PdM Radars programs. All documentation 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), etc. and be approved and signed by the Government. 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.4.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 Program Office

Estimates (POEs) utilizing automated cost modeling software. Additionally, the Contractor shall provide input for Life Cycle Cost analyses, O&S Cost Reduction Analyses, Cost Risk

Evaluation, Technical Risk, Evaluation, and Planning Programming Budgeting and Execution

System (PPBES) preparation efforts.

3.2.5 OPERATIONS

3.2.5.1 Administrative Support. The Contractor shall assist the Government in preparing, reviewing, and updating PdM Radars administrative documentation. Documentation shall include review and update of weekly suspense reports, major event calendars, good news reports and control of documents being staffed through PM C-RAM and PEO M&S. The Contractor shall provide technical/administrative support to include preparation of briefing notes and action items for program reviews, user conferences, and other support meetings. The Contractor shall provide quick response to Project Managers, Product Managers, Product Directors, functional support division chiefs and team leaders and their staffs for development of briefings, schedules, hardware/software requirements, and “what-if” budget and programmatic exercises.

3.2.5.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.5.3 Schedule Development/Assessment Support. The Contractor shall perform and/or provide input and recommendations in the following activities: developing and maintaining program schedules, including logic-based networks for PdM Radars programs/systems; assessing planned (Government and/or prime Contractor) schedules against contract dates and other known and/or conflicting schedule events; performing critical path analysis on both Contractor and

Government schedules; conducting schedule risk assessments on both Contractor and

Government schedules; modifying, developing, and maintaining software programs for the development, maintenance, and recurring assessment of schedules; developing schedule assessment techniques; and evaluating COTS software scheduling/assessment tools.

3.2.5.4 Information Technology 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.6 LOGISTICS — FIELDING / NEW EQUIPMENT TRAINING / DEFIELDING

3.2.6.1 General.

3.2.6.1.1 The Contractor shall support initial issue, materiel fielding and NET requirements at locations specified by PdM Radars, to include the preparation and conduct of briefings, review of training material and technical manuals and update as required due to engineering changes, modification work orders, configuration changes and variant changes to the end item, system installation and checkout, configuration of software fielding, and post-fielding assessments for

CONUS and OCONUS locations. The Contractor shall be capable of fully supporting materiel fielding and NET requirements within 30 days of contract award.

3.2.6.1.2 Specifically, the Contractor shall (1) integrate training of separate sub-system, testing, quality assurance, configuration management, logistics, engineering, production, transportation, maintenance and logistics support for all PdM Radars products; (2) coordinate all special training actions necessary to support the program’s acquisition strategy, conduct all necessary coordination between stakeholders and resolve training related issues; (3) assist PdM Radars in managing the Fielding/NET, Displaced Equipment Training (DET), Delta Training, New

Software Training (NST), down-sizing of OEF and Defielding team efforts; (4) schedule, track and coordinate, via the Total Package Fielding (TPF) concept outlined in AR 700-142, to ensure all PdM products are delivered; and (5) provide data and briefings to the PdM Radars leadership.

3.2.6.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 PM Office, 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 (1) provide technical, tactical, and logistical insight for the reliability, maintainability, and supportability of PdM Radars’ portfolio of systems; (2) coordinate with

Army units for the actual fielding including requirements, facilities, manpower support, shipping info, and points of contact; (3) make daily coordination with gaining units; (4) develop installation and new equipment training schedule; (5) conduct new equipment and sustainment training at unit locations; (6) coordinate assets and resources to ensure adherence to fielding schedules; and (7) coordinate with PdM Radars in response to system integration requirements and the integration of engineering change orders into previously fielded systems. Develop and facilitate New Material Introductory Briefs (NMIB) to gaining units, prior to materiel fieldings.

3.2.6.3 Contractor Fielding Coordinator. The fielding coordinator (1) coordinates and conducts pre-fielding inventories of radar systems end items to include Component of the End Item

(COEI), Additional Authorized Listing (AAL), and Basic Issue Item (BII); (2) coordinates and conducts pre-fielding performance testing of radar systems prior to hand-off to unit; (3) 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; and (4) 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.6.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.6.5 Staffing. The Contractor shall on a quarterly basis 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.

3.2.6.6 Surge Support/Staffing. The Contractor shall support short-notice fielding, training and testing events. The Contractor shall have the necessary technical depth 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 must be willing and able to travel on short-notice to CONUS and

OCONUS locations to support surge requirements. Contractor shall respond to PdM Radars’ requests for surge support within 24 hours of request. Response and support shall directly address the Government’s request.

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

The Contractor shall document all operator qualifications. This documentation shall be provided to the Administrative Contracting Officer and the PdM Fielding Lead before any contract employees engages in any mode of equipment operation.

3.2.6.8 Instructor and Key Personnel (IKP) Training. Fielding/NET team members shall perform

IKP training, which is the technical training that supports the initial transfer of knowledge on the operation and maintenance of new equipment as a means of establishing a training capability.

3.2.6.9 Disposal/Defielding. The Contractor shall assist the units in identifying equipment and inventory and shall provide Second Destination Transportation Code for the shipment of equipment classified for disposal to the Army Depots. The Contractor shall provide defielding operations support to include recommending priorities and objectives for the planning and execution of defielding operations and resource management efforts.

3.2.6.10 The Government will evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP), which is an attachment to the contract.

4.0 DATA ITEM DELIVERABLES

The data items to be delivered under the contract are summarized below. Specific requirements are set forth in the associated Contract Data Requirements Lists (CDRLs) (DD Forms 1423), which are exhibits to the contract.

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

The Monthly Status Report shall (a) clearly outline the efforts performed by the Contractor during the reporting period and the status of those efforts; (b) clearly describe any accomplishments, problems or issues that would affect the timely completion of the contract; and

(c) include funds and man-hours expenditure.

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

Reports of conferences, working group meetings, and trips associated with this contract shall address the following:

a) Objective/goal of conference/working group/trip, along with reason for travel;

b) Contract task that the trip supports;

c) Radar program that the trip supports;

d) Itinerary – list work performance locations only;

e) Degree of success – describe the level to which the stated objectives are met;

f) Technical issues encountered – provide an estimate of the cause of the technical issue as well as a proposed solution;

g) Contacts made – list and describe relevant contacts made with other Government personnel, contractors, and foreign nationals encountered; and

h) Any other relevant information.

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

Program and program system engineering technical assessments shall reflect compliance with

PWS Paragraph 3.2.2.3.3.

5.0 TRAVEL OR MATERIAL REQUIREMENTS

Costs for transportation may be based upon mileage rates, actual costs incurred, or a combination of thereof, provided the method used results in a reasonable charge. Travel costs shall be considered reasonable and allowable only to the extent that they do not exceed on a daily basis, the maximum per diem rate in effect at the time of the travel. The JTR, while not wholly applicable to Contractors, shall provide the basis for the determination as to reasonable and allowable. Maximum use is to be made of the lowest available customary standard coach or equivalent airfare accommodations available during normal business hours. All necessary travel meeting the above criteria shall be reviewed in advance by the PdM Radars Contracting Officer's

Representative or Contracting Officer and reimbursed at JTR rates. Exceptions to these guidelines shall be approved in advance by the Contracting Officer or his/her designee.

6.0 IRAQ / AFGHANISTAN / KUWAIT / OTHER LOCATIONS /

SPECIAL REQUIREMENTS

If travel to Iraq, Afghanistan, Kuwait or other locations is necessary, C-JTSCC Acquisition

Instruction (AI), Appendix 2 – Part 52, CENTCOM Theater Business clearance clauses and provisions shall be incorporated on an as needed basis by contract modification.

7.0 CONTRACTOR EMPLOYEES DEPLOYED TO REPUBLIC OF KOREA

See the clause in Section H of the contract entitled, “Invited Contractor or Technical

Representative Status Under U.S. - Republic of Korea (ROK) Status of Forces Agreement

(SOFA).

8.0 DEPLOYMENT REQUIREMENTS (as governed by AR 525-93)

8.1 Legal

If a SOFA is in place, contractor personnel deployed with the supported unit will be covered by the SOFA to the same extent as soldiers of the supported unit. If a SOFA is not in place, the commander of the deployed unit will ensure legal protection for deployed contractor personnel to the same extent as that provided to soldiers of the supported unit.

8.2 Standard Identification Cards

Contractor personnel will receive a CAC or a DD Form 2764, and personal identification tags as part of the processing for overseas movement. If the contractor processes its personnel for deployment, it is the contractor’s responsibility to ensure that contractor personnel possess the required identification prior to deployment. In such instances, the Government will provide the contractor with a point of contact (POC) and reasonable direction to proceed. Upon completion of deployment, the contractor shall ensure that all issued controlled identification cards and tags are returned to the Government.

8.3 Tour of Duty/Hours of Work

The individual’s tour of duty will be defined by the Government at the time of deployment notification. Hours of work are the hours worked during the normal workday. The normal workday, when deployed, will be 12 hours per day, seven days per week, or other durations depending on the operational needs. The contractor may rotate qualified replacement contractor personnel into the location when an individual’s tour of duty has been satisfied.

8.4 Allowable Cost and Reimbursable

To accommodate the additional cost and inherent risk associated with deployment status, additional premiums for hardship and hazardous duty are authorized, to be billed as ‘other direct costs’ on a per hour basis. The differentials paid will be in accordance with the Department of

State guidelines for countries within the requested geographical areas.

9.0 ORGANIZATIONAL CONFLICT OF INTEREST

All functions related to acquisition support shall be on an advisory basis only. The Contractor is advised that, since the Contractor will provide systems engineering, technical direction, specifications, work statements, and evaluation services, the Contractor may be restricted from participation in certain activities in accordance with FAR 9.5. Accordingly, prior to commencement of services under this PWS, the Contractor shall execute and return to the

Contracting Officer the Non-Disclosure Agreement (NDA) at Appendix A of this PWS, and all

Contractor employees covered by the NDA shall execute and return to the Contracting Officer the Personal Financial Interest/Protection of Sensitive Information Agreement, also at Appendix

A of this PWS.

10.0 CONTRACTOR MANPOWER REPORTING REQUIREMENTS

See the clause in Section C of the contract entitled, “Accounting for Contract Services

Requirement – Enterprise-Wide Contractor Manpower Reporting Application (June 2013).”

APPENDIX A

CONTRACTOR NON-DISCLOSURE AGREEMENT

This Agreement refers to Contract/Order ______________ entered into between the US

Government and _________________________ (Contractor).

As an officer of (fill in name of Contractor), authorized to bind the company, I understand that in connection with our participation in the Systems Engineering and Technical Assistance (SETA)

Support for Product Manager Radars (PdM Radars SETA Support) acquisition under the subject

Contract/Order, Contractor’s employees may acquire or have access to procurement sensitive or source selection information relating to any aspect of the PdM Radars SETA Support acquisition.

Company ( fill in name) hereby agrees that it will obtain Contractor - Employee Personal

Financial Interest/Protection of Sensitive Information Agreements from any and all employees who will be tasked to perform work under the subject Contract/Order prior to their assignment to that Contract/Order. The Company shall provide a copy of each signed agreement to the

Contracting Officer. Company (fill in name) acknowledges that the Contractor - Employee

Personal Financial Interest/Protection of Sensitive Information Agreements require Contractor’s employee(s) to promptly notify Company management in the event that the employee releases any of the information covered by that agreement and/or whether during the course of their participation, the employee, his or her spouse, minor children or any member of the employee’s immediate family/household has/or acquires any holdings or interest whatsoever in any other private organization (e.g., Contractors, offerors, their subcontractors, joint venture partners, or team members), identified to the employee during the course of the employee’s participation, which may have an interest in the matter the Company is supporting pursuant to the above stated

Contract/Order. The Company agrees to educate its employees in regard to their conflict of interest responsibilities.

Company (fill in name) further agrees that it will notify the Contracting Officer within 24 hours, or the next working day, whichever is later, of any employee violation. The notification will identify the business organization or other entity, or individual person, to whom the information in question was divulged and the content of that information. Company (fill in name ) agrees, in the event of such notification, that, unless authorized otherwise by the Contracting Officer, it will immediately withdraw that employee from further participation in the acquisition until the OCI issue is resolved.

This agreement shall be interpreted under and in conformance with the laws of the United States.

Signature and Date Company

Printed Name Phone Number

CONTRACTOR EMPLOYEE

PERSONAL FINANCIAL INTEREST/PROTECTION OF SENSITIVE INFORMATION

AGREEMENT

This Agreement refers to Contract _____________________ entered into between the US

Government and ____________________(Contractor).

As an employee of the aforementioned Contractor, I understand that in connection with my involvement in the support of the above-referenced Contract/Order, I may receive or have access to certain “sensitive information” relating to said Contract/Order, and/or may be called upon to perform services which could have a potential impact on the financial interests of other companies, businesses or corporate entities. I hereby agree that I will not discuss or otherwise disclose (except as may be legally or contractually required) any such “sensitive information” maintained by the Government or by others on behalf of the Government to any person, including personnel in my own organization, not authorized to receive such information.

“Sensitive information” includes:

(a) Information provided to the Contractor or the…