C06 Amendment N6893626R50100002.pdf

R

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

16C. DATE SIGNED

Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE PAGE OF PAGES

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6) CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBE

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

Section A - Solicitation/Contract Form

The following changes have been made:

INFORMATION FROM TO

Response Due Date 08 Oct 2026 19 Oct 2026

N6893626R50100002

Section J - List of Attachments

The following attachments were added:

Attachment 5 L-4 RFP Second Set of Questions and Govt Responses

Section L - Instructions, Conditions, & Notices to Offerors or Quoters

Miscellaneous text in this section has been modified to:

PART A GENERAL INSTRUCTIONS

1. GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror's approach, expertise, and capability as required by the solicitation. Proposals must demonstrate that the Offeror has a thorough understanding of all requirements and associated risks and is able, willing, and competent to devote the resources necessary to meet all requirements. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror's proposal, deemed beneficial to the Government, into the final contract, with or without discussions. Subcontracting Plan information shall appear only in (Small Business Subcontracting Plan).Annex X

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 Government to evaluate its proposal without discussions. Unsubstantiated statements that the prospective Offeror understands, can or will comply with the specifications, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

The Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place and summarized and referenced in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

Throughout these instructions, "Offeror" is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A "Joint Venture" (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. "JV Team Members" are the entities that make up a Joint Venture. The term "entity" is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code than the Offeror). The following entities are defined as principal entities and only principal entities will be used in the past performance evaluations: (a) the prime contractor; (b) JV Team Members; and (c) other entities that are proposed to perform at least 20% f the proposed total cost/price for the contract. o Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Annex X and associated with a commensurate dollar value.

Per FAR 15.104(b)(1)(ii)(A), cost or price will not be evaluated at the basic award, as the Government intends to make award to each and all qualifying Offerors.

2. PROPOSAL FORMAT AND SUBMISSION

Offerors shall format all proposals using a Times New Roman 12-point normal font (no reduction permitted), single-spaced. The Offeror shall number all pages with volume, paragraph, and page numbers. If the Offeror uses graphs to convey information, the graphs must show enough detail to understand the information described. The Offeror shall present graphs and tables in no smaller than a 10 pt font.

2.1 Electronic Submission of Proposal

All volumes of the proposal shall be submitted electronically through the Solicitation Module of the Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil. No other submissions, such as mail, hand-carried, or other electronic system (e.g., DOD SAFE) are authorized by the solicitation unless specifically authorized by the Contracting Officer pursuant to the paragraphs regarding PIEE System outages below. For instructions on how to post an offer, please refer to the Posting Offer demo: https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf

It is the Offeror's responsibility to follow the registration instructions found on the PIEE website. It is advised that all potential prime Offerors and their subcontractors ensure the proper company points of contact are registered in the site based on their CAGE codes and have the proper roles assigned well in advance of the solicitation closing date. Subcontractors are only required to register in PIEE if they want to submit their proprietary proposal information separate from the prime offer. Documents submitted by the subcontractor directly to the Government must have the prime contractor's name, CAGE, and RFP number on the first page of the document.

It is also the Offeror's responsibility to confirm receipt of proposals and all electronic communications. Screen shots of the submission should also be taken to validate a submission was accepted in the PIEE system against this solicitation. The Government is not obligated to search for incorrectly submitted proposals in PIEE.

The submission date for all Volumes shall be no later than the date and time specified in Block 9 of the SF 33 of the RFP. It is requested that the Past

Performance Volume information be submitted prior to the submission date specified in Block 9 of the SF 33 of the RFP.seven days

If there is an unanticipated PIEE System outage within 24 hours of the proposal due date and the outage has interrupted normal Government processes so that proposals cannot be received by the exact time specified in the solicitation, the Contractor shall immediately notify the Contracting Officer.

This notification shall occur prior to the proposal submission deadline and shall be made in writing. The notification may be in conjunction with verbal notification, but verbal notification alone shall not be sufficient. The Offeror shall obtain written approval from the Contracting Officer to submit the proposal via an alternate method as determined by the Contracting Officer, or the Contracting Officer may advise the Offeror that the

Government will follow the procedures set forth in FAR 15.106 for amending the solicitation closing date

2.1.1 Electronic Proposal Media

The Offeror shall submit all volumes of its proposal electronically and ensure compatibility with the operating system and applications defined in

Section 2.1.2 below. The Offeror is responsible for ensuring electronic proposals are virus-free in accordance with Section 2.1.4.

2.1.2 Operating System and Applications

The Government uses a Microsoft Windows Operating System to access proposals. Offerors shall submit proposal information using the following applications: Microsoft Word, Microsoft Excel, and Microsoft PowerPoint. However, Offerors shall submit letters and other signed documents as a fully searchable Portable Document Format (.pdf) file. Use of other application software for submission of proposals is prohibited

2.1.3 Hyperlinks

The Offeror shall not use hyperlinks in proposal volumes.

https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf

2.1.4 Virus Free Electronic Submission

The Offeror is responsible for ensuring that its electronic proposal is virus-free. The Offeror shall certify, in its proposal cover letter, that all electronic proposal information delivered throughout the evaluation (e.g., original proposal submission, responses to evaluation notices, Final Proposal

Revisions) are virus-free. The Offeror shall specify the software, version, and virus definition used to check the data

2.1.5 Multimedia

In order to reduce file sizes, the Offeror shall not embed sound or video (e.g., MPEG) files within the proposal submission. The Offeror is encouraged to simplify the color palette used in creating figures; and minimize size of graphics files; and avoid scanned images.

2.1.6 File Naming Conventions

Valid extensions for files using their associated applications follow:

Type of Application/Files Valid Extensions

Portable Document Files .pdf

Microsoft Word documents .docx

Microsoft Excel documents .xlsx

Microsoft Power Point .pptx

Microsoft Project .mpp

The Offeror shall follow the basic structure of the file naming convention in Table G-1 "Proposal Structure" for electronic file submissions (e.g., proposal volumes, attachments, appendices), where "Volume Number" represents the sequential numbering of files. Offeror's shall keep file names short (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names often become corrupt or inaccessible.

The Offeror should provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. Please submit each volume, or annex as one file if possible. Offerors should not provide each section/paragraph as separate files.

Table L-1 Proposal Structure

Volume Number

Volume Title Page Limit

1 EXECUTIVE SUMMARY 5 Pages

2 TECHNICAL

2 Understanding of the Work 20 Pages

2 Staffing Plan 10 Pages

2 Management Plan 10 Pages

2 Technical Challenge Report 10 Pages

3 PAST PERFORMANCE

No page limit

4 CONTRACT ADMINISTRATION

No page limit

ANNEX A

Relevant Portions of Final Versions of Previous SOW/PWS for Past Performance

No page limit

ANNEX X Small Business Subcontracting Plan No page limit

3. PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one-for-one comparison between the information presented and these proposal instructions. Offerors shall structure proposal information such that the proposal paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.

Information submitted as an Annex to a particular proposal volume could include manuals, specifications, plans, procedures, and company policies, as well as other information requested in Section B Specific Instructions and do not count towards the suggested page count.

Subcontracting Plan information, (e.g., dollar values and/or hourly rates) shall not be included in any volume other than (Subcontracting Annex X Plan).

Table L-2 Section L List of Attachments

Attachment Number Attachment Name

L-1 Technical Challenge

L-2 Past Performance Information Form

L-3 Contractor Performance Assessment Questionnaire

L-4 RFP Questions Form

L-5 Table ES-2 Relevant Contract Summary For Past Performance

L-6 Table ES-1 Offeror Summary

L-7 Table T-1 Cross Reference Matrix

L-8 Table CA-1 Business Systems Status

4. PROPOSAL SUBMISSION AND PACKAGING

All Proposals shall be UNCLASSIFIED.

4.1 PROPOSAL SUBMISSION

Method of delivery, such as by hand, United States Postal Service or commercial carrier, are not authorized. Offerors will follow the directions for electronic submittal identified in paragraph 2.1.

The submission date for all volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 of the solicitation. However, it is requested one electronic copy of Volume 3 Past Performance, prior to the submission date/time specified on Standard Form seven calendar days 33 (Block 9). Offerors shall indicate any changes made to the information delivered early in the final submission provided on the date and time specified in Block 9 of Standard Form 33 of the solicitation.

5. CHANGES TO SOLICITATION

The Government will post all amendments to this solicitation at https://www.sam.gov/

Search the database for the solicitation number N6893626R5010

PART B SPECIFIC INSTRUCTIONS

1. VOLUME 1 - EXECUTIVE SUMMARY

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-5 Table ES-2 Relevant Contract Summary For Past Performance Attachment L-6 Table ES-1 Offeror Summary

The purpose of the Executive Summary is to provide the Government with an overview of the Offeror's entire proposal. The Executive Summary volume should be divided into the sections outlined below:

(1) Technical

The Offeror shall provide a succinct summary of what is proposed for each element, describing the approach or the design configuration and/or the proposed solution. In general, the description should be a short paragraph that provides only the factual description of what is proposed without adjectives or discussions of benefit. In a separate paragraph, identify significant features or approaches of its proposal that exceed requirements, enhance performance or operations, or reduce risk with benefit to the Government.

Specifically, identify where in the Technical Volume (e.g., paragraph and page number as a minimum) the details of these features or approaches are provided.

(2) Relevant Contract Summary Table

The Offeror shall complete the Table ES-2 "Relevant Contract Summary", Attachment L-5, for all contracts proposed as relevant for Past Performance for the principal entities.

(3) Contract Administration The Offeror shall provide a summary of any exceptions or deviations, and proposed Section H clauses addressed in Volume 4 "Contract Administration".

a. The Offeror shall complete Table ES-1 "Offeror Summary", Attachment L-6, and submit it within Volume 1. This table summarizes the Offeror and its entities' proposed type and level of work, indicating a commitment to that effort during contract performance.

Table ES-1 Offeror Summary (Attachment L-6)

Offeror:

Entity Name

Physica l Locati on of Entity

CAG

E Co des

Roles and Responsibilities with

Work Description

Works hare -

Principal Entity Yes or No?

Total Proposed cost /price (must add up to

100%) 100%

b. For the Past Performance evaluations, contract references that relate to a different CAGE code than the proposed entity will be considered if the CAGE code was created as a result of a corporate acquisition, reorganization, merger, or other administrative reason and refer to the same division in the same physical location for where the work is being performed or from where the work is being directed in accordance with the proposed roles and responsibilities. All current CAGE codes must appear in Table ES-1 "Offeror Summary" Attachment L-6, which indicates a commitment of work for those entities. To facilitate the Relevancy determination for Past Performance, the Offeror shall provide a written explanation if multiple CAGE codes for the same physical location are applicable to one entity. The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes at the same physical location for where the work is being performed or from where the work is being directed. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reasons and explain how the changes impact the relevance of any contract references provided.

Note: "Place of Performance" for this solicitation pertains to the physical location of the prime or other entities that will perform the work.

Table ES-2 Relevant Contract Summary For Past Performance (Attachment L-5)

Offeror:

Entity Name

Con trac t Refe renc e

Contract Number

Contra ct Type

Contra ct Title

*Description of Changes /Additions from Early

Information

Prime or Joint Venture Company

P1

P2

P3

JV team member A (where applicable)

T1

T2

T3

T4

JV team member N (where applicable)

T5

Subcontractor A S1

S2

S3

Subcontractor B S4

S5

*Contracts deleted should be identified in a narrative paragraph following Table ES-2.

c. c. Additionally, if applicable, the Offeror shall provide a description of the legal relationship between JV entities.

2. VOLUME 2 - TECHNICAL

The Offeror shall complete Table T-1 (Technical CRM) Attachment L-7, and submit it as the first page of Volume 2 (Technical). The Technical CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror's Technical CRM may be identical to the one provided or revised to add information. For example, the Offeror's Technical CRM may cross-reference its proposal volumes, paragraph numbers, and pages to specific solicitation requirements identified within the table, as well as other parts of the proposal that contain relevant information.

Attachment L-7 Table T-1 Cross Reference Matrix Attachment L-1 Technical Challenge

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Table T-1 Cross Reference Matrix (Attachment L-7)

Section L - Proposal

Instructions Volume or Paragraph Numbers

Section L - Proposal

Instructions Volume or

Paragraph Title

RFP

Sections (e.

g. Sections F, H, and

M)

SOO/SOW/PWS

S p e ci fi c a ti o n

C L I N

G ov er n m e nt W B S

Volume 2 Technical

2.1 Technical

Element 1

Example:

Para 3.1

Note: This column shall address all paragraphs in Sections xx and xy of the

SOW/PWS.

2.2 Technical

Element 2

2.3 Technical

Element 3

2.4 Technical

Element 4

In Volume 2, provide the information described below:

Throughout the Technical Volume the Offeror should identify any proposed capability, approach or feature that reduces risk inherent in the program.

Specifically, explain the benefits to the Government in technical terms and the degree of impact it will have to risk.

2.1 Understanding of the Work: The technical proposal shall provide details that will demonstrate the offeror's understanding of the work and capability to perform the tasking described in the statement of work (SOW). The narrative shall include detailed procedure and methodology which would be used in accomplishing each of the SOW tasks. The proposal shall identify risks that may impact successful performance and actions required to mitigate the risks.

2.2 Staffing Plan: The technical proposal shall provide details that will demonstrate the offeror's ability to perform the work through team member qualifications of security clearances, education, experience, and professional credentials. The proposal shall demonstrate recruitment, retention, and training plans and procedures that demonstrate how the offeror will meet the requirements of the SOW.

2.3 Management Plan: The technical proposal shall provide details that will demonstrate the offeror's ability to perform the work through adequacy of management and resources to support the technical requirements of the solicitation. The proposal shall identify management roles of the proposed workforce and the lines of responsibility and communication to demonstrate the offeror's ability to plan, manage, staff, and execute the work.

2.4 Technical Challenge: The technical proposal shall provide a report in response to the Technical Challenge questions Attachment L-1. The Technical Challenge Report must, at a minimum, address the Offeror's understanding of the problem, the methodology for developing the proposed solution, and a detailed description of the proposed solution, including its feasibility, potential risks, and expected outcomes. Failure to submit a report that addresses the Technical Challenge questions will result in the entire proposal being deemed unacceptable and ineligible for award.

Offerors may use AI-based tools or methods in preparing their Technical Challenge Report, provided that:

- All proposal content is accurate, verifiable, and fully substantiated by the Offeror;

- The Offeror ensures strict compliance with all applicable Government Controlled Unclassified Information (CUI) and cybersecurity regulations;

- The Offeror clearly identifies any portions of the report that were generated or substantially assisted by AI tools, including a brief description of the tool(s) used and the Offeror's process for verifying the accuracy and security of the information.

The Government will not evaluate the use or non-use of AI tools as a positive or negative discriminator. However, Offerors remain responsible for the quality, accuracy, and security of all submitted information.

3. VOLUME 3 - PAST PERFORMANCE

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-2 Past Performance Information Form Attachment L-3 Contractor Performance Assessment Questionnaire Attachment L-4 RFP Questions Form

For this volume, the Offeror shall identify all relevant contracts (where for the purpose of these instructions the term contract also refers to delivery order or task order), or those portions of a relevant contract, whose performance is within years of the proposal due date for the principal entities. five The relevant contracts provided for each principal entity shall be relative to its proposed role and responsibilities. Commercial contracts may be included. Offerors shall also identify relevant contracts within the past years of the proposal due date that had any show-cause notices, cure five notices, or termination for default. The Offeror shall complete for each, and all contracts proposed as relevant for Past Performance. Attachment L-2

In (Final Versions of Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other Supporting Documentation for Past Annex A Performance), the Offeror shall provide electronic copies of the complete final versions of the SOW/PWS or other supporting solicitation/contract documentation from each contract or delivery/task order reference identified. should only be provided in electronic format and should not Annex A be provided in paper copy. For contract references that contain delivery/task orders, additionally provide the work description for each specific delivery/task order. Where multiple task/delivery orders represent the same or substantially similar work effort and were performed under the same CPARS assessment, offerors may submit those orders as one reference, provided the offeror separately identifies the dollar value and period of performance for each order. For such a reference, the Government may consider the cumulative value of the identified orders

For contract references where the Offeror performed as a subcontractor, the Offeror shall also provide a complete electronic in assessing magnitude.

copy of the SOW/PWS or other documentation of the agreement between the prime and subcontractor that clearly defines the portions of the work effort of the Prime's SOW/PWS that the Offeror performed as a subcontractor.

Contract Performance Assessment Reporting System (CPARS) and Questionnaires will be the primary customer feedback data used to evaluate the Offeror's past performance. The System for Award Management web system (SAM.gov) will be the primary method used to retrieve the CPARS for this source selection. For all contracts identified that do not have a CPARS, the Offeror shall forward a copy of Contractor Attachment L-3 Performance Assessment Questionnaire to that contract's Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM), or commercial contractor equivalents. Please forward all questionnaires within weeks from this solicitation's release date two to allow adequate time for the recipient to respond. Note that the Offeror should not reference this solicitation's number when distributing the past performance questionnaires to customers. The Offeror should include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to the PCO/Contract Specialist, identified in the RFP posting in SAM.gov. The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient. The Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information as needed.

Offerors are reminded that the Government reserves the right to use information to evaluate past performance obtained from sources other than those identified by the Offeror. The Government may send additional questionnaires and/or obtain information from sources identified by the Government evaluation team.

3.1 Authorization Letter(s)

The Offeror should submit a signed "Release of Adverse Past Performance Authorization Letter(s)" with written consent from each principal entity (including JV team members), authorizing the release of adverse past performance information to the Prime. The signed letter

(s) should be included in a separate tab within (Past Performance). This authorization letter allows the Government to coordinate past Volume 3 performance issue(s) with the Prime Offeror. For any principal entity (including JV team members) that does not provide an authorization letter with such written consent, the Offeror shall provide point of contact information for each principal entity. This contact information shall include a name, address, phone number, and email address (including JV team members), with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if it does not submit the Release of Adverse Past Performance Authorization Letters with written consent, then the Government will address any past performance issues directly with the principal entity (including JV team members), and the Offeror will forfeit the opportunity to participate in any related discussions.

3.2 Relevant Contract Data

For each contract identified for past performance , the Offeror shall complete (Past Performance Information Form), according to the Attachment L-2 instructions within the attachment and submit it within this section and as a separate electronic file. All detailed information and comparative analysis of the past performance contract references to this solicitation's requirements shall be provided in (Past Performance), of the Offeror's Volume 3 proposal.

If a contract has Delivery Orders (D.O.s)/Task Orders (T.O.s), provide a separate contract reference and separate for each D.O/T.O. Attachment L-2 The Offeror may use one reference number/tab for multiple D.O.s/T.Os if they are the same work effort and performed under the same CPAR;

however, identify the dollar amount and period of performance for each. Do not provide a contract reference to the basic contract.

In general, recent performance will be considered a better indicator of future performance. If the Offeror is proposing as a JV, the Offeror should provide the relevant contracts for the JV as a whole, and for each team member of the JV.

3.3 Evaluation

The burden of providing thorough and complete past performance and systemic improvement information remains with the Offeror.

For each contract identified and submitted via , the Offeror shall provide contract data regarding relevancy, past performance Attachment L-2 information, and demonstrated systemic improvement, as described below. As this information is presented in the proposal, demonstrate the relevancy of the principal entities past performance with respect to this solicitation's requirements. For any contract references where the principal entities are aware of problems, the Offeror shall describe the issues. For each past performance problem identified, describe the status of the systemic improvement efforts.

a. Relevancy: Offerors are required to explain what aspects of the referenced contracts are deemed relevant, as defined by Section M, to this solicitation's requirements. To demonstrate relevancy, Offerors shall provide a comparative analysis to the scope, magnitude, and complexity or similarity of this solicitation's requirements. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs, and page numbers) of the referenced contract's SOW/PWS (Annex A) to clearly identify how past efforts performed are similar to this solicitation's requirements. In addition, the referenced sections only need to be identified and the full text does not need to be broken out separately from the complete SOW/PWS..

The reference contract(s) provided should be relative to each principal entity's proposed role/responsibility versus relative to the whole solicitation. For example, a subcontractor who is being proposed to perform only software has a past contract whose total work is software. Even though the software effort is only 10% of the hypothetical solicitation's effort, the previous contract relates to 100% of the subcontractor proposed effort for the hypothetical solicitation and therefore the reference contract would be considered Very Relevant vice Somewhat Relevant.

Offerors should be advised that the CAGE Code for each referenced contract is considered as part of the Relevancy determination, which determines if the contract reference will be included in the Past Performance evaluations.

Offerors are advised that contracts assessed as not relevant by the Government will not be considered in the Past Performance assessments.

b. Past Performance Information: For the relevant contracts provide a brief description of past performance in delivering quality services. Include in these descriptions any information that demonstrates the level of performance obtained, where available; provide quantifiable measures/trends to demonstrate past and current performance. Also describe past problems, including when they occurred, what the circumstances were surrounding the situation, and what the consequences were as a result of the problem.

For Small Business Utilization, the Large Business Offeror shall provide copies of the final or most recent SF 294s/Individual Subcontracting Reports (ISRs) for the three most relevant Government contracts provided in the Past Performance section of its proposal. The Small Business Offeror may provide this information in a format substantially the same as the ISR. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program, the Offeror shall provide copies of Defense Contracting Management Agency's (DCMA) most recent "Review of Contractor's Comprehensive Subcontracting Program" (DCMA Form 640), and three final or most recent SF 295s/Summary Subcontracting Reports (SSRs), and explain how the results shown in these documents demonstrate the feasibility of the Offeror's proposed SB Utilization Strategy. If applicable, note whether the contract met or exceeded Small Business (SB), Veteran-Owned Small Business (VOSB), Service- Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business (HUBZone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB) small business utilization and subcontracting goals. All Offerors providing this information must explain how this information translates to reasonableness of their proposed SB Utilization Strategy goals provided in the technical Volume.

c. Demonstrated Systemic Improvement: Identify systemic improvement actions taken to resolve any past problems identified.

Provide the records of such results and indicate where they are documented, preferably in Government record systems. Describe the techniques, elements, and tools used to correct problems on the reference contract and, if applicable, how these techniques, elements, and tools may be used for the contract to be awarded as the result of this solicitation. Provide quantifiable evidence or metrics that substantiate or demonstrate claims of improvement and to demonstrate that the past problem will not occur on the contract to be awarded as the result of this solicitation. It is incumbent upon the Offeror to explain the relevance of the data provided and substantiate that improvements from past performance problems are being made. The Government does not assume the duty to search for data to cure the problems it finds in the information provided by the Offeror. Consideration for discounting problems may be given when those problems are addressed through demonstrated systemic improvement.

Demonstrated systemic improvement may be indicated by information as it relates to preventing recurrence of past problems, including:

identification of the root cause of a problem, a corrective action plan that systemically addresses the past problem, how and when the plan was implemented, documented timeframe to demonstrate when corrective action was implemented and became successful; and performance data, preferably through Government records, to show performance improvements. With regard to performance improvement data, explain the likelihood to which the problem will not reoccur on during the performance of this prospective contract based on the amount of time that good performance was sustained in consideration of the nature of the past problem and effort.

4. VOLUME 4 - CONTRACT ADMINISTRATION

The Offeror shall provide the following contract administration information.

a. Offeror Representatives and Information: The Offeror shall provide a summary sheet comprised of the information listed below for the entities identified in Table ES-1 "Offeror Summary".

(1) PRIME CONTRACTOR

i. Business Name;

ii. Address;

iii. Principal point of contact for this solicitation (Name, title, phone number, email);

iv. Secondary point of contact for this solicitation (Name, title, phone number, email);

v. Individuals authorized to negotiate with the Government and contractually bind the Offeror (Name, title, phone number, email);

vi. Establishment Taxpayer Identification Number (TIN);

vii. TIN of Parent Corporation (if applicable);

viii. CAGE code;

ix. Business size for this effort (large or small); and

x. Percentage of work and role and responsibility performing.

(2) ALL OTHER ENTITIES

i. Business Name; Address; DCMA point of contact and telephone number, if applicable;

ii. DCAA point of contact and telephone number, if applicable;

iii. CAGE code; and

iv. Percentage of work and role and responsibility performing.

b. Government Agency Information: Provide the mailing address, telephone, fax numbers, email address, and facility codes for the Offeror's local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. In addition, provide the name, telephone number, fax number, and email address for the Administrative Contracting Officer (ACO) at DCMA.

c. Business System Compliances: The Offeror shall indicate the most recent date that the Offeror's cognizant DCMA/DCAA determined the adequacy of the Offeror's systems (including but not limited to Accounting, Property, and Purchasing). If the Offeror's systems' status is not adequate, list the date of the last adequacy determination and the current status of any systems reviews or ongoing audits;

Business Systems Status Table: The Offeror shall complete Table CA-1 (Business Systems Status) showing the current status and or determinations regarding its business systems. If any item is not applicable to the Offeror or for contract performance, so state and justify. If any item has been determined to be unapproved/inadequate outline the potential impact on contract execution, mitigation plan, and correction plan.

Submit relevant DCAA/DCMA reports, audits, and determinations in Annex X (DCAA/DCMA Reports, Audits, and Determinations).

Table CA-1 Business Systems Status

Business System (D)FAR Reference

Status

Comments

Accounting System* 16.301-3

Estimating System 215.407-5

CAS Disclosure Statements** 30.301

Purchasing System 44.301

Earned Value Management System 242.302(S-71)

Property Management System 45.105

*Because the awarded contract will contain cost reimbursement CLINS, in accordance with FAR 16.301-3 an adequate Accounting System is a condition for award regardless of any best value determination.

**An adequate CAS Disclosure Statement is a condition for award for Offerors subject to full CAS requirements regardless of any best value determination.

This information is to facilitate the PCO's responsibility determination and any need to discuss information related to this does not constitute discussions.

d. Small Business (SB) Subcontracting Plan - Large Business Offerors shall provide their Small Business Subcontracting Plan conforming to the requirements of FAR 52.219-9 Small Business Subcontracting Plan and FAR 19.302 and accompanying regulations as

The SB Subcontracting Plan of the successful Offeror(s) will be reviewed as well as part of Annex X (Small Business Subcontracting Plan).

approved by the PCO prior to contract award as part of the responsibility determination. See FAR 19.206-3 regarding failure of the apparent successful Offeror to negotiate and submit a SB Subcontracting Plan or submit a Comprehensive or Commercial SB Subcontracting Plan acceptable to the Contracting Officer. The successful Offeror's approved Subcontracting Plan will be incorporated into the resultant contract and contractor performance against the plan will be monitored by the Government during contract execution.

e. Terms and Conditions:

All exceptions and deviations that the Offeror takes from the provisions of the solicitation and its applicable documents shall be included in this section.

An exception occurs if/when an Offeror states it will not comply with a solicitation requirement, usually involving contract terms and conditions.

A deviation is where an Offeror states it will not comply with a solicitation requirement but proposes an alternative to meet the intent of the requirement, usually involving a PBSOW requirement. An exception or deviation is considered a deficiency.

The Offeror shall provide one of the following two statements in this section. If the Offeror takes any exceptions or deviations to the provisions of the solicitation and its applicable documents, the Offeror shall provide the following statement: "All exceptions and deviations taken from the solicitation terms, conditions or requirements, including any applicable documents, are included in this section". If the Offeror does not take any such exceptions or deviations, then the Offeror shall provide the following statement: "No exceptions or deviations are taken to the terms and conditions or any requirement of the solicitation."

If proposing an exception or deviation, the Offeror shall provide a detailed description for each in this section. Indicate the difficulty with the applicable requirement and the proposed solution. Specifically identify the portion of the solicitation and the proposal, which are affected. Also, identify any proposed H-clauses containing unique contract terms and conditions not covered by clauses in this solicitation and associated with an exception or deviation identified in this section. The Government will review the information and may elect to clarify the requirement via an amendment or clarify the requirement by holding discussions.

f. Model Contract Documents: The model contract documents should be provided as a separate electronic file and as a separate section in The Offeror shall provide the following documents within this section:this volume.

(1) Original signed SF33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed SF30 cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation.

The SF-33 Block 12 "fill-in" (proposal validity date) shall be completed IAW Section A (Solicitation/Contract Form);

(2) Signed Representations, Certifications, and Acknowledgements or System for Award Management (SAM) reference;

(3) A complete copy of all FAR, DFARS, NAVAIR, and special clauses and provisions requiring contractor fill-ins and

(4) Section H (including any other proposed clauses). All Offeror proposed H Clauses, or other contract additions, in full text, if applicable.

If an Offeror proposes to perform work above or not included in this solicitation (e.g., including, but not limited to, an aspect of a proposal that the Offeror believes the Government should evaluate as a strength), the Offeror must include contractually binding additions for the contract award document. These additions may be H clauses, additions to the PBSOW, additions to the CDRLs (if data is to be delivered), or other additions. For the H clause, it must state as a minimum: a) the Offeror's performance responsibilities; b) the performance periods, including delivery dates, if applicable; and, c) the financial responsibilities and liabilities of the Offeror. The Offeror's proposal should include information regarding any Government performance and financial responsibilities incurred as a result of any proposed H clause or other proposed additions for the contract award document.

Section M - Evaluation Factors for Award

Miscellaneous text in this section has been modified to:

I. GENERAL INFORMATION

The Government expects to select multiple Offerors for the ISR&T MAC requirements whose proposals meet the acceptability standards specified in Section M, Part I, B, if otherwise eligible for award.

Per FAR 15.304(c)(1)(ii)(A), cost or price will not be evaluated at the basic award, as the Government intends to make award to each and all qualifying Offerors. Qualifying offers are proposals that receive a Technical rating of Acceptable, and Performance Confidence Assessment rating of Satisfactory Confidence. If a proposal receives a Performance Confidence Assessment rating of Neutral Confidence, Neutral Confidence will be considered to be the equivalent of Satisfactory Confidence as it pertains to the standard of a qualifying offer for Past Performance.

Contractors must demonstrate the technical capability to fully accomplish the requirements in the SOW either as the Prime or with a Joint Venture (JV) Team or in a teaming arrangement with a subcontractor(s). The proposal must demonstrate to the Government's satisfaction that the Offeror will provide a program that will ensure the successful accomplishment of the solicitation requirements and overall program objectives. Proposal information provided for one element may be used to assess other element if the Government deems it appropriate.

A. EVALUATION PROCESS

The Government intends to evaluate each proposal and award a contract without discussions to the responsible Offeror whose offer, conforming to the solicitation, provides the greatest overall benefit to the Government, all factors considered. Therefore, Offerors are cautioned that their initial offer should contain the Offeror's best terms from a technical and past performance standpoint. However, the Government reserves the right to conduct discussions and request proposal revisions if it is determined to be in the best interest of the Government. When a competitive range is established, the Government 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. The Government may use information other than that provided by the Offeror in its evaluation (past performance information, results of questionnaires, site surveys, etc.).

Non-compliance with the terms, conditions, or requirements set forth in the solicitation will be considered a deficiency. The Government may consider any exception or deviation to any term or condition of the RFP that is not expressly authorized by the RFP to be a deficiency, as defined in FAR 15.001. Additionally, any approach that relies on Government resources or operations (e.g., Government Furnished Property, Government Furnished Equipment, Government personnel/actions, Government Concept of Operation changes, etc.) in order to comply with a requirement, unless otherwise allowed, may be considered a deficiency. A proposal assessed with a deficiency will make the offer ineligible for award.

B. EVALUATION FACTORS FOR AWARD

Proposals shall be evaluated using the factors, which are listed below, where Technical is the most important factor.

A. Technical

B. Past Performance

The proposal must demonstrate to the Government's satisfaction that the Offeror will provide a program that will ensure the successful accomplishment of the solicitation requirements and overall program objectives. Proposal information provided for one factor may be used to assess other factors if the Government deems it appropriate.

II. SPECIFIC INFORMATION

A. TECHNICAL

The Government will evaluate the proposal to determine the Offeror's understanding of, approach to, and ability to meet the solicitation requirements. The Government will assess the Offeror's Technical Proposal with respect to its compliance with the solicitation requirements and the risk associated with the Offeror's approach. The evaluation will also include an assessment of the following elements, which will not be rated separately.

1. Understanding the Work

2. Staffing Plan

3. Management Plan

4. Technical Challenge Report

1. Understanding of the Work: The Government will evaluate each Offeror's proposed approach to the statement of work (SOW) in Section C of the solicitation to assess its demonstrated ability to meet requirements, adequacy of its approach, and understanding of the requirements, to determine technical acceptability.

2. Staffing Plan: The Government will evaluate the Offeror's overall Staffing Plan and its supporting information to determine if the Offeror can meet the minimum team member qualification requirements, security clearances, education, experience, and professional credentials. The Government will evaluate how the proposed staffing plan demonstrates the Offeror's plan for employee retention, recruitment, recruiting strategies, interviewing, and hiring techniques, and training will provide workforce continuity and benefit the overall contracting approach over the contract's entire period of performance.

3. Management Plan: The Government will evaluate the Offeror's overall management approach based on the information required by Section L of the solicitation. The management approach will be evaluated to assess the Offeror's ability to plan, manage, staff, and execute the contract and whether any proposed processes and procedures ensure successful accomplishment of the tasks described in the SOW.

4. Technical Challenge Report: The Government will evaluate the Offeror's report in response to the technical challenge to determine the Offeror's understanding of approach to…