ADDENDUM TO FAR 52.212-1 INSTRUCTIONS TO OFFERORS Oct24.pdf

ADDENDUM TO FAR 52.212-1

INSTRUCTIONS TO OFFERORS (ITO)

1.0 Program Structure and Objective

1.1.1. The Government plans to award a single contract for Base Supply and Munitions program. The contract will primarily include requisition, receiving, storing, issuing, delivering and disposing of supplies and equipment assets to support customers on Tinker AFB, to include tenant units and transient customers.

1.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, inclusive of all options.

1.2. Budget/Funding Information

Funding will be obligated for the Firm-Fixed-Price (FFP) Contract Line Item Number (CLIN) for the base period, to include the phase-in period. The government may incrementally fund the line items as necessary.

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) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the model contract/solicitation.

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 Government Point of Entry web site at SAM.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. Oral Presentation

Oral presentations will not be utilized.

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

2.2.7. Submission, Modification, Revision, and Withdrawal of Proposals Proposal packages shall be transmitted to the Solicitation CO via DoD SAFE (safe.apps.mil).

Physical delivery of proposal packages will not be accepted. See sections 2.6 & 2.7 below.

2.2.8. Communications

Exchanges of source selection information between Government and Offerors will be controlled by the CO. E-mail (encrypted when possible or with password protected attachments) may be used to transmit such information to Offerors and shall include “Source Selection Information – http://www.fbo.gov/

See FAR 2.101 & 3.104” in the subject line.

2.3 Organization/Number of Copies/Page Limits

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

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

2.2.10. The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.3 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.3. 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 2.3. Proposal Organization

Volume ITO

Paragraph Number

Volume Title Electronic Copies

Page Limit

I 3.0. Technical 1 30

2.3.1. Title Page (Not Included in 30

Page Limit)

2.3.2. & Attachment 2.0

Team List (Not included in 30 page limit)

2.3.8. Table of Contents

Unlimited

2.3.9. List of Tables and Figures

2.3.10. Glossary of Abbreviations and

Acronyms

II 4.0. Past Performance 1 Unlimited

2.0

1.1

Past Performance Information Form (PPIF)

1.4

Consent Letter

1.5

Client Authorization Letters

1.2

Present/Past Performance Questionnaires

Tab Only

4.3.2. Relevant Contract Narrative

Max of 5 Pages per contract

4.3.3. Roadmap

III 5.0. Price Volume 1 Unlimited

5.2. General Information

5.4.13. Volume Organization

IV 6.0. Contract Documentation 1 Unlimited

2.0

2.3.8. Table of Contents

2.3.9. List of Tables and Figures

2.3.10. Glossary of Abbreviations and

Acronyms

2.0

6.1. Model Contract (Sections A-J)

N/A

6.1.4. Representations and

Certifications (Section K)

N/A

6.3. Contact Information

6.0. Attachments to the Model

Contract

2.2.11. Names

Offerors shall submit volumes with the following file names: Volume I – Technical.doc or .docx, Volume II – Past Performance.doc or .docx, Volume III – Price.doc or .docx with PricingMatrix.xlsx, and Volume IV – Contract.doc or docx. Files provided in .pdf format are also acceptable if conversion is made from a Word document or equivalent Word processing software while maintaining searchable text.

2.2.12. Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation. 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.2.13. Pricing Information

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

2.2.14. 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.2.15. Indexing

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

2.2.16. Include an indexed list of Tables and Figures.

2.2.17. 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.3 Page Size and Format

2.2.18. 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, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume.

These page format restrictions shall apply to responses to Evaluation Notice (ENs).

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

2.3. Labeling

A cover sheet shall be included in each proposal volume, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror’s name. For each proposal volume, the Offeror shall apply all appropriate markings including those prescribed IAW 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.4. Electronic Offers

2.4.1. All proposals shall be submitted using DoD SAFE, https://safe.apps.mil/. All interested Offerors must e-mail SrA Robert Kipler (robert.kipler@us.af.mil), SSgt Samuel Nemargut mailto:robert.kipler@us.af.mil

(samuel.nemargut@us.af.mil), Gerald Mosley (gerald.mosley.1@us.af.mil) in order to receive a request code to drop-off (upload) files in DoD SAFE. One of the Government Points of Contact (GPOCs) will send an e-mail to the Offeror acknowledging the request for a proposal drop-off code in DoD Safe. The GPOC e-mail acknowledging the request will not be sent to the Offeror after close of business hours, weekends, or on nationally observed holidays. If you do not receive an acknowledgement e-mail from either of the GPOCs after 72 hours, you must send another e-mail.

E-mails will not be returned after close of business hours, weekends, or on nationally observed holidays. After the e-mail request for a drop-off code has been sent from the Offeror and the Offeror has received the acknowledgment e-mail from either GPOC, the Offeror will then receive an e-mail from DoD SAFE to drop-off proposals and other requested documents. If the Offeror does not receive the e-mail from DoD SAFE the Offeror will need to check SPAM and JUNK folders before requesting another drop-off code from the GPOC. The request for drop-off is only valid for 14 days. If the 14 days has expired and the RFP is still open, the Offeror may send another e-mail request for drop-off code to the GPOCs e-mail addresses listed above.

2.4.2. Be advised that classified information is not allowed on DoD SAFE. Any files containing CUI/PII/PHI must be encrypted prior to uploading or by checking the “Encrypt every file” box. The Offeror is allowed to drop-off one or more files (up to 8GB total). The Offeror may select the box ‘Send me an e-mail when each recipient picks up the files” for documentation purposes. The GPOC will receive an automated e-mail containing the information the Offeror has entered and instructions for downloading the file(s). The GPOC will have 7 days to retrieve the files submitted in the drop-off. DoD SAFE does not guarantee delivery of documents within a specified time period under 4 hours.

2.4.3. All electronic documents and files submitted shall contain 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 as a separate file. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office 365 Word, MS Office 365 Excel, MS Office 365 Power Point, and Adobe PDF Note: files must be searchable and able to copy and paste. For amendment purposes to the proposal, the "original" proposal shall be clearly identified.

2.5. Distribution

Once the Offeror has uploaded the Offeror’s proposal in its entirety to DoD SAFE, the Offeror shall take a screen shot (Print Screen function) of the Offeror’s DoD SAFE upload confirmation screen showing all the uploaded files included in the proposal submission. The Offeror shall notify SrA Robert Kipler (robert.kipler@us.af.mil) and Gerald Mosely (gerald.mosley.1@us.af.mil) by email that the files have been uploaded and provide a copy of the DoD SAFE completed upload confirmation screen shot. If the proposal files are uploaded in their entirety prior to the proposal closing date and time, and the Offeror has notified SrA Robert Kipler and Gerald Mosely the files have been uploaded (notification is to include the DoD SAFE upload confirmation screen shot has also been provided), the proposal will be considered timely, even if the files are not accessible to the PCO in DoD SAFE until after the proposal closing date and time. If the Offeror fails to notify SrA Robert Kipler and/or Gerald Mosley by email, the files will be considered timely if they are accessible in DoD SAFE prior to the closing date and time. However, they will be considered late proposals, if they are not accessible until after the proposal date and time.

Email addresses are as follows:

SrA Robert Kipler (robert.kipler@us.af.mil) Gerald Mosley (gerald.mosley.1@us.af.mil) mailto:samuel.nemargut@us.af.mil mailto:gerald.mosley.1@us.af.mil

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 sub-factors 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 sub-factors. All the requirements specified in the solicitation are mandatory. By the offeror’s proposal submission, the offeror is representing that its firm will perform all the requirements specified in the solicitation. It is neither necessary nor desirable for the offeror to state so in its 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

The offeror shall address its proposed approach to meeting the minimum performance or capability requirements of each technical subfactor in the offeror’s technical volume.

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) Subfactor One – Program Management and Orientation Plan

(6) Subfactor Two – Manpower and Organization Chart

(7) Subfactor Three – Execution Plans

3.2.3. Subfactor One: Program Management and Orientation Plan The Offeror shall provide an approach for program management and orientation for the Base Supply and Munitions program. As a minimum, the approach shall provide the following essential components in addition to requirements outlined in the PWS:

a. At a minimum, the approach shall describe how the offeror will possess or obtain the appropriate facility clearance, SECRET, prior to performing work on a classified Government contract for all required personnel.

1.) The Contractor shall possess or obtain an appropriate facility clearance, SECRET, prior to performing work on a classified Government contract. In accordance with PWS

1.17.2. the following personnel shall have a SECRET security clearance: Contract Manager, Alt. Contract Manager, Supply and Munitions War Reserve Material Managers.

b. A transition plan to accomplish contract transition and phase in IAW 1.24 and all subparagrphs, to include hiring and training personnel, and obtaining security clearance, badges, and Common Access Cards (CAC). The plan must also include an approach to observe work accomplished by the current workforce without interfering with the production efforts of the current Government and contractor personnel.

c. An approach to manage and ensure a successful contractor mobilization changeover. The approach must include a milestone chart depicting changeover activities and an organizational chart identifying key positions IAW PWS 1.28 and all subparagraphs.

3.2.4. Sub-factor Two: Manpower and Organization Chart

The Offeror shall provide an approach for manpower and organization. As a minimum the proposal must describe the offeror’s organization chart and include manning numbers by all functional areas to include overall and total manning numbers for each specific functional area with an approach for sustaining proposed manpower levels during the contract performance period IAW PWS paragraph 1.6.1.9.

3.2.5 Sub-factor Three: Execution Plans

a. The offeror shall provide an approach for quality control. As a minimum the proposal must provide procedures for interfacing with Government representatives (i.e., Contracting Officer’s Representative, Contract Administrators, and Contracting Officers), approach to requirements listed in the Services Summary in the PWS and description of the internal feedback system and lines of authority for Quality Control personnel IAW PWS paragraph 1.8 and sub-paragraphs.

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 Factor 1, Technical subfactors, and Factor 3, Price. 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. Attachment 1.6 Commitment to Perform as Proposed Letter. This letter shall be executed and signed by the Prime contractor and each Subcontractor. The letter states that, in the event a contract is awarded to the Prime Contractor, the Prime Contractor and Subcontractor (to include teaming partners, and/or joint venture partners) commit to joint contract performance as described in the proposal. A separate letter shall be completed for each subcontractor separately. If the signed commitment is not fully executed by both parties and provided with the Past Performance Proposal, the subcontractor references will not be evaluated or considered. In the event the signed letter is not submitted with the initial proposal, but is later submitted during the evaluation, the subcontractor references will be considered at that point.

4.2. Early Proposal Information

4.2.1. 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 PPIS (Attachment 1.1). The POCs will complete the questionnaires and forward them by email directly to Gerald Mosley (Gerald.mosley.1@us.af.mil) and SrA Robert Kipler (robert.kipler@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- 2, 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-1, para 2.3.2.1 Recency Assessment.

Request each PPIFs not exceed a target of 8 pages, although more or less may be submitted if necessary and relevant to the base supply and munitions effort. Request each offeror submit up to four (4) PPIS forms for the prime Contractor and up to three (3) for each significant subcontractor/teaming partner limited to the last 3 years. The target of 8 pages for PPIS does not include the allowable 5 pages for ITO Paragraph Number 4.3.2, Relevant Contract Narrative. 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 PPIS forms are not automatically assigned an “Unknown Confidence” rating. Fewer numbers may be acceptable if the Government determines there is sufficient information to determine a confidence rating. Please only submit information on subcontractors and teaming partners performing key or critical portions of the base supply and munitions effort. There is no limit on the number of PPIS forms allowed per team; however, offerors are requested to limit responses to those efforts necessary for evaluation and relevant to the base supply and munitions effort.

4.3.2. PPI Relevant Contract Narrative

For each PPIF, the offeror shall provide a narrative explaining what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate.

Specifically, the narrative should focus on similarities to 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.

If subcontractor experience is submitted for consideration as part of the proposal, the offeror should include a commitment signed by offeror and subcontractor certifying that if a contract is awarded resulting from the proposal, the parties commit to joint performance as proposed. If the signed commitment is not fully executed by both parties and provided with the Past Performance Proposal, subcontractor references will not be evaluated or considered.

Affiliate companies, sister companies, teaming arrangements, joint venture agreement, etc., will be considered, provided that sufficient documentation is included in the proposal. The Prime contractor must demonstrate that the affiliate will perform significant and critical aspects of the contract if awarded. Proposal documentation should include a copy of the signed arrangement such as documented affiliation, a copy of the teaming agreement, a copy of the joint venture agreement, etc.

If the required information is not included in the proposal, the proposed affiliate companies, sister companies, joint venture companies, etc. not be evaluated or considered.

5.0. Factor 3: Price

5.1. In the price volume, the Offeror shall provide the following information in addition to the pricing in Pricing Matrix (Attachment 2). 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.

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 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.). It shall be noted that completeness is one aspect of price reasonableness. For completeness, the Offeror shall provide unit prices and/or rates for all listed items in the Pricing Matrix (Attachment 2). If an Offeror’s proposed unit price or rate is zero, then the Offeror shall provide rationale to support the zero dollar/rate entry.

5.2.2. Unbalanced Pricing

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 Contract Line Item Numbers (CLINs) or SubCLINs. 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. Also, an offer could be so grossly unbalanced that acceptance of the offer would be tantamount to allowing an advanced payment. If what appears unbalanced is due to sound rationale associated with, for example, the proposal’s technical approach or emerging technologies, it is in the offeror’s best interest to provide explanations or supporting rationale for any significant annual CLIN price variances.

To assist in the determination of balanced pricing, offerors shall complete the attached Pricing Matrix (Attachment 2).

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 and to ensure the proposed price does not pose a risk to performance. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc). All proposed prices shall be sufficient and adequately proposed to ensure the proposed price does not pose an unacceptable risk to performance.

5.2.4. Pricing Information Requirements

FAR part 15 applies as appropriate. Specifically, FAR 15.404-1 applies regarding proposal analysis. Price analysis techniques shall be utilized to ensure fair and reasonable pricing IAW FAR 15.404-1(b). Providing information to assist with pricing evaluation to further support proposed pricing will expedite the source selection process. In accordance with FAR 15.403-3- 1(b), prices based on adequate price competition do not require submission of certified 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. If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit pricing data.

5.2.5. Rounding

All dollar amounts shall be rounded to the nearest penny. 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. Total Evaluated Price (TEP)

The TEP is calculated in the Pricing Matrix (Attachment 2) in the “Pricing Matrix” worksheet. To calculate the TEP, the proposed prices and/or rates will be multiplied by the quantities in the Pricing Matrix. The product of each calculation (by CLIN) will be summed to arrive at a Total Evaluated Price.

Refer to the “Calculation Methodology” worksheet for information pertaining to the TEP calculation methodology by CLIN.

The TEP is for evaluation purposes only.

5.4. Pricing Support Information

Explain the methodology used to estimate prices in the development of the offeror’s proposed pricing. A variety of estimating techniques and methods are acceptable as a basis of estimate in proposed pricing. When responding to the price volume requirements in the solicitation, the offeror and associated subcontractors may use any generally acceptable estimating techniques consistent with the Offerors Disclosure Statement as appropriate, and if required based on current contracts per Defense Contract Audit Agency (DCAA) policy and guidance. Acceptable contemporary estimating methods can include Cost-to-Cost and Cost-to Non-Cost Estimating Relationships (CERs), commercially available parametric price models, in-house developed parametric price models, commercial catalogs, etc. If there are no deviations, then state accordingly. The government reserves the right to obtain information from the Contract Business Analysis Repository (CBAR) as considered necessary.

5.4.1. Past Experience Basis of Estimate

Where price estimates 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 price data available from the past experience was adapted to the current effort pricing.

5.4.2. Price Assumptions Used in Development of Proposed Pricing All significant assumptions, scope limitations and/or qualifications affecting the pricing proposal shall be addressed and explained. If there are no proposed price assumptions, then state accordingly in Section 2 of the price volume.

5.4.3. Accounting/Estimating System

Indicate whether you have Government approval of your accounting system and if so, provide evidence of such approval. Provide a summary description of your standard estimating system or methods. Identify any deviations from your standard estimating procedures or your accounting system in preparing this proposal. If there are no deviations, then provide a definitive statement stating as such in Section 1 of the Price Volume.

5.4.4. Service Contract Labor Standards (SCLS)

It is the responsibility of the offeror and the subsequent contract awardee to comply with the SCLS Wage Determination (WD) rates. In this section of the price volume, demonstrate compliance with SCLS requirements per Department of Labor (DoL) Government Point of Contact (POC) for any questions regarding use of SCLS. As applicable for SCLS-covered positions, demonstrate your understanding that all such direct labor rates shall be equal to or exceed the appropriate corresponding job category/skill level IAW the WD rates for the associated geographical locale as required. The Offeror, in their proposal, is required to identify the job categories/skill levels they consider subject to the SCLS and cross-reference via a SCLS equivalency table. Provide general information regarding any CBAs applicable to this acquisition.

5.4.5. Government Furnished Property/Equipment/Material (GFP/GFE/GFM) Provide assumptions regarding usage of all GFP, including GFE and GFM as reflected in your pricing proposal.

5.4.6. Contractor Furnished Property/Equipment/Tooling/Material (CFP/CFE/CFT/CFM) Provide assumptions regarding usage of all CFP, including CFE and CFM as reflected in your pricing proposal. It is the contractor’s responsibility to obtain property, equipment, tooling, and/or material required for performance of this contract.

5.4.7. Other Documentation

Other documentation considered by Offerors to be essential for support of proposed prices shall be presented in this section. For the FFP effort on this contract, all risk associated with subcontractor pricing at all tiers, market changes, etc. is to be considered and priced into the proposed prices. Offerors shall be held to their proposed pricing.

5.4.8. Submission of Pricing Matrix

Submit the completed Pricing Matrix (Attachment 2) in support of the proposed TEP. The proposed pricing in the Pricing Matrix submitted shall be consistent with your approved estimating system and shall duplicate the logic and mathematical formulas reflected in your electronic proposal. The Pricing Matrix (Attachment 2) submitted shall comply with the following format requirements:

•Electronic data file shall be .XLS (MS-Excel 365 or earlier) compatible format

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

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

SECTION 3 - Other information such as Government Furnished Property/Government Furnished Equipment (GFP/GFE), long lead costs, termination costs, labor cost, inflation rate summary and explanation. List each exception to the ground rules and assumptions provided in the solicitation and each qualification of the Cost/Price volume, if any.

Provide complete rationale for any exceptions.

SECTION 4 - Copy of Pricing Matrix (Attachment 2) from RFP with Offeror’s proposed prices included.

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 (SF 1449).

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 SF 1449. Signature by the offeror on the SF 1449 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover.

6.1.2. Supplies or Services and Costs/Prices (Section B) Completed pricing information in attached Pricing Matrix of the model contract, not in Section B.

6.1.3. Contract Clauses and Provisions (Section I)

The offeror shall provide information to complete clauses and provisions 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 http://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.204-8, Annual Representations and Certifications 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

SOO, SOW, SPEC,

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

6.3. Other Information Required

6.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 your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

6.3.2. Government Offices

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

http://www.sam.gov/

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

TIN; size of business (large or small); and labor surplus area designation. 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.

ITO ATTACHMENTS

PAST PERFORMANCE PACKAGE ATTACHMENT

ITO Attachment – 1.1 PAST PERFORMANCE INFORMATION FORM (PPIF)

ITO Attachment – 1.2 PAST AND PRESENT PERFORMANCE

ITO Attachment – 1.3 SAMPLE QUESTIONNAIRE COVER LETTER

ITO Attachment – 1.4 SAMPLE CONSENT LETTER

ITO Attachment – 1.5 SAMPLE CLIENT AUTHORIZATION

ITO Attachment – 1.6 COMMITMENT TO PERFORM AS

PROPOSED LETTER

ITO Attachment – 2.0 PROPOSED TEAM LIST

ITO ATTACHMENT 1.1

PAST PERFORMANCE INFORMATION FORM (PPIF)

Provide the information requested in this form for each contract/program being described. Provide frank, concise comments regarding your performance on the contracts you identify. Request each offeror submit between 4 and 3 PPIS forms for the prime Contractor and between 3 and 2 for each significant subcontractor/teaming partner.

A. Offeror Name (Company/Division):

CAGE Code:

DUNS Number:

(NOTE: If the company or division performing this effort is different than the offeror 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).

B. Program Title:

C. Contract Specifics:

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 $ Value: (Do not include unexercised options)

6. Current Contract $ Value: (Do not include unexercised options)

7. 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 (Please indicate whether it was development and/or production, or other acquisition phase and highlight portions considered most relevant to current acquisition)

E. Completion Date:

1. Original date:

2. Current Schedule:

3. Estimate at Completion:

4. How Many Times Changed:

5. Primary Causes of Change:

F. Are there Contractor Performance Assessment Reports (CPARS) or other Past Performance Reports available for this contract? YES NO

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

1. Program Manager and/or Name:

Site Manager Office:

Address:

Telephone:

Fax Number:

Email:

2. Contracting Officer Name:

Office:

Email:

3. Administrative Name:

Contracting Specialist Office:

Email:

H. Address any technical (or other) area about this contract/program considered unique.

I. For each of the applicable sub-factors under the technical factor in the “Evaluation Criteria for Award, illustrate how your experience on this program applies to that sub-factor, if you are to perform the same effort on the proposed contract.

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

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

A. Contractor:

B. Cage Code of contractor contract was awarded to:

C. Contract number:

D. Contract type:

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

E. Was this a competitive contract? Yes No

F. Period of performance:

G. Initial contract cost: $

H. Current/final contract cost: $

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

J. Description of service provided:

SECTION 2: CUSTOMER OR AGENCY IDENTIFICATION

A. Customer or agency name:

B. Customer or agency description (if applicable):

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

SECTION 3. EVALUATOR IDENTIFICATION

A. Evaluator's name:

B. Evaluator's title:

C. Evaluator's phone/fax number:

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

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.

NOT APPLICABLE - Unable to provide a score.

Factor 1 Technical Subfactor 1 Program Management and Orientation Plan G Y R N P1. Ability to provide a qualified, experienced program manager who is knowledgeable and able to meet program milestones, requirements, resolve problems, communicate…