Attachment 1 - TEDDS_PWS_10DEC10.docx

CONTRACTOR MANAGEMENT, TECHINCAL AND ADMINISTRATIVE

SUPPORT SERVICES

FOR THE U.S. COAST GUARD

COMMAND CONTROL AND COMMUNICATIONS

ENGINEERING CENTER (C3CEN)

PERFORMANCE WORK STATEMENT (PWS)

1.0 GENERAL.

1.1 SCOPE.

1.1.1 The purpose of this acquisition is to acquire Technical Engineering Development and Support Services (TEDSS) for the development, integration, deployment and maintenance of new and existing U.S. Coast Guard Command, Control, Communications, Computer, and Information Technology (C4IT) systems. These technical engineering development and support services are required by the U.S. Coast Guard’s Command, Control, and Communications Engineering Center (C3CEN) located in Portsmouth, Virginia which is a Center of Excellence within the Coast Guard’s C4IT Service Center.

1.1.2 The offeror shall provide technical engineering development and support services as set forth in the task and delivery orders to be competitively awarded. These services will be provided for the C3CEN Product Lines and Core Technology Service areas.

1.2 BACKGROUND.

1.2.1 The Command and Control Engineering Center’s (C3CEN) primary mission is to develop, integrate, deploy, maintain, and enhance advanced electronic Command and Control (C2) and navigation systems. C3CEN facilitates continuous improvement engineering that focuses on the rapid deployment of essential functionality followed by planned improvements based on enhanced or refined requirements. In addition to providing maintenance and troubleshooting assistance on its assigned systems that are beyond the scope or capability of operational level support, C3CEN provides a point of contact for technical liaison and information through a System Management and Engineering Facility Help Desk.

1.2.2 The C3 Systems developed and supported at C3CEN have a multi-mission focus on Law Enforcement, Search and Rescue, Maritime Mobility, Marine Safety, Defense Readiness, Marine Environmental Protection, and Ports, Waterways and Coastal Security. The systems may be as complex as a multi-tiered network of computers, radars, navigation receivers, satellite and radio based communication links installed throughout a Coast Guard Cutter. Additionally, the system may be as simple as a single computer connected to a telephone line in an Operations Center. In both instances, the system architecture reflects the C3 process and the system implementation supports the Sense-Assess-Decide-Act cycles occurring now and always within hundreds of Coast Guard Units.

1.2.3 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 Contractor shall provide a Program Manager who shall be responsible for all Contractor work performed under this PWS. The Program Manager is further designated as Key by the Government (see PWS 1.4).

1.3.1.1 The Program Manager shall be a single point of contact for the Contracting Officer and the Contracting Officer’s Technical Representative (COTR). It is anticipated that the Program Manager shall be one of the senior level employees provided by the Contractor for this work effort. The name of the Program Manager, and the name(s) of any alternate(s) who shall act for the Contractor in the absence of the Program Manager, shall be provided to the Government as part of the Contractor's proposal. During any absence of the Program Manager, only one alternate shall have full authority to act for the Contractor 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, the Contractor shall not replace the Program Manager without prior acknowledgement from the Contracting Officer.

1.3.1.2 The Program Manager shall be available to the COTR 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 shall provide qualified personnel to perform all requirements specified in this PWS and are further designated as Key by the Government (see PWS 1.4). All Contractor employees supporting this task order shall also be citizens or legal residents of the United States. See TEDSS labor category descriptions, Attachment 3.

1.3.3 Employee Identification. Contractor employees visiting Government facilities shall wear an identification badge that, at minimum, displays the Contractor name, the employee’s photo, name, clearance-level and badge expiration date. Visiting Contractor employees shall comply with all Government escort rules and requirements. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent and display all identification and visitor badges in plain view above the waist at all times.

1.3.3.1 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 above the waist at all times.

1.3.4 Employee Conduct. Contractor employees shall comply with all applicable Government regulations, policies and procedures (e.g., fire, safety, sanitation, environmental protection, security, “off limits” areas, wearing of parts of military uniforms, and possession of weapons) 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 reflect discredit on the United States, the Department of Homeland Security or the U.S. Coast Guard.

1.3.5 Removing Employees for Misconduct or Security Reasons. The Government may, at its sole discretion, direct the Contractor to remove any Contractor employee from U.S. Coast Guard facilities for misconduct or security reasons. Removal does not relieve the Contractor of the responsibility to continue providing the services required under this PWS. The Contracting Officer will provide the Contractor with a written explanation to support any request to remove an employee.

1.3.6 Conflict of Interest. The Contractor 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.

1.4 KEY PERSONNEL.

Before replacing any individual designated as Key by the Government, the Contractor 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. The Contractor shall not replace Key Contractor personnel without acknowledgement from the Contracting Officer. The Government may designate additional Contractor personnel as Key in each task order awarded. The labor category identified below is considered essential to the work being performed under this Contract and is key personnel:

1.4.1 Program Manager

The Contractor shall provide a Program Manager who shall be responsible for all work (Task Orders) performed under this contract. The Program Manager is further designated as Key by the Government (refer to paragraph 1.4).

The Program Manager shall be a single point of contact for the Contracting Officer and the Contracting Officer’s Technical Representative (COTR). It is anticipated that the Program Manager shall be one of the senior level employees provided by the Contractor for this work effort. The name of Program Manager, and the name(s) of any alternate(s) who shall act for the Contractor 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, the Contractor shall not replace the Program Manager without prior approval from the Contracting Officer.

The Program Manager shall be available to the COTR via telephone between the hours of 0700 and 1700 EST, Monday through Friday, and shall respond to a request for discussion or resolution of technical problems within 1 hour of notification.

1.4.1 Qualified Personnel

The Contractor shall provide only qualified personnel to perform all requirements specified in task orders awarded under this contract. The Contractor shall provide proof of these qualifications upon request by the USUSCG.

The Contractor shall provide qualified personnel to meet the requirements (e.g., installer(s), tester(s), systems specialists/engineers, and technicians) as set forth in Attachment 3, labor category descriptions.

1.5 SECURITY REQUIREMENTS

1.5.1 Contractor access to classified information is required under this Contract. The maximum level of classification is Secret. The details are specified in the attached Department of Defense (DD) Form 254. The Contractor shall submit a list to the COTR showing the name and address of each employee under this PWS prior to the start of the period of performance and within three (3) business days anytime information on that list changes.

1.5.2 Employees proposed under this Contract may be required to possess and maintain a Secret security clearance. If required, it shall be annotated in individual task orders. All contracted work shall meet the requirements of USUSCG 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 Nondisclosure Agreement (SF-312).

1.6 PERIOD OF PERFORMANCE.

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

1.7 PLACE OF PERFORMANCE.

1.7.1 Aboard various US Coast Guard cutters, as stated in individual task orders and may include time underway.

1.7.2 At the U.S. Coast Guard Command Control and Communications Engineering Center(C3CEN), 4000 Coast Guard Blvd, Portsmouth, VA 23703-2199.

1.7.3 At various other locations as defined in individual task orders. Work may be performed at locations worldwide.

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.

1.9 TRAVEL.

Contractor travel shall be required in support of this PWS. All travel required by the Government outside the local commuting area(s) will be reimbursed to the Contractor in accordance with the Federal Travel Regulations. The Contractor shall be responsible for obtaining COTR approval (electronic mail is acceptable) for all reimbursable travel in advance of each travel event.

1.9.1 The Government will require both CONUS and OCONUS travel in support of this Contract. Individual task orders will specify travel locations.

1.10 KICK-OFF MEETING.

The Contractor shall attend a Kick-Off Meeting with the Contracting Officer and the COTR not later than seven (7) business days after the date of award. The purpose of the Kick-Off Meeting, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this PWS and review the Contractor's 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.

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

1.12 PROGRESS REPORTS.

The Program Manager shall provide a monthly progress report to the COTR and Contracting Officer electronically. 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 be available to meet with the COTR upon request to present deliverables, discuss progress, exchange information and resolve emergent technical problems and issues. These meetings shall take place at the Government's facility.

1.14 GENERAL REPORT REQUIREMENTS.

The Contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with Coast Guard Standard Workstation.

1.15 PERFORMANCE REQUIREMENTS SUMMARY.

This Contract includes a Performance Requirements Summary (PRS). In general, the PRS sets forth the expected outcomes (objectives) of individual task orders and service(s) required of the Contractor to achieve the objectives, a performance standard per outcome, and a plan of action in the event the Contractor does not meet the performance standard. The PRS is not an exclusive remedy and inclusion of the PRS does not preclude the Government from using any other remedy available by law or contract terms.

1.16 INTELLECTUAL PROPERTY.

All Contractor developed processes and procedures and other forms of intellectual property first developed under this work statement shall be considered Government property.

1.16.1 All documentation and electronic data and information collected by the Contractor 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 Executable software and source code generated specifically for this task 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 Performance Work Statement (PWS). 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 COTR 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 the contractor 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 Task Orders 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 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. 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.

1.19.3 Security Requirements for Unclassified Information Technology Resources

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

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

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

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

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.

· Within six (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.

1.19.4 Contractor Employee Access Clause:

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

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

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

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

· 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 the contract. Any additions or deletions of non-U.S. citizens after contract award shall also be reported to the contracting officer.

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

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 USUSCG and DHS Enterprise Architecture policies, standards, and procedures. Specifically, the contractor 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 USUSCG 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 USUSCG and DHS Enterprise Data Management Office (EDMO) for review and insertion into the USUSCG and DHS Data Reference Model.

· 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 GOVERNMENT FURNISHED RESOURCES.

The Government will provide the workspace, equipment and supplies, when necessary, to perform the on-site portion of Contractor services required in this Contract, unless specifically stated otherwise in this work statement. The Contractor shall use Government furnished property only for the performance of work under this Contract. Since the Contractor will not be taking control of the GFP, the provisions of FAR part 45 are not applicable. The Government will furnish a reasonable number of remote access privileges in support of the tasks at Section 5.0.

4.0 CONTRACTOR FURNISHED PROPERTY.

The Contractor shall furnish all services, material, and equipment to perform this Contract except for the Government Furnished Resources in PWS 3.0 of this contract.

5.0 REQUIREMENTS.

The Contractor shall provide qualified personnel with the required knowledge and experience, materials, equipment, test instrumentation, data collection and analysis, hardware and software and other services that will support C3CEN’s technical, engineering and administrative support requirements in the execution of the following seven (7) Core Technology and Product Lines.

5.1 Product Lines/Core Technologies:

5.1.1 Communications Area Master Stations (CAMS): Provides reliable and efficient communications to USCG units and the maritime public. Some services are also key elements of the Global Maritime Distress and Safety System (GMDSS). Examples include, but are not limited to:

· Communication Facilities

· Mobile Contingency Communications

5.1.2 Command Centers: Command, Control, and Communications (C3) nodes at the Area, District and Sector levels that provide interoperability with the Integrated Deepwater System (IDS), Rescue 21, and other systems being developed based on new Command, Control, Communication, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) requirements. The integrated CC equipment is designed to enhance the Coast Guard's Area, District and Sector Commander's Maritime Domain Awareness (MDA); improving their ability to provide accurate and timely response to operational multi-mission requirements. Examples include, but are not limited to:

· Search and Rescue (SAR) Systems

· Command Center Display Systems

· Common Operational Picture (COP) Systems

· COP Web Services System (CWSS)

· Port & Coastal Surveillance Systems

· Vessel Traffic Systems (VTS)

· WATCHKEEPER

5.1.3 Differential Global Positioning Systems (DGPS): This system consists of two control centers and over eighty-five (85) remote broadcast sites. The service broadcasts correction signals on marine radio beacon frequencies to improve the accuracy of and integrity to GPS-derived positions. The System provides service for coverage of the continental US, the Great Lakes, Puerto Rico, portions of Alaska and Hawaii, and a greater part of the Mississippi River Basin. Examples include, but are not limited to:

· Differential Global Positioning System (DGPS)

· Nationwide Control Station (NCS)

· GPS Automated Point Positioning System (GAPPS)

5.1.4 Remote Mission Systems: The system consists of shore based VHF communications, nationwide automatic identification of vessels in harbors and harbor approaches, and electronic aids to navigation in support of USCG missions. Examples include, but are not limited to:

· Rescue 21

· National Distress System

· Nationwide Automatic Identification Systems (NAIS)

· Short Range Aids to Navigation (SRAN) Systems

5.1.5 Command and Control Systems: Shipboard Command and Control Systems (SCCS), SeaWatch, and other tactical systems for the US Coast Guard’s C4IT, Surface and Aviation Product Lines. Examples include, but are not limited to:

· Shipboard Command and Control Systems (SCCS)

· SEAWATCH

· Biometrics

· Navy Type Navy Owned (NTNO)

· Mission Support Pallet

5.1.6 Communication Systems: These systems consist of UHF, VHF, HF and MF radio systems (e.g., commercial satellite, military satellite and terrestrial radio communication systems) designed to meet established enterprise-wide requirements. In addition to providing entire systems, procures and installs ancillary radio system components (e.g. antennas, patch panels, modems) both afloat and ashore. Examples include, but are not limited to:

· VHF Systems

· UHF Systems

· HF Systems

· MF Systems

· Ancillary

· SATCOM Systems

5.1.7 Navigation Systems: These include Electronic Navigation systems and Navigation Sensors installed onboard all Coast Guard boats and cutters. Electronic Navigation systems comprise both commercial and government systems that serve as Electronic Charting Systems (ECS), Electronic Chart Display and Information Systems (ECDIS), and Integrated Navigation Systems (INS). ECS variants include Star Technologies’ CAPN, ICAN’s Aldebaran, and C3CEN’s Vega-ECS. ECDIS variants include Transas Marine’s Navisailor 3100, OSL’s ECPINS, Sperry Marine’s Visionmaster ECDIS, and C3CEN’s Vega-ECDIS. INS variants include Kongsberg INS and C3CEN’s COMDAC-INS and Vega-INS. Navigation Sensors comprise a variety of electronic nautical sensors, Differential Global Positioning Systems (DGPS) receivers, radars, depth sounders, Automatic Direction Finders (ADF), Automatic Identification System (AIS) transponders, and fixed or handheld electro-optical devices. Examples of all product types include, but are not limited to:

· Maritime Radar

· DGPS Receivers

· Depth-Sounders

· Direction Finders

· AIS Transponders

· Shipboard Night Vision/Electro Optical

· Night Vision Goggles (Portable Image Intensifiers)

· Hand Held Thermal Imagers

· Weapons Mounted Optical Devices

· Flight Deck Video Systems

· Integrated Navigation Systems (INS)

· Electronic Chart Display & Information System (ECDIS)

· Electronic Charting System (ECS)

· Data Distribution Systems

5.2 Functional Areas: The following nine (9) functional areas are required to support all seven (7) Product Lines/Core Technologies identified in Paragraph 5.1, above:

5.2.1 System Design, Development, Implementation, and Enhancement of Command, Control and Communications Systems: The contractor may be required to support the design, system hardware and software development and integration, testing, implementation, and enhancement of Coast Guard Command, Control and Communications Systems. These systems will be developed, implemented, and enhanced in accordance with the Coast Guard’s System Development Life Cycle Methodology.

5.2.2 System Requirements Analysis and Development: The contractor may be required to support the development of lower level system requirements derived from the mission or business requirements provided by the Coast Guard. This includes a statement that identifies a system, product or process’ characteristic or constraint, which is unambiguous, clear, unique, consistent, stand-alone (not grouped), and verifiable, and is deemed necessary for stakeholder acceptability. A statement is one that defines a user need, a system performance demand, a project or design constraint, or a special characteristic.

5.2.3 Integrated Logistics Support Planning and Execution: The Contractor may be required to support the logistics planning and management support required to maintain the system during its life-cycle. This includes preparing and maintaining life-cycle documentation that will be used by depot level support facilities and other field personnel responsible for maintaining and support the new system.

5.2.4 System Life-cycle Maintenance Execution, Manufacturing and Assembly Services: The contractor may be required to administer system software, hardware, and providing system support over the life of a system including the manufacturing of electrical/electronic components and providing assembly services. This may include managing Diminishing Manufacturing Sources and Material Shortages (DMSMS).

5.2.5 Preparation of All Information Security and Certification and Accreditation Documentation and Support Required to Obtain Certification: The contractor may be required to provide all Certification and Accreditation documentation required to ensure that all system and system enhancement meet the Federal Information Security Management Act of 2002 (FISMA) A United States federal law (44 U.S.C. § 3541, et seq.) enacted in 2002 as Title III of the E-Government Act of 2002 (Pub.L. 107-347, 116 Stat. 2899).

5.2.6 Field Engineering Support: The contractor may be required to ensure that the subject system is performing within all specifications; conduct routine hardware and software maintenance, install system upgrades to ensure effective system operations; provide user training and assist user in problem resolution. The Contractor may also be required to provide onsite assistance as required, including short notice callouts or support via telephone or other means. This requirement may involve travel to various locations to meet deployed Coast Guard cutters, both pier-side and underway.

5.2.7 Training Support: The contractor may be required to determine the level of training that will be required to ensure that the Coast Guard can operate and maintain the system(s) they develop or enhance. Training activities may include developing training aids, providing trainers to train Coast Guard personnel, developing training plans, and producing all required training materials.

5.2.8 Program/Project Management Support: The contractor may be required to manage all program/project activities under this Contract. These activities include preparing project management plans; developing and monitoring project schedule and budgets; ensuring all delivered products and services meet task order requirements, perform configuration management, ensure all project documentation meets the standards specified in the Contract.

5.2.9 System Performance Data Analysis: The contractor may be required to support the collection of data on system performance, analyze the data and provide recommendations or a course of action that will result in improved efficiencies or system performance.

5.3 Meetings.

The Contractor shall attend Integration, Standardization, Technical Working Group meetings and various engineering related meetings, in support of the performance of PWS.

5.4 Reporting.

Unless otherwise stated, the following reports shall be sent to the COTR. Copies shall be forwarded to other designated official.

5.4.1 Burn-rate Reports. The Contractor shall submit a monthly Burn-rate Report for each T&M task order to the COTR via email. The report shall contain the following:

· Monthly burn-rate

· Planned funding versus actual funding

· Bid amount versus funded amount

· Cumulative planned funding versus cumulative actual funding

· Cumulative funding delta

· Graph of data

· Narrative explanation of costs that vary by more than 10% for the Contractor or Subcontractor, and 20% for a major task.

5.4.2 Trip Reports. The Contractor shall submit a Trip Report via email within five (5) business days after returning from any offsite support trip. If offsite support trips occur back-to-back, then the Trip Report shall be submitted within five (5) business days to the COTR after the last offsite support trip. This report shall contain the purpose, destination, dates, and a brief summary of work accomplished and problems encountered.

6.0 REFERENCES.

Appendix B DHS Acquisition Instruction/Guidebook 102-01-001 (series), Appendix B, Systems Engineering Life Cycle (SELC)