sei 15 oct questions and responses.pdf

1. Reference: Section L‐1 Instructions to Offerors, Part II ‐ Technical Proposal, Subfactor 7: Small Business Subcontracting Plan. The instructions for the subcontracting plan include that the minimum content requirements of the plan are addressed in FAR 52.219‐9 and FAR 19.704. FAR 52.219‐9 and FAR 19.704 require the subcontracting plan include dollars planned to be subcontracted. As the instructions for the Technical Proposal also provide that cost or pricing data is not to be included in the technical proposal, can the Small Business Subcontracting Plan be submitted with an offeror’s Price Proposal?

Sec L‐1 has been updated to require offerors to submit their subcontracting plans as part of the Price proposal.

2. The latest RFP amendment and comments date 13 Oct 2009 changed 1.4.2.1.3.5 to 1.4.2.1.2.5 in section L‐1 and M002. 1.4.2.1.2.5 states :

The contractor shall ensure the RLCC is maintained and/or upgraded to meet mission requirements and provide a quality work environment. The contractor shall initiate all RLCC repairs and modification projects with 30 SW major service contracts. The contractor will submit and monitor service work requests to 30th Space Wing Civil Engineer Squadron (30 SW/CES). The contractor shall review and assess schematics and support equipment design documentation for compliance with RLCC requirements. The contractor shall provide escort and access to secured areas to complete authorized work and shall monitor through completion

It is unclear how this paragraph relates to Work load fluctuation, as opposed to normal staffing assessments. Please clarify.

Both in the 5 Oct 09 PWS and the 13 Oct 09 PWS (attached in the current amendment to the RFP) 1.4.2.1.2.5 reads as follows:

“The contractor shall perform SQL server database administration, database programming to prepare for launch operations, satellite and booster processing, and contingency/anomaly resolution.”

The workload surge for this effort is not considered frequent, but based on mitigating circumstances that may arise during mission‐assurance verification that requires the contractor to work beyond the normal duty hours. This may occur subject to launch verification or data programming which has a likelihood of occurring once or twice a year .