Clarifications_to_the_Request_for_Proposal.docx

DOCX document 15 KB Posted

Attached to
Engineering Services
Solicitation number
FA825119R0017
Issued by

About this file

Clarification to the RFP

View the file

Other files

File Type Posted
Clarifications_to_the_RFP__2.docx DOCX document
FA825119R0017_______0002.pdf PDF
FA825119R0017_______0001.pdf PDF
PWS_update.docx DOCX document
CDRL.pdf PDF
PWS.docx DOCX document
FA825119R0017.pdf PDF
Pre_Solicitation.docx DOCX document

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

Clarifications to the Request for Proposal:

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.

1. Reference to a SOO in Section M of the RFP was an error and it has been corrected to reference PWS Yes, the reference to a SOO is in error and is referring to the PWS.

1. Paragraph 2 of section 5.3 in the PWS has been removed, AIMT support is not a requirement.

1. Physical work location will be at Hill AFB and/or the contractor’s facility. The bulk of the effort will be in support of Hill AFB. Support for the other 2 sites (Tinker and Robins) can be accomplished from Hill AFB or the local area. Travel funding is included to support Program Management Reviews and could be used as needed to support the other sites. The PWS has been modified to indicate a Common Access Card is required with at least a favorable NACI, a Secret clearance is not required.

1. PWS Section 5.1 modified: There are approximately 1000 NIIN’s in the Phase I list, All are in-process, approximately 2/3 are in the EO/JEDMICS publication process and 1/3 have completed the EO process and are in the TO update process.

1. Does PWS Section 5.1.2 represent the work of a third party contractor? Some of the actual registration in the DoD IUID registry of NIIN’s and marking data has been accomplished via a subcontractor. However, the support, integration, and process development should be accomplished by the prime contractor. Some registration was accomplished by the contractor. If it anticipated that a subcontractor would be used for registration, that effort should be included in the in the proposal.

1. PWS Section 5.1.3: Right now, there is not a lot of definition for this requirement. We have been marking parts in the AF depots for many years but the AF is in its infancy when it comes to utilizing the IUID marks to our advantage in the depot. There are a few cases where we use the IUID mark to induct a part into the process, record data about that part, or track the part through a set of processes. Expanding this utilization where practical with the goal to reduce process time, reduce data entry errors, or provide improved visibility of assets in the shop would be the desired outcome of this subtask. To date, minimal effort has been expended in this area.

1. 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.

1. Government computers and work space would be provided for at least part of the team. This equipment is not issued to the contractor so is not GFP/GFE, but rather put in place within the 748 SCMG for use by the contract team.

1. PWS Section 7.2 modified: Secret clearance is not required. A CAC card is required and at least a favorable NACI adjudication is required.

1. PWS section 10 modified: The period of performance for the base effort will be for 12 months for the base period and each option.

1. Phase I NIIN’s will be defined at time of award.

1. Does the 200 NIIN’s per month throughput estimate include NIINs that result in a determination of “not recommended for marking?” It includes the NIIN’s determined to be bypassed for various reasons.

1. A list of NIIN’s will be provided at the start of the contract.

1. No access to classified data will be required. The database/spreadsheet would be created by the contractor with input from the NMRW personnel.

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

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

1. The project schedule, quality assurance plan, table of contents and acronym list can be outside the 10 page limit.

1. The response SOW should cover the appropriate technical sections of the PWS but also indicate planned compliance with the other sections.

File details come from the government source that posted it.