Section_L.pdf

Section L

Instructions To Offerors (ITO)

Instructions, conditions, and notices to respondents for proposal preparation using tradeoff source selection procedures.

Note: Price competition is anticipated, but may not be realized. If competition is not realized, the offeror shall have 20 calendar days to submit certified cost and pricing data in accordance with FAR Part 15.4 and Table 15-2. The offeror shall provide a copy of their FAR Part 15 proposal, cost and pricing data, and electronic media to the cognizant Defense Contract Management Agency (DCMA) and Defense Contract Audit Agency (DCAA) auditors and the contracting officer. The procedures at DFARS 215.371, Only One Offeror, and any other applicable supplements and / or procedures apply.

General (LG) Instructions For Basis of Contract Award

LG1. General Guidance

The government plans to award a single contract for the 420th Logistics and Data Services (LADS) program.

In accordance with the Performance Work Statement (PWS),the contractor will be required to provide logistics services, logistics analyses and reports to support Depot Level Reparable (DLRs) Spares and Air Force- (AF-) Managed Consumables and to further develop, test, transition, and refine innovative, non-forecast-based, inventory stock-age methodologies for highly variable demand and sporadic demand items and to support Air Force implementation of such methodologies in current legacy systems as well as possible future advanced planning systems. This requirement supports all AF-managed items maintained at Hill Air Force Base (AFB), Tinker AFB, and Robins AFB.

Award will be made on the basis of “best value” utilizing tradeoff source selection procedures to the offeror providing the “best value” to the government over the entire period of performance.

LG1.0.1. 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, price, and specific requirements of the solicitation. This information shall be provided in the format and content of the below table. Offerors are cautioned the Government could determine any identified exceptions to be unacceptable, which would make the proposal ineligible for award.

Solicitation Document Page / Paragraph Requirement / Portion Rationale

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

LG1.0.2. Compliance

This section of the ITO provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The 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 SOW and appendices. Non-conformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation.

LG1.0.3. Clarity

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall 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 proposal.

LG1.0.4. Unnecessary Elaborations

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

LG1.0.5. Disposition of Files

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.

LG1.0.6. Point of Contact

The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. Address any questions or concerns the offeror may have to the PCO. Written requests for clarification may be sent to the PCO at the address located in Section A of the model contract/solicitation.

LG1.0.7. Debriefing

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

LG1.0.8. Solicitation Errors or Omissions

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

LG1.0.9. Availability of Documents

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

LG1.0.10. Solicitation Amendments

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

LG1.0.11. Submission, Modification, Revision, and Withdrawal of Proposals

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

LG1.0.12. Title Page

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.

LG1.0.13. Team List

A team list of the offeror’s primary Point of Contacts shall be submitted in each volume.

LG1.0.14. Proposal Organization

The offeror shall prepare the proposal as set forth in the Proposal Organization Table as outlined below.

Volume ITO Para Number Volume Title

Hard Copies / Disk

Copies

Page Limit

I LT1 Technical 6/2 75

LG1.0.12 Title Page (Not included in page limit) 1

LG1.0.13 Team List (Not included in page limit) 5

LG1.0.18 Table of Contents Unlimited

LG1.1.2 List of Tables and Figures Unlimited

LG1.0.19 Glossary of Abbreviations and Acronyms Unlimited

LTSF3.1 Small Business Subcontracting Plan (Not included in page limit)

Unlimited

LTSF3.1 Small Business Participation Plan (Not included in page limit)

Unlimited

II LPP2.0 Past Performance 6/2 Unlimited

LG1.0.12 Title Page 1

LG1.0.13 Team List 5

LG1.0.18 Table of Contents Unlimited

LG1.1.2 List of Tables and Figures Unlimited

LG1.0.19 Glossary of Abbreviations and Acronyms Unlimited

LPP2.3.3 Present/Past Performance Information Sheets

(PPIS)

Unlimited

LPP2.3.1 Consent Letter Unlimited

LPP2.3.2 Client Authorization Letters Unlimited

LPP2.3.3 Present/Past Performance Questionnaires Tab Only

LPP2.1 Relevant Contract Narrative Request Max 5

LPP2.2 Small Business Prior Performance Information Unlimited

LPP2.3.4 Roadmap 2

III LCP5.0 Price Volume 4/2 Unlimited

LCP5.0 Table of Contents Unlimited

LG1.0.19 Glossary of Abbreviations and Acronyms Unlimited

LCP5.0 General Information Unlimited

LCP5.0 Volume Organization Unlimited

IV LG1.3 Contract Documentation 3/1 Unlimited

LG1.0.12 Title Page 1

LG1.0.13 Team List 5

LG1.0.18 Table of Contents Unlimited

LG1.1.2 List of Tables and Figures Unlimited

LG1.0.19 Glossary of Abbreviations and Acronyms Unlimited

LG1.0.13 Team List, Arrangements, and/or Letters of Intent

Unlimited

LG1.3.1 Model Contract (Sections A-J) N/A

LG1.3.5 Representations and Certifications (Section K) N/A

LG1.5 Contact Information Unlimited

LG1.3.1 Attachments to the Model Contract Unlimited

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 Proposal Organization Table. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary.

Text of proposals shall be submitted in English. Proposals received in languages other than English shall be rejected.

LG1.0.15. Page Limitations

Page limitations as stated in the Proposal Organization Table shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will be returned to the offeror as soon as practical. 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.

LG1.0.16. Price Information

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

Cost trade off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade off decisions.

LG1.0.17. Cross Referencing

Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted when its use would conserve space without impairing clarity.

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

The proposal shall include an indexed list of Tables and Figures.

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

LG1.0.20. Budget and Funding Information

Funding will be obligated on the basic contract, as required, for the Firm-Fixed-Price (FFP) Contract Line Item Numbers (CLIN) / Sub Contract Line Item Numbers (SubCLIN) established in the basic contract.

LG1.1. Page Size and Format

LG1.1.1. Page Format

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 also apply to responses to Evaluation Notice (ENs). These limitations shall apply to both electronic and hard copy proposals.

LG1.1.2. Tables, Charts, Graphs, and Figures

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-points. These limitations shall apply to both electronic and hard copy proposals. Any text within figures, charts, tables, and graphs which do not meet this requirement will not be considered in the evaluation.

These limitations shall also apply to responses to ENs.

LG1.1.3. Binding and Labeling

Each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification and the offeror’s name. The same identifying data shall be placed on the spine of each binder.

The original proposal shall be printed double sided so that pages can be flipped on the short edge otherwise known as head to toe printing (head to toe is a term used in duplex printing meaning that the top or head of a document's front side should match with the bottom or "toe" of the back side). For document security, the document shall be bound in a three-ring, loose-leaf binder. The original proposal shall be maintained with the contract file until no longer required.

All other proposal copies shall be printed double sided so that pages can be flipped on the long edge otherwise known as head to head printing (head to head is a term used in duplex printing meaning that the top or "head" of a document's front side should match with the top of the back side). The proposal copies will be used by the source selection team members for evaluation of offers. Unless the offeror requests otherwise, the government will destroy extra copies of such unsuccessful proposals.

All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

LG1.1.4. Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. When discrepancies exist between the written hard copies and those provided in electronic format, the written hard copies will take precedence in all cases. For electronic copies, indicate on each Compact Disc Read Only Memory (CD-ROM) the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, required plans, exhibits, appendices, and attachments, if any. The offeror shall submit volumes I through V in electronic format. Each volume shall be submitted on a separate CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Word 2007 or 2010, MS Excel 2007 or 2010, MS Project 2007 or 2010, and MS Power Point 2007 or 2010.

LG1.2. Distribution

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

DEPARTMENT OF THE AIR FORCE

Office: AFSC/PZAAC Attention: Mr. James Banks Address: 3001 Staff Drive, Suite 1AB1 100B Tinker AFB OK 73145-3020 Telephone: 405-736-5668 Email: james.banks.12@us.af.mil

LG1.3. Contract Documentation

LG1.3.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 proposal shall include a signed copy of the Model Contract, and Sections A through K.

LG1.3.2. Solicitation/Contract Form (Section A)

The contractor shall complete all applicable blocks and sign the proposal. Signature by the offeror in response to the request for proposal constitutes an offer, which the government may accept. The "original" copy shall be clearly marked under separate cover and shall be provided without any punched holes.

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

Complete pricing information in the pricing matrix provided with the RFP.

LG1.3.4. Contract Clauses (Section I)

The offeror shall provide required information to complete clauses as required. The offeror shall ensure all appropriate clause “fill-ins” are documented.

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

The offeror has completed the annual representations and certification in accordance with FAR 4.1201 electronically via the System Award Management website at https://www.acquisition.gov. After reviewing the SAM database information, the offeror verifies by submission of this offer that the representation and certifications are current and correct.

LG1.4. 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 OC-ALC/PKC. This does not diminish the authority of the program director or PCO, 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.

LG1.5. Authorized Offeror Personnel

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

LG1.6. Government Offices

Provide the mailing address, telephone, email addresses, and facility codes for the cognizant Contract Administration Office (CAO), Defense Contract Audit Agency (DCAA), and Government Paying Office. Also, provide the name and telephone and email address for the Administrative CO (ACO).

LG1.7. Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; CAGE code; DUNS code; Tax Identification Number (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.

Technical (LT) General Instructions

LT1. Technical Volume

The Technical Volume shall be clear, specific, complete, and include sufficient detail for effective evaluation.

Legibility, clarity and coherence are very important. Offeror responses will be evaluated against the Technical Subfactors defined in Section M, Evaluation Factors for Award. Offerors should review Section M criteria to ensure the minimum requirements are met. Provide as specifically as possible the actual methodology the offeror would use for accomplishing / satisfying each of the subfactors and the PWS.

Offerors proposing efficiencies in the technical volume should provide an explanation as to how the efficiencies affect their overall approach. Offerors shall assume that the government has no prior knowledge of their experience or facilities, and will base its evaluation only on the information presented in the proposal.

All the requirements specified in the solicitation are mandatory. By the offeror’s proposal submission, the offeror is representing that the company / firm will perform ALL the requirements specified in the solicitation.

It is neither necessary nor desirable to tell the government so in the proposal. It is imperative that the offeror fully describe and provide detail as to how the offeror shall meet the subfactor requirements. Do not merely copy and paste, rephrase, or restate the objectives or reformulate the requirements specified in the solicitation.

LT1.1. Format and Specific Content

LT1.1. Format and Specific Content In the Technical Volume, address the proposed approach to meeting the minimum performance or capability requirements of each technical subfactor. The Technical Volume shall be organized according to the following general outline:

1) Team List

2) Table of Contents

3) List of Table and Drawings

4) Glossary

5) Subfactor 1, Contractor Requirements

6) Subfactor 2, Trade-Off curves for Sporadic and Highly Variable Demand Items

7) Subfactor 3, Live Demonstration of Inventory Simulation Capabilities

8) Subfactor 4, Small Business. Note, offerors that are considered a large business by the applicable NAICS must also submit a small business subcontracting plan in addition to the small business participation plan.

Technical Subfactor (TSF) 1

LTSF1. Contractor Requirements

The Offeror shall provide an approach for the accomplishment of Contractor Requirements. The approach shall provide a detailed approach for the accomplishment of requirements in PWS Sections 1.4 through

1.4.3.7. As a minimum, the offeror’s approach shall include details of how:

a) The offeror will acquire data, perform analyses and generate reports and charts required by the PWS.

The offeror shall provide a plan for how the requirements in PWS sections 1.4 through 1.4.3.7 will be satisfied.

b) D200A will be emulated. The offeror shall provide a plan and description of how their proposed D200A emulation will replicate D200A demand planning, inventory planning and supply planning logic to mirror D200A buy and repair requirements (reference PWS 1.2.1, 1.4.1, 1.4.2.2, 1.4.3.7).

c) The offeror will simulate the impact changes in demand rates had on the D200 computation (comp).

This analysis is a comparison between the baseline comp and the simulated comp, using the previous year's rates. The offeror shall provide a step-by-step description of the process which will be used to make this comparison (reference PWS 1.4.2.2).

d) The offeror’s proposed inventory models and simulation capability will meet the requirements of PWS 1.4.2.5, 1.4.2.5.1 and 1.4.2.5.2. The offeror shall provide a detailed description of the inventory models which will be used to manage sporadic and highly variable demand items to produce 3-way trade-off curves between customer support, inventory investment (cost) and the amount of buy and repair workload (buy and repair actions). The offeror shall provide a detailed description of the inventory simulation software that will be used to assess the performance of said inventory models. The offeror shall indicate the programming language or languages the simulation capability is programmed in. The offeror shall provide examples of analyses which have been conducted using simulation capability and shall annotate who the customers of such analyses were.

Technical Subfactor (TSF) 2

LTSF2. Trade-Off curves for Sporadic and Highly Variable Demand Items

The Government has included in this solicitation four flat files containing sample data (here after known as “Sample Data”). These Sample Data are a direct representation of the data that will be provided at contract award. These Sample Data are for demonstration purposes only and shall not be considered as part of the Flat Files delivered after contract award. The Offeror shall include in their proposal trade off curves for sporadic demand and highly variable demand items using the Sample Data provided by the government and consistent with paragraph 1.4.2.5.1 and 1.4.2.5.2 of the PWS. The offeror’s submission should include two separate trade-off curves, one for highly variable demand and one for sporadic demand items. The trade-off curves must depict various inventory investment options with the expected customer wait time plotted on the vertical axis, expected annual buy and repair obligations plotted on the horizontal axis and the expected number of repair actions per year depicted by using lines of constant workload with multiple lines on the trade-off curve graph (each line should represent a different workload investment option). The offeror must describe in their proposal how the trade-off curves were produced and how their methodology meets the requirements set forth in paragraphs 1.4.2.5.1 and 1.4.2.5.2 of the PWS. The offeror must also describe in their proposal the business rules used to segment items from the Sample Data file into the sporadic demand versus highly variable demand categories.

Technical Subfactor (TSF) 3

LTSF3. Live Demonstration of Inventory Simulation Capabilities

Live Demonstration of inventory simulation capabilities will be utilized. The Government has included in this solicitation four flat files containing sample data (here after known as “Sample Data”). These Sample Data are a direct representation of the data that will be provided at contract award. These Sample Data are for demonstration purposes only and shall not be considered as part of the Flat Files delivered after contract award. The government will allow each offeror 30 minutes for set-up and 3 hours to perform a live demonstration of their inventory simulations capability which shall simulate inventory levels generated by the sporadic demand model over a 3 year period using a minimum of 10 randomized demand sequences per NIIN that are based on actual demand patterns by NIIN provided in the Sample Data files. Offerors must generate the demand sequences during the demonstration. Offerors must provide their own computer and bring it to the live demonstration session. Offerors will not have access to government networks during the live demonstration and should already have all software, Sample Data and any other required data loaded on the offeror’s computer prior to the live demonstration. The Government will provide the ability to display the computer screen content on an external viewer so the evaluation team can follow along. The Government expects to contact offerors within three working days after proposal submission deadline to schedule a date and time for the Live Demonstration. The government intends to schedule all live demonstrations not later than ten calendar days of proposal response date. All live demonstrations will be conducted at Tinker AFB, OK. All travel costs are at contractor expense.

Prior to live demonstration, the offeror shall select an operating point on the sporadic demand trade-off curve included in their proposal to technical subfactor 2. Any point on the offeror’s sporadic demand trade-off curve may be used but the offeror must identify the trade-off curve point selected and provide the government a list of inventory levels by NIIN which correspond to the trade-off curve point selected. The trade-off curve point which will be used in the offeror’s live demonstration and the list of levels by NIIN which will be used during the demonstration must be provided in the offeror’s technical proposal. During the demonstration, the offeror should explain how simulation parameters were set and any assumptions that were made.

The Offeror shall provide a live demonstration of their inventory simulation capabilities as described in section M, and using the Sample Data. As a minimum, the live demonstration shall provide the following essential components.

Live demonstration shall be considered acceptable when the offeror's demonstration includes:

a) Successfully providing a list of levels by NIIN corresponding to a point on the trade-off curve provided in the offeror’s proposal to technical subfactor 2.

b) Successfully communicate inventory simulation settings and assumptions.

c) Successfully simulate the performance of inventory levels over a three year period with dynamic levels updates and using a minimum of 10 randomized demand sequences per NIIN. The randomized demand sequences must be generated using the transactional demand histories provided in the Sample Data. The randomized demand sequences shall be generated by playing out the actual historical data in multiple different randomized sequences. The frequency of dynamic levels updates should be communicated when simulation settings and assumptions are discussed (LTSF 3.b above).

Performance metrics should be averaged across the number of demand sequences used with the following being computed and communicated at the end of the simulation:

1. Based on simulation results, offeror must compute and communicate average customer wait time for each of the 3 years in the simulation.

2. Based on simulation results, offeror must compute and communicate average buy and repair actions for each of the 3 years in the simulation

3. Based on simulation results, offeror must compute and communicate average buy and repair obligation costs for each of the 3 years in the simulation

d) Successfully export the average customer wait time, buy and repair actions and buy and repair obligation costs, by NIIN, to Excel

Technical Subfactor (TSF) 4

LTSF4. Small Business (SB)

LTSF4.1. SB Plan Format

Prepare and submit one SB Participation Plan. For each SB category identified in the SB Participation Plan, specifically identify the SB concerns that will participate in this acquisition, either as part of a joint venture or a first-tier subcontractor, and provide the extent to which each identified SB concern will participate (expressed in both dollars and percentages of the total acquisition).

Large businesses must submit both a Small Business Participation Plan (dollars expressed in total contract value) and a Small Business Subcontracting Plan (dollars expressed in subcontracted dollars). Large businesses will not be eligible for award if they fail to submit an acceptable Subcontracting Plan. The Subcontracting Plan shall reflect and be consistent with the commitments offered in the SB Participation Plan. Large businesses achieve goals through subcontracting. Small businesses can achieve goals through their own performance / participation as a prime without having to subcontract.

An offeror submitting a proposal as a prime contractor and approved in the “Test Program for Negotiation of Comprehensive SB Subcontracting Plans” shall submit their Comprehensive SB Subcontracting Plan in lieu of the SB Subcontracting Plan.

LTSF4.1.1. SB Size Determination

For purposes of the SB Participation Plan, the business size standard applicable to this solicitation shall be determined by the North American Industry Classification System (NAICS) Code as indicated on the front page of the solicitation.

LTSF4.2. Documentation of Commitment

The offeror shall provide documentation regarding commitments for this effort including teaming agreements. Copies of such agreements shall be provided as part of the SB Participation Plan. All offerors shall provide any information concerning long-term relationships with SB subcontractors, such as mentor-protégé relationships, etc.

All offerors shall provide the following for all SBs participating in the proposed contract.

Name of SB:

Contractor and Government Entity (CAGE) of SB:

Type of SB:

Estimate of total dollars:

Type of service/supply:

Variety and complexity of the work:

PWS references:

Past Performance (LPP) General Instructions

LPP1. Past Performance General Instructions

Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Section L. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners proposed to perform the work outlined in the solicitation. Offerors are cautioned that the government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

LPP2. Past Performance Proposal Information

LPP2.1 Submission of Past Performance Volume

Each offeror is requested to submit Volume II, Past Performance. The Past Performance volume shall include a team list, which includes the prime contractor and all significant subcontractors. The offeror shall describe the portion of effort each team member is proposed to perform in relation to Factor 1 Technical to include all subfactors, Factor 3 Price, and how they relate to Scope, Magnitude, and Complexity, as defined in Section M. 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.

Past Performance Information Sheets (PPIS). The offeror shall provide Past Performance Information Sheets (PPIS) on current or previous contracts. The PPIS forms shall be completed in accordance with Section L, Attachment 1, Past Performance Information Instructions. The offeror shall submit contracts which include all or some performance within the past three years, as defined in Section M. Request each offeror submit up to five (5) PPIS forms for the prime contractor and up to four (4) PPIS forms for each significant subcontractor/teaming partner. Significant subcontractor is defined as a contractor who is proposed to perform over 10 percent of the total effort, or a contractor who is proposed to perform less than 10 percent of the total effort, but is determined to be performing a critical function. NOTE: The requested number of PPIS forms 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 is 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. Request each PPIS not exceed a target of 8 pages, although more or less may be submitted, if necessary and relevant to the LADS effort.

PPIS Relevant Contract Narrative. For each PPIS form, the offeror shall provide a narrative explaining what aspects of the contract is deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate. Specifically, the narrative should focus on similarities to the Factor 1 Technical to include all subfactors, Factor 3 Price, and how they relate to Scope, Magnitude, and Complexity, as defined in Section M 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.

LPP2.2. SB Prior Performance Information

Large businesses shall provide a description of their performance over the past three calendar years in complying with the requirements of FAR clause 52.219-9, SB Subcontracting Plan, including documentation of their accomplishment of the goals established under subcontracting plans of prior contracts. Large businesses that have never held a contract incorporating FAR clause 52.219-9 shall so state.

The offeror’s SB Subcontracting Plan shall address historical performance for each SB goal category, the goal approved for each category, and the actual goal achievement. To accomplish this effort, completing the entries below would address past SB Subcontracting Plan goal achievement:

Note: Calendar Year (CY) 16 is 1 Jan 16 – 31 Dec 16 Calendar Year (CY) 15 is 1 Jan 15 – 31 Dec 15 Calendar Year (CY) 14 is 1 Jan 14 – 31 Dec 14

Subcontract Goals CY16 CY15 CY14

(Offeror’s) SB Goal: _____ _____ _____

(Offeror’s) SB Accomplishment: _____ _____ _____

(Offeror’s) SDB Goal: _____ _____ _____

(Offeror’s) SDB Accomplishment: _____ _____ _____

(Offeror’s) WOSB Goal: _____ _____ _____

(Offeror’s) WOSB Accomplishment: _____ _____ _____

(Offeror’s) HUBZoneSB Goal: _____ _____ _____

(Offeror’s) HUBZoneSB Accomplishment: _____ _____ _____

(Offeror’s) SDVOSB Goal: _____ _____ _____

(Offeror’s) SDVOSB Accomplishment: _____ _____ _____

LPP2.3. Supporting Documents for Past Performance

LPP2.3.1. Subcontractor Consent Letter

Along with the information required in this paragraph, the offeror shall submit a Subcontractor Consent Letter (attached) 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.

LPP2.3.2. Client Authorization Letter

For each identified effort for a commercial customer, the offeror shall also submit a Client Authorization Letter (attached) authorizing release to the government of requested information on the offeror’s performance.

LPP2.3.3. Past Performance Questionnaire

As soon as practical, the offeror shall complete the attached Past Performance Questionnaire, Section 1 and send to all points of contacts the offeror has listed in the Past Performance Information Sheets.

The POCs will complete the questionnaires and forward them by email to:

James.banks.12@us.af.mil

RESPONDENTS TO THE QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION

SHEETS BACK TO THE OFFEROR.

Offeror shall not follow-up with respondents to ensure they have completed the questionnaires.

The Past Performance Team will conduct such follow-up with any POC as necessary.

LPP2.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, offerors 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 identified 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, the "roadmap" shall be both specifically applicable to the efforts identified, yet general enough to apply to efforts on which the government receives information from other sources.

LPP2.3.5. List of Section L, Past Performance Attachments

Attachment 1: Past Performance Information Instructions Attachment 2: Past Performance Questionnaire Attachment 3: Client Authorization Letter Attachment 4: Subcontractor Consent Letter Attachment 5: Proposed Team List

Price (LCP) General Instructions

LCP1. General Guidance

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

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

Information beyond that required by this instruction shall not be submitted, unless it is considered essential to document or support the 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.

Other than the Small Business Participation Plan, under no circumstances shall this information and documentation be included elsewhere in the proposal.

LCP1.0.1. Price Reasonableness

The proposal will be evaluated for reasonableness. Unreasonable proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition.

Price reasonableness is based on total evaluated proposed price and must represent a price to the government a prudent person would pay in the conduct of competitive business. Normally, price reasonableness is established through adequate price competition, but may also be determined through other proposal analysis techniques. To assist in the price reasonableness assessment, the offeror is required to provide supporting explanation/rationale as outlined in the Pricing Volume, Section 5. The offeror’s proposal shall be sufficiently detailed to demonstrate price reasonableness. The burden of proof for credibility of proposed pricing rests with the offeror. It shall be noted that completeness is one aspect of price reasonableness – all required pricing shall be provided as complete pricing.

LCP1.0.2. Price Balance

The offeror is cautioned against submitting an offer that exhibits unbalanced pricing. Unbalanced pricing may increase performance risk and could result in payment of unreasonable prices. Unbalanced pricing exists when, despite an acceptable Total Evaluated Price (TEP), the price of one or more CLINs or SubCLINs is significantly over or understated as indicated by application of price analysis techniques such that there is reasonable doubt the offer would result in the lowest overall price to the government, even though it is the lowest TEP; or the offer is so grossly unbalanced, its acceptance would be tantamount to allowing an advanced payment. Balanced pricing is determined with respect to separately priced CLINs or SubCLINs or significant unexplained variance in pricing from year to year.

LCP1.0.3. Price Realism

Proposed pricing must demonstrate adequate understanding of the requirement and does not pose a risk to performance. Specifically, all proposed prices shall be sufficient and adequately proposed to ensure performance is not at risk with prices proposed too low.

LCP2. Cost or Pricing Data Requirements

FAR part 15 applies. In accordance with FAR 15.403-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, data other than certified cost or pricing data may be required to support price reasonableness. FAR 15.403-3(a) provides for obtaining data other than certified cost or pricing data if needed to determine price reasonableness. Therefore, the FAR does not preclude the requirement for obtaining data other than certified cost or pricing data under certain circumstances and the government reserves the right to obtain data as appropriate. If the PCO determines proposed prices to appear unreasonable or the possibility that an offeror does not fully understand the requirement; the offeror may be required to support price reasonableness via data other than certified cost or pricing data. If, after receipt of proposals, the PCO 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 other than certified cost or pricing data.

LCP2.1. Total Evaluated Price (TEP)

Pricing will be evaluated using the Pricing Matrix (electronic cost model). The TEP is the sum of extended pricing for the base-year plus the sum of extended pricing for the four option-years as stated in attachment 5, paragraph MCP2.1. The offeror shall propose unit pricing per CLIN / SubCLIN as requested in the RFP model contract and Pricing Matrix (electronic cost model).

LCP2.2. Pricing Particulars

LCP2.2.1. Rounding

All dollar amounts shall be rounded to two (2) decimal places to the right of the decimal point. The electronic cost model format provides for decimal places that must be in accordance with this required decimal format. If any pricing proposal deviates from this format, the government will apply the specified format to determine the TEP.

LCP2.2.2. Annual Price Changes

Proposed price increases greater than 5 percent per year shall be verified and addressed for reasonableness and balanced pricing in this section. Unexplained unit price variances between sequential performance period years could suggest unbalanced pricing. It is in the offeror’s best interest to provide an explanation of any significant annual CLIN / SubCLIN price variances.

LCP2.2.3. Subcontractor and Vendor Pricing

Include a detailed explanation of offeror’s determination of proposed subcontractor or vendor pricing considered fair and reasonable. As prime contractor, documentation is required to demonstrate subcontractor / vendor quotes are considered fair and reasonable. Also include a detailed description of offeror’s process for evaluating subcontractor / vendor pricing in offeror’s determination of fair and reasonable pricing.

LCP2.2.4. Explanation of Specific Estimating Techniques and Methods

Explain the methodology used to estimate prices in the development of the 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 offeror’s disclosure statement as appropriate. The government reserves the right to obtain information from the Contract Business Analysis Repository (CBAR) as considered necessary.

LCP2.2.5. Estimating System

Provide a summary description of the offeror’s standard estimating system or methods. Also, identify any deviations from offeror’s standard estimating procedures in preparing this proposal volume. Indicate whether the offeror has government approval of this system and if so, provide evidence of such approval.

LCP2.2.6. Purchasing System

Provide a summary description of offeror’s purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provisions are made to ensure quantity and other discounts). Also, identify any deviations from offeror’s standard procedures in preparing this proposal. Indicate whether offeror has government approval of the system and if so, provide evidence of such approval.

LCP2.2.7. Accounting System

Provide a summary of offeror’s accounting system or methods. Provide a current disclosure statement and discuss any pending revisions applicable to this solicitation. Indicate whether the offeror has government DCMA approval of the accounting system and if so, provide evidence of such approval. Also, identify any deviations from offeror’s standard procedures in preparing this proposal.

LCP2.2.8. Past Experience Basis of Estimate

When 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 data available from the past experiences was adapted to the current effort pricing.

LCP2.2.9. Proposed Price Reduction per Corporate/Management Decision

I…