Skip to main content

The CCC Process Through the Eyes of a Project Manager

Kevin Jermyn, Sr. Project Manager
Originally shared June 12, 2018

CCC Technologies successful upgrades/Migrations in the Avaya CM world all start with developing a project plan with emphasis on minimum risk to customer and end user.

To start, CCC Account Executives and Design Engineers engage the Project Manager, Lead Engineer, and the VP of operations once the design and customer needs are realized and developed.  We collaborate with design changes to maximize flexibility and minimize risk, which allows for less down time for the customer.  Most designs will end up with new equipment or the customer moving to a virtual environment; some with a mix of both.

Once a project is in house, the PM and Engineer discuss deploying the solution. We look at multiple sites or single sites with the same savvy.

Whether new servers or virtual servers, the key is to stand up the new servers/gateways with the existing environment.  We can now test new applications prior to our cutover. We can have users create new mailbox greetings & passwords prior to the 1st day business. This allows end-users to concentrate on the needs of business on 1st day. We can flush out any issues prior to going live. At cutover we may need to change IP address or register new servers to existing gateways, which is done rather quickly. Also, if we find an issue we can revert rather quickly to the old system if necessary. I can only remember once or twice that this has happened over the last 15 years at CCC.

If we have multiple sites, we still start by getting the main site tested and running side by side with the existing one.  Our Engineer will set up an IP connection from new to existing and then test.  Most remote sites will be getting a new server & reuse existing gateway. By setting up the IP connection a CCC Engineer can upgrade remote sites prior to the main site. The Engineer can register the remote site with the new main server which helps our customer minimize resources needed to support each site. Imagine if all sites had to be cutover at the same time as the main site; testing would take hours and the outage window would be much longer. Then, if a site doesn’t register we would need to troubleshoot with the customer at the site, and most likely with a Customer Network Engineer. With CCC’s process, we can troubleshoot prior to cutover minimizing risk for our customer.

CCC strives for nonevent at each cutover. We plan for developing and fine tuning and have a commitment to minimize downtime & risk while maximizing a great customer experience.

If you have any questions, contact your CCC Technologies Representative or call us at 877.288.9227.

If you need support, please call our 100% U. S.-based Customer Care Team at 1-866.347.3780 anytime, day or night.

Comments

Popular posts from this blog

Four Key Components of a Robust Security Plan Every SMB Must Know

Four Key Components of a Robust Security Plan Every SMB Must Know Most businesses are now technology dependent. This means security concerns aren’t just worrisome to large corporate enterprises anymore, but also the neighborhood sandwich shop, the main street tax advisor, and the local non-profit. Regardless of size or type, practically any organization has valuable digital assets and data that should not be breached under any circumstances. This makes it the responsibility of every business, especially those collecting and storing customer/client information, to implement a multipronged approach to safeguard such information. Yes, we’re looking at you, Mr. Pizza Shop Owner who has our names, addresses, phone numbers, and credit card information stored to make future ordering easier and hassle free. Today’s SMB Needs a Robust Security Plan Protecting your business and its reputation comes down to developing, implementing, and monitoring a robust security p...

3 Things to Consider Before Jumping Into BYOD

3 Things to Consider Before Jumping Into BYOD You’ve read it time and time again. “Bring Your Own Device” isn’t a trend, it’s the future. Workplaces where companies let workers use their own devices for work purposes are the new normal. BYOD attracts new hires and lifts employee morale and productivity. But this doesn’t mean a small business owner should recklessly jump right into BYOD just because everyone else is doing it.  Data and network security concerns have to be thought out, defined, and addressed in a comprehensive BYOD policy. Here are three things to consider. Cost of Support Most businesses salivate at the thought of the money saved by having employees participate in a BYOD program. With employees using their own devices for work, there is no need to shell out thousands of dollars for desktop PCs, smartphones, tablets, and laptops. While that’s undoubtedly a huge incentive, extra support costs must also be factored in. Chances are your employ...

4 Essential Pieces to Any Small Business BYOD Strategy

4 Essential Pieces of Any Small Business BYOD Strategy Believe it or not, once upon a time, kids at the bus stop didn’t have cell phones and the mobile device strategy of many businesses was typically "you’ll take what you’re given, refrain from using it for any personal use, and the data may be scrubbed clean whenever we please." We’ve come a long way.  Today, businesses really have no choice but to let employees use personal devices for work purposes.  Blurred lines now make it difficult to differentiate between what is professional and what is personal.  A company or organization may partially pay for an employee’s tablet computer or smartphone, but that same device is used to upload photos to Facebook or download torrents of this season of Game of Thrones. Naturally, security and privacy issues are a concern since these devices sync to the company network.  Larger corporations may be able to hire IT support or produce sophis...