PC8174_BCG_2016_SOW_(16Jul15).doc

07/16/2015

STATEMENT OF WORK

START:

24 Sep 2015

COMPLETE:

23 Sep 2016

SHORT TITLE:

Buffalo Computer Graphics Simulator Support and Maintenance contract, test application support, and non-recurring engineering services required in support of current C3CEN electronic navigation system, command & control system, and radar system engineering projects.

1.

PLACE(S) OF PERFORMANCE:

a. On-site at C3CEN in Portsmouth, VA.

b. Northrop Grumman Sperry Marine in Charlottesville, VA

c. Contractor’s facility located at 3741 Lake Shore Road Blasdell, NY 14219

2.

REFERENCES:

a. Encrypted Automatic Identification System (EAIS) Interface Design Description (IDD) v2.0 dtd October 27, 2014

b. Federal Travel Regulation (FTR) or equivalent Coast Guard travel regulations.

3.

SPECIFICATIONS: N/A.

3.1 DHS Enterprise Architecture Compliance

All solutions and services shall meet DHS and USCG Enterprise Architecture policies, standards, and procedures. Specifically, the contractor shall comply with the following Homeland Security Enterprise Architecture (HLS EA) and Coast Guard Enterprise Architecture (CGEA) requirements:

(a) All developed solutions and requirements shall be compliant with the HLS EA and CGEA.

(b) All IT hardware or software shall be compliant with the HLS and USCG EA Technical Reference Model (TRM) Standards and Products Profiles.

(c) Description information all data assets, information exchanges and data standards, whether adopted or developed, shall be submitted to the DHS Enterprise Data Management Office (EDMO) for review and insertion into the DHS Data Reference Model and Enterprise Architecture Information Repository.

(d) Development of data assets, information exchanges and data standards will comply with the DHS Data Management Policy MD 103-01 and all data-related artifacts will be developed and validated according to DHS data management architectural guidelines.

(e) Applicability of Internet Protocol Version 6 (IPv6) to DHS-related components (networks, infrastructure, and applications) specific to individual acquisitions shall be in accordance with the DHS Enterprise Architecture (per OMB Memorandum M-05-22, August 2, 2005) regardless of whether the acquisition is for modification, upgrade, or replacement. All EA-related component acquisitions shall be IPv6 compliant as defined in the U.S. Government Version 6 (USGv6) Profile National Institute of Standards and Technology (NIST) Special Publication 500-267) and the corresponding declarations of conformance defined in the USGv6 Test Program.

4.

SECURITY REQUIREMENTS:

Contractor employee access to classified, and sensitive but unclassified (for-official-use-only) information is required. Due to the time-sensitive nature of this contract, key personnel must hold US citizenship and are required to possess, at a minimum, a valid in-scope national security clearance at the SECRET level.

The contractor will perform classified-related work at the following location(s):

US Coast Guard Command, Control and Communications Engineering Center (C3CEN), 4000 Coast Guard Blvd, Portsmouth, VA 23703

There is no requirement for the contractor to process or store classified information at company owned facilities.

Classified level access is required to develop, repair, and maintain maritime simulation aspects of the classified Seawatch Program located in classified restricted areas at U.S. Coast Guard C3CEN. Access to classified information cannot be precluded by escorting personnel due to the nature of this work.

DHS MD 11055 states that waivers to the U.S. citizen requirement may only granted by the Head of the Component or designee with the concurrence of both the DHS CSO and CIO or their designees.

The contractor’s facility security officer (FSO) shall provide a visit authorization letter (VAL) to the place of performance at least five business days in advance of commencing work. All requests shall contain the information required by the National Industrial Security Program Operating Manual (NISPOM), DOD 5220.22-M, and shall not exceed the completion date of the contract or a 12 month period, whichever is shorter. Additionally, the VAL shall note the applicable government COR responsible for coordinating the visit so that the host location can verify “Need-To-Know,” as necessary.

All contractor personnel requiring routine (1) unescorted logon access to a DHS/CG Computer Information System, (2) unescorted access to CG controlled classified material, (3) unescorted access to federal facilities, or (4) requiring Public Key Infrastructure (PKI) authentication to perform their required duties under this contract/task order shall be issued a Common Access Card (CAC). A completed background investigation (BI) with favorable adjudication must be completed in order for a CAC to be issued. For persons without a completed BI, a BI must have been initiated.

Prospective offerors shall provide proof of holding a current Facility Security Clearance (FCL) issued by the Defense Security Service (DSS). This should be provided on company letterhead and must include full business name and address, Data Universal Numbering System (DUNS) code, Commercial and Government Entity (CAGE) code, date FCL granted, and cognizant DSS security office address with phone number.

Contractor personnel shall read, complete and sign the Department of Homeland Security Non-Disclosure Agreement – DHS Form 11000-6 (series). This form will be maintained on file by the Contracting Officer or servicing CG Command Security Officer.

Contractor or subcontractor employees who are declined a CAC via Trusted Associate Sponsorship System (TASS) are ineligible to perform work that requires a CAC under this contract/task order.

When an employee with a CAC is no longer performing work under this contract/task order, the employee must surrender the CAC to the COR or the company project manager on the same day the employee stops working. Additionally, the COR will immediately advise the servicing Command Security Officer of the sponsoring unit. In all cases, the CAC shall be delivered to the COR no more than five business days following the departure of the employee.

Contractor’s employees shall comply with all applicable government regulations, policies and procedures, e.g., security, safety, sanitation, and environmental protection when visiting or working at government facilities. The contractor shall ensure contractor employees present a professional appearance at all times and that their conduct shall not bring discredit on the United States, the Department of Homeland Security or the U.S. Coast Guard. The contractor employee shall not release any government personnel contact information or information concerning official unit business or operations to unauthorized parties.

The government may, at its sole discretion, direct the contractor to remove any contractor employee from Coast Guard and Department of Homeland Security facilities for misconduct or security reasons. Removal does not relieve the contractor of the responsibility to continue providing the services required in this contract/task order. The government will provide the contractor with an immediate written explanation of the request to remove the employee through the Coast Guard KO.

All contractor developed processes and procedures, and other forms of intellectual property developed under this contract/task order shall be considered government property.

All documents, records, reports and correspondence generated under this contract/task order by the contractor employee are the property of the U.S. government. Any disposal or destruction of such material must be pre-approved by the COR.

The contractor employee shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, the contractor employee shall secure work areas, equipment and materials to prevent loss.

The contractor employee shall be responsible for all keys issued by the government and shall ensure that keys are not lost, misplaced, or used by unauthorized persons. The contractor employee shall not duplicate keys issued by the government. Opening of locked areas by the contractor employee to permit access by persons other than those specifically authorized for the performance of official work is strictly prohibited. The contractor employee shall ensure that combinations to locks are protected from unauthorized disclosure.

The government is the only source for media release information. The contractor employee shall not provide any government-related information to the media and shall refer all queries to the COR or KO.

Contractor access to sensitive but unclassified information (SBU) is required under this contract. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, “Safeguarding SBU/FOUO information.” SBU includes information categorized by DHS or other government agencies as: For Official Use Only (FOUO); Official Use Only (OUO); Sensitive Homeland Security Information (SHSI); Limited Official Use (LOU); Law Enforcement Sensitive (LES); Safeguarding Information (SGI); Unclassified Controlled Nuclear Information (UCNI); and any other identifier used by other government agencies to categorize information as sensitive but unclassified. The Contractor shall sign a non-disclosure agreement (DHS Form 11000-6). The Contractor shall continue to ensure employees safeguard this information when the new Controlled Unclassified Information (CUI) framework replaces the Sensitive But Unclassified (SBU) categorization.

Contractor employees granted access to USCG IT systems shall adhere to CG information system rules and regulations to safeguard government information.

Contractor employees working on-site at government facilities shall wear a government issued identification badge. All contractor employees shall identify themselves as contractors when their status is not readily apparent and display the government issued badge in plain view, on front and above the waist at all times. All contractor employees working on-site shall be required to complete a security arrival brief upon check-in.

Persons determined by the KO and COR to be a substantial risk to U.S. national security interests will not be employed under this contract. Contractor employees must maintain their security clearance eligibility for the duration of this contract/task order.

All hardware, software, and services provided must be compliant in accordance with 140-01 Information Technology Systems Security and the DHS Sensitive Systems Handbooks 4300A for SBU Systems and 4300B for Secret Classified systems. All Top Secret / SCI access and procedures shall be in accordance with DHS Sensitive Compartmented Information (SCI) Systems Policy Directive 4300C and DHS SCI Information Assurance Handbook 4300C.

All systems shall be certified and accredited in compliance with the requirements of national level policies, DHS policies, procedures, and practices; and following the direction provided in the Designated Accrediting Authority (DAA) approved certification and accreditation (C&A) process. C&A is a comprehensive process to ensure implementation of security measures that effectively counter relevant threats and vulnerabilities. C&A consists of several iterative, interdependent phases and steps whose scope and specific activities may vary with the each IS being certified and accredited.

A risk assessment shall be performed for each IS to identify specific areas that require safeguards against deliberate or inadvertent unauthorized disclosure, modifications, or destruction of information; denial of service; and unauthorized use of the IS. In addition, a risk assessment shall be performed to evaluate changes to the department’s intelligence enterprise to ensure changes to the enterprise have not created additional threats and vulnerabilities. Countermeasures shall be applied in those areas to eliminate or adequately reduce the identified risk. The risk assessment shall be based on accepted methodologies’, input for the organization’s counterintelligence component, the organization’s mission requirements, the classification and sensitivity of the information, and a balanced, cost-effective application of security disciplines and technologies.

- FIPS 140-2 and FIPS 197 Advanced Encryption Standard (AES) 256 encryption compliance: All hardware and software interfaces shall meet FIPS 140-2 and FIPS 197 Advanced Encryption Standard (AES) 256 encryption compliance.

- Federal Desktop Core Configuration (FDCC) Clause: All hardware and software shall be Federal Desktop Core Configuration (FDCC) compatible.

- Security Certification/Accreditation: USCG shall provide personnel with the appropriate clearance levels to support the security certification/accreditation processes under this Agreement in accordance with DHS MD 4300A, DHS Sensitive Systems Policy and Handbook. During all SDLC phases of USCG systems, USCG personnel shall develop documentation and provide any required information for all levels of classification in support of the certification / accreditation process. In addition, all security certification / accreditation will be performed using the DHS certification/accreditation process, methodology and tools.

DHS Sensitive Systems Policy Directive 4300 A, Section 4.1.4 requires the "Separation of duties to prevent a single individual from being able to disrupt or corrupt a critical security process." The Policy requires the following: "Components shall divide and separate duties and responsibilities of critical IT system functions among different individuals to minimize the possibility that any one individual would have the necessary authority or system access to be able to engage in fraudulent or criminal activity." Security testing is but one critical systems function that needs to be performed by a provider (either government or contractor) other than the system designer / developer / operator. This requirement is based, in part, on NIST 800-53 Rev 3, Security Control CA-2 Security Assessments - enhancement 1 which requires "The organization employs an independent assessor or assessment team to conduct an assessment of the security controls in the information system." Consequently, the vendor that provides C&A services may not perform the security controls testing.

4.1

CONTRACTOR EMPLOYEE ACCESS

(a) Sensitive Information, as used in this Chapter, means any information, the loss, misuse, disclosure, or unauthorized access to or modification of which could adversely affect the national or homeland security interest, or the conduct of Federal programs, or the privacy to which individuals are entitled under section 552a of title 5, United States Code (the Privacy Act), but which has not been specifically authorized under criteria established by an Executive Order or an Act of Congress to be kept secret in the interest of national defense, homeland security or foreign policy. This definition includes the following categories of information:

(1) Protected Critical Infrastructure Information (PCII) as set out in the Critical Infrastructure Information Act of 2002 (Title II, Subtitle B, of the Homeland Security Act, Public Law 107-296, 196 Stat. 2135), as amended, the implementing regulations thereto (Title 6, Code of Federal Regulations, Part 29) as amended, the applicable PCII Procedures Manual, as amended, and any supplementary guidance officially communicated by an authorized official of the Department of Homeland Security (including the PCII Program Manager or his/her designee);

(2) Sensitive Security Information (SSI), as defined in Title 49, Code of Federal

Regulations, Part 1520, as amended, “Policies and Procedures of Safeguarding and Control of SSI,” as amended, and any supplementary guidance officially communicated by an authorized official of the Department of Homeland Security (including the Assistant Secretary for the Transportation Security Administration or his/her designee);

(3) Information designated as “For Official Use Only,” which is unclassified information of a sensitive nature and the unauthorized disclosure of which could adversely impact a person’s privacy or welfare, the conduct of Federal programs, or other programs or operations essential to the national or homeland security interest; and

(4) Any information that is designated “sensitive” or subject to other controls, safeguards or protections in accordance with subsequently adopted homeland security information handling procedures.

(b) “Information Technology Resources” include, but are not limited to, computer equipment, networking equipment, telecommunications equipment, cabling, network drives, computer drives, network software, computer software, software programs, intranet sites, and internet sites.

(c) Contractor employees working on this contract must complete such forms as may be necessary for security or other reasons, including the conduct of background investigations to determine suitability. Completed forms shall be submitted as directed by the Contracting Officer. Upon the Contracting Officer's request, the Contractor's employees shall be fingerprinted, or subject to other investigations as required. All contractor employees requiring recurring access to Government facilities or access to sensitive information or IT resources are required to have a favorably adjudicated background investigation prior to commencing work on this contract unless this requirement is waived under Departmental procedures.

(d) The Contracting Officer may require the contractor to prohibit individuals from working on the contract if the government deems their initial or continued employment contrary to the public interest for any reason, including, but not limited to, carelessness, and insubordination, incompetence, or security concerns.

(e) Work under this contract may involve access to sensitive information. Therefore, the Contractor shall not disclose, orally or in writing, any sensitive information to any person unless authorized in writing by the Contracting Officer. For those contractor employees authorized access to sensitive information, the contractor shall ensure that these persons receive training concerning the protection and disclosure of sensitive information both during and after contract performance.

(f) The Contractor shall include the substance of this clause in all subcontracts at any tier where the subcontractor may have access to Government facilities, sensitive information, or resources.

(g) Before receiving access to IT resources under this contract the individual must receive a security briefing, which the Contracting Officer’s Technical Representative (COTR) will arrange, and complete any nondisclosure agreement furnished by DHS.

(h) The contractor shall have access only to those areas of DHS information technology resources explicitly stated in this contract or approved by the COTR in writing as necessary for performance of the work under this contract. Any attempts by contractor personnel to gain access to any information technology resources not expressly authorized by the statement of work, other terms and conditions in this contract, or as approved in writing by the COTR, is strictly prohibited. In the event of violation of this provision, DHS will take appropriate actions with regard to the contract and the individual(s) involved.

(i) Contractor access to DHS networks from a remote location is a temporary privilege for mutual convenience while the contractor performs business for the DHS Component. It is not a right, a guarantee of access, a condition of the contract, or Government Furnished Equipment (GFE).

(j) Contractor access will be terminated for unauthorized use. The contractor agrees to hold and save DHS harmless from any unauthorized use and agrees not to request additional time or money under the contract for any delays resulting from unauthorized use or access.

(k) Non-U.S. citizens shall not be authorized to access or assist in the development, operation, management or maintenance of Department IT systems under the contract, unless a waiver has been granted by the Head of the Component or designee, with the concurrence of both the Department’s Chief Security Officer (CSO) and the Chief Information Officer (CIO) or their designees. Within DHS Headquarters, the waiver may be granted only with the approval of both the CSO and the CIO or their designees. In order for a waiver to be granted:

(1) The individual must be a legal permanent resident of the U.S. or a citizen of Ireland, Israel, the Republic of the Philippines, or any nation on the Allied Nations List maintained by the Department of State;

(2) There must be a compelling reason for using this individual as opposed to a U.S. citizen; and

(3) The waiver must be in the best interest of the Government.

(l) Contractors shall identify in their proposals the names and citizenship of all non-U.S. citizens proposed to work under the contract. Any additions or deletions of non-U.S. citizens after contract award shall also be reported to the contracting officer.

4.2

SECURITY REQUIREMENTS FOR UNCLASSIFIED INFORMATION

TECHNOLOGY RESOURCES

(a) The Contractor shall be responsible for Information Technology (IT) security for all systems connected to a DHS network or operated by the Contractor for DHS, regardless of location. This clause applies to all or any part of the contract that includes information technology resources or services for which the Contractor must have physical or electronic access to sensitive information contained in DHS unclassified systems that directly support the agency's mission.

(b) The Contractor shall provide, implement, and maintain an IT Security Plan. This plan shall describe the processes and procedures that will be followed to ensure appropriate security of IT resources that are developed, processed, or used under this contract.

(1) Within 30 days after contract award, the contractor shall submit for approval its IT Security Plan, which shall be consistent with and further detail the approach contained in the offertory’s proposal. The plan, as approved by the Contracting Officer, shall be incorporated into the contract as a compliance document.

(2) The Contractor's IT Security Plan shall comply with Federal laws that include, but are not limited to, the Computer Security Act of 1987 (40 U.S.C. 1441 et seq.); the Government Information Security Reform Act of 2000; and the Federal Information Security Management Act of 2002; and with Federal policies and procedures that include, but are not limited to, OMB Circular A-130.

(3) The security plan shall specifically include instructions regarding handling and protecting sensitive information at the Contractor's site (including any information stored, processed, or transmitted using the Contractor's computer systems), and the secure management, operation, maintenance, programming, and system administration of computer systems, networks, and telecommunications systems.

(c) Examples of tasks that require security provisions include--

(1) Acquisition, transmission or analysis of data owned by DHS with significant replacement cost should the contractor's copy be corrupted; and

(2) Access to DHS networks or computers at a level beyond that granted the general public (e.g., such as bypassing a firewall).

(d) At the expiration of the contract, the contractor shall return all sensitive DHS information and IT resources provided to the contractor during the contract, and certify that all non-public DHS information has been purged from any contractor-owned system. Components shall conduct reviews to ensure that the security requirements in the contract are implemented and enforced.

(e) Within 6 months after contract award, the contractor shall submit written proof of IT Security accreditation to DHS for approval by the DHS Contracting Officer. Accreditation will proceed according to the criteria of the DHS Sensitive System Policy Publication, 4300A (Version 5.5, September 30, 2007) or any replacement publication, which the Contracting Officer will provide upon request. This accreditation will include a final security plan, risk assessment, security test and evaluation, and disaster recovery plan/continuity of operations plan. This accreditation, when accepted by the Contracting Officer, shall be incorporated into the contract as a compliance document. The contractor shall comply with the approved accreditation documentation.

4.3 Access to Unclassified Facilities, Information Technology Resources, and Sensitive Information

The assurance of the security of unclassified facilities, Information Technology (IT) resources, and sensitive information during the acquisition process and contract performance are essential to the DHS mission. DHS Management Directive (MD) 11042.1 Safeguarding Sensitive But Unclassified (For Official Use Only) Information, describes how contractors must handle sensitive but unclassified information. DHS MD 4300.1 Information Technology Systems Security and the DHS Sensitive Systems Handbook prescribe policies and procedures on security for IT resources. Contractors shall comply with these policies and procedures, any replacement publications, or any other current or future DHS policies and procedures covering contractors specifically for all Contracts that require access to DHS facilities, IT resources or sensitive information. Contractors shall not use or redistribute any DHS information processed, stored, or transmitted by the contractor except as specified in the task order.

4.4 Security Review

The Government may elect to conduct periodic reviews to ensure that the security requirements contained in this contract are being implemented and enforced. The Contractor shall afford DHS including the organization of the DHS Office of the Chief Information Officer, the Office of the Inspector General, authorized Contracting Officer’s Technical Representative (COTR), and other government oversight organizations, access to the Contractor’s facilities, installations, operations, documentation, databases, and personnel used in the performance of this contract. The Contractor will contact the DHS Chief Information Security Officer to coordinate and participate in the review and inspection activity of government oversight organizations external to the DHS. Access shall be provided to the extent necessary for the government to carry out a program of inspection, investigation, and audit to safeguard against threats and hazards to the integrity, availability, and confidentiality of DHS data or the function of computer systems operated on behalf of DHS, and to preserve evidence of computer crime.

4.5 Interconnection Security Agreements

Interconnections between DHS and non-DHS IT systems shall be established only through controlled interfaces and via approved service providers. The controlled interfaces shall be accredited at the highest security level of information on the network. Connections with other Federal agencies shall be documented based on interagency agreements; memoranda of understanding, service level agreements or interconnect service agreements.

5.

Contract Management Designation:

5.1 The Contracting Officer (KO) for this procurement is Ms. Debra Smith, C3CEN at (757) 483-8440.

5.2 The Contracting Officer Technical Representative (COTR) for this procurement is LT Adam Reckley, C3CEN, at (757) 686-4076.

5.3 The alternate Contracting Officer Technical Representative (COTR) for this procurement is Mr. Michael Parsons, C3CEN, at (757) 686-4179.

6.

DESCRIPTION OF WORK:

6.1 Scope: This PWS outlines FY 2016 Buffalo Computer Graphics Simulator upgrades, test and radar integration application upgrades, and non-recurring engineering services required in support of current C3CEN electronic navigation system, command & control system, and radar system engineering projects.

6.1.1 Task A: Non-Recurring Engineering (NRE) for maintenance and support of US Coast Guard owned maritime simulators (NTE 200 hrs):

Modify and maintain Coast Guard owned EAIS (STEDS & BFT) simulation capabilities contained within existing BCG simulators. Add support for ITU-R-1371-5, USCG EAIS IDD v1.0, and other enhancements as specified by COR. Resolve all COMRIC, RDSComms, AN/SPS-50, AN/SPS-78, and SSR-PCRP integration/simulation issues.

6.1.2 Task B: Non-Recurring Engineering (NRE) for maintenance and support of US Coast Guard owned NavNet-IMO radar integration software (NTE 100 hrs):

Modify and maintain Coast Guard owned NavNet-IMO software. Develop built-in-test capabilities and diagnostics to help test and troubleshoot integration issues.

6.1.3 Task C: Non-Recurring Engineering (NRE) for EAIS Upgrades (NTE 200hrs NRE): Modify and correct issues with existing Coast Guard EAIS (STEDS & BFT) simulation capabilities contained within existing BCG simulators.

6.1.4 Task D: Non-Recurring Engineering (NRE) for maintenance and support of US Coast Guard owned SeaWatch Interface (NTE 100 hrs):

Modify and maintain Coast Guard owned BCG software created for the SeaWatch team. This includes assisting with integration the new AN/SPS-78 radar system with the SeaWatch system and modifying the BCG simulator to simulate the Furuno antenna output to the SPS-78 PCRP. The simulator shall be able to receive radar data, monitor the radar’s status and to control the radar transmitter.

NOTE: Task D requires a DD Form 254 be issued to the contractor.

6.1.5 Task E: PCS-100INS Radar Simulator (1ea): Upgrade to include the Coast Guard AIS Blue Force Tracking (BFT)/ Sensitive but Unclassified Tactical Information Exchange and Display System (STEDS) simulation package. These units will be configured in a rack mount PC containing sixteen (16) internal serial ports (octal cable x2 is acceptable) and at a minimum must be fully compatible with RP version 8.160. Additionally, this unit will include a rack mount 17 inch monitor, mouse, keyboard drawer.

6.1.6 Task F: PCS-200VMS Radar Simulator (1ea): Upgrade to include the Coast Guard AIS Blue Force Tracking (BFT)/ Sensitive but Unclassified Tactical Information Exchange and Display System (STEDS) simulation package. This unit will be configured in a rack mount PC containing sixteen (16) internal serial ports (octal cable x2 is acceptable) and at a minimum must be fully compatible with newest version RP. Additionally, this unit will include a rack mount 17 inch monitor, mouse, keyboard drawer.

6.1.7 Task G: Integrate support for USCG AN/SPS-78 Radar systems in C3CEN simulators (NTE 100 hrs NRE): Develop AN/SPS-78 interface capability for existing Radar/EAIS simulators currently owned by C3CEN.

6.1.8 Task H: Implement the new IEC 61162-450 protocol for LAN distributed radar data in C3CEN simulators (NTE 100 hrs NRE): Add the IEC 61162-450 LAN distributed radar interface capability to all existing Radar simulators currently at C3CEN.

6.1.9 Task I: BCG On-Site Support: On-Site support will include four (4) trips to C3CEN. Schedule and tasks to be accomplished for each trip will be jointly determined by the USCG and BCG based upon the agreed upon need. This support is offered for work performed at C3CEN Portsmouth, VA or at Sperry Marine at Charlottesville, VA. Each trip is composed of two days on-site plus travel time.

6.1.10 Task J: PCS-199-COP AIS/EAIS Target Simulator Unit (1ea): This unit is capable of generating 40,000 AIS and EAIS targets simultaneously for testing the COP environment.

7.

GOVERNMENT FURNISHED EQUIPMENT (GFE):

7.1. The government shall provide access to BCG Simulators being upgraded at C3CEN in Portsmouth, VA. Contractor shall transport all equipment required in support of the upgrade to C3CEN.

8.

CONTRACTOR FURNISHED MATERIAL (CFM):

8.1. Contractor shall provide all equipment required in support of upgrades. The contractor shall transport all equipment to installation site.

9.

TRAVEL REQUIREMENTS:

9.1 Travel (defined as trips) eight (6) on site support trips to C3CEN in Portsmouth, VA and/or Northup Grumman Sperry Marine in Charlottesville, VA. No additional travel is authorized.

10.

TRANSPORTATION OF EQUIPMENT/MATERIAL:

10.1 The contractor is responsible for transporting all materials required to perform tasks.

11.

DATA DELIVERABLES:

11.1 Electronic copies of all user technical/operation manuals and documentation shall be submitted.

11.2 Copies of all software on removable media shall be supplied. Patches may be delivered via electronic media, when requested by the COTR.

12.

SUB-CONTRACTING REQUIREMENTS: N/A

13.

ACCEPTANCE PLAN

13.1 All work to be performed and all material and data to be submitted under this work order will be inspected and accepted by the designated Government Representative.

12.

OTHER CONDITIONS/REQUIREMENTS:

12.1 Quality Assurance Provisions:

12.1.1 Acceptance: Preliminary reports, outlines and draft documents submitted to the Coast Guard will be reviewed by the Coast Guard for completeness, and may be returned to the contractor for correction. Absence of any comments by the Coast Guard shall not relieve the Contractor of the responsibility for complying with the requirements of this work statement. Final approval and acceptance of documentation required herein shall be by the letter of approval and acceptance of the Contracting Officer. Any letter of acknowledgement of receipt of material shall not be construed as a waiver of review, or as an acknowledgement that the material is in conformance with this work statement. Any approval given during preparation of the documentation, or approval for shipment shall not guarantee the final acceptance of the completed documentation.

12.1.2 Compliance: The contractor shall ensure the delivered tasks and products meet all standards and guidelines provided in this contract and in applicable regulations and directives.

13. LIST OF ATTACHMENTS: N/A

14. SECTION 508 COMPLIANCE.

Accessibility Requirements (Section 508) Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) requires that when Federal agencies develop, procure, maintain, or use electronic and information technology (EIT), they must ensure that it is accessible to people with disabilities. Federal employees and members of the public who have disabilities must have equal access to and use of information and data that is comparable to that enjoyed by non-disabled Federal employees and members of the public.

All EIT deliverables within this work statement shall comply with the applicable technical and functional performance criteria of Section 508 unless exempt.

Section 508 Applicable Exceptions

DHS Office of Accessible Systems and Technology has reviewed this acquisition request and has determined that a National Security Exception for the purposes of Section 508 applies and is thereby authorized. National Security Exception USCG-20110822-001 has been attached and included in the contract file.