52.212-1_Addendum_updated.docx

FA810119RA010

52.212-1 ADDENDUM

INSTRUCTIONS TO OFFERORS (ITO)

ADDENDUM TO FAR 52.212-1

INSTRUCTIONS TO OFFERORS

1.0 Program Structure and Objective

1.1. The Government plans to award a single performance-based contract for the Paramedics/Ambulance Services program at Tinker Air Force Base (AFB), Oklahoma. The contract 24 hour on-base state certified paramedic level emergency response and patient transport services for all personnel on Tinker AFB. In addition the contractor will be responsible for the following off base facilities as described in the Performance Work Statement (PWS). This shall include afterhours flight line response, participation in all readiness exercises, real world events, and stand-by response for special events (such as: change of command, air shows, athletic events, live fire training, etc.). Contractor shall furnish all labor, management, supervision, vehicles, supplies, equipment, transportation, and reports, except as provided in paragraph 3, government furnished property and services. Contractor care shall cover the range of paramedic and ambulance services provided in the local community. Performance shall be according to the requirements contained in the PWS, professional standards of the Joint Commission on Accreditation of Healthcare Organization (JCAHO), AFI 44-119-Clinical Performance Improvement, the Department of Transportation (DOT) and the National Registry for Emergency Medical Technicians (NREMT). The contractor shall participate in flight line hazard or mishap response planning. The contractor shall reside on base and provide back-up ambulance support during responses/transports.

1.2. Award will be made on the basis of “best value” utilizing Tradeoff Source Selection Procedures. Award will be made to the contractor that provides the “best value” to the Government over the entire period of performance.

1.3. Budget/Funding Information

Funding will be obligated for the Firm-Fixed-Price (FFP) Contract Line Item Number (CLINs) for the base period. The awarded contract will include a transition period (up to 30 days) and a nine month base period with four (4) one-year options. The transition period is not separately priced.

2.0 General Instructions

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

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

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

2.1.4. 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 until this date.

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

2.2. General Information

2.2.1. Point of Contact

The Contracting Officer (CO) and the Contract Administrator (CA) listed below are the only points of contact for this acquisition. Address any questions or concerns you may have to the aforementioned individuals. Written requests for clarification may be sent to the CO or CA at the following email addresses:

Sherri Croak, Contracting Officer, sherri.croak@us.af.mil Rachel Gordon, Contract Administrator, rachel.gordon.1@us.af.mil

2.2.2. Debriefings

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

2.2.3. Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions. This reservation includes matters of additional or substitute pages of the initial proposal.

2.2.4. Electronic Reference Documents

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

2.2.5. Amendments to Solicitation

If this RFP is amended, all terms and conditions that are not amended remain unchanged and in full force and effect. Offerors shall acknowledge receipt of any amendment and provide confirmation upon submission of the offeror’s proposal. Any unacknowledged amendments in the offeror’s proposal are subject to solicitation provision FAR 52.212-1(f).

2.2.6. Submission, Modification, Revision, and Withdrawal of Proposals Proposals and modifications to proposals shall be submitted in sealed envelopes or packages in paper media and electronic media addressed to the CO at the address shown in Section A of the model contract/solicitation, and showing the time and date specified for receipt, the solicitation number, and the name and address of the offeror.

2.3. Organization/Number of Copies/Page Limits

2.3.1. The Title Page of each volume must show solicitation number, name, address, and telephone and of the offeror and e-mail address if available.

2.3.2. A Team List of the offeror’s primary Point of Contacts shall be submitted in each volume using the format shown in Attachment 2 of the ITO.

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

Table 1 Proposal Organization

Volume

ITO

Paragraph Number

Volume Title Hard Copies/ Disk Copies

Page Limit

Unlimited

Unlimited

Unlimited

3.2.3 3.2.4 Subfactor 1 Technical: Resource Management Subfactor 2 Technical: Quality Control Plan

Unlimited

Unlimited

Tab Only

Request Max 5 pages per contract

Unlimited

Unlimited

Unlimited

Unlimited

Unlimited

Unlimited

N/A

N/A

Unlimited

Unlimited

2.3.4. Page Limitations

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

2.3.5. Pricing Information

All pricing information shall be addressed ONLY in the Price Proposal and Contract Documentation volumes.

2.3.6. Cross Referencing

The Technical 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 the technical proposal evaluation, which is not found in the Technical volume, will be assumed to have been omitted from the proposal, and will not be considered in the technical evaluation. Cross-referencing within a proposal volume is permitted when its use would conserve space without impairing clarity. The Past Performance and Price evaluation will utilize information from each’s respective volume for the evaluation, but may also utilize information from other volumes as well.

2.3.7. Indexing

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

2.3.8. Include an indexed list of Tables and Figures.

2.3.9. Glossary of Abbreviations and Acronyms

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

2.4. Page Size and Format

2.4.1. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Page line spacing shall be 1.5 lines. Except for the reproduced sections of the solicitation document, the text size shall be no less than Arial 12 points. Tracking, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to Evaluation Notice (ENs). These limitations shall apply to both electronic and hard copy proposals.

2.4.1. 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 and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. The following limitation only applies to the Technical Volume. Text intended for evaluation within all figures, charts, tables, and graphs, to include imbedded images, shall be no less than Arial 8-pt. These limitations shall apply to both electronic and hard copy proposals. Any text within figures, charts, tables, and graphs which do not meet this requirement will not be considered in the evaluation. These limitations shall apply to both electronic and hard copy proposals.

2.5. 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. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.6. Electronic Offers

The content and page size of electronic copies should be identical to the hard copies. In such cases where a discrepancy exists between the written hard copy and electronic copy, a clarification EN may be issued to allow offerors the opportunity to make both versions consistent with each other. For electronic copies, indicate on each Compact Disc Read Only Memory (CD-ROM) the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, required plans, exhibits, appendices, and attachments, if any. The offeror shall submit volumes I through IV in electronic format. Each volume shall be submitted on a separate CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Word, MS Excel, and MS-Power Point.

2.7. Distribution

The "original" proposal shall be clearly identified. Proposals shall be addressed to the Contracting Officer and mailed to:

DEPARTMENT OF THE AIR FORCE

AFSC/PZIOA ATTN: SHERRI CROAK

3.0 Factor 1 – Technical

3.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 Addendum to FAR 52.212-2, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is neither necessary nor desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

3.2. Format and Specific Content

3.2.1. Technical

In the Technical Volume, address your proposed approach to meeting the minimum performance or capability requirements of each technical subfactor. The Offeror, and subcontractors as required, must provide original copies of their approved state license/certification to provide ambulance services from the Oklahoma State Department of Health EMS Division to be considered for the technical evaluation. (NOTE: Failure to provide the required license/certification with the original proposal will result in the Offeror being uanawardable. Also, the Government will not accept proposals that state required license/certifications will be obtained prior to contract award or prior to commencement of full performance.)

3.2.2. Volume Organization

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

(1) Team List Attach 2.0

(2) Table of Contents

(3) List of Table and Drawings

(4) Glossary

(5) Licenses/Certifications

(6) Subfactor One – Resource Management

(7) Subfactor Two – Quality Control

3.2.3. Subfactor One: Resource Management

The Offeror shall provide an approach for Resource Management for the Paramedic/Ambulance Services program. As a minimum, the approach shall provide the following essential components:

a) An approach for manpower and organization. As a minimum, the proposal must describe the Offeror’s organization chart to include manning numbers and identifying positions. The proposal shall also include an approach for hiring and training of personnel as well as an approach for sustaining proposed manpower levels during the life of the contract. To be acceptable, the offeror must demonstrate an understanding of the required Emergency Medical Technician (EMT) training, certifications, licensing, experience, education and health requirements for all EMT personnel IAW PWS paragraphs 1.18, 1.19, 1.20, 1.21, 1.22 and 1.23. The offeror must also demonstrate an effective process to recruit, train, and retain a qualified and capable workforce throughout the life of the contract.

b) A transition approach to manage and accomplish contract transition, orientation and phase in. As a minimum, the approach must include a critical path analysis of transition milestones. To be acceptable, the offeror must demonstrate an effective approach to complete all workforce requirements IAW PWS paragraph 1.17.

c) An approach for emergency response procedures. As a minimum the approach must include how the offeror intends to perform Oklahoma Emergency Medical (EMS) pre-hospital care protocol and Ambulance Response. To be acceptable, the offeror must demonstrate an effective approach for EMS and Ambulance Response IAW PWS paragraphs 1.8 and 1.9.

d) An approach for preparing and providing patient information and documentation. As a minimum, the approach must demonstrate how the offeror intends to comply with MTF established standards and procedures. To be acceptable, the offeror must demonstrate an effective approach for patient information and documentation IAW PWS paragraphs 1.10, 1.11, 1.12, 1.14, and 1.15.

3.2.4. Subfactor Two: Quality Control

The offeror shall provide their proposed approach to providing quality control and the submittal of a feasible Quality Control Plan suitable as a compliance document upon award. The Quality Control Plan will be evaluated based upon the proposed approach of accountability for all work. The plan should include, but not be limited to, the areas identified in PWS.

a) An acceptable quality control procedures to be used to satisfy the requirements identified in Basic Service listed within the Performance Work Statement. PWS 1.26

b) An adequate plan to identify the functional areas to which all Quality Control and/or inspection personnel (at all levels) will be assigned. In addition, adequate identification of all management/supervisory quality positions.

4.0. Factor 2 – Past Performance

4.1. General

4.1.1. Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 1.1 of the ITO. The Past Performance volume shall include a team list, which includes the prime contractor, all significant subcontractors, teaming partners, and/or joint venture partners proposed to perform the work outlined in the solicitation. The offeror shall describe the portion of effort each team member is proposed to perform in relation to the Factor 1 Technical subfactors, Factor 3 Price, and Scope, Magnitude and Complexity. The Government Past Performance Evaluation Team (PPET) evaluates each member of the offeror’s team for relevancy and performance, based on their proposed portion of effort. Therefore, it is important for the offeror to provide a detailed portion of effort description, in order for the PPET to conduct an accurate assessment. Offerors shall also provide approximate percentages for portion of effort for each team member. For the Past Performance evaluation, the Government will use data provided by the offeror in the Past Performance volume, as well as data obtained from other sources.

4.1.2. Along with the information required in this paragraph, the offeror shall submit a consent letter (Attachment 1.4) 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 1.5) authorizing release to the Government of requested information on the offeror’s performance.

4.2. Early Proposal Information

4.2.1 Each offeror is requested to submit the Past Performance volume five (5) calendar days prior to the solicitation closing date. The Past Performance volume early proposal information is a request and not a requirement. Failure to submit early proposal information will not result in offeror disqualification, nor will offerors be penalized.

4.2.2. As soon as practicable, offerors shall complete Section 1 of the attached Past Performance Questionnaire (Attachment 1.2) and e-mail it and the Performance Questionnaire Letter (Attachment 1.3) to all points of contacts (POCs) the offeror has listed in the Past Performance Information Form (Attachment 1.1). The POCs will complete the questionnaires and forward them directly to the Past Performance Evaluation Team (PPET). (Attn: Sherri Croak). Email address for questionnaires is sherri.croak@us.af.mil. RESPONDENTS TO THE QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION SHEETS BACK TO THE OFFEROR. Offerors shall not follow-up with respondents to ensure they have completed the questionnaires. The PPET will conduct such follow-up with any POC as necessary.

4.3. Relevant Contracts

4.3.1. The offeror shall provide Past Performance Information (PPI) on current or previous contracts (or efforts). The PPI shall be completed in accordance with Addendum to FAR 52.212-1, Attachment 1.1, Past Performance Information Form (identified in this document as “PPIF”). The offeror shall submit PPIFs for contracts which include all or some performance within the past three years, as defined in Addendum to FAR 52.212-2, para 2.3.2.1 Recency Assessment. Request each offeror submit up to three (3) PPIFs for the prime contractor, and up to three (3) PPIFs for each significant subcontractor/teaming partner. Significant subcontractor is defined as a contractor who is proposed to perform over 10% of the total effort, or a contractor who is proposed to perform less than 10% of the total effort, but is determined to be performing a critical function. NOTE: The requested number of PPIFs for the prime and subcontractors are preferences and not requirements. Offerors may submit more than the preferred number, if the offeror believes the extra contracts are needed to fully describe their relevancy. Offerors who submit less than the preferred number of PPIFs are not automatically assigned a “Neutral Confidence” rating. Fewer numbers may be acceptable, if the Government determines there is sufficient information to determine a confidence rating. Request each PPIF not exceed a target of 8 pages, although more or less may be submitted, if necessary and relevant to the Paramedic/Ambulance Service program.

4.3.2. PPI Relevant Contract Narrative

For each PPIF, the offeror shall provide a narrative explaining what aspects of the contract is deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate. Specifically, the narrative should focus on similarities to the Factor 1 Technical subfactors, Factor 3 Price, and Scope, Magnitude, and Complexity, as defined in Addendum to FAR 52.212-2, paragraph 2.3.2.2, and should be tailored to the proposed portion of effort. Categorize the relevant information into the specific technical subfactors and price assessment used to evaluate the proposal. The narrative 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 shall 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. The offeror is requested to limit the narrative to a maximum of 5 pages. However, the offeror may exceed the requested page limit, if determined necessary to fully describe relevancy.

4.3.3. 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 the 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, offeror’s shall include 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 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), the "roadmap" should be both specifically applicable to the efforts identified, yet general enough to apply to efforts on which the Government receives information from other sources.

5.0. Factor 3 – Price

5.1. In the price volume, the Offeror shall provide the following information in addition to the pricing in Supplies or Services and Prices/Cost Section (Part B) of the solicitation. These instructions are to assist you in submitting information required to evaluate the reasonableness of your proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal.

5.2. General Instructions

Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price position. All information relating to the proposed price including all required supporting documentation must be included in the section of the proposal designated as the Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal. Price proposals will be evaluated for: (1) reasonableness, (2) balance, (3) price realism and (4) Total Evaluated Price (TEP). All information provided in response to the solicitation will be reviewed and will contribute to the determination of complete, reasonable, balanced, and realistic pricing. Offerors who’s TEP is determined to be unreasonable, unbalanced or unrealistic may not be considered for award. Unreasonable or unrealistic proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition. Additionally, an Offeror’s price may be rejected if it contains unbalanced pricing to the extent it poses an unacceptable risk to the Government. The TEP will be calculated as the sum of the Offeror’s proposed prices for the CLINs unit prices including the base period, all option periods and six-month Option to Extend Services period. Evaluation of options or optional CLINs shall not obligate the Government to exercise such options or optional CLINs. The TEP will be calculated as the sum of the offeror’s proposed prices for the following periods: Transition Period, one (1) 11-month Base Period; four (4) one year Option Periods; and one (1) six-month Extension Period IAW FAR 52.217-8 “Option to Extend Services.” The six-month extension of services is IAW FAR 52.217-8, "Option to Extend Services", and will only be utilized if necessary. The six-month extension of services is not to be considered part of any option period and will be a separate option exercised if it is utilized. Offerors will not be required to submit pricing for a six-month extension of services. The Government will develop the TEP which will include this pricing, based on the contractor’s final option period pricing.

5.2.1. Price Reasonableness

The Government will evaluate proposals for reasonableness. Normally, price reasonableness is established through adequate price competition, but may also be determined through other price analysis techniques. The burden of proof for credibility of proposed costs/prices rests with the offeror. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc.)

5.2.2 Balance

The Government will evaluate proposals for balance. The offeror is cautioned against submitting an offer which exhibits unbalanced pricing. Unbalanced pricing may increase performance risk and could result in payment of unreasonable or unrealistic prices. For this acquisition, balanced pricing is determined with respect to year-to-year price variances for separately priced CLINs. Offerors shall provide rationale for any proposed CLIN price increase greater than 5% from one year to another, or any proposed CLIN price decrease from one year to another. Unexplained price variances from year-to-year could suggest unbalanced pricing. It is in the Offerors best interest to provide explanations or supporting rationale for any significant annual CLIN price variances.

5.2.3 Price Realism

The Government will evaluate proposals for price realism to determine whether proposed prices are based on an adequate understanding of contract requirements. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc).

5.2.4. Cost or Pricing Information Requirements

FAR 12.209 gives the requirement to establish price reasonableness in accordance with 13.106-3 (Simplified Acquisition Procedures), 14.408-2 (Sealed Bidding), or 15.4 (Contract Pricing by Negotiation), as applicable. FAR part 15 applies. In accordance with FAR 15.403-3-1(b), prices based on adequate price competition do not require submission of cost or pricing data. In accordance with FAR 15.403-3(a), however, information other than cost or pricing data may be required to support price reasonableness. FAR 15.403-3(a)(1) provides for obtaining information other than cost or pricing data if needed to determine price reasonableness. Therefore, the FAR does not preclude the requirement for obtaining other than cost or pricing data under certain circumstances and the Government reserves the right to obtain data as appropriate. Should the CO determine proposed prices to appear unreasonable or the possibility that an Offeror does not fully understand the requirement, the Offerors may be required to support price reasonableness via other than cost or pricing data.

5.2.5. Rounding

All proposed dollar amounts shall be rounded to four decimal places. If any pricing proposal deviates from this format, the Government will apply the specified format to determine the extended pricing and total evaluated price (TEP). Offerors are advised to apply this specified format to their computations when developing unit prices

5.3. Estimating Methodology Utilized in Pricing Proposal

5.3.1. Past Experience with MSI Inventory Management

Where Paramedic/Ambulance prices are based on past experience, identify the past experience, explain how the past experience relates to the current effort including similarities and differences and how data available from the past experiences was adapted to the current effort.

5.3.2. Annual Price Changes

Proposed price increases greater than 5% per period shall be verified and addressed for reasonableness in this section.

5.3.3. Cost Assumptions Used in Development of Proposed Pricing Information to support reasonableness of proposed pricing is required including supporting data and estimating methodology to support price reasonableness. All cost assumptions (including indirect rates for the Offeror’s appropriate accounting period, volume or location discounts), scope limitations and/or qualifications of the pricing proposal shall be addressed and explained.

5.3.4. Proposed Price Reduction per Corporate/Management Decision If estimated costs to perform the proposed effort have been decreased due to a management decision, provide a summary of the reduction by major cost element (e.g., material, labor, overhead, etc.) summary.

5.4. SCA

It is the responsibility of the Offeror and the subsequent contract awarded to comply with the Services Contract Act (SCA). In this section of the Cost/Price Volume, a table shall be provided conforming (linking) the Offeror’s proposed job categories/skill levels considered subject to the SCA with the job categories/skill levels of the Wage Determination (WD). This cross-reference provides a tie between the labor categories/skill levels proposed and the labor categories/skill levels listed in the SCA WD.

5.5. Government Field Support Agencies

Not applicable to this acquisiton.

5.6. Other Documentation

Other documentation considered by Offerors to be essential for support of proposed prices shall be presented in this section. Pursuant to paragraph 5.3.4 above, Offerors are requested to address any proposed prices which reflect a business decision to offer prices at or below cost. It should be noted that the burden to demonstrate price reasonableness is incumbent upon the Offeror. Similarly, it should be clearly demonstrated that ALL proposed pricing is provided to the Government in good faith and intent without any pricing strategy of bidding low then upwardly revising pricing after contract award. Evidence of deliberate gaming as corporate strategy to win competitive contracts will put Offerors at risk for elimination from the competitive range.

5.7. Volume Organization

The Price volume shall consist of the following sections:

SECTION 1 – Table of Contents; narrative description of purchasing system and pricing methodology. Include your rationale in response to the following paragraphs in Section1:

5.2.1 – Price Reasonableness and Balance

5.2.2 – Pricing Information Requirement

5.3 – Estimating Methodology Utilized in Pricing Proposal

SECTION 2 - Include your response to the following paragraphs in Section 2:

5.4 – Services Contract Act (SCA)

SECTION 3 – Include any other pricing documentation considered by Offerors to be essential for support of proposed prices shall be presented in Section 3.

6.0. Contract Documentation

6.1. Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the Model Contract.

6.1.1. Solicitation/Contract Form (Section A)

Completion of blocks 12, 17 and signature and date for blocks 30a, 30b and 30c of the SF1449. Signature by the offeror on the SF1449 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

6.1.2. Supplies or Services and Costs/Prices (Section B)

Completed pricing information in Section B of the model contract.

6.1.3. Contract Clauses (Section I)

The offeror shall provide required information to complete clauses as required.

6.1.4. Representations, Certifications, and other Statements of Offerors (Section K) The offeror has completed the annual representations and certification electronically via the system for award management (SAM) website at https://www.sam.gov. After reviewing the SAM database information, the offeror verifies by submission of this offer that the representation and certifications currently posted electronically at FAR 52.212-3, Offeror Representations and Certifications—Commercial Items are correct.

6.2. Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 6.2. Offerors are cautioned the Government could determine any identified exceptions to be unacceptable, which would make the proposal ineligible for award.

Table 6.2 - Solicitation Exceptions Solicitation Document Page/ Paragraph Requirement/ Portion Rationale

Page and Paragraph Numbers

why the requirement can/will not be met

6.3. Other Information Required

6.3.1. Ombudsman

An Ombudsman has been appointed to hear concerns from offerors or potential offerors during the proposal development phase of this acquisition. The Ombudsman for this acquisition is Greg May. This does not diminish the authority of the program director or CO, but communicates offeror concerns, issues, disagreements and recommendations to the appropriate Government personnel. When requested, the Ombudsman shall maintain strict confidentiality as to the source of the concern. The Ombudsman does not participate in the evaluation of proposals or in the source selection process; interested parties are invited to call AFSC/PKC at greg.may@us.af.mil.

6.3.2. Authorized Offeror Personnel

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

6.3.3. Government Offices

Not applicable to this acquisition.

6.3.4. Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small).

ITO ATTACHMENTS

PAST PERFORMANCE PACKAGE ATTACHMENT

ITO Attachment – 2.0 PROPOSED TEAM LIST

ITO ATTACHMENT 1.1

PAST PERFORMANCE INFORMATION FORM

Provide the infonnation requested in this form for each contract/program being described. Provide frank, concise comments regarding your performance on the contracts you identify. Request each offerer submit up to three PPIFs for the prime Contractor and up to three for each significant subcontractor/teaming partner.

A.Offerer Name (Company/Division): ____________________________

CAGE CODE: ________________________

DUNS NUMBER: _____________________

(NOTE: If the company or division performing this effort is different than the offerer or the relevance of this effort to the instant acquisition is impacted by any company/corporate organizational change, note those changes. Refer to the "Organizational Structure Change History" you provided as part of your Past Performance Volume).

1. Contracting Agency or Customer: ___________________________

2. Contract Number: ________________________________________

3. Contract Type: __________________________________________ If multiple types (i.e. Firm-Fixed Price with Time & Material), list percentage and dollar amount of Firm-Fixed Price portion

4. Period of Performance: ____________________________________

5. Original Contract Dollar Value: __________________________ (Do not include unexercised options)

6. Current Contract Dollar Value: ___________________________ (Do not include unexercised options) If Amounts for 5 and 6 above are different, provide a brief description of the reason:

D. Brief Description of Effort as ____ Prime or ____ Subcontractor (Include performance considered most relevant to current acquisition)

E. Are there Contractor Performance Assessment Reports (CPARS) or other Past Performance Reports available for this contract? ________ YES ________NO

F. Primary Customer Points of Contact: (For Government contracts provide current information on all individuals. For commercial contracts, provide points of contact fulfilling these same roles)

1. Program Manager, COR and/or Site Manager Name: _____________________________ Telephone: _________________________ Email: _____________________________

2. Contracting Officer Name: _____________________________ Telephone: ___________________________ Email: _______________________________

G. Address any technical (or other) area about this contract considered unique.

H. For each applicable technical factor, illustrate how your experience on this contract applies, if you are to perform the same effort on the proposed contract.

I. Specify, by name, any key individual(s) who participated in this contract and are to support the proposed effort. Also, indicate their contractual roles for both acquisitions.

J. Describe the nature or portion of the work on the proposed effort to be performed by the business entity being reported here. Also estimate the percentage of the total proposed effort to be performed by this entity, and whether this entity will be performing as the prime, subcontractor or a corporate division related to the prime ( define relationship).

ITO ATTACHMENT 1.2

PAST PERFORMANCE QUESTIONNAIRE

WHEN FILLED IN THIS DOCUMENT IS SOURCE SELECTION SENSITIVE INFORMATION IAW FAR 3.104

SECTION 1: CONTRACT IDENTIFICATION

1. Contractor: ______________________________________________________________________________

1. Cage Code of contractor contract was awarded to: _________________________________

1. Contract number: _______________________________________

1. Contract type: ______________________________ (If multiple types (i.e. Firm-Fixed Price with Time & Material), list percentage and dollar amount of Firm-Fixed Price portion)

1. Was this a competitive contract? Yes _____ No _____

1. Period of performance: _________________________________________________________

1. Initial contract cost: $____________________________

1. Current/final contract cost: $_______________________________

1. Reasons for differences between initial contract cost and final contract costs: ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

1. Description of service provided: _______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

SECTION 2: CUSTOMER OR AGENCY IDENTIFICATION

1. Customer or agency name: _________________________________________________________________

1. Customer or agency description (if applicable): _______________________________________________________________

1. Geographic description of services under this contract, i.e. local, nationwide, worldwide, other Commands:

SECTION 3. EVALUATOR IDENTIFICATION

1. Evaluator's name: _________________________________________________________________________________

1. Evaluator's title: __________________________________________________________________________________

1. Evaluator's phone/fax number:_______________________________________________________________________

1. Evaluator’s email: ________________________________________________________________________________

E. Number of years evaluator worked on subject contract: _____________________________________

SECTION 4: EVALUATION

Please indicate your satisfaction with the contractor’s performance by placing an “X” in the appropriate block using the scale provided to the right of each question. This scale is defined as follows:

CODE PERFORMANCE LEVEL

B BLUE/EXCEPTIONAL - The contractor’s performance meets contractual requirements and exceeds some or many (requirements) to the Government’s benefit. The contractual performance was accomplished with few minor problems for which corrective actions taken by the contractor were highly effective.

G GREEN/SATISFACTORY – The contractor’s performance meets contractual requirements. The contractual performance contained some minor problems for which corrective actions taken by the contractor appear or were satisfactory.

Y YELLOW/MARGINAL – Performance does not meet some contractual requirements. The contractual performance reflects a serious problem for which the contractor has not yet identified corrective actions or the contractor’s proposed actions appear only marginally effective or were not fully implemented.

R RED/UNSATISFACTORY – Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance contains serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

N NOT APPLICABLE - Unable to provide a score.

Subfactor 1 RESOURCE MANAGEMENT

1. Did the contractor adequately provide a qualified, experienced program manager who is knowledgeable and able to meet program milestones, requirements, resolve problems, communicate with customer and report program status.

2. Did the contractor hired and retained field workers with appropriate technical skills and training commensurate with those required for successful project completion.

3. Did the contractor adequately manage and smoothly transition resources and personnel during contract transistion.

4. Did the contractor identified risks/problems as they occurred and offered constructive and/or viable solution/alternatives.

5. Did the contractor’s on-site supervisor displayed initiative to resolve problems on-site.

6. Did the Contractor provided the required Reports/Documentation as required in the contract.

Subfactor 2 QUALITY CONTROL

7. Did the contractor provided and followed effective quality control plan and/or inspection procedures to meet contract requirements.

8. Did the contractor deliver a quality service that was apparent in day-to-day operations.

9. Did the contractor corrected deficiencies in a timely manner and pursuant to their quality control procedures.

10. Did the contractor maintained a quality workforce and subcontractors through project completion.

11. Did the contractor responded to problems and took appropriate action to correct performance issues and satisfied customer concerns in a timely manner.

Factor 3 Price Performance

12. Were funds status reporting accurate and timely? If not, please explain.

13. Did the contractor promote savings for the customer and ensure best value commercial pricing in proposals? Please explain.

14. Did the contractor adhere to contract price/cost of the orginial contract? If not, please explain.

15. Were invoices submitted in a timely manner with no errors?

16. Was the contractor ever issued a cure or show cause notice under the referenced contract? If yes, explain outcome in "Remarks."

17. Would you award another contract to this contractor? If not, explain in "Remarks."

2. Please discuss each and every response for which you indicated B/E (Blue/Exceptional), Y/M (Yellow/Marginal) or R/U (Red/Unsatisfactory) in response to the questions above (use additional sheets,…