A moratorium on enhancements to the AMS/SIS, Housing, Sigma/SAM, and associated applications from January 1, 2007 through the end of the Oracle/PeopleSoft Student Administration implementation project has been established.  (for reference see CSS-A001)  

The moratorium will help ensure that the current legacy applications remain static as the BG@100 project team configures the new business processes in PeopleSoft and eliminates the need to divert university staff from focusing on the Student Administration implementation.  

As per CSS-A001 a moratorium is in place for application development activities that are not approved by the BG@100 Executive Steering Committee.  This moratorium covers all ITS application development related to the AMS/SIS, Housing, SIgma/SAM, or associated applications.  

Exceptions to the moratorium need the review and approval of the BG@100 Executive Steering Committee.  The procedures described in the documentation provided below establishes the steps required to submit an exception request for ESC review.  The Action/Information Item template is also provided below for use in submitting an exception request.

• Moratorium Exception Procedures

• Moratorium Action Item Template - doc format
• Moratorium Action Item Template - pdf format
• 
  
• Moratorium Information Item Template - doc format
• Moratorium Information Item Template - pdf format
• 
  
• Moratorium Exception Tracking Spreadsheet - (last updated 8/8/08)

• BG@100 Action Items
• BG@100 Information Items

Systems Development Moratorium Exception Procedures

The BG@100 Executive Steering Committee approved Action Item CSS-A001 regarding a Moratorium on application development projects which runs until the end of the BG@100 Student Administration implementation project.  Action Item CSS-A001 included a provision for handling exceptions to the moratorium.  The procedures below describe the steps that should be taken to submit a moratorium exception request to the Executive Steering Committee.

1. A University department identifies a need for an application enhancement, application upgrade, or general program change (moratorium exception).
2. The department works with other individuals associated with the identified need to document it in one of the following formats.
   1.  If the exception is based on a regulator release, mandate, or application bug fix, the exception request will be documented in the form of an ESC Information Item.
   2. If the exception is not based on a regulator release, mandate, or application bug fix, the exception request will be documented in the form of an ESC Action Item
3. The documented moratorium exception request is submitted electronically to the Application Support Manager (John Konecny) for review and to provide additional documentation (time estimates, etc.).  The updated exception request is shared with the submitting department for review by that department prior to proceeding to Step 4.
4. The Application Support Manager places an entry for the exception request on the Moratorium Exception Tracking Spreadsheet.  The Moratorium Exception Tracking Spreadsheet will be published to the BG@100 web site monthly.  All exceptions submitted to the Application Support Manager will be recorded on the Moratorium Exception Tracking Spreadsheet including exceptions requests that do not get submitted to ESC.
5. The Application Support Manager forwards the exception request electronically to the BG@100 Project Director.
6. The BG@100 Project Director reviews the exception request and places it on the Executive Steering Committee Agenda.  The ESC meetings are scheduled the second and fourth Mondays of each month.  All agenda items must be submitted electronically with the agenda to the ESC members the Thursday prior to the scheduled ESC meeting.
7. The BG@100 Project Director notifies the department that submitted the exception request that the item has been placed on the ESC meeting agenda.  The department that submitted the exception request will provide the name of the individual that will present the item at the ESC meeting.
8. The designated individual attends the ESC meeting and presents the Information or Action Item to the committee.  The committee members will have an opportunity to ask questions and then will act on the item.  Information Items will either be accepted by the ESC or tabled for further research.  If an item is tabled, the presenter will be invited to the next meeting to finish the discussion on the item.
9. Once an Information or Action item has been acted upon by the ESC, the item will be published to the BG@100 web site and the BG@100 Project Director will notify the Applications Support Manger of the actions.
10. The Applications Support Manager will update the Moratorium Exception Tracking Spreadsheet.
    1. If the moratorium exception item was approved by the ESC to be worked on, the item will be assigned to the appropriate ITS resource and scheduled.  An ITS resource will contact the department that submitted the exception to notify them of the assignment and schedule the project to start.
    2. If the moratorium exception item is not approved by the ESC, the department that submitted the exception is notified by the Applications Support Manager.

 Back to Project Home Page