Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 20 views

    Sop - Appendix

    Uploaded by

    Tryphena Boateng

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Sop - Appendix

    Uploaded by

    Tryphena Boateng
    20 views3 pages

    Original Title

    SOP - APPENDIX

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    20 views3 pages

    Sop - Appendix

    Uploaded by

    Tryphena Boateng

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 3

    APPENDIX

    1. Document ID
    This is a unique identifier of the written document that is on a particular
    SOP.

    The format for SOPs for the Directorate should be: SOP-UD-001 (This is
    explained as Standard Operating Procedure Dash UITS Directorate Dash
    Numbers). The numbers should suggest the order in which the SOP for the
    Directorate appears. 001 will suggest the first of its kind, 002 the second, in
    that order.

    The format for SOPs for the Divisions should be:


    SOP-Code_Of_Division-001 (This is explained as Standard Operating
    Procedure Dash The Code of the Division Dash Numbers). The numbers
    should suggest the order in which the SOP for the Directorate appears. 001
    will suggest the first of its kind, 002 the second, in that order.

    DIVISIONAL CODES

    1. NOID - Network Operations and Infrastructure Division

    2. SDSD - Software Development Services Division


    3. USSD - User Support Service Division
    4. ISTAD - Information Security and Technology Assurance Division
    5. SDMD - Systems and Data Management Division

    2. Version Number
    This is a numerical value that describes the number of times it has been
    reviewed and accepted.

    Examples: A version number of 2.0, suggests a 2nd review of the first. A


    version number.

    3. Date Authorized
    This is the Date the SOP was approved.

    4. Effective Date
    This is the Date the SOP will effectively commence. This could be set a few
    days after the SOP has been approved.

    1
    5. Review Date
    This is the Date the current SOP will be reviewed. This should be three (3)
    years after the Effective Date of the SOP. In situations where it is prudent to
    review before the three year period, a letter should be sent to the TAC
    explaining the need before the Revised version could commence.

    6. Applicable
    This refers to the individuals or group or division the intended SOP applies to.

    7. Author(s)
    The name(s) of the person(s) that prepared the SOP.

    8. Approved by
    The name of the authorized person(s) who approved the SOP after careful
    considerations and perusal of the prepared SOP.

    9. Signature
    A digital signature of the authorized person who approved the SOP.

    10.Date Approved
    The date the SOP was approved.

    11.Purpose
    This briefly describes the intended reason for the SOP. Kindly do well to be
    brief and succinct with the purpose in order not to derial or confuse the reader.

    12.Scope
    A brief discussion about the extent to which this SOP should be used
    comprising the group(s), individual(s), what kind of task(s), etc.

    13.Applicability
    Who or what groups should comply with this SOP.

    14.Terms
    If there are any peculiar terms used in the SOP, where in few kindly state and
    explain in the SOP prepared, or if more than necessary, create an Appendix and
    explain all the terms.

    2
    15.Procedure
    This is a step by step approach to be followed in order to achieve the purpose
    of the SOP.
    This should be done in a well ordered and numbered order explicitly.

    16.Appendix
    Where necessary create an appendix to support the SOP. See (14) of this
    document.

    17.Related Documents
    If there are any other documents that compliments the SOP, please state for
    the purposes of reference by the individuals who will use the SOP.

    18.Version Control
    This helps keep track of the various transitions by way of review the SOP has
    undergone. This will help the applicable individual(s) or group(s) to know if it is
    the current SOP they are working with.

    You might also like