LRIT_ASP_Solicitation_Questions_and_Responses_052715.docx

DOCX document 25 KB Posted

Attached to
Technical Support Services for the U. S. Coast Guard Office of C4 and Sensor Capabilities Long Range Identification and Tracking (LRIT) Application Service Provider
Solicitation number
HSCG23-15-R-PCI035
Issued by

About this file

LRIT ASP Solicitation Questions and Responses 052715

View the file

Other files

File Type Posted
ASPFE-DC.wsdl WSDL file
DC-ASPFE.wsdl WSDL file
A3Tech-Requirements_Revision_1.docx DOCX document
LRIT_ASP_Solicitation_Questions_and_Responses_052115.docx DOCX document
SynopsisSolicitation_LRIT_ASP_Revision_1.docx DOCX document
A2SOW_Revision_1.docx DOCX document
A3Tech-Requirements.docx DOCX document
A1_Pricing_Spreadsheet.xlsx XLSX spreadsheet
A4PPQ.DOC DOC document
A2SOW.docx DOCX document
SynopsisSolicitation_LRIT_ASP.docx DOCX document
Show all 11

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

LRIT ASP Questions Received and Responses:

Date: 05/21/15

1. Maps requirement is documented in SOW 2.1 It is not clear what “[…] basic tools to assist with technical troubleshooting of the connectivity between the ship, the Communication Service Provider (CSP), the ASP, and the U.S. NDC” is. Could the USCG kindly clarify which basic tools they may require?

RESPONSE: The minimum requirement for basic tools to assist with technical troubleshooting of the connectivity between the ship, the Communication Service Provider (CSP), the ASP, and the U.S. NDC consists of two parts. Part 1 includes the ability for the ASP to have a set of tools to reach the vessel for troubleshooting. This can be as simple as a ship owner’s phone list and phone to contact the operators to automated DNID resets. Technical troubleshooting of connectivity resolution has proven to be resolved by all ASP providers in variety of ways. The tools used by the ASP can be made available to the CG Watch but are not required. Part 2 requires an Application Service Provider Front End geo-display/viewer that is web-based. It must be able to run on Internet Explorer Version 9. The geo-spatial interface shall have the ability to display vessels last reported position and indicate any non-reporting cycles. This information shall be able to be filtered and generated in an Excel file version or Adobe Acrobat PDF. It shall also have the ability to generate an Excel or Adobe report of vessels that are considered non-reporting.

2. The 10 page limit of the technical proposal, we have some technical diagrams, etc. Can our proposal include additional annexes with no page limit?

RESPONSE: The 10 page limit is firm. If it is desired to put diagrams in the proposal, do so with the understanding of the space limitation. If the page limitation is exceeded, pages that exceed the page limitations shall be removed without review.

3. Section 2.2.3 Issue Conformance Test Reports to vessels on behalf of the U.S.:

We believe that there will be no need to test / certify the existing USA fleet in it’s entirety, but that this will only be required of newly Flagged vessels or vessels with a change of equipment. Please confirm this requirement with regard to the conformance testing (post award). Is this for new US Flagged vessels/"change of equipment” vessels, or for the entire existing fleet (approximately 800 ships)?

RESPONSE: Yes, this is for new flagged vessels and vessels that have changed their communications equipment.

4. Section 2.3.4 in the statement of work indicates that the USCG only wants to receive Latitude and Longitude. Could the USCG please reconfirm this since the majority of LRIT DCs are now requesting Latitude, Longitude, Speed and Heading?

RESPONSE: Thank you for pointing this out. We reviewed the requirements to reconfirm and have updated the SOW to include speed and heading as additional fields required for the ASP position reports.

5. Section 2.1 Web-based interface: What browser support is required?

RESPONSE: Internet Explorer Version 9.

6. The document 'ASP Technical Requirements’:

a. This has an isolated reference to sending LRIT XML messages over email; is this just a typo?

RESPONSE: Yes, this is a typo. Paragraph 9.1.1 should read, simply, “The examples provided form the suggested XML format upon which the LRIT messages should be based.”

7. Regarding the offers price proposal : From the SOW “The Government estimates, but does not guarantee that 4,460 labor hours per year are required to meet sections 2.4 – 2.7 of the SOW. If the offeror bases its price proposal on a labor mix other than what is provided in the pricing spreadsheet, the offeror must explain its rationale”.

Question- Traditionally, regarding delivery of ASP services for a contracting government, there is not a global precedent requiring a supplier to submit a proposal for labor hours as it relates to ASP services. This cost is traditionally included in the delivery of LRIT data. Regarding this RFP, will the USCG require the offeror to submit labor hours as part of their proposal? If this model differs from past ASP contracts, please explain the government’s intention regarding the change to the ASP pricing format. The SOW states that the labor hours are “required” to meet the terms of the SOW.

RESPONSE: Yes, the offeror is required to provide a breakout of the labor categories, hours, and rates that together provide the support for and total firm fixed price for the Support Labor CLIN covering SOW 2.4-2.7. This requirement serves to obtain greater awareness and tracking of the cost of LRIT ASP services.

Further clarification was requested on the Government’s response to Question #7.

RESPONSE: It is understood that services have been included in the delivery of LRIT data in the past. This contract has the support labor services separated from the delivery of data as shown in the pricing spreadsheet. The Government has provided an estimate of the labor categories and labor hours. Offerors may differ in their labor mix based on their business practices and expertise. The requested information provided by the labor mix and its supporting rationale (if different from the estimated hours per the instructions) is to evaluate an offeor’s pricing to assist in determining if the total firm fixed price for the Support Labor CLIN is fair and reasonable.

8. Regarding Annex A, #4 (4.6) in the ASP Technical Requirements Document: Receipt Messages codes; We notice most receipt messages are regarding communication between the NDC and the IDE. Please detail which messages are specific to the exchange between the NDC and the ASP.

RESPONSE: : The following receipt codes are applicable to communications between the ASP and the NDC:

· 4 (CSP not available)

· 5 (Ship not responding)

· 6 (Ship not available)

· 7 (System fault)

9. What is the anticipated award date?

RESPONSE: Award is anticipated to be made before the end of June.

10. Our parent company is recognized by the IMO as a LRIT ASP and is currently providing LRIT services to over 45 Administrations. Our US company is a wholly owned subsidiary and as an individual entity is not a recognized IMO LRIT ASP. Are we able to present the bid via our US company or will we have to submit our bid via our parent company?

RESPONSE: The parent company must make the bid per the requirement for the company to be a recognized IMO LRIT ASP.

11. A request was received asking for the WSDL Files from the USCG.

RESPONSE: The WSDL Files have been attached to this solicitation as a reference.

File details come from the government source that posted it. Updated .