You should be re-directed to another page momentarily. If not, please visit site://ACAD-BUFIN-it.miami.edu/about-umit/projects-and-implementations/adrs/index.

Decommissioning Process Phases

0. Request

Initially, UMIT will request information pertaining to the data located within the mainframe environment.

1. Discover, Analyze, and Recommend

In this phase, UMIT will work together with central offices/data custodians to determine what archival data needs to be retained. Additionally, central offices will recommend reporting formats to facilitate access to archival data post decommissioning. Consideration first will be given to all existing reporting formats to determine adequacy for post decommissioning relevance. New reporting formats will only be considered if nothing suitable exists. 

Steps in this phase:

  • Gather reporting requirements
  • Assess pre-existing reports
  • Determine gap between what is needed and what exists
  • if an additional reporting format is needed specify needs
  • Assess feasibility of producing reports (is this a complex and time consuming task)
  • Assess business case for developing reports (is there a compelling need)
  • Recommend development of feasible, business needed reports

2. Design, Develop, and Integrate

UMIT will isolate all pre-existing reports that have been identified as required for retention. These reports will be imbedded with appropriate indexing to allow for authorization (granting access) and searching.  Pre-exisitng reports will be stored in appropriate repositories, integrating them into existing data.

UMIT, with continued interaction from central offices, will design reporting formats that meet requirements from the previous phase.  Once designed, UMIT will develop the reports and imbed the necessary indexing to allow for authorization (granting access) and searching.  Newly designed reports will be stored in appropriate repositories.

Steps in this phase:

  • Detail design: what is requested?
  • Development (acquisition and/or build): how to produce?
  • Configuration: what technologies to use?
  • Customization: how to present the data?
  • Interfaces: how to acquire the data?
  • Data conversion: how to get data in the right format?
  • Functional testing: can it be done?

3. Testing and Quality Insurance

Test to ensure it meets:

  • Requirements provided in design
  • Usability needs, i.e. can it be accessed
  • Load capacities, to support all those likely to request
  • Accuracy requirements
  • Security
  • Retention standards

4. Deploy and Maintain

Ensure processes are in place to:

  • Grant access
  • Train users
  • Ensure backup

5. Evaluate

Review overall:

  • Performance
  • Assess gaps

6. Archive and Retire

Closure of:

  • Decommission all application software
  • Archive all appropriate data
  • Decommission mainframe and all associated hardware and services
  • Disconnect and dispose of all equipment
  • Destroy all operational tapes and disks