Exhibit_01_-_Proposal_Requirements.pdf

EXHIBIT 1 – PROPOSAL REQUIREMENTS

1. General

a. Written proposals submitted in response to this request for proposals (RFP) shall not exceed 35 pages (excluding attachments).

b. Statement of understanding of the scope of work as outlined in Attachment A of this RFP.

c. At a minimum, submitted proposals must include the tasks outlined in Attachment A.

Proposals must also detail a comprehensive transition plan to transfer all intellectual property—including source code, design documents, APIs, and technical documentation—to the state upon contract completion.

d. Provide a description of the proposed technical architecture, emphasizing modularity, scalability (e.g., microservices, containerization), and secure API integrations.

e. Work plan and schedule to complete the project scope of work identifying milestones and deliverables.

2. Project Team

a. An organizational chart showing the firm’s approach towards the staffing and management of the project shall be provided. Titles, roles, and the number of staff required to fill those roles should be shown on the chart. The proposed relationships between staff should be shown as well.

b. A staffing plan identifying the approximate number, expertise, and experience level of staff by role and responsibility based on anticipated work.

i. Resumes:

1. List of the personnel on the project team, including a summary of their qualifications and work experience (resumes may be included as an attachment).

2. Resumes should include persons’ active professional registrations and registration number, including expiration date. This includes any sub-consultants proposed for use.

ii. Team Experience:

1. This segment should highlight or expand upon project experience.

Elaborate on the proposed team’s previous work as a team with other key staff and proposers listed.

2. Describe staffing capability, workload, and record of meeting schedules on similar projects. Also describe ability to adapt to unexpected work.

3. Finally, describe the feasibility of oversight, ability, and willingness to respond to OWC requirements for this procurement.

3. Example Projects

A representative list of similar projects completed within the last five years including:

Contracting firm Contracting firm project manager Contracting firm contact information Contract amount Date of contract

EXHIBIT 1 – PROPOSAL REQUIREMENTS

Date of completion Consultant project manager and contact information Project description

4. Additional Information

a. Proposer should explain its approach and strategy for successfully completing similar projects. The project approach should be sufficient in detail to demonstrate the proposer’s understanding of the project, its unique challenges, and the processes and procedures that must be followed. The proposer should identify the most critical steps in the successful completion of similar projects.

b. Proposer should describe its tools, procedures, and techniques used to keep projects within budget and schedule.

c. Proposer should provide a summary of experience.

d. Proposer should explain why their team should be selected and include any other information they feel is relevant.

e. In addition, the proposal should describe adherence to industry standards (e.g., IEEE

1016, TOGAF, NIST SP 800-53/ISO 27001, OpenAPI, WCAG 2.1, DAMA-DMBOK) and outline the agile/DevOps practices (e.g., continuous integration, automated testing) that will be employed.

5. Abbreviated Design Review Process:

Throughout the 12-month period of performance, the contractor shall conduct incremental design reviews to baseline decisions and track progress. These reviews shall include a Requirements Review, a Preliminary Design Review, a Critical Design Review, and a Final Design Review. The proposal must outline the schedule, deliverables, and documentation process associated with these reviews.

6. Schedule/Timeline An estimated project schedule is provided in Exhibit 3. Proposals must include milestones that align with the provided schedule and clearly indicate the timeline for key deliverables, including the final handoff of intellectual property.