ERP Deployment Methods

When searching for a new Enterprise Resource Planning (ERP) system, or when looking for ways to get the most out of your existing system, the topic of deployment method often comes up. If you aren't a "techie" type this can sometimes feel like an overwhelming choice to make as there are many nuances to each type. And to make matters worse, vendors often use a lot of acronyms and buzz words to describe the different types of deployments which can make it that much more challenging.


Today we are going to break down the three main types of deployments into bit sized pieces.






Cloud

  • AKA : True Could, Multi-tenant Cloud, SaaS

  • Servers are located in a data center

  • Client is not responsible for server upkeep

  • App is (usually) browser based

  • App is immediately accessible anywhere

  • Nothing to install locally

  • No direct access to database

  • Hardware is often shared between clients

Pros

  • Requires little to no hardware maintenance

  • Less internal IT staff required to keep systems going

  • Very easy to deploy to remote and traveling employees

  • Server resources can scale up and down with business

Cons

  • No direct access to data

  • Clients often think cloud means "easier to use" than other methods and that just isn't the case. You still need experts in the application available

  • No internet means no access


Private Cloud

  • AKA : Hosted, Cloud Hosting

  • Servers are located in a data center

  • Client is usually responsible for server upkeep

  • App can be browser based or a client app

  • App is immediately accessible anywhere

  • Nothing to install locally

  • Database is accessible in cloud environment

  • Hardware is dedicated to one client

Pros

  • Can easily deploy a single application or give users a whole "cloud" desktop

  • Maintain full control of the environment

  • Easy to deploy to remote and traveling employees

  • Retain access to your data

  • Allows cloud access to desktop applications

  • Can scale up and down with your business

Cons

  • Often requires internal IT support staff

  • No internet still means no access

  • Is usually more expensive than a Cloud solution


On Premise

  • AKA : Legacy System, in-house deployment

  • Servers are located at the client site

  • Client is responsible for server upkeep

  • App can be browser based or a client app

  • App requires access through firewall or VPN (Virtual Private Network)

  • Database and App are installed locally

  • Full access to database

  • Hardware is owned by the client

Pros

  • Complete control of environment

  • Full access to data

  • Still works for local users even with no internet access

  • Can be more cost effective when dealing with very large amounts of data


Cons

  • Requires internal IT support

  • Responsible for all server maintenance and backups, etc

  • Giving access to remote and traveling employees can be more challenging and is more of a security risk

  • Harder to scale up or down as it requires physically adding or taking away hardware


As you can see, there are pros and cons to each approach. That's why it's important to work with a firm that has seen all three of these scenarios in action and can help you decide which deployment methodology makes the most sense for your business not just today, but in the future as well.


Curious about what method is right for your business systems? Contact us today and we can help you down the right path.

Call

T: 281-607-1333   

Houston, TX

Columbus, OH

  • White LinkedIn Icon
  • White Facebook Icon
  • White Twitter Icon
  • White Instagram Icon

[service​s]

[products]

[stay in touch]

- Blaze IT LLC -

  • White LinkedIn Icon
  • White Facebook Icon
  • White Twitter Icon
  • White Instagram Icon

[erp software consulting]