Body
The intent of this process is to ensure that all stakeholders are aware of the upcoming changes to Sierra Connect, and to mitigate any adverse impacts. This process also supports an overarching goal to communicate the changes that are made and document the when, where, and why of the request.
When an attribute and/or associated flag(s) are no longer useful they should be reviewed for modification or removal. It is recommended that each department review the functionality and usefulness of their Sierra Connect attributes and flags on an annual basis.
If it is found that modification is necessary, the end user should review and compile the needed changes and expected improved functionality. These changes should be presented at an upcoming Sierra Connect meeting, and if necessary, presented at an upcoming SS-ITS meeting to communicate the anticipated changes. Once modification is approved, a ticket should be submitted to ITS to modify the attribute and/or flag.
For removal from the system:
If it is found that removal is necessary, this request should be presented at an upcoming Sierra Connect Meeting, and if necessary, presented at an upcoming SS-ITS meeting to communicate the anticipated removal. Once removal is approved, a ticket should be submitted to ITS to have the attribute or flag removed from the system.
What happens once a ticket for modification or removal is submitted?
ITS will assign the ticket based on priority and available resources. If the request requires programming it should be expected that the minimum turnaround time would be 3 weeks to complete. If the request does not require programming, it could be completed in less than 3 weeks. However, it will depend on the priority and availability of resources.