Attachment 3 Section L - Instructions to Offerors.pdf

Increased Capacity Latrine

AFLCMC/WLTK Legacy Tanker Division

Controlled by: Air Force - AFLCMC/WLTK

Controlled by: AFLCMC/PZK-3

CUI Category: Procurement and Acquisition - Source Selection

Distribution/Dissemination Controls: FEDCON

POC: Jacob Booth PH: 405-734-8587, CELL: 405-615-8007, jacob.booth@us.af.mil mailto:jacob.booth@us.af.mil

SECTION L (Attachment 3)

INSTRUCTIONS TO OFFERORS (ITO)

1.0 Program Structure and Objective

The Government plans to award a single contract for Increased Capacity Latrine program. The

Increased Capacity Latrine shall introduce a larger capacity latrine to extend mission duration and capability. Per TO 11-2-KC-135V3, KC-135 Operations Procedures, Table 13.3, Latrine

Capacity v. Personnel Loading Chart, tanker mission duration is limited by the size of the latrine and the number of passengers it can support for a mission of a certain duration. The introduction of a latrine with a larger capacity would allow the KC-135 to carry more passengers for a longer duration. The addition of external servicing ports would also eliminate technician exposure to biological waste products.

1.1. Contract Award

Award will be made to the offeror who is rated “acceptable” in Factor 1 Technical and Factor 3

Past Performance, has the lowest evaluated cost or price, and whose proposal conforms to the solicitation requirements.

1.2. Budget/Funding Information

Funding will be obligated on individual orders, as required, for the Firm Fixed Price (FFP)

Contract Line Item Numbers (CLINs) established in the basic contract, as well as the Cost

Reimbursable (CR) for Travel.

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 Statement of Work (SOW) 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 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.1.6. All or parts of the offeror’s technical proposal will be added to the contract. Should there be any discrepancies between the technical proposal and the SOW, Airworthiness Certification

Basis or Systems Requirement Document (SRD), the SOW, A/W Cert Basis and SRD will take precedence.

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 System for Award

Management (SAM) website at https://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. 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 https://sam.gov/ confirmation upon submission of the offeror’s proposal. Any unacknowledged amendments in the offeror’s proposal are subject to solicitation provision FAR 52.215-1(b).

2.2.6. 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 ITO sections 2.6 & 2.7.

2.2.7. 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 –

See FAR 2.101 & 3.104” in the subject line.

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 facsimile numbers of the offeror and electronic 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 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 below shall be submitted in separate electronic files and uploaded to DoD SAFE as described in paragraph 2.5. and 2.6. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Volume

ITO

Paragraph

Number

Volume Title

Electronic

Copies

Page

Limit

I 3.0 Technical 1 20

2.3.1 Title Page (Not included in 20 page limit) 1

2.3.2 Team List (see ITO Attachment 2.0)(Not

included in 20 page limit)

3.2 Table of Contents (Not included in 10 page

limit)

Unlimited

3.2 List of Tables, Drawings, and Figures Unlimited

3.2 Glossary of Abbreviations and Acronyms (Not

included in 20 page limit)

Unlimited

3.2.1.1

3.2.1.2

3.2.1.3

Subfactor 1: Special Standards of

Responsibility

Subfactor 2: Manufacture and Production Plan

Included as part of the 20 page limit

II 4.0 Price Unlimited

4.1 General Information Unlimited

III 5.0 Past Performance 1 Unlimited

2.3.1 Title Page 1

2.3.2 Team List (See ITO Attachment 2.0) 5

5.1 Past Performance Information Forms (PPIF)

(See ITO Attachment 1.1)

N/A

5.1.2 Consent Letter (See ITO Attachment 1.4) Unlimited

5.1.3 Client Authorization Letters (See ITO

Attachment 1.5)

Unlimited

5.1.4 Commitment to Perform as Proposed Letter

(See ITO Attachment 1.6)

Unlimited

5.2.2 Present/Past Performance Questionnaires (See

ITO Attachment 1.2)

Not

Included in the

Offeror’s

Proposal

5.3.2 Relevant Contract Narrative Request

Max 5 pages per contract

5.3.4 Organizational Structure Change History 2

IV 5.1 Contract Documentation 1 N/A

2.3.1 Title Page (SF33) N/A

2.3.2 Team List (See ITO Attachment 2.0) Unlimited

2.3.3 Table of Contents Unlimited

2.3.8 List of Tables, Figures, and Drawings Unlimited

2.3.9 Model Contract (Sections A-J) N/A

6.1.4 Representations and Certifications (Section K) N/A

6.3.2-6.3.3 Contact Information Unlimited

6.3.5 Attachments to the Model Contract Unlimited

2.3.4. Names

Offerors shall submit volumes with the following file names: Volume I – Technical.doc or

.docx, Volume II – Price.doc or .docx with PricingMatrix.xlsx, Volume III – Past

Performance.doc or .docx 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.3.5. Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be 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.3.6. Pricing Information

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

Documentation volumes.

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. Tables and Figures

Include an indexed list of tables, figures, and drawings.

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. Offerors are prohibited from using other Arial fonts such as Arial Black, Arial Narrow or

Arial Rounded MT Bold. 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, bottom and side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to Evaluation Notice (ENs).

2.4.2. 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 10-pt. These limitations shall apply to electronic 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 electronic proposals.

2.5. 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.6. Electronic Offers

All proposals shall be submitted using DoD SAFE, https://safe.apps.mil/. All interested offerors must e-mail the PCO, Mr. Jacob Booth (jacob.booth@us.af.mil) and Contract Specialist, Richard

Warcup (richard.warcup@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 calendar days. If the 14 calendar 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.

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

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.7. 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 the PCO, Mr. Jacob Booth (jacob.booth@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 the PCO (Mr. Jacob Booth) 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 the PCO (Mr. Jacob Booth) 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:

PCO, Mr. Jacob Booth, jacob.booth@us.af.mil

3.0. Factor 1 - Technical

3.1. General

The Technical proposal should be specific and complete. Legibility, clarity and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in

Evaluation Factors for Award (or Section M). Using the instructions provided below, provide as specifically as possible, the actual methodology you would use for accomplishing/satisfying these subfactors. Offerors shall assume that the government has no prior knowledge of their experience or facilities and will base its evaluation on the information presented in the proposal.

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 technical proposal. The technical proposal should only address the requirements of the subfactors listed below. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

3.2. Format and Specific Content

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

1. Team List ITO Attachment 2.0

2. Table of Contents

3. List of Tables, Figures, and Drawings

4. Glossary of Abbreviations and Acronyms

5. Subfactor 1: Special Standards of Responsibility

6. Subfactor 2: Manufacture and Production Strategy

3.2.1. Technical Volume

In the Technical Volume, address your proposed approach to meeting the minimum performance or capability requirements of each technical subfactor.

3.2.1.1. Subfactor One: Special Standards of Responsibility

The offeror shall provide an approach for the Increased Capacity Latrine. As a minimum, the approach shall provide the following essential elements:

a. An approach that produces a functional first article increased capacity latrine for two (2) KC-

135 aircraft. At a minimum, the approach must specifically address SOW 1.0 – Scope, as follows:

1. Have a capacity of at least 8 gallons, not to include the rinse tank.

2. Fit within the existing latrine compartment and be useable without interfering with the aircraft battery, a circuit breaker panel located on the aft wall, or any structural component.

3. Be secured to the existing floor in a manner that meets crash certification requirements MIL-

HDBK-516C 5.1.9 a (5).

4. Be installed and secured without any modification to the existing aircraft or load bearing structures (i.e. mounting to the flooring without going into the aircraft structure).

5. Be capable of servicing without removing either the latrine or any subcomponent. The latrine may be serviced by existing cart that will connect to servicing points on the latrine. For access to the servicing points, modifications may be made to the aft latrine compartment wall. This wall is non-structural or load bearing.

6. Be equipped with commercially available servicing points and connections.

7. Connect to an existing aircraft electrical wire connector that supplies 28Vdc, 5 Amp circuit

(cannot draw more power). The latrine may come with appropriate wiring that can be pinned to the existing connector.

8. Be capable of performing without leaks or splashing from the container at maximum roll and bank angles.

9. Latrine must have a way to prevent pressure build-up due to temperature or changes in altitude.

3.2.1.2. Subfactor Two: Manufacture and Production Strategy

The Offeror shall provide an Integrated Master Schedule for the Increased Capacity Latrine program. As a minimum, the approach shall provide the following essential components:

a) A detailed schedule outlining program progress from contract award until the delivery of the last purchased kit. (CDRL A029)

1 A detailed plan outlining how the offeror will meet the minimum production quantity of 70 kits per year. (SOW 3.9) This will include two (2) first article kits due forty-five (45) days after receipt of approval of first article to be used to ensure fit and function before going into full rate production. (SOW 3.8.2)

4.0. Factor 2 - Price

Completion of the RFP, Section B Schedule will represent the price proposal.

4.1. General Information

In the price volume, the Offeror shall provide the following information in addition to the Pricing

Matrix (Attachment 2) These instructions are to assist you in submitting information required to evaluate the reasonableness of your proposed cost/price. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal.

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.

Offeror’s pricing proposal will be evaluated for reasonableness, balance, and realism.

Unreasonable and/or unrealistic proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition. Additionally, unbalanced pricing may pose an unacceptable risk to the Government and may render an Offeror’s proposal ineligible for award.

Offers should be sufficiently detailed to demonstrate their price reasonableness and balance. The burden of proof for credibility of proposed prices rests with the Offeror.

4.1.1. Price Reasonableness

The Government will evaluate proposals for reasonableness, to include completeness. Normally, price reasonableness is established through adequate price competition, but may also be determined through proposal analysis techniques. The burden of proof for credibility of proposed costs/prices rest with the Offeror. Offerors shall provide sufficient rationale describing how prices/rates 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.

4.1.2. Balanced 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 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 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)

4.1.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 an unacceptable risk to performance. The Government may also use other evaluation techniques, as needed. To evaluate pricing realism, the Government may use one or more of the price analysis techniques described in FAR 15.404. 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 performance is not at an acceptable risk with prices proposed too low.

4.1.4. Total Evaluated Price (TEP)

Offerors shall complete the Pricing Matrix (Attachment 2). Offerors must ensure all required proposed pricing is provided in the Pricing Matrix, ensuring all periods of performance are priced. The TEP is calculated as the sum of the basic period (2-years), and two 2-year options.

The Pricing Matrix will be used for all pricing.

The Best Estimated Quantities (BEQ) provided in the Pricing Matrix (Attachment 2) are based on historical data and future projected requirements. All such quantities will be used for evaluation purposes only and do not obligate the Government to exercise options or guarantee such quantities during the contract period of performance.

4.1.5. Pricing Information Requirements

FAR 15.4 applies as appropriate. Specifically, FAR 15.404-1 applies regarding proposal analysis. Price analysis techniques shall be utilized to ensure fair and reasonable pricing in accordance FAR 15.404-1(b). Providing information to assist with pricing evaluation to further support proposed pricing will expedite the source selection process.

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. 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 cost or pricing data.

4.1.6. Rounding

In the Pricing Matrix (Attachment 2), all proposed dollar amounts shall be rounded to the nearest penny.

4.2. Pricing Support Information

4.2.1. Explanation of Specific Estimating Techniques and Methods

Explain the methodology used to estimate costs/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, commercially available parametric price models, in-house developed parametric price models, commercial catalogs, etc. In addition, the Offeror is required to provide a summary of the estimating system, purchasing system, and accounting system and provide an explanation of any deviations used in the development of the Pricing

Volume. If there are no deviations, then state accordingly in Section 2 of the Price Volume.

4.2.2. 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 experiences was adapted to the current effort pricing.

4.2.3. Proposed Price Reduction per Corporate/Management Decision

If proposed prices to perform the proposed effort have been decreased due to a management decision, provide a summary of the reduction by major pricing element (e.g., material, labor, overhead, etc.). Also, provide complete rationale for the reduction. Provide the estimated dollar and percentage of the reduction, explaining how such reductions are ensured not to increase performance risk to the Government. If the Offeror has not proposed any price reductions, then state accordingly in Section 2 of the Price Volume.

4.2.4. Subcontractor Pricing

Submit a list of the proposed probable Subcontractors showing (a) the supplier, (b) description of effort, and (c) type of contract. As Prime Contractor, documentation is required to demonstrate

Subcontractor commercial quotes are considered fair and reasonable. Include a detailed description of your process/methodology for evaluating Subcontractor pricing and a determination of subcontractor proposed prices as fair and reasonable. Offerors are required to provide an explanation of how indirect costs (Including Material Handling costs), General and

Administrative (G&A) and profit are applied to Subcontractor proposed prices and whether all

Subcontractor costs, including indirect rates (particularly Material Handling rates), G&A, and profit are included as a total subcontract amount (i.e., Prime treats all Subcontractor/vendor costs as their direct cost to which the Prime applies their own indirect costs, G&A, cost of money

(COM) and profit).

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

4.2.6. Accounting System

Defense Contract Management Agency (DCMA) determines the adequacy of a contractor’s accounting system following an audit performed by Defense Contract Audit Agency (DCAA).

Any potential contract awardee must have his accounting system determined adequate before contract award can be made.

The Offeror shall state whether the accounting system has been reviewed and determined adequate by the Government and provide evidence of the review and approval by

DCAA/DCMA. The Offeror shall provide any known/cited accounting system deficiencies and identify any deviations from the Offeror’s standard procedures in preparing this proposal. For known/cited accounting system or methods non-compliances, provide a schedule and description of corrective actions the Offeror is taking to eliminate the non-compliance issues. If there are no deviations, then state accordingly in Section 1 of the Price Volume.

If the Offeror does not currently have an adequate accounting system, the Offeror shall complete and submit the “Contractor Self Assertion in support of the proposed TEP. The proposed pricing in the Pricing Matrix submitted must be consistent with your approved estimating system and must duplicate the logic and mathematical formulas reflected in the Price Volume. The Pricing

Matrix submitted must comply with the following format requirements:

a. Data file shall be submitted to the Solicitation PCO via DoD SAFE (safe.apps.mil)

b. Data file shall be .XLS file format (MS Office 365-Excel) without passwords or hidden information.

4.2.7. Annual Price Changes

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

5.1. Volume Organization

The Price volume shall consist of the following sections to include Title Page, Table of Contents, List of Tables and Figures, and Glossary of Abbreviations and Acronyms:

SECTION 1 – Include your rationale in response to the following paragraphs in Section 1, along with a Table of Contents

5.2.1. – Price Reasonableness

5.2.2. – Balanced Pricing

5.2.3. – Price Realism

5.3. – Pricing Information Requirements

5.3.1. – Rounding

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

5.4. – Pricing Support Information

5.4.1. – Explanation of Specific Estimating Techniques and Methods

5.4.2. – Past Experience Basis of Estimate

5.4.3. – Proposed Price Reduction per Corporate/Management Decision

5.4.4. – Subcontractor Pricing

5.4.5. – Price Assumptions Used in Development of Proposed Pricing

SECTION 3 - Include your response to the following paragraphs in Section 3.

5.4.6 – Accounting System

5.4.7. – Government Field Support Agencies

5.4.8. – Government Furnished Property/Equipment/Material (GFP/GFE/GFM)

5.4.9. - Contractor Furnished Property/Equipment/Tooling/Material

(CFP/CFE/CFT/CFM)

5.4.10 - Other Documentation

SECTION 4 – Include your response to the following paragraphs in Section 4.

5.4.11. – Submission of Pricing Matrix

6.0. Factor 3 - Past Performance

6.1. General

6.1.1. Past Performance Information Forms (PPIF)

Each Offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in ITO Attachment 1.1. 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, and factor 4, price. The Government’s Past Performance Evaluation Team (PPET) evaluates each member of the Offeror’s team for relevancy and performance, based on their proposed portion of the 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.

6.1.2. Attachment 1.4 Consent Letter

This letter executed and signed by each subcontractor, teaming partner, and/or joint venture partner. The letter authorizes release of adverse past performance information to the Offeror so the Offeror can respond to such information.

6.1.3. Attachment 1.5 Client Authorization Letter

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.

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

6.2. Early Proposal Information

6.2.1. Each Offeror is requested to submit past performance information for each relevant contract fifteen (15) 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.

6.2.2. As soon as practicable, Offerors shall complete Section 1 of the attached Past Performance

Questionnaire (ITO Attachment 1.2) and e-mail it and the Performance Questionnaire Letter

(ITO Attachment 1.3) to all points of contacts (POCs) the Offeror has listed in the Past

Performance Information Sheets (ITO Attachment 1.1). The POCs will complete the questionnaires and forward them by email, directly to the PCO (Attn. Jacob Booth) Email address for questionnaires jacob.booth@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.

6.3. Relevant Contracts

6.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 ITO Attachment 1.1, Past

Performance Information Form (PPIF). The Offeror shall submit PPIFs for contracts which include all or some performance within the past three (3) years, as defined in Section M, paragraph 2.4.3, Recency Assessment. The Government requests each Offeror submit up to three (3) PPIFs for the prime contractor, and up to two (2) PPIFs for each significant subcontractor/teaming partner. Significant subcontractor is defined as a contractor who is proposed to perform over 5% of the total effort, or a contractor who is proposed to perform less than 5% 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 an “Unacceptable” rating. Fewer numbers may be acceptable if the government determines there is sufficient information to determine an “Acceptable” rating. Request each PPIF not exceed a target of 5 pages, although more or less may be submitted, if necessary and relevant to the KC-135 Increased Capacity

Latrine program.

6.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 the Factor 1, Technical

Subfactors, Factor 2, Price, and Scope, Magnitude and Complexity as defined in Section M, paragraph 2.4.4 and should be tailored to the proposed portion of the effort. 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 an “Unacceptable” 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. 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.

6.3.3. 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. will not be evaluated or considered.

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.

6.3.4. Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between 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 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.

7.0. Contract Documentation

7.1. Model Contract/Representations and Certifications

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

Model Contract and Sections A through K.

7.1.1. Solicitation/Contract Form (Section A)

Completion of blocks 15-18 to include signature and date of the SF33. Signature by the offeror on the SF33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover.

7.1.2. Supplies or Services and Prices (Attachment 2 – Pricing Matrix)

Offerors shall complete the pricing information in the Pricing Matrix (Attachment 2) of the model contract.

7.1.3. Contract Clauses (Section I)

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

7.1.4. Representations, Certifications, and other Statements of Offerors (Section K)

The offeror has completed the annual representations and certification electronically via the

SAM website accessed through https://www.sam.gov/SAM/. After reviewing the SAM database information, the offeror verifies by submission of this offer that the representation and certifications currently posted electronically are correct.

7.2. Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an 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 7.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

7.3. Other Information Required

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

AFSC/PZC located at Tinker AFB, OK. 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/PZC at 405-736-3273.

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

7.3.3. Government Offices

Provide the mailing address, telephone and fax numbers and facility codes for the cognizant

Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

7.3.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); 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.

7.3.5. Attachments to the Model Contract

The offeror shall provide the following as attachments to the model contract:

a. Subcontracting Plan (if applicable). Include a subcontracting plan IAW FAR 19.704.

The plan must be approved by the CO prior to contract award.

LIST OF DOCUMENTS, EXHIBITS OR ATTACHMENTS

See Section J of the RFP.

ITO ATTACHMENTS

PAST PERFORMANCE PACKAGE ATTACHMENT

ITO Attachment – 1.1 PAST PERFORMANCE INFORMATION FORM (PPIF)

ITO Attachment – 1.2 PAST PERFORMANCE QUESTIONNAIRE

ITO Attachment – 1.3 SAMPLE QUESTIONNAIRE COVER LETTER

ITO Attachment – 1.4 SAMPLE CONSENT LETTER

ITO Attachment – 1.5 SAMPLE CLIENT AUTHORIZATION LETTER

ITO Attachment – 1.6 COMMITMENT TO PERFORM AS PROPOSE LETTER

ITO Attachment – 2.0 PROPOSED TEAM LIST

ITO ATTACHMENT 1.1

PAST PERFORMANCE INFORMATION FORM

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 6 and 10 PPIS forms for the prime Contractor and between

4 and 7 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 Officer Office:

Email:

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

I. For each of the applicable subfactors under the technical factor in the “Evaluation…