FA4452-16-R-0005_Amendment_0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

1. This amendment removes FAR Deviation 252.209-7991. This f ill-in provision has been incorporated into the FAR through FAR interim rule 2015-011. The Deviation is no longer required.

2. This amendment corrects the paragraph numbering error on pages 52-53 of the RFP and the paragraph number error in the deliverable table on page 54 for Exhibits B-BD.

3. This amendment corrects an error in para 4.1.2.1 of Addendum to FAR 52.212-1—Instructions to Offerors. 4.1.2.1 states, “Complete applicable attachments and submit w ith proposal in Volume III.” This is an error. Attachments 2,3,4,5, & 6 are required in Volume II--Past Performance IAW RFP Addendum to FAR 52.212-1—Instructions to Offerors para 3. Para 4.1.2.1 w ill be revised to read: “4.1.2.1. Complete applicable attachments and submit w ith proposal in the required volume.”

4. This amendment corrects the numbering error in Block 5 of Exhibits B-BD. The PWS para reference w as updated w hich required Block 5 to be updated.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 31

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

16C. DATE SIGNED

BY 29-Jul-2016

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

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

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

X 9B. DATED (SEE ITEM 11)

14-Jul-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

29-Jul-2016

CODE

763 SCONS

507 SYMINGTON DRIVE

SUITE W202

SCOTT AFB IL 62225-5022

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

1385324193C Typewritten Text 618 256-9957

1385324193C Typewritten Text lee.mutschler@us.af.mil

FA4452-16-R-0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

INSTRUCTIONS TO OFFERORS

Addendum to FAR Clause 52.212-1 Instructions to Offerors (ITO)—Commercial Items

1.0 General Instructions

a. The contractor’s proposal must include all data and information requested by these instructions and must be submitted in accordance with (IAW) these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS). Non-conformance with these instructions 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 contractor 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 contractor's proposal.

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

d. FAR Clause 52.212-1(c) is amended as follows: The offeror agrees to hold the prices in its offer firm until 1 Jun 17.

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

1.1 General Information

1.1.1. Points of Contact (POCs)

The Contract Specialist (CS), Mr. Lee Mutschler, and the Contracting Officer (PCO), Ms. Lisa Gross, are the sole POCs for this acquisition. Please address any questions or concerns you may have to these POCs. Written requests for clarification may be sent to the email addresses listed below:

POC Phone Email Mr. Lee Mutschler (618) 256-9957 lee.mutschler@us.af.mil Ms. Lisa Gross (618) 256-9965 lisa.gross@us.af.mil

1.1.2 Debriefings

The PCO will promptly notify offerors of any decision to exclude them from the competitive range (if discussions are held); 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 PCO 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 FAR 15.506, as applicable.

1.1.3 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the contractor shall immediately notify the CS or PCO in writing with supporting rationale as well as the remedies the contractor is asking the CS or PCO 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.

1.1.4 Oral Presentations

Oral presentations will not be permitted.

1.1.5 Communications

Exchanges of evaluation information between Government and offerors will be controlled by the CS. When email is used to transmit such information to offerors it will include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Otherwise, evaluation will be transmitted via mail or picked up/dropped off by a local offeror representative.

1.1.6 Amendments to Solicitation

If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged.

Offerors shall acknowledge receipt of any amendment to this request by the day and time specified in the amendment(s).

1.2 Organization/Number of Copies/Page Limits

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

Table 1.2 - Proposal Organization

VOLUME Instructions

Paragraph Number

VOLUME TITLE COPIES PAGE LIMIT

I 2.0 Technical/Technical Risk 1 30 II 3.0 Past Performance 1 30 III 4.0 Contract Documentation and Price 1 No Limit

1.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 destroyed. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following: blank pages, cover pages, table of contents, tabs, indexed lists of tables and figures, glossaries, labor category position descriptions of all personnel, organization structure change history (IAW paragraph 3.3.2 of this instruction), quality control plan, and those noted in the Proposal Organization Table (Table 1.2) as unlimited.

1.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 single spaced and the text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These limitations shall apply to both electronic and hard copy proposals.

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 by 17 inches in size. Foldout pages exceeding 8.5x11 shall fold entirely within the volume, and count as two pages. Foldout pages should 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 limitations shall apply to both electronic and hard copy proposals.

1.2.2 Cost or Pricing Related Data

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

The contracting officer has determined there may be 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 of the price.

1.2.3 Cross-Referencing

Each volume shall be written on a stand-alone basis so that its contents may be evaluated without 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.

1.2.4 Indexing

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

1.2.5 Title Page

Each volume must include a title page. The title pages must show:

a. Solicitation Number

b. Name, address, telephone numbers and email address of the contractor

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

1.2.7 Tables and Figures

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

1.2.8 Binding and Labeling

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 contractor's name. The same identifying data should be placed on the spine of each binder. 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.

1.3 Electronic Offers

Electronic offers alone will not be accepted. However, each contractor is required to submit an identical electronic copy of their proposal on a CD no later than the required proposal due date. The CD shall be in addition to the required number of hard copies designated in Table 1.2 above. The content and page size of electronic copies must be identical to the hard copies. The outside of the CD or the CD jacket must be labeled to correspond with the hard copies. For electronic copies, indicate volume number and title, and use separate files to permit rapid location of information. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office 2010 suite of applications. In the event of a discrepancy between the hard copies and electronic copies, the electronic copy will be considered the original.

1.4 Distribution

The “original” proposal shall be identified. Hard copies and electronic copies of proposals shall be addressed and mailed or hand carried to:

AFICA 763 Specialized Contracting Squadron Attn: Solicitation FA4452-16-R-0005 Attn: Mr. Lee Mutschler 507 Symington Drive, Room W202 Scott AFB IL 62225-5022

Access to Scott AFB for Delivery of Hand Carried Proposals: Offerors are cautioned that when hand-carrying proposals individuals not affiliated with this installation must obtain visitors’ passes prior to entrance. The Shiloh gate has been designated as the “Visitor’s Control Center.” Some delays can be anticipated for visitors to process through the “Visitor’s Control Center” and offerors should allow sufficient time to obtain visitors’ passes. Each visitor must have an on-site sponsor to obtain a visitor’s pass. Please contact Lee Mutschler at (618) 256-9957 for more information.

Late proposals will be processed in accordance with FAR 52.212-1(f), Submission, Modifications, Revisions, and Withdrawals of Proposals.

2.0 Volume I - Technical Volume

The contractor shall include a master table of contents of the entire proposal at the front of the Technical Volume.

2.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in the Addendum to FAR Clause 52.212-2, Evaluation Criteria. 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.

2.2 Format and Specific Content

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

2.2.3 Subfactor 1 – Technical Approach

Each offeror shall provide a technical approach narrative describing their technical methodology/approach to be used in performing Flight Dispatch Services, En-Route Flight Monitoring, and Flight Operations Service Management. The specific requirements of the Technical Approach subfactor are defined in Addendum to FAR Clause 52.212-2, Evaluation Criteria.

2.2.4 Subfactor 2 – Staffing Approach

Each offeror shall provide a staffing approach narrative, a supporting personnel matrix, identify their key personnel, provide key personnel labor category descriptions, provide key personnel specific résumés, provide a notional shift schedule demonstrating 24x7x365 coverage, provide labor category descriptions for non-key personnel, provide an organizational structure hierarchy chart, and provide a phase-in plan. The specific requirements of the Staffing Approach subfactor are defined in Addendum to FAR Clause 52.212-2, Evaluation Criteria.

2.2.5 Subfactor 3 – Other Technical Requirements (This subfactor is not included in the integrated assessment) Each offeror shall provide a Mission Essential Contractor Services plan as required by DFARS 252.237-7024 and a Quality Control Plan (QCP) to ensure the delivery of conforming services IAW the PWS. The QCP will be incorporated by reference into the Quality Assurance Surveillance Plan (QASP) (Attachment 1) at award. The specific requirements of the Other Technical Requirements subfactor are defined in Addendum to FAR Clause 52.212-2, Evaluation Criteria.

2.2.5 Volume Organization

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

1. Table of Contents

2. Technical Approach

3. Staffing Approach

4. Labor Category Position Descriptions

5. Mission Essential Contractor Services Plan

6. QCP

7. Glossary of Abbreviations and Acronyms

3.0 Volume II – Past Performance

3.1 General

Each offeror shall submit a past performance volume with their proposal containing past performance information IAW the format contained in the Past Performance Information Sheet (PPIS) (Attachment 2). This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposing 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 Subcontractor Consent Letter (Attachment 3) executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall also submit a Client Authorization Letter (Attachment 4 for a sample letter), authorizing release to the Government of requested information on the offeror's performance.

3.2 Early Proposal Information

Each offeror is requested to submit the information shown in the Past Performance Questionnaire (PPQ) (Attachment 6), for each relevant contract 10 calendar days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in offeror disqualification.

As soon as practicable, offerors shall complete Section 1 of the attached PPQ (Attachment 6) and email it and the PPQ Cover Letter (Attachment 5) to points of contact (POCs) the offeror has listed in the PPIS (Attachment 3). The POCs listed in the PPIS’s should represent the individuals most knowledgeable about the offeror’s performance on the identified contract or program, such as the following: (1) Contracting Officer’s Representative; (2) Program/Project Manager; (3) Contracting Officer. The POCs will complete the questionnaires and forward them by email directly to the Contract Specialist, Mr. Lee Mutschler at lee.mutschler@us.af.mil. RESPONDENTS TO THE QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION SHEETS BACK TO THE OFFEROR. Offerors shall state this in their emails to the POC’s completing the PPQ. In order to facilitate receiving the PPQs that are not received early, offerors shall submit the name, phone number, and email address for the POCs receiving PPQs to the CS 10 calendar days prior to the date set for receipt of proposal. The Source Selection Evaluation Board (SSEB) will conduct follow-up reviews with any POCs as necessary. The SSEB will evaluate no more than three PPQs (total) for each referenced contract.

3.3 Relevant Contracts

There is no page limit per PPIS; however, the total Past Performance volume shall not exceed 30 pages. Submit information in accordance with the PPIS (Attachment 2) on no more than five recent contracts that you consider most relevant in demonstrating your or your subcontractor’s ability to perform the proposed effort. A contract, task order or blanket purchase agreement (BPA) call is considered recent if it is ongoing or if it was completed within three years of the date of issuance of this solicitation. If submitting and indefinite delivery contract vehicle or BPA for consideration, the task order or BPA call for which evaluation is requested shall be specified. Past Performance Information sheets including more than one contract, task order or BPA call will be counted for as many contracts, task orders or BPA calls that are included on the Past Performance Information sheet. 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 Addendum to FAR Clause 52.212-2, Evaluation Criteria, paragraph 2.2 – Factor 2 Past Performance.

The Government may consider past performance in the aggregate in addition to on an individual contract basis. In the case of offerors for which there is no information on past contract performance or where past contract performance information is not available, the offeror may not be evaluated favorably or unfavorably on the factor of past contract performance (see FAR 15.305(a)(2)(iv).) In this case, the offeror’s past performance is unknown and assigned a performance confidence rating of “neutral.” Although the SSEB will not rate an offeror that lacks recent, relevant past performance favorably or unfavorably with regard to past performance, the SSA may determine that a “Substantial Confidence” or “Satisfactory Confidence” past performance rating is worth more than a “Neutral Confidence” past performance rating in a best value tradeoff.

3.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 may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate. For example, 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 Past Performance criteria used to evaluate the proposal.

3.3.2 Organizational Structure Change History

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

4.0 Volume III – Contract Documentation and Price

4.1 Contract Documentation

4.1.1 Fill-Ins

Complete blocks 12, 17a, 17b, 30a, 30b, 30c, and all CLINs on the SF1449. By completing these blocks, the offeror accepts the contract terms and conditions as written in the RFP.

Complete all fill-in full text clauses and provisions unless already completed in your online representations and certifications a SAM.gov.

Complete the provision 252.209-7991 (Dev) included in this solicitation.

4.1.2 Attachments/Exhibits

4.1.2.1. Complete applicable attachments and submit with proposal in the required volume.

Attachments to the RFP include:

Attachment 1 – QASP Attachment 2 – PPIS Attachment 3 – Subcontractor Consent Letter Attachment 4 – Client Authorization Letter Attachment 5 – PPQ Cover Letter Attachment 6 – PPQ Attachment 7 – Subcontracting Plan Review Checklist

4.1.2.2. Complete blocks 17 and 18 of all Exhibits and submit with proposal in Volume III.

Exhibits to the RFP include:

Exhibit A Exhibit AA Exhibit AB Exhibit AC Exhibit AD Exhibit B Exhibit BA Exhibit BB Exhibit BC Exhibit BD

4.1.3 Teaming Matrix

A Teaming Matrix (if applicable) shall be submitted with the Volume III. Teaming arrangements are encouraged.

Offerors shall describe which tasks each member of their teaming arrangement will be responsible for and indicate any potential OCI concerns and mitigations.

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

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

Table 4.1 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion

Rationale and Impact (if any)

PWS, RFP, ITO, etc. Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

4.2 Other Information Required

4.2.1 Authorized Contractor Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

4.2.2 Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address; 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).

4.2.3 Price Completeness and Reasonableness

The contractor shall submit pricing information to support the completeness and reasonableness of their proposed prices for all CLINs. The pricing information submitted should fully support PWS requirements for each task element specified in the PWS. A breakdown should also be provided for price traceability which shows the skill mix, labor categories, position descriptions, estimated number of hours, and estimated fully burdened labor rates.

Information shall also be segregated by the performance periods and a total price for each CLIN as specified in the solicitation. Information shall also show the consolidated total price for performance. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed prices rests with the contractor.

4.2.4 Price Data

Data beyond that required by this instruction shall not be submitted unless you consider it essential to document or support your 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 Contract Documentation and Price Volume.

4.2.5 Rounding

All unit and extended prices provided shall be rounded to the nearest dollar. Extended prices MUST be divisible by 11 for base period and 12 for option periods. All loaded labor rates shall be rounded to the nearest penny.

4.2.6 Organizational Conflict of Interest (OCI)

The Government does not anticipate any OCI related to this requirement; however, at time of submitting a proposal, the offeror shall submit an Organizational Conflict of Interest Identification and Mitigation Plan (OIMP), as described herein: the contractor must submit and maintain an OIMP acceptable to the PCO. The OIMP shall include, at a minimum, processes and internal controls necessary to identify, capture, and mitigate OCI activities at the subcontractor level. The Government-accepted OIMP shall be incorporated by reference into a resultant contract. If the offeror does not identify any OCI, no OIMP is required.

4.2.7 Security Clearance

A security clearance is not required; however, contractor personnel will be required to pass a National Agency Check with Inquiries (NACI) after award.

4.2.8 Subcontracting Plan - (Applies to Large Business Only)

IAW FAR 19.705-2, large business prime Offerors shall provide a clear, detailed and realistic plan that complies with FAR 52.219-9 Alt II (Dev) and DFARS 252.219-7003 and satisfies all of the requirements of FAR 19.704, DFARS 219.704, and AFFARS 5319.704(a)(1) in order to be determined acceptable by the PCO prior to contract award. The Offeror's submission must provide sufficient information to support the PCO's review of the subcontracting plan to determine acceptability. Offerors should propose positive goals that are realistically obtainable and provide rationale for the proposed goals. If small business subcontract possibilities do not exist or are limited, the Offeror's plan must state such and provide rationale supporting the assertion. An approved Subcontracting Plan is required for any contract awarded to a large business Offeror. The Subcontracting Plan Checklist that will be used by the Contracting Officer is included as Attachment 7 to the RFP and shall be used as a guide when preparing a subcontracting plan.

This factor will be evaluated on an Acceptable/Unacceptable basis. Failure to submit such a plan will render the offeror ineligible for further consideration in this source selection. In other words, if an offeror’s small business subcontracting plan does not meet the aforementioned requirements, the offeror’s proposal may be disqualified from further consideration.

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT

For

EXECUTIVE AIRLIFT FLIGHT DISPATCH

July 29, 2016

Contents

1. Description of Services

1.1. Scope

1.2. Tasking POCs

1.3. Mission Statement

1.4. Mission Essential Contractor Services

1.5. Task Descriptions

1.5.1. Flight Dispatch Services (TASK 1)

1.5.1.1. Flight Planning Analysis (Pre‐Mission Execution)

1.5.1.2. Diplomatic Clearances

1.5.1.3. Mission Planning Package

1.5.1.4. Mission Review

1.5.1.5. Mission Planning Package Update

1.5.1.6. Calculate Final TOLD and W&B

1.5.1.7. Flight Plan Filing

1.5.1.8. Mission Planning Package Update (“Paper the Crew”)

1.5.1.9. Dispatcher‐to‐Pilot Briefing

1.5.2. En‐route Flight Monitoring (TASK 2)

1.5.2.1. Weather Assessment

1.5.2.2. Re‐planning

1.5.2.3. Safety of Flight

1.5.2.4. En‐route Mission Planning Package Update

1.5.3. Flight Operations Service Management (TASK 3)

1.5.3.1. ACARS Ground Host Processing

1.5.3.1.1. Technical Support

1.5.3.2. SATCOM ORT Management

1.5.3.3. Onboard Performance Tool (OPT) Airport Database Management

1.5.3.3.1. OPT Airfield Database Subscription

1.5.3.4. Locator Transmitter (ELT) Management

1.5.3.5. Identification Friend or Foe (IFF)/Mode S ACARS (ICAO) ID Management

1.5.3.6. SARB Support

1.5.3.7. Support for CNS/ATM and New Aircraft Technologies

1.5.3.7.1. Controller‐Pilot Data Link Communications (CPDLC) Management

1.5.3.8. EGPWS Database Management

1.5.3.8.1. EGPWS Database Annual Subscription

1.5.3.9. FMS Navigation Database Management (NDB):

1.5.3.9.1. FMS Navigation Database (NDB) Annual Subscription

1.5.4. Dispatch Familiarization Course (TASK 4)

1.5.5. Phase‐In

1.5.6. Phase‐Out

1.5.6.1. Phase‐Out Program

1.5.6.2. Description

1.5.6.3. Inclusions

1.5.6.4. Deliverable

1.5.6.5. Cooperation

1.6. Deliverables

2. Service Summary

3. General Information

3.1. Program Management Support

3.1.1. Risk Management Program

3.1.2. Program Management POC

3.1.3. Key Contact List

3.1.4. Contractor Manpower Reporting

3.2. Security Requirements

3.2.1. Access to Installation During Force Protection condition (FPCONS)

3.2.2. Property Protection

3.2.3. Contractor Working in Controlled or Restricted Areas

3.2.4. Access to Government Facilities with Controlled or Restricted Areas

3.2.5. Contractor Consent to Background Checks

3.2.6. Citizenship

3.2.7. Badges

3.2.8. Safeguarding For Official Use Only (FOUO) and other Unclassified Information

3.2.9. Information Assurance

3.2.10. Communications Security:

3.2.11. Privacy Act

3.3. Place of Performance

3.4. Hours of Operation

3.5. Administrative Items

3.5.1. Dispatchers

3.5.2. English Language

3.5.3. Conduct

3.5.4. Access

3.5.5. Original Equipment Manufacturer (OEM) Data

3.6. Publications and Services

3.6.1. AF Publications

3.6.2. DOD Publications

3.6.3. FAA Publications

3.6.4. Access

1. Description of Services

1.1. Scope

The purpose of this Performance Work Statement (PWS) is to define the tasks to be accomplished for Flight Dispatch of four Boeing 757-200 (designated C-32A), four Boeing 737-700 (designated C-40B) and seven Boeing 737-700 (designated C-40C) Commercial Derivative Aircraft (CDA). Although Very Important Person Special Air Mission (VIPSAM) operations are not identical to commercial operations, the geographical scope is worldwide and the level of service provided to part 121 commercial ops is the most rigorous and thorough. The contractor shall provide flight dispatch services comparable to existing commercial airline 24/7/365 world-wide operations. This PWS describes the efforts and tasks that shall be performed by the contractor for the organizations listed below.

Performance shall be at the contractor’s facility. This PWS covers the United States Air Force (USAF) C-32A, C-40B and C-40C fleet aircraft, hereafter referred to as “Covered Aircraft”. The covered aircraft include:

- (4) Boeing 757-200 (designated C-32A) o 4 at KADW (Andrews 89th AW, 1st ALS), AMC

- (4) Boeing 737-700 (designated C-40B) o 2 at KADW (Andrews 89th AW, 1st ALS), AMC o 1 at ETAR (Ramstein 86th ALW), USAFE o 1 at PHIK (Hickam 15 ALW), PACAF – (TASK 4 only)

- (7) Boeing 737-700 (designated C-40C) o 3 at KADW (Andrews 201st ALS), ANG o 4 at KBLV (Scott 932d ALW), AFRC

- A contingency/backup capability to support ‘day of flight’ dispatch operations for two VC-25s (B-747) is also required. Unless specifically called out separately, the term C-40 aircraft encompasses both C-40B and C-40C aircraft.

1.2. Tasking POCs

Tasking agency POCs are:

1.3. Mission Statement

The mission of the covered aircraft is to provide safe, comfortable, and reliable worldwide transportation for executive level Government officials and Department of Defense (DOD) civilian and military senior leaders. This includes the President of the United States (POTUS), the First Lady of the United States (FLOTUS), Vice President of the United States (VPOTUS), Secretary of Defense (SECDEF), Secretary of State (SECSTATE), Congressional Leaders, other Secretarial and Cabinet leaders, US Combatant and Component Commanders from all services, foreign heads of state, Office of the Secretary of Defense (OSD), White House Military Office (WHMO), foreign dignitaries, senior executive, Congressional and senior military leaders, and their respective staff. These missions are collectively referred to as Executive Airlift (EA).

1.4. Mission Essential Contractor Services

The following tasks are designated as mission essential.

Task 1: Flight Dispatch Services Task 2: En-route Flight Monitoring Task 3: Flight Operations Service Management Task 4: Dispatch Familiarization Course

1.5. Task Descriptions

The PWS includes the following tasks: flight dispatch services, en-route flight monitoring, Presidential Airlift Group, and flight operations management. The contractor shall provide

Designation Type IKO Base AS AW MAJCOM # Aircraft COR/POC C-32A 757-200 KADW Andrews 1st 89th AMC 4 Joe Flynn C-40B 737-700 KADW Andrews 1st 89th AMC 2 Joe Flynn C-40B 737-700 ETAR Ramstein 76th 86th USAFE 1 Capt Nicholas Varner C-40B 737-700 PHIK Hickam 65th 15th PACAF 1 Lt Col Pete Birchenough C-40C 737-700 KADW Andrews 201st 113th ANG 3 Capt Brian Meinhart C-40C 737-700 KBLV Scott 73d /54th 932d / 375th AFRC/AMC 4 Lt Col Barry Rutledge all services comparable with the Federal Aviation Administration’s (FAA’s) FAR 121 standard.

1.5.1. Flight Dispatch Services (TASK 1)

Flight dispatch includes the following subtasks: flight planning analysis, diplomatic clearance, Mission Planning Package delivery, mission review, Mission Planning Package update, calculating final Take Off and Landing Data (TOLD) and Weight and Balance (W&B) data, and “Paper the Crew.”

1.5.1.1. Flight Planning Analysis (Pre-Mission Execution)

Contractor shall receive tasking from the tasking agency Point of Contact (POC).

Contractor shall perform pre-execution mission analysis in order to ensure tasking is executable. Upon receipt of a tasking from the tasking agency, the contractor shall:

Perform an analysis of airfields and routes to be used on each sortie for the purposes of verifying airfield operational and physical suitability for listed aircraft type

Establish the suitability of the route of flight based on historic wind data Identify limiting factors relative to aircraft operations and performance Ensure Arrivals and Departures meet USAF Terminal Instrument Procedures

(TERPS) requirements.

The analysis and route development shall include potential/proposed en-route and destination alternate airfields (chock to chock). The analysis will be based on and compliant with:

Tasking Agency direction AFI’s: AFI 11-230, 11-202 Vol 3, and 11-2C-VIP Vol 3, AFI 11-2VIP V3, and

DoD Foreign Clearance Guide (FCG) Aircraft operations manuals and performance data Aircraft Takeoff & Landing Data (TOLD) and Weight & Balance (W&B) Extended Range Operations (ETOPS) Engine-Out Drift down Communication, Navigation, Surveillance/Air Traffic Monitoring (CNS/ATM) equipment compliance Flight crew operations manuals Central Flow Management Unit (CFMU) validation when applicable DOD Flight Information Publications (FLIP) o Foreign Clearance Guide (FCG) o Airfield Suitability and Restrictions Report (ASRR) o Giant Report o DOD Notice to Airmen (NOTAMS) o USAF/Air Force Reserve Command (AFRC)/Air National Guard (ANG)

Air Force Instructions (AFI) Diplomatic Clearances Suitable approach/departure procedures Applicable Jeppesen (and/or local) airspace/airfield charts and procedures

1.5.1.2. Diplomatic Clearances

Contractor shall create and sustain a program for obtaining and maintaining diplomatic clearances. Upon receipt of a tasking, contractor shall obtain required diplomatic clearances and/or use provided/projected clearances. The contractor shall maintain an Aircraft and Personnel Automated Clearance System (APACS) account with read/write access. Government will provide access or view permissions for each USAF/AFRC/ANG APACS account to the contractor. The contractor shall inform tasking agency POC promptly of any potential problems identified with securing diplomatic clearances.

1.5.1.3. Mission Planning Package

Upon completion of analysis contractor shall generate Mission Planning Package.

The Mission Planning Package shall include:

Flight plan for each leg to be flown Diplomatic clearances A consolidated analysis of aircraft performance capability at each location

1.5.1.4. Mission Review

Contractor shall perform a continuous review of each sortie up to and including 48 hours prior to the date and time of mission departure. The review shall confirm all aspects of the mission planning package and provide recommended solutions for any outstanding items. Any weather patterns that may impact mission execution shall be analyzed to ensure each sortie can be successfully completed within the allotted mission timing.

1.5.1.5. Mission Planning Package Update

Upon completion of mission review the contractor shall update the Mission Planning Package. Contractor and tasking agency POC shall have a shared responsibility discussion with the goal of arriving at routing decisions.

1.5.1.6. Calculate Final TOLD and W&B

Contractor shall use actual conditions to calculate TOLD and W&B data. Aircraft Communication Addressing and Reporting System (ACARS) menus shall display aircraft W&B function for pilot interface. The contractor shall provide the aircrew the ability to print results using ACARS Printer.

1.5.1.7. Flight Plan Filing

Contractor shall address filing issues and negotiate with Air Traffic Control (ATC) at all times for the tasking agency and successfully file a flight plan within five minutes of the crew notifying contractor of any issue.

1.5.1.8. Mission Planning Package Update (“Paper the Crew”)

Contractor shall complete and transmit via email (or fax upon request) an updated Mission Planning Package to the aircrew up to and including 4.5 hours prior to takeoff. The updated package shall confirm all aspects of the Mission Planning Package and provide recommended solutions for any remaining outstanding items.

Any updated weather patterns that may impact mission execution shall be analyzed to ensure each sortie can be successfully completed within the allotted mission timing.

The following new items shall be added:

Complete and file DD Form 1801 with ATC Digital filed flight plan request, ATC acknowledgement and change/amendment messages Text and graphic weather observations, charts and forecasts, and all relevant weather advisories/warnings, Pilot Reports (PIREPS), Significant Meteorological Information (SIGMETS), Airman’s Meteorological Information (AIRMETS)

1.5.1.9. Dispatcher-to-Pilot Briefing

Contractor shall verbally communicate and provide a physical written summary (or highlights) of issues that are associated with any part of the Mission Planning Package. Any unresolved issues or noteworthy performance issues or concerns should be highlighted in this briefing. The Mission Planning Package briefing shall include a FAR 121 or comparable dispatcher briefing.

1.5.2. En-route Flight Monitoring (TASK 2)

En-route Flight Monitoring includes the following subtasks: weather assessment, re-planning, safety of flight, and en-route Mission Planning Package update.

1.5.2.1. Weather Assessment

Contractor shall provide Enhanced Weather Information Systems Certified dispatchers capable of developing a tailored assessment relative to each flight and providing an assessment and necessary recommendations to the Pilot In Charge (PIC). The contractor shall:

Monitor weather conditions for airports utilized in the flight plan and notify the PIC when conditions are observed or forecast to be below minimums within two hours of arrival.

Provide continuous proactive flight following and ACARS/ Airborne Flight Information Service (AFIS) monitoring, always aware of the aircraft position in flight progress and proximity relative to adverse and unsafe meteorological or geological activity.

Advise the PIC of adverse and unsafe meteorological or geological activity immediately upon discovery with recommended courses of action to facilitate the utmost level of safety.

Provide en-route weather (SIGMETS, PIREPS, forecasts, etc.) and any other meteorological or dispatch information, upon request by the PIC.

Send Meteorological Terminal Aviation Routine Weather Report (METAR)/Terminal Aerodrome Forecast (TAF)/NOTAMs/En-route Winds/Descent winds via ACARS, to the PIC.

Monitor and provide updated ETOPS alternate and destination weather forecasts to the aircraft via ACARS/AFIS no later than 30 minutes prior to ETOPS airspace entry.

1.5.2.2. Re-planning

Contractor shall execute any actions for flight re-planning including revised diplomatic coordination if conditions require an adjustment to the route of flight or diversion, subject to coordination with PIC and/or tasking agency POC.

1.5.2.3. Safety of Flight

Contractor shall be prepared to execute any actions relative to flight operations that are requested by the PIC and/or ATC when such action is necessary to ensure safe operations.

1.5.2.4. En-route Mission Planning Package Update

Contractor shall complete and transmit an updated Mission Planning Package to the aircrew via email and/or ACARS while airborne.

1.5.3. Flight Operations Service Management (TASK 3)

Provide total program management support ACARS, all data subscriptions, and any subscription related services.

1.5.3.1. ACARS Ground Host Processing

Provide ACARS ground host service infrastructure. Contractor shall provide ACARS Ground Host Processing access and deliver service for each sortie. ACARS information to be transmitted includes the following:

METAR/TAF/NOTAM/En-Route Wind/Descent winds data retrieval En-route weather (SIGMETS/PIREP, Forecasts, and any other meteorology/dispatch information) Airport weather retrieval Text messaging capabilities including ACARS-to-email and aircraft-to-aircraft messaging Flight Management System (FMS) flight plan up-link/down-link capabilities Automatic ACARS initialization up-link messaging Route-specific customized weather briefing up-link Full-formatted flight plan up-link and filing strip to flight deck printer FMS position report trigger message uplink ACARS/AFIS/FMS position report support for flight monitoring and following Flight tracking/position reporting, automatic ACARS initialization Runway gross weight data Aircraft-specific weight and balance/performance data fuel alert function block-in/block-out report message "MISC" messages for new applications

1.5.3.1.1. Technical Support

Contractor shall provide the technical support necessary for onboard ACARS/FMS and Data Link Service Provider (DSP) menu set-up, software/label address routing lists, network and aircraft test script development and execution, software updates, and on-going technical management. Contractor is required to keep up to date with current standards and update process/support when standards change.

Contractor shall facilitate daily operations and management of uplink/downlink software configurations. Contractor shall serve as the “single point of contact” for all flight deck data communications problems.

1.5.3.2. SATCOM ORT Management

Contractor shall:

Coordinate with selected Satellite Communications (SATCOM) suppliers and fleet operators to assure aircraft registration, set-up, activation and sustaining service.

Provide for maintenance and update of aircraft SATCOM “Owner Requirements Table” (ORT) lists with suppliers and Inmarsat.

Provide ORT coordination with selected SATCOM suppliers, DSP’s, and fleet operators to assure certified ORT software and fleet aircraft communications system interface.

Provide troubleshooting coordination and phone maintenance services as required as part of ORT sustaining SATCOM service support of fleet aircraft SATCOM operations with suppliers and Inmarsat.

1.5.3.3. Onboard Performance Tool (OPT) Airport Database Management Contractor shall:

Coordinate with Government selected airport data service suppliers to set-up and manage operational use of the OPT Airport Database.

Provide required OPT hardware database / options set-up,…