FA4452-08-R-0001-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

SEE CONTINUATION PAGES.

Point of Contact:

Matt Bow en 618-256-4233 matt.bow en@scott.af.mil

1. CONTRACT ID CODE PAGE OF PAGES

S 1 22

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 28-Aug-2008

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X FA4452-08-R-0001

X 9B. DATED (SEE ITEM 11)

31-Jul-2008

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

28-Aug-2008

CODE

HQ AMC/A7KQ

507 SYMINGTON DR, RM W202

SCOTT AFB IL 62225-5022

FA4452 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

FA4452-08-R-0001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

1. Section J, Attachment 1, Performance Work Statement (PWS), Exhibit A, Contract Data Requirements Lists (CDRLs), is updated to reflect a change in CDRL Data Item Number D002, Training Program Structure Document/ Training Plan (TPSD/TP). Data Item Number D002, page A-42, is replaced in its entirety to reflect change to Item

12. Draft submittal date in Item 12 is changed to be consistent with Section L, Table 1.2, Volume II submittal requirements. First sentence of Item 12 now reads “Draft TPSD/TP is due with submittal of technical proposal, Volume II—Mission Capability Volume.” No other changes are made to Attachment 1, PWS, or to Exhibit A, CDRLs.

2. Section L, L-100, INFORMATION TO OFFERORS (ITO) and INSTRUCTIONS FOR PROPOSAL PREPARATION, Table 1.2, ITO Paragraph Number 3.2.5, Transition Plan (Phase-In Plan). There are no page limitations for Transition Plan (Phase-In Plan).

3. Section M, M-100, EVALAUTION FACTORS FOR CONTRACT AWARD, TABLE 4—PAST PERFORMANCE RELEVANCY, is updated to include non-DoD Federal and State experience to be consistent with answers provided with Amendment 0001.

4. No other changes are addressed in this solicitation Amendment 0002. Amendment 0001 changes are highlighted in blue text. Amendment 0002 changes are highlighted in red text.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following has been modified:

SECTION L

L-100 INFORMATION TO OFFERORS (ITO) and INSTRUCTIONS FOR PROPOSAL PREPARATION

1.0 General Instructions:

1.0.1 This section of the ITO provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include all data and information requested by the ITO and must be submitted in accordance with these instructions. Any offeror who submits an incomplete package may be considered non-responsive. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS). Non-conformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation.

1.0.2 The proposal shall be clear, concise and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the offeror's proposal.

1.0.3 Elaborate brochures or documentation, binding, detailed artwork or other embellishments are unnecessary and not desired.

1.0.4 Addendum to Block 12 of SF 33 – The proposal acceptance period in Section A (front page) of the Request for Proposal (RFP). Due to the complexity of this acquisition, the Government requests that offerors’ proposals remain valid through 1 December 2008. The offeror shall make a clear statement in Section A (front page) of the proposal documentation volume that the proposal is valid until this date.

1.0.5 In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

1.1 General Information

1.1.1 Point of Contact: The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Block 7 of Section A (front page) of the RFP. Requests for clarification may also be sent to the CO at e-mail address in Block 10.c. of Section A (front page) of the RFP.

1.1.2 Debriefings: The CO will promptly notify offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with FAR 15.505. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506.

Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

1.1.3 Discrepancies: If an offeror believes the requirements in these instructions contain an error, omission or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

1.1.4 Electronic Reference Documents: All referenced documents for this solicitation are available on the Federal Business Opportunities (FBO) web site at http://www.fbo.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

1.1.5 Oral Presentation: Oral presentations will not be allowed.

1.1.6 Amendments to Solicitation: If this RFP is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this request by the date and time specified in the amendment(s).

1.1.7 Use of Non-Government Personnel in Source Selection:

a. It is the Government’s intent to utilize non-government advisors in the conduct of this source selection.

Offerors are advised that data, including proprietary data, submitted to the Government in response to this solicitation will be released to non-government advisors for review and analysis.

b. The non-government advisors whom will be involved in this source selection and the manner in which they will be involved are as follows:

MITRE Corporation: Employees of this firm will serve as advisors to the Source Selection Evaluation Team. These individuals possess irreplaceable technical knowledge, which is not readily available in the agency or another Federal agency. These advisors may be required to provide advice regarding proposal strengths and weaknesses but will not determine ratings or rankings of offerors’ proposals.

Company name and address of non-government advisors is:

MITRE Corporation 1662 Windham Way O’Fallon IL 62269

MITRE Corporation non-government advisors are as follows. All three are Federally Funded Research and Development Center (FFRDC) employees:

Mr. Mike Marek, FFRDC Mr. Ed Kera, FFRDC Mr. Jim Urscheler, FFRDC

c. Submission of offeror’s proposal in response to this request for proposal will constitute acceptance of non-governmental personnel participation as advisors in the source selection. If the offeror has any objection to non-government advisor access to its proposal information, the offeror shall provide grounds and justification for its objections to the contracting officer. The contracting officer will then make a determination whether the non-government advisor(s) shall be permitted to participate in the source selection. The contracting officer will inform the objecting offeror of the final determination, and, if the use of non-government advisors has been changed, will inform all offerors of the change.

d. Copies of non-governmental advisor agreements established between the companies listed above and the offeror are to be provided to the contracting officer. The companies listed above will not assist or participate in preparation or submission of any proposal associated with this acquisition. All representatives have signed nondisclosure forms.

1.2 Organization/Number of Copies/Page Limits

1.2.1 The title page of each volume must show:

(a) Solicitation Number

(b) Name, address and telephone and facsimile numbers of the offeror (and electronic (e-mail) address if available)

1.2.2 A Teaming Matrix (if applicable) shall be submitted with the Mission Capability - Volume II. The Teaming Matrix consists of the prime and other key firms, partners, subcontractors, etc., and includes the distribution of workload cross referenced by task.

1.2.3 The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1.2. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 1.2 - Proposal Organization:

Volume

ITO

Paragraph Number

Volume Title

Hard Copies/ Disk Copies

Page Limit

I 2.0 Executive Summary 6/2 10

1.2.1 Title Page (Not Included in 10 page limit) 1

2.2 Master Table of Contents Unlimited

II 3.0 Mission Capability 6/2 50

1.2.1 Title Page (Not included in 50 page limit) 1

1.2.2 Teaming Matrix (if applicable) (Not included in 50

page limit)

1.2.7 Table of Contents (Not included in 50 page limit) Unlimited

1.2.8 List of Tables and Figures (Not included in 50 page

limit) Unlimited

1.2.9 Glossary of Abbreviations and Acronyms (Not

included in 50 page limit)

Unlimited

3.2.3 Technical Approach

(Subfactor 1)

3.2.3.2 Draft Configuration Management Plan (Not included

in 50-page limit)

Unlimited

3.2.3.3 Draft Quality Plan (Not included in 50-page limit) Unlimited

3.2.3.4 Master Test Plan (Not included in 50-page limit) Unlimited

3.2.3.5 Training Plan (Not included in 50-page limit) Unlimited

3.2.4 Program Management Plan

(Subfactor 2)

3.2.4.1 Staffing Plan (Not included in 50-page limit) Unlimited

3.2.5 Transition Plan (Phase-In Plan)

(Not included in 50-page limit) (Subfactor 3)

Unlimited

3.2.6 Management of Subcontracting Plan

(Subfactor 4)

3.2.7 Technical Risk *

III 4.0 Past Performance 6/2 Unlimited

1.2.1 Title Page 1

1.2.7 Table of Contents Unlimited

1.2.8 List of Tables and Figures Unlimited

1.2.9 Glossary of Abbreviations and Acronyms Unlimited

4.1 Present/Past Performance Information Sheets (PPIS) **

4.1.1 Consent Letter Unlimited

4.1.1 Client Authorization Letters Unlimited

4.2 Present/Past Performance Questionnaire Log Unlimited

4.3.1 Relevant Contract Narrative 10

4.3.2 Roadmap (Organizational Change Structure History) 2

IV 5.0 Cost/Price 6/2 Unlimited

1.2.1 Title Page 1

1.2.7 Table of Contents Unlimited

1.2.8 List of Tables and Figures Unlimited

1.2.9 Glossary of Abbreviations and Acronyms Unlimited

5.1 General Instructions Unlimited

5.2 Volume Organization Unlimited

5.2, 5.3 Section 1 –Summary Description of Purchasing and

Accounting Systems; Summary of Estimating Methodology

Unlimited

5.1.3, 5.2 Section 2 – Cost and Pricing Information and Supporting Data

Unlimited

V 6.0 Contract Documentation 6/2 Unlimited

1.2.1 Title Page 1

1.2.7 Table of Contents Unlimited

1.2.8 List of Tables and Figures Unlimited

1.2.9 Glossary of Abbreviations and Acronyms Unlimited

1.2.6 Cross-Reference Matrix Unlimited

6.1 RFP (Sections A-J) Unlimited

6.1.6 Representations and Certifications (Section K) Unlimited 6.3.1-6.3.2 Contact Information Unlimited

6.3.3 Organizational Conflict of Interest (OCI)

Identification and Mitigation Plan Unlimited

*Counts towards 50-page Mission Capability Volume Limit **Request each PPIS not exceed a target of 8 pages, although more or less may be submitted if necessary and relevant to the AISS effort. Request each offeror submit up to 10 PPIS forms for the prime Contractor and up to 7 for each significant subcontractor/teaming partner. Only submit information on subcontractors and teaming partners performing key or critical portions of the AISS effort. There is no limit on the number of PPIS forms allowed per team; however, offerors are requested to limit responses to those efforts necessary for evaluation and relevant to the AISS effort.

1.2.4 Page Limitations: Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will be returned to the offeror as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, tabs, glossaries and those noted in the Proposed Organization Chart as unlimited.

1.2.5 Cost or Pricing Information: All cost or pricing information shall be addressed ONLY in the Cost/Price Proposal and Contract Documentation Volumes. Cost trade-off information, work-hour estimates and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

1.2.6 Cross Referencing: Cross-referencing between proposal volumes is not permitted. To the greatest extent possible, each volume shall be written so its contents may be evaluated with a minimum of cross-referencing within that volume. Information required for proposal evaluation not found in its designated volume will be assumed to have been omitted from the proposal.

The offeror shall provide a cross-reference matrix indicating the proposal reference information as it relates to the ITO, PWS and CLIN numbers contained in the RFP.

1.2.7 Indexing: Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections and will not count against page limitations.

1.2.8 Include an indexed list of Tables and Figures. This index will not count against page limitations.

1.2.9 Glossary of Abbreviations and Acronyms: Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

1.3 Page Size and Format:

1.3.1 A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 points. Tracking, kerning and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and 3/4 inch side margins.

Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

1.3.2 Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume and count as a single page. Foldout pages 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 8 point. These limitations shall apply to both electronic and hard copy proposals.

1.4 Binding and Labeling: Each volume of the proposal should be separately bound in a three-ring loose-leaf binder, which shall permit the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification and the offeror's name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data and 3.104-4, Disclosure, Protection and Marking of Contractor Bid or Proposal Information and Source Selection Information.

1.5 Electronic Offers: The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and electronic copy, the hard copy shall take precedence. For electronic copies, indicate on each Compact Disk (CD) / Digital Versatile Disc (DVD) the volume number and title.

Use separate files to permit rapid location of all portions, including subfactor required plans, exhibits, annexes and attachments, if any. The offeror shall submit volumes I through V in electronic format, using read only CDs/DVDs.

Each volume shall be on a separate CD/DVD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Word 2003, MS Excel 2003, MS Project 2003 and MS PowerPoint 2003 as applicable.

1.6 Distribution: The "original" proposal shall be identified. Proposals shall be addressed to the Contracting Officer and mailed or hand-delivered to:

Matthew R. Bowen Contracting Officer AMC Specialized Contracting Branch 507 Symington Drive Room W202

Scott AFB IL 62225-5022

2.0 Volume I - Executive Summary: In the executive summary volume, the offeror shall provide the following information:

2.1 Narrative Summary: A concise narrative summary of the entire proposal, including significant risks and a highlight of any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

2.2 Table of Contents: A master table of contents of the entire proposal

3.0 Volume II - Mission Capability Volume

3.1 General: The Mission Capability Volume should be specific and complete. Legibility, clarity and coherence are very important. Your responses will be evaluated against the Mission Capability subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. In arriving at a source selection decision, the Government reserves the right to give positive consideration for performance in excess of threshold requirements where the Government derives a benefit.

3.2 Format and Specific Content

3.2.1 Mission Capability: In the Mission Capability volume, address your proposed approach to meeting the requirements of each Mission Capability subfactor, as well as the risks in your proposed approach in terms of mission capability/performance and schedule.

3.2.2 Volume Organization: The Mission Capability volume shall be organized according to the following general outline:

Title Page Teaming List Attach 1 Table of Contents List of Table and Figures Glossary Subfactor One – Technical Approach Subfactor Two – Program Management Subfactor Three – Transition Plan Subfactor Four – Management of Subcontracting Plan

3.2.3 Subfactor One: Technical Approach: Offeror shall provide an integrated technical solution. The technical solution should represent the offeror's approach to meeting overall PWS requirements. Identify any best practices/innovations proposed. At a minimum, the technical approach must provide the following essential elements:

3.2.3.1 A sound plan for accomplishing the requirements as described in the PWS: Your plan shall provide a logical approach that ensures timely support and shall specifically address the following requirements in written form (with or without graphics):

3.2.3.1.1 Incorporation of the AMC’s global mobility mission operational and systems view to include its relationship to USTRANSCOM’s Distribution Process as it relates to PWS Para 2.1.

3.2.3.1.2 Process for assigning roles and responsibilities you will use to support the Missions Systems Office PWS Para 2.1.

3.2.3.1.3 Process for identifying, tracking and scheduling Mission Systems user requirements for all major tasks identified in the PWS.

3.2.3.1.4 Process used to analyze requirements and provide alternative solutions to include the communication process necessary to meet functional and performance requirements as defined in PWS Para 2.2.

3.2.3.1.5 Approach for providing effective 24/7 support as defined in PWS Para 2.2.4 and 2.3.

3.2.3.1.6 Approach for sustaining and maintaining the various Missions Systems infrastructure environments, to include maintenance, parts selection, and sparing approaches, as described in PWS Para 2.3.1.

3.2.3.2 Provide your draft Configuration Management Plan (CMP) described in B013 and PWS Para. 2.1.7 and provide an explanation of how you will manage multiple Mission Systems configuration baselines and potential fielding strategy to support worldwide deployments.

3.2.3.3 Provide your draft Quality Plan described in B012 and PWS Para. 2.1.8.

3.2.3.4 Demonstrate competence in the creation and execution of developmental and operational testing by providing a testing plan as described in the PWS Para. 2.4.2, C002, to include an explanation of your approach for conducting internal and external testing.

3.2.3.5 Demonstrate competence in the development and execution of training by providing a training plan as described in the PWS Para. 2.5.1, Data Item Number D002, to include an explanation of your approach for developing, managing, and conducting both classroom and computer-based training.

3.2.4 Subfactor Two: Program Management: Offeror shall provide an integrated Program Management Plan. The plan should represent the offeror's approach to overall program management of the AISS requirements. Identify any best practices/innovations proposed. At a minimum, the proposed plan must provide the following essential elements:

3.2.4.1 A staffing plan containing a personnel matrix which identifies the personnel resources to perform the requirements of the PWS. Your plan shall provide a logical approach that ensures timely support and shall specifically address the following requirements in written form (with or without graphics):

3.2.4.1.1 Process to recruit/retain/replace personnel who have the knowledge, experience, training, language ability, and technical expertise/certification/security clearances commensurate with the requirements of the PWS.

3.2.4.1.2 Identifies key positions and provides position descriptions which identify the educational and experience level and requisite security clearances of any individuals who will perform in a key position and other qualifications showing the key individual’s ability to comply with the minimum requirements of the PWS. Salaries and fringe benefits proposed for the professional employees who will work under the contract should be included in accordance with FAR 52.222-46, incorporated by reference.

3.2.4.2 Process to systematically provide for early identification of non-conforming supplies or services, metrics to track performance trends and the corrective actions required to insure timely and acceptable delivery/performance in accordance with the PWS.

3.2.5 Subfactor Three: Transition Plan (Phase-In): Offerors shall provide a plan for the transition of services that includes specific details of the timelines needed to meet all government requirements as detailed in the PWS. In addition, the proposed plan must provide the following transition plan requirements:

3.2.5.1 An explanation for start-up, mobilization, and transition depicting the chronological sequence of events which will be accomplished starting at Task Order award in order to meet all requirements of the PWS.

3.2.5.2 A listing of risks, their severity or probability and what actions you would take to mitigate those risks.

3.2.6 Subfactor Four: Management of Subcontracting Plan – The offeror shall submit the following:

3.2.6.1 Plan to manage subcontractors that are part of your proposed solution to meet government requirements.

Include in the plan the functional correlation matrix that links the requirements of the PWS to the subcontractor(s) performing that function and how small business utilization plan will be managed, implemented, and integrated appropriately so as to ensure successful performance of contract requirements.

3.2.6.2 Submit a Small Business Subcontracting Plan as required by FAR 52.219-9, incorporated by reference in this solicitation. The subcontracting plan shall contain how the offeror will meet the 20% small business subcontracting plan target.

A subcontracting plan is required as part of initial proposal submission from all offerors' other than small business concerns. Describe in your Small Business Subcontracting Plan commitment/targets for the participation of small, veteran-owned, service-disabled veteran owned, disadvantaged, HUBZone, and/or women-owned small businesses.

All offerors shall provide a Small Business utilization approach. Your approach must outline your process to manage, implement, and integrate the entire team to ensure successful performance of contract requirements with the end result of obtaining the small business subcontracting target of 20%. Describe the extent and nature of work to be performed by small business concerns, including the identification of specific small business concerns and the work to be performed.

3.2.7 Technical Risk: Provide the following documentation in Volume II, Mission Capability, as related to Mission Capability subfactors Technical Approach, Program Management, Transition Plan, and Management of Subcontracting Plan:

3.2.7.1 Identify any risks associated with implementation of Mission Capability requirements by subfactor. Identify how you intend to mitigate those risks.

3.2.7.2 Identify if the offeror, including subcontractors, core team members and, if applicable mentor/protégé and joint venture partners, have successfully used the proposed Mission Capability approaches. If not successfully used, describe how you intend to mitigate risks associated with implementation of those Mission Capability requirements.

4.0 Volume III - Past Performance

4.1 General: Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 2 to Section J. This information is required for the offeror and all key or significant subcontractors, teaming partners and/or joint venture partners proposed to perform the work outlined in the solicitation. Offerors are cautioned the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

4.1.1 The offeror shall submit, along with the information required in this paragraph, a consent letter (Attachment 3 to Section J), executed by each subcontractor, teaming partner and/or joint venture partner, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter (Attachment 4 to Section J), authorizing release to the Government of requested information on the offeror's performance.

4.2 Early Proposal Information: Each offeror is requested to submit the information shown in Attachment 2 for each relevant contract fifteen (15) calendar days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in offeror disqualification. As soon as practicable, offerors shall complete Section 1 of the attached Past Performance Questionnaire (Attachment 5 to Section J) and e-mail it and the Performance

Questionnaire Letter (Attachment 6 to Section J) to all points of contacts (POCs) the offeror has listed in the Past Performance Information Sheets (PPIS) (Attachment 2 to Section J). The POCs listed in the PPIS’s should represent the individuals most knowledgeable about the Offeror’s performance on the identified contract or program, such as the following: (1) Quality Assurance Personnel (QAP); (2) Program/Project Manager; (3) Contracting Officer. For commercial contracts, send the questionnaires to the commercial equivalents of these individuals. The POCs will complete the questionnaires and forward them by email or FAX, directly to the Source Selection Evaluation Team (SSET) to the Attention of Matt Bowen, email copies to Matt.Bowen@scott.af.mil or FAX copies to 618-256-5724.

RESPONDENTS TO THE QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION

SHEETS BACK TO THE OFFEROR! Offerors shall not follow-up with respondents to ensure they have completed the questionnaires. The SSET will conduct such follow-up with any POC as necessary. Offerors shall provide a Present/Past Performance Questionnaire Log indicating they have sent the questionnaires to the PPIS POCs for completion, and identifying who they sent them to and when.

4.3 Relevant Contracts: Submit information in accordance with Attachment 2 to Section J: Request you submit Past Performance Information for up to ten (10) contracts from the prime Contractor you consider most relevant in demonstrating your ability to perform the proposed effort. Also, request you include information for up to seven (7) contracts performed by each of your core team members and significant subcontractors you consider most relevant in demonstrating their ability to perform the proposed effort. Please only submit information on subcontractors and teaming partners performing key or critical portions of the AISS effort. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining performance confidence and relevancy, see Section M, provision 4.0 – “Evaluation Factors and Subfactors”, paragraphs 4.2.2.1 and 4.2.2.2 – Past Performance. For each PPIS, the offeror is requested not to exceed 8 pages, but may submit more or less if necessary for evaluation and relevance to the AISS effort. Offerors are again cautioned to include only information relevant to the AISS effort that is necessary for evaluation. Please note: for purposes of past performance evaluation, the managing partner of a joint venture will be considered the prime and the other partner(s) will be evaluated as teaming partner/subcontractor. For relevant efforts performed under delivery or task order contracts, the offeror shall include the specific order number(s). The Government may consider the offeror’s past performance in aggregate, rather than on an effort (contract) by effort basis.

4.3.1 Specific Content: Offerors are required to provide a relevant contract narrative explaining what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions, in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate. For example, the submittal of quality performance indicators or other management indicators to clearly support that an offeror has overcome past problems is required. Categorize the relevance information into the specific Mission Capability subfactors and Cost/Price factor used to evaluate the proposal.

Please note: In determining relevancy, the Government will consider the portion of the effort accomplished on previous/current contracts compared to the portion to be performed on the proposed effort by the same entity. For large, multi-function companies, limit the references to work done by the division, group or unit planning to perform the proposed work.

4.3.2 Organizational Structure Change History: Many companies have acquired, been acquired by or otherwise merged with other companies and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a “roadmap” describing all such changes in the organization of your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the offeror(s), your “roadmap” should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

This requirement only applies to prime Contractors.

5.0 Volume IV – Cost/Price Volume

5.1 General Instructions

5.1.1 Cost/Price Reasonableness: These instructions are to assist you in submitting information other than cost or pricing data that is required to evaluate the reasonableness of your proposed cost/price. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis the offeror does not understand the requirement or has made an unrealistic proposal.

Offers should be sufficiently detailed to demonstrate their price reasonableness. Proposed pricing should also support cost realism, balance and completeness. These areas will be further addressed in paragraph 5.1.3. Cost/Price Information and in Section M, 4.2.3. Cost (Price). The burden of proof for credibility of proposed costs/prices rests with the offeror.

5.1.2 Estimating Techniques and Methods: When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating techniques, including contemporary estimating methods to develop their estimates.

5.1.3 Cost/Price Information: Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All information relating to the proposed price including all required supporting documentation must be included in the section of the proposal designated as the Cost/Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

The offeror shall submit a total proposed price, calculated IAW paragraph 4.2.3, Cost (Price), of Section M 4.0 “Evaluation Factors and Subfactors”. For evaluation purposes, offerors shall assume the contract award date to be 15 Oct 2008. All provided pricing information shall be valid for the performance periods as stated in the RFP.

5.1.4 Cost or Pricing Information Requirements: In accordance with 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. Information shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit cost or pricing data.

5.1.5 Rounding: All total dollar amounts provided shall be rounded to the nearest dollar.

5.2 Volume Organization: The Cost/Price volume shall consist of the following sections:

SECTION 1 – Summary descriptions of estimating, purchasing and accounting systems; changes to estimating or accounting practices.

SECTION 2 – Cost or pricing information and supporting data including estimating methodology to support the reasonableness of the proposed CLIN prices. All significant assumptions (including indirect rates for the appropriate Contractor’s accounting period), scope limitations and/or qualifications of the cost proposal, shall be addressed and explained.

5.3 Estimating Methodology

5.3.1 Estimating System: Provide a detailed description of your estimating system or estimating methods used to support your proposal. Also, identify any deviations from the estimating system you are using to support the proposal and those you used to support proposals submitted to other government offices and commercial enterprises.

Include in your discussion, whether you have Government approval of your estimating system and if so, provide evidence of such approval. This information should be provided in Section 1 of Volume IV (Cost/Price).

5.3.2 Accounting System: Provide a brief description of the cost accounting method used to prepare your proposal, e.g., base to which indirect rates apply, etc. Include with your description any deviations from your accounting system you are using to support your proposal. Furthermore, provide a statement whether you have a Defense Contract Audit Agency approved accounting system and if so, provide evidence of such approval. If not, include a brief description for the reasons for not having a DCAA approved accounting system. This information should be provided in Section 1 of Volume IV (Cost/Price).

5.3.3 Purchasing System: Provide a summary description of your purchasing system or methods (e.g. how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). In instances of competitive bid vendor proposals, provide your approach in the evaluation of proposed pricing to ensure fair and reasonable prices in determination of award to subcontractors.

Also, identify any deviations from your standard procedures for preparing this proposal. Indicate whether you have Government approval of your system and if so, provide evidence of such approval. This information should be provided in Section 1 of Volume IV (Cost/Price).

Cost models. The Offeror shall submit an electronically encoded cost/price model in support of its proposed price.

Any cost/price model submitted shall be consistent with the Offeror’s approved estimating system and shall duplicate the logic and mathematical formula reflected in the paper copy of the proposal. Cost/price models submitted should normally comply with the following format requirements: Data file should be submitted on CD- ROM in .XLS file format, consistent with the instructions in this section.

6.0 Volume V – Contract Documentation

6.1 RFP/Representations and Certifications: The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror’s proposal shall include a signed copy of the RFP and Sections A through K.

6.1.1 Section A – Solicitation/Contract Form: Complete blocks 12, 13, 14, 15a, 15b, 16, (15c if applicable) and sign and date blocks 17 and 18 of the SF33. Signature by the offeror on the SF33 constitutes an offer, which the Government may accept. The “original” copy should be clearly marked under separate cover and should be provided without any punched holes.

6.1.2 Section B – Supplies or Services and Costs/Prices: Complete pricing information in Section B of the RFP.

Offerors must include unit and extended prices based on the quantities for each FFP CLIN listed, except Future Negotiated Task (FNT) CLINs X009, and provide not-to-exceed pricing for labor-hour CLINs X002. Failure to do so may be cause for rejection of the entire offer. The Government has inserted Not-to-Exceed (NTE) amounts for cost-reimbursable CLINs X006 and X007; offerors shall not change these NTE amounts. FNT CLINs X009 and X010 will remain unpriced and will be negotiated on an as needed basis.

Provide proposed labor categories and rates for base and option periods for all FFP and LH CLINs. FNT CLIN X009 and X010 will utilize this pricing schedule when negotiated on an as needed basis.

6.1.3 Section C – Descriptions and Specifications – Performance Work Statement – Exhibit A, Contract Data Requirements List, DD Forms 1423: Provide estimated price in Block 18 for each CDRL item, in accordance with DFARS 215.470(a). Data price estimates will not be used for contract pricing purposes without further analysis, per

DFARS PGI 215.470.

6.1.4 Section I – Contract Clauses

6.1.5 Section J— List of Documents, Exhibits and Other Attachments. As part of our past performance evaluation, the contractor is required to complete Attachment 2—Past Performance Information, Attachment 3—Consent Letter, Attachment 4—Client Authorization Letter, Attachment 5—Past Performance Questionnaire, and Attachment 6— Performance Questionnaire Letter.

6.1.6 Section K – Representations, Certifications and other Statements of Offerors: Complete representations, certifications, acknowledgments and statements. Offeror is required to fill out an online provision 52.204-8 Annual Representations and Certifications (Jan 2006), Online Representations and Certifications (ORCA) at http://orca.bpn.gov/

6.2 Exceptions to Solicitation Requirements: Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications and technical requirements, in addition to those identified as evaluation factors or subfactors. 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. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost and specific requirements of the solicitation. This information shall be provided in the format and content of Table 6.2.

Table 6.2 – Solicitation Exceptions

SOLICITATION

Document

Page/ Paragraph

Requirement/ Portion

Rationale

PWS, RFP, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

6.3 Other Information Required

6.3.1 Authorized Offeror Personnel: Provide the name, title and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually.

Identify those individuals authorized to negotiate with the Government.

6.3.2 Company/Division Address, Identifying Codes and Applicable Designations: Provide company/division’s street address, county and facility code; Commercial and Government Entity (CAGE) code; Data Universal Numbering System (DUNS) code; and size of business (large or small).

6.3.3 Organizational Conflict of Interest (OCI) Identification and Mitigation Plan (OIMP): At time of submitting technical proposal, offeror must either state affirmatively it has no OCI issues, or it must submit an OIMP, as described in PWS paragraph 8.2. If the award of this contract either creates or has the potential to create an actual or perceived OCI by the contractor, its employees, or subcontractors, the offeror shall submit an OIMP at the time of technical proposal. The Government-accepted OIMP shall be incorporated by reference into resultant contract.

6.3.4 Alternate Proposals: No alternate proposals will be accepted.

SECTION M - EVALUATION FACTORS FOR AWARD

The following has been modified:

SECTION M

M-100. EVALUATION FACTORS FOR CONTRACT AWARD

1.0 General

This is a full trade-off source selection conducted in accordance with Federal Acquisition Regulation (FAR) 15.3, Source Selection, as supplemented by the Defense Federal Acquisition Regulation Supplement (DFARS), and the Air Force Federal Acquisition Regulation Supplement (AFFARS) Mandatory Procedures (MP) 5315.3. The full trade-off source selection is referred to in this section as best value. The regulations governing best value source selection process are available electronically at the Air Force (AF) FARSite, http://farsite.hill.af.mil.

1.1 The Government reserves the right to -

1.1.1 Eliminate a proposal from the competitive range based upon:

a) An unrealistic cost or price;

b) Evidence that the offeror does not understand the requirement; and/or

c) Major technical or business deficiencies or omissions which initial or continuing discussions with the offeror could not reasonably be expected to cure.

1.1.2 Limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals (Reference clause , FAR 52.215-1, Instructions to Offerors – Competitive Acquisitions).

1.1.3 Award without discussions.

1.1.4 Make no award.

2.0 Basis For Award: A contract will be awarded to the offeror who, along with its proposal

2.1 Is determined responsible in accordance with the FAR, as supplemented.

2.2 Submits a proposal conforming to this solicitation’s requirements, which includes all stated terms, conditions, representations, certifications to include the information required in section L of this solicitation.

2.3 Is judged to meet or exceed the evaluation criteria discussed in this section and otherwise represents the best value to the Government. ( Best value to the Government is defined as trade-off between price and performance/solutions that provides the greatest overall benefit, when evaluated against specified selection criteria.)

The best value judgment may result in an award to an offeror who submitted a higher rated, higher priced proposal, where Source Selection Authority (SSA) determines that the technical…