DVSS_Questions_1.docx

DVSS QUESTIONS AND ANSWERS

1. The SOW (Paragraph 3.3, Page 30) states that the “Contractor shall be appraised at a CMMi maturity level three (3) or higher by a certified Software Engineering Institute (SEI) appraiser.” Would the Government find it acceptable for the Contractor to become certified at a CMMi Level III between the Proposal Submission Date and the Contract Award Date?

If any offeror cannot meet this requirement they would need to provide a plan that shows how they would successfully be appraised at CMMi maturity level 3. Plan would be evaluated with proposal.

2. As stated throughout the SOW and Attachment A, the DVSS solution must seamlessly interface to the DDGM Machinery Control System (MCS) and be “capable of being automatically launched by the Machinery Controls Software (MCS)” as stated in Attachment A, Paragraph 4.2.2.1, Page 19. It is not clear if the system would provide the MCS with a command interface, an API, and/or service. As only the incumbent would have the information needed to confirm this, will complete Machinery Control System (MCS) software documentation be provided by the Government prior to Proposal Submission Date to allow the Contractor the opportunity to adequately describe all requested interface design requirements?

Starting DVSS software must be transparent to the MCS console operator. “Automatically launched by MCS” means that the MCS console operator does not have to enter a user name and password or a server name or IP address or any other information to login to DVSS when it is launched on the MCS console. To meet this requirement the vendor would need to demonstrate that a batch file or other executable that can launch their DVSS software (both Multiviewer and Single Viewer) into the configuration required for the DVSS User. The launch file needs to include any switches or commands to start DVSS software and have it open into the correct configuration to meet all of the DVSS User requirements in the Performance Specification. The vendor should also look at paragraph 4.3 in the performance specification for software user access and password requirements as part of this requirement. The command lines in the demonstration file will then be integrated into the MCS software by the Government to automatically launch DVSS software on the MCS consoles when DVSS is selected by the console operator using the MCS software.

3. In the Level of Effort Table within the SOW (Page 2), the personnel hours are split evenly between on-site hours and contractor site hours. Can the Government please provide a rationale for this requirement in a design, fabricate, assemble, test, and delivery effort?

Hours would be at contractor site as much as possible; However some travel and service hours to LBES or a ship may be required if integration issues arise during testing and vendor support is required.

4. Within the SOW, when comparing the Engineering Services and Software Maintenance CLIN Ceilings (Page 2) to the Level of Effort Table (Page 2), the average man-hour rate is less than $50/hour. Is it the Government’s intent that the Level of Effort Hours equate to the Engineering Services and Software Maintenance CLIN Ceilings?

No, the LOE table is a reference of the maximum about of work that could be needed for each labor category but it is not the attention of the Government to exhaust all of the LOE hours during the life of the contract. It is not the intention of the Government to do pre-award cost analysis of the category totals just of the individual labor rates of those categories. So offerors only need to show how they came to the rate offered for each category.

The offeror is only required to bid any burden associated with the Not to Exceed CLIN’s. DO NOT try to back into the not to exceed amount use that amount as the base for any burden and fee you need to add.

5. The SOW (Paragraph 8.0, Page 62) states that all items to be provided under this contract shall conform to design, manufacturing, and performance requirements and be free from defects in material and workmanship for 2 years (24 months) from the date of installation. As the Contractor cannot control Government Installation Dates, should the warranty be for 2 years (24 months) from the date of delivery?

The Government wants the warranty to be from install if the units are held at the contractor facility. Delays are anticipated and addressed under the storage requirements. Under CLIN 0036 a Preservation and Preventative Maintenance Plan is required. The Government understands that once the Navy takes physical possession of the units the warranty is in effect.

6. The SOW (Paragraph L.3.2.1, Page 159) requests that detailed design information such as Mean Time between Failure (MTBF) and Mean Time to Repair (MTTR) be submitted with the Proposal. In most cases, this level of information will not be available until after design completion. With this in mind, is this truly a design, fabricate, assemble, test, and delivery effort, or a follow on to the current design?

The proposal shall include all of the Early Vendor Information (EVI) listed in the Statement of Work, Paragraph 2.1 as part of a proposed design for the system. As the bidder is selecting components for the proposed design they should also be looking at the MTBF data of the components to see if they meet the requirements in the performance specification. The proposed design should also take into account the MTTR requirements. The EVI paragraph does allow the bidder to explain how they determined the predicted MTBF and MTTR for the proposal. The data can come from service contracts, parts ordering data or another basis, such as a component’s data sheet.

Bidders should also take into account the requirements paragraphs 5.3.1 and 5.3.2 as well as what is required for CDRL A028 and A029 when developing the MTBF/MTTR data for their proposal.