Pre-Award ATFP Follow-on PWS DRAFT.pdf

PERFORMANCE WORK STATEMENT (PWS)

For

Anti-Terrorism/Force Protection (AT/FP) Electronic Surveillance Systems (ESS)

1. SCOPE

1.1 The Space and Naval Warfare Systems Center Pacific (SSC PAC) Security Systems

Branch, Code 4118, has a requirement to provide life cycle sustainment, installation, integration, testing and procurement/acquisition support for Anti-Terrorism/Force Protection (AT/FP) Electronic Surveillance Systems (ESS) during their life cycle and to provide technical expertise to Naval Facilities Engineering Command (NAVFAC), Commander Naval Installation Command (CNIC), Navy Munitions Command (NMC), Naval Mine and Anti-Submarine Warfare Command (NMAWC), Strategic Weapons Facility Pacific (SWFPAC), United States Marine Corps, the Program Executive Offices (PEO), other Department of Defense (DOD) agencies, Department of Homeland Security (DHS), United States Coast Guard (USCG), Customs and Border Protection (CBP), and other Government activities as required. Specifically, Code 4118 performs the procurement, installation, integration, testing and life cycle sustainment of Naval ATFP ESS at shore installations throughout the world. Systems/equipment and services are defined as equipment and/or systems that facilitate the detection, delay, deterrence, assessment, and response to terrorist events. Sustainment services include: preventive and corrective maintenance, interoperability, maintenance planning, supply/logistics support, testing and evaluation, reliability and maintainability, and configuration management.

1.2 Code 4118 provides the support necessary to carry out the day-to-day operations and maintenance of hardware, software and related equipment. The scope of this effort includes the following services:

Security System procurement, installation, integration, and testing including:

o Site Surveys o Pre-Installation Test and Checkout (PITCO) o System Operational Verification Test (SOVT)

Lifecycle Sustainment Support of systems and equipment, hardware and software applications, to include:

o Preventative Maintenance o Corrective Maintenance (Equipment Repair, Overhaul, or replacement)

Information Assurance (IA) Life Cycle Sustainment support (DoD Information

Assurance Certification and Accreditation Process (DIACAP) process support, Approvals To Operate (ATO), software upgrades, security patches, and documentation)

Spare parts management 24/7 CNIC Help Desk Operations and Service Call Management to provide end to end life cycle sustainment support to include:

o Response and Resolution of Service Calls o Asset and Configuration Management o Contract Support and Data Requirements

Systems engineering and project management services requirements include, but are not limited to, providing recommendations for assessments of effectiveness, standardization, regional systems solutions, engineering efficiencies, reduction in total ownership costs, reduction of manpower, enterprise network solutions, and recommended design and technical solutions based on Commercial Off-the-Shelf (COTS) technology

SharePoint based application life cycle sustainment support o AT/FP Information Management (AIM) system o Next generation application implementation o IA requirements

Alarm System life cycle sustainment support for CONUS/OCONUS naval facilities currently terminating in the facility / local dispatch centers (LDC) to include Intrusion Detection Systems

Wide Area Alert and Notification integration and life cycle sustainment support which includes the Automated Telephone Notification System /Computer Desktop Notification System (ATNS/CDNS) life cycle support and Mass Notification systems Giant Voice and Indoor Voice

Regional Dispatch Center (RDC) integration and life cycle sustainment support Enterprise Land Mobile Radio (ELMR) life cycle sustainment support Security Surveillance Systems integration and life cycle sustainment support Physical Security/Access Control (PS/AC) integration and life cycle sustainment support Telephony / Telecommunication infrastructure integration and life cycle sustainment support.

1.3 The systems provide the capability to receive/transmit orders, receive and process information into situational awareness displays, support command decision processes and communicate electronic data to multi-service, multi-agency nodes across the entire all-hazards/all-threats spectrum of Ashore and Afloat operations. These systems also provide all-hazard warnings to all personnel on board the installation, and others as appropriate.

The system specifics are summarized as follows:

The Regional Operations Center (ROC) and Emergency Operations Center (EOC) serves as the C4I point for information gathering, gain situational awareness, and exercise control over forces from early warning and detection of suspicious events through response and recovery.

The Regional Dispatch Center (RDC) command facility is the hub for all emergency communications between Navy citizens and the First Responders in a Navy Region.

The term RDC is intended to address the overarching RDC capability and all related subsystems within the RDC Family of Systems (FoS), to include, but not limited to, the Navy Emergency Response Management System (NERMS) and Enterprise NERMS (e-NERMS): Computer Aided Dispatch (CAD), Alarm Monitoring Automation System (AMAS), Records Management System (RMS), Mobile Data Computers (MDC), Navy 911, E-911, and ALI, Navy Emergency Management Addressing Project (NEMAP), Geographic Information System (GIS), and the Emergency Call Management System (ECMS).

Wide-Area Alert and Notification (WAAN) systems are utilized to update and disseminate information concerning a terrorist threat or danger, or if an incident has occurred. This includes procedures and techniques necessary to counter the threat and may include civil distribution systems, audio, signage or warning signals and e-mail via Navy Marine Corps Intranet (NMCI) or NGEN wide area network of computers.

Giant Voice (GV) is part of the Wide Area Alert and Notification (WAAN) suite of systems. GV is comprised of an Outdoor Voice/Alert function and a System Control function. The outdoor alert function is intended to provide initial alert and follow-on directions to personnel not located in a building. The System Control function allows authorized personnel to operate the system manually or autonomously. The outdoor component consists of the outside speaker(s) positioned on pole(s) and buildings across the installation. The Giant Voice system is installed as a base-wide system to provide a siren signal and pre-recorded and live voice messages. In order to create the right level of sound output, multiple poles and speakers will be positioned across the installation.

Indoor Voice (IV) is part of the individual building Mass Notification Systems (MNS) and is comprised of Indoor Voice, Interior Notification, and System Control functions. The Indoor Voice (IV) function is intended to provide real-time alert and follow-on directions to personnel inside and around buildings who may or may not have direct access to a telephone or computer. The System Control function allows authorized personnel to operate the system manually or autonomously. The Interior Notification function is intended to be provided by loud speakers, warning lights, and illuminated signs or displays. Speakers are provided at all locations in and around the building at entrances/exits and other outdoor areas (such as courtyards) commonly used by the building occupants.

Automated Telephone Notification System (ATNS) provides military installations with the ability to rapidly and effectively disseminate emergency alerting and notifications throughout the telephone and data network environments, including signals or messaging appropriate to force protection conditions (FPCONs), weather conditions, watches, warnings, evacuation routes, and other alerting information to meet Department of Defense (DoD) and federal warning requirements.

Computer Desktop Notification System (CDNS) provides Navy installations with the ability to rapidly and effectively disseminate emergency alerting and notification information throughout the data networks environment, including signals or messaging appropriate to FPCONs, information operations conditions (INFOCONs), watches, warnings, evacuation routes, and other alerting information to meet DoD and federal warning requirements.

Sensor Infrastructure, Integration, and Alarm Notification. Equipment Sensors and Alarm interfaces are part of the Navy Emergency Response Management System (NERMS) Alarm Monitoring and Automation System (AMAS) located at a Regional Dispatch Center (RDC). The RDC AMAS receives signals from and continuously polls all interfaced physical security and fire alarm system equipment sensors which result in the return of alarm signals. AMAS is divided into two systems, one local and one regional (LAMAS and RAMAS). Sensors and sensor interfaces/infrastructure are installed to provide alarm notification and alarm management to all command dispatch centers. This infrastructure integrates/interfaces all existing Fire Alarm, Access Control Systems (ACS), Intrusion Detection Systems (IDS), and Central Alarm Station Receiving/Monitoring Systems with LAMAS and/or RAMAS and then interfaces LAMAS with RAMAS.

o Access Control Systems (ACS) include screening, controlling, validating, and detecting authorized and unauthorized access at entry control points to installations, piers, harbors, ships, and incident sites from land. This includes physical restraints to prevent unauthorized access through perimeter security to installations, buildings, restricted areas, piers, harbors, family housing and incident sites from land.

Physical Security/Access Control (PS/AC). Physical security and access control which is comprised of the following: Automated Vehicle Gate (AVG), Automated Pedestrian Turnstile (APT), Enclaves, Electronic Security Systems, and Physical Security Information Management (PSIMS). PS/AC systems include: Physical Access Control System (PACS) software, either Lenel, AMAG, or another vendor's solution; License Plate Reader (LPR) systems S/W; iCX Chameleon for custom gate C2; various types of Video Management Systems (VMSs); as well as databases utilizing Oracle or MS SQL.

Security Surveillance Systems include the capability to detect and identify unauthorized movement of personnel, vehicles and material in or around installations, piers, harbors, ships, restricted areas, and incident sites

Sensor Management System (SMS) Telephony / Telecommunication infrastructure coordination, integration and sustainment of telephony interfaces, software applications, and hardware equipment utilized between local commercial telephony providers and county telephony agencies to the base BCO and the regional naval RDC/LDC end users.

Joint Perimeter Surveillance Command and Control System (JPSC2) Radar Sonar Surveillance Center (RSSC) and Communications Detachments

(COMMSDET) operating the Mobile Ashore Support Terminal (MAST IIIs) for Coastal Riverine Force

ELMR Backbone CONUS/OCONUS sustainment to include access of proprietary information to program, integrates, and configures ELMR components as required.

SharePoint based application system support PSNet enterprise connectivity Assess Control Systems and Intrusion Detection Systems integration and sustainment Electronic Harbor Security Systems (EHSS) C4I installation and integration requirements.

Aruba Wireless Solutions (WIFI)

2. APPLICABLE DOCUMENTS

2.1 DEPARTMENT OF DEFENSE DOCUMENTS

2.1.1 DOD 5000.2-M, Department of Defense Manual, Defense Acquisition Management Documentation and Reports.

2.1.2 DOD Directive 5000.1, Defense Acquisition.

2.1.3 DOD INST 5000.2, Defense Acquisition Management Policies and Procedures

2.1.4 DOD 5220.22-M (Series), National Industrial Security Program Operating

Manual (NISPOM)

2.1.5 DODINST 6055.17 Mass Warning and Notification

2.1.6 DODINST 5310.84, Security of DOD Personnel at U.S. Missions Abroad

2.1.7 DODINST 2000.12, DOD Antiterrorism/Force Protection Program

2.1.8 DODINST 2000.16 DOD Antiterrorism Standards

2.1.9 DODINST 5239.1C, Navy Information Assurance (IA) Program

2.1.10 DODINST 6055.17, Installation Emergency Program (IEMP)

2.1.11 DODINST 5200.08-R, Physical Security Program

2.1.12 DODINST 8570.01-M, Information Assurance Workforce Improvement Program, Incorporating Change 3, January 24, 2012

2.1.13 DOD 5205.02 (Series), DOD Operations Security (OPSEC) Program

2.2 MILITARY HANDBOOKS

2.2.1 MIL-HDBK-245D, Preparation of Performance Work Statement

2.2.2 MIL-HDBK-419A, Grounding, Bonding, and Shielding for Electronic Equipment and Facilities

2.2.3 MIL-HDBK-454A, General Guidelines for Electronic Equipment

2.2.4 MIL-HDBK-61A, Configuration Management Guidance

2.2.5 MIL-HDBK-781A, Handbook for Reliability Test Methods, Plans and

Environments for Engineering, Development, Qualification and Production

2.2.6 MIL-HDBK-881A, Work Breakdown Structures for Defense Materiel Items

2.2.7 MIL-HDBK-2036, Preparation of Electronic Equipment Specifications

2.2.8 MIL-HDBK-46855A, Human Engineering Guidelines for Military Systems, Equipment and Facilities

2.3 MILITARY SPECIFICATIONS AND STANDARDS

2.3.1 MIL-E-17555H, Electronic/Electrical Equipment, Accessories and Repair Parts, Packaging/Packing.

2.3.2 MIL-M-85337A, Technical Manuals, QA Program Requirements

2.3.3 MIL-P-24534A, (Navy) Military Specification, Planned Maintenance System, Development of MRC, MIP, and Associated Documentation

2.3.4 MIL-PRF-29612B, Training Data Products

2.3.5 MIL-STD-130M, Identification and Marking of US Military Property

2.3.6 MIL-STD-740B, Airborne and Structure Borne Noise Measurements and

Acceptance Criteria

2.3.7 MIL-STD-1310G, Standard Practices for Shipboard Bonding, Grounding and

Other Techniques for Electromagnetic Compatibility and Safety

2.3.8 MIL-STD-1472F, Human Engineering

2.3.9 MIL-STD-2110(EC), Restoration, Overhaul, and Repair of Electronic Equipment.

2.3.10 MIL-STD-38784, Standard Practices for Manual, Technical, General Style and

Format Requirements.

2.4 OTHER GOVERNMENT DOCUMENTATION/INSTRUCTIONS

2.4.1 NAVSEA S0300-BD-PRO-010/020/030, VOLS I, II, III, ILS Procedures Manual for Systems/Equipment.

2.4.2 NAVSEA SL720-AA-MAN-010, Fleet Modernization Program (FMP) Management and Operations Manual.

2.4.3 NAVSEAINST 4130.12A, Configuration Management Plan Content Guidance and Practical Applications

2.4.4 NAVSEAINST 5000.39, Acquisition and Management of Integrated Logistic Support for Ships, Systems and Equipment

2.4.5 SECNAVINST 4130.2, Configuration Management Program

2.4.6 ASN RDA Memorandum, DON Policy on Digital Product / Technical Data of 23

Oct 2004

2.4.7 SPAWARSYSCEN PACIFIC: Shore Installation Process Handbook

2.4.8 ASN RDA Memorandums, Software Process Improvement Initiative Contract

Language Change of 17 November 2006

2.4.9 OPNAVINST 5513.4E, Classification Guide

2.4.10 OPNAVINST 5530.14E, Navy Physical Security and Law Enforcement Progra

2.4.11 OPNAVINST 3440.17, Regional Operations Centers

2.4.12 OPNAVINST 4790.4. Vol. I, Navy Maintenance and Material Management (3M), Planned Maintenance Subsystem (PMS).

2.4.13 HSPD-12, Homeland Security Presidential Directive

2.4.14 FIPS-201, Personal Identity Verification of Federal Employees and Contractors

2.4.15 UFC 4-010-1 DOD Minimum Antiterrorism Standards for buildings

2.4.16 UFC 4-022-1, Security Engineering: Entry Control Facilities

2.4.17 NAVADMIN 107-12 Navy Information Assurance Workforce and Operating

System/Computing Environment Certifications

2.4.18 SECNAV 5239.2, Department of the Navy Information Assurance (IA)

Workforce Management Manual

2.4.19 COMNAVCYBERFORINST 5239.1, Information Assurance Workforce

Improvement Program (IA WIP

2.4.20 SPAWARINST 5239.16 Information Assurance Workforce Improvement

Program Training, Certification and Workforce Management (IA WIP)

2.4.21 OPNAVINST F3300.53C (Series), Navy Antiterrorism Program

2.4.22 National Security Decision Directive 298 (Series), National Operations Security

Program (NSDD) 298

2.4.23 OPNAVINST 3432.1 (Series), DON Operations Sec

2.4.24 SPAWARINST 3432.1 (Series), Operations Security Policy

2.5 COMMERCIAL TECHNICAL MANUALS, STANDARDS, SPECIFICATIONS

AND PRACTICES.

2.5.1 ANSI/ASME-Y-14.5M: Dimensioning and Tolerancing for Engineering Drawings

2.5.2 ANSI/IEEE 315: Graphical Symbols for Electrical and Electronic Diagrams

2.5.3 ANSI/TIA-222-G-2005: Structural Standard for Antenna Supporting Structure and Antennas

2.5.4 NENA i3 Technical Requirements Document, NENA 08-751, Issue 1, 28 Sept

2.5.5 NFPA 1221: Standard for the Installation, Maintenance, and Use of Emergency

Services Communications Systems, 2010

2.5.6 APCO 25(Project 25) Standards

3. REQUIREMENTS

The contractor shall provide all labor, materials, equipment, and management or supervision necessary to perform the work identified within this PWS.

The contractor shall provide the following:

3.1 PROJECT EXECUTION SUPPORT

The contractor shall provide Project Execution support, including but not limited to:: preparing agendas, presentations, and minutes for project meetings; managing the cost and schedule processes and outputs (e.g., gathering data to generate various reports and upload to the AT/FP Information Management (AIM) Portal, as required); preparing, and delivering training materials, guidance and instruction to project execution personnel; and the development and presentation of various reports. Specific project execution support tasks, deliverables, and performance assessment metrics will be provided at the task order level.

3.2 PROGRAM SUPPORT

3.2.1 The contractor shall review maintenance methodologies and procedures, investigate areas requiring improved or additional personnel maintenance training/techniques, and provide recommendations for minimum maintenance requirements. Recommend revisions to existing technical support documentation.

3.2.2 The contractor shall review security requirements at various facilities and provide recommendations to the Government. Once individual site requirements have been validated, the contractor shall develop a security system concept and evaluate any technical design plans and component integration at sites specified

3.2.3 The contractor shall collect data, conduct engineering analyses and evaluate engineering parameters associated with long range planning for out-year programs to provide input for development, maintenance, and use of an advanced technology base.

3.2.4 The contractor shall prepare planning documents such as a Plan of Action and

Milestones (POA&M) for executing installations from initiation to completion.

3.3 INTEGRATED LOGISTIC SUPPORT (ILS) AND CONFIGURATION DATA

MANAGEMENT SUPPORT

3.3.1 The contractor shall support the sustainment of systems and equipment installed, including regionally installed equipment. This sustainment support includes, but is not limited to, developing ILS action item lists; developing ILS and Configuration Management Plan (CMP) input to the Program Management Plan (PMP); preparing ILS and sustainment updates to Project Execution documents (e.g., PWS template and appendices); prepare ILS inputs for briefings for PMR, QER, and road shows; maintaining ILS Master POA&M; providing oversight for preventive maintenance plans (including milestones and schedules), and developing/ and recommending overall maintenance policies and procedures.

3.3.2 The contractor shall verify system/equipment configurations. The contractor shall correct differences between installed configuration and authorized baseline including approved modifications. The contractor shall record and report all unauthorized modifications.

3.3.3 Specific ILS and Configuration Data Management (CDM) support tasks, deliverables, and performance assessment metrics will be provided in individual task orders.

3.4 ATFP INFORMATION MANAGEMENT (AIM) PORTAL SUPPORT

3.4.1 The contractor shall provide supporting the AIM Portal operating system;

maintaining AIM database integrity; preparing AIM Working Group (AIMWG) meeting agenda, minutes, and action item lists; developing and maintaining AIM processes, producing AIM reports (including summary reports of AIM costs and performance) and analyzing AIM System for efficiency and effectiveness.

3.5 INFORMATION SYSTEMS SECURITY SUPPORT

3.5.1 The contractor shall provide IA support for C&A for AT/FP systems through their lifecycle. The effort includes testing, mitigations, annual IA compliance, sustainment engineering support, and preparation and submission of C&A packages IN ACCORDANCE WITH the references in section 4.0 and DIACAP.

Enhancement can be viewed as the next generation of the system, when a new release is done on a system it will require a new IA package.

3.5.2 The contractor shall work with Government personnel to ensure compliance with all current Navy Information Technology (IT) & IA policies.

3.5.3 The contractor shall ensure that all integrated, installed, or operational application hosted on Navy networks are registered in the Department of the Navy (DON) Application and Database Management System (DADMS) and approved by the appropriate Functional Area Manager (FAM). The contractor shall ensure that all networks, servers, or associated devices procured and/or connected to a Navy network complete DADMS registration and receive FAM approval, as applicable.

The contractor shall ensure that all systems supported shall be registered within DoD Information Technology Portfolio Repository (DITPR). The contractor shall ensure that all systems supported shall be registered in Enterprise Mission Assurance Support Service (eMASS). The contractor shall ensure that all systems supported shall be documented, collected, and uploaded for FRCB approval to the SPAWAR PEO Integrated Data Environment and Repository (SPIDER).

3.6 SYSTEM ENGINEERING SUPPORT

3.6.1 The contractor shall routinely evaluate installed systems, subsystems, projects, activities, and develop recommendations to reduce Total Ownership Costs (TOC).

As needed, the contractor shall develop draft engineering plans and specifications, perform risk identification/analysis/mitigation, and perform traceability. In addition, the contractor shall suggest an integration solution. This may include building a working model of a system or group of systems. Typical associated tasks include, but are not limited to: computer-aided design, design studies and analysis, high-level detailed specification preparation, configuration management, and document control.

3.6.2 The contractor will be an active participant in engineering and requirements management in support of AT/FP systems. The contractor shall provide systems engineering expertise toward programmatic and sustainment engineering efforts including the following, as required: Risk Assessment; Test and Evaluation;

Integrated Product Team (IPT) participation; and laboratory interactions.

3.6.3 The contractor shall review, verify, update, or revise technical documentation for specified electronic equipment/systems, such as engineering drawings, technical manuals, provisioning data, configuration data, and training plans and provide written recommendations or reports.

3.6.4 The contractor shall review/draft/revise test plans, repair procedures, equipment documentation, modifications to existing baseline, and adequacy of technical support documentation and test instrumentation to insure that proper quality assurance is maintained in accordance with the current prescribed standards.

3.6.5 The contractor shall develop, analyze, revise and/or recommends changes to test procedures including Pre Installation Test and Checkout (PITCO) and System Operations and Validation Testing (SOVT).

3.6.6 The contractor shall update interface control documents (ICDs) as required.

3.6.7 The contractor shall conduct initial system/equipment installations, upgrades and certifications.

3.6.8 The contractor shall install, groom, test, checkout, and evaluate new systems/equipment.

3.6.9 The contractor shall perform obsolescence program research to identify suitable replacement piece parts and/or provide recommendations to purchase the form, fit, and functional parts for continuing equipment operation to meet mission requirements.

3.6.10 The contractor shall collect and/or correlate system, subsystem, unit, or component level maintenance, reliability, maintainability, or operational performance data.

3.6.11 The contractor shall develop or revise maintenance, reliability, maintainability, or operational performance parameter data bases, conduct analysis on selected parameters, and provide parameter baselines, comparisons to specifications or predictions, platform deviations from predicted or average performance, and make recommendations for changes to test methods, procedures, or specifications.

3.6.12 The contractor shall perform system/equipment tests, grooms, checks, upgrades, inspections, and certifications including SOVT.

3.6.13 The contractor shall perform comprehensive repair of designated systems/equipment.

3.6.14 The contractor shall perform system/equipment de-installation and/or removal.

3.6.15 The contractor shall perform on site analysis of system fault symptoms, assess degree of operational impairment / mission degradation, recommend alternate operational modes, and conduct all necessary repairs.

3.7 SOFTWARE ENGINEERING

3.7.1 The contractor shall identify and address risks, to identify resource requirements

(skill levels, facilities, computer resources) and schedules, to describe the metrics program, to define the contractor's software management organization and its interfaces, and to define use of automated tools.

3.7.2 The contractor shall employ well-defined written procedures for software metrics collection and analysis.

3.7.3 The contractor shall utilize software metrics, including product, productivity, quality, and management metrics, to assure the quality of all software and documentation produced.

3.7.4 The contractor shall prepare, develop, and maintain the following software support, operational, and change documentation: the technical preparation, impact evaluation/analysis, and planning necessary to implement or disapprove software change documentation.

3.7.5 The contractor shall provide technical support to the SSC Pacific Project Software

Change Control Board for the evaluation and disposition of all proposed changes to the software and documentation produced

4. REPORTS

4.1 PROGRESS AND FUND EXPENDITURE REPORTS

In all cases, the contractor shall prepare a comprehensive Monthly Status Report for active task orders. The specific format will be provided on the CDRL provided at the task order level. Such reports shall contain a separate breakdown for each active task order from date of award through submission of final billing. This mandatory report shall relate to the contractor’s established billing cycle and shall be delivered to the requiring activity within the time frame specified in the

CDRL.

5. OTHER

5.1 CYBER SECURITY (IA) WORKFORCE

5.1.1 The contractor shall ensure that personnel accessing cyber/information systems have the proper and current CS certification to perform CS functions identified in section 7 of this PWS in accordance with DoD 8570.01-M, Cyber Security Workforce Improvement Program. The contractor shall meet applicable cyber security certification requirements, including (a) DoD-approved CS workforce certifications appropriate for each specified category and level and (b) appropriate operating system certification for cyber security technical positions as required by DoD 8570.01-M. Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing cyber security functions

5.1.2 The contractor shall provide documentation supporting the cyber security certification status of personnel performing cyber security functions, reporting current CS certification status and compliance using CDRL Contractor Roster, DI-MGMT-81596 in the format prescribed by the COR

5.2 METHOD OF SURVEILLANCE

5.2.1 The Government will monitor and assess the contractor(s)’s performance against the Acceptable Quality Level in accordance with the clause at FAR 52.246-5 entitled “Inspection of Services – Cost Reimbursement.” The delivered products will be subjected to Government test and evaluation for performance and accuracy.

5.2.2 The Government will review the requirements, design, system functionality and performance to determine whether they are appropriate, comprehensive and in sufficient detail to successfully implement the target system. The Government will review requirements analysis reports, system test reports, inspection reports, monthly status reports, financial reports, training evaluations, help desk logs, system error logs, user comments, and other sources to determine if Government requirements and expectations are being met. The Government will monitor the contractor’s responsiveness. The contractor will be required to correct deficiencies.

5.3 ACCEPTANCE

The SSC Pacific Contracting Officer Representative (COR) is responsible for the acceptance of the final deliverable products/services. The COR will ensure that upon final acceptance, the task order has been satisfactorily completed, all deliverable products have been received and Government Provided Property and all residual materials, (notes, tech manuals, brochures, research material and remaining supplies), have been received

5.4 OVERTIME

Should overtime be required in the performance of any task under this contract, prior approval shall be required of the Ordering Officer, SSC Pacific Code 224, with verification and concurrence with the COR/technical code or as specified in each Task order.

6. TRAVEL

6.1 Travel may be required for the performance of the tasks. Estimates of travel requirements including destination, period of travel, number of personnel, and special requirements, if any, shall be specified in the individual delivery/task order PWS. Travel to various (ATC) Air Traffic Control sites, ships, and DOD/military installations and facilities may also required

6.2 If foreign travel is required, as specified per delivery/task order, all outgoing Country/Theater clearance message requests shall be submitted to the SPAWAR System Center Pacific foreign travel team, Topside, Building 27, 2nd Floor -Room 206 for action. A Request for Foreign Travel form shall be submitted for each traveler, in advance of the travel, to initiate the release of a clearance message at least 40 days in advance of departure. Each Traveler must also submit a Personal Protection Plan and have a Level 1 Antiterrorism/Force Protection briefing within one year of departure and a country specific briefing within 90 days of departure. Note: per OPNAVINST F3300.53C contractor employees must receive the AT/FP briefing annually.

CFA Yokosuka (Japan) CFA Sasebo (Japan) NAF Atsugi (Japan) NSF Diego Garcia (British Indian Ocean Territory) CFA Chinhae (South Korea) NRC Singapore (Republic of Singapore) CNR Marianas (Guam) JB Pearl Harbor-Hickam (Hawaii, USA) PMRF Barking Sands (Hawaii, USA) NCTAMS PAC (Hawaii, USA) NAVSTA GITMO Bay (Cuba) USN Expeditionary Base (Djibouti) NSA Naples (Italy) NAS Sigonella (Sicily, Italy) NAVSTA Rota (Spain) NAS Bahrain (Kingdom of Bahrain) NAS Souda Bay (Crete, Greece) Navy District Washington DC (USA) Kwajalein Atoll (Marshall Islands) USAG, Hawaii (USA) USAG Kaiserslutem/Landstuhl Hospital (Germany) USAG Graferwoehr/Vilseck (Germany) USAG Yongsan (South Korea) Camps Red Cloud/ Casey (South Korea) USAG Daegu (South Korea) USAG Stuttgart/Patch Barracks (Germany) USAG Humphreys, (South Korea) USAG Tori Station (Japan) USAG Benelux (Netherlands) Camp Zama (Japan) Fort Buchanan (Puerto Rico)

6.3 Contractors performing full time tasking in Germany or Italy, and are not legal German or Italian citizens, must have the position approved in the DOCPERS database. The contractor shall be required to coordinate with Government CORs and provide necessary personal documents for DOCPERS processing.

7. SECURITY REQUIREMENT

7.1 The work performed by the Contractor will include access to unclassified up to Top

Secret data, information, meetings, and spaces. All classified work will be performed at the government sites. Contractor may be required to access SIPRNET at the government site only. The contractor shall be NATO briefed and complete the derivative classification training prior to being granted access to SIPRnet; training is provided by the facility security officer.

7.2 The contractor shall (1) be responsible for all security aspects of the work performed under this contract, (2) ensure compliance with the National Industry Security Program Operating Manual (DODINST 5220.22M), and (3) ensure compliance with any written instructions from the SSC Pacific Security Officer. The contractor shall be responsible for compliance with the Department of Defense Industrial Security Manual and in accordance with the Contract Security Classification Specification, (DD 254), Attachment 1.

7.3 If foreign travel is required, all outgoing Country/Theater clearance message requests shall be submitted to Commanding Officer, Attn: Foreign Travel Team, Space and Naval Warfare Systems Center Pacific, 53560 Hull Street, Building 27, 2nd Floor -Room 206, San Diego, CA 92152 for action. A Request for Foreign Travel form shall be submitted for each traveler, in advance of the travel, to initiate the release of a clearance message at least 40 days in advance of departure. Each Traveler must also submit a Personal Protection Plan and have a Level 1 Antiterrorism/Force Protection briefing within one year of departure and a country specific briefing within 90 days of departure. Anti- Terrorism/Force Protection (AT/FP) briefings are required for all personnel (Military, DOD Civilian, and contractor) per OPNAVINST F3300.53C. Contractor employees must receive the AT/FP briefing annually. The briefing is available at https://atlevel1.dtic.mil/at/, if experiencing problems accessing this website contact ssc_fortrav@navy.mil. Forward a copy of the training certificate to the previous email address or fax to (619) 553-6863. SERE 100.1 Level A Code of Conduct training is also required prior to OConus travel for all personnel. SERE 100.1 Level A training can be accessed at https://wwwa.nko.navy.mil. Other specialized training for specific locations may also be required contact the SSC Pacific foreign travel team.

7.4 As required by NISPOM, Chapter 1, Section 3, contractors are required to report certain events that have an impact on the status of the facility clearance (FCL), the status of an employee's personnel clearance (PCL), the proper safeguarding of classified information, or an indication that classified information has been lost or compromised. Contractors working under SSC Pacific contracts will ensure information pertaining to assigned contractor personnel are reported to the Contracting Officer Representative (COR)/Technical Point of Contact (TPOC), Contracting Specialist, and the Security's COR along with notifying the appropriate agencies such as Cognizant Security Agency (CSA), Cognizant Security Office (CSO), or Department Of Defense Central Adjudication Facility (DODCAF) when related to the denial, suspension, or revocation of a security clearance of any assigned personnel, any adverse information on an assigned employee's continued suitability for continued access to classified access; any instance of loss or compromise, or suspected loss or compromise, of classified information; actual, probable or possible espionage, sabotage, or subversive information; or any other circumstances of a security nature that would affect the contractor's operation while working under SSC Pacific contracts.

7.5 Operations Security - OPSEC is a five step analytical process (identify critical information; analyze the threat; analyze vulnerabilities; assess risk; develop countermeasures) that is used as a means to identify, control, and protect unclassified and unclassified sensitive information associated with U.S. national security related programs and activities. All personnel working under this task will at some time handle, produce or process Critical Information or CPI, and therefore all personnel must practice OPSEC.

All work is to be performed in accordance with DoD and OPSEC requirements and in accordance with the OPSEC attachment to the DD254.

8. GOVERNMENT FURNISHED DOCUMENT

Technical documents identified in the PWS of each task order will be made available to the contractor by SSC Pacific. All documents furnished during the life of the contract remain the property of the government, and if removed from SSC Pacific shall be returned upon completion of the tasking unless otherwise specified in the individual task order.

9. GOVERNMENT FURNISHED MATERIALS/EQUIPMENT (GFM/GFE)

9.1 From time to time, the Contractor may be required to utilize GFM/GFE. Such GFM/GFE shall be specified at the task order level. The contractor shall maintain accountability of Government material and maintain receipts, inventory, adjustments, and shipments of government property. As specified per the delivery/task order, the contractor shall periodically perform, record, and disclose physical inventory results as required per delivery/task order. A physical inventory shall be performed upon contract completion or termination. The contractor shall investigate and promptly furnish a written narrative of all incidents of loss, damage, destruction, or theft to the Government Property Administrator as soon as the facts become known or when requested by the Government.

The contractor shall clearly identify assets to be provided to subcontractors and shall ensure appropriate flow down of contract terms and conditions.

9.2 The contractor is authorized to use Government vehicles only for the performance specified per delivery/task orders. The contactor must be properly insured for vehicles (government or contractor owned/rented) operated in connection with those delivery/task orders. The contractor shall provide a certificate of insurance coverage to the contracting officer verifying it has the proper insurance to operate the vehicles.

9.3 Contractor owned/rented vehicles shall be placarded with the contractor's name and logo or other signs. These signs should identify the name of the company and telephone number at a minimum.

9.4 The contractor is authorized to drive Government vehicles (Nissan Caravans or similar vehicles per each site visit) for the performance of those delivery/task orders to transport equipment on site as required. The contractor shall provide a certificate of auto insurance coverage to the Contracting Officer to show the proper insurance to operate said vehicles.

Contractor personnel shall obtain their international driver's licenses prior to travel.

Contractor shall verify the driving requirements for each installation site and comply with the requirements. Contractor shall coordinate with installation site to obtain international driver's license prior to travel.”

9.5 The contractor shall provide rigging, forklift, crane service, and other services required to accomplish equipment installation/removal/relocation and personnel transport. The contractor shall provide operators with proper licenses to operate aforementioned services.

9.6 Contractors are authorized to drive government vehicles, overhead cranes, electric carts and forklifts. With regard to crane and forklift services, the contractor shall comply with Naval Facilities Command (NAVFAC) P-307 and any other NAVFAC requirements in effect at Government locations.

10. GOVERNMENT FURNISHED FACILITIES ACCESS

10.1 The contractor will be responsible for establishing and maintaining the contractor support facility. Tasking under this contract may require specialized facilities to adequately perform them. When such facilities already exist, and it is in the government’s interest not to require what may be a costly duplication of resources, the government may provide the contractor access to these facilities for use in this tasking.

When Government furnished facilities are to be provided, the facilities will be identified in the individual task order.

10.2 Contractor employees anticipated to be working on-site at SSC PAC lab environment will be provided a common desk, telephone and computer for use as required.

Individuals assigned outside of a lab environment will be provided a desk and a personal computer for work use. A common telephone will be located in the space for use as required. If additional contractor personnel are required to work onsite (full time) at SSC Pacific, each individual will be provided with the necessary equipment required in support of their individual tasking.

11. PLACE OF PERFORMANCE

11.1Tasking required by this PWS shall be performed primarily [SSC PAC, Navy, Army, US

Coast Guard, and Contractor’s] facilities and various outlying sites. Some work will also be performed at various C4ISR and DOD/military installations and facilities as specified in the delivery/task order PWS.

11.2 Approximately 50% of the scheduled work will be performed locally at Government provided spaces at SSC PAC and various C4ISR and DOD/military installations and facilities as specified in the individual delivery/task order PWS. The remaining 50% shall be performed at the contractor facilities for tasks such as technical and logistics documentation updates and development, drafting tasks for engineering drawings and general administrative tasks.

11.3 The Government will provide access to Government workspaces, but any special accommodation requests (such as ergonomic chairs) shall be the responsibility of the contractor to provide.

12. DATA DELIVERABLES

12.1 Deliverables under this contract will have been reviewed IAW “DON Policy on Digital

Product/Technical Data, ASN RD&A MEMO of 23 OCT 04 and shall be provided in accordance with the Contract Data Requirements List, CDRL DD Form 1423, as specified in the individual delivery/task orders.

END OF PWS