로그인
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > 포럼 홈 > Microsoft Operations Framework -- MOF 4.0 > Documenting the process and procedure
질문하기질문하기
포럼 검색:
 

답변됨Documenting the process and procedure

답변

  • 2009년 6월 11일 목요일 오전 8:30Akmeev Ruslan 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     답변됨
    로그인하여 투표
    0
    로그인하여 투표

    1-st document: Process Description.
    Executive Summary
    Goals
    Activities
    KPIs
    Roles
    Inputs/Outputs of process
    List of workflows

    2-nd document: Process Workflows
    Lot of Tables: Activity|Role|In-Out|Time|Comments

    +several documents (role matrix, work instructions, workforce calculations, etc), depend from customer.

     
  • 2009년 6월 11일 목요일 오전 8:46net_rfid 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     답변됨
    로그인하여 투표
    0
    로그인하여 투표
    hi Bitha,

    i would like to give the process which i am following for change management documentation. these are the process which you can follow in writting them in the same manner(the best way to make one manin document and put subdocuments in it).

    1. Initiation =  The change initiator completes an RFC.
    2. Acceptance & Classification = The change Manager accepts the RFC and classifies it according to type.
    3. Logging = The RFC goes to into Configuration Management Database
    4. Assessment = the change Manager Performs an initial assessment of the RFC and assigns a priority and classification.
    5. Authorization or Rejection = If the formal Change process is unsuitable, the change Manager rejects the RFC and             notifies the change initiator.
    6. Planning & Cordination = The change Maanger establishes the initial Plan , task,roles and responsibilities for the evaluating     and implementing the change.
    7. Evaluation = After the change , One or More eveluating determine if the change was successful or not.
    8. Closure = The change Manager cloes the RFC, and communicate status to the initiator. 


    i hope this will hepl you. 

    Feel Free to ask,

    Cheer,

    NET_RFID 
    Enam

     

모든 응답

  • 2009년 6월 11일 목요일 오전 8:30Akmeev Ruslan 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     답변됨
    로그인하여 투표
    0
    로그인하여 투표

    1-st document: Process Description.
    Executive Summary
    Goals
    Activities
    KPIs
    Roles
    Inputs/Outputs of process
    List of workflows

    2-nd document: Process Workflows
    Lot of Tables: Activity|Role|In-Out|Time|Comments

    +several documents (role matrix, work instructions, workforce calculations, etc), depend from customer.

     
  • 2009년 6월 11일 목요일 오전 8:46net_rfid 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     답변됨
    로그인하여 투표
    0
    로그인하여 투표
    hi Bitha,

    i would like to give the process which i am following for change management documentation. these are the process which you can follow in writting them in the same manner(the best way to make one manin document and put subdocuments in it).

    1. Initiation =  The change initiator completes an RFC.
    2. Acceptance & Classification = The change Manager accepts the RFC and classifies it according to type.
    3. Logging = The RFC goes to into Configuration Management Database
    4. Assessment = the change Manager Performs an initial assessment of the RFC and assigns a priority and classification.
    5. Authorization or Rejection = If the formal Change process is unsuitable, the change Manager rejects the RFC and             notifies the change initiator.
    6. Planning & Cordination = The change Maanger establishes the initial Plan , task,roles and responsibilities for the evaluating     and implementing the change.
    7. Evaluation = After the change , One or More eveluating determine if the change was successful or not.
    8. Closure = The change Manager cloes the RFC, and communicate status to the initiator. 


    i hope this will hepl you. 

    Feel Free to ask,

    Cheer,

    NET_RFID 
    Enam

     
  • 2009년 6월 11일 목요일 오후 2:46Cleber MarquesMVP, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표

    Great suggestions folks. Congrats.

     

    Bitha, remember that you need to adapt the process to your necessity, OK? Draw a process that help you and your organization archive the determined goals.

     

    Hope this helps

    Regards,

     

    Cleber Marques

    Microsoft Most Valuable Professional (MVP)
    MOF Brazil Project: Simplifying IT Service Management
    www.mof.com.br | www.clebermarques.com | www.clebermarques.com.br
     
  • 2009년 6월 23일 화요일 오전 2:00Cleber MarquesMVP, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표

    Hi,

     

    I’m marking this post as answered, if you need any help about MOF please open a new thread. J

    Thank you,

     

    Cleber Marques

    Microsoft Most Valuable Professional (MVP)
    MOF Brazil Project: Simplifying IT Service Management
    www.mof.com.br | www.clebermarques.com | www.clebermarques.com.br
     
  • 2009년 7월 19일 일요일 오전 11:00Andrew Sword [MVP] 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표
    Type of Change. For example Low, Medium or High impact.
    Andrew Sword, MVP
     
  • 2009년 7월 19일 일요일 오전 11:08Cleber MarquesMVP, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표

    I agree Andrew, good points. Change levels is a good start.

     

    Regards,

     

    Cleber Marques

    Microsoft Most Valuable Professional (MVP)
    MOF Brazil Project: Simplifying IT Service Management
    www.mof.com.br | www.clebermarques.com | www.clebermarques.com.br