Affirmed Name - Project1: Technology & Data Readiness

20%

Status

In Process [In Process]

20% complete, updated on Thu 3/5/26 1:43 PM by Gloria Walden Johnson

Changed Percent Complete from 16% to 20%.
Changed Health from Yellow - At risk with corrective actions to Green - On track.
Project Plan modified based on the Program Initiative and Project Governance Sequencing.

Details

Dates
Fri 1/3/25 - Tue 6/30/26
Acct/Dept
Division of Information Technology
Service
Project and Change Management Office / Information Technology Project Request
Type
Strategic Projects / Division of IT Project
Health
Green - On track
Portfolio(s)
Classification
Large Project (>230 Hours)
Requirements
PROJECT 1 REQUIREMENTS
These are the functional and governance requirements necessary to declare readiness.
Functional Requirements:
- The project must produce a validated enterprise inventory of all systems interacting with name data.
- The project must document integration flow between systems of record and downstream systems.
- The project must identify all name override capabilities.
- The project must document legal-name-only constraints.
- The project must assess synchronization between SIS, CHRS, and identity systems.
- The project must document CO-dependent technical constraints.
Documentation Requirements
- CMDB name-source fields must be populated and validated.
- Risk and issue logs must be maintained.
- Readiness artifacts must be stored in the official repository.
- The executive sponsor must formally acknowledge the readiness gate criteria.
Created
Mon 8/14/23 4:44 PM
Modified
Thu 3/5/26 1:43 PM

Change Impact

How will you measure the impact of this project?
What are some metrics or KPIs that will be used to measure success? Think about the five metrics to measure: quality, quantity, timeliness, cost, and customer satisfaction.
1. Measure Completion of Readiness Coverage
2. Measure Risk Identification & Mitigation Readiness
3. Measure Dependency Control
4. Governance & Decision Readiness
What are the consequences of not doing this project?
For example: direct significant negative consequences to the University, unable to conduct basic services; failure to resolve customer complaints or requests; loss of opportunity for improved service delivery or efficiency. Please explain.
If Project 1 (Technology & Data Readiness) is not completed, the campus will NOT “save time,” and shifts risk forward into implementation, where the cost, disruption, and exposure are significantly higher.
How many employees will be impacted by this change?
Select the size of the employee population that will be impacted by this request.
Hundreds
How many students will be impacted by this change?
Select the size of the student population that will be impacted by this request.
Dozens

Project Costs

Funding Status
Funding is not necessary

Project Details

Project Champion
Person who voluntarily takes special interest in the adoption, implementation, and success of the project. They will help enforce the project solution with internal resources and promote it across campus.
Divisional VP Support
Does your divisional VP support this request?
Yes
What would a successful solution look like?
What outcome will you have at the conclusion of this project? If this proposal is one of a multi-phase project, please explain your plans, goals, and timelines for subsequent phases.
We have complete visibility into where name data resides, how it flows, where it can be overridden, and what risks exist. Governance is defined, dependencies are tracked, and the campus is positioned to implement immediately upon receipt of the Chancellor’s Office guidance.
Department Head Support
Did you discuss this request with your department head and receive approval for submission?
Yes
Department Head Name
Select the staff member that approved this project request.
Executive Sponsor Support
Do you have the support of your Executive sponsor who will be funding the project?
Yes
Executive Sponsor Division
The executive sponsor's campus division. Campuswide is used for projects that have multiple executive sponsors or are initiated by cabinet.
Campuswide
Project Purpose
What organizational need are you looking to address?
Project 1 establishes enterprise-wide technology and data readiness in preparation for AB 760 implementation.

Its purpose is to ensure that all systems, integrations, governance structures, and risks related to name data are fully documented, validated, and controlled prior to configuration or policy activation.
If this request is mandated, please provide details about what's driving the mandate.
If you selected Chancellor's Office, legal or collective bargaining requirement, please provide details about the policy, law or executive memorandum that’s driving the mandate.
2 CCR § 11034(h)

(h) Recording of Gender and Name. As provided in sections 11016(b)(1) and 11032(b)(2) of these regulations, inquiries that directly or indirectly identify an individual on the basis of sex, including gender, gender identity, or gender expression, are unlawful unless the employer establishes a permissible defense (section 11010). For recordkeeping purposes in accordance with section 11013(b), an employer may request an applicant to provide this information solely on a voluntary basis.

(1) An applicant's designation on an application form of a gender that is inconsistent with the applicant's assigned sex at birth or presumed gender may be considered fraudulent or a misrepresentation for the purpose of an adverse employment action based on the applicant's designation only if the employer establishes a permissible defense (section 11010).

(2) An employer shall not discriminate against an applicant based on the applicant's failure to designate male or female on an application form.

(3) If an employee requests to be identified with a preferred gender, name, and/or pronoun, including gender-neutral pronouns, an employer or other covered entity who fails to abide by the employee's stated preference may be liable under the Act, except as noted in subsection (4) below.

(4) An employer is permitted to use an employee's gender or legal name as indicated in a government-issued identification document only if it is necessary to meet a legally-mandated obligation, but otherwise must identify the employee in accordance with the employee's gender identity and preferred name.
Success Criteria/Requirements
What constitutes project success (e.g. requirements, key goals, features, functions, capabilities, etc.)?
Enterprise System Visibility Achieved
✔ 100% of systems that store, display, or consume name data are identified
✔ All integrations involving name data are mapped
✔ No undocumented shadow systems remain

System-of-Record Authority Confirmed
✔ SIS confirmed as authoritative source for student legal/affirmed name
✔ HR/CHRS confirmed as authoritative source for employee legal name
✔ Integration flow validated
✔ No conflicting authoritative sources exist

Override Points Identified & Documented
✔ All systems allowing name override identified
✔ Override risk level assessed
✔ Remediation strategy defined for Project 2

Legal & Regulatory Constraints Identified
✔ Systems requiring legal name documented (e.g., Health Center, CSE)
✔ FERPA implications reviewed
✔ HIPAA considerations assessed (if applicable)
CO Dependencies Documented & Tracked
✔ Delivered PeopleSoft code dependency logged
✔ ERS file constraints documented
✔ CHRS synchronization limitations identified
✔ HR policy dependency tracked

Governance & Decision Framework Established
✔ RACI finalized
✔ Escalation path documented
✔ Readiness-to-Implementation gate defined
✔ Sponsor alignment confirmed

Defined transition criteria such as:
- All systems inventoried
- All risks categorized
- All override points documented
- All CO dependencies tracked
- Executive sponsor approval
- Success = Controlled transition into Project 2.
Project Urgency
Indicate if there is a mandate or requirement driving this request.
Mandated by Federal Law, State Law, or Executive Order
Hard Deadline
If there is a hard deadline, please indicate the date below.
05/31/2025
Deadline Reason
Describe the business requirement or reason for the project deadline.
The campus needs to get compliant with this regulation as soon as possible.

Project Resources & Effort

What resources will this project require?
Identify the department and/or individuals that might need to work on this project and the estimated number of hours required for each individual.
PCMO, HR, EAPP, ISEC, IRSA, and ITSS, Registrars, Faculty, HR
DoIT Departments Involved
Any Division of IT departments that will be involved in this project.
EAPP (Enterprise Applications)
IRSA (Institutional Research and Strategic Analytics)
ISEC (Information Security)
ITSS (Information Technology Support Services)
PCMO (Project and Change Management Office)
Complexity of Implementation
What is the complexity of the project?
Moderate (multiple interfaces/impacts/dependencies)
What is the solution type?
The solution type translates to the level of impact on IT staffing and technology maintenance. Based on consultation with your IT representative, pick the best fit for your proposed solution.
New features in an existing system, moderate breadth/depth

Description

Program Name:
Affirmed Name (AB 760) Readiness & Implementation Program

The Affirmed Name (AB 760) Readiness & Implementation Program establishes a sequenced, governance-driven approach to achieving CSU-aligned compliance with AB 760. The Program separates readiness activities from implementation to reduce institutional risk and prevent premature system configuration before the Chancellor’s Office guidance.

The Program consists of two formally structured projects:
- Project 1 – Technology & Data Readiness
- Project 2 – AB 760 Policy Implementation

Project 1 focuses on enterprise technology and data readiness in preparation for the implementation of AB 760. This phase is actionable prior to the Chancellor’s Office policy finalization and delivered system updates.

Scope includes:

- Enterprise system and integration inventory
- Validation of Student (SIS) and HR (HRIS/CHRS) systems of record
- Identification of legal-name usage constraints and exceptions
- Documentation of downstream system impacts
- CMDB name-source alignment and cataloging
- Technical gap, risk, and dependency documentation
- Development of readiness artifacts and implementation gating criteria

Organizational Risks

  1. High Impact On Other Projects

    CHRS - although it has wrapped up

  2. Medium Learning Curves

    New process to update names

Systems Affected

  1. CSU, Learn

    Academic & Instructional Systems

    - Name display appears in classes, rosters, communications, and faculty workflows.
    - Canvas (listed again due to dual student/faculty impact)
    - Kaltura
    - Turnitin
    - Lab Management Systems
    - Tutoring / Advising Platforms (EAB Navigate, etc.)
    - Proctoring Systems
    - Classroom Tech Systems (Name-based login or roster syncs)

  2. Other

    Student-Facing Systems (Name Display or Self-Service)

    These systems often allow users to view or update personal information.

    - Tassel / Marching Order (Commencement)
    - VZO (Preferred Name Override System)
    - Student Center / Portal
    - Canvas (LMS)
    - Library Systems (Alma / Primo)
    -Housing StarRez
    - Wildcat ID Card System
    - Account Center / Password Tools
    - Handshake (Career Center)
    - International Programs Systems (SEVIS-linked processes)
    - Health Center EMR • Point and Click (PnC)
    - Counseling Center Systems
    - Orientation & Student Life systems (various vendor apps)

  3. PeopleSoft CS

    - Student Records
    - Admissions
    - Financial Aid
    - Student Financials
    - Academic Advising
    - Graduation / Degree Audit
    - Enrollment & Registration
    - CS 360 Modifications (local Chico mods)

  4. PeopleSoft HR

    - Employee Self Service
    - Workforce Administration
    - Payroll
    - Benefits
    - Position Data
    (CHRS>CS one-way sync noted in discovery)

    Employee-Facing or HR-Related Systems
    - Includes systems used by HR, payroll, and supervisors.
    - CHRS / PeopleSoft HR (primary)
    - PageUp (Recruitment & onboarding)
    - CHRS Recruiting
    - Time & Labor Systems
    - Payroll Systems
    - Campus Paperless Hiring Tools
    - Background Check Vendor Systems
    - Docusign workflows with employee/employment data
    - Parking Services Portal
    - Travel & Expense Systems (Concur, if applicable)

  5. RDS

    Data Warehouse & Reporting
    - CSU Data Warehouse
    - Chico State Data Warehouse
    - Cognos Reports
    - Insight Reports
    - RDS (Real-time Data Store)
    - ERS Reporting (Enrollment Reporting System) *
    (This one is a confirmed pain point due to special characters.)

  6. SSO

    Identity & Access Management - Systems pull names from these directories during authentication.
    - Azure AD / Active Directory
    - Shibboleth / SSO
    - LDAP

Alternate Manager(s)

Sponsor

Stakeholders (14)

AR
Aldine Ruble
Responsible, Consulted, Informed
Data Warehouse
Reporting & Downstream
Fri 2/27/26 4:35 PM
CN
Charlene Neal
Assistant Registrar
Responsible, Consulted
Consulted, informed.
Thu 4/24/25 11:05 AM
CW
Chris Witthans
Information Security Officer
Responsible, Consulted, Informed
Technology Workstream Lead - ISEC
Fri 2/27/26 4:34 PM
Gloria Walden Johnson
Gloria Walden Johnson
Responsible
Program Manager
Project Manager
Fri 2/27/26 4:23 PM
GC
Greg Coates
Analyst/Programmer
Responsible, Consulted, Informed
Account Center
Fri 2/27/26 4:33 PM
Jim Nelson
Jim Nelson
Chico State
Responsible, Consulted, Informed
CMDB & Integrations
Fri 2/27/26 4:32 PM
MS
Monique Sendze
Accountable
Executive Sponsor
Fri 2/27/26 4:25 PM
RC
Rebecca Campbell
Consulted, Informed
System Steward / Operations
Fri 2/27/26 4:28 PM
RC
Rich Carrillo
Consulted, Informed
System Steward / Operations
Fri 2/27/26 4:27 PM
RM
Ron Morris
Responsible, Consulted, Informed
Employee records (student & staff)
Local systems that store names
Customer- or student-facing interactions
Documents or rosters where affirmed names must appear
Compliance responsibilities
Mon 12/1/25 1:07 PM
Scott Kodai
Scott Kodai
Senior Director, Enterprise Applications
Responsible, Consulted, Informed
Technology Workstream Lead (EAPP)
Fri 2/27/26 4:31 PM
SW
Sheryl Woodward
Consulted, Informed
HR System Authority
Fri 2/27/26 4:19 PM
TF
Tony Fierro
Responsible, Consulted, Informed
PeopleSoft Technical Lead
Fri 2/27/26 4:30 PM
TD
Tricia Douthit
Responsible, Consulted, Informed
Technology Workstream Lead - IRSA
Fri 2/27/26 4:34 PM