From: music@reg.triumf.ca (FRED W. BACH)
Subject: What should a System Manager Do ?
News-Software: VAX/VMS VNEWS 1.41    
Keywords: System manager
Organization: TRIUMF: Tri-University Meson Facility
Date: Tue, 14 Apr 1992 02:41:00 GMT

  Recently there was a thread in one of these DEC-related newsgroups, as
 I recall, about what a system manager does.  I have some general principles
 I would like to put out for discussion to this newsgroup.

   What a System Manager *SHOULD* do (not necessarily in the right order):
   ---------------------------------

      Treat your help well

      Keep good records (purchases, maintenance, payments, new/old users)

      Insure integrity of Existing Data

      Insure integrity of Existing Hardware and Software
       (the above two items would also include providing Security
        against malicious loss of Existing Data or Hardware or Software)

      Provide user access to Existing Data as applicable.

      Provide users means of viewing, massaging, outputting and storing
       Existing Data.

      Provide users with means to input and store NEW data.

      Provide information to help users perform their above tasks.

      Upgrade functionality as necessary to maintain the serviceability
       of the Hardware and Software.

      Keep abreast of new technology which could help in performing the
       above tasks.

      Know who can help you when you need it, and establish formal or
       semi-formal protocols for this to occur. Hardware people need
       software support, and software people need hardware support.

      Maintain some sort of contingency in all the areas for which you
       are responsible. 

      Know where how far your responsibilities go and how much authority
       you really have.  Use your authority when you must, but use good
       manners at all times.  Most (but not all) people will respond to
       kindness better than force.

      If you have any, know who your enemies are, but don't be paranoid.

      Keep management adequately informed of the state of things without
       driving management into information overload.  

   A list of DO NOT's for System Managers :
   --------------------------------------

      DO NOT remove data without notice.

      DO NOT remove functionality without notice and discussion.

      DO NOT presume others know what you know.

      DO NOT presume that things won't go wrong.  They will!

      DO NOT presume that others will read your mind when they read your
       messages.

      DO NOT presume that everyone reads the HELP and NEWS every day, since
       they do not.

      DO NOT treat you help badly, or else they might reciprocate.

      DO NOT presume that even knowledgeable users will be able to 
       solve problems for themselves.  Sometimes their time constraints
       are just too tight and they will need help.

      DO NOT reveal confidential information you may come across.

      DO NOT unnecessarily computerize sensitive information.  The
       chips have ears, as it were.

      DO NOT forget that your job depends on user satisfaction, although
       you may have temporary power over the users.

      DO NOT over-extend yourself, your budget, or your associates, too far
       and then have to suffer the consequences thereafter.

   Well, there you are.  A few things to mull over.  What did I leave out?


    Fred W. Bach                             Internet: music@erich.triumf.ca
    Operations group,                        Voice:  604-222-1047 loc 278/419
    TRIUMF (TRi-University Meson Facility)   FAX:    604-222-1074
    4004 WESBROOK MALL, UBC CAMPUS
    University of British Columbia,
    Vancouver, B.C., CANADA   V6T 2A3

  Disclaimer:

     These are my opinions, based on my experience, and in NO way
     necessarily reflect the views of my employer or fellow employees.
     My opinions should only get you to read and ask questions.

        ** I'm just a humble programmer working at my terminal. **