52.212-1 ADDENDUM - OFFER PREPARATION INSTRUCTIONS -.docx

52.212-1 Addendum Instructions to Offerors (ITO) MROi On-Site Functional Office Support (OSFOS)

52.212-1 ADDENDUM - OFFER PREPARATION INSTRUCTIONS

A. 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 sub factors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. The Offer shall consist of two (2) volumes:

1. Volume I - Technical Evaluation and Quality Control Plan

2. Volume II - Price Proposal

B. The contracting officer has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the contracting officer will review this determination and if, in the contracting officer’s opinion, adequate price competition exists no additional cost information will be requested. However, if at any time during this competition the contracting officer determines that adequate price competition no longer exists Offerors may be required to submit information other than cost or pricing data to support a determination of price reasonableness.

Table 1: Proposal Organization

· Subfactor One: Air Force (AF) Depot Maintenance Operations Experience

· Subfactor Two: System Implementation Experience

· Subfactor Three: Experience with AF Depot Systems

· Subfactor Four: Agile Development Experience

· Completeness

· Price Reasonableness

· Balance

· TEP Matrix

1. Page Limitations Individual page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Each page shall be counted except the following: blank pages, title pages, tables of contents, lists of tables and drawings, cross-reference matrices, and glossaries. If full Teaming arrangement agreements are provided, they can be added as an appendix to the Technical Volume 1, which will not count towards overall page limit.

2. Page Size and Format A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches, using at least 1-inch margins on the top and bottom and ¾-inch side margins. Except for the reproduced sections of the solicitation document, the text size shall be Times New Roman font and no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software.

Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to any official responses.

3. Tables, Charts, Graphs and Figures Organizations, systems and layout, implementation schedules, plans, etc. shall be depicted in tables, charts, graphs, or figures wherever practical. These items shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. Pages of this size may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than Times New Roman 10 point and searchable for text in Microsoft (MS) Office Word and/or PDF formats to the maximum practical extent. Ensure all tables, graphics, and figures in the electronic version of the proposal are incorporated into the proposal in a format that allows a word search by the host program (do not paste as pictures) to the maximum practical extent.

C. SPECIFIC INSTRUCTIONS:

1. VOLUME I - TECHNICAL EVALUATION – Limited to no more than thirty (30) pages. Submit one (1) electronic copy. Please describe your capability and experience relating to each section of the PWS. The proposal shall not simply restate or rephrase the Government’s requirement, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. An Offeror shall assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the proposal. The following technical sub factors will be evaluated in accordance with FAR 52.212-2 Addendum of the solicitation. Incomplete descriptions and copying words from the PWS are unacceptable.

a. Sub-factor 1: Air Force (AF) Depot Maintenance Operations Experience In support of PWS paragraph 3.5, the offeror must demonstrate by providing a clear understanding of AF Sustainment Center (AFSC) depot operations. Describe the business operations of an AF depot’s maintenance operations, to include financial accounting of those maintenance activities. The offeror must demonstrate clear and complete understanding of the entire hierarchical organizational structure of at least 3 different types of maintenance groups as listed in PWS paragraph 2. The offeror shall provide up to three examples of experience that detail roles, outcomes, and specific project involvement relative to depot operations.

b. Sub-factor 2: System Implementation Experience In support of paragraphs 3.3 and 3.8, the offeror must demonstrate a sound understanding of the process steps and critical activities required to replace an existing AF depot IT system with a new system that includes business process transformation, across multiple organizations. The offeror’s description must include steps from pre-replacement and preparation, through implementation, post implementation and ending with factors that must be monitored post-implementation. The offeror must describe specific system replacement experience within the past 5 years.

c. Sub-factor 3: Experience with AF Depot Information Technology (IT) Systems - In support of paragraphs 3.2 and 3.7, the offeror must demonstrate a detailed working knowledge of: at least one of the systems MROi is subsuming; and 3 of the systems MROi will interface (at least one 1 Maintenance System and 1 Financial System) that are listed in PWS Appendix B. The offeror must include specific information of the functions performed by the systems, the user base and detailed user roles, information exchanges with other systems, and the specific role the offeror performed relative to the systems, i.e., development, implementation, sustainment, support, help desk, project management. The offeror shall provide up to three examples of detailed experience supporting any of the systems listed in PWS appendix B.

d. Sub-factor 4: Agile Development Experience – In support of paragraphs 3.6 and 3.10, the offeror must demonstrate recent prior experience (within 3 years) supporting an Agile development program and ability to provide at least one person per each of the three ALCs with at least one year of Agile experience immediately upon contract award. The offeror must describe the specific agile roles fulfilled by their team.

2. VOLUME II - PRICE - Submit one (1) electronic copy.

a. Complete blocks 12, 17a, 30a, 30b, and 30c for the RFP Section A of the SF1449. In doing so, the offeror accedes to the contract terms and conditions as written in the SOLICITATION, with attachments. The SOLICITATION constitutes the model contract.

b. Offerors shall input into the TEP Worksheet, located in Section J Attachment - TEP Worksheet. The Total Evaluated Price (TEP) will be the sum of the proposed prices for all CLINs including the base and all options. The TEP will be used for evaluation purposes only and does not constitute the total contract price, however, all prices that comprise the TEP are contractually binding and thus all prices must be populated.

c. Submit a copy of the completed TEP worksheet in the Price Volume (Volume I) in Microsoft Excel (non PDF format). All cells of the TEP worksheet must be filled in. An omitted CLIN price/cell may result in an incomplete price submission.

d. Cost or Pricing Information Requirements - IAW FAR 15.402, 15.403-1(b) and 15.403-3(a), “information other than cost or pricing data” may be required to support price reasonableness. If, after receipt of proposals, the CO 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 CO determines that adequate competition no longer exists, then cost and pricing data may be required.

e. Rounding - All dollar amounts provided shall not extend beyond two decimal places.

f. The Data CLIN is to be left blank for all years. The Data CLINs are Not Separately Priced line items.

D. DOCUMENTS SUBMITTED IN RESPONSE TO THIS RFP MUST BE FULLY RESPONSIVE TO AND CONSISTENT WITH THE FOLLOWING:

1. Requirements of the solicitation (Item Numbers), PWS, government standards and regulations pertaining to the PWS.

2. Evaluation Factors for Award.

3. Any limitation on the number of proposal pages. Pages exceeding the page limitations set forth in this FAR Clause 52.212-1 addendum will not be read or evaluated, and will be removed from the proposal.

E. GENERAL INFORMATION

1. INFORMATION REGARDING SUBMISSION OF OFFERS:

Electronic submittal of offers is required. Email offers to Kevin Hutchison at kevin.hutchison.2@us.af.mil, phone 801-777-4449 and Jason Neering at jason.neering@us.af.mil 801-777-9296.

In addition to electronic submission, offerors may elect to mail copies of their proposal to the following:

AFSC OL:H/PZIMA

Kevin Hutchison 6038 Aspen Ave, Bldg 1289 Upstairs Hill AFB, UT 84056

(End of provision)