MPSCIIISectionL.pdf

SECTION L

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 and sustainment for mission planning systems to CONUS / OCONUS operational units as well as FMS customers. The support includes configuration management and control, drafting and publishing of technical documentation, system checkout, fielding, supply, training support, customer assistance visits, a twenty-four (24) hour / seven (7) day a week help line, international support and training, combined test force support, Mission Planning Central (MPC) maintenance, deployment and management of the MPS

System Support Representatives (SSRs) at worldwide locations, transition to follow on systems and support of all wing and unit level planning requirements and related efforts. These services will be obtained through source selection procedures IAW Federal Acquisition Regulation (FAR) Part 15, Defense Federal Acquisition Regulation Supplement (DFAR) Part 15, Air Force Acquisition

Regulation Supplement (AFFARS) Part 15, Defense Federal Acquisition Regulation

Supplement Procedures, Guidance and Information (DFARS Subpart 215.3--Source Selection) with the new DoD source selection procedures memorandum revised on 01 Apr 2016. The contract will be a

Firm Fixed Price (FFP), Indefinite Delivery, Indefinite Quantity (IDIQ) contract. The ordering period for this effort is five years with a six (6) month option to extend. The total period of performance can extend up to one year from the date of the last ordering period to complete all previously awarded Task

Orders.

2.0 General Instructions

This section of the ITO provides general guidance for preparing proposals as well as specific instructions on the format and content of proposal. To assure timely and equitable evaluation of proposals, the offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and the offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS) and Contract

Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation. Failure to comply with the terms and conditions of the solicitation may result in the offeror being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and must provide complete supporting rationale. The Government reserves the right to determine any such exceptions unacceptable.

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.

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

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.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals and return extra copies to the offeror.

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

1) Requirements of the RFP and government standards and regulations pertaining to the PWS

2) Evaluation Factors for Award in Section M of this RFP

3) Any limitation on the number of proposal pages. Pages exceeding the page limitations set forth in this Section L will not be read or evaluated. Paper pages will be removed from the proposal and returned to the offeror.

2.1 General Information

2.1.1. Point of Contact

The Contracting Officers (CO) are the sole point of contact for this acquisition. Address any questions or concerns you may have to Mr. Ken Hernandez and Mr. Sean Jones at 6039 Wardleigh Rd, Bldg.

1206 Hill AFB, UT 84056-5838 or via e-mail to the following: Kenneth.Hernandez.1@us.af.mil and

Sean.Jones.2@us.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 preaward debriefing or they may choose to wait until after the source selection decision to request a postaward 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.

mailto:Kenneth.Hernandez.1@us.af.mil mailto:Sean.Jones.2@us.af.mil file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b15505 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b15506

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 Solicitation Requirements, Terms and Conditions

Offerors are shall meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as factors or subfactors.

Failure to comply with the terms and conditions of the solicitation may result in the offeror being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and must provide complete supporting rationale. The Government reserves the right to determine any such exceptions unacceptable. By submission of its offer, the offeror accedes to all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors.

2.1.5. Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities

(FedBizOpps) website 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.6 Communications

Exchanges of source selection information between Government and offerors will be controlled by the

CO. 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. See Attachment L-4 for email encryption instructions. Otherwise, source selection information will be transmitted via postal service.

All inquiries must be submitted via e-mail to the Contracting Officers, Mr. Kenneth Hernandez at kenneth.hernandez.1@us.af.mil and Mr. Sean Jones at sean.jones.2@us.af.mil. Questions will be answered and posted to FedBizOps as quickly as possible during the proposal preparation period.

2.1.7 Oral Presentations

Oral presentations will not be allowed.

2.1.8 Organization/Number of Copies/Page Limits

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

http://www.fedbizopps.gov/ file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc%23T2101 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b3104 mailto:kenneth.hernandez.1@us.af.mil mailto:sean.jones.2@us.af.mil

Table 1 - Proposal Organization

VOLUME ITO

Paragraph

Number

VOLUME TITLE PAGE

LIMIT

NUMBER

OF

HARD

COPIES

NUMBER

OF SOFT

COPIES

I Executive Summary; including

Narrative Summary and Table of

Contents

6 3 2

II Technical 100** 3 2

III Past Performance; including

Company Roadmap (if required)

7/contract*;

max of 12 contracts

2 2

III Subcontractor Consent Letters Unlimited 1 2

IV Cost/ Unlimited 1 2

V Contract Documentation Unlimited 1 2

*See Past Performance Information (PPI), Section L Paragraph 5.6

**See Page Limitations, Section L Paragraph 2.1.8.1, for page count exceptions

Additionally, the offeror shall prepare one (1) Master Proposal containing one hard copy of each volume identified above in Table 1. This Master Proposal shall be printed double-sided, flipped on the short end, two-hole punched centered on top of the page, and bound together but not in a binder.

2.1.8.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. 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. Each page shall be counted except the following: cover sheets (not to be confused with the

Narrative Summary), Tables of Contents, title pages, glossary of abbreviations, acronym lists, blank pages, tabbed dividers, and staffing table. Each volume shall conform to the numbering, page count, and quantity of copies shown in Table 1 above.

2.1.8.2 Page Size and Format

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, single spaced.

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 size and format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

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 will count as a single page, and any hole punches shall not interfere with or delete information. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics and 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.1.9 Pricing Related Data

All cost or pricing data shall be addressed ONLY in the Price Proposal and Contract Documentation

Volumes. Cost trade-off information, work hour estimates, and material kinds and quantities

(excluding dollar amounts/prices) may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

2.1.10 Classified Information

No classified proposals shall be submitted. Proposals shall be in compliance with the DD Form 254 and contract security requirements.

2.1.11 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 government will fill out a portion of the Cross Reference Matrix and the offeror will fill out the remaining sections in Attachment L-2 of this ITO indicating the proposal reference information as it relates to the ITO, PWS, CLIN numbers, and CDRL references found therein.

2.1.12 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.1.13 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.1.14 Binding and Labeling

Other than the Master Proposal identified in Table 1, each volume of the proposal should 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 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 FAR

3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source

Selection Information.

2.1.15 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD/DVD 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/DVDs (CDRs or DVDRs not CDRWs or DVDRWs). Each volume shall be in a different directory on a CD or 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 and searchable by the Microsoft (MS) Office Suite

2010 or Adobe PDF format, as applicable. In the event there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

2.1.15.1 Electronic File Names

For electronic submissions, the file naming convention for the proposal volumes is as follows. You may expand on these files 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

Contractual Documentation company name contract.xxx

NOTE: .xxx = appropriate default file extension for MS Office suite / Adobe document type

2.1.15.2 Hyperlink

The Table of Contents in the soft copies of all proposal volumes, other than Volume III, 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 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc%23b522151 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b31044 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b31044 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. A Hyper-linking reference between different filenames is not acceptable.

Volume III will be submitted in accordance with Attachment L-3 and will not be able to be hyperlinked.

2.1.16 Distribution

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

AFLCMC/PZZKB

Attn: Mr. Sean Jones

6039 Wardleigh Rd, Bldg. 1206

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

3.0 Volume I - Executive Summary

In the executive summary volume, the offeror shall provide the following information:

3.1 Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. The executive summary is for informational purposes only as 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 of the entire proposal.

4.0 Volume II - Technical Volume

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 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc%23T2101 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b3104 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 technical solution for meeting or exceeding the Government’s 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 Table and Drawings

(3) Glossary

(4) Cross Reference Matrix

(5) Technical Proposal (Subfactors)

4.3 Subfactor One: Program Management

Offeror shall provide an approach for Program Management. The proposed approach shall thoroughly substantiate all of the following:

4.3.1 Human Resources- The contractor shall identify approach for recruiting, hiring, training, and staffing (PWS 2.1.1.1). The recruiting and hiring approach shall demonstrate, through explicit evidence and examples, the offeror’s ability to hire and retain qualified personnel. Training approach shall demonstrate to the government the offeror’s ability to train personnel on applicable position specific duties, however OCONUS specific training for personnel shall be addressed in 4.3.4. The contractor shall complete the Staffing Table in Attachment L-10. The table shall identify how the offeror proposes to organize and staff all positions/functions in accordance with the requirements/tasks in the PWS.

4.3.2 Cybersecurity and Information Assurance (IA) – The contractor shall demonstrate the

Cybersecurity/IA approach to the government pertaining to the offeror’s ability to provide cybersecurity and maintain certifications IAW the PWS and the current versions of DoD and Air Force

Information Assurance requirements (including, but not limited to, DoDI 8500.01 (Mar 14, 2014), DoDI 8510.01 (March 12, 2014; Incorporating Change 1, May 24, 2016) and DoD 8570.01-M

(December 19, 2005; Incorporating Change 4, Nov 10, 2015 )(PWS 2.2.1.1.1, 2.2.1.1.2, 2.11.3, including all sub-paragraphs, 2.11.4.1 and 2.12.2.1)

4.3.3 Security Clearance – The contractor shall demonstrate the security clearance approach pertaining to the offeror’s practices and procedures for obtaining and maintaining required security clearances for personnel and facilities IAW applicable DoD and USAF directives and instructions

(including, but not limited to 5 CFR 732 and Executive Order 12968). (PWS 2.1.1.5, 2.10.4.2, 2.11.1.3)

4.3.4 OCONUS Personnel - The contractor shall demonstrate the Outside of Continental United

States (OCONUS) personnel approach pertaining to the offeror’s practices and procedures for placing, training (specific country and theater) and supporting permanent and temporary personnel in OCONUS locations. This approach shall address: the basic approach for placing, training (specific country and theater) and supporting personnel overseas supporting various Unified Combatant Commands such as

NORTHCOM, SOCOM, PACOM, EUCOM, AFRICOM, and CENTCOM. Include the approach for obtaining various documentation required by the US Department of State, Department of Defense, and host countries (i.e. visas and country clearances, Status of Forces Agreements (SOFAs), as well as

Technical Expert Status Agreements (TESAs), and International Traffic in Arms Regulations (ITARs) exemptions). (PWS 2.1.1.6 and 2.10.1.3)

4.3.5 Transition– The contractor shall demonstrate the transition approach pertaining to the offeror’s strategy to transition all contract activities and personnel from the incumbent to the awardee within 30 calendar days of the start of the initial task order. The transition approach shall address: transition of

Government Furnished Property (GFP)/Government Furnished Equipment (GFE) and transition of personnel, if applicable, within the transition period. (PWS 6.1)

4.4 Subfactor Two: Mission Planning System Support Facility (MPSSF)

The contractor shall provide an approach for support for the Mission Planning System Support Facility.

The proposed approach shall thoroughly substantiate all of the following:

4.4.1 Mission Planning Central (MPC) Support – The contractor shall demonstrate the MPC Support approach pertaining to the offeror’s proposed approach to support and maintain MPC operations IAW

PWS 2.11. This plan shall include the maintenance/sustainment of the existing functionality (PWS

2.11.5 including sub-paragraphs), establishment of an Integrated Product Team (IPT) to manage

Change Enhancement Requests (CERs) (PWS 2.11.1.8), provide MPC system software security (PWS

2.11.3 including sub-paragraphs), and provide MPC training to users, developers, testers, and program managers (PWS 2.11.1.4).

4.4.2 Deficiency Investigation Process– The contractor shall demonstrate the Deficiency

Investigation Process approach pertaining to the offeror’s proposed approach to identify Mission

Planning Environment (MPE) deficiencies and manage the process IAW T.O. 00-35D-54 (August 1, 2015) and the PWS 2.3.1.1.2-4. The approach shall address the performance of Screening Point duties

IAW the PWS 2.5.1.6 and TO 00-35D-54, and 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, and shall provide an acceptable centrally accessible tool for tracking the status of the reported problem to closure. Mission Planning has a waiver for the Joint Deficiency Reporting System (JDRS), and the current tool is the Enterprise Deficiency

Reporting (EDR) tool located on MPC, however the contractor may propose an alternate solution provided it meets the requirements of T.O. 00-35D-54.

4.4.3 Operational User and SSR Training – The contractor shall demonstrate the operational user and

SSR training approach pertaining to the offeror’s proposed approach for developing and delivering training plans for existing and new MPEs to applicable operational users and SSRs IAW PWS

2.2.1.3.10, 2.2.1.3.12, 2.3.1.1.5, 2.4 (including sub-paragraphs), 2.7.1.4, 2.10.1.2, 2.10.1.3, 2.10.1.3.1, 2.10.1.7.1, 2.10.1.9, and 2.11.1.4. The approach shall address the Mission Planning Training (MPT) involvement throughout the MPE development and testing process and the delivery of the training in conjunction with operational test of a new MPE.

4.5 Subfactor Three: System Support Representatives (SSRs) (PWS 2.2)

The contractor shall provide an approach for SSRs. The proposed approach shall thoroughly substantiate all of the following:

4.5.1 Worldwide Support – The contractor shall demonstrate their approach for worldwide support pertaining to the offeror’s proposed approach for supporting a minimum of 70 geographically separated locations. The approach shall address the offeror’s ability to ensure SSRs at each location are performing duties, as required by the PWS 2.2.1.3.

4.5.2 Support for Deployed Units – The contractor shall demonstrate their approach for support of deployed units pertaining to the offeror’s proposed approach for supporting activities required prior to, and during, a unit’s deployment. The offeror 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.2.1.3.12. User support may include, but is not limited to, contacting the MPSSF.

4.5.3 Mission Planning Environment (MPE) Configuration Control – The contractor shall demonstrate the MPE configuration control approach pertaining to the offeror’s proposed plan to maintain configuration control for all fielded and certified MPEs IAW PWS 2.2.1.3.1 and 2.2.1.3.2 The plan shall address: the communication between the applicable MPSSF functions and SSRs (PWS

2.7.1.4, 2.9.1.6) ; use of MPE Letters and MAJCOM Certification Letters to ensure MPEs are functional and related systems remain interoperable (PWS 2.2.1.3.1, 2.2.1.3.8, 2.5.1.2, 2.5.1.5, 2.10.1.8); SSRs implementation and maintenance procedures and practices for loading new or updated mission planning data (i.e. charts, mapping updates and aeronautical information) IAW PWS 2.2.1.3.8.

4.5.4 Support for Operational Test – The contractor shall demonstrate the support approach for operational test pertaining to the offeror’s proposed plan for SSR participation in operational test events

IAW PWS 2.2.1.3.15. The plan shall address how the SSR will be trained on the systems administration for the new MPE prior to the test event. (PWS 2.4.1.6, 2.4.1.8, 2.4.1.18, 2.7.1.4, 2.10.1.4, 2.10.1.7.1)

5.0 Volume III - Past Performance

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-3. This information is required on the offeror and all key subcontractors, teaming partners, and/or joint venture partners. Key subcontractors/partners are those who are proposed to perform 15 percent or more of the proposed effort based on the total proposed price or 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 Relevant Contracts

Submit information in accordance with Attachment L-3. The offeror shall submit Past Performance

Information on three recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. A recent contract is an ongoing contract (with at least one full year of performance history) or a contract completed within the last five years of the date of issuance of the solicitation. Also include information on up to three recent contracts performed by each of your teaming partners and key subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section

M, paragraph 4.3 and 4.4 – under Past Performance Evaluation Factor.

5.3 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 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 rated with higher confidence than they may have otherwise been rated. 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 used to evaluate the proposal.

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

5.5 Workload Sharing

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

Table 2 – Total Contract Workload Sharing

Contract Percent Performed by Prime

Percent Performed by

Subcontractor(s) Short Description

Mission Planning

Support Contract III

51% - Company X 17% - Company Y

32% - Company Z

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

Table 3 – 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)

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

SSRs 80% - Company X 15% - Company Y

5% - Company Z

See note above.

5.6 Past Performance Information (PPI)

The PPI Tool, instructions provided in (Section L, Attachment L-3) 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 subcontractor for Federal agencies and commercial customers during the five (5) years prior to the date of issuance of this solicitation. Limit each PPI to seven (7) pages, with a maximum of 12 contracts. Submit two (2) 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 PPI 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 piece of PPI.

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.2, for past and present relevant contracts. As with all past contracts identified in the proposal, use the PPI

Tool (Section L, Attachment L-3).

5.7 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.8 Questionnaires

The Government requests the offeror, as soon as possible, to send out Past Performance Questionnaire

Cover Sheet (Attachment L-7), Past Performance Questionnaire (Attachment L-8) and the

Questionnaire Cover Letter (Attachment L-9) to all points of contact the offeror has listed in the Past

Performance Information Tool (reference Attachment L-3) for each PPI reference identified in the Past

Performance Volume.

Individuals identified as references within the Past Performance Volume will submit completed questionnaires directly to the government to Mr. Sean Jones at sean.jones.2@us.af.mil. Once the Past

Performance Questionnaires are completed, 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 government evaluators 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-7, PAST PERFORMANCE

QUESTIONAIRE COVER SHEET. THE QUESTIONNAIRES SHALL NOT BE SENT BACK TO

THE OFFEROR.

5.9 Subcontractor Consent

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 all 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

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.2 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. The burden of proof for credibility of proposed prices rests with the offeror.

6.3 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.4 Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All data 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 data and documentation be included elsewhere in the proposal.

6.5 Cost or Pricing Data Requirements

The contracting officer has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the contracting officer will review this determination and if, in the contracting officer's opinion, adequate price competition exists no additional data will be requested and certification under FAR 15.406-2 will not be required. However, if at any time during this competition the contracting officer determines that adequate price competition no longer exists; offerors may be required to submit cost data to the extent necessary for the contracting officer to determine the reasonableness and affordability of the price. In accordance with FAR 15.403-

1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5 . If, after receipt of proposals, the CO determines that there is insufficient data 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.6 Total Evaluated Price (TEP) Pricing Table

Offerors shall populate the pricing and cost cells in Section J Attachment 1, TEP Pricing Table per the instructions in the TEP Pricing Table. The Government will use this worksheet to calculate the TEP.

The offeror shall complete and return this in MS Excel format. 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.7 Evaluation of Compensation for Professional Employees

The offeror shall submit a professional employee compensation plan meeting the requirements of FAR

52.222-46, Evaluation of Compensation for Professional Employees. The offeror shall detail the base labor rate, fringe, all other burdens, and profit/fee contained in labor rates to facilitate comparisons in accordance with FAR 52.222-46.

6.8 Accounting System

Indicate whether you and any and all related entities (e.g. subcontractors, teaming partners, interdivisional orders, etc) that will be issued other than fixed price type work have Government approval of accounting systems and if so, provide evidence of such approval. Also, identify any deviations from your standard procedures in preparing this proposal.

6.9 Rounding

file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/far/FAR15.DOC%23b154062 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154031 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154031 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154033 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154035 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154031

All dollar amounts provided shall be rounded to the nearest dollar.

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 Sections A through K.

7.1.1 Section A - Solicitation/Contract Form

Completion of blocks 13 and 15 and signature and date for block 16, 17, and 18 of the SF 33. Any amendments (SF 30) to the RFP must be signed in block 15. Signature by the offeror on the SF 33/SF

30 constitutes an offer, which the Government may accept. In signing the SF 33/SF 30, the offeror accedes to the contract terms and conditions as written in the RFP Sections A through K. The

"original" copy should be clearly marked under separate cover and should be provided without any punched holes.

7.1.2 Section B - Supplies or Services and Prices

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

Pricing Table File.

7.1.3 Section F - Deliveries or Performance

The Period of Performance will be identified on each individual task order.

7.1.4 Section G - Contract Administrative Data

Contract Administrative Data Section G of the Model Contract will include all fundcites and dollar amounts for the contract. The offeror is not required to fill in this information

7.1.6 Section I - Contract Clauses

The offeror shall complete necessary fill-ins in Section I and submit only pages that require a fill-in.

The offeror shall comply with the clauses specified within Section I of the Model Contract.

Furthermore, any reference of a clause and/or provision in the solicitation will be adhered to and included in the resulting contract. All laws, regulations, and statutory authorities will also be applied within the model contract.

7.1.7 Section K - Representations, Certifications, and other Statements of Offerors Representations, Certifications, and other Statements of Offerors The offeror shall provide completed representations, certifications, acknowledgments, and statements.

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 offeror 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 4.

Table 4 - 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;

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 GFP and/or Base Support Requirements

The Government plans to provide the items listed in the Government-Furnished Property (GFP) attachment of Section J of the solicitation.