Clarifications_to_the_RFP__2.docx

Clarifications to RFP #2

1. Response to Question 1, stated, “1. Since there is no milestones specified in the PWS, the project schedule can be removed. This is a level of effort type contract and we anticipate a monthly billing. The requirement for the production schedule has been removed from Section M of the RFP and will no longer be used as Evaluation Criteria.”

Question 1: Please confirm the effort is FFP and not FFP LH.

Response: This is a FFP contract with Travel and ODC being Cost Reimbursement.

2. We are unsure if there is a requirement to have a contractor facility in the vicinity. For example, PWS paragraph 7.1 states, “Work will be performed at both the Contractor facility and Government facilities.” How many office spaces can the government allocate for this effort? PWS Paragraph 7.1 states, “For work at a Government facility, the Government shall provide office space as required including office furniture, computers, telephones, etc.”

Question 2: Please confirm: 1) Is a contractor facility is required and 2) Provide appropriate limits for contractor office space availability at Government facilities.

Response: Currently we have desk space for 2 people on base, the Government has provided more space than that in the past but that is the current allocation. The contractor may request more spaces but additional spaces will be dependent on availability. The Government estimate for this effort is 4 – 5 FTE’s. Work performed beyond the on-base space will need to be at a contractor’s facility.

3. The PWS includes no milestones. As such, the preponderance of requirements have open-ended start and end dates. Worst case, everything starts on the same date and ends on the same date. By inspection, that is not likely but what is most likely or planned is not stated.

Question 3. Please provide sufficient detail in the PWS to bound separate work requirements over time such that a reasonable quantification of effort can be estimated.

Response: It is anticipated that this will be primarily a level of effort and with no project schedule, the hours bills will be roughly level loaded over the period of performance. Some variance may occur but it is not anticipated to be significant.

4. RFP - Pricing shall be submitted as a Microsoft Excel document and shall include the following:

A high-level pricing detail.

Back up documentation as applicable

Question 4. To ensure we provide clear and sufficient pricing data, we request that you elaborate on what is meant by “high-level” pricing detail.

Response: It is anticipated that this will be primarily a level of effort and with no project schedule, the hours bills will be roughly level loaded over the period of performance. Some variance may occur but it is not anticipated to be significant.

5. Solicitation PWS, paragraph 5.2 states the following:

5.2 Database Utilization

The contractor shall track all NIIN’s for Class IX status, IUID marking requirement, and thru the JEDMICS and TO publication processes.

The contractor shall manage, maintain, and update the IUID Program Management Database used for tracking all NIIN’s for Class IX status, IUID marking requirement, and thru the JEDMICS and TO publication processes.

The contractor shall manage, maintain and update the Marking Data Association Tool (MDAT) database. Train government personnel in the use and support of MDAT for maintaining marking data, syncing all marking machines to prevent the creation duplicate UII’s. Manage and support the transition away from EDCL as appropriate.

In response to Industry questions, the Government responses for # 8, #16 and #17 stated:

8. PWS Section 5.2: MDAT is not proprietary and is an Access database application. No training from the incumbent supplier would be provided. The source code would be made available.

16. This is primarily data entry. There may be minor software updates or bug fixes required.

17. The software code will be provided by the Government.

Discussion: We understand that the IUID Program Management Database and MDAT tools were developed under previous IUID support contracts and delivered to/and accepted by the Government and the associated hardware and software are not propriety. We further understand that “bug fixes” in the software and software updates may be required. To ensure we propose sufficient hours to address this requirement, we submit the following question regarding hardware and software documentation.

Question 5: In addition to the source code, please identify the tool documentation (e.g., design/interface specifications, product specifications, users manuals, etc.) that will be made available by the Government to the winning contractor for the IUID Program Management Database and the Marking Data Association Tools (MDAT) to ensure they can be managed, maintained, and updated as required by PWS paragraph 5.2 Response: No documentation, product specifications or users manuals exist or will be provided by the Government for MDAT or the Program Management Database.