Attachment 20 Section L Draft.pdf

FA2488-22-R-B003

Attachment 20 Section L

Attachment 20

Section L Instructions to Offerors

Eglin Operations and Maintenance Services (EOMS)

II

2 OCT 2024

SECTION L

INSTRUCTIONS TO OFFERORS (ITO)

L-1.0 General Instructions to Offerors

L-1.1 The offeror's proposal must include all data and information requested by this Instructions to Offerors (ITO) and must be submitted in accordance with these instructions. The offer shall comply with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

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

L-1.3 Elaborate documentation, detailed artwork, or other embellishments are unnecessary and not desired.

L-1.4 The proposal acceptance period is specified in Block 12 of the SF33 of the model contract/solicitation. The offeror’s signature on the SF33 will be considered acceptance of the proposal acceptance period.

L-1.5 These proposal instructions are designed to assist offerors in preparing a complete response that reflects a full understanding of the approach proposed to accomplish all contractual requirements. Section M details how proposals will be evaluated. Offerors are expected to comply with all requirements of this Request for Proposal (RFP).

L-1.6 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 to be eligible for award. By submission of its offer, the offeror consents and agrees to all solicitation requirements and identified constraints.

Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Non-conformance with the instructions provided may result in an unfavorable proposal evaluation or rejection of an offeror’s proposal, rendering it ineligible for award.

L-1.7 Cross-Teaming Restriction.

The Government seeks to maximize full and open competition among offerors and ensure that it receives proposals that are free from any Offeror incentives or disincentives that may favor one proposal over another. To help safeguard the integrity of the procurement process, Offerors who submit proposals as prime contractors for this contract, or as a member of a joint venture (JV) prime contractor, may not also serve as a subcontractor to another Offeror submitting a proposal as a prime contractor for this contract.

L-1.8 Points of Contact.

The Procuring Contracting Officer (PCO), Mr. Ronald Wilson, is the primary point of contact for this acquisition. Address any questions or concerns to the PCO at ronald.wilson.22@us.af.mil with a courtesy copy to Mr. John Sarver at john.sarver.2@us.af.mil.

L-1.9 Discrepancies, Errors, and Omissions

If an Offeror believes the requirements in these instructions lack clarity or contain an error, omission, discrepancy, ambiguity, or are otherwise unsound, the Offeror shall immediately contact the PCO in writing with supporting rationale. Government responses will be posted to SAM.gov for access by all Offerors.

L-1.10 Consideration of Alternate Proposals

Alternate proposals will not be considered.

L-1.11 Electronic Reference Documents

A Bidders’ Library has been established in SAM.gov containing access instructions/documents to assist in the preparation of proposals. All other referenced documents for this solicitation will be made available on SAM.gov and the Procurement Integrated Enterprise Environment (PIEE) (https://piee.eb.mil) Solicitation Module. Potential offerors are encouraged to subscribe for real-time email notifications when information has been posted to the website for this solicitation.

L-1.12 Amendment of Solicitation Prior to Proposal Closing

The Government reserves the right to revise and amend the solicitation prior to the proposal closing time. Such revisions or amendments will be communicated by amendment(s) to this Request for Proposal. If such amendments require material changes in quantities or prices, the proposal closing date may be postponed by enough days to enable offerors to revise their proposals. In such cases, the amendment will include announcement of the new proposal closing date and time. Amendments will be posted at SAM.gov and the PIEE Solicitation Module with the solicitation documents without notice. Offerors are responsible for accessing all amendments prior to proposal submission at SAM.gov or https://piee.eb.mil.

L-1.13 Proposal Delivery

All proposals shall be delivered electronically using the PIEE Solicitation Module (https://piee.eb.mil). Further information on the PIEE Solicitation Module can be found at:

https://pieetraining.eb.mil/wbt/xhtml/wbt/sol/index.xhtml. Proposals must be received no later than the date and time listed in block 9 of the SF 33. The maximum file size that can be uploaded into the PIEE Solicitation module is 1.9 GB. Offerors submitting proposals via the PIEE Solicitation Module should follow up via email to confirm receipt. Offerors are responsible for confirming the Government received their respective proposal submission and subcontractor submissions prior to the proposal due date. NOTE: Proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3).

L-1.14 Questions

All questions regarding this solicitation must be submitted in writing. Any questions and subsequent answers will be posted to sam.gov. It is the responsibility of the contractor to continuously monitor the site for updates. To mitigate the risks associated with the cancellation of this solicitation due to untimely submission of questions, all questions must be submitted to the individual(s) listed below no later than close of business 7 calendar days prior to the date designated for receipt of proposals. Any questions submitted after this period may not be answered.

Submit all questions to the Contracting Officer, Ronald J. Wilson via email at ronald.wilson.22@us.af.mil.

L-2.0 SOURCE SELECTION METHODOLOGY

L-2.1 Competitive, Best Value Source Selection

The Government intends to award one contract for the Eglin Operations Sustainment and Maintenance (EOMS) II effort. EOMS II is a Cost-Plus Award Fee (CPAF) with Cost Contract Line Item Numbers (CLINs) for Travel and Materials and Firm-Fixed Price (FFP) CLIN for Transition and a variety of award terms and options that allows for performance up to 10-years.

L-2.1.1 Offerors Best Terms

The Government may award without discussions but reserves the right to enter into discussions.

Therefore, the Offeror’s initial proposal shall contain the Offeror’s best terms for Technical, and Cost/price. If the Government contemplates award without discussions, the Offerors may be given the opportunity in accordance with (IAW) Federal Acquisition Regulation (FAR) 15.306 to clarify certain aspects of its proposal (e.g., the relevance of an Offeror’s past performance information (PPI) and adverse PPI to which the Offeror has not previously had an opportunity to respond) or to resolve minor or clerical errors.

L-2.1.2 Evaluation Notices (ENs)

The Government may need to conduct written exchanges with Offerors which will be in the form of an EN. Page format and limitations will be placed on responses to ENs in the event they are issued. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

L-2.1.3 Competitive Range

If discussions are to be conducted, the PCO will establish a competitive range (as set forth in FAR 15.306(c)) based on the ratings of each proposal against all evaluation criteria which will be approved by the Source Selection Authority (SSA). If the PCO determines that an Offeror’s mailto:ronald.wilson.22@us.af.mil proposal should not be included in the competitive range, the proposal will be eliminated from consideration for award and written notice of the decision will be provided to the unsuccessful Offeror IAW FAR 15.503.

If the PCO 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 PCO, with the approval of the SSA, may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

L-2.1.4 Final Proposal Revisions (FPRs)

If discussions are deemed necessary with Offerors, upon completion of those discussions, the PCO will request that the Offeror provide an FPR. Revisions to any volume(s) shall be submitted by providing two versions, one “clean” version, and one “track changes” version.

The Offeror is advised that any changes to the proposal in the FPR shall be fully addressed and / or explained and reflected in the proposed Cost/price volume. Failure to comply with this requirement can adversely influence the evaluation of the proposal. The PCO will establish a common due date and time for submission of the FPR.

When FPRs are requested, any revisions or non-compliance with contract terms and conditions submitted in the FPR may not be subject to further discussions and may render the offer unacceptable for the Government. This provision is not intended to restrict the Offeror’s opportunity to revise its proposal. Rather, it is intended to preclude any misunderstandings by the Government that could result if new or revised terms and conditions submitted in the FPR have not been fully disclosed, discussed, and understood during discussions. Hence, such new or revised terms and conditions are not solicited and, if submitted in the FPR, may render the offer unacceptable to the Government.

L-2.1.5 Debriefings

The PCO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon they may request and receive a debriefing IAW 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 the competitive range of the source selection decision IAW FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make a request IAW the requirements of FAR 15.505 or 15.506, as applicable.

L-2.1.6 Communications and Exchanges

Exchanges of source selection information between Government and Offerors will be controlled by the PCO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Controlled Unclassified Information and 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. NOTE: Proposal submissions shall follow the instructions provided in L-13.

L-2.2 Proposal Content

To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation by the Government 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 its facilities and experience and will base its evaluation on the information presented in the Offeror's proposal. The Offeror’s proposal shall demonstrate that the Offeror possesses the technical expertise and past performance to perform the Performance Work Statement (PWS) requirements.

The Offeror’s proposal shall include all of the information requested and shall comply fully with these Section L instructions. Failure to do so may cause the Offeror’s proposal to be eliminated from consideration for award. Offerors are reminded to properly mark proposal documents which contain proprietary or restricted information.

NOTE: IF THE PROPOSAL IS NOT RECEIVED BY THE DUE DATE / TIME SPECIFIED,

THE OFFEROR’S PROPOSAL IS CONSIDERED LATE IAW FAR 52.215-1.

With the exception of the Cost/Price Volume, no cost or pricing information should appear in any other volume. The Government advises Offerors that taking exception to or deviating from any term or condition of the RFP may make an offer unacceptable and the Offeror ineligible for award.

The proposal acceptance period is specified in Block 12 of the solicitation. By signing in Block 17 of the SF33, the Offeror acknowledges that the proposal is valid for a period of not less than 280 days from the proposal due date.

L-2.3 PROPOSAL ORGANIZATION

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the various technical and management approaches, as well as past performance and cost/price, to be meaningfully evaluated without discussions. The offer must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and are not desired.

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. Proposal submissions via email will not be accepted. IAW FAR Subpart 4.8, Government Contract Files, the Government will retain an electronic copy of all unsuccessful proposals.

The Offeror’s electronic copies shall be submitted in an un-compressed format readable and searchable by Microsoft (MS) Office 2016 (or later) applications. Use separate files to permit rapid location of all portions, exhibits, annexes, and attachments, if any.

L-2.3.1 ORGANIZATION/NUMBER OF COPIES/PAGE LIMITS

L-2.3.1.1 The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table L-2.3.1.1-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 as specified in Table L-2.3.1.1-1. The Offeror’s proposal shall consist of three separate volumes: Volume I – Contract Documentation, Volume II – Technical Proposal, Volume III Cost/Price Proposal. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table L-2.3.1.1-1: Proposal Organization

Volume ITO Paragraph Number

Volume Title Maximum Number of Pages

I Contract Documentation N/A II Technical Proposal 150

III Cost/Price Proposal N/A

L-2.3.1.2 Page Limitations

Page / character limitations shall be treated as maximums. If exceeded, the excess pages / characters will not be read or considered in the evaluation of the proposal and the Offeror will be notified. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, the sheet counts as two pages. All pages count towards the maximum page limitation except the cover pages, tables of contents, glossaries, list of table and drawings, acronym list, cross reference matrix, small business subcontracting plan, and organizational conflict of interest mitigation plan. A cross-reference matrix will not be counted in the page limits. All pages shall be numbered. All ENs will specify the page limitation for the Offeror’s EN response.

L-2.3.1.3 Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. Page size shall be

8.5 x 11 inches, not including displays as defined in paragraph (b) below. Pages shall be single spaced. 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. In the event the Offeror creates an ambiguity, the Government may exercise its own discretion in counting pages. These page size and format restrictions shall also apply to responses to ENs.

(b) Legible tables, charts, drawings, graphs, diagrams, schematics, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, and plans. These displays shall be uncomplicated, legible, shall not exceed 11 x 17 inches in size, and may only be used for large tables, charts, drawings, graphs, diagrams, schematics, and figures, not for pages of text. 11 x 17-inch pages shall count as two pages. For these displays, the text shall be no smaller than 10-point font.

L-2.3.1.4 Cross-Referencing

Offerors shall write each volume on a stand-alone basis, meaning the Government must be able to evaluate each volume without having to cross reference 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 where its use would conserve space without impairing clarity. The Offeror shall provide a solicitation cross reference matrix indicating, by ITO or PWS paragraph number, the corresponding proposal paragraph in that section that addresses the referenced item. Offerors must ensure that cost/price information is only included in Volume III. Do NOT include any cost/price information in Volume II.

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

L-2.3.1.6 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used within the volume.

Glossaries do not count against any page limitations.

L-3.0 SPECIFIC INSTRUCTIONS

L-3.1 VOLUME I – CONTRACT DOCUMENTATION

L-3.1.1 Volume I Organization

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file(s).

L-3.1.1.1 Cover Letter. The cover letter shall include the business status / categories, Offeror primary and alternate points of contact with email / phone and who is authorized to contractually obligate the Offeror, Commercial and Government Entity (CAGE) Code, Unique Entity Identification (UEI),a statement that the Offeror understands the requirements specified and will meet the requirements therein, and a statement that the Offeror does or does not take exception to any of the requirements of this solicitation.

L-3.1.1.2 Master Table of Contents. The Offeror shall include a master table of contents of the entire proposal within the Contract Documentation Volume. This master table of contents shall contain a consolidation of the individual table of contents for all volumes.

L-3.1.1.3 Executive Summary. The Executive Summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with the Section M evaluation factors / subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal. The Executive Summary shall not exceed 5 pages.

L-3.1.1.4 Solicitation / Representations and Certifications

The Offeror’s proposal shall include a signed copy of the SF 33, and Sections A through K. This includes:

L-3.1.1.4.1 Section A – Solicitation / Contract Form

Complete the “Offeror” portion of the SF 33 in its entirety. An official having the authority to contractually bind the Offeror’s company shall sign the SF 33 IAW FAR 4.102.

L-3.1.1.4.2 Section B – Supplies or Services and Costs/prices

Complete pricing information in Section B of the SF33.

L-3.1.1.4.3 Sections G - I

Complete fill-ins as applicable

L-3.1.1.4.4 Section K – Representations, Certifications, and other Statements of Offeror

Complete representations, certifications, acknowledgements, and statements.

L-3.1.1.5 Exceptions or Assumptions 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. 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. The Offeror shall 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 L-3.1.1.5-1.

Table L-3.1.1.5-1: Solicitation Exceptions

Solicitation Document Page / Paragraph Requirement / Portion Rationale

PWS, SF33, etc. Applicable page and paragraph numbers

Identify the requirement or portion to which exception is taken

Describe why therequirement can / will not be met

L-3.1.2 Other Information Required

L-3.1.2.1 Authorized Offeror Personnel

Provide the name, title, telephone number, and email address 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.

L-3.1.2.2 Government Offices

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

L-3.1.2.3 Company / Division Address, Identifying Codes, and Applicable Designations

Provide company / division street address, county, and facility code; CAGE code; UEI; Taxpayer Identification Number; size of business (large or small IAW NAICS 541330, Exception 1); and labor surplus area designation (if applicable). If proposing as a JV, provide the information above for each JV partner. 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.

L-3.1.2.4 Attachments to the SF33

The Offeror shall provide the following as attachments to the SF33:

L-3.1.2.4.1 Government Furnished Property (GFP)

The Government plans to provide the items listed in the RFP, Attachment 4. Although not anticipated, if the Offeror requires the use of GFP (including vehicles and facilities) other than the property specified, the Offeror shall provide a listing including quantity, federal stock number, nomenclature, date needed and duration of availability, estimated fair rental value (IAW FAR clause 52.245-1), reason for need, and cross reference to Cost/Price volume paragraphs which pertain to GFP and/or base support. The Offeror shall also provide the written authorization from the cognizant Contracting Officer, as applicable. A statement from the Contracting Officer must also be included in the proposal indicating that such Government owned property will be available for the timely completion of performance under the ensuing contract on a non-interference basis, whether or not the proposal is based on “No Charge for

Use.” The Offeror must also indicate whether or not the Offeror could perform the work in the event that the use of such GFP is not authorized or the contract authorizing the GFP is phased out. If the Offeror proposes use of GFP under a Government contract, the usage will be limited IAW the terms and conditions of the contract, inclusive of any negotiated phased-out program.

The Offeror is responsible for updating Attachment 4 to reflect GFP requirements. Any additional GFP required by the Offeror should be labeled Contractor Specific GFP and should be indicated in bold font. Any GFP not required by the Offeror should be deleted and annotated.

The Offeror shall supply this information in the format shown below in Table L-3.1.2.4.1-1.

Table L-3.1.2.4.1-1: Example Required Information for Using GFP / Base Support

Quantity

National Stock Number (NSN) or

Part

Nomenclature

Duration of Need

Rental Value

Reason for Need

Offeror’s Shipping Address

2 Ea

FS156- 09-

ACG-1372

Time Counter

1 Oct 10 –

30 Dec 10

$1,000.00

Needed to calibrate 5 mhz/1 pps SATCOM

Simulator offset

103 East Driveway

L-3.1.2.4.2 OCI Plan

The Offeror shall provide a written OCI mitigation plan, which outlines the Offeror’s approach for detecting, avoiding, and mitigating OCI issues and risks IAW Special Contract Requirement Clause FA2488.52.203-9Z01, Organizational Conflicts of Interest (APR 2023) and FAR Subpart

9.5. The plan shall address all actual, potential, or perceived OCIs for the Offeror, including those resulting from teaming arrangements. The plan should reflect the results of the Advisory Multi-Step Process, updated with any relevant changes to the Offerors and each team members or team member affiliates particular circumstances. Any changes or updates to the OCI mitigation plan occurring after proposal submission shall be provided as such changes occur, but no later than contract award. The OCI mitigation plan will be made a part of the resultant contract.

An Offeror’s failure to provide an acceptable OCI mitigation plan will cause the Offeror to be determined non-responsible and relieves the Government of any further obligation to resolve OCI issues. See FAR Subpart 9.504(e). Notices to Offerors of OCI issues and their responses thereto are not negotiations or discussions as those terms are used in FAR 15.306(d).

L-3.1.2.4.3 Transition Plan

As required by paragraph L-3.2.5.

L-3.1.2.4.4 Small Business Participation Commitment Document

As required by paragraph L-3.2.2.5.1

L-3.1.2.4.5 Small Business Subcontracting Plan

As required by paragraph L-3.2.2.5.2

L-3.1.2.4.6 Small Business Past Performance

As required by paragraph L-3.2.2.5.3

L-3.2 Volume II – Technical Propsal

L-3.2.1 General

The Offeror shall make sure the Technical Proposal Volume is specific and complete. Legibility, clarity, and coherence are very important. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying the subfactors identified below. 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. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. It is the Offeror’s responsibility to ensure the completeness of its proposal. The Government does not assume that an Offeror possesses any capability that the Offeror fails to identify in its proposal.

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

• Table of Contents

• List of Tables and Drawings

• Glossary

• Cross Reference Matrix

• Contract Work Breakdown Structure and Dictionary

• Subfactor 1.1: Management Approach o Workload Management o Budget Management o Quality and Performance o Management Operations Execution o Prior Experience o Subcontracting Management o Small Business Participation Commitment Document o Small Business Subcontracting Plan

• Subfactor 1.2: Technical Operations o Operation of Test and Test Support Assets o Lifecycle Sustainment o Sustainment and Modernization o Sustainment and Modernization Execution o Data Assertions

• Subfactor 1.3: Qualified Personnel o Key Personnel o Staffing Plan

• Subfactor 1.4: Transition

L-3.2.2 Subfactor 1.1: Management Approach (PWS 4.1.1)

The Offerors shall provide an approach to managing the diverse workforce necessary to meet all PWS requirements, including an assessment of the risks uniquely associated with this approach and the Offeror’s plan to mitigate these risks. The Offeror shall describe its methodology to meet the Management Approach requirements outlined in the Measures of Merit identified in Section M; specifically describe how the Offeror will incorporate risk management into all aspects of its approach. Offerors shall demonstrate their approach to capitalize on the advantages of contemporary workforce management technology. The approach should clearly demonstrate the methods and strategies that will be employed to design and implement tools and systems aimed at improving workforce efficiency and productivity.

The Offeror’s shall provide their management approach from the Program Director down to the supervisors with assignment of responsibility and accountability to execute the requirements of the PWS. Include organizational structure for the Program Director to the lowest supervisory level of the contract and for any positions responsible for managing one or more PWS Major Mission Area (General Support Services, Range Support Services, Range Instrumentation Systems, Explosive Test Facilities, and Major Ground Test Facilities (MGTF)). The Offeror shall describe its key interfaces with multiple contractors and Government entities and the associated contractual issues. Discuss how the Offeror’s approach will ensure cohesive integration among the various interfaces.

L-3.2.2.1 Workload Management (PWS 4.1.3, 4.1.4, 4.1.5, 4.1.6)

The Offeror shall describe its management approach to accommodate significant workload increases and decreases, including shifts in the baseline mission workload and anticipated surge workload. Describe the Offeror’s plan to execute baseline test operations and maintenance while simultaneously conducting large-scale improvement, restoration, and modernization efforts.

Address changes that occur both year-to-year and within the execution year.

L-3.2.2.2 Budget Management (PWS 4.1.19)

The Offeror shall describe its management approach to provide the Government with accurate financial estimates in their annual DBA spend plan and meet the Government provided DBA spend plan goal. Discuss how the Offeror’s approach will appropriately manage cost while ensuring they will not exceed DBA budget. Discuss how the Offeror’s approach will ensure efficiency in DBA and Reimbursable Budget Authority (RBA) execution to minimize charging DBA during regular work hours and overtime RBA to support test missions. Discuss how the Offeror’s approach will provide government oversight on risk management & acceptance to avoid decisions on funds allocation leading to poor care for test and training capabilities.

L-3.2.2.3 Quality and Performance Management (PWS 4.1.1, 5)

The Offeror shall describe its management approach to performance measurement.

Specifically, describe the Offeror’s key test operations and sustainment metrics, including formulas, if applicable, that internally track progress and performance. In addition, provide recommended key metrics for the Government’s use to evaluate the Offeror’s performance.

The Offer shall describe its approach to implementing a Quality Assurance Program. Describe how the contractor will assign responsibilities, allocate resources, and establish processes to meet PWS requirements without need for Government inspection and multiple corrective action cycles. Describe how non-conformance with any PWS requirement will be identified, documented, tracked, corrected, and communicated to the Government.

L-3.2.2.4 Management Operations Execution

The Offeror shall describe its approach to the Management Operations Scenario defined in Attachment L-1. T he Offeror’s approach shall address each of the questions listed in Attachment L-1.

L-3.2.2.5 Prior Experience

The Offeror shall provide a list of prior experience references for themselves and all major subcontractors and teaming partners. Each reference must include the contract number, a summary of the work performed, and a description of how the reference directly relates to the requirement as specified in the PWS. Reference pages will not count towards page limitations.

The Offeror shall provide up to three (3) references for themselves and each major subcontractor and teaming partner, if applicable. Each reference must be from a separate contract and must be ongoing (within a minimum of 1-year of performance) or have been completed within the past five (5) years of the date of the solicitation.

The Offeror shall provide contact information for each reference, including the name, title, organization, phone number, and email address of a point of contact who can verify the information provided.

The Government will use the references provided to evaluate the Offeror's technical capabilities, and experience. The Government may also use the references to validate the Offeror's proposed approach and to assess the Offeror's ability to meet the requirements of the proposed contract.

L-3.2.2.6 Small Business Participation

The Government’s evaluation of small business participation for this subfactor is separate and distinct from the Offeror’s Small Business Subcontracting Plan as required in L-3.2.2.6.2. The evaluation of Small Business Participation via submittal of a proposed Small Business Participation Commitment Document (see L-3.2.2.6.1 below) shall apply to all Offerors.

L-3.2.2.6.1 Small Business Participation Commitment Document

Small Business Participation Commitment Document: All Offerors, small businesses and other than small businesses (including Comprehensive Subcontracting Plan Program Participants and Commercial Subcontracting Plan Holders) shall provide a “Small Business Participation Commitment Document (SBPCD)” in response to the solicitation’s small business participation requirements which shall be evaluated in accordance with section M-2.2.4.6.1 of this solicitation. Offerors’ proposed Small Business participation requirements/commitments shall be incorporated into any resultant contract and monitored as a measure of contract compliance. These requirements apply at the prime contract and first tier subcontract levels.

Small business concerns that qualify in more than one socioeconomic category may be counted in each category for which they qualify. Small business past performance will be evaluated for this acquisition (see L-3.2.2.6.3 below) in accordance with Section M-2.2.4.6.3 of this solicitation. A template for this document is provided as Attachment L-3. This document will not be included in page limitations.

L-3.2.2.6.2 Small Business Subcontracting Plan

The Offeror shall submit a Small Business Subcontracting Plan IAW FAR 52.219-9, Small Business Subcontracting Plan, that also identifies the extent of the Offeror’s commitment to the participation of small business, veteran-owned small business, service-disabled veteran-owned small business, HUBZone small business, small disadvantaged business, and women-owned small business concerns, whether as JV members, teaming arrangement partners, or subcontractors. Contractor must be able to meet no less than the DoD Small Business Subcontracting Goals for 2024: https://business.defense.gov/About/Goals-and-Performance/.

The Small Business Subcontracting Plan shall be included in Volume I, Contract Documentation (see L-3.1.2.4.5) and will be made a part of the resultant contract. This plan will not be included in page limitations.

L-3.2.3 Subfactor 1.2: Technical Operations

The Offeror shall describe its approach to meet the Technical Operations requirements outlined in the PWS; specifically describe how the Offeror will incorporate risk management into all aspects of its approach.

L-3.2.3.1 Operation of Test and Test Support Assets https://business.defense.gov/About/Goals-and-Performance/

The Offeror shall describe its overall approach to facility operations in support of testing.

Describe the Offeror’s methodology to ensure delivery of test environments and system operational data.

L-3.2.3.2 Lifecycle Sustainment (PWS 4.1.9, 4.1.10, 4.1.11)

The Offeror shall describe its lifecycle sustainment program for test and test support assets.

The Offeror shall describe how safe and effective the program will be by describing the Offeror's approach to balancing the elements of performance, cost, and risk. In addition, the Offeror shall describe its understanding of software lifecycle management, including configuration management and development principles required during development, test, production, and execution.

Describe the Offeror’s approach to scheduled and unscheduled maintenance of range items and approach to restoring range capability after an unplanned outage. Describe how the contractor achieves a responsive and holistic approach to fault detection, isolation, and restoration during both mission and non-mission intervals and reports system status to the Government. Describe proposed strategies to achieve high range item availability and reliability as operations tempo increases and the time for preventive maintenance and checkout decreases. Describe how an integrated maintenance schedule is developed, how priority conflicts that impact required maintenance are resolved, and how these approaches maximize range capacity.

L-3.2.3.3 Sustainment and Modernization (PWS 4.1.24)

The Offeror shall describe its approach to applying systems engineering processes throughout the acquisition lifecycle. Discuss how this approach will lead to the delivery of new capabilities and modifications / upgrades to current facilities on time and on cost while meeting technical requirements. Describe in detail the Offeror’s approach to managing requirements, risks, design processes, and configuration management.

Describe the Offeror's approach for developing an optimized future range architecture while maximizing the performance of the Eglin Test and Training Center (ETTC). Describe how the Offeror’s approach enables the Government to leverage technology to meet the demand for future range capacity and capability.

Describe the Offeror’s existing internal programs and policies that promote a culture of continuous improvement and the results of the programs and policies including an assessment of any risks uniquely associated with these specific ideas and plans, and the Offeror’s plan to mitigate these risks. Continuous improvement includes, but is not limited to, operational efficiencies, enhanced relevancy, a reduced reliance on Direct Budget Authority (DBA) funding, and innovation.

L-3.2.3.4 Sustainment and Modernization Execution

The Offeror shall describe its approach to the Sustainment and Modernization Scenario defined in Attachment L-2. The Offeror’s approach shall address each of the questions listed in Attachment L-2.

L-3.2.3.5 Data Assertions

If the Offeror makes any assertions when completing Section K (DFARS 252.227-7017(d)), the Offeror shall identify each assertion correlated to each individual item of intellectual property to be delivered, provided, or otherwise furnished to the Government during contract performance. The Offeror shall do so by adding a parenthetical after its identification of each individual item of "Technical Data or Computer Software to be Furnished with Restrictions" in its completed DFARS 252.227-7017 representation that identifies the specific part of the contract (e.g., Contract Data Requirements List (CDRL) number, PWS paragraph) that will require the awardee to deliver, provide, or otherwise furnish that intellectual property to the Government.

L-3.2.4 Subfactor 1.3: Qualified Personnel

The Offeror shall describe its approach to meet the Qualified Personnel requirements outlined in the Measures of Merit identified in Section M.

L-3.2.4.1 Key Personnel

The Offeror shall identify key positions and the qualifications for each key position. The Offeror shall describe the approach that will be taken to employ the key personnel for the EOMS II effort, to include a management philosophy, employing the right leaders, back-fill contingency plans, and how this approach will maximize performance while also managing risks.

L-3.2.4.2 Staffing Plan The Offeror shall provide a comprehensive Staffing Plan that also includes the Minimum Team Complement (MTC) defined in PWS Appendix 1 that addresses the approach to promote employee retention, morale, productivity, growth, and development. Specifically, the Staffing Plan shall describe, 1) the Offeror’s recruitment and retention policies, 2) the Offeror’s plan to create more depth of experience across the workforce, 3) the Offeror’s approach to capturing institutional knowledge of critical skillsets, and 4) the Offeror’s approach to maintain the staff and skills necessary to execute the ETTC’s standard baseline operations while simultaneously executing significant increases in workload requirements due to anticipated surge projects. The approach shall include the Offeror’s understanding of the risks uniquely associated with the staffing strategy, processes, or approach, and the Offeror’s approach to mitigate these risks.

Address any difficulties anticipated in fulfilling the staffing requirements of the EOMS II contract and the plans to overcome those difficulties. The Staffing Plan will not be included in the Technical Volume page count.

If the Offeror’s approach to fill one or more of the MTC positions is with non-incumbent personnel, then the Offeror shall provide the position title(s) and reasoning behind the replacement(s).

L-3.2.5 Subfactor 1.4: Transition (PWS 8)

The Offeror shall provide a detailed Transition Plan to assume the responsibilities outlined in the PWS, including phase-in and phase-out activities. Discuss how the Offeror will meet the EOMS II requirements and ensure there is no interruption or degradation in delivery of services in support of the ETTC mission. The Transition Plan shall include 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 ETTC contractors, disruption, risk, and schedule.

The Transition Plan shall be included in Volume I, Contract Documentation (see L-3.1.2.4.3) and will be made a part of the resultant contract. The Transition Plan will not be included in the Technical Volume page count Contract Data Requirements List (CDRL) number, PWS paragraph) that will require the awardee to deliver, provide, or otherwise furnish that intellectual property to the Government.

L-3.3 VOLUME III – COST/PRICE PROPOSAL

L-3.3.1 Volume III Organization

The Cost/price Volume shall be organized according to the following general outline:

• Introduction

• Table of Contents

• Summary Descriptions of Estimating, Purchasing, and Accounting Systems

• Changes to Estimating, Accounting Practices, or Cost Accounting Standards (CAS) Disclosure Statement

• Estimating Methodology

• Cost and Supporting Information (Attachments L-4, Cost Model for Primes and L-5, Cost Model for Subcontractors)

• Professional Employee Compensation Plan

• Other Information. List each exception to the ground rules and assumptions provided in the solicitation and each qualification of the Cost/price volume, if any. Provide complete rationale for any exceptions.

L-3.3.2 Price Information

L-3.3.2.1 General Instructions

This section is to assist Offerors in submitting data other than certified cost or pricing data that is required to evaluate the completeness, reasonableness, realism, and balance of the proposed cost/price.

Compliance with these requirements is mandatory and failure to comply may result in rejection of the Offeror’s proposal. Note that unrealistically low or unreasonably 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 unreasonable proposal. Additionally, unbalanced pricing that poses an unacceptable risk to the Government may be a reason to reject an Offeror’s proposal. Offers should be sufficiently detailed to demonstrate reasonableness, realism, and balance. The burden of proof for credibility of proposed costs/prices rests with the Offeror.

Data beyond that required by this instruction shall not be submitted, unless the Offeror considers it essential to document or support its cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

L-3.3.2.2 Estimating Techniques and Methods

When responding to the Cost/price Volume requirements in the solicitation, the Offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (e.g., Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships, commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop estimates.

L-3.3.2.3 Cost or Pricing Data

The PCO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the PCO will review this determination and if, in the PCO’s opinion, adequate price competition exists no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. 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 certified cost or pricing data.

L-3.3.3 Accounting System

An acceptable accounting system is required. Indicate whether the Offeror has an acceptable accounting system as defined in DFARS 252.242- 7006. Also, identify any deviations from the Offeror’s standard procedures in preparing this proposal.

L-3.3.4 Purchasing System

The Offerors shall provide a summary description of 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, Offerors shall identify any deviations from standard procedures in preparing proposals. Offerors shall indicate whether or not they have Government approval of their purchasing system and if so, provide evidence of such approval.

L-3.3.5 Estimating Methodology

Provide a summary description of the Offeror’s standard estimating system or methods. The summary description shall cover separately each cost element (e.g., labor, indirect costs, other direct costs, overhead, General and Administrative [G&A]). Clarify if a portion of the required information is not applicable for a particular cost element. Also, identify any deviations from the Offeror’s standard estimating procedures in preparing this proposal volume

L-3.3.5.1 Past Experience

Identify where the Offeror’s cost estimates are based upon past experience, identify the past experience, explain how the past experience relates to the current effort, including similarities and differences, and how cost data available from the past experiences was adapted to the current effort.

L-3.3.6 Government-Provided Cost Considerations

L-3.3.6.1 Commonality with Other Programs

Any cost reductions made in the Offeror’s proposal that are attributed to commonality with other programs, company funded efforts, or capitalization of equipment must be supported with the following:

(a) Commonality - Identify the specific program(s) and why it is applicable. Address the cost allowability and allocability of this action per FAR and the Offeror’s CAS Disclosure Statement.

(b) Company-Funded Efforts - Identify the specific efforts, the planned start and end dates, the applicability to the current solicitation, the source of company funding, and how the Offeror plans to account for or allocate these costs IAW generally accepted accounting principles and the Offeror’s CAS Disclosure Statement, if applicable.

(c) Capital Equipment - Identify the specific item(s) capitalized and what other applications exist for the equipment, provide corporate approvals for each action, address the cost allowability and allocability of the action per the FAR and the Offeror’s CAS Disclosure Statement.

L-3.3.6.2 Schedule of Hours by Labor Skill Mix

The schedule of hours by skill mix is provided when Offerors fully complete Attachments L-4, Cost Model for Prime…