GEARSS_Section_L_(V3)_-_20150319.docx

17 March 2015

L001 PROPOSAL PREPARATION INSTRUCTIONS

1 GENERAL INFORMATION

1.1 To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Failure to meet a requirement may result in an offer being ineligible for award. The response shall consist of the following volumes: Part I - Executive Summary/Contract Volume, Part II - Technical Volume; Part III - Price Volume. Proposals shall be delivered in hard copy and electronic form. The electronic version shall be 2010 Microsoft Office Suite compatible and delivered on a PC-compatible compact disk (CD) or digital video disk (DVD).

1.2 Rights in Data. TBD

1.3 Technical and Price proposals shall be submitted to the Government no later than 12:00 pm MST on TBD 2015.

L002 GENERAL INSTRUCTIONS

2.1 Point of Contact: The Procurement Contracting Officer (PCO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at the address located in Section A of the model contract/solicitation. Hand carried proposals shall be delivered to the PCO at 1050 E. Stewart Avenue, Building 2025, Peterson AFB, CO 80914.

2.2 Debriefing: The PCO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a pre-award or post-award debriefing in accordance with FAR 15.505 and 15.506.

2.3 Discrepancies: If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale as well as the remedies the Offeror is asking the PCO to consider as related to the omission or error.

2.4 Binding Requirements: The titles and contents of the volumes shall be as defined in Table 1, Volume Matrix. All shall be within the required page limits and with the number of copies as specified in Table 1. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders.

2.5 Complete blocks 12, 13, 15, 16, 17 and 18 of the RFP Section A, SF33. In doing so, the Offeror accedes to the contract terms and conditions as written in the RFP Sections A through K. These sections constitute the model contract. Include the model contract information in the Executive Summary. The proposal acceptance period is specified in Section A of the model contract/solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through the number of days annotated in Block 12, Section A.

2.6 Complete the necessary fill-ins and certifications in Sections I through K. Section K shall be returned in its entirety. For Sections C through I, the Offeror shall submit only those pages that require a fill-in.

2.7 Provide a copy of the letter from the Small Business Administration (SBA) showing proof of Section 8(a) status.

2.8 Format for proposal Parts II and III shall be as follows:

2.8.1 The proposals will be 8 1/2” x 11” paper except for fold-outs used for charts, tables, or diagrams, which may not exceed 11” x 17”.

2.8.2 A page is defined as one face of a sheet of paper containing information. Double sided pages will be counted as two pages.

2.8.3 Typing for the proposal body text shall be Times New Roman or Arial and shall not be less than 12 point font. Line spacing shall be at least 1.5 line spaced. Text in tables, diagrams and other graphics shall be no smaller than 8 point font to ensure legibility without external optical aid (i.e., magnifiers).

2.8.4 Elaborate formats, bindings or color presentations are not desired or required.

2.8.5 Documents submitted in response to this RFP must be fully responsive to and consistent with the following:

2.8.5.1 Requirements of the RFP.

2.8.5.2 Evaluation Factors for Award in Section M of this RFP.

2.8.5.3 Page Limitations. Page limitations shall be treated as maximums. Pages exceeding the page limitations set forth in this Section L will not be read or evaluated, and will be removed from the proposal. Each page shall be counted except the following: Cover pages, tables of contents, tabs, glossaries, and items listed in Table 1 as "unlimited."

2.8.5.4 Proposals must be legible and written in the English language.

2.9 No classified information shall be included in Offeror’s proposal.

2.10 A Bidder’s Library is available on FedBizOpps for Offeror’s reference and use in proposal development. Offerors can call (719) 556-0643 or (719) 556-2855 for access.

I EXECUTIVE SUMMARY/

CONTRACTS VOLUME

No Limit for Contracts Volume (Sections A-K)

TECHNICAL VOLUME ATTACHMENTS

III PRICE VOLUME

Table 1. Volume Matrix (VM)

2.11 For Rights in Data, the Offeror shall: TBD

3 SPECIFIC INSTRUCTIONS

3.0 PART I – EXECUTIVE SUMMARY/CONTRACTS VOLUME

Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.1 PART II – TECHNICAL VOLUME

Within each subfactor, address Technical Risk associated with your proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Provide rationale for each risk and its impact on cost, schedule, and performance. Propose realistic mitigations for identified risks that will eliminate or reduce risk to an acceptable level.

3.1.1 Subfactor 1: Phase-In. The Offeror shall provide a single integrated phase-in plan with schedule milestones. The plan shall include placement of personnel at all site locations with specific deployment, badging, training, security and travel requirements defined.

3.1.1.1 Provide a Phase-In Staffing Plan that describes the specific steps or methodology the Offeror proposes to use to meet program phase-in milestones IAW PWS 3.5.2. Reference the information provided in Subfactor 2 rather than repeating it; Subfactor 1 is only evaluating Offerors ability to staff critical positions during the Phase-In period; the Offeror's basic understanding of the skills and experience necessary to perform the PWS on an ongoing basis will be evaluated under Subfactor 2.

3.1.2 Subfactor 2: Critical Staffing. The Offeror shall:

3.1.2.1 Provide the job requisitions for the technical and management staff the Offeror proposes to perform specified PWS tasks 3.2.1, 3.3.1, 3.3.3, 3.3.5, 3.3.10, 3.3.12, 3.4.1, 3.4.2, 3.4.3 and 3.4.8.

3.1.2.2 Provide clear evidence (hiring procedures, retention statistics, contingency offers to potential employees, etc.) that demonstrates the Offeror has the ability to obtain the proposed staff to accomplish the skills required to perform all the tasks in the PWS.

3.1.2.3 Provide a matrix or table that identifies an overall staffing approach to include skill mix with hours for tasks in paragraph 2 and each task of paragraph 3 (3.1.1, 3.1.2, etc.) of the PWS. Additionally, the contractor shall provide a total for each high level objective of paragraph 3 (3.1, 3.2, etc.) of the PWS. Provide this staffing approach with hours for the base year and each option year for the duration of the contract.

3.1.3 Subfactor 3: Technical Process Approach. The Offeror shall:

3.1.3.1 Describe the performance required day-to-day of the PWS high level objectives 3.2, 3.3 and 3.4 that demonstrate a clear understanding of the technical and operational environment.

3.1.3.2 TBD (Data Rights)

3.3 PART III – PRICE VOLUME

3.3.1 Pricing Information Requirements – In accordance with FAR 15.402, 15.403-1(b) and 15.403-3(a), “data other than cost or pricing data” may be required to support price reasonableness. If, after receipt of proposals, the PCO determines that there is insufficient information available to determine the reasonableness of the proposed pricing the Offeror shall be required to submit additional information other than cost or pricing data. If, during the source selection process, the PCO determines that adequate competition no longer exists, then pricing data may be required.

3.3.2 Pricing Assumptions - Summarize all significant pricing assumptions, scope limitations and/or qualifications of the Price proposal. The Offerors’ proposal shall be valid for 180 days after the date of submittal.

3.3.3 Estimating Techniques and Methods - When responding to the Price Volume requirements in the solicitation, the Offeror may use any generally accepted estimating technique to develop their proposal. Provide proof of and a summary description of your standard estimating system, accounting system or methods.

3.3.4 Pricing Summary – The Offeror shall fill out Section B and Table 2, GEARSS Proposed Pricing.

(CY 16

Base)

CLIN 0002

(CY 16 ODC)

CLIN 1001

(CY 17 OPT)

CLIN 1002

(CY 17 ODC)

CLIN 2001

(CY 18 OPT)

CLIN 2002

(CY 18 ODC)

CLIN 3001

(CY 19 OPT)

CLIN 3002

(CY 19 ODC)

Total Estimated Price

Table 2. GEARSS Proposed Pricing

3.3.6 Other Requirements. Contractor shall provide the cognizant Defense Contracting Audit Agency (DCAA) auditor and Defense Contract Management Agency (DCMA) Administrative Contracting Officer (ACO) points of contact including, name, address phone number and e-mail address.

Page 1 of 6 Section L: FA8823-15-R-0001