TMQ-53_Section_L_Final-_RFQ_Amendment_0001_dated_22Oct14.pdf

Amendment 0001 22Oct14: Changes made to L7.3.4 Associate Contractor Agreements.

Section L-III - Information To Offerors (ITO) and Instructions For Proposal Preparation

L1.0 Program Structure and Objectives The objective of this effort is to solicit for Contractor Logistics Support to sustain the AN/TMQ-53 Tactical Meteorological Observing System in its approved configuration worldwide, while maintaining Fully Mission Capable (FMC) availability rates for systems operating in more than 20 different countries worldwide, and to accomplish the work requirements specified within the Performance Work Statement (PWS).

L2.0 General Instructions

L2.1 Proposal Compliance. The offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Request for Proposal (RFP), including all applicable attached documents. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

L2.2 Include Sufficient Detail. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The technical proposal must convey to the Government that the offeror possesses adequate technical expertise and experience, sufficient resources, and is able to plan, organize, and use those resources in a coordinated and timely fashion to meet the needs of the Government. The offeror’s proposal shall not simply copy and paste, rephrase or restate the Performance Work Statement (PWS) or Technical Order language for the technical volume 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 or experience and will base its evaluation on the information presented in the offeror's proposal.

L2.3 Embellishments Not Desired. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

L2.4 Proposal Acceptance and Validity Dates. 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 (9 (nine) months from RFP closing date).

L2.5 Disposition of Proposals. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals.

Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

L2.6 General Information

L2.6.1 Point of Contact The Contracting Officer (CO) and the Contract Negotiator are the only points of contact for this acquisition. Address any questions or concerns you may have to the CO or Contract Negotiator. Requests for clarification may be emailed to the CO or Contract Negotiator

AFLCMC/PZZKB

ATTN: Ms Michelle Esquivel Contracting Officer michelle.esquivel@us.af.mil 801-586-4693

AFLCMC/PZZKB

ATTN: Ms Lori Noble Contract Negotiator lori.noble2@us.af.mil 801-586-1233

L2.6.2 Debriefings Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable. The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to only one debriefing for each proposal. For unsuccessful offerors in the competitive range of the source selection, the CO will notify the offerors of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing.

L2.6.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 or Contract Negotiator by email 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.

L2.6.4 Electronic Reference Documents mailto:michelle.esquivel@us.af.mil mailto:lori.noble2@us.af.mil https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b15505 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b15506

All referenced documents for this solicitation will either be available on the Federal Business Opportunities (FedBizOpps) website at https://www.fbo.gov/ or through the CO or Contract Negotiator. Offerors are fully responsible for retrieving all information and updates on FedBizOpps.

L2.6.5 Offeror and Government Information Exchanges Exchanges of source selection information (i.e. questions and answers) between Government and offerors will be controlled by the CO and/or Contract Negotiator.

Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Otherwise, source selection information will be transmitted via direct mail. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted email, you will need to contact the CO and/or Contract Negotiator prior to that first submittal in order to exchange certificates used for encryption. To insure the process is working correctly, send a test encrypted message first (without including any source selection information). The CO may determine to conduct telephone exchanges when deemed appropriate by the Government. Do not email proposals. Proposals submitted only by email may result in an unfavorable proposal evaluation. See L2.8 for additional information.

L2.7 Organization/Number of Copies/Page Limits The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 2.2. The technical proposal, price proposal, and past performance volumes identified in the table shall be separately bound in three-ring, loose-leaf binders; the remaining volumes can be in one binder with a clear tab for each volume. However, for the electronic copy requested below, every volume shall be on a different CD-R. The paper and electronic copies shall be clearly identified.

The contents of each proposal volume are described in this section and summarized in the table below. Offerors shall include a Table of Contents in the proposal. In addition to the “Hard Copies” requested in Table 2.2 below, please submit one CD-R for each volume of the offeror’s proposal (not on CD-RW).

Table 2.2 - Proposal Organization

Volume

ITO

Paragraph Number

Volume Title Hard Copies

CD-R

Copies Page Limit

I 3.0 Executive Summary 2 1 5 II 4.0 Technical Proposal 6 1 200 III 5.0 Price Proposal 3 1 Unlimited IV 6.0 Past Performance 3 1 25 https://www.fbo.gov/ https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc%23T2101 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b3104

V 7.0 Contract Documentation 2 1 Unlimited

L2.7.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 either returned to the offeror or disposed of as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. When both sides of a sheet display printed material, it shall be counted as 2 pages. In the event that an offeror includes fold-out pages, the folded-out portion shall be counted the same as an 8.5 x 11 sheet. Each page shall be counted except the following:

cover/title pages, tables of contents, tabbed dividers, acronym lists, RFP Cross Reference Matrix (RCRM), and glossaries.

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

Proposals shall be prepared using a minimum Arial 12 point font on 8.5” x 11” white paper, not including foldouts. Pages shall be typed using 1.5 line spacing. Use at least 1 inch margins on the top and bottom and ¾-inch side margins. Offerors shall ensure that each page provides identification of the submitting offeror and solicitation number in the header or footer. Pages shall be numbered sequentially by volume.

The page size and format restrictions shall apply to responses to ENs. 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 shall fold entirely within the volume, and each 8.5 x 11 surface of a foldout shall be counted as a separate page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text font size shall be no smaller than Arial 8 point font.

These limitations shall apply to both electronic and hard copy proposals.

L2.7.2 Pricing Related Data All pricing information shall be addressed ONLY in Volume III Price and Volume V Contract Documentation. All amounts provided in response to these instructions shall be rounded to the nearest whole U.S. dollar.

L2.7.3 Classified Information Classified information SHALL NOT be provided in the offeror’s response to this RFP.

L2.7.4 Cross-Referencing To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal, except for cross-referencing directed herein. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The offeror shall fill out the RFP Cross Reference Matrix (RCRM) at Attachment L1 to specifically detail and correlate the RFP requirements to the offeror’s proposal.

Offerors shall document in sufficient detail allowing evaluators to easily follow the offeror’s proposal and match the proposal to the requirements of the RFP. The cross-reference matrix shall reference the Proposal, PWS, Contract Line Item Number (CLIN), Section L, Section M, CDRLs, and Model Contract. The RCRM is not included in the volume page count.

L2.7.5 Indexing Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

L2.7.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 are not included in the volume page count.

L2.7.7 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 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. Make sure to apply all appropriate markings to proposal data 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).

L2.8 Electronic Offers The content and page size of electronic copies must be identical to the hard copies in all respects. Electronic copies are defined as CD-R copies. Email proposals will not be considered an electronic copy. The electronic copies shall be submitted on a single, virus free, read-only CD-R in either Adobe PDF or Microsoft Word 2010 compatible formats. Indicate on each CD-R the volume number and title. Note that CD-RWs cannot be read, evaluated, or considered, and shall either be returned to the offeror or disposed of as soon as practicable. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any.

The offeror shall submit volumes Ithrough V in electronic format, using CD-Rs. Each volume shall be on a different CD-R. If files are compressed, the necessary decompression program must be included. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc%23b522151 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b31044

L2.9 Distribution The "original" proposal shall be so designated and signed by the offeror’s authorized representative, and the copies should be identified appropriately. All requested copies must be received by the due date identified on the front page of the RFP. Proposals shall be addressed to the CO and delivered to:

AFLCMC/PZZKB

ATTN: Ms Michelle Esquivel Contracting Officer 6039 Wardleigh Road, Bldg 1206 Hill AFB, UT 84056-5838 michelle.esquivel@us.af.mil 801-586-4693

Include Solicitation Number FA8217-14-R-5009 on the address label.

L2.10 Federal Holidays The following Federal Legal Holidays are observed by this base:

New Year’s Day 1 January Martin Luther King’s Birthday Third Monday in January Presidents Day Third Monday in February Memorial Day Last Monday in May Independence Day 4 July Labor Day First Monday in September Columbus Day Second Monday in October Veterans Day 11 November (if Nov 11 falls on a Sunday, then it is observed on the following Monday) Thanksgiving Day Fourth Thursday in November

Christmas Day 25 December

L2.11 Proposal Submissions Offerors should allow for sufficient time to deliver all proposal information. Offerors are responsible for submitting proposals, and any modification, or revisions, so as to reach the Government office designated in the solicitation by the time specified in the solicitation. Any proposal, modification, or revision received at the Government office designated in the solicitation after the exact time specified for receipt of offers is “late” and will not be considered. Late proposals will handled in accordance with FAR 52.215-1.

L2.12 Proposal Quality Proposal must be written in a logical, practical, clear and concise manner and contain all pertinent information in sufficient detail to provide the evaluators with a clear understanding of the offeror’s approach and to permit evaluation of the proposed program. It is the responsibility of the offeror to present enough information to allow the various work efforts, support, and management approaches to be meaningfully evaluated without discussions. The offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions. In presenting material in this proposal, the offeror is advised that quality of information is more important than quantity. Offerors are encouraged to use quantitative terms wherever possible and avoid the use of qualitative and subjective terms to the maximum extent practicable. A proposal must be internally consistent or the proposal will be considered unrealistic and may be considered unacceptable. Proposals must clearly and convincingly demonstrate that the offeror has a thorough understanding of the requirements and associated risks, and is able, willing, and competent to devote the resources necessary to meet the requirements and has valid and practical solutions for all requirements.

L3.0 Volume I - Executive Summary

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

L3.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 price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

L3.2 Table of Contents Include a master table of contents of the entire proposal.

L4.0 Volume II - Technical Proposal

L4.1 General The Technical Proposal shall be clear, specific, complete, and include sufficient detail for effective evaluation. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your company will perform all the requirements specified in the solicitation/PWS. 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.

L4.2 Format and Specific Content L4.2.1 Technical In the technical volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor.

L4.2.2 Volume Organization The Technical Volume shall be organized according to the following general outline:

Table of Contents List of Table and Drawings Glossary RFP Cross Reference Matrix (RCRM) Factor 1 Technical Tab A – Subfactor 1: Management Approach and Transition Tab B – Subfactor 2: Technical Approach Tab C – Subfactor 3: Staffing Plan

L4.3 Technical Capability Factor

L4.3.1 Subfactor 1: Management Approach and Transition:

The offeror shall address their technical risk separately in each plan in this subfactor using established risk management processes. Address technical risks associated with those aspects of your proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Classify each risk in accordance with the Technical Risk Ratings table in Section M4.3.1. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: PWS requirements), whether or not those requirements are identified as subfactors. Propose a realistic "work-around" or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation. The Government evaluators will make the final determination of the Technical Risk Rating assigned in the evaluation.

L4.3.1.1 Program Management Plan (PMP). This subfactor evaluates specific elements of the offeror’s PMP, which shall detail the approach and plan by which the offeror will effectively execute the requirements of the PWS. The offeror shall prepare the following elements of the PMP in the same format as CDRL A001 (PWS Section 5.1):

1. A support concept and Spares Management Program (PWS Section 6.3.1)

2. Repair Management Process (PWS Section 6.4)

3. Transportation Plan (PWS Section 6.8)

4. A management process to ensure high quality sustainment support services throughout the term of this contract (PWS Section 5.1)

L4.3.1.2 Transition Plan. This subfactor evaluates the offeror’s detailed and comprehensive Transition Plan, which shall be incorporated into the contract. The transition plan shall contain a narrative discussion describing the offeror’s transition phase-in approach and ability to achieve full contract performance at the end of the specified phase-in period in accordance with PWS Section 4.1. The detailed, sound, and comprehensive narrative shall include the following information:

1. A plan and milestone chart to manage and accomplish a seamless contract phase-in process and employee orientation to ensure successful contract performance at the end of the specified phase-in period.

2. A comprehensive, realistic, overall strategy to include timeframes, inventory relocation, capital investment considerations, including installation of indoor and outdoor components of the mock-ups from incumbent contractor

3. A plan for coordinating with the Government for the transfer and accounting of Government Furnished Property and Equipment.

4. A reasonable methodology to maintain the AN/TMQ-53 at an availability up-time-ratio (UTR) of 96% on day 1 after transition is complete

L4.3.1.3 Proof of ISO 9001 or Offeror’s Plan to Obtain ISO 9001. The offeror shall provide evidence of ISO 9001 certification or a plan for achieving certification within six months of contract award. In addition, the offeror shall provide a plan for keeping the ISO certification current (e.g., ISO 9001:2015).

L4.3.2 Subfactor 2: Technical Approach For this subfactor, offerors shall submit responses to the three Sample Scenarios below. The Sample Scenarios are representative of the types of situations that have arisen for the AN/TMQ-53 program in the past and may arise in the future. The Sample Scenarios will be used for evaluation purposes only. Scenarios are not awardable taskings.

L4.3.2.1 Sample Scenario #1: Shipping (See Attachment L2)

The offeror’s response to Sample Scenario #1 shall describe the processes, analysis, and rationale that determine the selected actions for the sample scenario. The offeror shall describe in their response all actions needed to resolve the situation and what actions they will take to support the Government. The solution shall define the issue, incorporate all appropriate documentation and provide full implementation details. The offeror’s solution shall be complete and clearly demonstrate that the offeror has sufficient familiarity, corporate experience, technical expertise and competence to accurately, effectively and efficiently understand, and interpret shipping and customs regulations in order to perform shipping tasks in accordance with section 6.2.4 of the PWS. The offeror shall ensure their response includes all of the information outlined in the RESPONSE section of Scenario #1.

L4.3.2.2 Sample Scenario #2: Obsolescence (See Attachment L3)

The offeror’s response to Sample Scenario #2 shall describe the processes, analysis, and rationale that determine the selected actions for the sample scenario. The offeror shall describe in their response all actions needed to resolve the situation and what actions they will take to support the Government. The solution shall define the issue, incorporate all appropriate documentation and provide full implementation details. The offeror’s solution shall be complete and clearly demonstrate that the offeror has sufficient familiarity, corporate experience, technical expertise and competence to accurately, effectively and efficiently update the AN/TMQ-53 hardware configuration baseline (IAW PWS requirements) with an Iridium modem that meets all of the requirements of the TRD and does not degrade the Operational Safety, Suitability & Effectiveness of the AN/TMQ-53. The offeror shall ensure their response includes all of the information outlined in the RESPONSE section of Scenario #2.

L4.3.2.3 Sample Scenario #3: Software Upgrade (See Attachment L4)

The offeror’s response to Sample Scenario #3 shall describe the processes, analysis, and rationale that determine the selected actions for the sample scenario. The offeror shall describe in their response all actions needed to resolve the situation and what actions they will take to support the Government. The solution shall define the issue, incorporate all appropriate documentation and provide full implementation details. The offeror’s solution shall be complete and clearly demonstrate that the offeror has sufficient familiarity, corporate experience, technical expertise and competence to accurately, effectively and efficiently update the AN/TMQ-53 software configuration baseline (IAW PWS requirements) with a new operating system and new Automated Observing System (AOS) software that meets all of the requirements of the TRD and does not degrade the Operational Safety, Suitability & Effectiveness of the AN/TMQ-

53. The offeror shall ensure their response includes all of the information outlined in the RESPONSE section of Scenario #3.

L4.3.3 Subfactor 3: Staffing Plan This subfactor evaluates the detailed Staffing Plan, which will be incorporated into the contract. The Staffing Plan shall provide the offeror’s intended team structure, including partnerships, which demonstrate how the offeror will provide the required level of skills and experience to perform the Contractor Logistics Support (CLS) services for this contract.

The plan shall demonstrate key personnel with at least three continuous years of experience in the past five years in the following areas: Shipping/Customs (PWS Sections 6.2, 6.8), Obsolescence (PWS Section 7), Iridium (PWS Section 6.3.3), Information Assurance (PWS Section 8), Technical Manuals (PWS Section 9), Helpdesk troubleshooting (PWS Section 6.2), software integration (PWS Section 7), and experience supporting tactical systems. In addition the plan will outline experience with Automated Observation System (AOS) Software (PWS Section 8.1) and Item Unique Identification (IUID) Markings (PWS Section 6.7); however, the experience need not reflect at least three continuous years in a row of experience in the past five years for those two elements. Key personnel are defined in PWS Section 5.2.

In addition, the offeror’s Staffing Plan shall provide the following:

1. Team organization – The offeror shall provide a team organization chart with written rationale for the organizational structure by shift, skill mix, function, and numbers, that the offeror will use to meet PWS requirements (detailing the roles, responsibilities and capabilities of all team members, including subcontractor, supplier, and interdivisional team). The plan shall include a staffing matrix to PWS requirements and an explanation of the relevance of skills and prior experience in CLS services specifically related to weather systems of the team, as well as their interdependencies, relationships, and communication channels.

The plan shall include a sound and comprehensive plan to hire, train, maintain and retain qualified staff from contract start and throughout the period of performance to meet all PWS requirements. The plan shall provide an adequate description of the teaming arrangements with any subcontractors or joint ventures including the organizational relationship and the lines of responsibilities between the prime and subcontractors.

2. Key Personnel Skill Level and Experience – The offeror shall provide skill level, education, and prior experience in CLS services specifically related to weather systems of key personnel. The plan shall include resumes for key personnel reflecting their roles/responsibilities, required education, experience, certification, and qualifications needed to comply with PWS requirements.

Provide resumes for all key personnel as a separate attachment to the Technical Volume to substantiate the experience. Key personnel meeting this experience requirement do not have to be current employees. Offeror shall detail how it will address transition of key personnel to maintain expertise and continuity. Changes to resumes of key personnel at time of award must include equivalent personnel of the same or substantially similar background experience.

3. Skill Sets and Experience – Provide the blend of skill sets and CLS services specifically related to weather systems experience levels for the remainder of personnel.

L5.0 Volume III - Price

L5.1 General Instructions The primary purpose of the price proposal volume is to provide the CO and the price team evaluators an understanding of how the price proposal was developed. The price evaluation criteria of completeness, reasonableness, balance, 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.

L5.1.1 Total Evaluated Price (TEP) Attachment L10 is the Pricing workbook containing TEP worksheets and will be populated by the offeror in accordance with the worksheet’s instructions. Prices in the worksheet shall match pricing from information proposed in the line item schedule of the solicitation. The TEP is for award determination purposes only and will be a consideration in the best value award decision. The prices/rates proposed in the Pricing workbook will be incorporated into the contract at time of award.

The TEP for this acquisition will be established by adding together the firm-fixed price CLINs, (including the six-month option to extend services (clause 52.217-8)), as described below.

CLIN 0001, Contractor Logistics Support (CLS) CLIN 0002, Repairs CLIN 0003, Spares CLIN 0004, Software Licenses CLIN 0005, TMQ-53 Systems CLIN 0006, Contract Data Requirements List (CDRLs) CLIN 0007, Project Management CLIN 0008, Travel (shall be under a Cost Reimbursable – No Fee CLIN and will not be evaluated as part of the proposal) CLIN 0009, Shipping (shall be under a Cost Reimbursable – No Fee CLIN and will not be evaluated as part of the proposal) CLIN 0010, Transition

The total TEP will be the price factor in determining which offeror’s proposal represents the best value to the government. Consequently, the offeror submitting the “best value” proposal will be the successful contract awardee.

L5.1.2 Estimating Techniques and Methods: When responding to the Pricing 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.

L5.1.3 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 Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

L5.1.4 Pricing Data Requirements 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 additional pricing data.

L5.1.5 Rounding All dollar amounts provided shall be rounded to the nearest whole U.S. dollar.

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154031 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154033 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154035 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154031

L5.2 Volume Organization The Price volume shall consist of the following sections:

SECTION 1 - Table of Contents; summary descriptions of estimating, purchasing, and accounting systems; changes to estimating, and accounting practices, if applicable.

SECTION 2 – Data other than certified cost or pricing data, to include estimating methodology.

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

SECTION 4 - The offeror will complete the Excel file, “TMQ-53 Pricing Workbook” IAW in the instructions. This completed workbook will be utilized to develop the TEP. The TEP is for award determination purposes only and will be a consideration in the best value award decision.

L6.0 Volume IV - Past Performance

L6.1 General Each offeror shall submit a Past Performance Volume with their proposal, containing relevant and recent present and past performance information. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who the offeror proposes to perform 10 percent or more of the effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. The Government may contact the points of contact provided by the offeror for the purpose of ascertaining and/or clarifying past performance information. In addition to the data provided in this volume, the Government will use the Contractor Performance Assessment Reporting System (CPARS) and/or similar systems of other Government departments and agencies, questionnaires tailored to the circumstances of this acquisition, Defense Contract Management Agency (DCMA) channels, interviews with Program Managers and COs, and other sources known to the Government, including commercial sources. Past performance will only be reviewed from the lowest priced, technically acceptable offeror.

L6.1.1 Format and Specific Content Offerors may submit a maximum of five (5) recent and relevant contracts for the prime contractor and a maximum of three (3) recent and relevant contracts for it’s proposed key subcontractors. Format and Content is explained in each section/attachment below.

Offeror shall provide a portion of Past Performance information electronically via PPI Tool in FedBizOpps (See Attachment L5).

L6.1.2 Volume Organization The Past Performance Volume shall be organized according to the following general outline:

Table of Contents Summary Table Consent Letters Client Authorization Letters Roles and Responsibilities Worksheet Organization Structure Change History Glossary

L6.2 Consent Letter The offeror shall submit a Consent Letter (Attachment L6) executed by each key subcontractor, teaming partner, and/or joint venture partner identified on the Roles and Responsibilities Worksheet (Attachment L9) authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. A Consent Letter is provided because 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 key subcontractors and/or teaming partners that will perform major or critical aspects of the requirement, consenting to the release of their past performance information to the prime contractor.

L6.3 Client Authorization Letter For each identified effort for a commercial customer, the offeror shall also submit a Client Authorization Letter, contained in Attachment L7, authorizing release to the Government of requested information on the offeror's performance.

L6.4 Past Performance Questionnaire Offerors shall send a Past Performance Questionnaire, contained in Attachment L8, directly to the POCs for the efforts identified. All respondents shall be instructed that responses are to be provided directly to the Government CO not later than 27 October 2014.

L6.5 Recent and Relevant Contracts Recent as it pertains to past performance information, is defined as within three (3) years from the date of issuance of this solicitation. Relevant, as it pertains to past performance information, is defined as the extent of the similarity between the service/ support effort, complexity, dollar value, contract type and subcontract/ teaming or other comparable attributes in areas related to Contractor Logistics Support. Offerors shall provide rationale supporting its assertion of relevance. The rationale shall explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. Categorize the relevant information into the specific Technical subfactors and Price factor used to evaluate the proposal. The offeror shall submit past performance information for a maximum of five recent contracts that are most relevant in demonstrating the offeror’s ability to perform the proposed effort. The offeror shall also include information for a maximum of three recent contracts performed by each of the teaming partners and significant subcontractors that are considered most relevant in demonstrating their ability to perform the proposed effort.

For additional descriptions of the characteristics or aspects the Government will consider in determining recency and relevancy, see Section M, paragraph M4.0 – Technical Capability and paragraph M6.0 - Past Performance.

L6.6 Other Performance Confidence Considerations Merely having problems does not automatically equate to an unacceptable past performance evaluation rating. 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. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. Problems not addressed by the offeror, but found by the Government during the evaluation of the information in this volume, will be assumed to still exist. Note: In the case of Contractor Performance Assessment Report System (CPARS), if the offeror’s input has already been provided and the rationale/circumstances have not changed, DO NOT repeat them.

L6.7 Organizational Structure Change History Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of the offeror’s 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 the offeror identifies 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), the offeror’s "roadmap" should be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources.

L7.0 Volume V - Contract Documentation

L7.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 solicitation, and any applicable amendments.

L7.1.1 Section A - Solicitation/Contract Form Completion of OFFER, blocks 12-18, ensuring authorized signature by the offeror.

L7.1.2 Section B - Supplies or Services and Prices The offeror shall not complete Section B, but refer to Section 5 for instructions for completing the TEP. The contract clauses pertinent to this section and that are required to be filled-in will be completed on each individual task order.

L7.1.3 Section F - Deliveries or Performance Alternate delivery schedules are not acceptable as this is an Indefinite Delivery/ Indefinite Quantity award. Failure to meet the solicitation’s required delivery will result in ineligibility for award. Specific delivery requirements shall be addressed in each resulting Task/Delivery order placed under the resulting contract.

L7.1.4 Section G - Contract Administrative Data Upon Award, Section G data will be provided by the Government.

L7.1.5 Section H - Special Contract Requirements The contract clauses pertinent to this section and that are required to be filled-in will be completed in Section H of each individual task order.

L7.1.6 Section I - Contract Clauses

L7.1.7 Section K - Representations, Certifications, and other Statements of Offerors Completed representations, certifications, acknowledgments and statements.

L7.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. 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, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 7.2.

Table 7.2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion Rationale

PWS, Model Contract, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

L7.3 Other Information Required

L7.3.1 Authorized Offeror Personnel Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to the offeror’s proposal and who can obligate the offeror’s company contractually. Also, identify those individuals authorized to negotiate with the Government.

L7.3.2 Government Offices Provide the mailing address, telephone and email addresses, and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office.

Also, provide the name and telephone and email addresses for the Administrative Contracting Officer (ACO).

L7.3.3 Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; CAGE code;

DUNS code; TIN; and Small Business size status. 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.

L7.3.4 Associate Contractor Agreements (ACA) Provide statement of intent to submit Associate Contractor Agreements in accordance with AFFARS 5317.90. Once an award is made, the ACA will be required within 10 days after award and inserted into the contract as an attachment by modification.

L8.0 List of Attachments: Section L attachments listed below are provided as separate files.

Attachment L1: Cross Reference Matrix Attachment L2: Sample Scenario #1 – Shipping Attachment L3: Sample Scenario #2 – Obsolescence Attachment L4: Sample Scenario #3 – Software Upgrade Attachment L5: Past Performance Information Tool Attachment L6: Subcontractor/Teaming Partner Consent Letter For The Release Of

Past And Present Performance Information To The Prime Contractor Attachment L7: Sample Client Authorization Letter Attachment L8: Past Performance Questionnaire Attachment L9: Roles and Responsibilities Worksheet Attachment L10: TMQ-53 Pricing Workbook

Section L, Attachment L1 Instructions to Offerors Cross Reference Matrix

See Section L, Paragraph 2.7.4 regarding specific instructions for completion of the solicitation Cross Reference Matrix. If this matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over this matrix. Additionally, to the extent this matrix discloses details as to the extent or manner by which the Government intends to evaluate Offeror’s proposals for award, Section M references in the matrix are for information purposes only and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of Section M of the solicitation.

Evaluation Subfactors

PWS/

CDRLs Section

L Section

M CLIN

Model

Contract Proposal Subfactor 1:

Management Approach and Transition Program Management Plan Transition Plan ISO 9001 Plan Subfactor 2: Technical Approach Sample Scenario #1 – Shipping Sample Scenario #2 – Obsolescence Sample Scenario #3 – Software Upgrade Subfactor 3: Staffing Plan

Section L, Attachment L2

SAMPLE SCENARIO #1 - SHIPPING

BACKGROUND: The AN/TMQ-53 is currently deployed in Niger, Africa. Performing contractual requirements becomes more difficult in remote locations and special considerations are needed in regards to customs, shipping documentation, costs, schedule, etc. This includes the return shipping of the repairable part being replaced, which at times can be expensive, and confusing.

For this scenario, assume that MIL-Air Shipping is not available.

PURPOSE: Describe your approach to shipping parts to and from remote and difficult to reach locations in this scenario, Niger, Africa. Demonstrate specific information for replacing a broken ceilometer.

PWS APPLICABILITY: The tasks in this sample scenario are within the scope of the Contractor Logistics Support (CLS) Contract for the AN/TMQ-53 Tactical Meteorological Observing System (PWS Section 6.8)

RESPONSE: In your response to the scenario, address the following areas:

• A detailed description of how you would use the Transportation Plan required by

PWS Section 6.8 to ship to Niger, Africa, include:

o A description of how you would implement and manage all commercial transportation for shipment of systems and spares.

o A detailed explanation of how the contractor will ship and receive parts.

o A description of all customs documents, processes and procedures required to ship to Niger.

• Demonstrate that time requirements for shipping adhere to Section 6.2.4 of the

PWS.

• Provide performance and cost reports showing all necessary information as it relates to replacing a broken ceilometer to and from Niger, Africa that adhere to PWS Section 5.4.

• Clearly state all assumptions used in your response.

Section L, Attachment L3

SAMPLE SCENARIO #2 – OBSOLESCENCE

BACKGROUND: The OEM of the Iridium modem has subcontracted to different manufacturers and the government has become suspicious that certain of those…