Draft_Statement_of_Work.docx

STATEMENT OF WORK

FOR

ADAPTIVE PERSISTENT AWARENESS

SYSTEMS AND PROGRAM SUPPORT

1.0 SCOPE

The Naval Surface Warfare Center, Panama City Division (NSWC PCD) has requirements from multiple program areas to support Persistent Awareness systems development to support Anti-Terrorism/Force Protection and Home Land Security. Persistent Awareness (PA) programs are high priority programs with National Security implications. The scope of this Statement of Work (SOW) encompasses all phases of the Integrated Defense Acquisition Management Framework–Concept Refinement, Development, Deployment, Operations and Life Cycle Support Phases – as well as acquisition and installation of systems and support for various exercises and demonstrations.

1.1 Baseline Adaptive Persistent Awareness System (APAS). Under previous contracts, NSWC PCD has developed a representative APAS system that is being installed in various DOD and non-DOD facilities, airports, railroads and ports in CONUS and OCONUS. The core functions provided are sensor interfacing, wireless Internet Protocol (IP) networking, a user interface (Common Operational Picture), sensor/data processing, and archiving and retrieval. The baseline configuration will be tailored to suit the various locations requiring installation. Contractor support is required to assist in the design, modification, test, installation and maintenance of the equipment.

1.2 Acronyms

2.0 APPLICABLE DOCUMENTS

Applicable military standards, specifications, or other documents will be specified in individual delivery orders for specific tasks issued under this indefinite quantity contract.

3.0 REQUIREMENTS

The Contractor shall, in response to individual orders issued under the contract, provide support within the task areas set forth in this SOW as follows. The Contractor shall coordinate with the Contracting Officers Representative (COR) and Contract Specialist to conduct a kick-off meeting within ten working days after the award of an order to review the terms and conditions, Statement of Work (SOW) and Contract Data Requirements List (CDRL) requirements for the order. This meeting's date, time and location shall be determined within 5 days after award of each order placed against this contract.

3.1 Systems Engineering and Integration (SE&I)

3.1.1 SE&I Analysis Support. NSWC PCD is the Systems Engineering Agent for APAS, but requires additional SE&I support. There will be several Government agencies and Contractors involved in the PA program. For this SOW, the Contractor shall perform various analyses including: trade-offs, problems and potential problems, decisions, risks, tactics, missions and strategies associated with PA program initiatives. The Contractor shall review and analyze joint doctrine and program documentation and reports and utilize salient aspects of this documentation in SE&I analyses.

3.1.2 Systems Integration Technical Support. The Contractor shall support the adaptation of APAS to various locations, facilities and missions, such as ports, railheads, airports, buildings, etc. The Contractor shall provide support with the design, procurement, installation, configuration, and maintenance of APAS equipment. The Contractor shall provide support in the areas of wireless open architecture, service oriented architecture, sensor integration, network architecture design and development, data processing and data fusion, visualization, cognitive processing, use of unmanned vehicles, and integrating sensors on deployment platforms.

This task includes the procurement, integration, installation, and operation of software, mechanical, electrical, sensor, and electro-mechanical systems. The Contractor shall design, install, configure, test, and troubleshoot hardware and instrumentation down to the card level. The Contractor shall provide parts and equipment as required to support systems integration. (Specific materials will be identified at the delivery order level.)

3.1.3 Information Technology (IT) Systems Engineering Support. The Contractor shall provide engineering support for implementing and sustaining IT as it pertains to Command, Control, Communications, Computers and Intelligence, Surveillance and Reconnaissance (C4ISR) and PA systems. The Contractor shall provide deployable broadband communications support including planning meetings with regard to communications; supporting the Government’s network design agent; setting up communications equipment in the lab at NSWC PCD and on-site at deployment locations; and preparing the necessary documentation to support a communications event (e.g., Satellite Access Request, Gateway Access Request, Interim Authority to Connect, etc.) The Contractor shall provide IT support including network administration to establish and maintain IP-based networks, Wide Area Networks (WANs) and Local Area Networks (LANs); system administration to maintain portal services, system interoperability, computer applications; and Cybersecurity support as applied to IP networks.

3.2 Hardware and Software Engineering

3.2.1 Hardware Engineering. The Contractor shall assist in adapting the baseline APAS design for each installation and application. The Contractor shall provide assistance for the design, fabrication, integration, and testing of system C4ISR equipment; infrastructure, including enclosures and mountings; power source and loads; packaging and deployability considerations, as specified in individual delivery orders.

The Contractor shall provide additional related systems hardware engineering support as required, including development of specifications and engineering drawings and documentation as specified by individual delivery orders.

3.2.2 Integration Engineering. The Contractor shall provide software engineering support to adapt the current APAS architecture and facilitate the connection of legacy architectures and new C4ISR equipment. The Contractor shall provide IT systems software development support on-site at NSWC PCD. The Contractor shall provide minor software modifications as needed to support additional hardware interfaces and mission requirements as they arise. The Contractor shall support verification of any software modifications performed.

3.3 Test and Evaluation (T&E) Support (CDRL A006)

3.3.1 T&E Planning Support. The Contractor shall provide T&E planning support to include analysis of test requirements and objectives, preparation of test plans, test procedures, and test data sheets. This support will focus on Limited Operational Evaluations (LOEs) of PA programs. To that end, Contractor pre-deployment support and on-site deployed IT system support shall support T&E planning reviews as required and assist the Government in development of test and exercise scenarios.

3.3.2 T&E Field Engineering Support. The Contractor shall provide field engineering support for experimentation and operational analyses in support of system field evaluations and assessments. To support T&E initiatives, the Contractor shall procure, exercise, demonstrate, and test equipment and spare parts to ensure successful completion of the event. Specific material related to the event shall be specified by individual delivery orders. Developmental testing will be performed at NSWC PCD primarily, but may also be performed at potential deployment locations or other laboratories. Initial test beds are located at NSWC PCD, FL, Plattsmouth, NE, Decatur, AL and in Newark and Jersey City, New Jersey.

The Contractor shall provide the following types of assistance: provide technical assistance to accomplish performance objectives; support transportation and shipping, load out, set-up, configuration, operation, maintenance and tear-down of systems and equipment for test events, demonstrations and real world events; provide on-site software, networking, power and electrical, and communications systems engineering expertise and infrastructure system support; provide data collection and recording, including forensic data capture; assemble and provide for use during field activities test support materials in sufficient quantity to permit successful accomplishment of performance objectives; de-conflict resource availability with schedule; develop corrective courses of action as required; support pre- and post-event briefings and daily hot wash briefings; and support Hazardous Material (HAZMAT) acquisition and handling (including rubbing/isopropyl alcohol, medicines, cleaning fluids, fuel, oil, lubricants, paint, batteries and lumber) in accordance with local, state and federal regulations for T&E events.

3.3.3 Post-Test Support. The Contractor shall assist in Government analysis of test data; evaluation and documentation of T&E results. This support shall include After Action Reports (AARs) and lessons learned reports, as specified per delivery order.

3.4 Logistics

3.4.1 Logistics Planning. The Contractor shall provide logistics planning support to include supportability, reliability, maintenance and operator procedures, training, system integration, test and exercise preparation and support.

3.4.2 Logistics Support Analysis (LSA). The Contractor shall provide LSAs to support the development of logistics support policies as required by specific delivery orders. This may include but is not limited to development of plans for packaging, handling, shipping, and transportation (PHS&T) of systems and equipment; configuration management; maintenance concept development; Support Test Equipment/Test Measurement and Diagnostic Equipment (STE/TMDE) identification; training support; and system manpower analyses. Required documentation such as Integrated Logistics Support Plans (ILSPs), Technical Orders (TOs), Technical Manuals (TMs), interactive work specifications, provisioning documentation, Configuration Management Plans, Configuration Status Accounting support, training materials, and Interactive Electronic Technical Manuals, and Material Fielding Plans, will be identified in specific delivery orders. The Contractor shall develop standard operating procedures and processes associated with system operations and mission areas. (CDRL A001)

3.4.3 Operation, Maintenance, and Repair. The Contractor shall support operation, maintenance and repair of hardware, software and support infrastructure, as required. At a minimum, the Contractor shall maintain testbeds located at NSWC PCD, FL, Plattsmouth, NE, Decatur, AL and in Newark and Jersey City, New Jersey. The Contractor shall provide inventory management and configuration management services.

3.4.4 Training Support. The Contractor shall develop training materials as described in specific delivery orders, and support the conduct of training of APAS operational usage (for example but not limited to basic usage and basic trouble shooting) at NSWC PCD and on-site at deployed locations. Class sizes and content will vary depending on the configuration of APAS installed and the location, but for the purposes of estimating, consider a typical class size to be 8 to 12 persons per installation site, with training consisting of approximately 8 hours of classroom and 24-32 hours of hands-on training.

3.5 Technology Insertion Technical Support

The Contractor shall provide support to system technology insertion initiatives including transfer of existing and emerging technologies from current Commercial Off-the-Shelf (COTS) and Government Off-the-Shelf (GOTS) programs and systems to emerging AP systems. In supporting this task, the Contractor shall provide assessments of advanced programs, emerging technology, and innovation technology applications in support of wireless networking , sensors and sensor processing, and increased computer capabilities; identify, exploit and manipulate current and emerging technologies; implement advanced communication systems to improve flow of voice and data communication; implement advanced information systems to aid the quick collection and dissemination of critical information; provide analysis and assessment of Command and Control (C2) and sensor systems and other emerging technical efforts; deploy to support operations at exercises, demos, or real world events. The Contractor shall assist with development and update of the software technology road map in migration to network-centric service oriented architecture. The Contractor shall provide technical support for development of acquisition documentation associated with technology transfer efforts as specified per individual delivery orders. The Contactor shall support technology insertion of hardware, software and support infrastructure, as required, at existing or new installations. At a minimum, the Contractor shall support technology insertion at testbeds located at NSWC PCD, FL, Plattsmouth, NE, Decatur, AL and in Newark and Jersey City, New Jersey.

3.6 Installations

The Contractor shall provide APAS installation services which will include but are not limited to surveying potential sites as well as developing the design for an installation plan for each location, manufacturing and procuring infrastructure (such as towers and poles) and C4ISR components; assembling APAS components and packaging them for transportation; transporting system components and support equipment to installation sites and back to NSWC PCD and documenting all phases of the installation from design through acceptance by the customer. Infrastructure includes power from public utility companies, Internet Service Providers (ISP), and construction requirements as needed.

The Contractor shall implement material, parts, and component management processes to ensure:

(a) All incoming material will undergo a receipt inspection prior to being used or inducted into inventory

(b) All nonconforming material will be documented with a Material Discrepancy Report which will be resolved with the Government

(c) Periodic physical inventory of materials and parts on-hand and accounting of material usage (segregated by Government Furnished and Contractor purchased)

In addition, on-site installation and testing at selected locations will be required as specified on the individual orders. Approximately 2 to 3 installations will be made under this contract. The Contractor shall also be responsible for ensuring environmental documentation or permissions are provided that meet applicable state, federal and host nation laws and requirements at those locations as specified on the individual orders.

3.7 Programmatic Support

3.7.1 Program Analysis and Documentation Support. The Contractor shall perform programmatic analyses, develop and produce programmatic documentation, and provide administrative and other program support as required. The Contractor shall support Government development of program Plan of Action and Milestone (POA&M) documentation. The Contractor shall support the Government in the development and execution of support plans and programs for risk management, quality assurance, human systems integration, safety, and configuration management. Specific documentation will be described in individual delivery orders.

3.7.2 Meeting Support. The Contractor shall attend weekly meetings, to report on the status of ongoing tasks, along with other meetings related to this effort, such as design reviews, test-readiness reviews, etc. In support of these meetings, the Contractor will develop and update meeting support material, as required by individual delivery order Contract Data Requirements Lists (CDRLs), including agendas, action item reports, and meeting minutes.

3.7.3 Briefing Material Support. The Contractor shall assist in the preparation of briefing materials as necessary in using Government-Furnished Information (GFI). The Contractor shall also support the development of multi-media presentation materials, such as static displays and Microsoft PowerPoint automated presentations for program events and conferences.

3.8 Travel

Travel in the Continental United States (CONUS) and outside the Continental United States (OCONUS) will be required to support the task under this contract. All travel will be in accordance with the Joint Travel Regulations. For the purposes of this IDIQ contract, the Contractor shall propose a NTE Travel Ceiling in accordance with the instructions in Section L.

Specific travel locations and requirements will be identified in each individual order issued under this contract. Travel requirements for each Task/Delivery Order shall be seperately identified in the Contractor’s proposal at the order level including a detailed and fully-loaded price for the number of employees and their travel costs to include airfare, lodging, per diem, rental car, taxi/mileage, and any other associated travel costs.

3.9 Other Conditions

Occasional overtime is anticipated to be required to support these tasks; overtime must be requested through the Contracting Officer’s Representative and approved by the Contracting Officer prior to being conducted.

3.10 Monthly Status Report (MSR) (CDRL A002)

The Contractor shall monitor cost expenditures, activities undertaken, and progress towards completion of work and report this progress monthly for each individual delivery order. MSRs shall be delivered by the 15th of the following month starting the first complete month after award. The MSR shall include the following topics:

- Narrative summary of the work performed and results obtained, including a list of significant events that occurred concerning the accomplishment of the tasks under this order during the reporting period

- Anticipated activities for the following month

- An explanation of deviations from the last month’s projections

- Current or projected problems and issues being worked by the Contractor

- Current or projected problems and issues requiring Government attention

- Material expenditures and an accounting of material usage

- Trip Reports for travel performed including highlights and summary of technical discussion(s), action items and a list of attendees

3.10.1 Monthly Earned Value Management (EVM) Reporting. The Contractor shall provide an annual spend plan (graphical and tabular) for the duration of each delivery order broken down by month with his first monthly status report. There shall be a separate spend plan for each task or as directed by the Government Contracting Officer’s Representative (COR). NSWC PCD is using EVM to track project spending and execution. Tasks in the SOW are linked to EVM work packages. Cost proposals must be broken out by major task specified in section 3.0 of the SOW or as directed by the Government contracting officer’s representative. The Contractor shall report work performed in hours and actual costs in dollars expended each month and the “value of the work completed” in the same monthly period by task. The “value of the work completed” is the amount of work actually accomplished, in dollars, at that point in the schedule of planned work. For example, if all efforts in a task scheduled for a given month were completed, then the “value of the work completed” would equal the estimate in the spend plan. If only half of the work were completed, then the “value of the work completed” would be half the estimate in the spend plan. The Contractor shall submit his EVM report in conjunction with the MSR. Deviations from the spend plan should be explained in the narrative of the MSR.

3.11 Government Space and Access to Government Facilities (CDRL A003)

The Government will not provide any space under this Contract. Access to NSA PC requires Government identification cards, either Common Access Cards (CAC) or other Government approved identification (e.g., RapidGate). Contractor personnel will require access to Building 544. The Contractor shall provide a list of employees who require access, including standard security clearance information for them, to the Building 544 facility manager within 3 days of award. Access to Government building is from 0600 until 1800 Monday through Friday, except Federal holidays. Normal work hours are from 0730 to 1630, Monday through Friday, and possibly on weekends during periods of high productivity and may vary according to which office employee is working. The approval of the Procuring Contracting Officer (PCO) is required for performance of work outside normal working hours. Contract personnel shall always work under Government oversight. In the event that NSWC PCD operations are curtailed as a result of weather emergencies or other unplanned events, Contractor personnel shall be considered non-essential personnel and shall follow Naval Support Activity (NSA) Panama City instructions for non-essential personnel.

When a Government facility is closed and/or early dismissal of Federal employees is directed due to severe weather, security threat, or a facility related problem that prevents personnel from working, onsite Contractor personnel regularly assigned to work at that facility should follow the same reporting and/or departure directions given to Government personnel. The Contractor shall not direct charge to the contract for time off, but shall follow parent company policies regarding taking leave (administrative or other). Non-essential Contractor personnel, who are not required to remain at or report to the facility, shall follow their parent company policy regarding whether they should go/stay home or report to another company facility. Subsequent to an early dismissal and during periods of inclement weather, onsite Contractors should monitor radio and television announcements before departing for work to determine if the facility is closed or operating on a delayed arrival basis.

When Federal employees are excused from work due to a holiday or a special event (that is unrelated to severe weather, a security threat, or a facility related problem), on site Contractors will continue working established work hours or take leave in accordance with parent company policy. Those Contractors who take leave shall not direct charge the non-working hours to the task order. Contractors are responsible for predetermining and disclosing their charging practices for early dismissal, delayed openings, or closings in accordance with the FAR, applicable cost accounting standards, and company policy. Contractors shall follow their disclosed charging practices during the task order period of performance, and shall not follow any verbal directions to the contrary. The PCO will make the determination of cost allowability for time lost due to facility closure in accordance with FAR, applicable Cost Accounting Standards, and the Contractor's established accounting policy.

Contractor personnel may require access to classified and unclassified NSWC PCD Research, Development, Test and Evaluation (RDT&E) and APAS networks, unclassified NMCI networks and other Department of Defense (DoD) or Department of the Navy (DoN) websites. The Contractor shall provide a list of employees who require CAC identity cards to access these networks, within 3 days after award.

3.12 Safety

The requirements of this order may require Contractor personnel to come in contact or be exposed to hazardous conditions. The Contractor shall abide by all applicable federal, state, and local occupational safety and health requirements. The Contractor shall ensure employees have appropriate Personal Protection Equipment (PPE) and that all employees have all required training and certifications related to Occupational Safety and Health requirements. (CDRL A004)

3.13 Quality Control

The Contractor shall provide and maintain a Quality Control (QC) system that meets the requirements of ISO 9001:2008. The Contractor shall submit a Quality Control Plan (QCP) that documents the quality system procedures, planning, and all other documentation and data that comprise the quality system for Government for review and approval. The QCP shall identify the means by which the Contractor will ensure quality system effectiveness and demonstrate comprehensive management and review of the data, such that the results shall be used to indicate trends and progress in quality of services and data products provided. The QCP shall describe what is measured, how often it is tracked, and who reviews and assures that appropriate action is initiated when trends are unfavorable. The Government may perform any necessary inspections, validations, verifications and evaluations necessary to ascertain conformance and compliance to the requirements and adequacy of the implemented procedures. The Government reserves the right to disapprove the quality system or portions thereof when it fails to meet its contractual requirements. The supplier shall require of sub-tier suppliers a quality system that achieves control of quality of the services and data products or supplies provided. (CDRL A005)

4.0 GOVERNMENT FURNISHED INFORMATION AND PROPERTY

All Government furnished information will be specified and provided in the individual orders.

5.0 SECURITY

Performance of this contract will require the Contractor to receive, generate, and store National Security Information classified up to SECRET level at the Contractor Facility.

Provisions of the attached DD254 apply. The Prime Contractor shall:

Technical papers, either classified or unclassified, which the Contractor may wish to present at government-sponsored classified or limited attendance symposia must be submitted through the NSWC PCD Technical POC to initiate the process. Approval must be granted prior to Contractor presentation.

Information on this contract is not releasable to foreign nationals without written approval of the DoD office with controlling authority. The only exceptions to this requirement are a visit of a foreign national duly authorized by the DOD through established channels or if authorized under ITAR.

Access to Navy ships, to Navy or commercial shipyards where such ships or facilities are located is subject to the requirements of Title 32, CFR 765.5.

(1) Forward copies of DD254s provided to subcontractors to the Naval Surface Warfare Center Panama City Division (NSWC PCD), ATTN: Security.

(2) Direct the subcontractor to obtain approval, through the prime Contractor, for the public release of information received or generated by the sub through the prime Contractor.

(3) Submit the subcontractor’s request for public release through the technical point of contact identified on the DD 254.

5.1 Controlled Unclassified Information (CUI)

Controlled unclassified information (CUI) is official information that requires the application of controls and protective measures for a variety of reasons and has not been approved for public release, to include technical information, proprietary data, information requiring protection under the Privacy Act of 1974, and Government-developed privileged information involving the award of contracts. CUI is a categorical designation that refers to unclassified information that does not meet the standards for National Security Classification under Executive Order 13526, but is (a) pertinent to the national interest of the United States or to the important interests of entities outside the Federal Government, and (b) under law or policy requires protection from unauthorized disclosure, special handling safeguards, or prescribed limits on exchange or dissemination.

5.2 Minimum Requirements for Access to Controlled Unclassified Information (CUI)

Prior to access, Contractor personnel requiring access to DON controlled unclassified information (CUI) or "user level access to DON or DoD networks and information systems, system security and network defense systems, or to system resources providing visual access and/or ability to input, delete or otherwise manipulate sensitive information without controls to identify and deny sensitive information" contractors must have clearance eligibility, or submit an Electronic Questionnaire for Investigation Processing (SF 86) to NSWC PCD Security for processing and subsequent adjudication by the DON Central Adjudication Facility.

5.3 Minimum Protection Requirements for Controlled Unclassified Information

Security classification guides (OPNAVINST 5513 series) and unclassified limited documents (e.g., FOUO, Distribution Statement Controlled) are not authorized for public release and, therefore, cannot be posted on a publicly accessible webserver or transmitted over the Internet unless appropriately encrypted.

5.4 For Official use Only (FOUO)

FOUO is a document designation, not a classification. This designation is used by Department of Defense (DoD) and a number of other federal agencies to identify information or material, which although unclassified, disclosure to the public of the information would reasonably be expected to cause a foreseeable harm to an interest protected by one or more provisions of the FOIA. This includes information that qualifies for protection pursuant to the provisions of the Privacy Act of 1974, as amended. FOUO must be marked, controlled and safeguarded in accordance with DoD 5200.01, Vol. 4, DoD Information Security Program: Controlled Unclassified Information (CUI), February 24, 2012

5.5 Security of Unclassified DoD Information on Non-DoD Information Systems (DoD 8582.01) DoD Policy

Adequate security be provided for all unclassified DoD information on non-DoD information systems. Appropriate requirements shall be incorporated into all contracts, grants, and other legal agreements with non-DoD entities.

Information Safeguards are applicable to unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems, to the extent provided by the applicable contract, grant, or other legal agreement with the DoD.

Information Safeguards

Unclassified DoD information that has not been cleared for public release may be disseminated by the Contractor, grantee, or awardee to the extent required to further the contract, grant, or agreement objectives, provided that the information is disseminated within the scope of assigned duties and with a clear expectation that confidentiality will be preserved. Examples include:

a. Non-public information provided to a contractor (e.g., with a request for proposal).

b. Information developed during the course of a contract, grant, or other legal agreement (e.g., draft documents, reports, or briefings and deliverables).

c. Privileged information contained in transactions (e.g., privileged contract information, program schedules, contract-related event tracking).

It is recognized that adequate security will vary depending on the nature and sensitivity of the information on any given non-DoD information system. However, all unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems shall minimally be safeguarded as follows:

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

b. Protect unclassified DoD information by at least one physical or electronic barrier (e.g., locked container or room, logical authentication or logon procedure) when not under direct individual control of an authorized user.

c. At a minimum, overwrite media that have been used to process unclassified DoD information before external release or disposal.

d. Encrypt all information that has been identified as CUI when it is stored on mobile computing devices such as laptops and personal digital assistants, compact disks, or authorized removable storage media such as thumb drives and compact disks, using the best encryption technology available to the contractor or teaming partner.

e. Limit transfer of unclassified DoD information to subcontractors or teaming partners with a need to know and obtain a commitment from them to protect the information they receive to at least the same level of protection as that specified in the contract or other written agreement.

f. Transmit e-mail, text messages, and similar communications containing unclassified DoD information using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and transport layer security (TLS).

g. Encrypt organizational wireless connections and use encrypted wireless connections where available when traveling. If encrypted wireless is not available, encrypt document files (e.g., spreadsheet and word processing files), using at least application-provided password protected level encryption.

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

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

j. Provide protection against computer network intrusions and data exfiltration, minimally including:

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

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

k. Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, proprietary, critical program information (CPI), personally identifiable information, export controlled) as specified in contracts, grants, and other legal agreements.

l. Report loss or unauthorized disclosure of unclassified DoD information in accordance with contract, grant, or other legal agreement requirements and mechanisms.

m. Do not use external IT services (e.g., e-mail, content hosting, database, document processing) unless they provide at least the same level of protection as that specified in the contract or other written agreement.

5.6 Operations Security

Operations Security (OPSEC) is concerned with the protection of critical information: facts about intentions, capabilities, operations, or activities that are needed by adversaries or competitors to bring about failure or unacceptable consequences of mission accomplishment.

Critical information includes information regarding:

- Operations, missions, and exercises, test schedules or locations;

- Location/movement of sensitive information, equipment, or facilities;

- Force structure and readiness (e.g., recall rosters);

- Capabilities, vulnerabilities, limitations, security weaknesses;

- Intrusions/attacks of DoD networks or information systems;

- Network (and system) user IDs and passwords;

- Movements of key personnel or visitors (itineraries, agendas, etc.); and

- Security classification of equipment, systems, operations, etc.

The contractor, subcontractors and their personnel shall employ the following countermeasures to mitigate the susceptibility of critical information to exploitation, when applicable:

- Practice OPSEC and facilitate OPSEC awareness;

- Immediately retrieve documents from printers assessable by the public;

- Shred sensitive and Controlled Unclassified Information (CUI) documents when no longer needed;

- Protect information from personnel without a need-to-know;

- When promulgating information, limit details to that essential for legitimacy;

- During testing and evaluation, practice OPSEC methodologies of staging out of sight, desensitization, or speed of execution, whenever possible.

CONTRACTOR OPERATED VEHICLES Contractor-furnished vehicles shall meet the following criteria:

The company name shall be displayed on each of the Contractor's vehicles in a manner and size that is clearly visible. All vehicles shall display a valid state license plate that complies with State Vehicle Code. Vehicles shall meet all other requirement of the State Vehicle Code, such as safety standards, and shall carry proof of insurance and state registration. The Contractor shall mark all Government Furnished Vehicles “Contractor operated” in one and one-half inch (1 ½”) lettering. The color of the marking may be either black or blue to match other vehicle markings, and in close proximity to the USN number. Contractor personnel shall not utilize cellular telephones or personal devices while operating Contractor- furnished equipment or vehicles or personal owned vehicles on Government property.

6.0 PERFORMANCE BASED REQUIREMENTS

This requirement is performance based. The Contractor's performance will be evaluated by the Government in the areas listed below. The first evaluation will cover the period ending six months after date of Task Order award with successive evaluations being performed prior to the exercise of available options thereafter until the Contractor completes performance under all tasks. Evaluations will be posted to the Contractor Performance Assessment Report System (CPARS).

The Contractor’s performance under the task orders will be evaluated in the following areas:

- Quality of Product/Service

- Schedule

- Cost Control

- Business Relations

- Management of Key Personnel

The following five level assessment rating system will be used to evaluate a Contractor's performance.

The Contractor may obtain more information regarding the CPARS process at the following internet site: http://cpars.navy.mil.

6.1 Performance Objectives, Standards and Acceptable Quality Level (AQL)

The contract service requirements are summarized below into Performance Objectives, Performance Standards and AQLs that relate directly to mission essential items. The performance thresholds describe the minimally acceptable levels of service required for each requirement and are considered critical to mission success. Procedures as set forth in the FAR 52.246-4, Inspection of Services – Firm Fixed Price, shall be utilized to remedy all deficiencies.

PWS

paragraph 3.4

Documents and revisions are delivered IAW agreed upon schedules.

Documentation prduced, reviewed, and presented to meet acceptance. 100% completed by due date.

PWS

paragraph 3.5

PWS

paragraph 3.7.2

7.0 GOVERNMENT AND CONTRACTOR RELATIONSHIP

(a) The services to be delivered under this Contract are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Contract between the Government and the Contractor's personnel. It is, therefore, in the best interest of the Government to afford both parties a full understanding of their respective obligations.

(b) All Contractor, Subcontractor, and consultant personnel shall wear prominently displayed identification badges at all times when performing work on NSWC PCD property or attending meetings in the performance of this Contract. The badge shall contain the individual's name, the company name and logo. When participating in such meetings (e.g., as a speaker, panel member), those individuals in Contractor employ must supplement physical identification (e.g., badges, place markers) with verbal announcements so that it is clear to the assembled group that they are employees of the Contractor, not NSWC PCD employees. In addition, when working on NSWC PCD property, all Contractor, Subcontractor, and consultant personnel shall have signs visible on their desks or at their work sites that clearly state that they are not NSWC PCD employees.

(c) The Contractor is responsible for supervision of all Contractor personnel assigned to this Contract. The Contractor shall exercise ultimate over all aspects of Contractor personnel day-to-day work under this Contract including the assignment of work, means and manner of Contractor employee performance and the amount of Contractor supervision provided. The Contractor shall be ultimately responsible for all aspects of performance under this Contract including the work of its Contractor personnel.

Contractor personnel under this Contract shall not:

(1) Be placed in a position where they are under the supervision, direction, or evaluation of a Government employee.

(2) Be placed in a position of command, supervision, administration or control over Government personnel, or over personnel of other Contractors under other NSWC PCD contracts, or become a part of the Government organization.

(3) Be used in administration or supervision of Government procurement activities.

(4) Have access to proprietary information belonging to another without the express written permission of the owner of that proprietary information.

(d) Employee Relationship:

(1) The services to be performed under this Contract do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

(2) Rules, regulations, directives and requirements that are issued by the U.S. Navy and NSWC PCD under its responsibility for good order, administration, and security are applicable to all personnel who enter the Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services Contract.

(e) Inapplicability of Employee Benefits: This Contract does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

(1) Payments by the Government under this Contract are not subject to the Federal income tax withholdings.

(2) Payments by the Government under this Contract are not subject to the Federal Insurance Contributions Act.

(3) The Contractor is not entitled to unemployment compensation benefits under the Social Security Act, as amended, by virtue of performance of this Contract.

(4) The Contractor is not entitled to workman's compensation benefits by virtue of this Contract.

(5) The entire consideration and benefits to the Contractor for performance of this Contract are contained in the provisions for payment under this Contract.

(f) Notice. It is the Contractor's, as well as, the Government's responsibility to monitor Contract activities and notify the Contracting Officer if the Contractor believes that the intent of this clause has been or may be violated.

(1) The Contractor should notify the Contracting Officer in writing promptly, within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this clause. The notice should include the date, nature, and circumstances of the conduct, the name, function and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct, identify any documents or substance of any oral communication involved in the conduct, and the estimate in time by which the Government must respond to this notice to minimize cost, delay or disruption of performance.

(2) The Contracting Officer will promptly, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

(i) confirm the conduct is in violation and when necessary direct the mode of further performance,

(ii) countermand any communication regarded as a violation

(iii) deny that the conduct constitutes a violation and when necessary direct the mode of further performance; or

(iv) in the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor and the date.

8.0 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA)

The Contractor shall report ALL Contractor labor hours (including Subcontractor labor hours) required for performance of services provided under this contract for NSWC PCD via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil. Reporting inputs will be for the labor executed during the period of performance during each Government Fiscal Year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil.