FA8217-10-R-5022 0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE Page 1

2. AMENDMENT/MODIFICATION NO.

FA8217-10-R-5022-0002

3. EFFECTIVE DATE

10 DEC 2010

4. REQUISITION/PURCHASE REQ. NO.

FD20201076474

5. PROJECT NO (If applicable)

6. ISSUED BY CODE

DEPARTMENT OF THE AIR FORCE, DIRECTORATE OF CONTRACTING

OO ALC GHSK SPACE 3CI

6049 WARDLEIGH RD BLDG 1207

HILL AIR FORCE BASE UT 84056-5838

BUYER: Blake B. Gibson blake.gibson@hill.af.mil Phone: (801) 586- 3465 Fax: (801) 586-1287 No Collect Calls

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

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

CODE

X

9A. AMENDMENT OF SOLICITATION NO.

FA821710R5022

9B. DATED (SEE ITEM 11)

5-NOV-2010

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended. Offers 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 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 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 1 copies to the issuing office.

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

ROUTINE

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

15B. CONTRACTOR/OFFEROR

BY ________________________________________________________

(Signature of person authorized to sign)

15C. DATE SIGNED

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

16B. UNITED STATES OF AMERICA

BY ____________________________________________________

(Signature of Contracting Officer)

16C. DATE SIGNED

FACILITY CODE

NSN 7540-01-152-8070

PREVIOUS EDITION UNUSABLE

30-105 STANDARD FORM 30 (REV. 10-83)

PRESCRIBED BY GSA

FAR (48 CFR) 53.243

X

X X

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.

Amendment/Modification FA8217-10-R-5022-0002

Continuation of block 14. DESCRIPTION OF AMENDMENT/MODIFICATION

THE PURPOSE OF THIS AMENDMENT IS TO:

1) REVISE AND REPLACE THE CONTRACTOR DATA REQUIREMENTS LIST AS FOLOWS:

FROM: 7 OCT 2010, 16 PGS TO: 7 OCT 2010/8 DEC 2010, 17 PGS

2) REVISE AND REPLACE THE PERFORMANCE WORK STATEMENT AS FOLLOWS:

FROM: 5 NOV 2010 TO: 29 NOV 2010

3)REVISE AND REPLACE THE PRICING TABLE AS FOLLOWS:

FROM: 5 NOV 2010 TO: 29 NOV 2010

4) REVISE AND REPLACE SECTION TITLED "INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR PROPOSAL PREPARATION" IN SECTION L, INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR

RESPONDENTS AS SHOWN BELOW

ALL OTHER TERMS AND CONDITIONS IN SECTION L REMAIN UNCHANGED

5) REVISE AND REPLACE SECTION L ATTACMENTS AS FOLLOWS:

FROM: UNDATED TO: 29 NOV 2010

Request for Proposal FA8217-10-R-5022-0002

PART III - LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACHMENTS

SECTION J

LIST OF ATTACHMENTS

Form Number Description/File Name Date Number of Pages Contract Data Requirements List Mult Date 17

Performance Work Statement 29NOV2010 50

PWS Solicitation Cross Reference Matrix UNDATED 1

Pricing Table 29NOV2010 58

Staffing Table 05NOV2010 48

Government Furnished Property 07OCT2010 15

Section L Attachments 29NOV2010 14

DD 254 Contract Security Classification Specification UNDATED 22

Appendix "C" Safety, Fire Protection and Health Specification

16SEP2010 3

PART IV - REPRESENTATIONS AND INSTRUCTIONS

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

L-III - INFORMATION TO OFFERORS (ITO)

and INSTRUCTIONS FOR PROPOSAL PREPARATION

1.0 Program Structure and Objectives

The purpose of the Mission Planning Support Contract is to provide support for mission planning systems to CONUS / OCONUS operational units and some FMS customers. The support includes the analysis of deficiency reports, identification and analysis of degraded reliability or supportability trends, providing configuration management and control, drafting and publishing of technical documentation, system checkout, fielding, supply, maintenance and repair, training support, customer assistance visits, 24-hour/7 day-a-week assistance, international support and training, combined test force support, integrated database management, deployment and management of the MPS System Support Representatives (SSRs) at worldwide locations, transition to follow-on systems and support of all wing / unit-level planning requirements and related efforts, through source selection procedures IAW Air Force Acquisition Regulation Supplement (AFFARS) Part 15.3. This contract will include a five (5) year ordering period, six (6) year period of performance, and a six (6) month option to extend services, Firm Fixed Price (FFP), Indefinite Delivery, Indefinite Quantity (IDIQ) contract.

2.0 General Instructions

(a) 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. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

(b) 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 that 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.

(c) Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

(d) 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 this date. Mission Planning Support Section L Page 2

(e) 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.

2.1 General Information

2.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 Mr. Blake Gibson at 6029 Wardleigh Rd, Bldg 1207 Hill AFB, UT 84056-5838 or via e-mail to the following: Blake.Gibson@hill.af.mil.

2.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. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. 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 a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.1.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 CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

2.1.4 Electronic Reference Documents

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

2.1.5 Communications

Exchanges of source selection information between Government and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Otherwise, source selection information will be transmitted via postal service.

2.1.6 Oral Presentations – Oral presentations will not be allowed.

2.2 Organization/Number of Copies/Page Limits

The offeror shall prepare one proposal as set forth in the Proposal Organization Table (Table 2.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 2.2. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 2.2 - Proposal Organization

VOLUME ITO Paragraph Number

VOLUME TITLE PAGE LIMIT NUMBER

OF HARD

COPIES

NUMBER

OF SOFT

COPIES

I 3.0 Executive Summary - 4 2 I 3.1 Narrative Summary 3 4 2 I 3.2 Table of Contents Unlimited 4 2 II 4.0 Technical 150** 4 2 III 5.0 Relevant Past Performance 7/contract*;

max of 21 contracts

4 2

III 5.3.7 Company “Roadmap” 3 4 2 III 5.3 Subcontractor Consent

Letters Unlimited 4 2

III 5.3 Client Authorization Letters

Unlimited 4 2

IV 6.0 Price Unlimited 4 2 V 7.0 Contract Documentation Unlimited 4 2

*See Past Performance Information Sheet (PPIS) Instructions, Paragraph 5.3 **The following portions of Volume II, Technical Proposal, are excluded from the page count:

Definitions and Abbreviations, and PWS Solicitation Cross-Reference Matrix.

2.2.1 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 excess paper copies will be returned to the offeror as soon as practicable. Each page shall be counted except the following: cover sheets (not to be confused with the Narrative Summary), Tables of Content, title pages, glossary of abbreviations, acronym lists, blank pages, and tabbed dividers. Each volume shall conform to the numbering, page count, and quantity of copies shown in Table 2.2 above. Page limitations will 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.

2.2.1.1 Page Size and Format

(a) 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 white bond paper written in Times New Roman font. Except for the reproduced sections of the solicitation document, the text size shall be no less than 11 point. 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 ¾-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to both hard and soft copies as well as responses to ENs.

(b) 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 x 17 inches in size. Foldout pages shall fold entirely within the volume, and any hole punches shall not interfere with / delete information. 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 10 point. These page format restrictions shall apply to both hard and soft copies as well as responses to ENs.

2.2.2 Pricing Information

All pricing information shall be addressed ONLY in the 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 trade-off decisions.

2.2.3 Classified Information

No classified proposals shall be submitted.

2.2.4 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The offeror shall fill out the PWS Solicitation Cross Reference Matrix as Attachment L-1 of this ITO indicating the proposal reference information as it relates to the ITO, PWS, CLIN numbers, and CDRL references found therein.

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

2.2.6 Glossary of Abbreviations and Acronyms

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

2.2.7 Binding and Labeling

Each volume of the proposal shall be separately bound in a three-ring, loose leaf binder permitting 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 shall 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 FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.3 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The offeror shall submit volumes I through V in electronic format, using recordable CDs. Each volume shall be in a different directory on a CD. 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) Office Word 2007, MS Office Excel 2007, MS Office Project 2007, and MS Office Power Point 2007, as applicable. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

2.3.1 Electronic File Names

For electronic submissions, the file naming convention for the proposal volumes is as follows. You may expand on these file names as appropriate; just provide a list of the content of each.

Volume File Name

Executive Summary company name execsum.xxx Technical Proposal company name techprop.xxx Past Performance company name pastperf.xxx Price Volume company name price.xxx Contract Documentation company name contv.xxx

NOTE: .xxx = appropriate default file extension for document type (e.g. .doc for MS Word, .xls for MS Excel, etc.)

2.4 Hyperlink

The Table of Contents of all proposal volumes shall be hyperlinked to the corresponding material within each proposal volume such that “clicking” the mouse on an item in the Table of Contents will take the reader to the corresponding section within the body of the proposal volume. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above. In addition, any reference within the body of the proposal volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above. Hyper-linking references between different filenames are not necessary. Volume 3 does not need to be hyperlinked if it is impractical to do so.

Individual documents within Volume 3 should be hyperlinked within each document to the extent practicable.

2.5 Distribution

The original proposal shall be identified. Proposals shall be addressed to the Contracting Officer and mailed or hand carried to:

OO-ALC/GHSKB

Attn: Mr. Blake Gibson 6029 Wardleigh Rd, Bldg 1207 Hill AFB, UT 84056-5838

Any proposal pertaining to this contract is "For Official Use Only" and "Source Selection Information--See FAR 2.101 and FAR 3.104".

2.6 Proposal Inquiries

All inquiries must be submitted via e-mail to the Contracting Officer, Mr. Blake Gibson at blake.gibson@hill.af.mil. Questions will be answered and posted to FedBizOps as quickly as possible during the proposal preparation period.

3.0 VOLUME I - EXECUTIVE SUMMARY

In the Executive Summary Volume, the offeror shall provide the following information:

3.1 Narrative Summary

Provide a concise narrative summary of the entire proposal to include addressing significant risks, and highlighting key or unique features, excluding 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.

3.2 Table of Contents

Include a master table of contents for the entire proposal.

4.0 VOLUME II - TECHNICAL PROPOSAL

4.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. There will be no reference to rates or price in this volume. Offerors shall assume that the Government has no prior knowledge of their certifications, facilities and/or capabilities, and will base its evaluation on the information presented in the offeror’s proposal. Your responses will be evaluated against the Technical 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 that 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.

4.2 Format and Specific Content

4.2.1 Technical

In the Technical volume, address your proposed approach to meeting the minimum performance or capability requirements of each technical subfactor.

4.2.2 Volume Organization

The Technical Volume shall be organized according to the following general outline:

(1) Table of Contents

(2) List of Tables and Drawings

(3) Glossary

(4) PWS Solicitation Cross Reference Matrix

(5) Technical Proposal (Subfactors)

4.2.3 Subfactor One: Program Management

Offeror shall provide an approach for Program Management. At a minimum, the proposed approach shall thoroughly substantiate all of the following:

(1) Human Resources Plan – Identify processes for recruiting, hiring, training, and staffing. The recruiting and hiring plan(s) shall demonstrate the offeror’s ability to hire personnel to fill vacancies within 45 calendar days, with a goal of less than 20 calendar days, and include a top-level compensation plan for all employees. A vacancy is considered filled when personnel are successfully recruited, hired and begin training. Furthermore, the plan shall outline the offeror’s process for temporarily filling vacancies (short or long term) in accordance with PWS 2.1.2.2.8. Training plans shall demonstrate to the government the offeror’s ability to train personnel on applicable position specific duties. The staffing plan, using the Staffing Table in Attachment L-8, shall identify how the offeror proposes to organize and staff all positions to fulfill all requirements in the PWS.

(2) Organizational Conflict of Interest (OCI) Plan – If applicable, provide an OCI plan that demonstrates to the government the offeror’s resolution method for known OCI issues. OCIs shall be classified as either Impaired Objectivity, Unequal Access to Information, or Biased Ground Rules. Identify whether the OCI can be mitigated and which resolution method will be used. Resolution methods may include, but are not limited to, mitigation plans (firewalls or Non-Disclosure Agreements (NDAs)) or limitations on future contracting. Firewalls/NDAs are not considered effective for resolving “biased ground rules” or “impaired objectivity” OCIs.

(3) Information Assurance (IA) Plan – The IA plan shall demonstrate to the government the offeror’s ability to provide and maintain certifications IAW DoD 8570.01-M, Change 2, Apr 2010, and the PWS 2.1.4.6.

(4) Transition Plan – The transition plan shall demonstrate to the government the offeror’s strategy to transition all activities, as required by the contract, from the incumbent to the awardee. At a minimum, the transition plan shall address: transition of Mission Planning Central (MPC) operations and Government Furnished Equipment (GFE) from its current location to a secure facility, with no more than 24 hours of MPC downtime; transition of personnel, if applicable, with no more than ten (10) calendar day gaps in coverage.

(5) Security Clearance Plan – The security clearance plan shall demonstrate to the government the offeror’s practices and procedures for attaining and maintaining required security clearances for personnel and facilities IAW applicable DoD and USAF directives and instructions.

4.2.4 Subfactor Two: Support for Mission Planning System Support Facility

Offeror shall provide an approach for support for Mission Planning System Support Facility. At a minimum, the proposed approach shall thoroughly substantiate all of the following:

(1) Mission Planning Central (MPC) Support Plan - The MPC Support Plan shall demonstrate to the government the offeror’s proposed approach to support and maintain MPC operations IAW PWS 2.1.2.4.1.

At a minimum, this plan shall include the maintenance of the existing functionality, establishment of an Integrated Product Team (IPT) to manage Change Enhancement Requests (CERs), develop new MPC capabilities, provide system security (physical and software), and provide MPC training to users, developers, testers, and program managers. In addition, the offeror shall propose an approach to maintain and advance the existing classified Mission Planning System Support Facility (MPSSF) website.

(2) Deficiency Investigation Process Plan – The Deficiency Investigation Process Plan shall demonstrate to the government the offeror’s proposed approach to identify MPE deficiencies and manage the process IAW T.O. 00-35D-54 and the PWS 2.1.2.1.1(c). At a minimum, the plan shall address the specific processes and personnel used to identify potential deficiencies, report deficiencies to the appropriate government personnel within 24 hours for Category I and 48 hours for Category II deficiencies, process / tool for tracking the status of the reported problem to closure, and performance of Screening Point duties IAW the PWS.

(3) Operational User and SSR Training Plan – The operational user and SSR training plan shall demonstrate to the government the offeror’s proposed approach for developing and delivering training plans for existing and new MPEs to applicable operational users and SSRs (PWS 2.1.2.1.3). At a minimum, the plan shall address the Mission Planning Training (MPT) involvement throughout the MPE development process and the delivery of the training in conjunction with, or prior to, the fielding of a new

MPE.

(4) Fielding Events Plan – IAW PWS 2.1.2.1.4.3 the fielding events plan shall demonstrate to the government the offeror’s proposed approach for developing fielding schedules for new MPEs and the team members required to conduct a fielding event. At a minimum, the plan shall address: how the offeror determines what priority will be given to the receiving operational units, to include consideration for unit deployments and timing for weapon systems mission planning upgrades; the proposed team members for a fielding team.

4.2.5 Subfactor Three: System Support Representatives (SSRs)

Offeror shall provide an approach for SSRs. At a minimum, the proposed approach shall thoroughly substantiate all of the following:

(1) Worldwide Support Plan – The worldwide support plan shall demonstrate to the government the offeror’s proposed approach for supporting a minimum of 145 geographically separated locations. At a minimum, the plan shall address the offeror’s approach for ensuring SSRs at each location are performing duties, as required by the PWS 2.1.2.2, and how vacancies greater than 10 calendar days, whether short or long term, will be filled by personnel with all of the required security clearances and IA certifications for the position IAW PWS 2.1.2.2.8.

(2) Support Plan for Deployed Units – The support plan for deployed units shall demonstrate to the government the offeror’s proposed approach for supporting activities required prior to, and during, a unit’s deployment. At a minimum, the plan shall include a proposed approach for “building” MPEs that will be taken by the unit during the deployment, updating systems while they are deployed (to include the use of organic government personnel or the offeror’s personnel, if authorized by the government), and how the unit can begin getting user support for mission planning within two (2) hours of initial contact, if the SSR is not deployed with the unit IAW PWS 2.1.2.2.1(j) and 2.1.2.2.2(k). User support may include, but is not limited to, contacting a Subject Matter Expert (SME) in the MPSSF.

(3) Mission Planning Environment (MPE) Configuration Control Plan – The MPE configuration control plan shall demonstrate to the government the offeror’s proposed approach to maintain configuration control for all fielded and certified MPEs. At a minimum, the plan shall address: the communication between the MPSSF Configuration Management (CM) team, SMEs, and SSRs; use of MPE Letters and MAJCOM Certification Letters to ensure MPEs are functional and related systems remain interoperable; SSRs implementation and maintenance procedures and practices for loading new or updated mission planning data (i.e. charts, mapping updates and aeronautical information).

(4) Support Plan for Operational Test – The support plan for operational test shall demonstrate to the government the offeror’s proposed approach for SSR participation in operational test events IAW PWS 2.1.2.2.1(n). At a minimum, the plan shall address how the SSR will be trained on the systems administration for the new MPE prior to the test event.

5.0 VOLUME III – RELEVANT PAST PERFORMANCE INFORMATION

5.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 L-2. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, the offeror shall submit a Consent Letter (Attachment L-5) 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 L-6), authorizing release to the Government of requested information on the offeror's performance.

5.2 Early Proposal Information

Each offeror is required to submit the information shown in the Past Performance Volume, for each relevant contract, 15 calendar days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in offeror disqualification. However, late submittal of the Past Performance Volume after the date set for receipt of proposals will result in offeror disqualification per the late proposal rule.

5.3 Relevant Contracts

The Offeror shall submit Past Performance Information Sheets (PPIS), Attachment L-2, on three

(3) relevant contracts for the prime offeror and up to three (3) for each key partner and / or each subcontractor for Federal agencies and commercial customers with specific guidance below, for a maximum of 21 contracts:

(1) A key partner or subcontractor is defined by the government to be a company whose performance on this contract will be greater than or equal to 15 percent but less than 50 percent, by total contract value.

(2) List of Offeror’s relevant contracts in the past five (5) years

(3) Consent Letters executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing the release of past performance information so the offeror can respond to such information. Section L, Attachment L-5 is a sample consent letter.

(4) Client Authorization Letters (Attachment L-6) for each identified effort for a commercial customer authorizing release to the Government of requested information on the offeror’s performance.

5.3.1 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This shall 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, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required.

Categorize the relevant information into the specific Technical Subfactors and Price Factor used to evaluate the proposal.

5.3.2 Workload Sharing

Offeror shall submit workload sharing percentages, based on cost, for the total contract and each subfactor defined in Section L, paragraphs 4.2.3, 4.2.4, and 4.2.5. This information shall be provided in the format and content of Tables 5.3.2.1 and 5.3.2.2. Note: Percentages listed in Table 5.3.2.1 and 5.3.2.2 are for illustrative purposes only and should not be construed as suggested or required.

Table 5.3.2.1 – Total Contract Workload Sharing

Contract Percent Performed by

Prime Percent Performed by

Subcontractor(s) Short Description

Mission Planning Support Contract II

51% - Company X 17% - Company Y 32% - Company Z

Describe what requirement will be performed by the subcontractor(s)

Table 5.3.2.2 – Workload Sharing by Subfactor

Technical Subfactor Percent Performed by

Prime Percent Performed by

Subcontractor Short Description

Program Management 90% - Company X 10% - Company Y Describe what requirement will be performed by the subcontractor(s)

Support for MPSSF 20% - Company X 80% - Company Z See note above.

SSRs 80% - Company X 15% - Company Y 5% - Company Z

See note above.

5.3.3 Past Performance Information Sheets (PPIS)

The PPIS (Section L, Attachment L-2) will be used to submit information on no more than three (3) of the most relevant contracts performed by the prime offeror, up to three (3) for each key partner and / or each subcontractor for Federal agencies and commercial customers during the five (5) years prior to the date of issuance of this solicitation. Limit each PPIS to seven (7) pages, with a maximum of 21 contracts. Submit four (4) hard copies, and two (2) digital copies. Only references for same or similar type contracts are desired.

The offeror has discretion in determining the most beneficial mix and quantity of contracts by prime offeror, key partners or subcontractors covering as many of these elements as is practical.

If the customer for any PPIS is a potential offeror (or critical subcontractor) for this solicitation, the offeror shall provide the POCs for the next higher level customer. Example, if Contractors X and Y are both potential offerors for this solicitation and Contractor X was a subcontractor to Contractor Y on workload performed for the government, then Contractor X shall provide both Contractor Y and the government POCs for each applicable PPIS.

The evaluation of past performance information will take into account information regarding predecessor companies, key personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the requirement when such information is relevant to the acquisition and will be considered in the evaluation. If a teaming arrangement is contemplated, provide complete information as to the arrangement, including any relevant and recent past performance information on previous teaming arrangements with same partner. If this is a first time joint venture, each party to the arrangement must provide the information required in Section L, paragraph 5.3, for past and present relevant contracts. As with all past contracts identified in the proposal, use the PPIS (Section L, Attachment L-2).

5.3.4 Performance Surveys

The government will evaluate the quality and extent of offeror's performance deemed relevant to the requirements of this RFP. The government will use information submitted by the offeror, by independent submittals of questionnaires and other sources such as other Federal Government offices and commercial sources, to assess performance. Relevant performance includes performance of efforts involving support with the same and / or similar effort and complexities this solicitation requires.

5.3.5 Questionnaires

The Government requests the Offeror, as soon as possible, to send out Past Performance Questionnaire Cover Sheet (Attachment L-3), Past Performance Questionnaire (Attachment L-4) and the Questionnaire Cover Letter (Attachment L-7) to all points of contact the Offeror has listed in the Past Performance Information Sheets (reference Attachment L-2) for each PPIS identified in the Past Performance Volume.

POCs will submit completed questionnaires directly to the Government to Mr. Blake Gibson at Blake.Gibson@hill.af.mil. Once the Past Performance Questionnaires are completed by the POCs, the information contained therein shall be considered sensitive and shall not be released to the Offeror.

In addition to past performance questionnaires for each relevant contract submitted, the Performance Confidence Assessment Group (PCAG) may contact the points of contact provided by the Offeror for the purpose of ascertaining and/or clarifying past performance information.

RESPONDENTS TO THE QUESTIONNAIRES SHALL SEND THE COMPLETED INFORMATION TO THE

PCO AS OUTLINED IN ATTACHMENT L-3, PAST PERFORMANCE QUESTIONNAIRE COVER SHEET.

THE QUESTIONNAIRES SHALL NOT BE SENT BACK TO THE OFFEROR.

5.3.6 Subcontractor Consent Form

Subcontractor Consent Form, (Section L, Attachment L-5) Past performance information pertaining to a subcontractor cannot be disclosed to the prime offeror without the subcontractor’s consent. Provide with the proposal a letter from subcontractors that will perform major or critical aspects of the requirement, consenting to the release of their past performance information to the prime contractor.

For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter (see Attachment L-6 for an example), authorizing release to the Government of requested information on the offeror's performance.

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

6.0 VOLUME IV – PRICE

6.1 General Instructions

The primary purpose of the price proposal volume is to provide the contracting officer and the team evaluators an understanding of how the price proposal was developed. The price evaluation criteria of balance, reasonableness, and Total Evaluated Price (TEP) as defined in section M of the RFP will be assessed from the offeror’s information provided in this volume.

Submit the price proposal in Microsoft Word and Microsoft Excel worksheets as appropriate. Word documents and Excel spreadsheets must be editable and not password protected. Each disk shall be clearly labeled. The paper and electronic copies shall be clearly identified. Scanned documents in PDF files are NOT acceptable for the Price Proposal Volume.

6.1.1 Price Reasonableness and Balance

This section is to assist you in submitting information other than pricing data that is required to evaluate the reasonableness of your proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed prices rests with the offeror.

6.1.2 Estimating Techniques and Methods

When responding to the Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates.

6.1.3 Price Information

Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your 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 Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

6.1.4 Pricing Information Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), information other than 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 that 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 pricing data.

6.1.5 Rounding

All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.

6.2 Volume Organization

The Price volume shall consist of the following sections:

SECTION 1 – Table of Contents; summary descriptions of estimating, purchasing, and accounting systems;

changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure Statement, if applicable.

SECTION 2 – Pricing information and supporting data, to include estimating methodology.

SECTION 3 – Other information such as Government Furnished Property/Government Furnished Equipment (GFP/GFE), base support, long lead costs, termination costs, inflation rate summary and explanation, and life cycle costs. List each exception to the ground rules and assumptions provided in the solicitation and each qualification of the Price volume, if any. Provide complete rationale for any exceptions.

SECTION 4 – The offeror will complete the Excel file, Section J “Pricing Table” IAW the Instructions tab.

This completed worksheet will be utilized to develop the TEP. The TEP is for award determination purposes only and will be a consideration in the best value award decision. This is pending that all the proposed prices are considered balanced and reasonable.

6.3 Estimating Methodology

6.3.1 Estimating System

Provide a summary description of your standard estimating system or methods. The summary description shall cover separately each major cost element (e.g., Direct Material, Engineering Labor, Manufacturing Labor, Indirect Costs, Other Direct Costs, Overhead, G&A, etc.). Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

6.3.2 Accounting System

If applicable, indicate whether the systems utilized are Government approved and provide date and the name of the Administrating Contracting Officer (ACO who approved the Disclosure Statement. Also, identify any deviations from your standard procedures in preparing this proposal.

7.0 VOLUME V - CONTRACT DOCUMENTATION

7.1 Model Contract/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 Model Contract, and completed Sections A through K.

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

Table 7.2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion

Rationale

PWS, Model Contract, 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

7.3 Other Information Required

7.3.1 Authorized Offeror Personnel

Provide the name, title, email address 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.

Also, identify those individuals authorized to negotiate with the Government.

7.3.2 Government Offices

Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

7.3.3 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; and size of business (large or small). This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

7.3.4 Attachments to the Model Contract

The offeror shall provide the following as attachments to the model contract:

7.3.4.1 Completed Pricing Table

The offeror shall complete the Pricing Table in accordance with the instructions tab found in the Pricing Table file.

7.3.4.2 GFP and/or Base Support Requirements

The Government plans to provide the items listed in the GFP attachment of Section J. If the offeror requires the use of Government furnished items other than those specified, the offeror shall provide a listing including quantity, federal stock number, nomenclature, date needed and duration of availability, rental value per FAR 45.1 and 45.2, reason for need, and cross reference to price volume paragraphs which pertain to GFP and/or base support. The offeror shall also provide the written authorization from the cognizant ACO, as applicable. The offeror shall supply this information in the format shown in Table 7.3.

Table 7.3.4.2 - Required Information for Using GFP/Base Support

Quan-tit y

Federal Stock #

Nomen-cl ature

Duration of Need

Rental Value

Reason for Need

Cross Ref. to Cost Prop

2 EA FS156-09-2

ACG-1372

Time Counter

1 Oct 03 - 30 Dec 04

$1,000 Needed to calibrate our 5 mhz/1pps SATCOM simulator offset

Volume IV, pages 23 – 27, paragraphs A-C

7.3.4.3 Associate Contractor Agreements

If applicable, include Associate Contractor Agreements IAW AFMCFARS 5352.217-9010.

7.3.4.4 Applicable Documents

A list of Applicable Documents has been provided to the offerors as an annex to the PWS attachment in the solicitation, which includes a minimum list of Government Compliance Documents. The offeror shall provide a list of any offeror, industry, commercial, and tailored Government standards, specifications, processes, and/or practices selected as compliance documents. The offeror shall also provide a list of all Government compliance documents intended to be used as compliance documents during the course of this contract. The offeror shall submit a list of these documents, including any tailoring instructions, as an annex to the proposed PWS. The offeror shall submit the completed Proposed Compliance Documents as part of Volume V.