Attachment_8,_Section_L_FRFP.pdf

FSS II

FA9101-18-R-1000

Attachment 8

SECTION L

AEDC-L001. INFORMATION TO OFFERORS (ITO) (NOVEMBER 2018)

L-1.0. Program

This acquisition is for the Facility Support Services (FSS) II at Arnold Engineering Development

Complex (AEDC). The effort will be performed primarily at Arnold Air Force Base (AFB) in

Tennessee. Specific performance will also be required at AEDC facilities housed as tenants on sites at Tunnel 9 in White Oak, MD and on the National Aeronautics and Space Administration

(NASA) Ames Research Center (ARC) grounds at Moffett Field, CA. The FSS contract provides industrial and test security, security services, command, control, and communication functions, fire and emergency services, environmental, safety, occupational and environmental health, base supply, cargo movement, and vehicle maintenance. The AEDC mission is to provide developmental test and evaluation (DT&E) to Air Force Materiel Command (AFMC), other Air Force Major Commands (AF MAJCOMs), Department of Defense (DoD), and other users. AEDC also performs tests for foreign governments and companies when so required. The current contract was one of six efforts that were awarded in 2015. Previously, the FSS services were included in the operations and maintenance contracts at AEDC for more than 60 years.

AEDC is a test facility of the DoD Major Range and Test Facility Base (MRTFB) managed by the Air Force as outlined in DoD Directive 3200.11.

L-1.1. Budget / Funding Information

These services are continuing in nature and are necessary for operations at AEDC Arnold AFB, AEDC White Oak, MD and AEDC Moffett Field, CA. All the efforts included in this contract are efforts for which Congress has consistently appropriated funds. Total resources available in any fiscal year are based upon a budget subject to congressional approval and funding allocation to AEDC. Contract modifications for budget shortfalls may occasionally be necessary but are not anticipated.

The Government estimate of full-time equivalent (FTE) employees required for this effort is shown in the table below. These FTE estimates are approximate and are provided for Offerors only. This estimate is only provided as a reference to allow Offerors to better understand the general scope of this effort from the Government’s perspective.

PWS

FTEs

3.1 Industrial Security, Test Security, Security Management

Support 12.4(a)

3.2 Security Services 60

3.3 Command, Control, and Communications 12

3.4 Fire and Emergency Services Program 61

3.5 Environmental Program 15.5

3.6 Safety Program 4

3.7 Occupational and Environmental Health 1

3.8 Base Supply 30

3.9 Cargo Movement 5

3.10 Vehicle Operations and Maintenance 11

Total

211.9

Footnotes:

(a) The PWS 3.1 estimate includes firm-fixed price and cost-reimbursable FTEs for the total scope of work required in that area. For informational purposes, 65 percent of the effort for PWS 3.1 is fixed-price work and 35 percent is cost-reimbursable.

L-2.0. General Instructions

(a) The Offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data

Requirements List (CDRL), and solicitation. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

(b) 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.

(c) Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

(d) The proposal acceptance period is specified in Section A of the solicitation. The

Offeror shall make a clear statement in Section A of the Contract Documentation Part that the proposal is valid for a period of not less than 240 calendar days from release of the Request for

Proposal (RFP). This period may be extended upon the mutual agreement of the Offeror and the

Contracting Officer.

(e) 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 within 90 days of contract award.

L-2.1. General Information

L-2.1.1. Point of Contact

The Contracting Officer, Mr. John Lominac, Jr., is the sole point of contact for this acquisition.

Address any questions or concerns you may have to the Contracting Officer at aedc.sso@us.af.mil .

L-2.1.2. Debriefings

The Contracting Officer 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 Contracting Officer will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. 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.

L-2.1.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 Contracting Officer in writing with supporting rationale as well as the remedies the Offeror is asking the Contracting Officer to consider as related to the omission or error.

L-2.1.4. Discussions

The Government may award a contract without discussions. However, in accordance with DFARS

215.306, Exchange with Offerors after Receipt of Proposals, discussions should be conducted for all acquisitions with an estimated value of $100 million or more. Award without discussions on complex, large procurements is discouraged and seldom in the Government’s best interest. In addition, if the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition. The Offeror’s initial proposal should contain the

Offeror’s best terms from a price and technical standpoint.

L-2.1.5. Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities

(FBO) website 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.

In addition, a competition library was established on the AEDC public website, www.arnold.af.mil/FSSII/, where a significant amount of unclassified information is available to potential Offerors.

L-2.1.6. Communications

Exchanges of source selection information between Government and Offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See

FAR 2.101 and 3.104” in the Subject line. Otherwise, source selection information will be transmitted via other means as appropriate. The Government may use the U. S. Army Aviation and Missile Research Development and Engineering Center (AMRDEC) Safe Access File

Exchange (SAFE), https://safe.amrdec.army.mil/safe/, to transmit / receive source selection information.

L-2.2. Specific Information

To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. The offeror’s proposal shall consist of four (4) separate volumes; Volume I - Technical Proposal, Volume II –

Past Performance Information, Volume III – Price Proposal, and Volume IV – Contract

Documentation.

L-3.0 Proposal Preparation Instructions

L-3.1. Organization / Number of Copies / Page Limits

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

Table 3.1 - Proposal Organization

VOLUME

ITO Paragraph

Number

VOLUME TITLE

COPIES

(Electronic

/ Paper)

PAGE LIMIT /

GOAL

I L-4.1 Technical Proposal (1 / 2) 100 / NA

II L-4.2 Past Performance Information (1 / 2) See Note

III L-4.3 Price (1 / 2) NA

IV L-4.4 Contract Documentation (1 / 2) NA

Note: For Volume II, Past Performance, each submitted performance reference shall not have the

EZSource fields of “Contract Information” and “Program Details” together sum to a character count (excluding spaces) of greater than 27,000 characters.

L-3.1.1. Page Limitations

Page / character limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the Offeror as soon as practicable. Page limitations may be placed on responses to Evaluation

Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Each page shall be counted except the following: Cover pages, tables of contents, glossaries, tabs, the cross-reference matrix, Staffing and Organization

Plan, Quality Management System Plan, Risk Management Plan, Transition Plan, Mission-

Essential Contractor Services Plan.

L-3.1.2. Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x

11 inches, not including foldouts. Pages shall be typed with single line spacing. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point

Times New Roman font. 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 ¾-inch side margins. Pages shall be numbered sequentially by volume.

These page size and format restrictions shall also apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

(b) Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page, i.e., information shall only be on one side of the page. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 8 point. These limitations shall apply to both electronic and hard copy proposals.

L-3.1.3. Cross-Referencing

To the greatest extent possible, each Volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross-referencing to other Volumes of the proposal. Information required for proposal evaluation which is not found in its designated

Volume will be assumed to have been omitted from the proposal.

The Offeror shall complete Attachment L-7, Cross-Reference Matrix (CRM), which assures all requirements are addressed and easily accessible to the evaluators. The CRM shall be included in Offeror’s proposed Technical Volume (see L-4.1) but will not be included in page count. The

CRM must provide a single integrated index for the entire proposal. This index shall cross reference the Performance Work Statement (PWS), Section L, and Section M to the Offeror’s proposal.

L-3.1.4. Binding and Labeling for Paper Copy

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

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

Selection Information.

L-3.1.5 Requirements for Electronic Copy

The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD the Volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any.

The Offeror shall submit Volumes I through IV in electronic format, using virus-free CD-R. The

Offerors shall not use CD-RW. Each Volume shall be in a different directory on a CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in both Microsoft (MS) Office Word 2010 and Portable

Document Format (PDF). Proposals shall be in a format readable and searchable by Adobe

Acrobat Version 9.0 or later, MS Office Word 2010, MS Office Excel 2010, MS Office Project

2010, and MS Office Power Point 2010, as applicable. In the event there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

L-3.2. Distribution

The "original" proposal shall be identified. Proposals shall be addressed to the Contracting

Officer and mailed or hand carried to:

AFTC/PZZ (Arnold)

Attn: Mr. John Lominac, Jr.

1307 Schriever Avenue

Arnold AFB TN 37389-5100

L-4.0. Proposal Organization

L-4.1. Volume I – Technical Proposal

L-4.1.1. General

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

Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing / satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal.

Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

L-4.1.2. Technical

In the technical volume, address the technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor.

L-4.1.3. Volume Organization

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

Table of Contents

Technical Proposal Discussion

Staffing and Organization Plan (See Para L-4.1.4.3.1)

Quality Management System Plan (See Para L-4.1.4.5)

Risk Management Plan (See Para L-4.1.4.6)

Transition Plan (See Para L-4.1.5)

Mission-Essential Contractor Services Plan (See Para L-

4.1.7.2)

Cross-Reference Matrix (See L-3.1.3)

L-4.1.4. Subfactor 1: Management Approach:

L-4.1.4.1. Provide the Commercial and Government Entity (CAGE) Code for the prime contractor, joint venture partners, and subcontractors. This code will be used to search the

Defense Security Service database to confirm the Offeror’s Top Secret Facility Clearance (TS

FCL).

L-4.1.4.2. Provide a management approach to successfully perform in a multi-contractor environment. Address, as a minimum, interfacing, integrating, coordinating, cooperating, supporting, and communicating with associate contractors identified in PWS Special

Requirement 4.3(f), Associate Contractor Agreements. Identify all applicable contract interfaces and demonstrate how the Offeror intends to successfully manage those aspects of the Offeror’s work that depend on, or are dependent on, the Government or one or more of the other associate contractors supporting Arnold AFB’s mission and vision.

L-4.1.4.3. Provide a sound resource management approach that thoroughly demonstrates how to recruit and retain qualified personnel who have the knowledge, experience, training, and technical expertise / certification / security clearances commensurate with the requirements of the

PWS.

L-4.1.4.3.1. Provide a staffing and organization plan that demonstrates the Offeror’s approach to providing human resources for each PWS functional area and how the overall program will be functionally aligned and managed. Identify any areas in which corporate support will be utilized to meet the functional requirements. The plan shall include a brief job description that defines the roles and responsibilities of each position. This plan is a separate document and will not be included in the Technical Volume page limitations.

L-4.1.4.4. Describe a viable management approach to accommodating significant workload increases or decreases. Address potential changes that could occur both year to year and within the contract performance year, and how to mitigate / eliminate operational impacts.

L-4.1.4.5. Provide a quality management system (QMS) plan that fully demonstrates the quality of services provided is the sole responsibility of the contractor. The plan shall include how the

Offeror will effectively plan, implement, execute, and maintain a documented QMS, including, but not limited to: (1) detection of Contractor performance problems and defects; (2) root cause analysis; (3) corrective action processes; and (4) follow-up, measurement, and continuous improvement. The plan shall demonstrate how the Offeror will be the proactive participant in overall program quality, both at the corporate and local levels. This plan is a separate document and will not be included in the Technical Volume page limitations.

L-4.1.4.6. Provide a detailed risk management plan that addresses any risk considered likely to have a significant adverse impact to program cost, schedule, and / or performance during the full lifecycle of the contract. The plan shall include a thorough description of the Offeror’s risk management process, including, but not limited to: (1) Risk Planning, (2) Risk Identification, (3)

Risk Analysis, (4) Risk Mitigation, and (5) Risk Monitoring. The plan shall also provide an initial risk analysis identifying known or likely risk to the program. This plan is a separate document and will not be included in the Technical Volume page limitations.

L-4.1.5. Subfactor 2: Transition Management:

Provide a detailed transition plan to assume responsibilities outlined in the PWS, including phase-in and phase-out activities. Discuss how the Offeror will meet the FSS requirements and ensure there is no interruption or degradation in delivery of services that meet the FSS requirements. The transition plan shall address the following key components as a minimum:

quality management system implementation, organization, contract implementation issues, staffing, knowledge transfer, resource requirements, Government involvement, cooperative agreements with unions and other AEDC contractors, disruption, risk, and schedule. This plan is a separate document and will not be included in the Technical Volume page limitations.

L-4.1.6. Subfactor 3: Technical Operations and Compliance:

L-4.1.6.1. Provide an approach that adequately addresses the Offeror’s technical understanding and approach to meet the requirements of each functional area listed in PWS section 3.0.

Discuss how the requirements will be accomplished in accordance with applicable laws, regulations, and governing documents. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

L-4.1.6.2. Provide an overview of the Offeror’s property management system plan. Include descriptions on the plan to manage, protect, preserve, and maintain Government-furnished property utilizing commercial practices, voluntary consensus standards, or industry-leading practices and standards.

L-4.1.7. Subfactor 4: Mission-Essential Contractor Services:

L-4.1.7.1. Provide an approach for mission-essential contractor services in accordance with

DFARS Provision 252.237-7024, Notice of Continuation of Essential Contractor Services, that meets all the essential components stated in PWS para 3.12.8.

L-4.1.7.2. Provide a Mission-Essential Contractor Services Plan to ensure that Arnold AFB component missions or responsibilities identified in PWS para 3.12.8 are operational, functional, and capable to support necessities during crisis situations, addressing the requirements of

DFARS Clause 252.237-7023, Continuation of Essential Contractor Services. This plan is a separate document and will not be included in the Technical Volume page limitations and will be incorporated into the contract.

L-4.2. Volume II – Past Performance Information

L-4.2.1. Volume Organization

The Past Performance Volume shall be organized according to the following general outline

Summary (Not to exceed two pages. See Para L-4.2.2)

Past Performance References (See Para L-4.2.3.1)

PPI Submission (See Para L-4.2.3.2)

Relevant and Recency Determination (See Para L-4.2.3.4)

Relevancy Matrix (See Para L-4.2.3.6)

Organizational Structure Change History (See Para L-

4.2.3.7)

Consent Letters. Consent letters executed by each joint venture partner, major subcontractor, and key management personnel authorizing release of adverse past performance information so the Offeror can respond to such information.

A sample consent letter is provided as Attachment L-5.

Client Authorization Letters. Client authorization letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the Offeror's performance.

List of Questionnaire Recipients (See Para L-4.2.3.2)

L-4.2.2. Summary. Describe roles of Offerors and all subcontractors, teaming partners, or joint venture partners requiring past performance information IAW Para L-4.2.3.1.

L-4.2.3. Past Performance Information (PPI) Sheets (See Attachment L-1).

L-4.2.3.1. Number of PPI References. Offerors shall submit the following on contracts considered most relevant in demonstrating the ability to perform facility support services:

information required by the PPI Tool, List of Submitted References, Relevancy Matrix, Consent

Letters, Authorization Letters, and List of Questionnaire Recipients. This information is required on Offerors, subcontractors, or joint venture partners considered relevant to overall successful performance. Offerors may submit not more than five recent and relevant contracts for the prime contractor and not more than two for each major subcontractor. If the prime is a joint venture, Offerors may submit not more than three references per joint venture partner. For purposes of proposals only, a major subcontractor is defined as a subcontractor, other than the Offeror itself, that will be responsible for one or more of the performance requirements as stated in PWS 3.1 –

3.10. For PPI references in which the Offeror’s performance occurred as a member of joint venture, please state what percent stake the Offeror had in the joint venture. 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.

L-4.2.3.2. PPI Submission. Offerors must use the PPI tool, which they shall download from the

FSS RFP posting to Federal Business Opportunities (FBO) at https:www.fbo.gov for their electronic proposal submittal of relevant past performance contract information. Offerors shall provide hard copies of the pages generated from this tool as part of their Past Performance Volume.

Offerors shall save the PPI database file as Offeror name-Volume name (PPI)-FSS.mdb (e.g., XYZ

Company-Past Performance Volume (PPI)-FSS.mdb) to submit as part of the electronic copy of the

Past Performance Volume. Once complete, PPI sheets and past performance questionnaires (PPQs) will be treated as source selection information in accordance with FAR Part 3.104.

Offerors shall send PPQs on each identified contract to the points of contact for that contract. If the identified contract was a Government effort, please send to the Program Manager and Contracting

Officer. This questionnaire is contained at Attachment L-2, Past / Present Performance

Questionnaire. Provide a list of questionnaire recipients to include POCs and phone numbers.

PPI concerning subcontractor and teaming / joint venture partners cannot be disclosed to a private party without the subcontractor’s or teaming / joint venture partner’s consent. Because a prime contractor is a private party, the Government will need that consent before disclosing subcontractor

/ teaming / joint venture partner to the prime during exchanges. Therefore, the Offeror shall submit a consent letter executed by each teaming / joint venture partner and major subcontractor authorizing release of adverse past performance information to the Offeror, so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror's performance.

L-4.2.3.3. Early Proposal Information

The Past Performance Volume is to be provided directly to the FSS II Contracting Officer not later than 11:00 a.m. Central Standard Time (CST), 21 December 2018. The past performance questionnaires are to be provided directly to the FSS II Contracting Officer not later than 11 January

2019.

L-4.2.3.4. Relevant Contracts and Recency Determination

Offerors shall submit information on recent and relevant contracts demonstrating the ability to perform the full range of capabilities IAW FSS II PWS requirements and explain how / why the referenced contracts are relevant (including joint venture partners and major subcontractors). To be recent, the effort must be ongoing for at least one year or must have been completed during the past five years from the date of issuance of this solicitation. For a description of the characteristics or aspects the Government will consider in determining recency and relevancy, see Section M-2.4.1 and M-2.4.2.

L-4.2.3.5 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This 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 is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. 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. Categorize the relevant information into the specific Technical subfactors and Cost / Price factor used to evaluate the proposal. Past performance information pertaining to Technical subfactors and the

Cost / Price subfactor not listed under the appropriate section of the proposal may not be considered.

The proposal must clearly show how experience from any entity other than the Offeror is relevant to the Offeror’s ability to perform. The relevant considerations are whether the resources of the parent / partner / subdivision / originating firm(s) will be provided or relied upon for contract performance such that the other firm(s) will have meaningful involvement in contract performance.

L-4.2.3.6. Relevancy Matrix

The Offeror shall provide a completed relevancy matrix (Attachment L-6). Provide not more than five recent and relevant contracts for the prime contractor and not more than two for each major subcontractor. If the prime is a joint venture, provide not more than three references per joint venture partner. The relevancy matrix and other past performance information will be used to establish the relevance of present and past efforts. For your submitted references (efforts cited), please place a check mark into the columns for which the reference is applicable according to the column headings (which represent the evaluation factors and subfactors). For the “Cost / Price” column, insert the contract value for the reference. The "Applicable PWS

Requirements" column is present so that a cited reference can quickly be tied to one or several of the disparate performance areas (PWS 3.1 thru 3.10).

L-4.2.3.7. Organizational Structure Change History

Many companies have acquired, have been acquired by, or otherwise merged with other companies or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant current or past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include a "roadmap" describing all such changes in the organization of your company, or joint venture partner and proposed major subcontractors. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation / performance confidence assessment. Since the Government intends to consider present and past performance information provided by other sources as well as that provided by the offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

L-4.2.4. No Applicable Past Performance Information

If an Offeror has no recent or relevant past performance information, they should so state that in this Volume. However, the Government reserves the right to determine whether any recent past performance information exists and is relevant.

L-4.3. Volume III – Price Proposal

L-4.3.1. Volume Organization

The Price Proposal Volume shall be organized according to the following general outline

Price Proposal

Cost Model (See Para L-4.3.4.2)

L-4.3.2. Price Information

This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the completeness, reasonableness, realism, balance, and total evaluated price of your proposed cost / price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their completeness, reasonableness, realism, balance, and total evaluated price. The burden of proof for credibility of proposed prices rests with the offeror.

L-4.3.3. General Instructions

L-4.3.3.1. These instructions are to assist in the submission of price / financial data and information. All information relating to the proposed price must be included in the section of the proposal designated as Price Proposal Volume. The Price Proposal Volume is not subject to page limitation.

L-4.3.3.2. Insert proposed unit and extended prices in Section B, Supplies or Services and

Prices, for each Contract Line Item Number (CLIN), including phase-in, base year, all option periods, and phase-out. Use the same quantity unit from the base period for all option years. The number of units for the phase-in and phase-out CLINs is three months. The extended amount must equal the whole dollar unit price multiplied by the number of units. All displayed dollar amounts shall be rounded to the nearest dollar. The total evaluated price (TEP) will be calculated as the sum of the offeror’s proposed base year, excluding phase-in; all option periods, including the six-month extension; and phase-out. The TEP will not include cost-type CLINS.

L-4.3.4. Instructions for Pricing Sheets

L-4.3.4.1 Cost-Type CLINS

Although every effort has been made to provide Offerors with sufficient workload data to develop an accurate proposal, some areas incur costs so irregularly, it is in the best interest of both the Government and the Contractor to include cost-type CLINs. This solicitation includes four cost-type CLINs within the basic and each exercised option. For the purposes of this evaluation, cost-type CLINs are NOT to be included in the cost model and are NOT included in the total evaluated price per M-2.5.1.5. However, Offerors shall price these CLINs in Section B of the contract with a value of $5,000 for CLINs X005, XX14, XX15, and XX16.

L-4.3.4.2. Cost Model

Offerors shall complete Attachment L-8, Cost Model. This cost model will be utilized to evaluate proposed prices in accordance with Section M-2.5. Furthermore, proposed prices will be utilized as the basis for any future contract modifications.

L-4.4. Volume IV – Contract Documentation

L-4.4.1. Solicitation / Representations and Certifications

The purpose of this Volume is to provide information to the Government for preparing the contract document and supporting file(s). The Offeror's Contract Documentation Volume shall include a completed / signed copy of the Standard Form (SF) 33 cover page of solicitation (to include any amendments), the applicable clauses, the Offeror’s completed representations, certifications, acknowledgments and statements or indicate if information is contained in the

System for Award Management (SAM), applicable attachments, and any other data the Offeror chooses to bring to the attention of the Contracting Officer. 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 and should be provided without any punched holes.

L-4.4.2. Exceptions or Assumptions to Terms and Conditions

Offerors are advised that taking exception to any of the requirements specified in this solicitation may result in the proposal being found unacceptable. Since the Government reserves the right to award without discussions, Offerors run the risk of their proposal being found unacceptable as a result of exceptions to solicitation requirements. Clarification of Government requirements and any contractor assumptions should be handled by submitting a question / recommended change prior to Final Proposal Revision (FPR). All assumptions / clarifications must be finalized prior to FPR. If the Offeror still finds it necessary to take exception to any of the requirements specified in this solicitation, clearly indicate each exception in the appropriate Volume along with a complete explanation of why the exception was taken and what benefit accrues to the

Government. All exceptions to the solicitation requirements and supporting rationale shall be identified as such and consolidated into an overview section of the subject Volume. An overview section is only required if the Offeror takes exception to any requirement in the solicitation. The overview section will not be included in the proposal page limitation described above.

L-4.4.3. List of Government Property Using on Rent-Free Basis.

Provide information required by FAR 45.201(c)(1)-(4) on Government property that the offeror or its subcontractors propose to use.

L-4.4.4. Other Information Required

L-4.4.4.1. Authorized Offeror Personnel

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

L-4.4.4.2. Government Offices

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

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

Attachments

L-1 PPI Tool

L-2 Past / Present Performance Questionnaire (PPQ)

L-3 PPQ Cover Letter

L-4 Client Authorization Letter

L-5 Subcontractor Consent Letter

L-6 Relevancy Matrix

L-7 Cross-Reference Matrix

L-8 Cost Model