1. Common Application Inventory
ServiceNow CMDB
Common Application Inventory

2. New Opportunity – maybe
Remember the System-wide Application Inventory (SWAI)?
Might get to revisit this and improve on it ….
Use ITAC members this time
Use ServiceNow CMDB to house the data
Preparing a ‘proposal’ for ITLC and COO
Potential benefits
SWAG estimate

3. Benefits: Shared Service candidate identification
Supports Application Portfolio Management (local & system wide)
Supports procurement
Retirement/decommissioning planning
New/replacement system planning (roadmaps)
Supports Business Architecture (later phase)
System wide insights
Common definition/classification

4. One time set up:
Develop Solution Architecture, feasibility, prototype work
1 architect resource from 5 campuses, each 20 hours over two calendar months (100)
Design common lexicon, taxonomy, etc. to describe applications
Design common Application CI (physical schema in the SN CMDB) to implement canonical form  
2 architect resources from 5 campuses, each 10 hours over two calendar months (100)
2 ServiceNow admin resources, each 10 hours over two calendar months (20) 
Implement the common “Application CI” in each CMDB
1 ServiceNow admin resource, each campus, each 20 hours (300)

5. One time set up (continued):
Design export, transport and import of Application CIs for consolidated reporting
2 ServiceNow admin resources, each 20 hours over two calendar months (40) 
Requirements confirmation, Report design, CIO interviews
1 System wide Collaboration SME, 40 hours over two calendar months (40)
CIOs, SMEs, App managers/providers, each 1 hour over two calendar months (40)
Set up hours ~750?

6. Recurring tasks:
Investigate and document applications e.g. talk with CIO, talk with app manger/provider
1 architect resource from each campus, each application documented ~3 hours (3x#ofApps)
CIOs, SMEs, App managers/providers, each (app) 1 hour over (1#ofApps)
Hundreds of apps exist at each campus.
I’d venture a guess that it would be hard to find/document 100 important/expensive/intensive (mission critical) applications.
Smaller apps still need to be documented, but we can take our time with that (as-needed).
10 apps a week is ~ apps in two months.
I doubt we’ll get that type of focus as most campus architects have a day job.
~ apps in 4-6 months might be more realistic

7. Software licensing:
Each campus has some form of ServiceNow instance (department or campus wide) at their disposal (maybe not UCR?).
Additional costs for software/licensing would be small

8. ServiceNow expertise/development:
We might not have SN developers at each campus
so we may have to “rent” them or
utilize a set of local SMEs on other campus implementations (might not involve travel as SN is cloud based)