FLO Vs MES Ebook
FLO Vs MES Ebook
FLO Vs MES Ebook
Operations Platform
A comprehensive guide comparing traditional manufacturing execution systems and operations platforms to help
you choose the right solution for your business.
Overview The Benefits of Empowering
1 Chapter One
5 Workers
Chapter Five
In this guide, we’ll conduct an in-depth comparison of two of the top options that leading manufacturers are turning to
when it comes to powering their digital transformation: Traditional MES and Tulip’s Frontline Operations Platform.
As business environments have become more dynamic and with the introduction of new technology such as IoT,
no-code, and machine learning, a new class of industrial platforms have become a common alternative, giving
businesses more to consider when it comes to finding a system to help manage their specific production needs and
challenges. Read on as we compare and contrast the traditional execution systems long-trusted in the industry with
Tulip’s flexible, powerful, frontline operations platform.
The no-code flexibility of Tulip’s platform empowers those closest to the operations, engineers on the frontline, to build and
configure applications that help them solve the challenges they encounter on a daily basis. This gives organizations and their teams
the power to leverage their in-house process knowledge and domain expertise to create and update applications without extensive
programming and IT resources.
Tulip is cloud-based
The platform is updated with regular releases, allowing users to access downloadable content and receive real-time, in-product
support. This simplifies deployment, sharing, and extensibility.
The rich and varied data Tulip collects from humans, machines, devices, connectors can be stored and viewed in powerful, yet
simple-to-configure dashboards and reports, not rigid tables or a separate add-on module that requires data manipulation.
With support for machines and devices built in, it’s simple to set up and collect data where you need it.
Tulip is GxP-ready
The platform was built to make compliance a seamless part of operations with continuous validation, as well as support for digital
history records, permissions and controls, and authentication.
With the Tulip Library, new or experienced users can download and configure app templates, explore example apps, and add
connectors.
While traditional MES are a tried and tested means of coordinating, executing, and tracking manufacturing processes, they only
solve a subset of issues that Tulip can while being slow to implement, expensive to maintain, and difficult to update.
1. Cost of Ownership
2. Data Contextualization
3. The Upgrade Process
With any new major investment, you may have questions about the total cost of ownership, such as:
● How much of a time commitment and monetary investment will this require?
● How about over the span of its lifetime?
● How will this new system impact productivity?
● How soon will we see value from this solution?
● Will we be reliant on vendors?
● What is the update process like?
Traditional MES
Traditional MES solutions are rigid and highly hierarchical, requiring a significant effort to plan and build a system. Large
organizations can see implementation projects lasting multiple years. That’s multiple months or years of non-value-added time.
As complexity increases, vendors become gatekeepers to the success of projects. To configure the solution to meet your needs,
vendors often charge high fees for professional services, as these systems require extensive technical expertise.
Where the MES approach is rigid, top-down, and all-or-nothing, the no-code deployment approach is flexible,
bottoms-up, and gradual. Using a no-code platform, you can still implement data models or system architectures, but
with a lot more flexibility.
You can start with a few apps and gradually add more use cases and introduce more complexity over time. You can
scale the deployment at your own pace and see value in months, rather than years.
The flexibility of apps with the structure of governance gives companies the best of both worlds – localized
problem-solving by domain experts empowered with no-code tools and global best practice and knowledge sharing.
Traditional MES
Validation requirements for an all-encompassing system implementation with a complex data structure make MES adoption a long
process, requiring extensive IT support. Learning the process, standards, and system and validating those only extends adoption
further, delaying the time-to-value of the solution.
“You have to validate all of the configurations and master data, all the processes that you put into the [MES system. And that takes
a long time; you need to learn the standard and learn the system as well. We’re talking, a good six to twelve months, if you’re really
good at it.” Gilad Langer, Manufacturing Practice Lead at Tulip
Hear more from Gilad Langer as he broke down this very topic during a recent panel session: The Future of eBR and eDHR.
Validating a traditional system in regulated industries and the life sciences is exhaustive. Any bug fix or upgrade comes at the cost of
validating what can be a very complex IT system that touches every piece of your organization.
Rather than needing to validate the full system with every update, you can validate Tulip’s platform and then check and validate each
individual app before releasing it to production.
For GxP environments, Tulip has an auditable QMS and provides a fully validated platform release every 6 months.
Traditional MES
In a recent survey by Gartner, 59% of manufacturing industry respondents rated “Improving Employee Decision Making and
Competency” as extremely important criteria for MES investment Justification. Gartner)
Rigid MES systems with complicated procedures and extensive training required, support “employee decision making and
competency” in a very limited way.
With apps, you can build digital workflows that guide engineers and operators through tasks — making their jobs easier and
improving their productivity. Process engineers can shift their time from building documents and spreadsheets to building apps that
seamlessly inform and collect data from operators.
Traditional MES
Maintaining agility is becoming increasingly important across all industries. For agility, it is not only important to be able to rapidly
update production, but the systems that support production as well.
MES solutions are typically monolithic with heavy reliance on 3rd-party integrators, and often require ticketing systems for any
updates – large or small. Hiring support can be expensive in itself, but 3rd-party intervention is also costly in terms of time spent
without utilizing the full potential of your system. If you want to update something (new equipment, machine, UI fix, etc.), it could
take weeks. If you want to adjust the data structure or add a field, you might need to wait months for the team to include it in the
new version of the MES.
With a Frontline Operations platform, you can keep more system expertise in-house and significantly reduce release
cycles. Depending on their permissions, an engineer can set up a new sensor and add it to the system in a single
afternoon.
Additionally, faster, more frequent release cycles mean rapid innovation and ultimately a better solution. You could
argue that an additional cost associated with monolithic MES systems lies in the lost opportunity for innovation.
Just how does adding context to your data make it more valuable, and why do MES systems limit the potential in your
information? Frontline Operations Platforms with no-code, IIoT and native analytics can bring your data to life and grant
you flexibility, in ways that IT forward MES systems haven’t been able to achieve.
Some of the problems with data stored in an MES are fundamental to the way these systems exist today: MES are monolithic and
require extensive support and expertise to implement. IT support is a necessity, and routine updates often require the same
hands-on expertise from vendors. This leads to issues like:
Depending on how they’re implemented, MES systems can further build up “Data Silos.” Dated infrastructure leads to
systems that can’t always communicate with each other, and data being stored by departments or functions. To pull
information for a holistic view across the shop floor, a team may have to gather information across multiple systems,
computers, databases and records. Inaccessible databases that require IT support put your data in a form of cold
storage, making it difficult to access it on the fly.
Rigidity in MES systems often limits the means of data collection. Data must be correctly entered into your system, as
the MES is configured. If your process differs from the MES’ then it can be quite costly to have the vendor change or
adjust the software. Changing the color of a button can be a process that takes months of IT support, and requires
tremendous resources. This makes it tricky to stay agile, and continuously improve. Essentially, MES locks down your
processes and requires uniformity in your information.
MES have limited built-in analytics capabilities and may require you to export data and manipulate it in external tools like
Microsoft Excel to gain the insights you need. By the time you can create a dashboard, the data will be already out of
sync with what is currently happening in your operation. Keeping dashboards up to date doesn’t add any value to your
teams. With every change to your process, new data collection through this dated process will extend the time it takes
to actually solve a problem and implement a change.
Context with data is important. Tracking machine downtime is a good first step at improving your operations, but the
value comes from being able to detect the cause of downtime, and what factors are influencing it. MES can’t always
provide that data, because they simply don’t have the means to capture it. Legacy systems are designed to intake and
store records, like machine state changes, but usually do not have a way to store operators’ experiences and inputs
through notes and images.
● ERP systems like SAP and Netsuite, SQL databases, and HTTP APIs
● Networked and Legacy Machines
● IIoT devices and sensors
● Computer vision detection
● Human data entries
It is easy to add a new data source into your apps, and connectors in the Tulip Library make it easy to be up and
running in a matter of minutes. Machines can be connected and updated quickly as well, without the need for extensive
custom code.
Being able to view and create analytics and dashboards makes it easy to see the real-time status of your operation,
and watch improvements closely.
Centralizing data across apps and tables in a shared structure allows you to call upon important information upstream
or down, and quickly see patterns and trends. The no-code advantage shines through built-in analytics, eliminating the
need for complicated, additional business intelligence software.
Operators on the frontlines work closely with machines every day and often see valuable first-hand knowledge. While
MES are designed for systems and machines, solutions based on no-code platforms can be designed for humans as
well. Integrating IIoT into a no-code app platform allows you to record information from the operator’s actions to better
understand what is happening in your operations. Smart tools and sensors can provide context to machine downtime
and inefficiency in operations.
Tulip allows you to build guided workflow apps that make it easy for operators to add notes and images. This human
data can be used to augment machine data and help an engineer quickly identify the root cause of a bottleneck.
Context can help engineers identify patterns, trends, and correlations. Instead of tracking machine-focused metrics, it
becomes easy to monitor your whole process, creating a truly connected facility.
Before we dive into the upgrade process, it’s important to differentiate between customization and configuration when
comparing the MES approach to the new approach with Tulip’s no-code operations platform.
Customization Configuration
Code changes that a vendor or vs. How a customer sets up the existing
integrator makes to a product to functionality to create a more tailored
provide a more tailored solution for a solution for their processes without
customer touching the code
The approach that traditional MES vendors take to provide tailored solutions to their customers is through product
customizations via code changes. As we’ll see, customization is fine and great until the system needs to be updated.
Product Updates
With MES software (and most software products), you have the main product branch and then a product patch branch.
The main product branch has major releases every 6 months to a year, usually with big new features and updates.
The product patch branch results from a mix of features and error corrections (between 10 and 450. When it comes
time to update to the latest features available with the main product branch, a vendor will install a backport of error
corrections for the customer on the branched version. This entails regression testing to make sure the updates don’t
cause problems.
In this scenario without customizations, you can see that things can get messy pretty quickly, but an MES vendor can
deliver corrections fairly quickly in days or weeks.
For each customer, a vendor will create a project instance copied from the product source code and invest 1,000s of
hours on product adaptations (customizations) for a solution to meet the customer’s requirements. These
customizations are made with hard-coded changes. Now the customer has a customized software version that needs
to be validated and deployed.
Whenever a new product update is available, the vendor representative needs to provide a customized backport for the
customer’s custom version of the product. Corrections take weeks or months to complete.
To add even more complexity, a single manufacturer may actually have multiple sites that all require site-specific
customization.
Whenever a new product update is available, the vendor representative needs to provide a customized backport for
each of the customer’s custom versions of the product. Corrections take one to two months to complete.
Enticed by new product updates, a manufacturer may want to rejoin the main product branch again and complete a
large upgrade project. Fed up with trying to maintain multiple versions of the same product, the manufacturer will try to
adopt just one version and each site will claim their customization is the best.
For each code update, a validation step is needed to prove the system operates as it should. With the complications of
upgrading, after a vendor product update is available the site will not be able to see the latest updates for months.
There is also a difference in cost associated with validation requirements of MES vs. the Tulip approach, which is we
discuss in more depth later.
Tulip’s Frontline Operations Platform handles solution tailoring a little differently. As mentioned earlier, Tulip does not provide product
customizations for each of its customers. Rather, Tulip’s no-code platform is configurable and you can update the interface, data
structure, triggers, connections, etc. on your own — or with a little help from a Tulip or a Tulip partner. Tulip is also a cloud-native
platform that can be deployed with AWS, Azure, or AWS GovCloud.
What this means from an upgrade standpoint is that platform updates are incredibly simple and fast. If your company prefers
biweekly platform updates, you can see new features and bug fixes automatically. Tulip also offers long-term support releases 23
times a year for customers that prefer more control of when they upgrade. In each case, you can stay on the main platform branch
and get the latest features and bug fixes without disrupting your configurations.
If you or any Tulip customers need a correction, Tulip can provide it with a point release within a couple of days. This
update is available to any customer that wants it. And there is no risk to waiting, as the fixes get rolled up into the main
platform branch for the next full release.
Tulip can deliver corrections in hours or days. For changes that involve tailoring the solution, you can make the changes
in-house using our no-code app editor without relying on the vendor or an integrator.
Tulip allows for a simpler validation approach with each update. Tulip has an auditable QMS and provides a fully
validated platform release every 6 months. Apps created based on customer business needs are considered
configuration in the context of validation and are in themselves the documentation of the MBR. The MBRs are
version-controlled and accessible within Tulip. Apps when they are executed, generate a fully compliant history record
that is fully digital and linked to the MBR version.