A data center move project incurs numerous expenses during the course of the project. Some of these expenses will be one-time; others operationally significant. The planning phase needs to evaluate:
The state of the new facilities. Are racks provided? Will these racks meet your requirements? Are the electrical facilities sufficient? Does any equipment require DC power? If so, is this provided? Are cable trays provided or must these be purchased and installed? What D/R facilities are provided? What security is in place?
Equipment. Will all of the existing equipment be migrated? What new or replacement equipment will need to be purchased? Will this new hardware require new software licenses? Should redundant equipment be purchased before the move? Does any equipment need to be moved specifically by the vendor, manufacturer, or service provider?
Cabling. What cabling will be required and who will implement this cabling?
Transport. How will the equipment be transported to the new location? Will this task be outsourced? Is additional insurance required for this task?
The attached spreadsheet will help in outlining a high level data center move budget.
Corporate events range from simple holiday parties to complex symposiums with thousands of attendees. The below Work Breakdown Structure (WBS) document is intended to assist with planning a relatively simple corporate event.
The purpose of the Communications Management Plan is to document the methods required to ensure timely and appropriate generation, collection, dissemination, storage, and ultimate archival of project information.
Briefly describe how the Communications Management Plan will be used for the project and how the plan will impact the project team.
Identify Project Team
Who are the members of the project team and what are their roles? This section should always reference the below individials and provide contact information (email, phone, etc.)
the Project Manager
the project Sponsor
Key contributing staff
Vendors
Project Team Responsibility Matrix
This section should identify the role of each team member as well as particular communication roles for which they may be responsible. For example, if a technical team leader is responsible for weekly distribution of a product development status report, then this should be identified.
Methods of Communication
How will the team members communicate? If team members are geographically distributed, will a particular platform be used for conference calls or online meetings?
Project Documentation, Control and Archives
This section identifies what elements of the project will be documented, how that information will be captured, distributed and archived
Email
Some companies use particular public email folders or distribution lists. This should be documented.
Meeting Minutes
Who is responsible for capturing meeting minutes and how will these be distributed and archived?
Project Reports
Who is responsible for drafting and distributing project reports and how will these be distributed and archived? What is the content of these reports and to whom will they be distributed?
Other Documents
Are there other documents which need to be distributed to the project team?
Project Meetings
How will project meetings be scheduled and conducted? Who are the participants? If a schedule is available, then it should be provided.
Kickoff Meeting
Has the Project Kickoff Meeting been already scheduled? Identify participants, schedule, location.
Meeting Agenda
Who will be responsible for drafting the meeting agenda? When should these be distributed? Are these stakeholders who should also be on the agenda list even though they may not be participating in the meeting?
Project Reporting
What project reports should be distributed and who is responsible for doing so?
Summary
Due to changes in internal business processes, our company requires a new billing platform. We anticipate selecting the new platform within the next 14 days and require the selected product to be wholly implemented within 120 days.
Phased Implementation
The implementation will proceed in 2 distinct phases. The first phase will cover the core product and provide a provisioning interconnect with key services and accounting application architectures.
Core Requirements
The core product must include facilities for managing customers, products, services, equipment, bill generation and presentment, A/R and bill payment including a POS interface, settlement processes, service processing, marketing support and reporting. Ideally, the application will run on an (preference) platform and allow full database access for reporting. The core application and management interfaces should be web based and allow for custom interconnects via an open web services API.
General Requirements
The application should be web based and platform independent
Hierarchical user and system account privileges for audit control and systems management
Fully accessible data architecture and web services API
GAAP audit control compliance
Customer Care
Ability to manage all aspects of customer account data, including add, manage, remove services, equipment, bundled packages, etc.
Ability to manually activate or deactivate an account (e.g. in a non pay situation)
Access to historical account information, including invoices, equipment, services, packages
Ability to post debits / credits to account
Ability to track contact with customer, including memo or note functionality
Ability to set alerts on specific accounts
Web based end user interface allows for customer self care, including self sign up, order processing and online credit card payment (real time), usage reporting, access to summary statements
Provide reporting for equipment and inventory tracking, product and package statistics
Point of Sale (POS)Interconnect
The point of sale system must be wholly integrated with the CRM, A/R, provisioning and order management systems.
The POS system should support usage of standard peripherals, including cash drawer, receipt printer, card swipe and bar code scanner
Support for networked multiple store locations and multiple terminals at a single location
Service Management
Integrate with (products). Provide specifications (e.g. switch information for a telecommunications environment).
Integrated Provisioning
Integrate with (product) to enable automated provisioning from within billing
Provide aggregate A/R and general ledger export to accounting package
Bill Presentment
Supports convergent invoicing for multiple products and/or services
Ability to generate physical paper bills
Provide for a configurable company branded invoice
Ability to generate and distribute bills via email
Provide online bill and payment capabilities in end user web interface
A/R
Provides full GL management
Collections management
Reporting to include aging, subscriber billing balance history, GL, revenue, earned income, etc
Billing systems are usually complex. The billing implementation project work breakdown structure (WBS) presented here was used for upgrading an existing billing platform to a new platform provided by a different vendor.
The billing platform provided by the new vendor did not include a point of sale (POS) component, so the vendor was asked to enhance their platform to include this component. The client was responsible for purchasing the POS peripherals.
The most time consuming component of this project, aside from planning, involved data cleaning and migration to the new platform.
![[Facebook]](http://theprojectdiva.com/divapress/wp-content/plugins/bookmarkify/facebook.png)
![[Twitter]](http://theprojectdiva.com/divapress/wp-content/plugins/bookmarkify/twitter.png)
![[Email]](http://theprojectdiva.com/divapress/wp-content/plugins/bookmarkify/email.png)