Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
iconfalse

This is the proposed roll-out schedule for an a typical OperationsCommander OperationsCommander install.   The schedule listed is merely a guide and helps to understand what aspects will be considered at which stage in the process.   Installations are generally unique with their own challenges and may not follow this guide completely.

Table of Contents

Phase 1 (estimate: 2 weeks)

After receiving contract signoff, the first step in the project is to confirm the requirements and begin a more in depth gathering of information from the client.  Your Account Executive will schedule a conference call for discovery. You may chose choose to invite other relevant staff from your organizations organization to the table to discuss expectations and clarify requirements. You will be directed to the New Client Orientation and Rollout wiki. An overview of tasks to ensure a successful smooth deployment are included.   Some areas that will be covered immediately are as follows:

Your preview and production systems will be created and given to you at this time. You will find it useful to start using your preview system immediately. You can practice and make changes on this system without being concerned about impacting your customer-facing system. The Preview site can be reset to defaults many times and nothing you do there will be permanent. It is a great place to experience and learn the system.   For information about your preview system check out his this wiki article:

Setup of OPS-COM Preview and Production Spaces

.

Billing occurs at this stage usually for both sign off and the Preview Go Live Milestones.

Phase 2 (estimate: 2 weeks)

After the initial preparation and research is completed, we will move to Phase 2 and begin assembling the standard components of your install including the technical and financial requirements and implementing the hosted payment solution.   The New Client Orientation and Rollout wiki will continue to guide you through all tasks in this phase as long along with your Trainer and Account Executive. Other areas of coverage include:

Phase 3 (estimate: 3-4 weeks)

Phase 3 is the stage where we focus on the client specific content of the install.   This is where any custom development work is completed, or data imports are managed.   This is also the time when we would look at integrations to any external data supplier such as the new Mobile Parking App Solution or to integrate your Meters into the violations database for real-time enforcement.   You will also be introduced to the self-guided training agenda so that you can start playing with your preview system and understanding how things work. 

Your Account Executive and/or your Trainor Trainer will be working with you and your team to setupset up:

Phase 4 (estimate: 2-3 weeks)

Phase 4 is the final testing phase of the project where staff on both sides work through the various functionality of the install in order to both learn the specific operations and to identify any potential bugs or client process misses prior to Go Live.   This is also when your Training representative will be working with you to ensure you are understanding the system and how to use it. Sessions will with you and your team will be setup set up at a time that is convenient with you to work through live training sessions about the various modules in the system. 

Phase 5 (estimate: 1 day)

Phase 5 is the final step of the project when all the tasks have been completed, custom requirements fulfilled, and the Live site is launched for public use.   Final Go Live milestone billing is completed and your recurring revenues are also billed.

 

  

Related Pages

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
sorttitle
cqllabel in ("rollout","orientation","setup") and space = currentSpace()


Show if
special@authenticated


Support Agent Notes

No special notes. If you feel any should be added, please add them here.