Select Page

Doctor Who Regeneration for Digital Transformation

Regeneration as a Metaphor for Digital Transformation

As a Canadian living in the American diaspora, I’ve had fun, at times, playing with my adopted country’s misconceptions of my homeland. I once convinced a room full of Texans that I had a pet wolf back home, à la Jon Snow, and that I culled dinner from the nearby caribou herds with a hand spear. Easy pickings, they were — the Texans, not the caribou.

But as a Canadian, I’ve also fielded my share of awkward questions, most often in relation to my country of origin and its relationship with its ancestral United Kingdom. To summarize: no — we don’t send tax dollars to the queen anymore. And no — I couldn’t give a rip about Harry and Meghan. But when it comes to contextualizing Canada’s relationship with the UK, I often find myself quoting Robert Frost, who was himself quoting an Englishman, when he said, “Canada ripened off the tree — you fell off green!”

Not to get too mired in post-modern discussions on post-colonialism, I will admit that I’ve long held onto my commonwealth membership card over the years, pulling it out whenever it was useful. One such case was the matter of Doctor Who. As part of my cultural inheritance, I was rather fond of that man of manners and madness. As a child, I remember wanting a characteristic Doctor Who scarf for my birthday almost as much as that red Michael Jackson leather jacket that was also popular at the time — the one with all the zippers… ah… the 80s…

ERP System Time Travelers

So when I heard that the latest rendition of the “The Doctor” was on the precipice of a regeneration into a new incarnation, it seemed fitting that my mind would wander into the dimension of digital transformation, and pluck a few parallels where they hung out in front of me. For all you time-travelers out there, the EstesGroup has helped countless companies over the years transition ERP systems that were 40+ years old — systems that go back to the Tom Baker era, if anyone is keeping track. For such companies, the shift from a character-based system to a contemporary ERP is enough to tear a hole in a company’s fabric of time. But what does that mean for a company facing such a change?

System Regeneration

Digital transformation is like a regeneration in the Doctor Who series. ERP systems are a new incarnation of the Doctor — they come into being, replacing their predecessors. They go on adventures, solve problems, and take their companion companies to unexpected places. And in so doing, they amass monumental amounts of experience and ingenuity, and ultimately encapsulate the worldview of the time in their rows and their columns.

The worldviews themselves amount to the business requirements of the organization, as they relate to the system in question. Worldviews are not fixed in time, and evolve gradually, as the system is further modified, fine tuned, reconfigured, and integrated with other systems. While this worldview continually changes, the changes are rarely as abrupt as a new body fitting an old suit.

A migration to a new ERP system, on the other hand, amounts to a much more radical shift in worldviews. The challenges really have to do with the wisdom and knowledge that is bundled up inside the legacy system, and with finding a way to translate that information into the new ERP system without compromising the integrity of the new system.

Don’t blink — it’s no easy task. In this context, the question you must ask yourself relates to how you approach a regeneration, knowing that it must happen. This might be a good time to lean on the good Doctor for assistance. Fortunately, there are several of them from which to choose:

You might approach the needed changes in the spirit of the Tenth Doctor and simply exclaim “I don’t want to go!” That is, you can fight the new system and cling to the old, as it slips away, like breath on a mirror.

Or you might approach an impending regeneration in the spirit of the Eleventh Doctor, understanding that “times change and so must I.” That is, you can get ahead of the transition and maximize the time you have, to remember as much of the legacy system as possible, such that it is not forgotten in the new system.

The truth is, regardless of your reaction, some form of digital transformation is inevitable. Any moment now, he’s a’ comin’.

I’ve had many customers migrate simply because the current state was no longer tenable: ancient hardware, out-of-date operating systems, applications lacking the faculties to keep up with the current needs of the business, much less lead them into the future.

I‘ve also seen customers delay a regeneration until the 11th hour, or a minute before midnight, and have thus dragged into a transformation without preparation. When it comes to transformation, preparation is key. Good preparation allows you to understand the business requirements that underly your legacy system. This gives you a better chance of incorporating your requirements into your new system, without trying to forcibly alter the new system to mirror the old.

In working with system implementations, one comes to understand that over the course of a company’s existence, systems change. And that’s ok, that’s good. You’ve got to keep moving, so long as your system remembers all the systems that it used to be.

We all wish that our digital transformations would have an orchestral accompaniment as the universe sings our legacy systems to their sleep. The truth is, you have to provide the soundtrack. And that soundtrack is a manifestation of the attitude you bring into your system’s story. The song of your legacy system is ending, but the story of your organization never ends — as long as time passes really slowly, in the right order, and the next season does not get cancelled.

Fast, Personalized, Proven IT & ERP Expertise

No spam. No pressure. Just strategic insights and clear solutions.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*

P21 Integrations: Best Practices & Lessons Learned

Epicor Prophet 21 System Software Integrations

The most challenging part of a Prophet 21 migration are the P21 integrations. For many companies, third-party integrations are a necessary component of their P21 ecosystem. Compared to many ERP applications, Prophet 21 has been highly reliant on third-party software to round out the functionality necessary to support the needs of many Epicor customers. 

With this necessity comes the challenge of integration. Third-party solutions differ in their integration strategies, and depending on the P21 version and the architecture of the bolt-on, one of many integration strategies may be employed.

Seamless Integrations 

Speaking of architecture, historically speaking, the P21 application traditionally possessed a two-tier architecture, with the P21 desktop application acting as a fat client, talking directly to the P21 database layer. In the absence of a Prophet 21 middleware or application server layer, third-party applications, out of necessity, interacted with the P21 application at the database level. 

Logical Business Logic

Only over the past several years has the Prophet 21 ERP expanded to include an application server layer, known as the P21 middleware server. This allows for a new layer of P21 integrations. These integrations can speak to the P21 application at the application server level, or even at the API level over the web. But for customers yet to migrate to P21’s three-tier architecture, or customers with legacy integrations that are not yet API-compliant, these new opportunities are still a work in progress.

The combination of a two-tier architecture and a “best-of-breed” approach to functionality resulted in a significant number of integrations speaking to the database directly. This was the case whether the applications in question were external applications conversing over a given communication protocol, installed applications functioning through Windows scheduled tasks or ongoing services, or installed directly into the Prophet 21 database, through a combination of SQL Server stored procedures and scheduled jobs. Add the middleware server, the web-based and hybrid clients, and the expiring legacy desktop application to this already-complicated situation, and the plot thickens.

Custom Development, Access, Control

Not surprisingly, access and control are critical to a Prophet 21 installation, if you intend to integrate your P21 ERP with a family of third-party applications. That is why our private cloud hosted architecture has been such a great fit for P21 customers, removing the challenges of on-premise installations while retaining the full functionality of the P21 application, and a hybrid cloud integration platform that can support third-party integrations at any level. 

P21 Software Integration Worries, Care

All said, customers come to us with many questions regarding their Prophet 21 software and its integration environment:

  • What is the best way to integrate an application with the P21 environment? 
  • How much programming is required? 
  • If my third-party vendor only integrates over the REST API layer, what do I need to do to make this work? 
  • If I’m implementing a solution that has multiple integration layer options, which layer should I choose? 
  • What about home-grown apps? 
  • Are there security concerns? 
  • How many holes do I need to punch in my firewall? 
  • With all these options, what are my best options for Prophet 21 server care? 
  • How bolted-on should a bolt-on be?

How EstesGroup Can Help

As a company whose specialty is the migration of the P21 customers into private cloud environments, and integrating their entire P21 ecosystems, we’ve learned many lessons in the trenches. On May 11th, at the P21 Midwest User Group meeting, EstesGroup’s Daryl Sirota and Chris Koplar will be discussing Prophet 21 integrations, and some of the best practices and lessons learned, as they relate to Prophet 21 integrations. Bring your integration questions and we’ll tell you everything we know when it comes to creating a seamless hybrid cloud environment.

Prophet 21 Midwest User Group Meeting – May 11th

The P21 Midwest User Group meeting starts on May 11th, at 9:00. The event will be held at the following location:

Lee Mathews, a Cogent company

4525 NW 41st St, Suite 400

Riverside, MO 64150

 Are you a member of the P21 Midwest User Group and interested in attending? If so, contact Joseph Babbit ([email protected]) and spread the word!

Fast, Personalized, Proven IT & ERP Expertise

No spam. No pressure. Just strategic insights and clear solutions.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*

This Old IT: The Modify vs. Rebuild Software Quandary

When should you start from scratch?

When I was about ten years old, my family lived in an old frame house. I have a lot of fond memories from our time there, but it had some quirks.

Originally a two-bedroom house, a third bedroom had been added onto one side. Built in sort of a lean-to style, the roofline didn’t match, of course. And it was added against the dining room/kitchen side over what was formerly the back door, so you could look out the kitchen window into my parents’ bedroom. It was built on a concrete slab instead of the pier-and-beam construction of the old house, so you stepped down into it, and then there was another back door in the bedroom opening to the backyard. It was an interesting place.

I’m reminded of that house occasionally when I encounter an aging software package that we’re replacing with a modern Epicor ERP system.

When the old stuff was installed, the implementation team made modifications to tailor it to the company’s operation and crafted operating instructions to guide the team. Over the years, the company and its requirements evolved, so more changes and additions were tacked on, old features were abandoned but not removed, and documentation was bypassed in the name of expediency. “Spaghetti Mess” is the technical term for what you get after ten, twenty, or thirty years. That’s just the way of life.

Eventually, a company makes the painful choice to start afresh with current technology and fresh eyes, and we find ourselves on the brink of an adventure. As we all know, adventure is rarely experienced without peril, sacrifice, and hard work. But it also can bring us reward and satisfaction.

When IT comes to IT, our consultants will be there.

The EstesGroup will be excited to be your partners in this journey. Need help with technology solutions or cloud services?  Is it time for help with your enterprise resource planning (ERP) system? We’ll be there before you know it!

Fast, Personalized, Proven IT & ERP Expertise

No spam. No pressure. Just strategic insights and clear solutions.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*

Two Sides to Every Cloud ERP Adoption Story

Understanding Your Move to the Cloud

Cloud adoption is often as unique as your company culture. However, the common benefits of cloud adoption abound. You can save time and money while increasing security, availability, and scalability. If you choose a cloud-based ERP deployment, what do you need for a successful cloud migration? Do you need to have a Shakespearean team ready to write the future story of your company? Once on the stage, will your cloud adoption tale be a tragedy or a comedy? Let’s try to understand the people behind your move to the cloud to better write your cloud adoption plan.

  • Cloud experts (consultants, migration specialists, engineers)
  • Enterprise resource planning experts (ERP consultants, trained employees)
  • Decision makers (steering committee members, owners, leaders)
  • Cloud ERP users (internal staff, external support)
  • Data center staff (consultants, architects, engineers, help desk team members)

Do you need cloud-savvy ERP experts on your team?

Make better decisions when moving your business applications to the cloud by balancing your decision-making team with your hands-on enterprise resource planning (ERP) talent. You can save even more time and money by supporting your in-house managers with ERP and cloud ERP consultants or experts when needed.

Quick Cloud ERP Adoption Planning Tip

An independent ERP consultancy can offer you an unbiased view of your decisions ahead, especially when it comes to newer technology and software releases.

Who will write your first line of cloud code?

Choosing a cloud for an ERP system might begin with someone on your IT team who has a progressive vision for the technological management of your company. Or, an ERP system, like Epicor Kinetic or Epicor Prophet 21, might be purchased simultaneously with cloud ERP project team formation and then guided by key players, such as company owners, CEOs, CIOs, and onward.

Understanding Your Business Cloud Requirements

A cloud ERP vendor might try to convince you that Software as a Service (SaaS) is your best, even your only, option. However, before you sign up for a data migration to a public cloud, consider private cloud or hybrid cloud platforms.

An ERP solution adapts to your unique cloud strategy. Once you understand your cloud ERP solution options and decide that your project plan should indeed migrate away from on-premise infrastructure, it’s time to solidify teams and team strategies. Your ERP implementation team needs both thinkers and doers.

The Thinkers

Your steering group will monitor the progress of your project ensuring it stays on track to complete on time and on budget. This group also will provide support for the project making sure needed resources are available to the project as needed and helping to backfill when those resources are taken from another part of the business.

The project manager is part of this group. Regularly the project manager will provide status reports and predictions for the immediate future of the project. An executive sponsor represents top management and is part of the steering group. That person will report project status to the C-level team.

When there is a champion who was instrumental in moving the software acquisition along and likes their role keeping the business excited about the prospect the software will bring, that champion should be on the steering group. Some representation from departments and functions that will use the new software might also have a seat in this group.

The Doers

Your cloud ERP implementation team should include leaders from departments across the business. They are directly involved in the overall implementation of this software and its IT infrastructure and, in most cases, they and their peers will use the new software daily. Most of the people in this group will be full-time talent serving on the software project but will keep in contact with their former co-workers in the functions they came from.

Often people who were group managers get assigned to this group, but there is no reason to limit the team to managers or former managers. Team members should be passionate about the new ERP system, its infrastructure, and the benefits expected. They should be very knowledgeable in their particular function and have some expertise in the use of the ERP software and process flows throughout the business.

Members of the cloud ERP implementation team will coordinate work in sub-teams that will test transactions related to their functional area. As testing progresses, cloud ERP team members will coordinate testing that extends to more than one function.

This group of people must keep in contact with their previous functional groups ensuring they know about any new changes or challenges. Managers of those functions will want to know the progress of the software implementation and will want to make choices when options in the implementation arise.

This team will help set up training and the training processes that will be used to share knowledge developed during implementation with the users who will need that knowledge to do their work with the new system.

Implementation team members do not need to be information technology gurus. They should understand some basic concepts related to IT and databases. This team will be directly involved in capturing legacy data and moving that data to the new software and, ultimately, to the cloud infrastructure of your choosing.

Look for the following indicators of a successful cloud adoption plan execution when choosing your cloud provider, your data center, and your cloud ERP implementation partner:

  • Is this a vendor trying to upsell you? Can a vendor-managed SaaS ERP system support your growing business?
  • Can your cloud provider meet your budget needs while adapting to your project timeline?
  • Does your cloud provider have a strong history and good reputation?
  • Does your cloud provider’s data center meet your needs for uptime and security?
  • Does your potential cloud ERP partner provide staff that will fit into your ERP culture?
  • Will the cloud provider understand your enterprise resource planning methodology and serve as a source of expertise for your ERP software and the full spectrum of its deployment options?

Will cloud ERP adoption improve your business today?

Enterprise resource planning (ERP) software implementation is a long, challenging commitment that involves dozens of people working together toward a common goal. Your go-live in the cloud will be one of the most rewarding and promising days in your company’s story. You can expect immediate results as soon as your team is empowered by both the software and its underlying technology.

To begin work as cloud ERP implementation team members, training is key. Your cloud provider will enroll your team in an in-depth training for your new cloud-based ERP system. Your team will learn how cloud computing works, especially from the cybersecurity aspect, and will quickly become astute through real-time support for the new business processes. Part of the training will be introductions to developers and system support personnel at your cloud provider. Implementation team members will not need to solve every problem but will know where to look for the answers.

EstesGroup provides on-premise ERP expertise while also fully supporting cloud migrations to private clouds, hybrid clouds, and SaaS projects. Are you ready to take advantage of internet connectivity to move beyond on-site servers? Do you need help building a cloud ERP plan for 2022? We have Epicor Kinetic ERP hosting, Epicor Prophet 21 ERP hosting, Sage hosting, and Syspro hosting experts standing by, ready to answer your questions about cloud migrations for both new and old ERP systems. Our experts can help you meet your business requirements so that you stay competitive while reducing cost across your infrastructure.

Fast, Personalized, Proven IT & ERP Expertise

No spam. No pressure. Just strategic insights and clear solutions.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*

Epicor Kinetic Upgrade: A Customer Perspective

An Interview with an Epicor Kinetic User

I recently had the opportunity to sit down with an Epicor customer to discuss their recent upgrade to Epicor Kinetic 2021.1. For many Epicor customers, this is a decision they will be facing in the next 12 months since the Epicor lifecycle for 10.2.700 will create a decision point in September 2022.

During the discussion, we covered a lot of questions that are commonly asked. My hope is that what you learn here will be an input to your thought process about when and how to upgrade to Epicor Kinetic.

Epicor History

This customer has been using Epicor for almost 8 years after they went live on version 10x. After the implementation they fell into the habit of not upgrading on a cadence. They regretted this because it made upgrades more challenging. Plus maintaining an Epicor upgrade cadence would have benefited them with better Epicor support, fixes, and new features. In their situation they were faced with upgrading to Epicor Kinetic from V10.2.200.

They currently have 35 users and expect to expand to 50 users in the next 12 months. They do light manufacturing and lean more to the distribution side of the spectrum. They also use Electronic Data Interchange (EDI) and a Business Intelligence (BI) solution that interfaces with Epicor.

Upgrade to Kinetic

The upgrade process took them about 90 days of effort. Knowing that future upgrades are released regularly, they invested front-end effort into documenting their business processes, end-user procedures and customizations. They also developed standard test plans that they can reuse in the future when they need to do upgrades.

They are expecting this investment to pay off as they move to 2021.2 later this Fall. During the upgrade preparation they took some time to clean up reports on the system, review their over 300 dashboards and look for ways to reduce the complexity and number of customizations that had accumulated over the years.
They then did very thorough testing in a Pilot Kinetics environment. The testing used formal test plans with each department supporting the effort. They ran all reports and validated cross-functional capabilities of the new system using a copy of their production 10.x data. As they found issues, they created solutions and documented them.

Reports

They found that many of their reports didn’t fully convert over to the new Kinetics format. So, they reached out to get external SSRS support for conversion of these reports. They were able to resolve any conversion issues with their dashboard reports using internal resources. This typically involved compiling them in the new environment and then saving them in the new Kinetic format.

Menus

They also set up two separate menu structures, one with a Kinetic look and one with the Classic look. This allowed users who were hesitant to use the new Kinetic menus some time to adjust. They estimate that they will transition all users away from the Classic view over a nine-month period.

Epicor Kinetic Upgrade Process

The actual upgrade was done on the 3rd weekend of the month to avoid month-end closing activities. They pre-arranged for necessary on-call support and proceeded with the upgrade. It finished and they applied any solutions they had discovered during testing. Then they tested the overall functionality using some pre-determined tests. No glaring issues were found so they were able to release the environment to users.

They found that the minor kinks that remained took them about 30-45 days to resolve. They were pleased that there were no issues with user permissions after the upgrade or with printing and labels.

Lessons Learned

Here are a few Epicor Kinetic upgrade suggestions from the customer perspective:

  • Make sure you have the necessary licenses for your Pilot environment,
  • Don’t forget the testing of integrations that access or share data with Epicor,
  • Make sure that department heads sign off on the test plans, so they understand any gaps/concerns, and
  • Consider using the developed Test Plans to next create new End User Documentation.

In the end, they felt like the Epicor Kinetic upgrade was more of a UI and programming change than a lot of new features for their users.

One More Thing

In retrospect they had one other recommendation that I found valuable.

Since the new Kinetics Users Interface (UI) allows all Forms to be displayed in any popular browser, there is an important decision to make. The decision is whether to allow Users to access Epicor from personal devices (tablets, home computers, phones). Most companies will have security concerns that will affect this decision. In their case, they decided to not allow users to use personal devices for accessing the Epicor application.

Overall, this customer was pleased with the upgraded UI. They found that the new UI is cleaner and more modern. Plus, the users like the ability to sort, and rearrange columns on the screen. In version 2021.1 some of the features they needed still required them to use the Classic interface, but the new release 2021.2 seems to have resolved these problems.

For now, the largest issue has been helping users make the transition to the new User Interface. Some users felt it was a steep learning curve for them and others didn’t. It confirmed for them that users rarely like change particularly in the screens they use each day. That’s why it is important to give them time to experiment and view the new interface well before any upgrade.

The I.T. department didn’t see any speed issues with processing under the new release. And they are looking forward to not having to install/upgrade clients on user laptops/desktops as they fully use the new Kinetics interface.

I hope this quick look at one client’s experience will provide some background for your decision-making and spur some questions that your organization needs to explore. If you have any other questions, feel free to reach out to us.

Fast, Personalized, Proven IT & ERP Expertise

No spam. No pressure. Just strategic insights and clear solutions.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*

What Cloud is Your Cloud Provider On?

ERP Hosting is Better Than a Trip to the Ice Cream Parlor

The age of “mass customization” pervades many areas of our business and personal lives. The general populace has grown accustomed to being able to “dial in” solutions as needed, especially when it comes to products and services. Tailored solutions have become a competitive advantage, if not a necessity, these days, and every cloud provider claims variety and customizability, even in the ever-so rigid atmosphere of SaaS (Software as a Service). If you’re looking for a cloud provider for your ERP (enterprise resource planning) application, do you ask where your new infrastructure team will actually cloud your data?

Ice cream parlors have been playing the variety card for decades. I have always been a fan of a good sundae—a little of this, a sprinkle of that, one flavor, two… the combinations are endless, as are the effects on my palate. But no two ice cream parlors are created equal. Similarly, no two cloud providers are created equal. Sometimes it feels like there are no standards that govern what it exactly means to be “flexible” in the cloud or to have “scalability” in the cloud. Like with ice cream parlors, sometimes vanilla is nothing more than artificial vanilla flavoring. This means that as a cloud solutions buyer, you need to understand the unique build of your server infrastructure before you sign the cloud services agreement.

In the cloud computing world, an ice cream sundae model for ERP application deployment is a natural progression of the mass customization movement. After all, flexibility and scalability are defining features of cloud computing.

Nevertheless, the big players in cloud solutions continue to pull us back into a world of vanilla (or vanilla flavoring). Tiered pricing models, service bundles, rigid step-progressions, and consumption models that do not adjust for seasonality leave many cloud customers feeling like they are trapped in an artificial vanilla apocalypse. Cloud computing is defined by its flexibility, but you wouldn’t know this when reading the fine print of your IT service contract.

That is to say, application deployment is not a one-size-fits-all proposition, even if your cloud provider is positioning it in that manner.

Some customers, with small footprints and standard business requirements, fit nicely within a software as a service (SaaS) framework when it comes to deploying ERP systems. However, many customers of greater size and complexity struggle with the limitations of SaaS. They want levels of access and control that are not normally afforded by SaaS deployment models. But exactly what a customer wants and needs differs from customer to customer. For suppliers offering very rigid solution sets, this can be a problem.

Some customers want a level of access and control that SaaS can’t support. They still want their cloud server stack micro-managed, but they don’t have the internal resources to perform the management. These customers lean toward managed ERP hosting, which falls more closely under a platform as a service (PaaS) model, where the solution provider manages the infrastructure and application platform layers, and the customer consumes the final output.

Other customers have the in-house staff and expertise to manage their own architecture. They want the solution provider to set up an ecosystem, but intend to take ownership and management of that ecosystem thereafter. These folks don’t need managed hosting, as they can perform any micro-management themselves. The solutions to satisfy these customers fall more under an infrastructure as a service (IaaS) model, where the solution provider provides the infrastructure, and the management of the application layer is the client’s responsibility.

But such simple distinctions between PaaS and IaaS seem too rigid for many customers. Many customers want something in between. They desire a combination of service, access, control, and responsibility. A sprinkle of this, a dash of that, a little smooth, a little crunchy.

As a customer, you need to make sure your cloud solution provider can lay out the various features and options that comprise their solution and help you work though a combination that fits your business. This might involve user provisioning, backup and disaster recovery, performance monitoring and tuning, or general application administration. Whatever the case, make sure your cloud solution provider is not trying to drown you in vanilla.

A Few More Clouds (and Cloud Providers) to Ponder

What types of cloud computing would you trust with your ERP software deployment? If you are considering managed hosting, are you looking for other managed services as well, such as cloud security services? Are you looking for a flexible data center for a hybrid cloud deployment, perhaps with pricing on a pay-as-you-go basis. Do you know your hardware and software needs? When you open a web browser on a corporate computer, do you know if any of your business data is kept in a public cloud?

Are you in need of a tailored cloud solution for your ERP application’s deployment? Chat with us now and get a free technology assessment!

Fast, Personalized, Proven IT & ERP Expertise

No spam. No pressure. Just strategic insights and clear solutions.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*