Attachment E.pdf

Attachment E

SAMPLE TASK ORDER

TECHNICAL ENGINEERING DEVELOPMENT & SUPPORT SERVICES

FOR

U.S. COAST GUARD COMMAND AND CONTROL SYSTEMS

CONTRACTOR MANAGEMENT, TECHNICAL AND ADMINISTRATIVE SUPPORT SERVICES FOR THE

U.S. COAST GUARD, COMMAND AND CONTROL ENGINEERING CENTER (C2CEN), AFLOAT

DIVISION, C2 SYSTEMS BRANCH

TASK ORDER

STATEMENT OF WORK

1.0 GENERAL.

1.1 SCOPE.

The purpose of this task order is to obtain Contractor system engineering, system integration, technical and administrative support services for the U.S. Coast Guard, Command and Control Engineering Center (C2CEN), Afloat Division, C2 Systems Branch . Specifically, this task order requires Contractor support for the development and deployment of the Enhanced Mission C4ISR Capabilities (Seawatch) system (EMC2- SW). Development and deployment support includes, but is not limited to, system design support, system integration support, hardware integration support, software integration support, system testing and evaluation support, and electronics and networking installation work aboard various Coast Guard cutter classes and in C2CEN laboratories. This task order also includes system technical support for CG assets in which EMC2-Seawatch is deployed.

1.2 BACKGROUND.

The current Shipboard Command and Control System (SCCS) baseline, which integrates navigation sensors, surface search radar, tactical communications, and optical surveillance systems to provide integrated navigation and tactical C2 capability to legacy Deepwater assets, is nearing its expected end-of-life. Furthermore, changes to the Defense Information Systems Agency (DISA) Common Operating Environment (COE), has necessitated a major re-design to ensure the C2 system deployed onboard CG assets can meet the operational requirements well into the future. EMC2-Seawatch has been designated as the C2 system that will replace SCCS on the legacy assets and will be the C2 system onboard the FRC-B cutter class.

1.3 CONTRACTOR PERSONNEL.

1.3.1 Project Manager. The Contractor shall provide a Project Manager who shall be responsible for all Contractor work performed under this task order. The Project Manager is further designated as Key by the Government (see PWS 1.4).

1.3.1.1 The Project 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 Project Manager shall be one of the senior level employees provided by the Contractor for this work effort. The name of the Project Manager, and the name(s) of any alternate(s) who shall act for the Contractor in the absence of the Project Manager, shall be provided to the Government as part of the Contractor's proposal. During any absence of the Project Manager, only one alternate shall have full authority to act for the Contractor on all matters relating to work performed under this task order. The Project Manager and all designated alternates shall be able to read, write, speak and understand English. Additionally, the Contractor shall not replace the Project Manager without prior acknowledgement from the Contracting Officer.

1.3.1.2 The Project 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 task order 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. The Contractor qualified personnel shall have knowledge and experience in the following area:

1.3.2.1 System Engineering and Integration.

1.3.2.2 System Testing and Evaluation.

1.3.2.3 DISA COE software development and integration.

1.3.2.4 Solaris and Windows operating system development and integration.

1.3.2.5 U.S Coast Guard electronic equipment, including gryo compasses, Global Positioning System (GPS), Long Range Aid to Navigation (LORAN), depth sounders, speed logs, anemometers, psychrometers, Automatic Identification System (AIS) transceivers, air search RADAR, surface search RADAR, Fire Control RADAR, Electronic Surveillance Measures (ESM), Identification, Friend or Foe (IFF) , RADAR and video distribution, and data converters.

1.3.2.6 U.S. Coast Guard communication links, including Secure IP Routing Network (SIPRNET), LINK-11 and Officer in Tactical Charge Information Exchange System (OTCIXS) Equipment.

1.3.2.7 U.S. Coast Guard navigation systems, practices and standards.

1.3.2.8 National and international standards relating to electronic charting and navigation.

1.3.2.9 Navigation and tactical generation and simulation.

1.3.2.10 National and International shipboard sensor interface standards, including NMEA 0183.

1.3.2.11 Network and serial communications.

1.3.2.12 Data storage, archival, retrieval and playback.

1.3.2.13 U.S Coast Guard shipboard installation standards.

1.3.2.14 National and international standards for software development, testing, and integration.

1.3.2.15 Information Assurance, IT security plan compliance, and DHS MD 4300.1 IT System Security.

1.3.2.16 TEMPEST standards and practices.

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.3.2 Contractors shall wear a Common Access Card (CAC) identification card furnished by the government. Contractors shall use the Department of Defense Contractor Verification System to acquire the CAC. Contractor identification shall be worn above the waist and remain in plain view 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 task order. 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.

1.5 SECURITY.

Contractor access to classified information is required under this task order. The maximum level of classification is Secret. The details are specified in the attached Department of Defense Form 254.

1.5.1 All employees specified in this task order shall possess and maintain a Secret security clearance. 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 Nondisclosure Agreement (SF-312)”.

1.5.2 A DD-Form-254, Department of Defense Contract Security Classification Specification shall be used.

The Contractor shall submit a list to the COTR showing the name and address of each employee under this task order prior to the start of the period of performance and within three (3) business days anytime information on that list changes.

1.6 PERIOD OF PERFORMANCE.

The period of performance for this task order is one year from the date of award with four (4) one-year option periods.

1.7 PLACE OF PERFORMANCE.

The primary places of performance shall be as follows:

1.7.1 U.S. Coast Guard Command and Control Engineering Center (C2CEN), 4000 Coast Guard Blvd, Portsmouth, VA 23452-2199.

1.7.2 Aboard Coast Guard cutters, at their home, other ports of call, and while underway, as directed by

C2CEN

1.7.3 At various other locations as required in support of this task order.

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 preformed. 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 task order.

1.9 TRAVEL.

Contractor travel shall be required to support this task order. 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 estimates that approximately 5 Contractor trips will be made during the Period of Performance and 5 Contractor trips during the option year. Each trip will last approximately three (3) days.

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 task order and review the Contractor's project plan. The Kick-Off Meeting will be held at the Command and Control Engineering Center (C2CEN), 4000 Coast Guard Blvd, Portsmouth, VA 23452-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 Project Manager shall provide a bi-weekly activity report to the COTR and Contracting Officer via electronic mail. 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 bi-weekly period.

1.13 PROGRESS MEETINGS.

The Project 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 III (Windows XP and Microsoft Office Applications).

1.15 PERFORMANCE REQUIREMENTS SUMMARY.

This task order includes a Performance Requirements Summary (PRS). In general, the PRS sets forth the expected outcomes (objectives) of the task order, the service(s) required of the Contractor to achieve the objectives, a performance standard per outcome, and a plan for a reduction in payment 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, including reductions in payment in accordance with any clause for inspection of services.

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 52.227-14 Rights in Data - General (June 1987).

1.17 PROTECTION OF INFORMATION. Contractor access to proprietary information is required under this work statement. 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, requires Federal agencies to ensure that Electronic and Information Technology (EIT) they develop, procure, maintain or use is accessible to and usable by employees and consumers with disabilities.

The referenced EIT acquisition has been determined to be applicable to Section 508. In accordance with DHS Management Directive 4010.2 – Electronic and Information Technology Accessibility, claims for National Security Exception require a review and approval by the DHS Office of Accessible Systems & Technology (OAST).

DHS OAST has reviewed this acquisition request and has determined that a National Security Exception for the purposes of Section 508 applies and is thereby authorized. A memorandum identifying OAST’s approval has been attached and needs to be included in the contract file.

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

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 clause

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

(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 offeror'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

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 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 CG 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 CG and HLS EA.

• All IT hardware or software shall be compliant with the CG 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 CG and DHS Enterprise Data Management Office (EDMO) for review and insertion into the CG 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 TERMS & DEFINITIONS. No special terms are used in the PWS. Acronyms are defined through this document at first appearance.

3.0 GOVERNMENT FURNISHED RESOURCES. The Government will provide the workspace, equipment and supplies necessary to perform the on-site portion of Contractor services required in this task order, unless specifically stated otherwise in this work statement.

4.0 CONTRACTOR FURNISHED PROPERTY. None.

5.0 REQUIREMENTS.

5.1 Project Management Support. The Contractor shall provide project management support services, including but not limited to documentation support, presentation support, meeting support, program management support and information management support.

5.1.1 The Contractor shall comply with the PWS in its entirety and shall provide oversight of all Contractor and subcontractor services (both onsite and offsite).

5.1.2 The Contractor shall provide on-site project management services and shall be knowledgeable in system engineering and project management principles, including project planning, project scheduling and monitoring, requirements analysis, risk management, quality assurance, system testing and evaluation, and configuration management.

5.1.3 The Contractor shall provide onsite supervision for the day-to-day administrative and technical services. A Contractor designated onsite manager will be responsible for scheduling Contractor representation at meetings and delivery of all required reports.

5.1.4 The Contractor shall support C2CEN in developing Project Management Plan (PMP), including but not limited to a Project Work Breakdown Structure (WBS) and an Integrated Project Schedule (IPS).

5.2 Requirements Development and Analysis. The Contractor shall support C2CEN in deriving system level requirements and analyzing the impact of each requirement in terms of schedule, cost, and technical risk to the overall project plan.

5.2.1 Software Requirements. The contractor shall support C2CEN in allocating system requirements to be performed via software. Software requirements shall be documented in the Software Requirements Document (SRD).

5.2.2 Hardware Requirements. The contractor shall support C2CEN in allocating system requirements to be performed via hardware. Hardware requirements shall be documented in the Hardware Requirements Document (HRD).

5.3 System Design. The contractor shall support C2CEN in designing a scalable, flexible, and reliable C2 system that meets the baseline system requirements. The system design shall be documented in the System Design Specification (SDS).

5.3.1 Software Development & Integration. The contractor shall support the CG in analyzing and identifying COTS/GOTS software applications to meet the requirements allocated to software. The system shall utilize COTS/GOTS software applications to the furthest extent possible. If it determined that software application development is required, the contractor shall assist the CG in identifying sources-of-supply.

The software applications shall be documented in the Software Design Specification (SwDS).

5.3.2 Hardware integration. The contractor shall support the CG in analyzing and identify Commercial-off-the shelf/ Government off-the-shelf (COTS/GOTS) hardware to meet the requirements allocated to hardware. Hardware shall be limited to COTS/GOTS or modified COTS/GOTS. The software applications shall be documented in the Hardware Design Specification (HDS).

5.3.3 Interface Design Specification. The contractor shall support C2CEN in identifying hardware-hardware, hardware-software, and software-software interface requirements. Interface requirements shall be documented in the Interface Design Specification (IDS).

5.4 System integration. The contractor shall integrate hardware and software components specified in the SSD, SDS, HDS, and IDS.

5.4.1 The Contractor shall perform system integration at C2CEN's development laboratories, and shall assist as directed at various other offsite locations.

5.5 System Testing and Evaluation. The contractor shall support Developmental Testing and Evaluation (DT&E) and Operational Testing and Evaluation (OT&E) activities as directed by C2CEN. DT&E and OT&E activities include, but are not limited to:

A. Developing Master Test Plan B. Developing Test cases and scenarios C. Developing Test procedures D. Developing System Requirements Verification Matrix.

E. Executing test plans and procedures

5.6 Prototype installations. The contractor shall support C2CEN in performing prototype installations to integrate EMC2-Seawatch on CG assets as directed by C2CEN. These activities include, but are not limited to:

A. Performing site surveys B. Developing installation plans C. Updating ships drawings D. Performing prototype installs E. Performing System Operational Verification Tests (SOVT)

5.7 System Support. The contractor shall support C2CEN in troubleshooting and resolving problems on cutters in which EMC2-Seawatch is installed.

5.7.1 The Contractor shall 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.8 Documentation. The Contractor shall support C2CEN in creating, editing, and revising all necessary documents associated with this task order. Documents include, in addition to those noted elsewhere in this task order:

A. System Operators Manual B. Software Version Description C. Software Installation Plan

D. Software Users Manual E. Engineering Change documentation

5.9 Meetings. The Contractor shall participate in on-site and off-site meetings, as directed by C2CEN, in support of this task order.

5.10 Reporting. Unless otherwise stated, the following reports shall be sent to the COTR, CG EMC2- Seawatch Development Lead, and the Afloat Division, C2 system branch chief.

5.10.1 Activity Reports. The Contractor shall submit a brief and collective biweekly Activity Report via email. This report shall contain the following items:

• Summary of work performed during previous two weeks (not included in Trip Reports)

• Planned tasks for the next two weeks

• Any scheduled travel and absences

5.10.2 Burn-rate Reports. The Contractor shall submit a monthly Burn-rate Report 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.

• Burn Rate is defined as “Rate at which funds are expended on a project (for example, total dollars per day or total dollars per week). Usually quoted based on labor hours only, but may include materials as well”.

5.10.3 Trip Reports. The Contractor shall submit a Trip Report via email within five (5) business days after returning from an offsite support trip. If offsite support trips occur back-to-back, then the Trip Report shall be submitted within five (5) business days 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.

6.1 Coast Guard Industrial Security Program, COMDTINST 5520.13 [1998-08-08]

6.2 National Industrial Security Program, DODINST5220.22 (series)

6.3 Equipment Tag-Out Procedures, COMDTINST 9077.1 [1995-12-21]

6.4 Safety and Environmental Health Manual, COMDTINST M5100.47 [1990-04-24]

6.5 Electronics Manual, COMDTINST M10550.25 [2002-07-31]

6.6 Naval Engineering Manual, COMDTINST M9000.6 [2000-09-20]

6.7 MIL-DTL-15024F, Plates, Tags, and Bands for Identification of Equipment, General Specification [1997- 11-28]

6.8 MIL-STD-1310G, Shipboard Bonding, Grounding, and Other Techniques for Electromagnetic Compatibility and Safety [1996-06-28]

6.9 Command, Control, Communications, Computers and Information Technology, (C4&IT) Systems Development Life Cycle (SDLC) Policy, COMINST 5230.66

6.10 Command, Control, Communications, Computers and Information Technology, (C4&IT) Information Assurance (IA) Policy, COMDTINST 5230.67

6.11 Command, Control, Communications, Computers and Information Technology, (C4&IT) Enterprise Architecture (EA) Policy, COMDTINST 5230.68

6.12 Command, Control, Communications, Computers and Information Technology, (C4&IT) Configuration Management Policy, COMDTINST 5230.69

6.13 Command, Control, Communications, Computers and Information Technology, (C4&IT) Infrastructure Management Policy, COMDTINST 5230.70

6.14 USCG Navigation Standards, COMDTINST M3530.2A [2002-05-16]

6.15 US Navy’s ECDIS-N Certification Process, OPNAVINST 9420.2 [2001-02-15]

6.16 ITU-R M.1371-1 (AIS) [2001-08]

7.0 DELIVERABLES.

The Contractor shall consider items in BOLD as having mandatory due dates. Items noted as “COTR Checkpoints” are deliverables or events that must be reviewed and approved by the COTR prior to proceeding to next deliverable or event in this PWS.

ITEM PWS DELIVERABLE / EVENT DUE BY

1 1.10 Kick-Off Meeting

(7) days after date of award

2 1.10;

1.11 Draft Contractor Project Plan

Due at Kick-Off Meeting

3 1.10;

1.11 Final Contractor Project Plan

NLT (3) three business after Kick-Off Meeting

4 1.12

5.9.1 Activity Reports

Bi-weekly

5 5.9.2 Burn-rate Reports COB the fifth (5th) business day of the following month

6 5.9.3 Trip Reports NLT five (5) business days after return from trip

Note: PWS 8.0 begins on the next page.

8.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS).

The PRS table below reflects the deliverables considered by the Coast Guard to be most important for the successful performance of this task order. This includes the expected standards of performance and planned reductions for not meeting those standards.

The Government will establish a Quality Assurance Surveillance plan that is not part of this task order in order to monitor performance requirements summary items described in the table below.

CONTRACTOR MANAGEMENT, TECHINCAL AND ADMINISTRATIVE SUPPORT SERVICES FOR THE U.S. COAST GUARD, COMMAND AND

CONTROL ENGINEERING CENTER (C2CEN), SHIPBOARD ENGINEERING BRANCH (ES)

Objectives Required Service Performance Standard Reductions

1. Timely receipt of trip reports

Provide trip reports NLT 5 business days after returning from an offsite support trip. If offsite support trips occur back-to-back then the Trip Report shall be submitted within five (5) business days after the last offsite support trip.

(PWS 5.0)

100% on time delivery (unless Government causes delay)

A $200 reduction will be assessed for each day a trip report is overdue

2. Timely Reports Prompt response to requests for reports on any ongoing task (PWS 5.0)

All requests are acknowledged immediately.

Response times are consistent with customer needs (unless delay is caused by the Government)

If the Contractor demonstrates repeated failure to meet customer needs in any given quarter of the performance period, as determined by the COTR, the results may be reflected in the contractor’s performance evaluation for the task order.

3. Quality Technical Writing

All documents produced by the Contractor shall be well organized, clearly written and expertly edited. (PWS Section 5.0)

• Meets the requirements set forth in the PWS

• Written in a clear and simple language

• Organized in a logical manner

• Free from grammatical errors

If the deliverables determined to be unacceptable to the COTR and cannot be resolved to the satisfaction of the Government, results will be reflected in the Contractor’s performance evaluation for the task order.

CONTRACTOR MANAGEMENT, TECHINCAL AND ADMINISTRATIVE SUPPORT SERVICES FOR THE U.S. COAST GUARD, COMMAND AND

CONTROL ENGINEERING CENTER (C2CEN), SHIPBOARD ENGINEERING BRANCH (ES)

Objectives Required Service Performance Standard Reductions

4. High Quality Project Management Support that results in informed, accurate and timely decisions by Project Leaders so that project goals are accomplished.

Project management support services including project planning, project execution, project control and project close-out services.

(PWS 5.0)

Project management quality standards are as follows:

• Accurate information is provided to decision makers in timely manner.

• Attention to detail.

• Reports are logical and clearly written.

• Effective analysis of variables is used to analyze risk.

• Thorough research is apparent and effectively utilized in the reporting process.

• Milestones are realistic and actionable.

If the deliverables determined to be unacceptable to the COTR and cannot be resolved to the satisfaction of the Government, results will be reflected in the Contractor’s performance evaluation

CONTRACTOR MANAGEMENT, TECHINCAL AND ADMINISTRATIVE SUPPORT SERVICES FOR THE U.S. COAST GUARD, COMMAND AND

CONTROL ENGINEERING CENTER (C2CEN), SHIPBOARD ENGINEERING BRANCH (ES)

Objectives Required Service Performance Standard Reductions

5. High Quality technical support that results in informed, accurate and timely decisions by Project Leaders so that project goals are accomplished.

Technical support services including system requirements analysis, system design, system testing and evaluation, and system support.

(PWS 5.0)

Technical Support quality standards are as follows:

• Recommendation based on thorough analysis of system requirements and alternatives.

• High quality technical workmanship.

• Comprehensive testing and evaluation of all system requirements

• Strict configuration control of engineering and test labs

• Responsive to cost and schedule constraints

If the deliverables determined to be unacceptable to the COTR and cannot be resolved to the satisfaction of the Government, results will be reflected in the Contractor’s performance evaluation