How the work and owners are grouped
Source: Module Map and Name Crosswalk, draft v8, Confluence title “SUNY NCSIM Product Requirements.” Edited October 4, 2026 by Anthony Cala; exported October 25. Not reviewed or approved by SUNY. All four pages read; table layout checked. No annotations or attachments.
Names that refer to the same work
Pages 1–2 describe a hierarchy of pod, Jira epic, then FRD feature/story. Names vary between the plan, Jira and FRD. The table preserves that mapping rather than claiming a renamed or approved structure.
| Pod | Epic | FRD module | Plan scaffold row | July 15 plan item | RFP area |
|---|---|---|---|---|---|
| 1 Catalog & Discovery | SUNY-85 Instructional Activities Catalog / Master Non-Credit Activity Index | MOD-CAT Catalog & Discovery | R74, R1.2.1.4.1 | 01 | 2 |
| 2 Reporting & Analytics / Feedback & Survey | SUNY-93 Reporting & Analytics | MOD-RPT | R89, R1.2.1.5.1 | 09 | 10 |
| 2 | SUNY-91 Feedback & Survey | MOD-FBK | R102, R1.2.1.5.2 | 06 | 8 |
| 3 Communication & Engagement / Support Services | SUNY-90 Communication & Engagement | MOD-COM | R117, R1.2.1.6.1 | 07 | 7 |
| 3 | SUNY-92 Support | MOD-SUP Support Services | R130, R1.2.1.6.2 | 08 | 9 |
| 4 Enrollment & Registration / Profile Creation | SUNY-86 Registration & Enrollment | MOD-ENR Enrollment & Registration | R145, R1.2.1.7.1 | 02 | 3 |
| 4 | SUNY-84 Profile Creation | MOD-PRF Profile, Identity & Access Management | R158, R1.2.1.7.2 | 10 | 1 |
| 5 Credential Management / Learner Center Portal | SUNY-89 Credential Management | MOD-CRD | R173, R1.2.1.8.1 | 04 | 6 |
| 5 | SUNY-88 Learner Center | MOD-LCP Learner Center Portal | R187, R1.2.1.8.2 | 05 | 5 |
| 6 Finance & Billing | SUNY-87 Finance, Billing, & Fee Management | MOD-FIN Finance & Billing | R202, R1.2.1.9.1 | 03 | 4 |
The Running Task List has no catalog pod row. Its Pod 2 feedback row says “Feedback & Support,” while the map groups support in Pod 3. Other rows repeat “see notes” without explaining all differences here. Jira labels use the relevant pod name plus the short module label, such as mod-cat. These inconsistencies are navigation concerns, not evidence of missing product capability.
Who can help resolve a question, page 3
| Responsibility | Named person/status |
|---|---|
| FRD owner / PruTech lead BA | Alan Meng |
| Solution architect | Deepak Saini |
| Lead architect | Unconfirmed; Anthony Cala is described as oversight architect |
| Technical lead | Heena Karir |
| Pod leads | Unconfirmed |
| PruTech BAs | Sara Lim, Syed Khan (also configuration), Deepak Raj Gokul Das |
| Cross-functional analyst | Sai Sudeshna |
| SUNY BA | Anuraag Sharma |
| SUNY product owner | Name unconfirmed |
| Developers | Ownership unconfirmed; junior developers listed as Chirag Singh, Sakshi Bhuyar, Vishnu Zanwar |
| Integration | Raghavender Reddy |
| Data 360 | Phil Rymek, Salesforce professional services |
| Oracle | Anthony Pierro, as needed |
| Quality assurance | Khadija AQ |
| PruTech project manager | Virginia O'Brien |
| SUNY project manager | Katie Kirsch |
| PruTech engagement manager | Jennifer Shirah |
| Salesforce engagement manager | Bennett Donovan |
These are source-listed roles, not independently confirmed current assignments. In particular, the file does not settle who approves a design for SUNY.
Other records named, pages 3–4
The page lists pod/epic pages, persona/glossary pages, finance integration questions, a project/Salesforce dictionary and a requirements traceability matrix. Data-model pages cover people, organizations, calendar, catalog, programs, enrollment/results, credentials, inquiries/applications, support/cases and Data 360/reporting, plus a well-architected mapping. Their names and placeholders are present; their full contents are not supplied by this export.
Related topics: cross-source findings.