Attach_1__SOW_2-28-13.docx

INSTALLATION AND LOGISTICS MANAGEMENT SERVICES - Statement of Work – (SOW)

CONTRACTOR INSTALLATION AND LOGISTICS MANAGEMENT SERVICES (ILMS)

FOR THE U.S. COAST GUARD

COMMAND CONTROL AND COMMUNICATIONS

ENGINEERING CENTER (C3CEN)

STATEMENT OF WORK (SOW)

1.0 GENERAL.

1.1 SCOPE.

The purpose of this acquisition is to acquire non-personal Installation and Logistic Management Services (ILMS) for the U.S. Coast Guard wide Command, Control, Communication Computer and Information Technology (C4IT) system installation and logistics management. Required support services shall include, but not be limited to, the following:

a. C4IT System Documentation Support;

b. C4IT System Installation and De-installation of Equipment;

c. C4IT System Time Compliance Technical Order (TCTO) Support;

d. C4IT System Field Support; and

e. C4IT System Management and Engineering Facilities (SMEF) Support.

The installation and logistics management support services are required by the Command, Control, Communications Engineering Center (C3CEN) and Telecommunication and Information System Command (TISCOM) Centers of Excellence within the Coast Guard’s C4IT structure.

This PWS establishes and defines requirements for installation, logistics and management services (ILMS) required primarily within the continental United States (CONUS), including Alaska, Hawaii, Guam, or Puerto Rico, and/or OCONUS on an as-needed basis. The contractor shall provide all labor, material, supplies, test equipment, tools, and any other items required to satisfactorily perform support services. Services are to be performed aboard U.S. Coast Guard (USCG) vessels/cutters at USCG shore facilities and potentially USCG units located CONUS/OCONUS.

1.2 BACKGROUND.

On February 9, 2009, the Coast Guard established the Command, Control, Communications, Computers, and Information Technology (C4IT) Service Center. The establishment of the C4IT Service Center meets one of the Commandant’s Coast Guard Modernization Initiatives to shift to a product line-based command structure that will standardize processes and procedures across all locations, missions, and asset types. The primary mission of the C4IT Service Center is to unify the Coast Guard’s information technology support structure and business practices into a single mission support model for the entire Coast Guard. C3CEN was incorporated into the C4IT Service Center as a Center of Excellence whose primary mission is to continue to support the wide variety of Coast Guard command, control, and communication systems located at shore facilities, on vessels, and aircraft.

1.3 CONTRACTOR PERSONNEL.

1.3.1 Program Manager. The Government estimates that the Contractor may be able to fulfill all Contractual obligations with one (1) Program Manager who will be responsible for performance of all Contractor work assigned under this SOW. The Program Manager shall be designated as Key by the Government (see PWS 1.4).

Note: Interested parties may propose as many or as few person(s) deemed necessary to fulfill the obligations of the Program Manager labor category (see Attachment 6, Labor Definitions) as set forth in the SOW.

1.3.1.1 The Program Manager shall be a single point of contact for the Contracting Officer and the Contracting Officer’s Representative (COR). It is anticipated that the Program Manager shall be one of the senior level employees provided by Contractor(s) for this work effort. The name of the Program Manager, and the name(s) of any alternate(s) who shall act for contractor(s) in the absence of the Program Manager, shall be provided to the Government as part of the Contractor's proposal. Compliance with 1.4 is required for proposed alternates. During any absence of the Program Manager, only one alternate shall have full authority to act for contractor(s) on all matters relating to work performed under this PWS. The Program Manager and all designated alternates shall be able to read, write, speak and understand English. Additionally, contractor(s) shall not replace the Program Manager without the prior written consent and acknowledgement of the Contracting Officer.

1.3.1.2 The Program Manager shall be available to the COR/Program Office via telephone between the hours of 0800 and 1600 EST, Monday through Friday, and shall respond to a request for discussion or resolution of technical problems within four (4) hours of notification.

1.3.2 Qualified Personnel. The Contractor(s) shall submit qualified personnel to perform all support services specified in Paragraph 5.0 of this PWS. (Refer to labor category descriptions and qualifications in Labor Category Descriptions (Attachment 6). Personnel to be designated as Key by the Government shall comply with the requirements of the SOW, Paragraph 1.4., below. All Contractor employees supporting task orders issued against the base contract(s) shall also be United States citizens or legal residents of the United States.

1.3.3 Conflict of Interest. Contractor(s) shall not employ any person who is an employee of the United States Government if that employment would, or would appear to cause a Conflict of Interest (CoI) as set forth in FAR Part 9.5, Organizational and Consultant conflicts of Interest.

1.4 KEY PERSONNEL.

If requested, the Contractor shall designate key personnel by letter, submitting attached resume(s). Prior to appointing designated key personnel, the Contracting Officer shall review credentials set forth in the designee(s) resume(s). Also, before replacing individual designated as Key (see Paragraph 1.3.1, above) the contractor(s) shall notify the Contracting Officer no less than 15 business days in advance, submit written justification for replacement, and provide the name and qualifications of any proposed substitute(s). All proposed substitutes shall possess qualifications equal to or superior to those of the Key person being replaced. Contractor(s) shall not replace Key Contractor personnel without acknowledgement from the Contracting Officer. The Government may designate additional Contractor personnel as Key in each individual task order.

1.4.1 Substitution of Key Personnel. Individuals identified as key personnel previously accepted to perform under the base ILMS contract(s) are expected to remain dedicated to perform under task order(s) placed awarded to the Company. However, in the event that it becomes necessary for the contractor to replace the individual(s) designated as key personnel, the contractor shall request such substitutions in accordance with this clause. Substitution of key personnel will be considered under the following circumstances only:

(1) All substitutes shall have qualifications at least equal to those of the person being replaced. This shall be verified by submission and approval of the replacement’s resume to the COR for approval by the Contracting Officer;

(2) All appointments of key personnel shall be approved in writing by the Contracting Officer, and no substitutions of such personnel shall be made without the advance written approval of the Contracting Officer;

(3) Except as provided in paragraph (4) of this clause, at least 30 days (60) days ( if a security clearance is required) in advance of the proposed substitution, all proposed substitutions of key personnel shall be submitted in writing to the Contracting Officer, including the information required in paragraph (5) of this provision;

(4) The following identifies the requirements for situations where individuals proposed as key personnel become unavailable because of sudden illness, death or termination of employment. The contractor shall, within five (5) work days after the event, notify the Contracting Officer in writing of such unavailability. If the event happens after task order award, the contracting officer will determine if there is an immediate need for a temporary substitute and a continuing requirement for a permanent substitute for the key personnel position. The Contracting Officer will promptly inform the Contractor of this determination. If the Contracting Officer specifies that a temporary substitute is required, the Contractor shall as soon as is practical identify who will be performing the work as a temporary substitute. The temporary substitute will then start performance on a date mutually acceptable to the Contracting Officer and the Contractor. Work will start no later than 15 work days following the event, if the Contracting Officer specifies that a permanent substitute is required. The contractor shall submit, in writing, for the Contracting Officer’s approval, the information required in (5) and (6) below, for a proposed permanent substitute for the unavailable individual. The approval process will be the same as (7) below;

(5) Request for substitution of key personnel shall provide a detailed explanation of the circumstances necessitating substitution: a) a resume of the proposed substitute, and b) any other information requested by the Contracting Officer to make a determination as to the appropriateness of the proposed substitute’s qualifications. All resumes shall be signed by the proposed substitute and his/her formal (per company accepted organizational chart) direct Supervisor or higher authority;

(6) As a minimum (or as otherwise specified in the solicitation), resumes shall include the following:

(7) The Contracting Officer will promptly notify the contractor in writing of his/her approval or disapproval of all requests for substitution of key personnel.

NOTE: All disapprovals will require re-submission of another proposed substitution within 15 business days by the Contractor.

The following individual is designated as key personnel under this contract:

______________________Program Manager________________________ (end)

1.4.2 Program Manager. Contractor(s) shall provide a Program Manager who shall be responsible for all ILMS support services performed as delineated in each individual task order placed against the base contract(s). The Program Manager’s responsibilities are defined in Paragraph 1.4, above.

The Program Manager shall be a single point of contact for the Contracting Officer and the Contracting Officer’s Representative (COR). It is anticipated that the Program Manager shall be one of the senior level employees provided by contractor(s) for this work effort. The name of Program Manager, and the name(s) of any alternate(s) who shall act for contractor(s) in the absence of the Program Manager, shall be provided to the Government as part of the Contractor's proposal. The Program Manager and all designated alternates shall be able to read, write, speak and understand English. Additionally, contractor(s) shall not replace the Program Manager without prior approval from the Contracting Officer.

The Program Manager shall be available to the Contracting Officer’s Representative (COR) via telephone between the hours of 0800 and 1600 EST, Monday through Friday, and shall respond to a request for discussion or resolution of technical problems within four (4) hours of notification.

1.5 SECURITY REQUIREMENTS.

1.5.1 Access to Classified Information. Contractor access to classified information may be required for specific task orders under the base contact(s). The maximum level of classification is Secret. The details are specified in the attached Department of Defense (DD) Form 254). For classified task orders, the contractor(s) shall submit a list to the COR showing the name and address of each employee prior to the start of the period of performance and within three (3) business days anytime information on that list changes.

1.5.2 Secret Facility Clearance. Prime Contractors proposed under the base contract (s) are required to possess and maintain a Secret Facility Clearance. Further, all contracted work shall meet the requirements of USCG Commandant Instruction 5520.13 (series), Coast Guard Industrial Security Program, and the Department of Defense Instruction 5220.22 (series), National Industrial Security Program. Contractors must read and sign the Classified Information Non-Disclosure Agreement (SF-312 – Attachment 8).

1.5.3 Access to Sensitive/Unclassified Information. 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 in order to perform on-site ILMS system installation and de-installation of equipment, system time compliance technical order (TCTO) support, field support and/or system management and engineering facilities (SMEF) support located in classified restricted areas at or within USCG facilities. Persons determined by the KO and COTR 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.

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. The Prime Contractor shall provide proof of their Facility Clearance with their Proposal (see Section E, Proposal Submission, Section III).

NOTE: When the Offeror(s) is proposing a Teaming/Joint Venture or other Subcontractor Teaming Agreement, all parties of the partnership are required to hold a Secret Facility Clearance at time of award.

1.6 PERIOD OF PERFORMANCE.

The period of performance shall be from the date of award through sixty (60) calendar months.

1.7 PLACE OF PERFORMANCE.

Services are to be performed aboard U.S. Coast Guard (USCG) vessels/cutter, USCG shore facilities and potentially USCG units located OCONUS.

1.8 HOURS OF OPERATION.

Contractor employees shall generally perform all work in accordance with working hours at the sites where work is to be performed, generally 0800-1600. However, there may be occasions when Contractor employees shall be required to work other than normal business hours, including weekends and holidays, to fulfill requirements under this PWS. Alternate work hours must be pre-approved by the Contracting Officer and the need will be addressed in individual task orders.

1.9 TRAVEL.

Refer to Clause C.16, Travel of the RFP.

1.10 KICK-OFF MEETING.

Contractor(s) shall attend a Kick-Off Meeting with the Contracting Officer, Program Manager and the COR to be scheduled within fourteen (14) business days after the date of award. The purpose of the Kick-Off Meeting, which will be chaired by the Contracting Officer (or representative), is to discuss both technical and contracting objectives of this PWS, the Contractor's performance objectives and the project plan. The Kick-Off Meeting will be held at the Command Control and Communications Engineering Center (C3CEN), 4000 Coast Guard Blvd, Portsmouth, VA 23703-2199.

1.11 PROJECT PLAN.

Contractor(s) shall provide a draft Project Plan at Kick-Off Meetings for Government discussion, review and comment. Contractor(s) shall provide a final Project Plan to the COR and Contracting Officer not later than three (3) business days after the Kick-Off Meeting.

1.12 PROGRESS REPORTS.

As set forth in Paragraph 7.0, Deliverables, the Program Manager is responsible for submitting an electronic copy of all Monthly Progress Reports to the COR and/or Contracting Officer not later than the 30th day of each month. Should the 30th day of the month fall on a weekend, the Contractor shall submit reports on the preceding business day of the week. This report shall include a summary of all Contractor work performed, including a breakdown of labor hours by labor category, all direct costs by line item, an assessment of technical progress, schedule status, any travel conducted and any Contractor concerns or recommendations for the previous monthly period.

1.13 PROGRESS MEETINGS.

The Program Manager shall ensure compliance with the mandatory and non-mandatory requirements set forth in Paragraph 7.0, Deliverables. The Program Manager shall submit progress reports on an “as needed basis.” Information contained shall discussing progress made, identify and/or resolve emergent technical problems and issues or other pertinent data with the COR. If the Program Manager is unavailable, the Program Manager’s Alternate shall respond to the COR and/or C3CEN Program Representative within four (4) hours (as required in Paragraph 1.4.2). These meetings shall take place at the Government's facility (i.e., C3CEN, 4000 Coast Guard Blvd, Portsmouth, VA 23703-2199).

1.14 GENERAL REPORT REQUIREMENTS.

The Contractor(s) shall provide all Deliverables (i.e., written reports) as set forth in Paragraph 7.0, Deliverables. Documentation shall be submitted in electronic format with read/write capability using applications that are compatible with the U.S. Coast Guard Standard Workstation.

1.15 PERFORMANCE REQUIREMENTS SUMMARY.

This document includes a Performance Requirements Summary (PRS). The PRS table is in Paragraph 7.0, below. The PRS includes the expected outcomes (objectives) of each individual service(s) required. The PRS is not an exclusive remedy and inclusion of the PRS does not preclude the COR from using any other remedy available to rate satisfactory performance levels under the terms and conditions of the Statement of Work (SOW).

1.16 INTELLECTUAL PROPERTY.

As outlined in the standard Non-Disclosure Agreement (NDA - Attachment 4), no documentation, electronic data or information possessed by the Contractor or entered into or generated as a result of the award of individual task orders issued against the base contracts(s) shall be released to a third party outside of the Government.

1.16.1 Electronic Data. All documentation and electronic data and information collected by contractor(s) and entered into or generated in support of this work statement shall be considered Government property, and shall be returned to the Government at the end of the performance period.

1.16. 2 Rights in Data. Executable software and source code generated specifically for tasks identified in each individual task order shall be delivered with Unlimited Rights in accordance with Federal Acquisition Regulation (FAR)Part 52.227-14, Rights in Data - General (June 1987).

1.17 PROTECTION OF INFORMATION.

Contractor access to proprietary information is required under this Statement of Work (SOW). Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the law and Government policy and regulation.

1.18 SECTION 508 COMPLIANCE.

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, 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. Specifically, the following applicable standards have been identified:

36 CFR 1194.21 – Software Applications and Operating Systems, applies to all EIT software applications and operating systems procured or developed under this work statement including but not limited to GOTS and COTS software. In addition, this standard is to be applied to Web-based applications when needed to fulfill the functional performance criteria. This standard also applies to some Web based applications as described within 36 CFR 1194.22.

36 CFR 1194.22 – Web-based Intranet and Internet Information and Applications, applies to all Web-based deliverables, including documentation and reports procured or developed under this work statement. When any Web application uses a dynamic (non-static) interface, embeds custom user control(s), embeds video or multimedia, uses proprietary or technical approaches such as, but not limited to, Flash or Asynchronous Java script and XML (AJAX) then “1194.21 Software” standards also apply to fulfill functional performance criteria.

36 CFR 1194.23 – Telecommunications Products, applies to all telecommunications products including end-user interfaces such as telephones and non end-user interfaces such as switches, circuits, etc. that are procured, developed or used by the Federal Government.

36 CFR 1194.24 – Video and Multimedia Products, applies to all video and multimedia products that are procured or developed under this work statement. Any video or multimedia presentation shall also comply with the software standards (1194.21) when the presentation is through the use of a Web or Software application interface having user controls available.

36 CFR 1194.25 – Self Contained, Closed Products, applies to all EIT products such as printers, copiers, fax machines, kiosks, etc. that are procured or developed under this work statement.

36 CFR 1194.26 – Desktop and Portable Computers, applies to all desktop and portable computers, including but not limited to laptops and personal data assistants (PDA) that are procured or developed under this work statement.

36 CFR 1194.31 – Functional Performance Criteria applies to all EIT deliverables regardless of delivery method. All EIT deliverable shall use technical standards, regardless of technology, to fulfill the functional performance criteria.

36 CFR 1194.41 – Information Documentation and Support, applies to all documents, reports, as well as help and support services. To ensure that documents and reports fulfill the required “1194.31 Functional Performance Criteria”, they shall comply with the technical standard associated with Web-based Intranet and Internet Information and Applications at a minimum. In addition, any help or support provided in this work statement that offer telephone support, such as, but not limited to, a Service Desk shall have the ability to transmit and receive messages using TTY.

Exceptions for this work statement have been determined by the Department of Homeland Security (DHS) and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the COR and determination will be made in accordance with DHS MD 4010.2. DHS has identified the following exceptions that may apply:

36 CFR 1194.2(b) – (COTS/GOTS products), When procuring a product, each agency shall procure products which comply with the provisions in this part when such products are available in the commercial marketplace or when such products are developed in response to a Government solicitation. Agencies cannot claim a product as a whole is not commercially available because no product in the marketplace meets all the standards. If products are commercially available that meets some but not all of the standards, the agency must procure the product that best meets the standards.

When applying this standard, all procurements of EIT shall have documentation of market research that identify a list of products or services that first meet the agency business needs, and from that list of products or services, an analysis that the selected product met more of the accessibility requirements than the non-selected products as required by FAR 39.2. Any selection of a product or service that meets less accessibility standards due to a significant difficulty or expense shall only be permitted under an undue burden claim and requires approval from the DHS Office on Accessible Systems and Technology (OAST) in accordance with DHS MD 4010.2.

36 CFR 1194.3(b) – Incidental to Contract, all EIT that is exclusively owned and used by contractor(s) to fulfill this work statement does not require compliance with Section 508. This exception does not apply to any EIT deliverable, service or item that will be used by any Federal employee(s) or member(s) of the public. This exception only applies to those contractors assigned to fulfill the obligations of this work statement and for the purposes of this requirement, are not considered members of the public.

36 CFR 1194.3(f) – Back Office, applies to any EIT item that will be located in spaces frequented only by service personnel for maintenance, repair, or occasional monitoring of equipment. This exception does not include remote user interfaces that are accessible outside the enclosed “space”.

1.19 INFORMATION TECHNOLOGY (IT) SECURITY PLAN COMPLIANCE.

1.19.1 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. All services provided under this PWS must be compliant with DHS Information Security Policy, identified in MD4300.1, Information Technology Systems Security Program and 4300A Sensitive Systems Handbook. 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 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 contractor(s) except as specified in the PWS.

1.19.2 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. Contractor(s) 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 Representative (COR), and other government oversight organizations, access to the Contractor’s facilities, installations, operations, documentation, databases, and personnel used in the performance of this contract. Contractor(s) 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.

1.19.3 Security Requirements for Unclassified Information Technology Resources. Contractor(s) shall be responsible for Information Technology (IT) security for all systems connected to a DHS network or operated by contractor(s) 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 contractor(s) must have physical or electronic access to sensitive information contained in DHS unclassified systems that directly support the agency's mission.

Contractor(s) 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.

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

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

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.

Examples of tasks that require security provisions include—

(1) The transmission or analysis of data owned by DHS with significant replacement cost should the contractor's copy be corrupted.

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

At the expiration of the contract, contractor(s) shall return all sensitive DHS information and IT resources provided to contractor(s) provided as GFE during contract performance, 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 document are implemented and enforced.

Within six (6) months after the government notifies the Contractor(s) of award, the awardee(s) 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 award document as a compliance document. Contractor(s) shall comply with the approved accreditation documentation.

1.19.4 Contractor Employee Access Clause. Before receiving access to government Information Technology (IT) resources under the base contract(s), the Contractor and its employees must receive a security briefing, which the Contracting Officer’s Representative (COR) will arrange, and complete any nondisclosure agreement furnished by DHS.

Contractor(s) shall have access only to those areas of DHS Information Technology (IT) resources explicitly stated in the contract award document or approved by the COR 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 COR, is strictly prohibited. In the event of violation of this provision, DHS will take appropriate actions with regard to the contract awardee(s), its employees and/or the individual(s) involved.

Contractor access to DHS networks from a remote location is a temporary privilege for mutual convenience while contractor(s) 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).

Contractor access will be terminated for unauthorized use. Contractor(s) agrees to hold and save DHS harmless from any unauthorized use and agrees not to request additional time or money under the base contract or task order(s) issued there under, as applicable, for any delays resulting from unauthorized use or access.

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.

Contractors shall identify in their proposals the names and citizenship of all non-U.S. citizens proposed to work under task orders placed against the base contract(s) awarded, as applicable. Any additions or deletions of non-U.S. citizens shall be immediately reported to the Contracting Officer.

1.19.5 Inter-connection 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.

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

1.20 ENTERPRISE ARCHITECTURE COMPLIANCE.

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

· All developed solutions and requirements shall be compliant with the USCG and HLS EA;

· All IT hardware or software shall be compliant with the USCG and HLS EA Technical Reference Model (TRM) Standards and Products Profile;

· All data assets, information exchanges and data standards, whether adopted or developed, shall be submitted to the USCG and DHS Enterprise Data Management Office (EDMO) for review and insertion into the USCG and DHS Data Reference Model; and

· In compliance with Office of Management and Budget (OMB) mandates, all network hardware shall be IPv6 compatible without modification, upgrade, or replacement.

2.0 GOVERNMENT ACRONYMS AND DESCRIPTIONS.

3.0 RECEIPT AND INSPECTION OF GOVERNMENT FURNISHED PROPERTY (GFP).

3.1 Testing and Operation of GFE. Per Task Order requirements, the contractor shall set-up and tests all GFE for proper operation prior to installation. When complete operational tests are not practical; detailed physical inspections shall be made by the contractor to determine that all components and parts are present and in apparent good mechanical and electrical condition. The contractor shall, without extra charge, make minor adjustment and repair, such as replacing fuses, during this period.

3.2 Identification of Deficient GFE. Per Task Order requirements, the contractor shall furnish the government a list of equipment in which deficiencies were found, as applicable. This list shall state the nature of each deficiency and the contractor's cost estimate to correct the deficiency. The government reserves the right to furnish the repair parts or other required materials to complete the performance requirements as set forth in the individual task order.

3.3 Testing and Installation of Equipment. If after installation and during testing equipment is found defective, deficiencies shall be reported to the government (see 3.3.2, above). The Government reserves the right to replace or repair the defective material outside the contract or task the contractor to conduct an inspection of the equipment to discover the nature and full extent of the defect and the degree of repair necessary. Upon completion of the inspections, the contractor shall submit a cost estimate of required repairs to the Ordering Officer with a COR request for adjustment in the TO covering the inspection and repairs as required.

3.4 Verification of Operability. Per task order requirements, dependent upon verification by the government of equipment acceptability of the estimate of repair costs, the Ordering Officer shall verify and accept/reject recommendations as proposed by the Contractor. A modification may issue authorizing the contractor to proceed with all, some or none of the repairs. The contractor's ability and willingness to undertake this work promptly upon request shall be considered on a case-by-case basis. The contractor shall have the option of sub-contracting repair services, and the Government reserves the right to furnish the repair parts or other required material on a case-by-case basis.

4.0 CONTRACTOR FURNISHED PROPERTY (CFP) - FACILITIES (CFF).

4.1 Location/Maintenance of the CFP/CFF. The contractor shall maintain a facility within a 50 mile radius (in accordance with the FTR) of C3CEN, Portsmouth, VA in order to accomplish the requirements of the PWS:

4.2 Warehouse. A Contractor owned/leased warehouse will be maintained in accordance with clause 5.3.4, below.

Note: Tasks set forth in individual task orders, in accordance with Section 5.0 of this PWS, shall require frequent access to drawings that are maintained at government facilities. At least one example of each CG unit is located within a 50 mile radius of Portsmouth, V A, which enables prototyping, analysis, and evaluation of platforms at a minimum cost.

4.3 Classification of Data/Equipment. The USCG participates and handles classified data/equipment routinely. In order to provide TO support, the contractor shall require access to secure spaces, equipment and information. Therefore, the contractor shall have an established EKMS account and a facility cleared to store classified documents and equipment at the Secret level in order to handle, generate and communicate classified information or equipment. The contractor shall provide the proper documentation, for all of the facilities identified above. If team arrangements are required in the conduct of this effort, identical data shall be provided for each team member.

5. REQUIREMENTS.

5.1. Support Services. Contractor support services are delineated below (anticipated performance requirements are identified within each subparagraph – 5.2, 5.3, 5.4, 5.5 and 5.6, below):

5.2. System Documentation Support. The Contractor(s) shall prepare, distribute, revise (red line), and maintain C4IT system technical documentation and drawings (Examples of system design and documentation support include, but are not limited to: Preliminary Engineering Change Proposals; Project Management Plans; Work Breakdown Structures (WBS); Engineering Change Proposals; Equipment Support Sheets; Version Description Document(s); Configuration Item Descriptions; CAD drawings; Block Diagrams; Time Compliance Technical Orders, etc):

5.2.1 Support Services. The contractor shall provide engineering and design services in support of C4IT system requirements to complete prototype and production installations aboard Coast Guard Cutters and shore units. This will include, but is not limited to the provision of the following support services:

5.2.1.1 Technical writing services.

5.2.1.2 CAD level technical drawing services, delivered in formats compatible with the Coast Guard Standard Work Station III (typically MS Office).

5.2.1.3 System Engineering and Design Support: The contractor shall provide engineering and design services in support of CG C4IT requirements as follows:

5.2.2 Management Support. The Contractor shall provide management services in support of designated CG C4IT systems, equipment and/or programs:

5.3 System Installation/De-Installation of Equipment.

The Contractor shall provide equipment installers/de-installers to complete prototype and production installations aboard Coast Guard Cutters and shore units. This will include storing, staging, shipping, site preparation (including hot work), of materials and equipment as well as the installation, removal, cleanup and performance of any finish work in the performance of mission tasks defined in Paragraph 1.1, above. Also, performing System Operational Verification Tests (SOVT), correcting discrepancies, coordinating with the Customer to draft, finalize and submit reports, data in/out briefs or other documentation as needed, and submit deliverables to the COR (i.e., periodic progress reports, etc.) as defined in individual orders: