Suggested Resource Estimates for SPARC Implementation

Installing and Maintaining SPARCRequest at Your Institution

These estimates are based on the following assumptions:

Start-up period lasts 1 month
Initial load includes 1 to 2 programs/cores (dependent upon number of service providers and development of workflows)
% effort is based on a 40 hour work week
The chart does not factor in the task of gathering requirements or standing up the initial hardware, because of the wide variance in complexity and technology across institutions

Role	Main Duties	Start-up (Month 1-2)	Go Live/ Start-up (Month 3 - 6)	Ongoing Maintenance

Role	Main Duties	Start-up (Month 1-2)	Go Live/ Start-up (Month 3 - 6)	Ongoing Maintenance
Project Manager/ Product Owner	● Set priorities ● Track & report progress ● Identify Risk(s) ● Attend Open Source consortium meetings ● Meet with stakeholders and report progress to leadership ● Workflow development & assistance	30 – 45 %	20 – 30 %	5 – 10 %
Coordinator/Trainer	● Coordinates effort between programs/cores, helpdesk and development ● User and Admin Training ● Workflow development ● Scheduling meetings and training ● Implementation and milestone tracking	20 – 30 %	40 - 50 %	5 – 10 %
Analyst	● Communicates with development team ● Legacy data and catalog build ● Workflow development ● Assist with training	60 - 80 %	20 – 30 %	5 – 10 %
Help Desk	● Provide level 1 and level 2 support ● First point of contact for user questions	0 - 5 %	25 – 35 %	10 – 15 %
Installer/ Programmer/ Developer	● Installs and configures the application	80 - 100 %	20 – 30 %	10 - 20 %*

*This estimate is based on a mid to high level developer

*On-going maintenance is based on providing basic tasks such as user maintenance and changing configuration settings. If additional programming is required this effort will need to be increased.