Solicitation - SPRRA127QA004.pdf

REQUEST FOR QUOTATION

(THIS IS NOT AN ORDER)

THIS RFQ IS IS NOT A SMALL BUSINESS SET-ASIDE

15. DATE OF QUOTATION

16. SIGNER

a. NAME (Type or print)

c. TITLE (Type or print)

b. TELEPHONE

AREA CODE

NUMBER

STANDARD FORM 18 (REV. 6-95)

Prescribed by GSA-FAR (48 CFR) 53.215-1(a)

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition not usable

8. TO:

b. COMPANYa. NAME

c. STREET ADDRESS

d. CITY e. STATE f. ZIP CODE

9. DESTINATION

a. NAME OF CONSIGNEE

b. STREET ADDRESS

c. CITY

d. STATE e. ZIP CODE

7. DELIVERY

FOB DESTINATION

OTHER

(See Schedule)

10. PLEASE FURNISH QUOTATIONS TO THE

ISSUING OFFICE IN BLOCK 5a ON OR BEFORE CLOSE OF BUSINESS (Date)

IMPORTANT: This is a request for information and quotations furnished are not offers. If you are unable to quote, please so indicate on this form and return it to the address in Block 5a. This request does not commit the Government to pay any costs incurred in the preparation of the submission of this quotation or to contract for supplies or service. Supplies are of domestic origin unless otherwise indicated by quoter. Any representations and/or certifications attached to this Request for Quotation must be completed by the quoter.

11. SCHEDULE (Include applicable Federal, State and local taxes)

ITEM NO.

(a)

SUPPLIES/ SERVICES

(b)

QUANTITY

(c)

UNIT

(d)

UNIT PRICE

(e)

AMOUNT

(f)

12. DISCOUNT FOR PROMPT PAYMENT

a. 10 CALENDAR DAYS (%) b. 20 CALENDAR DAYS (%) c. 30 CALENDAR DAYS (%) d. CALENDAR DAYS

NUMBER PERCENTAGE

NOTE: Additional provisions and representations are are not attached.

13. NAME AND ADDRESS OF QUOTER

a. NAME OF QUOTER

b. STREET ADDRESS

c. COUNTY

d. CITY e. STATE f. ZIP CODE

14. SIGNATURE OF PERSON AUTHORIZED TO

SIGN QUOTATION

PAGE OF PAGES

1. REQUEST NO. 2. DATE ISSUED 3. REQUISITION/PURCHASE REQUEST NO. 4. CERT. FOR NAT. DEF.

UNDER BDSA REG. 2

AND/OR DMS REG. 1

RATING

5a. ISSUED BY 6. DELIVER BY (Date)

5b. FOR INFORMATION CALL (NO COLLECT CALLS)

NAME TELEPHONE NUMBER

AREA CODE NUMBER

Section A - Solicitation/Contract Form

BORESCOPE KIT, ENGINEInstrument Name:

Product Service Code : 6650

A-1. THIS IS A SINGLE PURCHASE FIRM-FIXED-PRICE (FFP) EFFORT FOR THREE (3) OF

NOUN: BORESCOPE KIT,ENGIN; NSN: 6650-01-234-1896; PART NUMBER: 21C7779P03

APPLICABLE TO T701C (UH-60/AH-64A) BLACKHAWK WEAPON.

A-2. FLIGHT SAFETY/CRITICAL SAFETY ITEM (CSI) IS NOT REQUIRED.

A-3. PRODUCTION LOT TESTING (PLT) IS NOT REQUIRED.

A-4. FIRST ARTICLE TEST (FAT) IS NOT REQUIRED.

A-5. SNRR MARKINGS ARE NOT REQUIRED.

A-6. TAMMS-A MARKINGS ARE NOT REQUIRED.

A-7. IUID MARKINGS ARE REQUIRED.

A-8. CONTRACTOR POINT OF CONTACT

NAME: TO BE DETERMINED AT TIME OF AWARD

TELEPHONE NUMBER: TO BE DETERMINED AT TIME OF AWARD

E-MAIL ADDRESS: TO BE DETERMINED AT TIME OF AWARD

A-9. DCMA POINT OF CONTACT

NAME: TO BE DETERMINED AT TIME OF AWARD

TELEPHONE NUMBER: TO BE DETERMINED AT TIME OF AWARD

E-MAIL ADDRESS: TO BE DETERMINED AT TIME OF AWARD

A-10. CONTRACT SPECIALIST POINT OF CONTACT

NAME: CHARLOTTE WITT

E-MAIL ADDRESS: charlotte.witt@dla.mil

SPRRA127QA004

A-11. This is a DO DPAS rated order, and you are required to notify DLA within 15 days of receipt of order if the rated order cannot be fulfilled as written. This includes conflicting rated order schedules. If no response is received during the required response time, the contractor self-attests order acceptance as is.

A-12. FOR LONG LEAD TIME ITEMS AND/OR LONG TERM CONTRACTS, THE PARTIES

RECOGNIZE THERE IS A RISK THAT PART(S) OR COMPONENT(S) REQUIRED FOR

PERFORMANCE OF THE CONTRACT/PURCHASE ORDER MAY BECOME UNAVAILABLE

DUE TO OBSOLESCENCE. UPON RECEIPT OF THE CONTRACT/PURCHASE ORDER,

CONTRACTOR IS RESPONSIBLE FOR VERIFYING ITS SOURCES OF SUPPLY. IF AT ANY

TIME DURING THE COURSE OF PERFORMANCE CONTRACTOR BECOMES AWARE THAT

IT IS UNABLE TO PROCURE A PART OR COMPONENT NECESSARY TO FULFILL THE

REQUIREMENTS OF THE CONTRACT, THE CONTRACTOR SHALL NOTIFY THE

CONTRACTING OFFICER IN WRITING WITHIN THIRTY DAYS. NOTIFICATION SHALL

INCLUDE CONTRACTORS RECOMMENDATION FOR CORRECTION OF THE PROBLEM, IF

POSSIBLE, WITH ESTIMATED COST AND SCHEDULE IMPACT, IF ANY. THE CONTRACTING

OFFICER WILL DETERMINE THE APPROPRIATE COURSE OF ACTION AND PROVIDE

DIRECTION TO THE CONTRACTOR. IN NO EVENT WILL CONTRACTOR PROCEED WITH

IMPLEMENTATION OF ITS RECOMMENDATION WITHOUT WRITTEN DIRECTION FROM THE

CONTRACTING OFFICER. AT THE SOLE DISCRETION OF THE CONTRACTING OFFICER,

THE CONTRACT MAY BE TERMINATED IN WHOLE OR IN PART, AS APPROPRIATE.

A-13. Product Quality Deficiency Reports (PQDRs): The Army utilizes the Product Quality Deficiency Report (PQDR) Program as required by the Defense Logistics Manual (DLM) 4000.25, Volume 2, June 24,2025 Change 21 and AR702-7-1 to identify, report, and resolve potential deficiencies found by the end user in products from the DoD supply chain. When requested by the Government, the Contractor shall assist the AvMC Systems Readiness Directorate (SRD) or the cognizant Contract Administration Office in evaluating PQDRs and exhibits for defects reported on items manufactured under this contract to determine the root cause for deficiencies. A final report should be given no later than 75 days after receipt of PQDR exhibit. Corrective action and Preventative Action to preclude recurrence of discrepancies shall be an integral part of the Contractor's Quality Program. The contractor shall not bill the Government as a direct charge for cooperation with the Government in the resolution of any PQDRs.

*** END OF NARRATIVE 1 ***

Section B - Supplies or Services & Prices or Costs

Additional Information/Notes

IAW 10 U.S.C. 2304(c)(1) FAR 6.302-1(a)(2). "A limited number of responsible sources and no other type of supplies or services will satisfy agency requirements; full and open competition need not be accounted for."

In the event only one proposal is received, this requirement will be evaluated as a sole source action, and all sole source procedures will be followed. See provision 252.215-7992, Only One Offer.

Approved Sources:

GENERAL ELECTRIC COMPANY, CAGE CODE: 99207

RHINESTAHL CORPORATION, CAGE CODE: 62340

RHINESTAHL CORPORATION, CAGE CODE: 5QE71

TRANSOM SCOPES, INC., CAGE CODE: 7U7S9

LENOX INSTRUMENT CO., INC., CAGE CODE: 35733

*** END OF NARRATIVE 1 ***

Item Supplies/Service Quanti ty

Unit Unit Price Amount

0001 BORESCOPE KIT, ENGINE

0001A A

BORESCOPE KIT, ENGINE

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification, or a DoD recognized unique identification equivalent.

3 Each

National Stock Number:

6650012341896

Manufacturer's CAGE: 81996

Manufacturer's Part Number:

21C7779P03

Product Service Code: 6650

Pricing Arrangement: Firm Fixed Price

Section C - Description/Specifications/Statement of Work

Requirements

BORESCOPE KIT,ENGINE

Section D - Packaging and Marking

PACKAGING/PACKING/SPECIFICATIONS:

MIL-STD-129 MARKINGS SHALL APPLY

UNIT PACK: 001 INTERMEDIATE PACK: 000

LEVEL PRESERVATION: MILITARY LEVEL PACKING: A

ADDITIONAL PACKAGING REQUIREMENTS

ESTIMATED MAXIMUM UNIT PACKAGE WEIGHT (POUNDS) AND SIZE (INCHES)

WT [23] LB

LN [25.5] IN

WD [24] IN

DP [13.5] IN

ALL WOOD PACKAGING MATERIAL (WPM) MUST BE ISPM-15 COMPLIANT

MIL-STD-2073-1 Codes, APPENDIX J

JI/A/MP [10] JII/CD [1] JIII/PM [00] JIV/WM [00] JV/CD [00]

JVI/CT [0] JVII/UC [ZZ] JVII/IC [00] JIX/A/PK [A] JX/SM [ZZ]

JVIIIA/OPI [M]

SUPPLEMENTAL INFORMATION:

ZZ=UC=CARRYING CASE OF ITEM IS SHIPPING CONTAINER; ZZ=SM=SPECIAL

MARKINGS 05&17

*** END OF NARRATIVE 1 ***

Section E - Inspection and Acceptance

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate Deviation

Variation Effective Date

52.246-1 Contractor Inspection Requirements.

1984-04

52.246-2 Inspection of Supplies-Fixed- Price.

1996-08

52.246-15 Certificate of Conformance. 1984-04

52.246-16 Responsibility for Supplies. 1984-04

FAR Clauses Incorporated by Full Text

Number Title Effective Date

Alternate Deviation

Variation Effective Date

52.246-11 Higher-Level Contract Quality Requirement.

2014-12

Higher-Level Contract Quality Requirement (Dec 2014)

(a) The Contractor shall comply with the higher-level quality standard(s) listed below.

ANSI/ISO/ASQ 9001:2015, AS 9100 OR EQUIVALENT, TAILORING: ALL PARAGRAPHS

UNDER 7.3 (DESIGN AND DEVELOPMENT) DO NOT APPLY.[Contracting Officer insert the title, number (if any), date, and tailoring (if any) of the higher-level quality standards.]

(b) The Contractor shall include applicable requirements of the higher-level quality standard(s) listed in paragraph (a) of this clause and the requirement to flow down such standards, as applicable, to lower-tier subcontracts, in-

(1) Any subcontract for critical and complex items (see 46.203(b) and (c)); or

(2) When the technical requirements of a subcontract require-

(i) Control of such things as design, work operations, in-process control, testing, and inspection; or

(ii) Attention to such factors as organization, planning, work instructions, documentation control, and advanced metrology.

(End of clause)

Section F - Deliveries or Performance

Accelerated Delivery Accelerated delivery of up to 180 calendar days prior to the established contract delivery date is authorized at no additional cost to the government. Any delivery exceeding 180 days early is strictly prohibited unless prior written approval has been granted by the contracting officer.

*** END OF NARRATIVE 1 ***

0001 Quantity

Address and POC

Special Handling/Notes FoB Details

Party to Pay Transportation Cost: Contractor

Point Type: Destination

0001AA From date of lead time event to delivery 270 Calendar Days

Date of Award DoDAAC: W62G2T

3 EachQuantity

Address and POC Ship To DoDAAC: W62G2T CountryCode: USA

W1A8 DLA DIST SAN JOAQUIN

25600 S CHRISMAN RD REC WHSE 57, TRACY CA 95304-5000 TRACY, CA

95304-5000 UNITED STATES

Special Handling/Notes FoB Details

Party to Pay Transportation Cost: Contractor

Point Type: Destination

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate Deviation

Variation Effective Date

52.242-17 Government Delay of Work. 1984-04

52.247-34 F.o.b. Destination. 1991-01

52.247-48 F.o.b. Destination-Evidence of Shipment.

1999-02

52.247-58 Loading, Blocking, and Bracing of Freight Car Shipments.

1984-04

Section G - Contract Administration Data

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate Deviation

Variation Effective Date

252.232-7003 Electronic Submission of Payment Requests and Receiving Reports.

2018-12

DFARS Clauses Incorporated by Full Text

Date

Alternate Deviation

Variation Effective Date

252.232-7006 Wide Area WorkFlow Payment Instructions.

2023-01

WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)

(a) As used in this clause- Definitions.

"Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization.

"Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

"Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system.

"Payment request" and "receiving report" are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(b) The WAWF system provides the method to electronically process Electronic invoicing.

vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) To access WAWF, the Contractor shall- WAWF access.

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

(d) The Contractor should follow the training instructions of the WAWF WAWF training.

Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the WAWF home page at https://wawf.eb.mil/

(e) Document submissions may be via web WAWF methods of document submission.

entry, Electronic Data Interchange, or File Transfer Protocol.

(f) The Contractor shall use the following information when WAWF payment instructions.

submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

(1) The Contractor shall submit payment requests using the following Document type.

document type(s):

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items-

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.

COMBO

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.

N/A

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial financing, submit a commercial financing request.

(2) ) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF "combo" document type to create some combinations of invoice and receiving report in one step.]

(3) The Contractor shall use the information in the Routing Data Document routing.

Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF

Pay Official DoDAAC TBD at time of award

Issue By DoDAAC

SPRRA1

Admin DoDAAC TBD at time of award

Inspect By DoDAAC TBD at time of award

Ship To Code W62G2T

Ship From Code TBD at time of award

Mark For Code N/A

Service Approver (DoDAAC) N/A

Service Acceptor (DoDAAC) N/A

Accept at Other DoDAAC N/A

LPO DoDAAC N/A

DCAA Auditor DoDAAC N/A

Other DoDAAC(s) N/A

(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert "See Schedule" or "Not applicable.")

(**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

(4) The Contractor shall ensure a payment request includes Payment request.

documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) The Contractor shall ensure a receiving report meets the Receiving report.

requirements of DFARS Appendix F.

(g) WAWF point of contact.

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

TBD

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

Section H - Special Contract Requirements

H-1. BAR CODE MARKINGS

Bar Code Markings are required in accordance with the latest revision of MIL-STD-129 and ISO /IEC 16388 - Information Technology - Automatic Identification and Data Capture Techniques - Bar code Symbology Specification - Code 39.

H-2. CALIBRATION

The calibration of Test, Measurement and Diagnostic Equipment shall be in accordance with American National Standards Institute/National Conference of Standards Laboratories (ANSI /NCSL) Z540-3-2006 (General Requirements for Calibration Laboratories and Measuring and Test Equipment) or ISO 10012:2003 (Quality Assurance Requirements for Measuring Equipment).

Terminology shall be as defined by International Organization for Standardization (ISO) 8402, Quality Management and Quality Assurance - Vocabulary.

H-3. ENGINEERING CHG PROPOSAL, VALUE ENG CHG PROPOSAL, REQUEST FOR

VARIANCE, ENG RELEASE RECORDS, NOTICE OF REVISION, AND SPECIFICATION CHG

NOTICE PREPARATION AND SUBMISSION INSTRUCTIONS

1. Contractor initiated Engineering Change Proposals (ECPs), Value Engineering Change Proposals (VECPs), and Request for Variance (RFVs), collectively referred to as "proposals", shall be prepared, submitted and distributed in accordance with paragraphs 2, 3 and 4 below except as specified in paragraph 5 below.

2. Format.

a. Class I ECPs require the "Long Form Procedure" for documenting the change and describing the effects of the change on the suitability and supportability of the Configuration Item (CI). Class I ECPs should be limited to those that are necessary or offer significant benefit to the Government.

Class I ECPs are those that affect the performance, reliability, maintainability, survivability, weight, balance, moment of inertia, interface characteristics, electromagnetic characteristics, or other technical requirements in the specifications and drawings. Class I ECPs also include those changes that affect Government Furnished Equipment, safety, compatibility, retrofit, operation and maintenance manuals, interchangeability, substitutability, replaceability, source control specifications and drawings, costs, guarantees or warranties, deliveries, or schedules. Class II ECPs are those that do not affect form, fit and function, cost, or schedule of the system CI and do not meet the other criteria described above for Class I ECPs.

b. Long Form Procedure: Class I changes to the CI require that DD Form 1692, pages 1 through 7 (as applicable), be prepared. Use of this procedure assures that all effects of the change on the CI

SPRRA127QA004 Page 16 of 60 are properly addressed and documented to the necessary detail to allow proper evaluation of the proposed change.

c. Short Form Procedure: ECPs and VECPs, which meet the requirements of Class II ECPs, shall be prepared using DD Form 1692 (page 1 only). Supplemental pages may be used with the form as necessary. The responsible Defense Contract Management Agency (DCMA) Contract Management Office (CMO) will validate data entries in Block 5 "Class of ECP", Block 6 "Priority", and Block 8 "Justification Codes."

d. The Contractor shall not manufacture items for acceptance by the Government that incorporate a known departure from requirements, unless the Government has approved an RFV. RFVs shall be prepared using DD Form 1694.

e. Each ECP and RFV shall be accompanied by a written and signed evaluation prepared by the responsible Defense Contract Management Agency (DCMA) technical representative. The DCMA written evaluation shall be considered part of the ECP/RFV proposal.

f. Classification of RFVs.

(1) Major RFVs. RFVs written against CIs shall be designated as major when the RFV consists of acceptance of an item having a nonconformance with contract or configuration documentation involving health; performance; interchangeability; reliability; survivability; maintainability; effective use or operation; weight; appearance (when a factor); or when there is a departure from a requirement classified as major in the contractual documentation.

(2) Critical RFVs. RFVs written against CIs shall be designated as critical when the RFV consists of acceptance of an item having a nonconformance with contract or configuration documentation involving safety or when there is a departure from a requirement classified as critical in the contractual documentation.

(3) Minor RFVs. RFVs written against CIs shall be designated as minor when the RFV consists of acceptance of an item having a nonconformance with contract or configuration documentation which does not involve any of the factors listed above in paragraphs f(1) or g(2), or when there is a departure from a requirement classified as minor in the contractual documentation.

g. Proposals shall include sufficient technical data to describe all changes from existing contract requirements.

h. Proposals shall include sufficient justification for making the change, including a statement of contract impact, if the change is not authorized.

i. Proposals for ECPs shall set forth a "not to exceed" price and delivery adjustment acceptable to the Contractor if the Government subsequently approves the proposal. If approved, the equitable increase shall not exceed this amount.

j. Times allowed for technical decisions for ECP and RFV proposals will be worked out via mutual agreement between the Contractor and the Government. SPRRA127QA004 Page 17 of 60

k. Proposals for VECPs shall set forth a "not less than" price and delivery adjustment acceptable to the Contractor if the Government subsequently approves the proposal. If approved, the savings shall not be less than this amount.

l. The Contractor shall utilize DD Form 2617, "Engineering Release Record" (ERR) to release new or revised configuration documentation to the Government for approval.

m. The Contractor shall utilize DD Form 1695, "Notice of Revision" (NOR) to describe the exact change(s) to configuration documentation specified as a data requirement in the contract. The Contractor shall describe the change using sub-sections entitled "WAS" to describe the current contractual technical requirement and "IS" to describe the proposed new requirement.

3. Submittal. The preferred method of submittal is digitally as a single file in Adobe Acrobat Portable Document Format (PDF). Unless otherwise specified, alternate methods of submittal shall be proposed to and authorized by the PCO prior to submittal. If the hardcopy method is requested and approved, the Contractor shall submit two (2) copies of each proposal to the responsible Administrative Contracting Officer (ACO). One (1) copy of each proposal shall be returned to the Contractor within (5) working days after receipt by the ACO, stating whether or not the proposal is in compliance with this provision. Any unresolved differences between the ACO and the Contractor concerning ECPs, VECPs, or RFVs will be submitted to the PCO for resolution.

4. Distribution.

a. Electronic Distribution. The preferred method of distribution for unclassified is through the email or DOD safe site (https://safe.apps.mil) addressed to the PCO. Classified material shall be distributed via SIPERNET or by classified email as determined by the PCO. Microsoft Word is required for use with the transmittal letter (E-mail). Required forms will be attached to the E-mail.

All forms may be obtained from the Office of the Secretary of Defense Executive Services Directorate DoD Directives Division website (http://www.esd.whs.mil/DD/) via the DoD Forms menu. The forms are provided in fillable Adobe Acrobat Portable Document Format (PDF). In order to access and use the forms, the user must have the "Adobe Acrobat" software installed on their computer. Drawings may be scanned and sent as an attachment. In some cases, because of size, drawings may have to be sent as hard copies or sent under special electronic instructions provided by the PCO.

5. Alternate Format, Submittal or Distribution Process. Proposals may be prepared in a different format, submitted using a different submittal process or distributed in a different manner than specified in paragraphs 2, 3 and 4 above, so long as the alternate approach is in accordance with a Government approved configuration management plan governed by this contract or the PCO authorizes the alternate format, submittal, or distribution process.

6. Government Acceptance. Acceptance of a proposal by the Government shall be affected by the issuance of a change order or execution of a supplemental agreement incorporating the proposal into the contract unless the PCO authorizes another method of acceptance. The Government will notify the Contractor in writing if a proposal is determined to be unacceptable. SPRRA127QA004

H-4. REVISIONS TO DRAWINGS/PART NUMBERS REQUIREMENT

(a) Sources in receipt of this solicitation are requested, at no cost to the Government, to immediately notify the Contracting Officer if they are aware of any change(s)/revision(s) to the drawing(s) or part number(s) in this solicitation which have been approved by the Government for implementation. Notification of part number changes shall be supported by data which indicates the type of change, approving authority as required by ANSI EIA 649 MIL-STD-973 and date and method of submittal of provisioning documentation and drawings. If complete data package has not been previously provided, the contractor shall, at no direct cost to the Government, immediately submit applicable drawings, along with a copy of the approval change authority, to the Contracting Officer, at the office symbol and mailing address listed in the "ISSUED BY" block on page one (1) of this document. The minimum acceptable data includes the next higher assembly and the item of Supply Detail Drawings which will allow provisioning, National Stock Number assignment and updating of AMCOM's data records.

(b) The contractor hereby verifies previous contractual submission of technical data:

Contract No.:

Contractor:

Explanation of Data Rights:

(c) The Government is not by this request soliciting, nor is the Government liable for cost incurred by the offeror in preparing or developing modifications, deviations, waivers, or other changes to drawings or part number(s). Furthermore, this request does not authorize changes to the drawing

(s) or part number(s) for this acquisition, another contract, or for any other purpose. Offerors performing any contract awarded as a result of this solicitation must comply with the drawing(s) and specifications as set forth herein, unless this solicitation is amended or any resulting contract is modified by the Contracting Officer.

(d) All proposed part number changes shall be submitted pursuant to the requirements of the requirement entitled, " ENGINEERING CHG PROPOSAL, VALUE ENG CHG PROPOSAL, REQUEST FOR VARIANCE, ENG RELEASE RECORDS, NOTICE OF REVISION, AND

SPECIFICATION CHG NOTICE PREPARATION AND SUBMISSION INSTRUCTIONS"

H-5. SOURCES ELIGIBLE FOR AWARD CONSIDERATION:

GENERAL ELECTRIC COMPANY, CAGE CODE: 99207

RHINESTAHL CORPORATION, CAGE CODE: 62340

RHINESTAHL CORPORATION, CAGE CODE: 5QE71

TRANSOM SCOPES, INC., CAGE CODE: 7U7S9

LENOX INSTRUMENT CO., INC., CAGE CODE: 35733

*** END OF NARRATIVE 1 ***

Section I - Contract Clauses

252.227-7013 RIGHTS IN TECHNICAL DATA--OTHER THAN COMMERCIAL PRODUCTS AND

COMMERCIAL SERVICES (AUG 2025)

(a) Definitions. As used in this clause--

"Computer data base" means a collection of data recorded in a form capable of being processed by a computer. The term does not include computer software.

"Computer program" means a set of instructions, rules, or routines recorded in a form that is capable of causing a computer to perform a specific operation or series of operations.

"Computer software" means computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae and related material that would enable the software to be reproduced, recreated, or recompiled. Computer software does not include computer data bases or computer software documentation.

"Computer software documentation" means owner's manuals, user's manuals, installation instructions, operating instructions, and other similar items, regardless of storage medium, that explain the capabilities of the computer software or provide instructions for using the software.

"Covered Government support contractor" means a contractor (other than a litigation support contractor covered by 252.204-7014) under a contract, the primary purpose of which is to furnish independent and impartial advice or technical assistance directly to the Government in support of the Government's management and oversight of a program or effort, (rather than to directly furnish an end item or service to accomplish a program or effort), provided that the contractor--

(1) Is not affiliated with the prime contractor or a first-tier subcontractor on the program or effort, or with any direct competitor of such prime contractor or any such first-tier subcontractor in furnishing end items or services of the type developed or produced on the program or effort; and

(2) Receives access to technical data or computer software for performance of a Government contract that contains the clause at 252.227-7025 , Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends.

"Detailed manufacturing or process data" means technical data that describe the steps, sequences, and conditions of manufacturing, processing or assembly used by the manufacturer to produce an item or component or to perform a process.

"Developed" means that an item, component, or process exists and is workable. Thus, the item or component must have been constructed or the process practiced. Workability is generally established when the item, component, or process has been analyzed or tested sufficiently to demonstrate to reasonable people skilled in the applicable art that there is a high probability that it will operate as intended. Whether, how much, and what type of analysis or testing is required to establish workability depends on the nature of the item, component, or process, and the state of the art. To be considered "developed," the item, component, or process need not be at the stage where it could be offered for sale or sold on the commercial market, nor must the item, component, or process be actually reduced to practice within the meaning of Title 35 of the United States Code.

"Developed exclusively at private expense" means development was accomplished entirely with costs charged to indirect cost pools, costs not allocated to a Government contract, or any combination thereof.

(1) Private expense determinations should be made at the lowest practicable level.

(2) Under fixed-price contracts, when total costs are greater than the firm-fixed-price or ceiling price of the contract, the additional development costs necessary to complete development shall not be considered when determining whether development was at Government, private, or mixed expense.

"Developed exclusively with government funds" means development was not accomplished exclusively or partially at private expense.

"Developed with mixed funding" means development was accomplished partially with costs charged to indirect cost pools and/or costs not allocated to a government contract, and partially with costs charged directly to a government contract.

"Form, fit, and function data" means technical data that describe the required overall physical, functional, and performance characteristics (along with the qualification requirements, if applicable) of an item, component, or process to the extent necessary to permit identification of physically and functionally interchangeable items.

"Generated" means, with regard to technical data or computer software, first created in the performance of this contract.

"Government purpose" means any activity in which the United States Government is a party, including cooperative agreements with international or multi-national defense organizations, or sales or transfers by the United States Government to foreign governments or international organizations. Government purposes include competitive procurement, but do not include the rights to use, modify, reproduce, release, perform, display, or disclose technical data for commercial purposes or authorize others to do so.

"Government purpose rights" means the rights to--

(1) Use, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction; and

(2) Release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes.

"Limited rights" means the rights to use, modify, reproduce, release, perform, display, or disclose technical data, in whole or in part, within the Government. The Government may not, without the written permission of the party asserting limited rights, release or disclose the technical data outside the Government, use the technical data for manufacture, or authorize the technical data to be used by another party, except that the Government may reproduce, release, or disclose such data or authorize the use or reproduction of the data by persons outside the Government if--

(1) The reproduction, release, disclosure, or use is--

(i) Necessary for emergency repair and overhaul; or

(ii) A release or disclosure to--

(A) A covered Government support contractor in performance of its covered Government support contract for use, modification, reproduction, performance, display, or release or disclosure to a person authorized to receive limited rights technical data; or

(B) A foreign government, of technical data other than detailed manufacturing or process data, when use of such data by the foreign government is in the interest of the Government and is required for evaluational or informational purposes;

(2) The recipient of the technical data is subject to a prohibition on the further reproduction, release, disclosure, or use of the technical data; and

(3) The contractor or subcontractor asserting the restriction is notified of such reproduction, release, disclosure, or use.

"Small Business Innovation Research/Small Business" Technology Transfer (SBIR/STTR) data means all technical data or computer software developed or generated in the performance of a phase I, II, or III SBIR/STTR contract or subcontract.

"Technical data" means recorded information, regardless of the form or method of the recording, of a scientific or technical nature (including computer software documentation). The term does not include computer software or data financial, administrative, cost or pricing, or management information, or information incidental to contract administration.

"Unlimited rights" means rights to use, modify, reproduce, perform, display, release, or disclose technical data in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so.

(b) Applicability.

(1) Except as provided in paragraph (b)(2) of this clause--

(i) This clause governs all technical data pertaining to other than commercial products or commercial services or to any portion of a commercial product or commercial servicethat was developed in any part at Government expense; and

(ii) The clause at Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7015, Technical Data--Commercial Products and Commercial Services, governs the technical data pertaining to any portion of a commercial product or commercial service that was developed exclusively at private expense.

(2) The clause at DFARS 252.227-7018, Rights in Other Than Commercial Technical Data and Computer Software--Small Business Innovation Research Program and Small Business Technology Transfer Program, governs technical data that are SBIR/STTR data.

(c) Rights in technical data. The Contractor grants or shall obtain for the Government the following royalty free, worldwide, nonexclusive, irrevocable license rights in technical data other than computer software documentation (see the DFARS 252.227-7014, Rights in Other Than Commercial Computer Software and Other Than Commercial Computer Software Documentation, clause of this contract for rights in computer software documentation):

(1) Unlimited rights. The Government shall have unlimited rights in technical data that are--

(i) Data pertaining to an item, component, or process which has been or will be developed exclusively with Government funds;

(ii) Studies, analyses, test data, or similar data produced for this contract, when the study, analysis, test, or similar work was specified as an element of performance;

(iii) Created exclusively with Government funds in the performance of a contract that does not require the development, manufacture, construction, or production of items, components, or processes;

(iv) Form, fit, and function data;

(v) Necessary for installation, operation, maintenance, or training purposes (other than detailed manufacturing or process data);

(vi) Corrections or changes to technical data furnished to the Contractor by the Government;

(vii) Otherwise publicly available or have been released or disclosed by the Contractor or subcontractor without restrictions on further use, release or disclosure, other than a release or disclosure resulting from the sale, transfer, or other assignment of interest in the technical data to another party or the sale or transfer of some or all of a business entity or its assets to another party;

(viii) Data in which the Government has obtained unlimited rights under another Government contract or as a result of negotiations; or

(ix) Data furnished to the Government, under this or any other Government contract or subcontract thereunder, with--

(A) Government purpose license rights or limited rights and the restrictive condition(s) has/have expired; or

(B) Government purpose rights and the Contractor's exclusive right to use such data for commercial purposes has expired.

(2) Government purpose rights.

(i) The Government shall have government purpose rights for a 5-year period, or such other period as may be negotiated, in technical data--

(A) That pertain to items, components, or processes developed with mixed funding except when the Government is entitled to unlimited rights in such data as provided in paragraphs (c)(1)(ii) and (c)(1)(iv) through (c)(1)(ix) of this clause; or

(B) Created with mixed funding in the performance of a contract that does not require the development, manufacture, construction, or production of items, components, or processes.

(ii) The 5-year period, or such other period as may have been negotiated, shall commence upon execution of the contract, subcontract, letter contract (or similar contractual instrument), contract modification, or option exercise that required development of the items, components, or processes or creation of the data described in paragraph (c)(2)(i)(B) of this clause. Upon expiration of the 5-year or other negotiated period, the Government shall have unlimited rights in the technical data.

(iii) The Government shall not release or disclose technical data in which it has government purpose rights unless--

(A) Prior to release or disclosure, the intended recipient is subject to the nondisclosure agreement at DFARS 227.7103-7 ; or

(B) The recipient is a Government contractor receiving access to the data for performance of a Government contract that contains the clause at DFARS 252.227-7025 , Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends.

(iv) The Contractor has the exclusive right, including the right to license others, to use technical data in which the Government has obtained government purpose rights under this contract for any commercial purpose during the time period specified in the government purpose rights legend prescribed in paragraph (g)(3) of this clause.

(3) Limited rights.

(i) Except as provided in paragraphs (c)(1)(ii) and (c)(1)(iv) through (c)(1)(ix) of this clause, the Government shall have limited rights in technical data--

(A) Pertaining to items, components, or processes developed exclusively at private expense and marked with the limited rights legend prescribed in paragraph (g) of this clause; or

(B) Created exclusively at private expense in the performance of a contract that does not require the development, manufacture, construction, or production of items, components, or processe

(ii) The Government shall require a recipient of limited rights data for emergency repair or overhaul to destroy the data and all copies in its possession promptly following completion of the emergency repair/overhaul and to notify the Contractor that the data have been destroyed.

(iii) The Contractor, its subcontractors, and suppliers are not required to provide the Government additional rights to use, modify, reproduce, release, perform, display, or disclose technical data furnished to the Government with limited rights. However, if the Government desires to obtain additional rights in technical data in which it has limited rights, the Contractor agrees to promptly enter into negotiations with the Contracting Officer to determine whether there are acceptable terms for transferring such rights. All technical data in which the Contractor has granted the Government additional rights shall be listed or described in a license agreement made part of the contract. The license shall enumerate the additional rights granted the Government in such data.

(iv) The Contractor acknowledges that--

(A) Limited rights data are authorized to be released or disclosed to covered Government support contractors;

(B) The Contractor will be notified of such release or disclosure

(C) The Contractor (or the party asserting restrictions as identified in the limited rights legend) may require each such covered Government support contractor to enter into a nondisclosure agreement directly with the Contractor (or the party asserting restrictions) regarding the covered Government support contractor's use of such data, or alternatively, that the Contractor (or party asserting restrictions) may waive in writing the requirement for a nondisclosure agreement; and

(D) Any such nondisclosure agreement shall address the restrictions on the covered Government support contractor's use of the limited rights data as set forth in the clause at DFARS 252.227- 7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends. The nondisclosure agreement shall not include any additional terms and conditions unless mutually agreed to by the parties to the nondisclosure agreement.

(4) Specifically negotiated license rights. The standard license rights granted to the Government under paragraphs (c)(1) through (c)(3) of this clause, including the period during which the Government shall have government purpose rights in technical data, may be modified by mutual agreement to provide such rights as the parties consider appropriate but shall not provide the Government lesser rights than are enumerated in the definition of "limited rights" of this clause.

Any rights so negotiated shall be identified in a license agreement made part of this contract.

(5) Prior government rights. Technical data that will be delivered, furnished, or otherwise provided to the Government under this contract, in which the Government has previously obtained rights shall be delivered, furnished, or provided with the preexisting rights, unless--

(i) The parties have agreed otherwise; or

(ii) Any restrictions on the Government's rights to use, modify, reproduce, release, perform, display, or disclose the data have expired or no longer apply

(6) Release from liability. The Contractor agrees to release the Government from liability for any release or disclosure of technical data made in accordance with the definition of "limited rights" or paragraph (c)(2)(iii) of this clause, in accordance with the terms of a license negotiated under paragraph (c)(4) of this clause, or by others to whom the recipient has released or disclosed the data and to seek relief solely from the party who has improperly used, modified, reproduced, released, performed, displayed, or disclosed Contractor data marked with restrictive legend.

(d) Contractor rights in technical data. All rights not granted to the Government are retained by the Contractor.

(e) Third party copyrighted data. The Contractor shall not, without the written approval of the Contracting Officer, incorporate any copyrighted data in the technical data to be delivered under this contract unless the Contractor is the copyright owner or has obtained for the Government the license rights necessary to perfect a license or licenses in the deliverable data of the appropriate scope set forth in paragraph (c) of this clause, and has affixed a statement of the license or licenses obtained on behalf of the Government and other persons to the data transmittal document.

(f) Identification and delivery of data to be furnished with restrictions on use, release, or disclosure.

(1) This paragraph does not apply to restrictions based solely on copyright.

(2) Except as provided in paragraph (f)(3) of this clause, technical data that the Contractor asserts should be furnished to the Government with restrictions on use, release, or disclosure are identified in an attachment to this contract (the Attachment). The Contractor shall not deliver any data with restrictive markings unless the data are listed on the Attachment.

(3) In addition to the assertions made in the Attachment, other assertions may be identified after award when based on new information or inadvertent omissions unless the inadvertent omissions would have materially affected the source selection decision. Such identification and assertion shall be submitted to the Contracting Officer as soon as practicable prior to the scheduled date for delivery of the data, in the following format, and signed by an official authorized to contractually obligate the Contractor:

IDENTIFICATION AND ASSERTION OF RESTRICTIONS ON THE GOVERNMENT'S USE,

RELEASE, OR DISCLOSURE OF TECHNICAL DATA

The Contractor asserts for itself, or the persons identified below, that the Government's rights to use, release, or disclose the following technical data should be restricted--

Technical Data

Name of Person to be Furnished

Basis for

Asserted Rights

Asserting

With Restrictions*

Assertion**

Category***

Restrictions****

(LIST)

(LIST)

(LIST)

(LIST)

*If the assertion is applicable to items, components, or processes developed at private expense, identify both the data and each such item, component, or process.

**Generally, the development of an item, component, or process at private expense, either exclusively or partially, is the only basis for asserting restrictions on the Government's rights to use, release, or disclose technical data pertaining to such items, components, or processes.

Indicate whether development was exclusively or partially at private expense. If development was not at private expense, enter the specific reason for asserting that the Government's rights should be restricted.

****Corporation, individual, or other person, as appropriate.

Date

Printed Name and Title

Signature

(End of identification and assertion)

(4) When requested by the Contracting Officer, the Contractor shall provide sufficient information to enable the Contracting Officer to evaluate the Contractor's assertions. The Contracting Officer reserves the right to add the Contractor's assertions to the Attachment and validate any listed assertion, at a later date, in accordance with the procedures in the DFARS 252.227-7037, Validation of Asserted Restrictions on Technical Data, clause of this contract.

(g) Marking requirements. The Contractor, and its subcontractors or suppliers, may only assert restrictions on the Government's rights to use, modify, reproduce, release, perform, display, or disclose technical data to be delivered under this contract by marking the deliverable data subject to restriction. Except as provided in paragraph (g)(6) of this clause, only the following legends are authorized under this contract: the government purpose rights legend at paragraph (g)(3) of this clause; the limited rights legend at paragraph (g)(4) of this clause; the special license rights legend at paragraph (g) (5) of this clause; and a notice of copyright as prescribed under 17 U.S.C. 401 or 402.

(1) General marking instructions. The Contractor, or its subcontractors or suppliers, shall conspicuously and legibly mark the appropriate legend on all technical data that qualify for such markings. The authorized legends shall be placed on the transmittal document or storage container and, for printed material, each page of the printed material containing technical data for which restrictions are asserted. When only portions of a page of printed material are subject to the asserted restrictions, such portions shall be identified by circling, underscoring, with a note, or other appropriate identifier. Technical data transmitted directly from one computer or computer terminal to another shall contain a notice of asserted restrictions. Reproductions of technical data or any portions thereof subject to asserted restrictions shall also reproduce the asserted restrictions.

(2) Omitted markings.

(i) Technical data delivered or otherwise provided under this contract without restrictive markings will be presumed to have been delivered with unlimited rights. To the extent practicable, if the Contractor has requested permission (see paragraph (g)(2)(ii) of this clause) to corret an inadvertent omission of markings, the Contracting Officer will not release or disclose the technical data pending evaluation of the request.

(ii) The Contractor may request permission to have conforming and justified restrictive markings placed on unmarked technical data at its expense. The request must be received by the Contracting Officer within 6 months following the furnishing or delivery of such technical data, or any extension of that time approved by the Contracting Officer. The Contractor shall--

(A) Identify the technical data that should have been marked;

(B) Demonstrate that the omission of the marking was inadvertent, the proposed marking is justified and conforms with the requirements for the marking of technical data contained in this clause; and

(C) Acknowledge, in writing, that the Government has no liability with respect to any disclosure, reproduction, or use of the technical data made prior to the addition of the marking or resulting from the omission of the marking.

(3) Government purpose rights markings. Data delivered or otherwise furnished to the Government with government purpose rights shall be marked as follows:

GOVERNMENT PURPOSE RIGHTS

Contract Number

Contractor Name

Contractor Address

Expiration Date

The Government's rights to use,…