UCaaS Project Step By Step Part 4 - Provisioning & Delivery

Posted by John Teeling on May 15, 2018
John Teeling
Find me on:

Step 4 - Provisioning & Delivery

Up to this point in our blog series, we have primarily been talking about the initial steps for getting a project off to a successful start from an administrative and design perspective. With this segment, we cover assembling the items needed to build and deploy a UCaaS Project to the customer’s specifications.   

Find all 9 steps of UCaaS project HERE


Some folks I know say this is the part of the project that most people can “do with their eyes closed.” I say this is the part where attention to detail is critical. Here we can exhibit our professionalism and do the most to build our customer’s confidence in our ability to execute and deliver the system that they are envisioning (and ultimately paying us for).

We’ve broken this process down into three areas to execute against. They are all critical and, if done correctly, result in a UCaaS system that tightly adheres to the customer’s requirements.

Perform Data Collection

  • The key to great data collection is using standardized forms that are structured in a manner which requires the customer to provide you with a detailed and organized response. This allows you to build and configure the system with user, configuration and functionality as we have outlined in the previous steps of process.
  • This is also a great time to gather their WAN and Network diagrams. This provides as-built documentation for the legacy system that you are replacing in case clarification is needed during the provisioning process.
  • During this phase, don’t forget all the other items that need to be considered or accounted for in the process, as they may or may not currently be connected to the legacy system. This includes analog, fax, alarms, TTY, and so on. We all know a lot of these items don’t come over to the new system but do need to be accounted for by the customer. Remind the customer to address them, so nothing gets “orphaned” in the implementation of your project. They’ll be grateful for it.

Customer Approves Final Design for Implementation

  • This one is simple yet so critical. If you have been thorough in your data collection and documentation process, then you have produced a documented design that you can take to the customer to review and approve.
  • This design includes the collected data, which is formatted into build tables for users, as well as configuration data, design diagrams and a sign-off sheet. The customer uses it later to acknowledge that you have designed a system that meets every project requirement.

Provisioning the Solution

Now that you have an approved set of “blueprints,” you can have your implementation engineers build and configure the system. There is only one true way to measure success at the end of the system build. Audit your build and configuration against the final design document. Then have the customer validate that audit. It’s best to do this and make any changes before the system goes to the site, if it’s premises based, or before you move on to the testing phase of a Cloud project.

That way, you validate the UCaaS system before the next phase of the project, which is Testing. This phase involves plenty of best practices, which should help customer feel confident that the project is firmly on track. Read about it in the next post of the 'UCaaS Project Step By Step' series. 


Tags: UCaaS, Customer Experience, CCaaS