AMD P00001-signed.pdf
PDF 519 KB Posted
- Attached to
- Air Force GEN IV IPV
- Solicitation number
- SPE4AX25R0015
- Issued by
-
Defense Logistics Agency Aviation
About this file
This document is a Standard Form 30 Amendment of Solicitation/Modification of Contract for SPE4AX-25-R-0015, issued by DLA Aviation for the Air Force GEN IV Industrial Product Support Vendor (IPV) contract. The amendment includes multiple significant updates:
Key modifications include adding a procurement note H13 for FAA parts delivery requiring specific airworthiness documentation, uploading documents to the DLA Automated Records Traceability (DART) database, and implementing new package marking requirements. The amendment also removes certain clauses like Service Contract Reporting Requirements, adds clauses about contract type (Firm Fixed Price with Economic Price Adjustment), and specifies an Indefinite Quantity contract structure. Additionally, the amendment updates solicitation submission guidelines, changing the number of copies required for Volume 5 (Price Proposal) from two hard copies to two electronic copies, and modifies various section references and metric calculation methodologies throughout the document.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| AMD P00002--signed.pdf | ||
| Attachment 1--Core LIst of Items_Market Basket LOCKED.xlsx | XLSX spreadsheet | |
| Attachment 2--Schedule of Items (SOI).xlsx | XLSX spreadsheet | |
| RFP SPE4AX25R0015--21 April 2025.pdf |
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
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 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 your 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.
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE
2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)
7. ADMINISTERED BY (If other than Item 6) CODE
STANDARD FORM 30 (REV. 10-83)
Prescribed by GSA FAR (48 CFR) 53.243
FACILITY CODE
9A. AMENDMENT OF SOLICITATION
NO.
9B. DATED (SEE ITEM 11)
10A. MODIFICATION OF CONTRACT/ORDER NO.
10B. DATED (SEE ITEM 13)
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.
12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. 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 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)
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.
15C. DATE SIGNED
15A. NAME AND TITLE OF SIGNER (Type or print)
16C. DATE SIGNED
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
PAGE OF PAGES
6. ISSUED BY CODE
8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X)
CODE
15B. CONTRACTOR/OFFEROR
(Signature of person authorized to sign)
16B. UNITED STATES OF AMERICA
(Signature of Contracting Officer)
NSN 7540-01-152-8070
Previous edition unusable
SPE4AX-25-R-0015 Page 2 of 12
The following updates have been incorporated into this solicitation:
1. The following procurement note H13 is hereby added and only applies to FAA parts that are delivered to the Air Force outside of original packaging not containing a QRC that corresponds to traceability information within DART:
H13 Airworthiness Parts for FAA Type Certified Aircraft – Contractor Requirements for Shipment Documentation, Upload of Documents into DLA Automated Records Traceability (DART) Database, and Package Marking (JAN 2025).
(a)The contractor shall furnish acceptable documentation with each shipment demonstrating appropriate certification of the item. Acceptable documentation is one of the following: (1) FAA Form 8130-3, Airworthiness Approval Tag; (2) Certificate of Conformance with information equivalent to information on FAA Form 8130-3, and compliant with the Contract Deliverables Requirements List; (3) European Aviation Safety Agency (EASA) Form 1, Authorized Release Certificate; or (4) Transport Canada Civil Aviation (TCCA) Form One, Authorized Release Certificate Form One. (2) Upload of Documents into DART Database (a) DART is a web-based application utilized to store and share documents between authorized users. Contractors are required to upload into DART a copy of the documentation described in paragraph (1)(a) of this procurement note. Contractors must be approved to access DART; requests for access to DART shall be emailed to:
DLADART@dla.mil. Upon being granted access, contractors will be emailed the DART Contractor User Guide. Contractors shall comply with the requirements outlined within DART Contractor User Guide. (b) The contractor shall upload into DART a copy of the documentation described in paragraph (1)(a) of this procurement note. Upon uploading the documentation, a Quick Release Code (QRC) will be presented to the contractor for download into the contractor’s computer/device. The contractor will transfer the QRC image to an adhesive label(s), no smaller than 3cm x 3cm, in preparation for printing and use in the contractor’s packaging operation. (c) Material that is manufactured in different lots shall have a unique document uploaded into DART; when completing the DART fill-ins prior to upload, the contractor will be prompted to fill-in the ‘lot’ field if applicable. A unique QRC will be presented to the contractor for each lot. (3) Shipping Container Marking (a) The contractor shall print the QRC adhesive label(s) and adhere a QRC label to each unit pack.
(b) For each shipping carton (or container), to include the intermediate carton (if utilized) and the outer carton, the contractor shall adhere a QRC label next to the MIL-STD-129 identification marking (label).
2. The following clauses hereby do not apply and are “unchecked”:
52-204-14, Service Contract Reporting Requirements (Oct 2016) (Pub. L. 111-118, section 743 of Div. C)
SPE4AX-25-R-0015 Page 3 of 12
52-204-15, Service Contract Reporting Requirements for Indefinite-Delivery Contracts (Oct 2016) (Pub. L. 111-117, section 743 of Div. C) 252.225-7001 Buy American and Balance Of Payments Program (FEB 2024) 252.225-7036, Buy American --Free Trade Agreements--Balance of Payment Program
(JUN 2022)
252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting (MAY 2024) FAR 52.208-9 Contractor Use of Mandatory Sources of Supply or Services
3. The following clause is hereby added:
FAR 52.216-01, Type of Contract “The Government contemplates award of a Firm Fixed Price with Economic Price Adjustment contract resulting from this solicitation. (End of provision)”
4. The following clause is hereby added:
FAR 52.216-22, Indefinite Quantity Contract “(a)This is an indefinite-quantity contract for the supplies or services specified, and effective for the period stated, in the Schedule. The quantities of supplies and services specified in the Schedule are estimates only and are not purchased by this contract.
(b)Delivery or performance shall be made only as authorized by orders issued in accordance with the Ordering clause. The Contractor shall furnish to the Government, when and if ordered, the supplies or services specified in the Schedule up to and including the quantity designated in the Schedule as the "maximum." The Government shall order at least the quantity of supplies or services designated in the Schedule as the "minimum."
(c)Except for any limitations on quantities in the Order Limitations clause or in the Schedule, there is no limit on the number of orders that may be issued. The Government may issue orders requiring delivery to multiple destinations or performance at multiple locations.
(d)Any order issued during the effective period of this contract and not completed within that period shall be completed by the Contractor within the time specified in the order. The contract shall govern the Contractor’s and Government’s rights and obligations with respect to that order to the same extent as if the order were completed during the contract’s effective period; provided, that the Contractor shall not be required to make any deliveries under this contract after 270 days from date of contract completion (End of clause)”
5. The following clause is hereby added:
SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT
REPORTING (MAY 2024) (DEVIATION 2024-O0013)
“(a) Definitions. As used in this clause— Adequate security means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information. Compromise means disclosure of information to
SPE4AX-25-R-0015 Page 4 of 12 unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred. Contractor attributional/proprietary information means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.
Controlled technical information means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions. Covered contractor information system means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information. Covered defense information means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is—
(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or
(2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract. Cyber incident means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein. Forensic analysis means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data. Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. Malicious software means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system.
This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware. Media means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system. Operationally critical support means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.
Rapidly report means within 72 hours of discovery of any cyber incident. Technical information means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data—Other Than Commercial
SPE4AX-25-R-0015 Page 5 of 12
Products and Commercial Services, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.
(b) Adequate security. The Contractor shall provide adequate security on all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:
(1) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government, the following security requirements apply: (i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract. (ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.
(2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply: (i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations”, Revision 2 (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171). (ii)(A) The Contractor shall implement NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.
(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.
(C) If the DoD CIO has previously adjudicated the contractor’s requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.
(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional
SPE4AX-25-R-0015 Page 6 of 12 information and equipment necessary for forensic analysis, and cyber incident damage assessment.
(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability.
These measures may be addressed in a system security plan. (c) Cyber incident reporting requirement.
(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor’s ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, the Contractor shall— (i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts.
This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor’s network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor’s ability to provide operationally critical support; and (ii) Rapidly report cyber incidents to DoD at https://dibnet.dod.mil.
(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at https://dibnet.dod.mil.
(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see https://public.cyber.mil/eca/.
(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer. (e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest. (f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information equipment that is necessary to conduct a forensic analysis. (g) Cyber incident damage assessment activities.
If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause. (h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor https://dibnet.dod.mil/
SPE4AX-25-R-0015 Page 7 of 12 attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released. (i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD—
(1) To entities with missions that may be affected by such information;
(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;
(3) To Government entities that conduct counterintelligence or law enforcement investigations;
(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or
(5) To a support services contractor (“recipient”) that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information. (j) Use and release of contractor attributional/proprietary information created by or for DoD.
Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government’s use and release of such information. (k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data. (l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor’s responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements. (m) Subcontracts. The Contractor shall—
(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial products or commercial services, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and
(2) Require subcontractors to— (i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this
SPE4AX-25-R-0015 Page 8 of 12 clause; and (ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause. (End of clause)”
6. FAR 52.229-3 Federal, State, and Local Taxes.
“(a)As used in this clause-
After-imposed Federal tax means any new or increased Federal excise tax or duty, or tax that was exempted or excluded on the contract date but whose exemption was later revoked or reduced during the contract period, on the transactions or property covered by this contract that the Contractor is required to pay or bear as the result of legislative, judicial, or administrative action taking effect after the contract date. It does not include social security tax or other employment taxes.
After-relieved Federal tax means any amount of Federal excise tax or duty, except social security or other employment taxes, that would otherwise have been payable on the transactions or property covered by this contract, but which the Contractor is not required to pay or bear, or for which the Contractor obtains a refund or drawback, as the result of legislative, judicial, or administrative action taking effect after the contract date.
All applicable Federal, State, and local taxes and duties means all taxes and duties, in effect on the contract date, that the taxing authority is imposing and collecting on the transactions or property covered by this contract.
Contract date means the date set for bid opening or, if this is a negotiated contract or a modification, the effective date of this contract or modification.
Local taxes includes taxes imposed by a possession or territory of the United States, Puerto Rico, or the Northern Mariana Islands, if the contract is performed wholly or partly in any of those areas.
(b)(1)The contract price includes all applicable Federal, State, and local taxes and duties, except as provided in subparagraph (b)(2)(i) of this clause.
(2)Taxes imposed under 26 U.S.C. 5000 C may not be-
(i)Included in the contract price; nor
(ii)Reimbursed.
(c)The contract price shall be increased by the amount of any after-imposed Federal tax, provided the Contractor warrants in writing that no amount for such newly imposed Federal excise tax or duty or rate increase was included in the contract price, as a contingency reserve or otherwise.
http://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title26-section5000&num=0&edition=prelim
SPE4AX-25-R-0015 Page 9 of 12
(d)The contract price shall be decreased by the amount of any after-relieved Federal tax.
(e)The contract price shall be decreased by the amount of any Federal excise tax or duty, except social security or other employment taxes, that the Contractor is required to pay or bear, or does not obtain a refund of, through the Contractor’s fault, negligence, or failure to follow instructions of the Contracting Officer.
(f)No adjustment shall be made in the contract price under this clause unless the amount of the adjustment exceeds $250.
(g)The Contractor shall promptly notify the Contracting Officer of all matters relating to any Federal excise tax or duty that reasonably may be expected to result in either an increase or decrease in the contract price and shall take appropriate action as the Contracting Officer directs.
(h)The Government shall, without liability, furnish evidence appropriate to establish exemption from any Federal, State, or local tax when the Contractor requests such evidence and a reasonable basis exists to sustain the exemption. (End of clause)”
7. Replace the following language in Section L.1.1:
Volume Page Limits Number of Written Copies Description 1 N/A 2* Completed RFP 2 30 4* Written Technical Proposal 3 50 4* Written Management Proposal 4 N/A 4* Past Performance 5 N/A 2* Price Proposal
*Volumes 1-5 shall be submitted in written form in the number of copies that is expressed in the table above. In addition to the those written copies, a CD-R or DVD-R (write once/read only) (1 copy) that is “closed” so that no further writes can be made to the media shall be provided. CD-RW or DVDR/W media types are not acceptable. Media must be virus scanned by the Offeror prior to submitting to the Government.
WITH
Volume Page Limits Number of Written Copies Description 1 N/A 2* Completed RFP 2 30 4* Written Technical Proposal 3 50 4* Written Management Proposal 4 N/A 4* Past Performance 5 N/A 0* Price Proposal
*Volumes 1-4 shall be submitted in written form in the number of copies that are expressed in the table above. In addition to the those written copies, a CD-R or DVD-R (write
SPE4AX-25-R-0015 Page 10 of 12 once/read only) (1 copy) that is “closed” so that no further writes can be made to the media shall be provided. Volume 5 shall be submitted in the form of two electronic copies via a CD-R or DVD-R (write once/read only) that is “closed” so that no further writes can be made to the media shall be provided. CD-RW or DVDR/W media types are not acceptable.
Media must be virus scanned by the Offeror prior to submitting to the Government.
8. Replace the following language in Section L.1.1 (2):
“The page limitation for Volume 2 and 3, Written Technical Proposal is 30 pages, and the Written Management Proposal is 50 pages. The page limitation includes any drawings, diagrams supporting illustrations, or spreadsheets, etc. but excludes any table of contents, resumes of key personnel, Small Business Subcontracting Plan, ISO 9001 (or equivalent) certifications or list of acronyms (if utilized). Offerors are cautioned that any pages that exceed the page limitation shall be removed and either retained in the contract file without being considered in the evaluation or sent back to the Offeror.”
WITH
“The page limitation for Volume 2 and 3, Written Technical Proposal is 30 pages, and the Written Management Proposal is 50 pages. The page limitation includes any drawings, diagrams supporting illustrations, or spreadsheets, etc. but excludes any table of contents, resumes of key personnel, Small Business Subcontracting Plan, ISO 9001 (or equivalent) certifications, Summary Subcontract Reports (SSR) or list of acronyms (if utilized). Offerors are cautioned that any pages that exceed the page limitation shall be removed and either retained in the contract file without being considered in the evaluation or sent back to the Offeror.”
9. Replace the following language in Section L.2.1.2 (5):
“Any information substantiating the Offeror’s track record of utilizing small business on past contracts in detail shall be included. At a minimum, the two most recent Summary Subcontract Reports (SSR).”
WITH
“Any information substantiating the Offeror’s track record of utilizing small business on past contracts in detail shall be included. At a minimum, the two most recent Summary Subcontract Reports (SSR). The SSR pages will not count toward the page limits listed in Section L.1.1.”
10. Replace the following language in Section L.2.4:
“Volume 5 shall be clearly marked as “Volume 5 – Price Proposal” and all information relating to price must be included in this section. Each offeror must submit two hard copies and one copy via digital media as stated in L.1.1. REMINDER: DO NOT DELETE
LINES IN ATTACHMENTS 1, 13, OR 14.”
SPE4AX-25-R-0015 Page 11 of 12
WITH
“Volume 5 shall be clearly marked as “Volume 5 – Price Proposal” and all information relating to price must be included in this section. Each offeror must submit two electronic copies via digital media as stated in L.1.1. REMINDER: DO NOT DELETE LINES IN
ATTACHMENTS 1, 13, OR 14.”
11. Replace the NAICS code in box 10 of page 1 of the solicitation with the correct NAICS code of 332722.
12. Replace “Page 1 of 19” on page 1 of the solicitation with “Page 1 of 129”.
13. Replace in all headers of the solicitation “SPE4AX-25-D-0015” with “SPE4AX-25-R- 0015”.
14. Replace any references to Integrated Product Support Vendor (IPV) with Industrial
Product Support Vendor (IPV).
15. Replace references to “BFR” in Sections H-902 and Section 7.1.1 of the PWS with
“FPA”.
16. Remove the following from Section M.3.1 as resumes are not applicable to the
Technical factor only the Management factor:
“Information contained in the submitted resumes pursuant to Section L.2.1 will be used in evaluating Offerors’ proposals according to the criteria listed below.”
17. Replace the following language in Section H-902, First Pass Acceptance:
FPA will be calculated as follows: FPA = [{1 - (Number of FPA failures reported in a given month) divided by (sum of the total non-automated bins supported plus the number of instances in which a mechanic requests a part from the automated bins or automated systems during the month plus the total kit MDR for the site)}*100].”
WITH
“FPA will be calculated as follows: FPA = [{1 - (Number of FPA failures reported in a given month) divided by (sum of the total non-automated bins supported plus the number of instances in which a mechanic requests a part from the automated bins or automated systems during the month plus the total kit MDR for the site plus the total lines on the recommended deletion for the site)}*100].”
18. Replace the following language in Section H-903, Mechanic Wait Time (MWT) Metric:
“MWT is calculated as the time it takes the Contractor to fill a bin/kit once it has a FPA failure, measured as the difference between the time the first FPA failure for a bin/kit is
SPE4AX-25-R-0015 Page 12 of 12 reported to the Contractor and when all FPA failures for the bin/kit have been remedied by the Contractor as verified by the COR.”
WITH
“MWT is calculated as the time it takes the Contractor to fill a bin/kit once it has a FPA failure, measured as the difference between the time the FPA failure for a bin/kit is reported to the Contractor and when the FPA failure for the bin/kit has been remedied by the Contractor as verified by the COR.”
19. The following language in Section H-903, Mechanic Wait Time (MWT) Metric has been deleted:
“MWT will be measured per bin/kit.”
20. Replace the following language in Section 5.2, Secondary Metric: Mechanic Wait Time
(MWT):
“MWT is calculated as the time it takes the Contractor to fill a bin / kit once it has an FPA failure, measured as the difference between the time the first FPA failure for a bin / kit is reported to the Contractor and when all FPA failures for the bin / kit have been remedied by the Contractor as verified by the COR.”
WITH
“MWT is calculated as the time it takes the Contractor to fill a bin/kit once it has a FPA failure, measured as the difference between the time the FPA failure for a bin/kit is reported to the Contractor and when the FPA failure for the bin/kit has been remedied by the Contractor as verified by the COR.”
21. Due to a change in Attachment 14 only, the current filed titled “Attachment 1--Core List of Items_Market Basket LOCKED.xlsx” is hereby replaced with “Attachment 1-- Core List of Items_Market Basket LOCKED v2.xlsx”.
22. Attachment 7 is hereby replaced with file titled “Attachment 7--Detailed Meeting Requirements updated 13 May 2025.docx”.
| CONTINUATION PAGE FOR MOD P00040.pdf |
| 6 Management Information System (MIS) |
| 6.1 Demand Data Exchange (DDE) and Web Based Customer Collaboration (CC) |
| 6.2 Supportability Analysis |
| 6.2.1 Objectives |
| 6.2.2 Scope |
| topmostSubform[0]: |
| Page1[0]: |
| AmendmentNo[0]: P00001 |
| Code[0]: SPE4AX |
| Code[1]: |
| AccountingData[0]: |
| A13[0]: |
| C13[0]: |
| D13[0]: |
| NameandTitleSigner[0]: |
| NameandTitleOfficer[0]: Robert J. Napolitano II |
| Description[0]: |
Please see continuation page(s).
| FacilityCode[0]: |
| Code[2]: SPE4AX |
| IssuedBy[0]: DLA AVIATION |
ASC SMSG DIV SPECIAL ACQUISITION
6090 STRATHMORE ROAD, RICHMOND, VA 23237
NameandAddress[0]:
AdministeredBy[0]: DLA AVIATION
6090 STRATHMORE ROAD
RICHMOND, VA 23237
| ContractIDCode[0]: | |
| ReqNumber[0]: 1000199557 | |
| AmendmentNo[1]: SPE4AX-25-R-0015 | |
| ModificationNo[0]: | |
| ProjectNo[0]: | |
| Page[0]: 1 | |
| Pages[0]: 12 | |
| EffectiveDate[0]: 06/03/2025 | |
| Dated9B[0]: 2025 April 21 | |
| Dated10B[0]: | |
| CheckBox9[0]: 1 | |
| CheckBox10[0]: Off | |
| CheckBox11[0]: 1 | |
| CheckBox13A[0]: Off | |
| CheckBox13B[0]: Off | |
| CheckBox13C[0]: Off | |
| CheckBox13D[0]: Off | |
| IsNot[0]: Off | |
| Is[0]: Off | |
| Extended[0]: Off | |
| NotExtended[0]: 1 | |
| 2025-06-02T10:16:25-0400 | |
| NAPOLITANO.ROBERT.J.II.1258008193 |
| DateSigned[0]: |
| DateSigned[1]: 03 June 2025 |
| Copies[0]: 1 |
| CopiesReturned[0]: |
File details come from the government source that posted it. Updated .