Enter the date the submitter intends to submit the completed Enhancement Request form in the Service Desk (SolarWinds) Ticket System. Click the field to enter a date. 

This date may be adjusted by the facilitator if it doesn't align to the actual submission date.  When drafting an enhancement request, this date can help others being asked for feedback to understand the date the request will be submitted.

This field is intended to record the primary Service Desk Ticket (SDT) that all activity for the submitted Enhancement Request (ER) would be tracked under.  This will become the field where the official Enhancement Request (Request Type) SDT will be listed. The person submitting the ER can enter the primary ticket they use as a reference for any issue reported and the WG facilitator will update it to the official SDT number for tracking.  All tickets related to a submitted Enhancement Request can be linked to that request within the Service Desk (SolarWinds).

Descriptive title to differentiate this from other similar requests.

Pillar and Module associated with this requested enhancement? Separate Pillar name and Module with a hyphen: Pillar-Module. Once the SBCTC Staff have had an opportunity to assess the enhancement(s) being requested, this may be updated if the request results in an impact across multiple pillars and or modules.  The person submitting the ER form need only provide their best understanding of the request upon submission.

To ensure any system request has the proper support to be considered by governance for action and expending of shared system resources, the Enhancement Request (ER) must go through specific channels to be considered for approval by governance bodies.

These organizations or individuals are referred to as "Sponsoring" the request and may initiate change requests; though they may not be the same as the individual submitting the ER form. 

On the ER form the submitter is required to specify which group/individual is sponsoring the request.The sponsor's contact information, as well as the contact information of the person who is completing the form (if different), is required in the next section.

• College President (or designee)
• Commission Chair (Indicate which commission)
• Data Governance Committee Co-Chair
• ctcLink College Collaboration Group Co-Chair

The sponsor's contact information, as well as the contact information of the person who is completing the form (if different) is required in this section. Please include:

• Name
• Title
• College
• Phone number(s)
• Email address

Choose as many stakeholder groups as apply to the description of the request, if known. While this information may be highlighted in the request description this section helps to elevate the stakeholder group impact visibility. 

This information will help the ctcLink Working Group better understand who is impacted by the change being requested.  The information also helps SBCTC teams in their communication approach during the solution design and implementation phases of a change.  

Check any box which applies and provide any necessary explanation in the request description:

☐ Student Self-Service in ctcLink ☐ Student Experience in HCX

☐ Student Experience in OAAP ☐ Faculty/Advisors Experience

☐ Employee Self-Service ☐ Manager Self-Service

☐ General Employee ☐ Administrative Staff (users)

☐ Other: (please detail)

Colleges are STRONGLY encouraged to discuss with other colleges to determine the breadth of system impact before submission. Check the box that applies.

☐ All Colleges ☐ Multiple Colleges: How many? ___ ☐ Just MY College

Please check ONE box,  and complete justification and reasoning behind the declared prioritization level.

☐ Critical – Critical system impact, severely degraded critical business processes, no workaround available.

☐ Urgent – Federal/state-mandated enhancement, degraded business process; workaround exists, but is unsustainable.

☐ High – Strongly desired enhancement. Impacts business process; workaround available, high college resource impact.

☐ Medium – Strongly desired enhancement. Impacted business process; viable workaround available, but not desired.

☐ Low– Desired enhancement, productivity improvement.

Provide a description of change being requested. Provide sufficient detail, including problem statement and whether the change impacts global or local configuration.

Describe the justification for selected prioritization level. Please ensure Enhancement Request Sponsor (i.e. commission, college President) supports the prioritization and justification.

Please provide background on why this enhancement request is being put forward. If the request started from an initial support request ticket, please provide details of the original issue reported that led to the eventual request for an enhancement to the system.

Please describe the impact if the enhancement request is not approved. This will help the governance group understand what will or will not happen if it declines to proceed with the enhancement request or delays addressing the request.

Please provide details about how the enhancement request was socialized and vetted. For example, the request went through college leadership channels to the College President, through the ctcLink College Collaboration Group and/or council and commission approvals or through federal/state mandate reviews and SBCTC ctcLink leadership.

If applicable, provide any additional Service Desk Ticket (SDT) reference numbers that will help others understand the complexity of the issues that are the business drivers for this request for a system enhancement.

Assessment of impacts that proceeding with this request will have on ctcLink (cross-module, cross-pillar) and any change implications with associated business processes based on analysis and discussion of SBCTC Customer Support, Application Services, Data Service, and PMO Teams.

Enter the estimation of effort for design, development, testing, training, and overall timeframe for delivery into Production.  

Detail the effort estimation to complete this enhancement, including each area of the work, for example, solution design, development, configuration, testing, training.