Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF SEPTEMBER 14, 2013 FBO #4312
SOLICITATION NOTICE

R -- Purchase of System Support Services - DRAWING

Notice Date
9/12/2013
 
Notice Type
Combined Synopsis/Solicitation
 
NAICS
541990 — All Other Professional, Scientific, and Technical Services
 
Contracting Office
Department of Homeland Security, United States Coast Guard (USCG), Commanding Officer (C2CEN), USCG Command and Control Engineering Center, 4000 Coast Guard Boulevard, Portsmouth, Virginia, 23703-2199, United States
 
ZIP Code
23703-2199
 
Solicitation Number
HSCG44-13-Q-PCR056
 
Archive Date
10/5/2013
 
Point of Contact
James A Lassiter, Phone: (757)686-2149
 
E-Mail Address
james.a.lassiter@uscg.mil
(james.a.lassiter@uscg.mil)
 
Small Business Set-Aside
N/A
 
Description
DRAWING This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Subart 12.6 as supplemented with additional information included in this notice. This announcement constitutes the ONLY solicitation and no other solicitation document will be issued. This solicitation is issued as a Request for Quote number RFQ HSCG44-13-Q-PCR056. This number is for tracking purposes only. Solicitation documents and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 05-69. This procurement will be processed in accordance with FAR Part 12 and 13.5. The North American Industry Classification System (NAICS) is 541990. The SBA size standard is $14.0. This is Not a Small Business Set-Aside, It is not anticipated that there will be 2 or more qualified Small Business Concerns to provide pricing for this requirement IAW 19.502(a). The USCG Command Control and Communications Engineering Center (C3CEN) Portsmouth, VA 23703 intends to award a Firm Fixed Price Purchase Order Contract for NAIS Data Services, IAW Performance Work Statement below. The Period of Performance (POP) is one (1) year from date of Award. This purchase is for USCG C3CEN, 4000 Coast Guard Blvd. Portsmouth, VA 23703. The Coast Guard does not own nor can they obtain specifications or other technical data for these Services. Requests for drawings and specifications will be disregarded. Note: The Government/USCG reserves the right to Award on an All or None Basis that is the Gov may issue a Purchase Order to the Offeror that submits the lowest aggregate price rather than issue a Purchase Order to each Offeror on the basis of the lowest Quotation on each item. *PLEASE NOTE* Interested Offeror's are to provide Firm Fixed Price Proposals IAW Statement of Work by Sep/20/2013 @ 7:00AM EST. FIRM FIXED Price Proposals may be submitted on company letterhead stationery and must include the following information: Cost Breakdown, Unit Price, Extended Price, Total Price, Payment Terms, discount offered for prompt payment, Company DUNS and Cage Code. Email quotes to the POC Beverly A. Turman-Dawson, Acquisition Specialist, Beverly.A.Turman-Dawson@uscg.mil. The Anticipated Award Date for the Purchase Order Contract is Sep/20/2013; this date is approximate and not exact. Schedule B Line Item 1: 1 EA of - Automatic Identification System (AIS) System Support Services IAW THE ATTACHED PERFORMANCE WORK STATEMENT _____________________ Period of Performance: 1 Year from Date of Award The following clauses are incorporated by reference, entire clause(s) available at http://www.arnet.gov/far; The Following FAR Provisions apply to this Acquisition: FAR 52.212-1 Instructions to Offerors-Commercial Items (JUN 2008), FAR 52.212-2 Evaluation-Commercial Items (JAN 1999) - award will be made to the Offeror proposing the Overall Best Value to the Government considering, Price, Technical Capability. FAR 52.212-3 Offeror Representations and Certifications-Commercial Items (AUG 2009) to include Alt I (APR 2002). These certifications must be included with quote and can be accessed and downloaded via FedBizOps with this RFQ. Contractors are encouraged to submit through http://orca.bpn.gov FAR 52.212-4 Contract Terms and Conditions -Commercial Items (June 2010). FAR 52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders-Commercial Items (August 2011). FAR 52.252-2 Clauses Incorporated by Reference (Jun 1998), the full text of the clause may be accessed electronically at Internet address http://www.arnet.gov/far; A Data Universal Numbering System (DUNS) Number is the primary identifier in FAR 52.204-7 Central Contractor Registration (CCR) (Jul 2006). Contractors are located and identified in CCR by their DUNS number. To facilitate payment via Electronic Funds Transfer - CCR, contractors should be registered in the CCR. A DUNS Number can be obtained via www.dnb.com and CCR registration can be obtained via www.ccr.dlis.dla.mil End of Clause The following Clauses and others as indicated by the Contracting Officer as applicable shall apply to the awarded contract. FAR 52.222-3 Convict Labor (JUN 2003) (E.O. 11755) FAR 52.222-19 Child Labor-Cooperation with Authorities and Remedies (AUG 2009) (E.O. 13126) FAR 52.222-21 Prohibition of Segregated Facilities (FEB 1999) FAR 52.222-26 Equal Opportunity (MAR 2007) (E.O. 11246), FAR 52.222-35 Equal Opportunity for Special Disable Veterans, Veterans of the Vietnam Era, and Other Eligible Veterans (SEPT 2006) (38 U.S.C. 4212), FAR 52.222-36 Affirmative Action for Workers with Disabilities (JUN 1998) (29 U.S.C. 793), FAR 52.222-37 Employment Reports on Special Disabled Veterans and Veterans of the Vietnam Era, and Other Eligible Veterans (SEPT 2006) (38 U.S.C. 4212), FAR 52.225-13 Restrictions on Certain Foreign Purchases (JUN 2008) (E.O. 12722, 12724, 13059.13067, 13121, and 13129) FAR52.232-33 Payment by Electronic Funds Transfer-Central Contractor Registration (OCT 2003) (31 U.S.C. 3332) End of Clause The following clauses are incorporated by reference, entire clause(s) available at http://www.arnet.gov/far; NOTICE TO OFFERORS CONCERNING REPRESENTATIONS AND CERTIFICATIONS: This solicitation contains FAR Clause 52.204-7, Central Contractor Registration and FAR Provision 52.204-8, Annual Representations and Certifications. In accordance with FAR 4.1201 prospective contractors are required to submit annual representations and certifications via the Online Representations and Certifications Application (ORCA) at http://orca.bpn.gov. Please ensure completion prior to submission of your quote. Also note that paragraph (b) of FAR 52.204-8, applies. NATIONWIDE AUTOMATIC IDENTIFICATION SYSTEM SUPPORT SERVICES FOR THE AIS RECEIVE COVERAGE IN WESTERN RIVERS PERFORMANCE WORK STATEMENT 1.0 GENERAL. 1.1 SCOPE. The purpose of this PWS is for the U.S. Coast Guard (USCG) to obtain Automatic Identification System (AIS) data and maintenance support services for Western River coverage detailed in section 1.9.2 below, 24 hours a day, 7 days a week. The AIS data will be used by the USCG and shared with Other Government Agencies (OGA). 1.2 BACKGROUND. To enhance Maritime Domain Awareness and more closely monitor the transportation of Certain Dangerous Cargos along over 11,000 miles of U.S. waters following the terrorist attacks of September 2001, the Coast Guard established the Inland River Vessel Movement Center (IRVMC). IRVMC was created in 2003 in response to an operational requirement established by the Homeland Security Council as part of Operation Liberty Shield and promulgated by the Commandant of the U. S. Coast Guard in the Operation Neptune Shield Operations Order (ONS OPORD). The purpose for IRVMC was to track certain dangerous cargo (CDC) movements on the inland waterways and disseminate CDC movement data via MISLE, supplying Sectors with critical information supporting homeland security missions. The CDC barge reporting requirement was established via 33 CFR Part 165, Regulated Navigation Area (RNA) regulations. The RNA required vessels towing CDC barges to report to IRVMC four hours before entering the RNA, when passing each of 96 designated reporting points, whenever a change in barge status occurred, and when requested by the IRVMC. Approved reporting methodologies included phone, fax, e-mail and automated electronic reporting. IRVMC was initially established in St Louis, Missouri with a complement of 20 Reservists recalled to active duty under Title 10 authority. In September 2006, upon expiration of the Title 10 funding, IRVMC was relocated to the USCG Navigation Center (NAVCEN) in Alexandria, VA. In conjunction with the move to NAVCEN, the Reservists were replaced by commercially contracted personnel (5 watch standers & 1 supervisor) providing a one-person continuous watch. In January 2011, the CG suspended IRVMC reporting requirements in an effort to transition the cumbersome manual process to a more robust prototype River Information System (RIS), owned and operated by U. S. Army Corps of Engineers (USACE). RIS will use AIS technology to provide vessel tracking information to USACE, the USCG's Nationwide AIS, and other government agencies and systems requiring this information. The RIS and NAIS development and deployment are experiencing unanticipated delays, necessitating the need to obtain commercial AIS services for the Western Rivers. The USCG currently contracts with Maritime Information System Incorporated (MIS) for Western Rivers AIS Data. This contract maintains Contractor owned Automatic Identification System (AIS) receiver sites in Western Rivers areas and delivers the data to USCG enterprise Nationwide Automatic Identification System (NAIS) system. 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 contract. 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 Representative (COR). 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 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 contract. The Project Manager and all designated alternates shall be able to read, write, speak and understand English. 1.3.1.2 The Project Manager shall be available to the COR via telephone between the hours of 0800 and 1700 (EST), Monday through Friday, and shall respond to a request for discussion or resolution of technical problems within two (2) hours of notification. 1.3.2 QUALIFIED Personnel. The Contractor shall provide qualified personnel to perform all requirements specified under this Contract. All Contractor employees supporting contracts under this Contract shall be citizens or legal residents of the United States. 1.3.3 Employee Identification. 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.4 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 acknowledgment from the Contracting Officer. The Government may designate additional Contractor personnel as Key at the time of award. 1.5 SECURITY. Contractor access to acquisition and operationally sensitive information is required under this contract. Contractor and/or sub-contractor's employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the law and government policy and regulation. 1.5.1 All hardware, software, and services provided must be compliant in accordance with 140-01 Information Technology Systems Security and the DHS Sensitive Systems Handbooks 4300A or 4300B. 1.5.2 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 140.01 Information Technology Systems Security and the DHS Sensitive Systems Handbook prescribe policies and procedures on security for IT resources. Contractors shall comply with these policies and procedures, any replacement publications, or any other current or future DHS policies and procedures covering Contractors specifically for all 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.5.3 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 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. The Contractor shall 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.5.4 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.5.5 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.5.6 SECURITY REQUIREMENTS FOR UNCLASSIFIED INFORMATION TECHNOLOGY RESOURCES (JUN 2006) (a) The Contractor shall be responsible for Information Technology (IT) security for all systems connected to a DHS network or operated by the Contractor for DHS, regardless of location. This clause applies to all or any part of the contract that includes information technology resources or services for which the Contractor must have physical or electronic access to sensitive information contained in DHS unclassified systems that directly support the agency's mission. (b) The Contractor shall provide, implement, and maintain an IT Security Plan. This plan shall describe the processes and procedures that will be followed to ensure appropriate security of IT resources that are developed, processed, or used under this contract. (1) Within 30 days after contract award, the Contractor shall submit for approval its IT Security Plan, which shall be consistent with and further detail the approach contained in the offered proposal. The plan, as approved by the Contracting Officer, shall be incorporated into the contract as a compliance document. (2) The Contractor's IT Security Plan shall comply with Federal laws that include, but are not limited to, the Computer Security Act of 1987 (40 U.S.C. 1441 et seq.); the Government Information Security Reform Act of 2000; and the Federal Information Security Management Act of 2002; and with Federal policies and procedures that include, but are not limited to, OMB Circular A-130. (3) The security plan shall specifically include instructions regarding handling and protecting sensitive information at the Contractor's site (including any information stored, processed, or transmitted using the Contractor's computer systems), and the secure management, operation, maintenance, programming, and system administration of computer systems, networks, and telecommunications systems. (c) Examples of tasks that require security provisions include: (1) Acquisition, transmission or analysis of data owned by DHS with significant replacement cost should the Contractor's copy be corrupted; and (2) Access to DHS networks or computers at a level beyond that granted the general public (e.g., such as bypassing a firewall). (d) At the expiration of the contract, the Contractor shall return all sensitive DHS information and IT resources provided to the Contractor during the contract, and certify that all non-public DHS information has been purged from any Contractor-owned system. Components shall conduct reviews to ensure that the security requirements in the contract are implemented and enforced. (e) Within three (3) 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 (7.2 dated April 20, 2010) 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.5.7 CONTRACTOR EMPLOYEE ACCESS (JUN 2006) (a) Sensitive Information, as used in this Chapter, means any information, the loss, misuse, disclosure, or unauthorized access to or modification of which could adversely affect the national or homeland security interest, or the conduct of Federal programs, or the privacy to which individuals are entitled under section 552a of title 5, United States Code (the Privacy Act), but which has not been specifically authorized under criteria established by an Executive Order or an Act of Congress to be kept secret in the interest of national defense, homeland security or foreign policy. This definition includes the following categories of information: (1) Protected Critical Infrastructure Information (PCII) as set out in the Critical Infrastructure Information Act of 2002 (Title II, Subtitle B, of the Homeland Security Act, Public Law 107-296, 196 Stat. 2135), as amended, the implementing regulations thereto (Title 6, Code of Federal Regulations, Part 29) as amended, the applicable PCII Procedures Manual, as amended, and any supplementary guidance officially communicated by an authorized official of the Department of Homeland Security (including the PCII Program Manager or his/her designee); (2) Sensitive Security Information (SSI), as defined in Title 49, Code of Federal Regulations, Part 1520, as amended, "Policies and Procedures of Safeguarding and Control of SSI," as amended, and any supplementary guidance officially communicated by an authorized official of the Department of Homeland Security (including the Assistant Secretary for the Transportation Security Administration or his/her designee); (3) Information designated as "For Official Use Only," which is unclassified information of a sensitive nature and the unauthorized disclosure of which could adversely impact a person's privacy or welfare, the conduct of Federal programs, or other programs or operations essential to the national or homeland security interest; and (4) Any information that is designated "sensitive" or subject to other controls, safeguards or protections in accordance with subsequently adopted homeland security information handling procedures. (b) "Information Technology Resources" include, but are not limited to, computer equipment, networking equipment, telecommunications equipment, cabling, network drives, computer drives, network software, computer software, software programs, intranet sites, and internet sites. (c) Contractor employees working on this contract must complete such forms as may be necessary for security or other reasons, including the conduct of background investigations to determine suitability. Completed forms shall be submitted as directed by the Contracting Officer. Upon the Contracting Officer's request, the Contractor's employees shall be fingerprinted, or subject to other investigations as required. All Contractor employees requiring recurring access to Government facilities or access to sensitive information or IT resources are required to have a favorably adjudicated background investigation prior to commencing work on this contract unless this requirement is waived under Departmental procedures. (d) The Contracting Officer may require the Contractor to prohibit individuals from working on the contract if the Government deems their initial or continued employment contrary to the public interest for any reason, including, but not limited to, carelessness, insubordination, incompetence, or security concerns. (e) Work under this contract may involve access to sensitive information. Therefore, the Contractor shall not disclose, orally or in writing, any sensitive information to any person unless authorized in writing by the Contracting Officer. For those Contractor employees authorized access to sensitive information, the Contractor shall ensure that these persons receive training concerning the protection and disclosure of sensitive information both during and after contract performance. (f) The Contractor shall include the substance of this clause in all subcontracts at any tier where the subcontractor may have access to Government facilities, sensitive information, or resources. 1.6 PERIOD OF PERFORMANCE. The period of performance for this contract is one year from the date of award. 1.7 PLACE OF PERFORMANCE. The primary place of performance will be at the Contractor's facilities. 1.8 HOURS OF OPERATION. The contractor shall provide data 24 hours a day, 7 days a week. Scheduled outages for routine maintenance shall be announced to the USCG Navigation Center at least 14 calendar days in advance and will count against operational time. Unscheduled outages shall be reported to USCG Navigation Center within 2 hours of detection. 1.9 TRAVEL. The contractor is responsible for any travel necessary for routine preventative or emergency maintenance to the Contractor's equipment or data network, or for any network surveillance to fulfill the service terms of this contract. The Government will not reimburse the Contractor for travel to the primary place of performance. All travel required by the Government outside of these activities will be reimbursed to the Contractor in accordance with the Federal Travel Regulations (FTR). The Contractor shall be responsible for obtaining prior COR approval (electronic mail is acceptable) for any reimbursable travel to include a budgeted amount in advance of each travel event. 1.9.1 Coordination of Field Visits. The Contractor shall be responsible for ensuring all visits to USCG units and Third Party Sites are properly coordinated with the Contracting Officer's Representative (COR) and Site Owner or Point of Contact prior to travel. 1.9.2 AIS Site Locations: The following table details the rivers of interest and the geographical coordinates that mark the starting and ending locations of the desired coverage areas. The USCG desires terrestrial based sites only and solutions that require Satellite AIS, shipboard relays of AIS information, "to be" site installations will not be accepted. Sites should be pre-existing and collectively have the ability to meet the receive coverage outlined in the table below: River Start Location End Location 1. Alabama River 31.143611, -87.934722 32.495278, -86.2925 2. Allegheny River 40.448055, -79.995277 40.990555, -79.585 3. McClellan-Kerr Arkansas River 33.960555, -91.130555 36.236839, -95.7337 4. Atchafalaya River 30.996774, -91.775432 29.548888, -91.243888 5. Black Warrior River 32.532222, -87.853056 33.618611, -87.237222 6. Big Sandy River 38.362748, -82.597552 38.183503, -82.606054 7. Clint River 35.87292, -84.528031 36.085, -84.103611 8. Cumberland River 37.125556, -88.418056 36.568611, -85.502222 9. Green River 37.901944, -87.488333 37.215555, -86.893055 10. Hiwassee River 35.410378, -84.99276 35.287222, -84.749722 11. Illinois River 38.967222, -90.446944 41.995278, -87.710278 12. Kanawha River 38.829722, -82.127777 38.129444, -81.262222 13. Kentucky River 38.669115, -85.185149 38.191388, -84.867222 14. Licking River 39.078945, -84.499395 39.004173, -84.468685 15. Lower Mississippi River 29.164521, -89.258758 36.981111, -89.115556 16. Mobile River 30.706955, -88.036818 31.122296, -87.946052 17. Monongahela River 40.432777, -79.998055 39.411846, -80.13271 18. Missouri River 38.821111, -90.124722 42.491944, -96.515 19. Ohio River 40.448056, -80.030555 37.006389, -89.164721 20. Ouachita River 31.278241, -91.82384 33.622777, -92.834166 21. Red River 31.013107, -91.676774 32.59146, -93.74333 22. Tennessee-Tombigbee River 30.75, -88.036389 35.487222, -84.878889 23. Tennessee River 37.075277, -88.586388 35.958888, -83.849722 24. Upper Mississippi River 36.979444, -89.140555 45.233888, -93.495833 25. White River 33.941944, -91.094166 35.752777, -91.747777 26. Yazoo River 32.377219, -90.897062 33.170625, -90.458588 27. Gulf Intracoastal Waterway (Mobile, AL to Houston, TX) 27.8, -97.39 30.69, -88.04 The following figure is a graphical depiction of the coordinates given in the table above. SEE ATTACHED DRAWING 1.9.3 FUTURE AIS SITES The contractor shall notify the government of newly commissioned sites as they come on line and provide connectivity details such as network port numbers in order for the Government to make the necessary data connections. 1.10 KICK-OFF MEETING. The Contractor shall attend a Kick-Off Meeting via teleconference with the Contracting Officer, the COR and the Technical Program Manager (TPM) NLT five (5) 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 contract and review the Contractor's project plan. The Kick-Off Meeting will be held via teleconference. 1.11 PROJECT PLAN. The Contractor shall provide a draft Project Plan that at a minimum, outlines how data will be sent, when it will be sent, Casualty response strategy, POC's for regular business hours and after hour notification requirements. The Contractor shall provide a final Project Plan to the COTR not later than 5 business days after the Kick-Off Meeting. 1.12 STATUS REPORTS. The Project Manager shall provide a monthly progress report to the Contracting Officer, COTR, and the TPM via electronic mail. This report shall include a summary of all Contractor work performed, any problems experienced and mitigation efforts. 1.13 STATUS MEETINGS. The Project Manager shall be responsible for keeping the Contracting Officer and COTR informed about Contractor progress throughout the performance period of this contract, and ensure Contractor activities are aligned with USCG objectives. 1.13.1 At minimum, the Project Manager shall review the status and results of Contractor performance with the COR on a monthly basis by telephone. 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 (Windows Vista and Microsoft Office 2007 Applications). 1.15 PERFORMANCE REQUIREMENTS SUMMARY. This contract includes a Performance Requirements Summary (PRS). In general, the PRS sets forth the expected outcomes (objectives) of the contract, 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 contract shall be considered Government property. 1.16.1 All documentation, photography and electronic data and information collected by the Contractor and entered into or generated in support of this contract shall be considered Government property, and shall be returned to the Government at the end of the performance period. 1.17 PROTECTION OF INFORMATION. Contractor access to proprietary information is required under this contract. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive but Unclassified (SBU) Information. SBU includes information categorized by DHS or other government agencies as: For Official Use Only (FOUO); Official Use Only (OUO); Sensitive Homeland Security Information (SHSI); Limited Official Use (LOU); Law Enforcement Sensitive (LES); Safeguarding Information (SGI); Unclassified Controlled Nuclear Information (UCNI); and any other identifier used by other government agencies to categorize information as sensitive but unclassified. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a non-disclosure agreement (DHS Form 11000-6). 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 (EIT), they must ensure that it is accessible to people with disabilities. Federal employees and members of the public who have disabilities must have equal access to and use of information and data that is comparable to that enjoyed by non-disabled Federal employees and members of the public. All EIT deliverables within this work statement shall comply with the applicable technical and functional performance criteria of Section 508 unless exempt. Specifically, the following applicable EIT accessibility standards have been identified: 1.18.1 Section 508 Applicable EIT Accessibility Standards 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 Javascript and XML (AJAX) then 1194.21 Software standards also apply to fulfill functional performance criteria. 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 help desk shall have the ability to transmit and receive messages using TTY. 1.18.2 Section 508 Applicable Exceptions Exceptions for this work statement have been determined by 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.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. 1.18.3 Section 508 Compliance Requirements 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 authorization from the DHS Office of Accessible Systems and Technology (OAST) in accordance with DHS MD 4010.2. 1.19 DHS Enterprise Architecture Compliance All solutions and services shall meet DHS and USCG Enterprise Architecture policies, standards, and procedures. Specifically, the Contractor shall comply with the following Homeland Security Enterprise Architecture (HLS EA) and Coast Guard Enterprise Architecture (CGEA) requirements: (1) All developed solutions and requirements shall be compliant with the HLS EA and CGEA. (2) All IT hardware or software shall be compliant with the HLS EA Technical Reference Model (TRM) Standards and Products Profile. (3) Description information for all data assets, information exchanges and data standards, whether adopted or developed, shall be submitted to the DHS Enterprise Data Management Office (EDMO) for review and insertion into the DHS Data Reference Model and Enterprise Architecture Information Repository. (4) In compliance with Office of Management and Budget (OMB) mandates, all network hardware shall be IPv6 compatible without modification, upgrade, or replacement. (5) All Information Technology assets being developed, procured, or acquired shall be IPv6 capable. 2.0 GOVERNMENT TERMS & DEFINITIONS. 2.1 AIS Automatic Identification System 2.2 COR Contracting Officer's Representative (Formerly Called COTR) 2.3 C3CEN Command, Control, and Communications Engineering Center 2.4 FTR Federal Travel Regulations 2.5 NAIS Nationwide Automatic Identification System 2.6 Operational System or sub-system functioning normally within tolerances 2.7 Outage Failure to receive and convey a properly formatted AIS message from a vessel within range 2.8 PM Project Manager 2.9 SOC System Operations Center 2.10 TPM Technical Program Manager 2.11 Up-time System functioning within its predefined parameters and tolerances 2.12 USCG OSC United States Coast Guard Operations System Center 2.13 USCG RDC United States Coast Guard Research & Development Center 3.0 GOVERNMENT FURNISHED RESOURCES. The Government will provide the following to the Contractor for work required under this contract: 3.1 Interconnect Support Agreement (ISA) for Contractor signature. 3.2 Instruct Contractor staff on how to connect / maintain the data feed. 3.3 Points of contact at USCG OSC, USCG RDC, USCG Navigation Center (NAVCEN), and USCG C3CEN. 3.4 The Government will provide copies of the references cited in this work statement at the Kick-Off Meeting. 4.0 CONTRACTOR FURNISHED PROPERTY. The Contractor shall furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract, except for the Government Furnished Resources specified in section 3 of this PWS. 5.0 REQUIREMENTS. The Contractor will provide Automatic Identification System (AIS) data services for designated areas as designated in this PWS. The AIS data will be used by the USCG and shared with other Government agencies at no additional cost to the Government. 5.1 The Contractor shall provide an AIS feed in the most current NEMA 0183 format per the International Standards from all sites needed to meet the coverage area listed in Section 1.9.2 to the USCG computer(s) located at the CG Research and Development Center (RDC). This will be the first step for evaluation and testing of data before connection to CG Operational Databases. 5.1.1 If formatting issues are found during evaluation, Contractor will work with CG RDC to understand and mitigate data format/delivery issues 5.1.2 Upon completion of the evaluation, Contractor will connect to the CG Enterprise Data Center (EDC) 5.2 The Contractor shall be responsible for the availability and maintenance of all sites. The Contractor shall maintain an availability of 96.0% or better, per site, calculated monthly 5.2.1 Availability = (Total site up time)/ (Total Site up time + Total site down time). Availability is rounded down with an accuracy of one tenth of a percent, for example 95.97% becomes 95.9%. 5.2.2 The Government will apply a fee reduction as outlined in the following table if the combined operational availability falls below the required level of 96% for a site during any month. The penalty shall be deducted from the monthly cost for the month in which the operational availability was not met. The penalty will be calculated by: (monthly cost/ total number of sites)= monthly cost per site (Monthly cost per site x Penalty rate per site) = calculated per site penalty fee Sum the Calculated per site penalty fee from each site performing below the availability of 96% to get the Total penalty fee Operational Availability Penalty rate per site Payment 100% - 96% None Full %100 95.9% - 90% 10% Monthly Cost - (Total penalty fee) 89.9% - 80% 20% Monthly Cost - (Total penalty fee) 79.9% - 70% 30% Monthly Cost - (Total penalty fee) 69.9% - 60% 40% Monthly Cost - (Total penalty fee) 59.9% - 50% 50% Monthly Cost - (Total penalty fee) 49.9% - 0% 100% None 0% 5.3 The Contractor shall ensure that the connection interface from the AIS feed to the demarcation at USCG computer(s) located at the CG EDC shall be maintained at 99% availability. The PM, or a representative, shall be available and respond to all trouble calls from USCG NAIS Systems Operation Center (SOC) during connection failures. Connection interface downtime is applied as site down time to each site provided by the contractor. 5.4 The Contractor shall monitor the connections and provide a technical representative to assist the USCG personnel to remotely troubleshoot the equipment when a failure occurs. 5.4.1 The Contractor shall respond to technical problems within two (2) hours of notification Monday through Friday between 0800 and 1700 (EST), and within eight (8) hours at other times. 5.5 The Government and the Contractor shall sign an Interconnect Support Agreement (ISA) prior to connecting Contractor data sources to NAIS. 6.0 REFERENCES. 6.1 National Marine Electronics Association (NMEA) 0183, STANDARD FOR INTERFACING MARINE ELECTRONIC DEVICES, most current version per the International Standards. This standard defines the data structure used by certified AIS equipment and the USCG NAIS I-1 network. In particular, the NAIS I-1 network uses the TAG Block features in addition to the basic AIS equipment's sentence structures. 6.2 Nationwide Automatic Identification System (NAIS), INCREMENT-1 INTERFACE CONTROL DOCUMENT, Version 1.3.0. This document provides the interface requirements imposed on NAIS subsystems. It defines the message structure and protocols governing the interchange of data among the NAIS I-1 network components. 6.3 IMO Resolution MSC.74 (69), Annex 3, RECOMMENDATION ON PERFORMANCE STANDARDS FOR A UNIVERSAL SHIPBORNE AUTOMATIC IDENTIFICATION SYSTEMS (AIS). This standard defines the basic performance requirements for AIS equipment, and was used by International Telecommunications Union and International Electro technical Commission in developing technical and test standards. 6.4 IMO Resolution A.917 (22), GUIDELINES FOR THE ONBOARD OPERATIONAL USE OF SHIPBORNE AUTOMATIC IDENTIFICATION SYSTEMS (AIS). These 14 page guidelines have been developed to promote the safe and effective use of ship borne Automatic Identification Systems (AIS), in particular to inform the mariner about the operational use, limits and potential uses of AIS. Consequently, AIS should be operated taking into account these Guidelines. 6.5 IMO Safety of Navigation Circular.227, GUIDELINES FOR THE INSTALLATION OF A SHIPBORNE AUTOMATIC IDENTIFICATION SYSTEM (AIS). These 14 page guidelines, prepared by the International Association of Lighthouse Authorities (IALA) and adopted by the International Maritime Organization (IMO), contains guidelines for manufacturers, installers, yards, suppliers and ship surveyors. It does not replace documentation supplied by the manufacturer. IMO SN Circ.245 amends these guidelines to recommend that AIS be connected through an uninterrupted power supply. 6.6 ITU-R Recommendation M.1371-4, TECHNICAL CHARACTERISTICS FOR A UNIVERSAL SHIPBORNE AUTOMATIC IDENTIFICATION SYSTEM USING TIME DIVISION MULTIPLE ACCESS IN THE MARITIME MOBILE BAND. The International Telecommunications Union Sector for Radio communications formally adopted this standard in August 2001. This is the standard that defines in detail how the AIS works, and as such is the primary AIS standard. It can be purchased electronically from ITU. ITU gave IALA the responsibility of maintaining technical guidelines for AIS design, and is available from them as "IALA TECHNICAL CLARIFICATIONS ON RECOMMENDATION ITU-R M.1371-1". 6.7 DHS Management Directive (MD) 11042.1 Safeguarding Sensitive But Unclassified (For Official Use Only) Information 6.8 DHS MD 140.01 Information Technology Systems Security and the DHS Sensitive Systems Handbook 6.9 FIPS 140-2 and FIPS 197 Advanced Encryption Standard (AES) 256 encryption compliance 6.10 Computer Security Act of 1987 (40 U.S.C. 1441 et seq.) 6.11 Government Information Security Reform Act of 2000 6.12 Federal Information Security Management Act of 2002 6.13 OMB Circular A-130 6.14 DHS Sensitive System Policy Publication, 4300A (7.2 dated April 20, 2010) 6.15 Protected Critical Infrastructure Information (PCII) as set out in the Critical Infrastructure Information Act of 2002 (Title II, Subtitle B, of the Homeland Security Act, Public Law 107-296, 196 Stat. 2135) 6.16 Title 6, Code of Federal Regulations, Part 29 6.17 Sensitive Security Information (SSI), as defined in Title 49, Code of Federal Regulations, Part 1520 6.18 Policies and Procedures of Safeguarding and Control of SSI For copies of references, you may contact the Contracting Officer. 7.0 DELIVERABLES. The Contractor shall consider items in BOLD as having mandatory due dates. Items noted as "COR Checkpoints" are deliverables or events that must be reviewed and approved by the COR prior to proceeding to next deliverable or event in this PWS. ITEM PWS DELIVERABLE / EVENT DUE BY 1 1.10 Kick-Off Meeting NLT five (5) business days after award. 2 1.10; 1.11 Draft Contractor Project Plan Due at Kick-Off Meeting. 3 1.10; 1.11 Final Contractor Project Plan NTL (5) days after the Kick-Off Meeting 4 1.12 Monthly Status Reports NLT the 10th day of the Month. (1 copies each via e-mail to USCG TPM, COR) and Contracting Officer. 5 1.56(b)(1) IT Security Plan NLT 30 days after contract award 6 1.56(e) IT Security Accreditation NLT three (3) months after contract award 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 contract. This includes the expected standards of performance and positive or negative incentives. NATIONWIDE AUTOMATIC IDENTIFICATION SYSTEM SUPPORT SERVICES FOR THE AIS RECEIVE COVERAGE IN WESTERN RIVERS Objectives Required Service Performance Standard Incentives (positive or negative) 1. Timely receipt of deliverables As specified in PWS 7.0, unless otherwise modified by Contracting Officer 100% on-time delivery (unless Government causes delay) The Government will apply a $250 reduction for each business day a deliverable is overdue beyond the performance standard (as verified by the COR). The Contracting Officer will make the decision after a written notice and a request for the Contractor to provide excusable delay information. 2. Site availability The Contractor shall be responsible for the availability and maintenance of all sites (PWS 5.2) The Contractor shall ensure that the AIS receiver sites are operational 96% or more per month (PWS 5.2.1) The Contractor shall maintain an availability of 96% or better, per site. The Government will apply a fee reduction based on the 96% availability per site each month not being met. The penalty fee will be calculated using a per site monthly cost for each site not meeting the availability as described in the PWS. (PWS 5.2.2) NOTICE FOR FILING AGENCY PROTESTS United States Coast Guard Ombudsman Program It is the policy of the United States Coast Guard (USCG) to issue solicitations and make contract awards in a fair and timely manner. The Ombudsman Program for Agency Protests (OPAP) was established to investigate agency protest issues and resolve them without expensive and time-consuming litigation. OPAP is an independent reviewing authority that is empowered to grant a prevailing protester essentially the same relief as the Government Accountability Office (GAO). Interested parties are encouraged to seek resolution of their concerns within the USCG as an Alternative Dispute Resolution (ADR) forum rather than filing a protest with the GAO or some external forum. Interested parties may seek resolution of their concerns informally or opt to file a formal agency protest with the Contracting Officer or Ombudsman. Informal Forum with the Ombudsman. Interested parties who believe a specific USCG procurement is unfair or otherwise defective should first direct their concerns to the applicable Contracting Officer. If the Contracting Officer is unable to satisfy their concerns, interested parties are encouraged to contact the U.S. Coast Guard Ombudsman for Agency Protests. Under this informal process the agency is not required to suspend contract award performance. Use of an informal forum does not suspend any time requirement for filing a protest with the agency or other forum. In order to ensure a timely response, interested parties should provide the following information to the Ombudsman: solicitation/contract number, contracting office, Contracting Officer, and solicitation closing date (if applicable). Formal Agency Protest with the Ombudsman. Prior to submitting a formal agency protest, protesters must first use their best efforts to resolve their concerns with the Contracting Officer through open and frank discussions. If the protester's concerns are unresolved, an Independent Review is available by the Ombudsman. The protester may file a formal agency protest to either the Contracting Officer or as an alternative to that, the Ombudsman under the OPAP program. Contract award or performance will be suspended during the protest period unless contract award or performance is justified, in writing, for urgent and compelling reasons or is determined in writing to be in the best interest of the Government. The agency's goal is to resolve protests in less than 35 calendar days from the date of filing. Protests shall include the information set forth in FAR 33.103(d) (2). If the protester fails to submit the required information, resolution of the protest may be delayed or the protest may be dismissed. To be timely protests must be filed within the period specified in FAR 33.103(e). Formal protests filed under the OPAP program should be submitted to: COMMANDANT (CG-9131) U S COAST GUARD OMBUDSMAN PROGRAM FOR AGENCY PROTESTS 2100 2ND ST SW STOP 7112 WASHINGTON DC 20593-7112 The Ombudsman Hotline telephone number is 202.372.3695
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/DHS/USCG/C2EC/HSCG44-13-Q-PCR056/listing.html)
 
Record
SN03185249-W 20130914/130912235244-5416b2f258a7ffa95dc205ff6cbd9af6 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.