Independent Project Oversight Report (IPOR) Rating

7100-237 Document Management System (DMS)

The EDD has analyzed a variety of existing software solutions used for its existing imaging, data capture, electronic file submissions, document storage, and retrieval services infrastructure. The proposed vendor solutions must provide the capability to develop processes that are streamlined, scalable, and flexible for variable workloads. The solution features should support the deployment of new configurable, scalable, and robust software for imaging paper and electronic submissions as well as efficiently process defined business workflows. The DMS project will provide foundational capabilities necessary to support EDD modernization and GovOps Strike team recommendations.

Project Details

Agency / State Entity Labor and Workforce Development / Employment Development Department
Total Cost $106,171,267
Last Approved Start Date 06/17/2024
Last Approved Finish Date 06/30/2027
Criticality Rating Medium
IPOR Reporting Period Overall IPOR Rating
11/01/2025 - 11/30/2025
Yellow
Independent Project Oversight Dashboard

Key Questions

Is the project on track to satisfy the customer's business objectives?Yes

Is the project on track to achieve the objectives in the approved timeframe?Uncertain

Is the project on track to achieve the objectives within the approved budget?No

Project Overall Health Comments
Yellow
The overall project status is yellow for the following reasons: o The Project Team needs to prioritize prerequisite technical training to ensure the Knowledge Transfer sessions are effective. o The go-live date for R1 Data Migration and the go-live date for R2 Disability Insurance are only separated by one (1) business day creating a support risk. o Several critical project services are nearly out of budget or are currently exceeding budget while the project completion date is still over a year away. o The project schedule as several deficiencies, fails a key critical path test, and lacks dependencies between releases. o Schedule variances should be evaluated at the “milestone” level, and those variances that exceed the project team’s decision-making authority require a thorough analysis. o A resource leveling analysis is needed in response to increased release execution parallelism.
Focus Area/Rating Comments
Governance

yellow icon Yellow
o For governance decision-making, project schedule variances should be measured at key milestones, not at the project completion date, thus ensuring problems are not masked until late in the project when corrective actions are limited and more costly. o When a schedule variance against a key milestone exceeds the project team’s decision-making authority, then a comprehensive analysis should be conducted and documented to support the decision-making process.
Time Management

yellow icon Yellow
o Release 2 (UI) has a backlog of sixty-six (66) defects that need to be addressed, and this is before considering the defects that will be found in Release 2 testing activities such as End-to-End (E2E) testing and User Acceptance Testing (UAT). o Because the initial sprints for Release 3 (Tax) are focused on UI/DI instead of Tax, and the Tax scope is expected to increase by ~100%, the project may experience a go-live delay and cost increase. o The project schedule was analyzed using an industry standard assessment tool and found to have several deficiencies such dangling starts or finishes, excessive lags, high slack, and overuse of relationship types which impacts the integrity of the schedule. o The industry standard assessment tool includes two (2) critical path tests. The project team should ensure the schedule passes both tests to maintain schedule integrity and consistent milestone forecasting. o There are no dependencies between the DMS Releases meaning the development and testing efforts for each Release can run in parallel, which creates a risk of resource contention which could delay the project schedule and/or increase project cost.
Cost & Contract Management

yellow icon Yellow
o The Project Team should reconcile the funding for IV&V services that has a current spend of 106% of budget while the project completion date is still over a year away. o The Project Team should also reconcile the funding for Project Management, Project Advisor, and Project Executive services that are nearly out of funds. o Per the November 2025 Project Status Report (PSR), the DMS project is underspending, partly due to the yet-to-be invoiced Release 1 Software Package.
Scope Management

green icon Green
o Change Request (CR) #3 will extend the discovery period for Tax and Remittance, include new or modified UI/DI/PFL forms, and move the production rollout of the PFL forms from Release 2 to Release 3. o CR#3 was approved on December 4, 2025 and is expected to require a contract amendment to account for the increased cost.
Resources

yellow icon Yellow
o Due to the increased level of parallel execution between the Releases, the Project Team should conduct a resource leveling analysis to ensure that both state resources and vendor availability align with the planned schedule activities. o The PM vendor is actively recruiting for a permanent, dedicated DMS scheduler. A dedicated scheduler can maintain the integrity of the schedule in real-time and ensure information is current for informed decision making.
Quality

yellow icon Yellow
o The Release 1 Data Migration Go-Live and the Release 2 DI Go-Live are only one (1) business day apart which could create support challenges for the Project Team. o The Project Team should conduct Release 1 E2E and UAT testing at scale to ensure system performance is not impacted by the addition of millions of documents into the production system. o Conflicting defect status definitions is causing communication misunderstandings and inaccurate sprint status reporting.
Risk And Issues

green icon Green
o The project team appears to be following the processes outlined in the Risk and Issue Management plan.
Transition Readiness

yellow icon Yellow
o The Release 1 acceptance period ended on October 27, 2025, and the State did not accept the release due to outstanding OCR accuracy, performance, and requirement issues. After the SI vendor addressed the issues, the State accepted Release 1 on December 3, 2025. o The Project Team needs to prioritize prerequisite technical training to increase the effectiveness of the Knowledge Transfer (KT) sessions to ensure the State is capable of maintaining the new system once the SI vendor leaves the project.
Conditions For Approval

green icon Green
All conditions for PAL Stage Gate approvals have been met.
Corrective Action

green icon Green
Comments about Corrective Action Plan Items • N/A
Project Approval Documents
Website Accessibility Certification

20250626 Release-16