Attachment 4.pdf

Attachment 4

Detailed Proposal Information

In addition to Appendix 2 of N0001425SB01, please include the following information when submitting a proposal package.

To the extent possible, the proposal should separate the classified elements into a separate appendix (included in the page count), keeping the majority of the proposal unclassified.

Proposal Package shall not exceed 50 pages plus exempted full page graphics.

A. Technical Proposal.

A.1. Technical and Management Approach: Provide a management plan that describes the proposed system development processes and management approach to support successful program execution. The proposal should describe teaming arrangements as appropriate. Lessons learned from prior experience in managing efforts with this level of complexity and uncertainty should be discussed. Provide an overview of the system development processes to be used along with the organizational responsibilities and authority for the development effort. Describe how the Production and Prototype design efforts have been integrated and sequenced to accelerate the

Prototype design products. Describe the proposed level of Government interaction to facilitate efficient interactions and streamlined decision making. Include in the management plan the proposed programmatic approach to cost, schedule, and risk management. Define the content of technical and financial progress reports to enable efficient program monitoring, tracking, and reporting. Program management tools should be the same tools used internally to manage the program; no additional unique information for the Government is desired or required.

A.2. Technical Understanding: Identify the key technical challenges encompassing both design and fabrication of OEX, including, but not limited to, the S&T issues of reliability, external communications, endurance, and robust autonomy as described in Attachment 1, Section

II. A. Key Program Objective and S&T Challenges (please see N0001425SBC04 Amendment 1) and describe your technical approach to addressing these challenges in Preliminary Design.

A.3. Integrated Master Schedule (IMS): The IMS shall detail the specific tasks to be accomplished, their inter-relationship, and time sequencing. This section should include:

• Provide a high-level description of the schedule with key events depicted. This description should explain how the schedule accounts for ONR’s desire to minimize the timeline to final PDR for the “Prototype Vehicle”.

• Identify the critical path, potential risks, and schedule risk mitigation plans.

• Provide the IMS in Microsoft Project electronic native format that can be printed on 11 by 17 inch foldout pages.

• The WBS structure in the IMS shall correlate with the Cost and SOW volume structure.

Approved, DCN# 2025-12-18-1783 12/19/2025

DISTRIBUTION STATEMENT A. Approved for public release: distribution is unlimited. 1 of 3

The IMS should be unclassified and should not contain any proprietary information.

The government desires an overall duration of 1 year for Phase I.

A.4. Deliverable descriptions.

For each sample deliverable listed in Attachment 1, Section II C.1 Phase 1A Preliminary Design and C.2 Phase 1B (Option) Detailed Design (please see N0001425SBC04 Amendment 1), provide a complete description of the content of the deliverable, standards used in determining content, and format to be used. For electronic forms, specify the media to be used and which commercially available product is required to read it.

A.5. Project Team and Experience.

The offeror should provide a management plan that describes the proposed engineering processes and management approach to support successful Phase 1 execution.

Boilerplate process description is strongly discouraged; this section should rather be seen as an opportunity to illustrate, where applicable, how the offeror’s processes have been used during proposal writing. In this section, the proposal shall:

• The offeror should describe proposed teammates, their competencies and proposed roles, and how the overall capabilities of the proposed team matches technologies and challenges of the OEX project.

• Key personnel should have adequate experience from past programs that is relevant to their proposed role on this program. ONR requires key personnel identified in the proposal to be assigned as proposed, and the resulting contract/agreement will indicate no substitution shall be made without prior approval of the Government.

• The offeror should provide resumes and qualifications of key personnel including the proposed Program Manager and any functional area leads as defined by the offeror’s team organization. This section should describe the role on the program, along with the percentage time commitment of each of these key personnel (not part of page count).

• The offeror should identify the specific capabilities and experience of the team members in the key S&T challenges of reliability, external communications, endurance, and autonomy.

• The offeror should discuss its ability to execute programs of similar content and complexity on schedule and within budget as demonstrated by the team corporate experience and key personnel performance on relevant past programs.

• Describe the capability and experience of the team in developing plans for fabrication and system integration of OEX sized seaframes and systems.

A.6. Resumes: Resumes for proposed key personnel should be provided. Each individual resume should be limited to two (2) pages.

B. Statement of Work (SOW):

DISTRIBUTION STATEMENT A. Approved for public release: distribution is unlimited. 2 of 3

B.1. Statement of Work (SOW): In plain English, clearly define the technical tasks/subtasks to be performed, their durations, and dependencies among them. The offeror shall employ a common work breakdown structure (WBS), or other detailed project organization structure, for numbering all activities in the SOW, IMS, and cost proposal. A less detailed WBS breakdown is acceptable for level-of-effort type tasks such as program management, program control, etc. The page length for the SOW will be dependent on the amount of effort. For each task/subtask, provide:

• A general description of the objective (for each defined task/activity);

• A detailed description of the approach to be taken to accomplish each defined task/activity;

• Identification of the primary organization responsible for task execution (prime, sub, team member, by name, etc.);

• The completion criteria for each task/activity - a product, event or milestone that defines its completion.

The SOW will be expressed on a common WBS matching the cost volume and IMS section. The use of the government’s WBS is not mandatory.

Note: Program reporting tools should be the same tools used internally to manage the program. No additional unique information for the Government is desired.

C. Data Rights.

C.1. Government Data Rights. The Government has programmatic requirements for the continuing development, acquisition, modification, and sustainment of the system. To satisfy these requirements, the Government anticipates that it will need Unlimited or Government

Purpose Rights in delivered data. Data on battery packs and their associated control systems may be provided with Limited Rights. Offerors who propose to provide less rights in data than requested will be required to address how their data rights assertions will impact these programmatic requirements.

DISTRIBUTION STATEMENT A. Approved for public release: distribution is unlimited. 3 of 3