info@easystreet.com


Update contacts

  Update Your
     Administrative &
     Emergency Contacts

Managed Server

  Check Point VPN Client
  Firewall & VPN Changes
  Secure Shell (SSH)
  EasyStreet Admin for
     Hire

Colocation

  Access Card Form
  Facility Rules
  Remote Hands Service
  Tape Rotation Service

Monitoring Service

  Monitoring Setup
  Suspending Notification




Technical Support


MANAGED SERVERS

Change management procedures: Control means flexibility

Face it: Change is constant, and managing it is key maintaining complex IT systems. That's why EasyStreet uses Change Management Procedures following ITIL standards. These six-step procedures ensure that changes managed by EasyStreet will be methodical, well-planned and transparent.

1. Request: Request changes using EasyStreet's online Request for Change (RFC) form. This initiates the documentation and review process for standard and emergency changes.

2. Plan: A requester plans the change implementation strategy in detail, including the desired outcome, potential negative effects, impacts on other systems, and rollback procedures. This information is submitted with the RFC forms for review by the Change Approval Board (CAB).

3. Review and Approve: EasyStreet's Change Approval Board (CAB) meets every normal business day to review RFC forms submitted before midnight the prior day. Changes requested by customers and internal changes that might impact specific customer systems are discussed among EasyStreet and customers following the CAB review. Consistent with ITIL standards, multiple areas of the business are represented at CAB meetings.

4. Schedule: The CAB schedules all changes, taking conflicting changes into account.

5. Implement: Following review, approval and scheduling, a requester will implement his or her requested change and document the results for review by the CAB.

6. Review: The CAB reviews all changes implemented since the previous CAB meeting to ensure the desired results were accomplished. If they were, the CAB formally closes the RFC. If the change implementation is incomplete or had unforseen consequences, these are reviewed by the CAB and referred back to the requester, with recommendations. The requester then submits a modified RFC form and begins the process again.




Copyright © 2008 EasyStreet Online Services, Inc. All rights reserved. Certain names, logos designs, titles, words or phrases on this site may constitute trademarks, servicemarks, or tradenames of EasyStreet or other entities which may be registered in certain jurisdictions.