14-4S01_QuestionAnswers.docx

DOCX document 22 KB Posted

Attached to
Services, Data Analysis of Bathymetric and Hydrographic Data
Solicitation number
N62306-14-Q-4S01
Issued by

About this file

Questions recieved and Answers provided for.

View the file

Other files

File Type Posted
14-4S01_QuestionAnswer2.docx DOCX document
N62306-14-Q-4S01-0001.doc DOC document
N62306-14-Q-4S01_SOL..doc DOC document
14-4S01_DD254.pdf PDF

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

N62306-14-Q-4S01 Questions & Answers

1. The subject RFQ was posted on NECO Website https://ww.neco.navy.mil. However, we were only able to obtain the entire solicitation including SOW through GOVWIN website---http://IQ.GovWin.com. Please clarify which website is the appropriate location to obtain all RFQ information.

The solicitation was posted to NECO (www.neco.navy.mil) on 16 July 2014 that filtered through to Federal Business Opportunities (FBO) (www.fbo.gov). The solicitation, with attachments, was re-posted to FBO on 24 July 2014. The appropriate location to obtain all RFQ information is at the Government Point of Entry (GPE) which is FBO.

2. Is it NAVOCEANO’s intent to award this contract against a GSA Federal Supply Schedule?

The Government’s intent is to award an Indefinite Delivery, Indefinite Quantity (IDIQ) type contract separate from GSA Federal Supply Schedules in accordance with FAR 12 and FAR 13.

3. We have reviewed Section 2.0 Scope of work and the undefined nature of the statement of work scope lends itself to an FPLOE type contract. Would NAVOCEANO consider changing the contract type from FFP to FPLOE?

Contract type is Firm-Fixed Price.

4. Section 5.1.1 requires delivery of a Processing Plan. However, this plan is not listed in the pricing table. Where should this plan be priced in our proposal and should it be invoiced as a separate line item?

The delivery of a Conceptual Processing Strategy is required for the submission of an offer to the solicitation. The file entitled “Conceptual Processing Strategy” has been added to the solicitation. The processing plan is not billable prior to the award. The Processing Plan will be required and can be invoiced for under the first task order as a one-time charge.

5. Where are travel prices to be proposed? Should travel be priced as one trip and added to the Exhibit 1 Data Set Table and the Table on Page 9? The totals row for the table on page 9 would be updated appropriately. Is travel invoiced as a separate line item?

Travel prices are to be proposed in the table as provided under Exhibit 1 Data Set Table.

Total price should reflect all prices charged during the specific period listed.

6. Regarding Travel, does the 4 days per trip include the travel days?

Travel days are included in the 4 days per trip requirement.

7. The table on page 9, which requests quantities of data sets (types) per year, requests Est. Cost. Is this supposed to be Est. Price?

The table is amended to reflect “Price” vice Est. Cost.

8. On page 9 of 52 of the solicitation it states “**Contractors shall provide a breakdown of labor categories (as required by the Statement of Work), estimated labor hours, and labor rates for each data set type.” Is this requirement correct for the FFP Contract Type or should it be deleted?

The statement has been retracted. A minimum criterion for consideration has been added.

9. There is a QASP Matrix on page 9 of 52. Is there any guidance/instructions for this matrix?

The following statement is added: “The matrix below is provided as a reference to the contractor for which performance will be graded against.”

10. On page 11 of 52, please provide clarification regarding the max quantity for years 1-5 being constant and the max amount varying between years 1 and 2-5 by $450K.

The types of datasets that will be sent will vary from year to year. Never will the quantity exceed the max quantity listed. More datasets will be available in year one. Dataset backlog will diminish as the effort continues.

11. On page 6 of 52, Section 2.5.7 states that monthly reports will include “monetary and hourly metrics”. Is this applicable for an FFP type contract where the requirement is to deliver processed data sets?

Section 2.5.7 is amended to read as follows: “Progress, Status, and Issues Document Generation: The contractor shall prepare a written progress / status / issues document that describes the current status of the effort. The contractor shall also document any issues that have been encountered in data processing and how they were remedied. The contractor shall provide the document to NAVOCEANO on a monthly basis.”

12. Referring to Exhibit 1 Data Set Table on page 8 of 52, how will datasets that cross one or more of the specified boundaries be classified? Below are several specific examples which would cross at least one boundary:

o A dataset, collected with an EM710, a Sonar Volume of 300 GB, and a depth range of 100 meters to 1000 meters, would it be classified as Hydrographic, Shallow Water Bathymetric or Bathymetric?

o A dataset, collected with a EM710, is entirely greater than 200 meters water depth, and has a Sonar Volume of 600 GB, would it be classified as Shallow water Bathymetric or Bathymetric?

o A dataset, collected with an EM1002 has more than 250 GB, how would it be classified?

o If a dataset is greater than 1TB, it falls outside of all Volumes. How would this be handled?

Sonar volumes and depth range values listed in section 2.2 of the SOW are estimates and area not considered thresholds. There are a couple of ways that the dataset types will be determined:

a. For datasets that have not been processed / validated / made into BAGs: A determination will be made to decide if NAVOCEANO Technical Specification documents exist. Where NAVOCEANO Technical Specification documents exist, we will use that document to define what type of survey it is. The document applies to both the transit data and main scheme data collected during the corresponding survey operation numbers. Technical Specification documents will accompany the dataset deliveries when available. In instances where survey Technical Specification documents are not available, we will classify them according to the area and average water depth of dataset. Dataset volume will typically be between limits listed in Section 2.2 in the SOW.

b. For datasets that have been processed / validated / but BAGs were either not produced or are not compatible with the current database structure: We will consider these datasets as "Other".

13. On Page 24 of 52, there is a “X” next to (17)(i) 52.219-9, Small Business Subcontracting Plan (July 2013) (15 U.S.C. 637(d)(4)). On, page 34 of 52 Section (c) states upon request by the CO offeror shall submit and negotiate a subcontracting plan. Please clarify if a subcontract plan is required to be submitted as part of this proposal submission.

The inclusion of the Clause FAR 52.219-9, Small Business Subcontracting Plan notes that the offeror shall submit and negotiate a subcontracting plan with at least a 5% small business goal. Submission of plan is due with by closing date of solicitation.

14. Does NAVOCEANO have a desired proposal format for the proposal submittal? Are there any page limits on the technical, cost or past performance? Is there a limit on the number of past performance contract references? Is there a specific font requirement? Regarding submittal, do we submit our proposal directly through NECO? Are hardcopies required?

Offeror is required to submit a copy of the solicitation filled out and signed by the closing date of the solicitation as noted in Blocks 8 and 28. No page limits on attachments to the offeror’s submission. Only 3 relevant past performance references are necessary. No specific font requirement is required. Submissions to the solicitation are required to be sent to the issuing office in Block 9. Hardcopies are not required; however, a signed copy must be provided.

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