Knowledge Base 6418:Planning your first 90 days as the new Remedy administrator
Adopting a new role and supporting new applications can be a challenging experience, especially whenthere are unknowns about how and why things work as they do. The new administrator is justifiablyconservative, afraid to make changes for fear of what it may break, and mostly reacting to problems asthey appear. In contrast, the experienced Remedy administrator, if properly prepared, can be a sageagent of change within your organization, recommending, evaluating, and championing improvements inyour system to reflect your evolving business needs. There is no single right path for going from one tothe other, but a frequent element in the successful journey is a bit of up front planning, evaluating whatroles will be required of the Remedy administrator and how best to facilitate them. A further reward of this exercise is that its outputs also facilitate training for your backup administrator, or transitioning theresponsibilities to your replacement when you move on.The paragraphs below discuss some ideas that you may want to consider in your development plan, andreferences additional resources, which may be helpful.The good news is that being an AR System administrator is similar in practice to being administrator of other applications. The same traits which make a successful administrator are applicable: being thoroughwhen investigating changes, being responsive to problems reported, deploying changes in an orderlyfashion, following a plan of preventative maintenance, and preparing for disaster recovery.
Define your current environment
A good first step in assessing your needs is to define your present environment. This step may not benecessary if you have been involved from the beginning, but in most cases it's good to come up to speedon developments previous to your involvement. This may include putting together a summary sheet of application and product versions, collecting any requirements definitions, design docs or logs maintainedeither by your predecessor and/or consultants. Also gather product manuals, media, internaldocumentation, and training materials.These are very tangible components and specific details. Another aspect of defining your currentenvironment involves understanding the role of these applications within your organization, what needsthey fulfill, what constituencies they serve, and how these will grow and change over time. Whatfeatures or roles of the application are areas of upcoming development? When evaluating your currentenvironment, try to get a grasp of both the size and shape of the application and administrative role, aswell as a feel for its progression within your organization.
Define your roles and needs to fulfill them
The next step of the evaluation should investigate your needs to successfully perform your administrativeduties. Below are some common administrator responsibilities.- Application configuration such as adding categories, groups, etc- Preventative maintenance, such as performance tuning, archiving- Addressing reported problems by users- Investigating and implementing application customization (in some cases)- Deploying application changes or upgrades- Backup/restore processThis needs assessment step is an important part of preparation, and should be based upon your role andcurrent environment as discovered earlier rather than a generic list, but below are some suggestions tostart with: