The SES Project Request System is designed to collect the appropriate business requirements so we can assess the business impact and complexity of requests. Because we don’t have the time and resources to do everything, we want to make sure we are using our resources wisely, getting the most payback from projects.
When do I need to submit a project request?
Anything that requires time from SES functional or technical personnel needs a project request including:
- New functions in SES
- Enhancements to existing SES functions
- New interfaces or changes to existing interfaces
- New reports or modifications to existing reports
- Putting queries on an automated schedule
These are items that DO NOT need a project request:
- Production fixes (things that aren’t working properly)
- Patches, regulatory updates, bundles, etc.
- Duplicate resolution
- Standard cyclical processing (e.g., term setup, standard financial aid setup and processing, tuition setup)
- Items that are in progress
- Items that do not require time from SES functional or technical personnel
For items that you are requesting for Fiscal Year 2017 (September 2016 – August 2017), we ask that you submit the projects requests by May 31st, 2016. Project requests will be accepted throughout the year, but priority will be given to requests submitted before the deadline.
How do I submit a project request?
If you are an SES administrative user (a staff member who logs into SES with an ID like ABCDE0), log into SES, select NU SES Project Request Form in your left-hand navigation, then follow the directions to add a project request.
How do projects get prioritized?
Projects will be evaluated and scored based on the following criteria:
- Necessary to avoid regulatory non-compliance for business
- Quality of service (e.g., improved University community experience, improved user satisfaction)
- Quality of decision making (data accuracy and reliability, reduced time to get access to information, self service)
- Improved student/staff/faculty/other University stakeholder effectiveness
- Impact of not doing the initiative
- Complexity and degree of customization required to implement the change
- Availability of appropriate enterprise system team(s) resources
- Resource and time commitment from proposing unit and executive sponsorship
- Ongoing maintenance required, both from a technical and functional user support standpoint
Breadth of Usage/Relative Priority of Requesting Unit
- Number of units that benefit from the change
- Number of users that benefit from the change
- University priority vs. unit priority
- Relative priority within requesting unit
Who can I contact for help?
Please contact Ann Dronen at email@example.com.