Ascend Project Timeline & Scope

The revised Ascend implementation timeline has a planned duration of 22 months, starting in September, 2021, and culminating with the go-live of the new system in July, 2023. An outline of the different phases, as well as explanation of key activities, are included below.

Ascend Timeline

 

Definitions of Terms

BPA (Business Process Analysis): The development of business process maps is iterative, and so each round is followed by Business Process Analysis sessions during which the maps are reviewed with user groups to ensure their accuracy and enhance the level of detail.

BPM (Business Process Mapping): The process of visually documenting future-state business processes in Visio maps, which show each step in relevant business processes, including Oracle Cloud steps, other system steps, offline steps, decision points, etc. Process maps also indicate the actors involved in a given business process. Ascend will contains three formal rounds of BPM.

CRP (Conference Room Pilot): CRP, or Conference Room Pilot testing, includes five cycles of iterative testing (4 completed previous and 1 upcoming), which are carried out by the project team to evaluate system configuration and business process maps. CRP testing also includes time to solution problems, reconfigure, and re-test.

Design Workshops: Refers to workshops carried out by the project team across both functional and technical workstreams. Functional workshops focus on business process and configuration decisions, involving team members from each specific area (e.g. Grants, Procurement, Receivables, etc.). Technical workshops address topics such as integration and conversions, involving individuals from the technical and functional teams.

SIT (Systems Integration Testing): During Systems Integration Testing (SIT), the project team will thoroughly test the integrations between different systems and ensure that all future-state business processes can be executed end-to-end successfully.

OST (Operations Simulation Testing): During Operations Simulation Testing (OST) the project team will fully test and vet future state production support capabilities and business processes to ensure a smooth system go-live.

UAT (User Acceptance Testing): User Acceptance Testing (UAT) is the final stage of testing. During this cycle, a broader group of UCLA employees who are future end users will test the system applications to ensure they understand how future functionality and business processes will be used to meet their local requirements and design specifications previously decided by running through a variety of business case test scenarios.

Scope

The Core Project Team is comprised of functional and technical teams, change management experts, and specialized workgroups engaged in planning, design, and testing of the new system, as well as groups focused on communicating to campus and creating training. The following business and technical areas have been identified as part of the Ascend Project scope. To learn more about the project, please see Who is Involved.

Functional Workstreams Technical Workstreams

Equipment Assets
Internal Billing
Planning & Budget
Reporting & Analytics
Application Security & Workflow
HCM/ERP Integrations
Data Clean-Up
General Ledger
Capital Projects
Receivables
Cash Management 
Procure-to-Pay (Procurement, Payables)
Expenses
Grant & Contract Management
Gifts and Endowments
Faculty Commitments

Middleware Integration Platform
App Development PaaS
Infrastructure/Environment Management
IDM
Integrations
Data Conversion
Security/Audit
Data Warehouse & BI