3. Maintenance Policies and Procedures › 3.2 User Maintenance Procedures › 3.2.2 User Change Control Procedure › 3.2.2.2 Authorization

3.2.2.2 Authorization

It is the responsibility of the user to integrate changes
into CA MICS. This applies to vendor-supplied maintenance and
user-generated modifications.

The final responsibility at most CA MICS installations for
authorizing the production implementation of CA MICS changes
rests with the CA MICS System Administrator, or some member
of the organization's management staff at an even higher
level.

Before arranging such authorization, you should ascertain
that:

    - The changes will not affect the operation of CA MICS,
      except in the documented way.

    - The changes will not affect the content of CA MICS
      data, except in the documented way.

    - The changes will not increase the dependence of your
      site on a particular CA MICS or operating system
      release to a level that you think is unreasonable.

The integrity of the CA MICS database is the prime
consideration.  That, after all, is a major reason behind the
acquisition of the product.  The criticality of the
integrity of data in the CA MICS database is self-evident,
especially if the CA MICS data is used in chargeback
applications.  Lost data can mean lost revenue.

The CA MICS Product Support Group is available to present
objective arguments you may use in formulating the decision
to implement or not implement a change.  Any negative
response from the CA MICS Product Support Group should be
considered carefully.