Colorado State University
Executive Summary
[Why are you interested in this program? Describe the campus need(s) to be addressed. Please format needs in story format as much as possible (e.g. I need to manage parent access to student info.) ]
Organization Description
CSU needs a more efficient and effective means of managing external identities. By participating in the campus success program, we hope to leverage many TIER tools and utilities, as well as expertise from the campus success program participants to make significant progress in that regard.
Organization Description
Colorado State University is a public research university located in Fort Collins, Colorado. The university is the state's land grant university, and the flagship university of the Colorado State University System.
CSU’s current enrollment is approximately 33,000 students, including resident and non-residents. The university consists of approximately 1,800 faculty in eight colleges and 63 academic departments. Bachelor's degrees are offered in 76 fields of study, with master's degrees in 57 fields. Colorado State confers doctoral degrees in 48 fields of study, in addition to a professional degree in veterinary medicine (28 total professional degrees).
In fiscal year 2016, CSU spent $332 million on research and development, ranking 47th in the nation overall, ergo our Carnegie classification as a Very High Research activity institution. Also in 2016, CSU set a fundraising record for a single campus in Colorado, raising $197.8 million.[Brief summary that should include demographics such as size, range and nature of academic programs, location of your university or college]
Containerized TIER Component(s) to be implemented
...
- Shibboleth IdP and SP
...
- Grouper Access Management Software
...
- COmanage Collaboration Management Platform
...
- Entity Registry, such as midPoint
Short Management-Level Use Case Description of Your Project
[Describe for upper management what problem you’re trying to solve. This should be written from a functional viewpoint and will used to describe your project on the web and in the wiki.]
Scope
A Colorado State University e-Identity (eID) has a limited lifecycle. An eID can be created when a person has an active affiliation with CSU. People applying for admission to the university, active students, faculty, staff and associates are all considered members of the CSU community and are eligible to create an eID, which includes issuance of a CSU-provided email address. When a person is no longer affiliated with the University, eIDs enter an expiration cycle where the identity is active for a limited time and will eventually be disabled.
More and more, people outside of the defined CSU member population need access to a limited set of protected resources via the network and/or web. We have identified three application development activities as part of our overall campus success program project (University Advancement, Parent Access and Access to Records for Former Students).
Scope
At the end of this project, the three development activities mentioned above will be integrated into COmanage, using social-SAML gateway services from Cirrus Identity and account linking functionality built into COmanage.[What will be the end result of the project? Describe what phases of work will be undertaken. It’s also important to mention what activities will not be included in this project.]
Key Stakeholders
Sponsor [ | name, title] Pat Burns, CIO and Dean of Libraries |
Campus Success Program Contact(s) | Scott Baily, Director, Academic Computing & Networking Srvcs. Scott.baily@colostate.edu, 970-491-4412 (office, direct) [name, title, contact information] |
Communications contact [name, title, contact information] | Katie Banghart, Communications Specialist |
Project manager | [name, title] Dave Hoffman, Senior Project Manager |
Project team members | Randy Miotke, Middleware Architect Jeff Ruch, Middleware Developer [name, title], [name, title], [name, title], [name, title] |
| Deployment Partners/Contractors | [name] |
Project Milestones
...
Activity | Assigned Resources | Start State | End Date | ||
Test Environment Setup and working | Randy/Jeff |
| |||
Synergistic Projects
9/15/2017 | |||
Setup COmanage V3 in Production | Greg Vogl | 10/9/2017 | 11/3/2017 |
Create New LDAP Infrastructure with Grouper and EDUPerson Directory data | Jeff Ruch & Randy Miotke | 11/6/2017 | 1/12/2018 |
Test COmanage Invitation process | Greg Vogl | 10/23/2017 | 10/27/2017 |
Test COmanage Matching Process | Greg Vogl | 10/23/2017 | 10/27/2017 |
Test COmanage Collaborative Organizations | Greg Vogl | 10/23/2017 | 10/27/2017 |
Document Services | Middleware Team | 12/1/2017 | 12/31/2017 |
Create COmanage Data Integration with HR and Student Systems | Greg Vogl & Jeff Ruch | 11/6/2017 | 11/17/2017 |
Go Live |
|
| 1/16/2018 |
Synergistic Projects
Research Data Storage Project depending on New LDAP Infrastructure and NIS Schema[Describe any synergistic projects that are currently underway]
Constraints, Assumptions, Risks and Dependencies
| Constraints | [Describe here potential factors that will impact the delivery of the project] | ||
| Assumptions | [Describe here conditions or situations that you are relying on in order to achieve project goals] | ||
| Resource Availability with other new projects and priorities | |||
| Assumptions | Containerized versions of Grouper and COmanage are straightforward to implement and maintain | ||
| Risks and Dependencies | Don’t meet target date of 1/16/2018. Next opportunity for Go Live is spring break Other competing projects take priority over this. | Risks and Dependencies | [What are the most significant risks? What things must happen before the project is delivered?] |