Mod 05_N61340-25-R-0006.pdf
PDF 347 KB Posted
- Solicitation number
- N6134025R0006
About this file
This document is an Amendment (Modification 0005) to a federal solicitation for a technology refresh and system configuration upgrade to the Royal Saudi Naval Forces (RSNF) MH-60R Tactical Operational Flight Trainer (TOFT). The amendment updates Section J to include a new Attachment (L-1) containing Q&A dated 19 May 2025 and extends the Solicitation Questions/Comments due date from 16 May 2025 to 06 June 2025.
The solicitation is specifically for Training Systems Contract IV (TSC IV) awardees and involves upgrading the MH-60R flight trainer's hardware and software systems. Key submission requirements include a technical approach detailing system configuration upgrade and tech refresh, functional block diagrams, and a narrative explaining software reuse strategy. Offerors must submit three proposal volumes: Technical (40-page limit), Past Performance, and Price, with specific instructions for electronic file submission, naming conventions, and content requirements. Large business offerors must commit to a minimum 20% small business participation goal and provide detailed documentation of small business involvement.
View the file
Other files
Show all 27
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
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)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA
FAR (48 CFR) 53.243
The purpose of Amendment 05 is to accomplish the follow ing:
1. Update Section J to include Attachment (L-1) QA_ Amendment 05_N6134025R0006 dated 19 May 2025.
2. Update Section L.6 Solicitation Questions/Comments due date from 16 May 2025 to 06 June 2025.
1. CONTRACT ID CODE PAGE OF PAGES
J 1 13
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 22-May-2025
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N6134025R0006
X 9B. DATED (SEE ITEM 11)
10-Feb-2025
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.
Offer 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 telegram 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 telegram or letter, provided each telegram or letter 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 NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, 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.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
22-May-2025
CODE
NAWCTSD PROCUREMENT GROUP
GT23000
12211 SCIENCE DR
ORLANDO FL 32826-3224
N61340 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
N6134025R0006
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS
The following have been modified:
CONTRACT ATTACHMENTS
DOCUMENT
TYPE
DESCRIPTION
ATTACHMENTS
Attachment 01 Statement of Work (SOW) #240042 for MH-60R Royal Saudi Naval Forces (RSNF)
Tactical Operational Flight Trainer (TOFT) Upgrade Dated 12 May 2025.
Attachment 02 Performance Specification #240041, TOFT Requirements Traceability Matrix for the
Royal Saudi Naval Forces (RSNF) dated 04 April 2025.
Attachment 03 DD Form 254 Department of Defense Contract Security Classification (Plan) Attachment 04 Data Item Transmittal, Acceptance Rejection Form (4330/60) Attachment 05 NAWCTSD GFI List dated 04 April 2025.
Attachment 06 Addendum to Commercial License
EXHIBITS
Exhibit A CDRL A00A- Engineering Change Proposal (ECP) CDRL A00B-Request for Variance (RFV) CDRL A00Q- Risk Management Framework (RMF) Package Deliverables_Rev 02
CDRL A001- Test Inspection Report (TIR) CDRL A002- Architecture Design Document (ADD) CDRL A003-Test Procedures (TP) CDRL A004- Software Product Design (SPD) CDRL A005- Software Product Package (SPP) CDRL A006- Requirements Traceability Verification Matrix (RTVM) CDRL A007- Visual Database Source Data CDRL A008- Visual Database Design Document CDRL A009- Software Version Description (SVD)
Exhibit B CDRL B001- Conference Agenda CDRL B002- Report, Record of Meeting/Minutes CDRL B003- Briefing Material CDRL B004- Integrated Program Management Data and Analysis Report (IPMDAR) CDRL B005- Technical and Management Work Plan (CPI Assessment)
Exhibit C CDRL C001- Training System Sparing Product Data (TSSPD) CDRL C002- Bill of Materials (BOM) for Logistics and Supply Chain Risk
Management
Exhibit D CDRL D001- Training Device Inventory Checklist/Report (TD ICL/R)
Exhibit E CDRL E001- Operation and Maintenance (O&M) Manuals CDRL E002- Planned Maintenance System (PMS) CDRL E003- Training System Support Documents (TSSD) CDRL E004- Commercial Off-the-Shelf (COTS) Manual and Supplemental Data CDRL E005- Product Engineering Design Data and Associated Lists (PEDDAL)
Exhibit F CDRL F001- Training Program Structure Document (Instructor Training Course)
CDRL F002- Training Program Structure Document (Maintenance Training Course)
RFP Section L Attachments
Atch (L-1) Q&A _ Amendment 05_ N6134025R0006_19 May 2025 Atch (L-2) Contractor Performance Assessment Questionnaire (CPAQ) Atch (L-3) Relevancy Information_Rev 01_26Feb2025 Atch (L-4) Small Business Participation Commitment Document (SBPCD) Atch (L-5) Offeror Summary Table
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
INSTRUCTIONS TO OFFERORS
PART A: GENERAL INSTRUCTIONS
1.0 GENERAL
Section L contains instructions on how to prepare and submit proposals in response to this solicitation.
Nonconformance with these instructions may result in an unfavorable proposal evaluation and elimination from consideration.
The government will base its evaluation on the information presented in the offeror's proposal. The offeror has the burden to submit a proposal that clearly and convincingly demonstrates that the offeror has an accurate understanding of the requirements, the associated risks, and otherwise sufficiently addresses all aspects of the solicitation. The offeror must clearly and convincingly reveal that the offeror’s proposed approach is viable for the evaluated requirements.
It is the offeror’s responsibility to submit a proposal that enables government evaluators to effectively evaluate and substantiate the validity of any assertions set forth in the offeror’s proposal. Assume the government has no prior knowledge of an offeror’s facilities and experience. Accordingly, do not simply rephrase or restate the government's requirements. Statements that the offeror will provide a particular feature, objective, or outcome without explaining how the offeror proposes to meet that feature, objective, or outcome are generally inadequate and may adversely impact the government’s evaluation assessment of the offeror. Also inadequate are the following types of statements:
a. unsupported statements that the offeror allegedly understands the requirements and risks;
b. unsupported statements that the offeror allegedly can or will comply with requirements;
c. unsupported statements that merely paraphrase the requirements;
d. undefined or explained statements such as “best commercial practices will be used”;
e. undefined or explained statements such as “standard procedures will be used”; and
f. undefined or explained statements such as “well-known techniques will be employed.”
Alternate proposals are not acceptable. In addition, taking exception or deviating from any term or condition of the RFP may make an offer unacceptable, and the proposal unawardable, unless the RFP expressly authorizes such an exception or deviation with regard to that specific term or condition.
There is no need to repeat information in the same volume or in more than one volume. If an overlap exists, the detailed information should be included in the most logical place and summarized and referenced in other areas. With the exception of the Price Volume, no cost or pricing information should appear in any volume.
2.0 PROPOSAL FORMAT
Written proposals must be formatted using a Times New Roman 12-point normal font, no reduction permitted, single-spaced, 1-inch margins all around, and formatted for standard 8.5 x 11-inch paper. All pages should be numbered with section and page numbers. If the offeror uses graphs to convey information, the graphs must show enough detail to easily discern the information described. Graphs and tables shall be presented in no smaller than a 10-point font.
Graphic resolution, including such data as tables or charts, should be consistent with the purpose of the data presented.
Text utilized in charts, figures and graphics should also be no smaller than a 10 point font and may use a font type selected by the offeror.
3.0 PROPOSAL CONTENT AND VOLUMES
The Offeror must present its proposal information in a manner that facilitates a one for one comparison between the information presented and Section L proposal instructions. Proposal information must be structured such that its paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.
Each volume and annex, if applicable of the proposal shall be submitted as an original electronic copy as specified in Table L-1 (Proposal Structure). All volumes of the proposal shall be received electronically via the Solicitation Module in PIEE prior to the closing date/time stated in this solicitation. Page limitations for each volume, if any, are also specified in Table L-1 (Proposal Structure). The title and table of contents pages as well as Section L Attachments are not included in the page limitations. Additionally, functional block diagrams provided in response to Section L requirements will not count toward the page limit. Any pages submitted exceeding the page limit shall be disregarded and NOT evaluated. Price information, (e.g., dollar values) shall not be included in any volume other than Volume 3 (Price).
Table L-1 Proposal Structure
Volume Number Volume Title Page Limit Electronic Copies
Required 1 TECHNICAL 40 pages 1 Original 2 PAST PERFORMANCE As Needed 1 Original 3 PRICE As Needed 1 Original
Each electronic volume must contain the following information:
a. Cover and title page
b. Title of proposal and proposal number as applicable
c. Offeror’s name, address and POC
d. Solicitation number
e. Proposal volume
f. Table of Contents (The table of contents must provide sufficient detail to easily locate important elements).
Table L-2 below lists the attachments provided to the offeror within Section L.
Table L-2 Section L Attachments
Section L Attachment
Number
Electronic File Title Attachment Name
L-1 Atch (L-1) Q&A Form Q&A Form L-2 Atch (L-2) Contractor Performance
Assessment Questionnaire (CPAQ) Contractor Performance Assessment Questionnaire (Vol 2)
L-3 Atch (L-3) Relevancy Information Relevancy Information (Vol 2) L-4 Atch (L-4) Small Business Participation
Commitment Document (SBPCD) Small Business Participation Commitment Document (Vol 1)
L-5 Atch (L-5) Offeror Summary Table Offeror Summary Table
4.0 ELECTRONIC PROPOSAL SUBMISSION
4.1 All proposals shall be UNCLASSIFIED. The submission date for each Volume of the proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP. Offerors are hereby notified that the Government will not reimburse for any costs incurred for solicitation preparation. Proposals shall be valid for 180 days from the proposal due date.
4.2 All volumes of the proposal shall be received electronically via the
SOLICITATION MODULE in PIEE prior to the closing date/time in this solicitation. No other submissions are authorized by the solicitation. 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 Code, and the solicitation number on the first page of the document.
The Solicitation Module will only allow a total of 1.9 Gigabytes (GB) inclusive of all files to be uploaded to the module. If an offeror anticipates their submission to be larger than 1.9 GB, the offeror must coordinate at least three (3) business days in advance with the Solicitation Contracting Officer and Contract Specialist (Jeannice Machado at jeannice.m.machado.civ@us.navy.mil and PCO Jason Harvey, jason.g.harvey.civ@us.navy.mil) Proposals that are rejected by the Solicitation Module will not be considered by the Government. Therefore, offerors should consider submitting proposals in advance of the deadline.
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 for this solicitation. The Government is not obligated to search for incorrectly submitted proposals in PIEE.
4.3 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 which will be provided by the Contracting Officer or the Contracting Officer may advise the offeror that the Government will follow the procedures set forth in FAR 15.208(d) for amending the solicitation closing date.
5.0 SOLICITATION CHANGES
For notice of any changes and additional information provided by the Government for the solicitation, please go to https://sam.gov. Search the database for the solicitation number N6134025R0006.
6.0 SOLICITATION QUESTIONS/ COMMENTS
Questions regarding this solicitation shall be submitted in writing with the use of Attachment L-1, Solicitation Questions and Answer Form. Each question or comment should reference the applicable document, page number, and paragraph number. Do not include any proprietary information in your question, because the government will provide the question and answer to all potential offerors. All questions must be submitted for the solicitation no later than 4:00pm on 06 June 2025, to Jeannice Machado, Contract Specialist, at Jeannice.m.machado.civ@us.navy.mil and PCO Jason Harvey, jason.g.harvey.civ@us.navy.mil.
6.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 6.1.4 below. The Offeror shall keep the portions of the proposal that contain pricing information separate from the portions of the proposal that do not contain pricing information.
6.1.2 Operating System and Applications
Offerors shall submit proposal information that is compatible with the following applications: Microsoft Office 2016 and Adobe Acrobat. Offerors shall submit letters and other signed documents as a fully searchable Portable Document Format (.pdf) files.
6.1.3 Hyperlinks
The Offeror shall not use hyperlinks (internal or external) in proposal volumes.
6.1.4 Virus Free Electronic Submission
The Offeror is responsible for ensuring that its electronic proposal is virus free.
6.1.5 Multimedia
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.
6.1.6 File Naming Conventions
Valid extensions for files using their associated applications follow:
Table L-3 File Naming Convention
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 L-3 Section 6.1.6 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices. 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.
mailto:Jeannice.m.machado.civ@us.navy.mil mailto:jason.g.harvey.civ@us.navy.mil
The offeror will provide electronic files fully compatible with Microsoft Office 2016 and information not supported by MS Office products, with the latest Adobe Acrobat reader.
All electronic files submitted shall follow the following naming convention:
For Volume 1 Technical proposal electronic files: Vol_1_XXX For Volume 2 Past Performance proposal electronic files: Vol_2_XXX For Volume 3 Cost/Price proposal electronic files: Vol_3_XXX The XXX represents the appropriate title the offeror can identify. For example:
Vol_1_Technical Supporting Docs Vol_2_CPARS N6134021C0032
Naming files in the format above will allow the Government to store electronic files for each volume accordingly
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.
7.0 SOLICITATION ATTACHMENTS AND EXHIBITS
Solicitation Attachments and Exhibits included in Section J will be made available upon request. Offerors are instructed to send a request for solicitation attachments and exhibits along with the offeror’s TSC IV award number via email to the Contract Specialist Jeannice.m.machado.civ@us.navy.mil and cc PCO Jason Harvey,jason.g.harvey.civ@us.navy.mil. Once the request is received, the documentation will be provided to the offeror via DoD Safe.
Upon award of a contract resulting from the subject solicitation, the unsuccessful Offerors shall destroy all solicitation attachments and exhibits within 10 calendar days of receiving notification of unsuccessful offer from the Government. In the event the solicitation is cancelled, all offerors shall also destroy all data produced from the usage of solicitation attachments and exhibits in development of the Offeror’s proposal.
PART B. SPECIFIC INSTRUCTIONS
VOLUME 1: TECHNICAL
L.1.1 Technical Factors
L.1.1.1 RSNF TOFT System Configuration (SC) 24 upgrade
a. The Offeror shall provide a written technical approach that clearly explains the hardware and software technical approach for accomplishing the SC24 upgrade.
b. The Offeror shall provide functional block diagrams, depicting internal and external sub-systems interfaces affected by the SC 24 upgrade.
L.1.1.2 RSNF TOFT Tech Refresh
a. The Offeror shall provide a written technical refresh approach to identify hardware architectural changes to the system to include the systems and sub-system hardware design that meets or exceeds the RSNF Tech Refresh performance requirements of the trainer IAW Specification 240041.
b. The Offeror shall provide functional block diagrams, depicting internal and external sub-systems interfaces affected by the Tech Refresh.
mailto:Jeannice.m.machado.civ@us.navy.mil mailto:jason.g.harvey.civ@us.navy.mil
c. The Offeror shall describe the software re-use approach nd provide a detailed description of the steps taken to reduce software development as well as identify whether the reuse items will be “as-is” or “modified” and the extent of modification.
The Offeror shall describe the rights in technical data (TD), computer software (CS) and computer software documentation (CSD). The rights described shall be consistent with the assertions in DFARS 252.227-7017 the “7017 List”. The Offeror (including their Subcontractors at all tiers) shall include copies of any proposed specifically negotiated license(s) associated with deliverable noncommercial items on the “7017 List”. The Offeror shall explain the extent to which the rights in TD, CS, and CSD offered to the Government promote maintainability and upgrades throughout its lifecycle and open and competitive procurement of enhancements the transfer of the product’s object code and source code to other contractors for use on other systems or platforms
• The Offeror (including their Subcontractors at all tiers) shall identify and list all noncommercial TD, CS, and CSD that is proposed to be delivered with less than unlimited rights pursuant to the procedures and requirements of the DFARS 252.227-7017 Identification and Assertion of Use, Release, or Disclosure Restrictions the “7017 List” provision incorporated in section K of this solicitation.
L.1.2 Management Approach
The Offeror shall provide a high-level timeline that identifies the estimated time of completion from contract award to RFT, and describe the execution of strategy to reduce the time TOFT is unavailable for use during technology refresh and system upgrade.
L.1.3 Small Business
L.1.3.1. Small Business Participation Commitment Document (Large Businesses Only)
Large Business Offerors (Large Businesses include non-profit entities) shall complete the Small Business Participation Commitment Document (SBPCD) provided as Attachment L-4 and submit it as a part of VOLUME 1.0 Technical (ref FAR 52.219-8 and DFARS 215.304).
The SBPCD shall:
a. Identify a minimum small business participation goal of 20% of the total evaluated price. The goal shall be calculated to the second decimal place; and
b. Identify goals for each small business socioeconomic category identified in Section 2 of the SBPCD. Each category shall be addressed in terms of dollar figures and percentages (i.e. do not enter “N/A” or “-” to indicate a zero goal; instead enter $0 and 0%, as applicable); and
c. In Section 3 of the SBPCD, list the planned Small Business participants who are proposed as parties to the execution of the order and whose technical and/or pricing information have been used in the preparation of the Prime’s proposal. There shall be no less than one small business participant listed. The Government does not require nor desire more than 10 small business participants to be listed. The Prime is not required to pre-determine the specific small business source(s) planned for provision of incidental items such as commercial piece parts, commercial supplies and/or incidental services. IAW FAR 19.703(a)(2) and FAR 52.204-7, each Small Business participant identified under item 3 of the SBPCD must have an active registration in SAM.gov or provide a written certification of its small business status applicable to the size standard of the NAICS assigned by the Prime.
Note: See additional instructions provided in the “Instructions” column of the SBPCD Template at Attachment L-4.
The SBPCD shall be incorporated into the order as an attachment in Section J.
The offeror shall ensure its proposal information complies with Part A, Section 4.0 above and is sufficient for the Government to evaluate in accordance with Section M.
If the Offeror is subject to a Commercial Subcontracting Plan (see FAR 19.7) or is a participant in the DoD Comprehensive Subcontracting Test Program specified in DFARS 219.702, rather than submitting Small Business Participation Commitment Document on Attachment L-4, SBPCD, the Offeror shall describe how Small Business participation on this order will contribute to its overall Commercial or Comprehensive Subcontracting goals (for Large Business Offerors only).
L.1.3.2 Written Representations of Small Business Participant Size (Large Businesses Only)
Large Business Prime Offerors shall provide written representation (signed letter/memorandum) from each Small Business participant listed in Section 3 of the SBPCD, confirming their size status as a “small business”. The written representation shall be provided as part of the Small Business Element, and include the following:
a) Statement showing the NAICS code determined by the Prime Offeror for the services or supplies being acquired from the Small Business participant and confirming the subcontractor does not exceed the size standard for the NAICS code;
b) Statement confirming that this certification is current, accurate, and complete;
c) Full company name, mailing address, and CAGE code of Small Business participant; and
d) Dated and signed by a senior company representative of the Small Business participant
In lieu of a signed letter/memorandum described above, the Large Business Prime Offeror may provide the Small Business participant(s)’ current System for Award Management (SAM) profile. This shall include FAR 52.219-1 (Small Business Program Representations) expanded to display the full text of the provision, showing the NAICS code assigned by the Prime Offeror for the services/supplies being acquired from the Small Business participant.
L.1.3.3 Small Business Participation of Small Business Prime Offerors
Each Small Business Prime Offeror shall submit a Small Business Participation Volume, which shall be completely stand-alone, and not require any reference to another source, volume, or proposal. The Small Business Participation Volume shall state only the following:
In accordance with 13 CFR § 125.3(g)(3) and FAR 15.305(a)(5), Small Business Offerors shall receive the maximum evaluation rating of ACCEPTABLE, which is defined as “The SB Participation Goal meets or exceeds 20% of the total proposed price; and small business participants are listed in the SBPCD, for the Small Business Participation evaluation factor, without having to submit any further information in connection with the Small Business Participation evaluation factor.
2.0 VOLUME II: PAST PERFORMANCE
The offeror’s proposal shall include a Past Performance volume consisting of (1) a completed Attachment L-5, Offeror Summary Table, (2) a completed Attachment L-3 Relevancy Information, (3) the most recent, contract copy of each past performance reference identified in Attachment L-3 (including any supporting documentation described in Section L, Part B, Paragraph 2.3 below), (4) any Show Cause Notices, Cure Notices, and Terminations for Default (and the related contracts), (5) any CPARs, and, if necessary, (6) a narrative.
The Offeror shall identify a maximum of three (3) past performance references performed within five years of date of issuance of the final solicitation.
The offeror shall only submit past performance references for the prime offeror (i.e., entity identified in Block 15A of Standard Form 33) and any entity proposed to perform at least 15% of the proposed price (such as a Join Venture Team member or a principal subcontractor). The Government will not evaluate past performance of parent, subsidiaries or other affiliates unless they are proposed to perform at least 15% of the proposed price. The burden of providing thorough and complete past performance and systemic improvement information remains with the offeror.
The offeror shall NOT submit past performance contract references that include classified supporting documentation. All proposals must be UNCLASSIFIED as outlined in Section L, Part A, Paragraph 4.1. The government will NOT obtain or evaluate classified material.
If the offeror submits a single award Indefinite Delivery Indefinite Quantity (IDIQ) contract as a reference, then it may identify up to a maximum of three (3) orders under the IDIQ. Those orders in the aggregate will count as one reference. However, orders under a Multiple Award Contract (MAC) will each count as a single reference.
Similarly, orders awarded under Basic Ordering Agreements (BOAs), or Blanket Purchase Agreements (BPAs) (or commercial equivalents) will each count as a single reference.
If the offeror proposes past performance of a JV Team member(s) or subcontractor(s), then the offeror should submit a signed “Release of Negative Past Performance Authorization Letter(s)”. Authorization Letter format should be provided by the offeror with written consent from the JV Team Member or any proposed subcontractor that authorizes the release of adverse past performance information to the prime offeror or (JV) POC. If the JV Team Member or subcontractor does not provide an authorization letter, then the offeror shall provide a POC for the JV Team Member or the subcontractor. The POC information shall include a name, address, phone number, and email address. The Government will contact that POC concerning that JV Team Member’s or subcontractor’s past performance.
2.1 Offeror Summary Table.
The offeror shall complete Attachment L-5. The offeror shall include all entities who will be involved with the performance of the contract.
Within the “Brief Work Description and/or Program Responsibility” block, the offeror shall include the applicable paragraph numbers of the solicitation SOW that correspond to the work that will be performed by each entity.
Attachment L-5 shall include the dollar value proposed for each entity. Adding up the dollar values identified in this table shall equal the total proposed price. The percentages in Attachment L-5 shall add up to 100%.
2.2 Past Performance Relevancy Information
The offeror shall complete Attachment L-3 Relevancy Information for all references proposed for Past Performance.
All past performance references must include the CAGE code in the cited past performance reference, and the cited past performance reference cannot include a higher tier contract. For past performance references where the contract is not directly with a Government agency and no CAGE code is identified, the past performance reference must include the company name and address that corresponds to the offeror’s CAGE code that is identified in Attachment L-5.
For past performance references where the offeror, JV Team Member, or subcontractor performed as a subcontractor, the offeror, JV Team Member or principal subcontractor shall provide a complete electronic copy of the SOW or PWS or other documentation of the agreement between the prime and subcontractor or the JV agreement that clearly defines the portions of the work effort of the Prime’s SOW/PWS that the offeror, JV Team Member, or principal subcontractor performed as a subcontractor. An offeror can submit contract documentation from a higher tier contract (e.g. a prime contract) for the past performance reference for the purposes of providing context on the contract requirements. However, the past performance references will only be evaluated based on the contract documentation provided for the entity identified in Attachment L-5 and in accordance with Section L, Part B, Paragraph 2.3.
2.3 Supporting documentation
The offeror shall only provide the following for each contract reference noted in accordance with Section L, Part B, Paragraph 2.2: 1) contract document for a contract with a Government agency or full purchase agreement for a contract between two commercial organizations; 2) complete SOW or PWS 3) subcontract or JV agreement. The offeror shall only provide the above contract documentation that are needed to demonstrate the current, accurate dollar value of the relevant contract line item numbers (CLINs) and the other relevancy information identified in Attachment L-3. The Government will not consider document deliverables under the past performance contract.
Moreover, the Government will not search for contract documents to fill gaps in the offeror’s proposal (such as a missing SOW).
The paragraphs cited in Attachment L-3 must be pinpoint citations to the lowest level paragraph that contains exact scope the offeror believes to be similar to the solicitation requirements. Do not provide high-level, broad citations.
2.4 Demonstrated Past Performance (DPP) Information
(E.g. CPAR’s and Contractor Performance Assessment Questionnaires (CPAQs).
Unless the Government directly solicits additional CPAQ’s as described in this section, a CPAQ is not required and SHALL NOT be submitted for past performance contracts that are ongoing and have a completed CPAR that is within 1 year from the date of issuance of the solicitation.
The offeror shall forward one (1) copy of the Contractor Performance Assessment Questionnaire (CPAQ), Attachment L-2, to the past performance contract reference customer’s Procuring Contracting Officer (PCO), Administrative Contracting Officer (ACO), Program Manager who is the Assessing Official, or Commercial Purchasing Agent via email. The offeror shall NOT complete the CPAQ, but submit to the point of contacts identified above for completion. The following past performance contract references instances must include a
CPAQ:
a. Past performance contract references that do not have CPARs.
b. Past performance contract references where the most recent CPAR completed by the Assessing Official is dated more than 1 year prior to the RFP’s release date and is not the final CPAR.
A past performance contract’s CPAR completed on a prime contractor will not be considered for the offeror or principal subcontractor performing as a subcontractor unless the subcontractor is identified specifically by name in the prime contractor’s CPARS report. If the offeror or principal subcontractor submits a past performance contract reference where the offeror or principal subcontractor performed as a subcontractor, then the offeror or principal subcontractor shall forward one (1) copy of the CPAQ, Attachment L-2, to the past performance contract reference Prime contractor program manager.
The Government will not evaluate CPAQs provided by offerors for completed contracts with a final CPAR submitted or for past performance contracts that are ongoing and have a completed CPARS report that is within 1 year from the date of issuance of the solicitation.
Small business concerns may provide other past performance rating information obtained IAW 13 CFR § 125.11.
The documentation shall clearly describe how the past performance reference meets the criteria for this rating information to be submitted.
Regardless of relevancy, the offeror, JV Team Members, and principal subcontractors shall provide all Show Cause Notices, Cure Notices, and Terminations for Default received on any contract, task order, or delivery order within five years of the issuance date of the final solicitation. For each instance, the offeror shall provide the contract, including any attached description of tasking, such as a SOW. This requirement applies to any contract, task order, or delivery order associated with the CAGE code and/or corresponding Unique Entity Identification (UEI) assigned with the CAGE code in SAM for the offeror, JV Team Members, and principal subcontractors proposed for this effort.
2.5 Narrative
The Offeror may include a narrative only if needed to (1) explain system improvement efforts concerning negative past performance information, or (2) to demonstrate that a past performance reference with a CAGE Code that is not shown in L-5 is nonetheless relevant pursuant to Section M, Part B, Paragraph 2.2. The only means of making such a demonstration is to (a) demonstrate that the Offeror acquired that other CAGE Code through a corporate acquisition, reorganization, merger and the personnel, facilities, or other resources of that other CAGE Code are now a part of the offeror and will be used to perform the requirements of the solicitation, or (b) the Government is required by 13 CFR 125.11 to consider the past performance where the offeror submits the information required by
13 CFR 125.11.
The offeror shall not provide self-described assertions of demonstrated past performance.
3.0 VOLUME III: PRICE
The Offeror shall submit a Price Volume consisting of: (1) a completed Section B, and, if necessary, (2) a Narrative.
3.01 Price
Provide a copy of section B of the solicitation populated with the CLIN unit prices and proposal prices using each CLIN’s quantity value.
3.02 Narrative
The offeror shall only submit a narrative if needed to address the below:
The offeror shall explain any appearance of unbalanced pricing in the proposal. Unbalanced pricing exists when, despite an acceptable total evaluated price, the price of one or more contract line items is significantly overstated as indicated by the application of price analysis techniques. Any apparent imbalances in the pricing or high proposed prices as compared to historical data should be fully explained.
3.1 ELEMENT: ADMINISTRATIVE
The offeror shall complete the following administrative requirements
a. Signed Standard Form 33 for basic solicitation and Standard Form 30 for each amendment, including completion of any RFP clause or provision that requires a fill-in or response.
b. Completed Section K.
c. Information to populate Section G.
d. The offeror shall include a statement that the proposal shall remain valid for a period of at least 180 days from the designated closing date indicated for receipt of proposals in the RFP.
e. Assumptions, Conditions, Exceptions, Deviations or Waivers: Assumptions, conditions, exceptions, deviations, and requests for waivers may cause proposals to be considered deficient and, thus, not awardable. If there are no assumptions, conditions, exceptions, deviations or waivers, the offeror shall provide a statement stating that the proposal contains no assumptions, conditions, exceptions, deviations or waivers. If the offeror proposes an assumption, condition, exception, deviation, or waiver to a term or condition of the solicitation, the offeror shall provide a detailed description for each assumption, condition, exception, deviation, or request for waiver, as applicable. The offeror shall identify the portion of the solicitation and the offeror’s proposal that are affected.
(End of Summary of Changes)
File details come from the government source that posted it. Updated .