DRAFT_RFS_Advanced Electrochromic Prototype-120423.pdf

PDF 424 KB Posted

Attached to
Draft Request for Solutions (RFS) Advanced Electrochromic Manufacturing Prototype Project
Solicitation number
W900KK-24-R-9001
Issued by

About this file

This document is a Request for Solutions (RFS) for an Advanced Electrochromic Manufacturing Prototype Project issued by the Department of the Army Materiel Command Contracting Command Orlando Contracting Center.

The RFS seeks proposals for prototypes of single-piece electronically dimmable eyewear for eye protection that utilizes mature electrochromic technology. Proposals must demonstrate the ability to manufacture the prototypes within 24 months of award with a budget of $4.6 million. Interested parties must submit solution papers by January 8, 2024 addressing their technical approach, past experience, pricing, and future production capabilities. The Army intends to award one Other Transaction Agreement and will evaluate solutions based on feasibility, risk, price, and ability to meet the objectives. The work will be conducted at the unclassified level with export controls applying to any results with defense applications.

View the file

Other files

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

DRAFT Request for Solutions (RFS) Advanced Electrochromic Manufacturing Prototype Project

December 2023

1.0 Purpose

This Request for Solutions (RFS) is being issued to identify potential solutions for prototypes of single piece electronically dimmable (auto-tinting) eyewear protection device (EDEPD) for eye protection gear (goggles, glasses, or helmet visors). Ideally, the prototype(s) will be a U.S based solution that utilizes mature electrochromic technology with the capability to be manufactured expediently and is completed within 24 months after Receipt of Agreement (ARA). The Government will evaluate the solutions with the intent to competitively award one Other Transaction Agreement (OTA) for this project.

However, more than one award may be made if determined to be in the Government’s best interest. This effort will be unclassified.

2.0 Authority

Title 10 United States Code (U.S.C.) 4022: Authority of the Department of Defense to carry out certain prototype projects, authorizes the use of Other Transactions (OTs) to acquire prototype capabilities and allow for those prototypes to transition into Production OTs. Under this authority, both dual-use and defense-specific projects are encouraged.

Pursuant to 10 U.S.C. 4022, if competitive procedures were used for the selection of parties for participation in the transaction for a prototype pilot and the participants in the transaction successfully completed the prototype project, production OTs are authorized and offer a streamlined method for transitioning into follow-on production without competition. Potential follow-on production contracts may be either sole source, based on successful completion of the prototype project within the scope of this document, or competed at the discretion of the Government.

It is anticipated that upon successful completion of the prototype, a follow-on production OTA or FAR based contract may be issued to the vendor(s) without the use of competitive procedures. Further, the Government reserves the right to determine part, or all the prototype project is successfully completed if the vendor shows a particularly favorable or unexpected result justifying the transition to production.

Prior to issuing a sole source Follow-On production agreement or contract, the Government will enter negotiations with the vendor(s) of the successful prototype. The negotiations may include evaluation of all potential cost element categories applicable to the effort and may also use price realism analysis. The Government will utilize the most applicable method in determining cost elements and prices are fair and reasonable.

To ensure appropriate use of this authority, a prototype agreement will not be entered into unless one of the following conditions is met:

(A) There is at least one nontraditional defense contractor or nonprofit research institution participating to a significant extent in the prototype project.

(B) All significant participants in the transaction other than the Federal Government are small businesses (including small businesses participating in a program described under section 9 of the Small Business Act (15 U.S.C. 638)) or nontraditional defense contractors.

(C) At least one third of the total cost of the prototype project is to be paid out of funds provided by sources other than the Federal Government.

A “Nontraditional defense contractor” is defined as an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of Defense (DoD) for the procurement or transaction, any contract or subcontract for the DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to 41 U.S.C §1502 and the regulations implementing such section.

3.0 Background

Goggles, glasses and helmets for pilots and Battlefield Airmen/soldiers have traditionally had to rely on donning/doffing/carrying separate units to maintain eye protection for operations under conditions across seven orders of ambient illumination from very dark (0.01 lux, moonless overcast night, inside of buildings/caves) to extremely bright (108 kilolux, full sun day). The current solution for dismounts is carrying two sets of goggles/eyewear. The current solution for pilots is to wear a helmet with two passive polycarbonate (PC) visors (one clear, one dark). This solution requires pilots to manually switch visors as lighting conditions change which can detract from flying or ground mission operations. Especially in single-seat aircraft, this process offers limited functionality and can put pilot safety at risk.

4.0 Goals

4.1 Overall Goals: The Government intends to enable expedient manufacturing of a novel electrochromic lens technology that will highly improve the visual display systems that the Department of Defense has made significant investments in already. The end goal of this effort will benefit several DoD programs that use electrochromic auto-tinting technology such as:

• F-35 Fighter Joint Program Office, which has established the requirement to improve the current production helmet system performance by way of a single day/night visor to replace the current two visor solution while reducing neck-born weight and helmet system complexity;

• Program Executive Office (PEO) Soldier, which acquires protective eyewear (spectacles) under its Army Approved Protective Eyewear List (APEL) to improve performance by expanding the dimming range and production capacity; and,

• Potential other applications including the goggle lens component of the Integrated Visual Augmentation System (IVAS) being developed for Soldiers and Marines.

4.2 Prototype Demonstrative Goals: The awardee(s) of this Advanced Electrochromic Manufacturing Project shall:

• Demonstrate the ability to deliver the prototypes of a single piece electronically dimmable eyewear protection device (EDEPD) for eye protection gear (goggles, glasses, or helmet visors) within the desired schedule,

• Deliver prototype test articles for the Government to evaluate against requirements,

• Successfully validate a single piece electronically dimmable eyewear protection device (EDEPD) for eye protection gear (goggles, glasses, or helmet visors) test articles,

• Certify the achievable Technology Readiness Level (TRL) and Manufacturing Readiness Level (MRL) with Government, and

• Demonstrate the Manufacturing Capabilities and Processes using US-based Qualified Sources of Supplies

5.0 Technical Objectives

For this OTA, the Government does not intend to provide Government Furnished Information (GFI) or Government Furnished Property (GFP). As such, vendors are responsible for providing all necessary resources to meet its proposed solution. The Government reserves the right to provide GFI of GFP should it be determined to be advantageous to the Government.

5.1 Minimum final prototype threshold requirements and Government’s overall program objectives: The following table provides the minimum threshold requirements for the final prototype and the Government’s overall EPEDP program objectives.

Description Threshold Objective Transmission modulation range

(Tmax – Tmin) 77% 99%

Tmax Clearest State 85% 100% Tmin Darkest State 8% 1% Maximum Switching speed in either direction 2s 200µs

Maximum Power Density (W/cm2)

6000 µW/cm2 10 µW/cm2

Maximum Haze 3% 1%

Transmission uniformity 10% 5% Minimum Lifetime 12 mos 36 mos Color neutrality Slight color tinting (specify

CIE(u’v’ coordinates) No noticeable color tinting (specify CIE (u’v’) coordinates)

Number of transmission states 2 = on/off Continuously variable Minimum Life Power) (without battery change) 8 hrs 72 hrs

Material/Supply Chain Maximum US based 100% US based

TRL 4 8

MRL 4 8

Production Rate:

• Toroidal visor (200 cm2 active area)

• Spherical goggle (40cm2 active area)

• Spectacle lens pair (27 cm2 active area)

• Toroidal visors: 20

/week AND/OR

• Spherical goggles:

50/week AND/OR

• Spectacle lens

250/week

• Toroidal visors:

40 /week

• Spherical goggles:100/week

• Spectacle lens:

500/week Fail Clear (to Tmax) when power supply is disconnected

Mandatory Mandatory

Weight • Same as the currently fielded EDEPD

• Less than the currently fielded

EDEPD

If offered solutions do not meet any of the above minimum thresholds, the solution paper shall provide explanation/reason for the limitation.

Offered solutions shall identity and provide a mitigation plan for significant technical challenges/risks that may prevent the final prototype from meeting minimum thresholds.

Vendors shall list all current non-US based material(s)/supply chain(s) and identify potential methods to transition US based material(s)/supply chain(s).

5.2 Project Technical Milestones/Decision Points (DP)

The program awardee will provide the following deliverables After Receipt of Agreement (ARA) as indicated. This portion should be included in the draft SOW with further detail provided to match proposed solution. For example, if the proposed solution includes quarterly submission of advancing test samples, then the draft SOW should have a corresponding section/paragraph that correlates with each submission.

5.2.1 Project Kick-off

The Contractor shall support a project Kick-off Meeting within thirty (30) calendar days After Receipt of Award (ARA) and provide presentation charts two (2) workdays prior.

The agenda shall address project scope, performance, schedule, progress, funding, metrics, risks and their mitigation, and new product opportunity analyses.

5.2.2 Project Execution Plan (2 months ARA)

The Contractor shall host the Project Execution Plan (PEP) meeting, within sixty (60) days ARA. The PEP shall include the following:

a. Facility tour including laboratory and manufacturing areas.

b. Presentations with agenda including:

i. Introduction of Personnel (Management, Technical);

ii. Company Business Plan and synergies with this (OASD(IBP) project;

iii. Current and Planned Product Roadmap;

iv. Plan of Action and Milestones (POAM),

v. Performance metric-based approach for expanding domestic manufacturing capabilities and improving technical performance,

vi. Supply chain for current products;

vii. Plans to on-shore any items not currently available from a US based source.

5.2.3 Design and Manufacturing Plan (3 months ARA)

The Contractor shall provide Design and Manufacturing Plan of their approach toward the agreed upon deliverables to the Government within three (3) months ARA. The focus of the design and manufacturing plan shall include but not limited to:

a. Design to include the solution of the prototype:

i. Solution of the prototype/product with all the requirements in 3.2

ii. Improvement (if any) to meet the objectives

iii. U.S.-Based Supply chain and Materials

iv. Non-U.S.-based Supply Chain and Materials

v. Software & Hardware

vi. Technical Risks, Supply Chain risks and Mitigation plans

b. Manufacturing plan, processes, and target of production rate:

i. Facility

ii. Equipment

iii. Supply chain capability and resilience

iv. Target production capability

v. Manufacturing technology Risks, Supply Chain risks and Mitigation plans

5.2.4 Monthly Progress Reports and Quarterly Project Management Reviews

(PMR)

The Contactor shall provide a written Monthly Progress Report limited to 20 pages of text/figures/tables describing: (a) technical and manufacturing achievements since the prior month, (b) plans for next month, and (c) a discussion of any issues. A written Monthly Progress Report is not required in months in which a Quarterly PMR is conducted.

Starting in the third month ARA the Contractor shall support either virtually or in person Quarterly PMR meetings throughout the life of the agreement. The Quarterly PMR read-ahead materials will be submitted to the government 7 business days before the meetings. The PMR shall cover the state of the project execution plan (milestones completed), progress on deliverables, the quality of monthly status reports, funding status, schedule (Gantt chart), comparison of current performance metrics vs. prototype thresholds/program objectives, and other pertinent information.

5.2.5 Test Article Sets

Solutions shall identify multiple sets of Test Articles for submission to the government for testing to validate the progression of the prototype throughout development. This shall identify the Test Article type, quantity and timeline for each submission. The Government preference is for increasing quantities (minimum quantity of four (4)) of test articles at six (6) month intervals until delivery of the final prototype quantities. The first set test article submitted will establish the baseline EDEPD performance for the manufacturer. The manufacturer shall provide test reports of these articles which include all the requirements listed in the SOW. The report shall include the baseline TRL of this set.

5.2.6 Final Set of Test Articles

Depending on the offered solution, the final set of test articles shall include 20 Toroidal visors and/or 35 Spherical goggles and/or 200 Spectacle lens to demonstrate the manufacturing capabilities and prove the processes using US-based qualified sources of supplies. The report shall include the manufacturer’s test reports that meet or exceed all the requirements listed in the SOW. The report shall include the Government expected TRL and MRL for this set.

5.2.7 Final Reports (24 months ARA)

a. Technical report of the prototypes/products to include:

i. Certification of TRL/MRL with Government

ii. Test Reports

iii. US-based suppliers with production capabilities, and

iv. Equipment used.

b. Manufacturing capabilities and processes reports

6.0 Solution Paper

Utilizing the requirements, objectives and goals described in this RFS, interested parties should prepare a solution paper and a draft Statement of Work (SOW) to accomplish its proposed solution. The Government has a current budget of $4.6M and a desired prototype delivery time of 24 months. Interested parties should provide proposed solutions that fall within the current budget and timeframe.

All submissions shall be unclassified.

Vendors are responsible for marking proprietary information appropriately.

Solution paper responses shall consist of one volume to include a General, Technical, Price, and Future Capabilities section. Responses shall be submitted in an editable/executable (not scanned) Word/Adobe PDF format. The Technical Approach/Solution Paper of the Technical section is limited to no more than 20 standard size (8 ½” X 11”) pages using standard margins and a standard and easily readable font, such as 12-point Arial font. Each page of the Technical Approach/Solution Page shall be numbered. Please note, each Section and Subsection, with the exception of the Futures Capability Section, is required to be completed and submitted by the appointed submission date and time. Failure to do so may limit your ability to receive an Agreement award. The proposed solution and draft SOW will be used to collaboratively negotiate a Final SOW for incorporation in the OTA.

Section Subsection Format** Counted towards page limit Page Limit*

Yes No

General

Cover Page/Vendor Information

MS

Word/PDF X

No Page Limit

Award Eligibility Requirement

MS

Word/PDF X

FOCI Status

MS

Word/PDF X

OCI & Mitigation Plan

MS

Word/PDF X

Technical Sub-Vendor List

MS

Word/PDF X 20-Page Limit

Vendor Experience

MS

Word/PDF X

Technical Approach / Solution Paper*

MS

Word/PDF X

Draft SOW

MS

Word/PDF X

Data Rights Assertation Tables

MS

Word/PDF X

Delivery Schedule

MS

Word/PDF Plan of Action and Milestone (POAM)

MS

Word/PDF X

Price Pricing Breakout MS Excel X No Page Limit Basis Of Estimate MS Excel X

Future Capability

Future Prototype Enhancements

Vendor format X No Page

Limit Follow-on Production

Vendor format X

*As noted below, Offerors have the choice to include the Materials and Supply Chain Table as a separate appendix and not count against the Technical Approach/Solution Paper page limit.

6.1 General Section (unlimited page count)

1. Cover Page/Vendor Information

2. Award Eligibility Requirements

3. Foreign Owned status

4. Organizational Conflicts of Interest and Mitigation Plans

6.1.1 Vendor Information

The Vendor information shall include the vendor’s name, Commercial and Government Entity (CAGE) Code (if available), NAICS Code, Business Size, Traditional, Small- Business and/or Non-Traditional status, address, primary point of contact, and status of U.S. ownership. The NAICS codes for this effort are 541715 Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology), 541713 Research and Development in Nanotechnology, and Product Service Code (PSC) AC13 National Defense R&D Services; Department of Defense – Military.

6.1.2 Award Eligibility Requirements

The vendor shall identify and describe how it meets the award eligibility requirements of 10 U.S.C. §4022(d)(1) that are noted in paragraph 2 above.

6.1.3 Foreign Owned, Controlled or Influenced (FOCI)

In accordance with RFS Attachment 1, PEO STRI Vendor/Contractor Vetting Process the vendor must include certification that the vendor (and subcontractor(s)) are not Foreign Owned or under USA Foreign Owned, Controlled or Influenced (FOCI) status (and are not in merger or purchasing discussions for a Foreign company or USA FOCI Company). Should a prospective vendor be unable to self-certify, they will be ineligible for award unless the mitigating circumstances in Attachment 1: PEO STRI Vendor/Contractor Vetting Process are met. In such a case, these mitigating circumstances shall be detailed in an appendix to the General Volume. Per Attachment 1: PEO STRI Vendor/Contractor Vetting Process, all vendors (Prime and Subs) must be vetted for eligibility, suitability, national status e.g., Foreign or USA Foreign Owned, Controlled and Influenced (FOCI) prior to the receipt of any award instrument.

6.1.4 Organizational Conflicts of Interest and Mitigation Plans

The vendor will submit an Organizational Conflict of Interest Mitigation Plan via an Appendix to its General Section. In the event there are no real or perceived OCIs, simply state so and annotate what actions would be taken in the event that one is realized.

6.2 Technical Section

The following shall be included within the Technical Section:

1. Sub-vendor List

2. Vendor Experience

3. Technical Approach/Solution Paper

4. Data Rights and Assertions

5. Anticipated Delivery Schedule

6. Plan of Action and Milestone (POAM)

6.2.1 Sub-Vendor List

Provide a list of all sub-vendors involved and their role within the performance of your submission as an appendix (which will not count towards the page count) stating any team member name(s), their role within the performance of your submission, FOCI status, OCI, Unique Entity ID, Commercial and Government Entity (CAGE) Code, Business Size for the appropriate NAICS Code.

6.2.2 Vendors Experience

Vendor shall describe their company or team’s, recent and relevant previous experience developing and manufacturing similar electronically dimmable eyewear protection device (EDEPD) for eye protection gear (goggles, glasses, or helmet visors) to the required work of this project. Projects worked in the last three years from the release of the RFS are considered recent.

6.2.3 Solution/Technical Approach

Vendor shall clearly describe its proposed solution along with identifying and defining what it considers successful completion. Successful completion should corelate with Government requirements and objectives identified in this document. The technical approach should clearly address all requirements, objectives, risks with mitigation solutions, deliverables, demonstrations, design reviews, testing approach to meet requirements, total project risk, and management reviews.

The solution shall discuss the feasibility of the technical approach by, at minimum, describing the following:

• Facility plan to demonstrate the proposed production capability.

• Approach technology in details, such as voltage-forced current flows thru electrolyte, voltage controlled molecular rotations, etc.

• The power supply approach (self-contained on lens, off-lens power supply located on helmet, in temple, or inside backpack) and life cycle of the power supply and duration of the full charged product.

• Evidence of the offerors ability to incorporate its solution into a physics based digital model. The model shall relate material properties to device performance parameters such as optical, temporal, electrical, mechanical, and weight.

• Materials used and supply chain, comprising a schematic diagram of solution offered. Vendors shall provide materials and supply chains with a table-formatted Bill of Materials (BoM) listing each functional material layer, chemical/trade names of material(s) used, and vendor information (name, address, URL).

Offerors may choose to include this table as a separate appendix so as not to count against the page count. The following is a sample format that may be utilized:

Part number

Functional Material Layer

Chemical/Trade names

Vendor/supplier Information

(name & location)

Vendor/ Supplier’s

URL

US-Base supplier

(Y/N)

6.2.4 Draft Statement of Work (SOW)

The vendor shall prepare a draft SOW completing at minimum the technical and deliverable portions of the SOW. The Sample SOW is not a complete SOW and only includes the Technical, Deliverable and Data Rights portion of the SOW. The Sample

SOW is provided to assist vendors; however, vendors are not required to utilize the sample and may use a format of its choosing. The proposed solution and draft SOW will be used to collaboratively negotiate a Final SOW, in government format, for incorporation in the OTA. Essentially, the draft SOW shows how the vendor will implement and accomplish its technical approach.

6.2.5 Data Rights Assertion Tables

The vendor shall complete the Data Rights Assertions Tables, Attachment 2, for all technical data (including computer software documentation) and computer software to be developed or delivered under the OTA. The data rights assertion table shall identify at the lowest segregable level the technical data (including computer software documentation) and computer software to be developed or delivered under its proposed solution, the vendor’s assertion as to the Government’s rights in each item of technical data (including computer software documentation) and computer software, the basis for such assertion, and the name of the person asserting any restrictions.

For any technical data (including computer software documentation) or computer software in which the vendor asserts the Government will have less than Government purpose rights, the vendor shall provide the open source, commercial, or other license it asserts is applicable. The vendor’s assertions, including any assertions of its sub-vendors or suppliers must be submitted as an attachment to its Solution Paper. The tables must be completed in the format set forth in the attachment, dated and signed by an official authorized to contractually obligate the vendor. If additional space is necessary, additional pages may be included. There is no page limit for the Data Rights Assertions Tables, and they do not count against the proposed technical solution page limitation.

6.2.5.1 Government Desired Rights in Technical Data and Computer Software

The Government requires Government Purpose Rights (GPR) in all technical data (including computer software documentation) and computer software developed under any OTA associated with this effort, for, at most, a five-year period. The five-year period, or such other period as may be negotiated, will commence upon execution of the OTA that required development of the technical data (including computer software documentation) and computer software. Upon expiration of the five-year (or other negotiated period), the Government desires unlimited rights in the technical data (including computer software documentation) and computer software.

Any commercial or COTS software necessary as a deliverable shall be provided with a transferable license that allows distribution of the software and transfer of the license to any Government agency or DoD vendor for any prototype project related purpose. All software licensing shall include a minimum term of five years of use. All software shall be provided with any available major upgrades, minor updates, security patches and technical support for the entire PoP. When the addition of new software or hardware is proposed for the system or developed under this solicitation with Government funding or partial Government funding, the vendor shall ensure that sufficient rights in technical data to include (software and hardware) are procured to enable the Government to maintain and modify the system using Government personnel and/or third-party vendors. Government approval is required for exceptions to GPR.

In its solution, the vendor for any OTA awarded in accordance with this RFS shall analyze feasible non-proprietary solutions and incorporate such solutions into its proposed solution when practicable. This preference for non-proprietary solutions applies to any technical data (including computer software documentation) and computer software developed or delivered under the OTA. The vendor shall clearly state all assumptions made during development of its proposal.

6.2.5.2 Data Rights License Terms Definitions

For the purpose of this RFS and final award document, the Government will use the data rights and computer software related terms defined in Attachment 4, Data Rights License Terms Definitions.

6.2.6 Anticipated Delivery Schedule

The vendor shall include the anticipated delivery dates with their solution that includes all completion dates for all objectives as described in the RFS. The Government’s desire is to complete the full set of requirements in 24 months after award.

6.2.7 Plan of Action and Milestone (POAM)

A POAM shall be provided. The POAM should be resource loaded with each task including predecessor (if applicable). The POAM may be attached as an appendix file.

The POAM is not included in the total page count and page count is unlimited.

Definition: A Plan of Action and Milestone (POAM) is a document for that “identifies tasks needing to be accomplished. It details resources required to accomplish the elements of the plan, any milestones in meeting the tasks, and scheduled completion dates for the milestones.”

6.3 Price Volume

1. Pricing Breakout

2. BOE

6.3.1 Pricing Breakout

Vendors are advised that the maximum fixed price ceiling budget available for the Advanced Electrochromic Manufacturing Prototype Project is: $4.6M.

The Government will evaluate the vendors pricing solution to determine if the solution price is within budget.

Vendors shall submit a fixed amount price for its solution, further divided into severable milestones. The Government is not dictating a specific price mechanism. However, proposed payments should be linked to clearly definable, detailed milestones of the prototype project events. They should clearly and precisely communicate what is being delivered at each milestone. The vendor’s pricing milestones may vary from the defined decision points, depending on the proposed solution. Milestones should be established and priced in a manner that prohibits milestone efforts from being worked concurrently.

Each milestone price should reflect the anticipated value the Government will receive toward accomplishment of the OTA goals and objectives at the time the milestone is completed. The price volume/section has no page number limitation.

6.3.2 Basis of Estimate (BOE)

Vendors shall provide a BOE, separated by individual phases, objectives, and pricing milestones, for the entire effort based on the solution of objective(s) submitted by the vendor. The vendor shall provide general cost or pricing information to support the BOE.

6.4 Future Capabilities:

This shall be a separate section that is clearly distinct from the proposed prototype solution paper and draft SOW. This portion can be provided in general terms and should illustrate achievable and feasible estimates for further prototype enhancements and follow-on production. This section is for future planning purposes and to better understand the vendor’s vision for its proposed solution. This will assist the Government with 1) understanding industry’s perceived capabilities 2) developing budget estimates, and 3) developing achievable future requirements. The Government may consider potential future capabilities/requirements in its evaluation.

6.4.1 Further prototype enhancements

The Government understands that it may not be feasible for a vendor to achieve all program objectives within the stated budget and timeframe. As a result, the Government requests top-level task, time, and Rough Order of Magnitude (ROM) cost estimates to achieve all desired technical requirements that can be achieved within a period of up to five years. Ideally, capabilities and cost estimates would be broken down by program objectives to provide the Government various options should additional funding become available. This portion may not be necessary if the solution meets all project objectives or no further enhancements are possible. If this applies, solutions should simply annotate this.

6.4.2 Follow-on Production

Pursuant to 10 U.S.C. 4022, if competitive procedures were used for the selection of parties for participation in the transaction for a prototype pilot and the participants in the transaction successfully completed the prototype project, production OTs are authorized and offer a streamlined method for transitioning into follow-on production without competition. Potential follow-on production contracts may be either sole source, based on successful completion of the prototype project within the scope of this document, or competed at the discretion of the Government.

It is anticipated that upon successful completion of the prototype, a follow-on production OTA or FAR based contract may be issued to the vendor without the use of competitive procedures. Successful completion will occur when the prototype has been validated and is accepted by the Government. Successful completion will be defined in the negotiated SOW for this project. If GFE has been issued for the development of the prototype, the GFE may remain at the vendor’s facility. Data rights for all deliverables will be in accordance with Government Desired Rights in Technical Data and Computer Software in Section 6.2.5.1.

Further, the Government reserves the right to determine part, or all the prototype project is successfully completed, if the vendor shows a particularly favorable or unexpected result justifying the transition to production.

Prior to issuing a sole source Follow-On production agreement or contract, the Government will enter negotiations with the awarded vendor. The negotiations may include evaluation of all potential cost element categories applicable to the effort and may also use price realism analysis. The Government will utilize the most applicable method in determining cost elements and prices are fair and reasonable.

In this portion of the Future Capabilities Section, vendors should provide:

• A description of manufacturing capabilities and facilities outlining the vendor’s ability to ramp up production at the end of the prototype project, to include tooling leading to higher level assembly improvements.

• Production rate capabilities for its offered solution (Toroidal visors and/or Spherical goggles and/or Spectacle lens).

• ROM pricing for potential follow-on production activities.

7.0 RFS Response Instructions:

The cost of preparing and submitting a response is not considered an allowable direct charge to any Government contract or agreement.

Non-compliance with the submission instructions provide herein may preclude the vendor from being considered for award.

All questions related to this RFS should be submitted using the Vendor Questions form provided as Attachment 5. Questions must be submitted via email to:

jaime.morrison.civ@army.mil and Kurt Kleinlein at kurt.l.kleinlein.civ@army.mil with “Advanced Electrochromic Prototype Project Question” used in the subject line.

Questions must be submitted no later than 15:00 PM ET 12 December 2023.

Questions received after the deadline may not be answered. Questions shall not include proprietary data.

The Government reserves the right to post submitted questions and answers, as necessary (and appropriate) to facilitate vendor Solution Paper responses. Submitted questions will be posted without identifying company names.

Solution responses shall be submitted no later than 15:00 PM ET on 8 January 2024.

Your response shall be submitted electronically to jaime.morrison.civ@army.mil and Kurt Kleinlein at kurt.l.kleinlein.civ@army.mil, with “ADVANCED ELECTROCHROMIC PROTOTYPE PROJECT RESPONSE” used in the subject line. Any submissions received after the deadline may be rejected as late and not considered.

Vendors must clearly state assumptions made within their response. Vendors are encouraged to challenge any Government assumptions or restrictive requirements in its individual solution and should articulate any major discrepancies between the RFS and its technical solution. Should a vendor’s solution require a change in policy and/or statue, the vendor shall outline within their technical volume, and describe why the change is needed to realize the benefit of the vendor’s prototype (and potential production).

Vendor’s solutions shall be valid for at least 180 days after submission.

8.0 Evaluation and Selection Process

The Government intends to award one OTA for this project. However, more than one award may be made if determined to be in the best interest of the Government.

The Government anticipates awarding to the vendor(s) whose solution best satisfies the Government’s objectives and is considered the most advantageous to the Government.

The Government will evaluate solutions wholistically against the requirements and objectives listed in this RFS, considering all four (4) sections of the solution paper.

Solutions should be complete, identify how the vendor is eligible to receive a prototype agreement award, provide a clear description of the proposed solution, be thorough, innovative, feasible and technically sound, and be within the desired time frame and budget as set forth in this RFS. The following provides interested vendors insight into the Government’s evaluation to determine the solution(s) that best satisfies the Government’s objectives and is considered the most advantageous to the Government:

a) Eligibility for Award: Vendor’s solution paper clearly identifies its status to receive a prototype agreement award pursuant to 10 U.S.C. 4022.

b) Vendor Experience: The performing vendor’s company or team’s recent and relevant experience with developing and manufacturing product lines for similar single piece electronically dimmable eyewear protection device (EDEPD) for eye protection gear (goggles, glasses, or helmet visors). Projects worked in the last three years from the release of the RFS are considered recent.

c) Technical Approach: Technical approach and the draft SOW clearly express thoroughness, innovation, clarity, feasibility and soundness, and risk of the proposed approach in meeting the requirements and technical objectives.

d) Data Rights: The vendor’s technical response will require that they clearly outline the appropriate assertion right in technical data, computer software and software documentation that will be delivered with the solutions with minimum GPRs. Data rights will be evaluated for completeness and if they are commensurate with the Government’s impact on development of data.

e) Delivery Schedule and POAM: Vendor proposed schedule is within the Anticipated schedule and meets the Project Technical Milestones/Decision Points. POAM identifies feasible tasks to be accomplished with predecessor tasks and highlights any long-lead items.

f) Price: Solution includes fixed price amount price, divided into realistic and severable milestones, that is within the Government’s stated budget. The price is commensurate with the proposed solution.

In making the final decision it may be necessary to compare solutions to determine which solution(s) are most advantageous to the Government. If the Government receives more than one highly rated solution, the Government may down select to vendors whose solutions are the most advantageous and technically feasible in order to hold expanded conversations.

Prior to award, the Government will conduct SOW collaborations and negotiate the potential final Agreement with the vendor(s) initially identified as having the most advantageous solution. Should those collaborations and negotiations be unsuccessful or result in the vendor(s) solution no longer being considered the most advantageous, the Government reserves the right to award an agreement to a vendor whose solutions was not initially considered the most advantageous solution.

The Government reserves the right to award to a respondent that does not meet all the requirements of the RFS but provides attributes or partial solutions of value.

Use of Non-Disclosure Agreements (NDAs)

Government participants and advisors in the evaluation process will be required to sign Non-Disclosure Agreements (NDAs), as well as ensuring the procedures are in accordance with 41 U.S.C. 423, Procurement Integrity Act.

Non-Government Advisors

This is to advise you that non-Government advisors will assist in the evaluation. The use of non-Government advisors will be strictly controlled. Non-Government advisors will be required to sign a NDA prior to viewing the Advanced Electrochromic Project.

The Agreements Officer (AO) will review NDAs for conflict prior to allowing access to evaluation information.

All non-Government advisors will only have access to the information corresponding to their area(s) of expertise. Advisors will not have access to the Price Volume of the response. The companies identified herein have agreed not to engage in the manufacture or production of hardware/services/R&D that is related to these efforts, and to refrain from disclosing proprietary information to unauthorized personnel.

The following company will have non-Government personnel advising:

ANSER

5275 Leesburg Pike Suite N-5000 Falls Church, VA 22041 Cage Code: 4A458

9.0 Security

This prototype project will be conducted at the Unclassified and Controlled Unclassified Information (CUI) level.

9.1 Export controls:

Research findings and technology developments arising from the resulting project may constitute a significant enhancement to the national defense and to the economic vitality of the United States. As such, in the conduct of all work related to this effort, the recipient will comply strictly with the International Traffic in Arms Regulation (22 C.F.R.

§§ 120-130), the National Industrial Security Program Operating Manual (DoD 5220.22- M) and the Department of Commerce Export Regulation (15 C.F.R. §§ 730-774).

Printed deliverable (e.g., printed hardcopies, .doc, web-based html, etc.) will be labeled accordingly and contain all appropriate markings associated with the distribution classification.

All technical data and information developed under this effort should be marked with the appropriate marking in accordance with DoDI 5320.24, Distribution Statements on Technical Documents. This generally should be marked with “DISTRIBUTION STATEMENT D. Distribution authorized to the DoD and U.S. DoD contractors only (fill in reason) (date DD MM YYYY). Other requests shall be referred to PEO STRI.”

9.2 Interaction and/or Disclosure with Foreign Country/Foreign National Personnel.

The contractor should comply with foreign disclosure processes IAW Army Regulation 380‐10, Foreign Disclosure and Contacts with Foreign Representatives; the Department of the Navy Foreign Disclosure Manual, SECNAV M-5510.34, as of June 2017;

Department of Defense Directive (DoDD) 5230.11, Disclosure of Classified Military Information to Foreign Governments and International Organizations; and DoDD 5230.20, Visits and Assignments of Foreign Nationals.

10.0 Attachments

Attachment 1: PEO STRI Vendor/Contractor Vetting Process Attachment 2: Data Rights Assertions Tables Attachment 3: Data Rights License Terms and Definitions Attachment 4: Terms and Conditions and EULA Attachment 5: Vendor Questions Form Attachment 6: Section 889-Telecommunications Representations Attachment 7: Sample Draft Statement of Work

1.0 Purpose
2.0 Authority
3.0 Background
4.0 Goals
5.0 Technical Objectives
5.2 Project Technical Milestones/Decision Points (DP)
5.2.1 Project Kick-off
5.2.3 Design and Manufacturing Plan (3 months ARA)
5.2.4 Monthly Progress Reports and Quarterly Project Management Reviews (PMR)
5.2.5 Test Article Sets
Solutions shall identify multiple sets of Test Articles for submission to the government for testing to validate the progression of the prototype throughout development. This shall identify the Test Article type, quantity and timeline for each submiss...
5.2.6 Final Set of Test Articles
5.2.7 Final Reports (24 months ARA)
6.1 General Section (unlimited page count)
6.1.1 Vendor Information
6.1.2 Award Eligibility Requirements
6.1.4 Organizational Conflicts of Interest and Mitigation Plans
6.2 Technical Section
6.2.1 Sub-Vendor List
6.2.2 Vendors Experience
6.2.3 Solution/Technical Approach
6.2.5.1 Government Desired Rights in Technical Data and Computer Software
7.0 RFS Response Instructions:
8.0 Evaluation and Selection Process
9.0 Security
9.1 Export controls:

10.0 Attachments

File details come from the government source that posted it. Updated .