Basic ERP and MES Integration

Walker Reynolds of 4.0 Solutions takes you through how basic ERP to MES integration works when using a Unified Namespace.
More info on our Building Your Own MES Bootcamp and MES-ERP integration training here: www.iiot.university/mes-bootcamp
Welcome to another 40 Solutions video! 🎉
If you found value in this video, please hit the 'Subscribe' button and turn on notifications! 🔔
👉 bit.ly/SubTo40Solutions
Connect with us on social media:
LinkedIn: bit.ly/40SolutionsLinkedIn
Facebook: bit.ly/4-0Facebook
Twitter: bit.ly/40SolutionsTwitter
Ready to dive deeper into the world of IIoT and Industry 4.0? 🌐
Join our thriving community on Discord and engage with like-minded individuals! 💬
👉 bit.ly/Industry40DIscord
Supercharge your IIoT knowledge with our FREE Mini-Course! 🚀
👉 bit.ly/iiotmini-course
Thank you for your support and stay tuned for more exciting content! 🙌
#MES #ERP #IIoT #Industry40 #DigitalTransformation

[@willemhaifetz-chen1588]

The Recruitment argument is fantastic.

[@mscscambodia]

I like this example, finally a video I see spindle speeds, feed rates, tool wear, part dimensions, surface finish (Ra) and more. When discussing manufacturing much of what I do is on CNC machines and the processes, tooling, and HMI's using G-code needed to produce tight tolerances. Metrology is next, right. Enjoy the videos and have picked up some great ideas over the last few years of watching. Now that I am retired after 27 years of teaching Advanced Manufacturing I will be spending time getting to actually work with manufactures integrating these processes...... and more I hope. Keep em coming.

[@JeffRankinenAmyJoey]

Great video explaining the difference between events and transactions in the Unified Namespace. Thanks for making us fluent in all layers of the automation stack. With generative AI technology, it's more important than ever. Excited about the Advanced MES bootcamp session tomorrow!

[@4.0Solutions]

Always glad to help!

[@MonsieurWhojee]

Brilliant. Where were you 5-7 years ago when we implemented our MES systems? Huge leap in knowledge by watching your videos. Thank you.

[@4.0Solutions]

Glad to help!

[@sherylmccrary9045]

Instead of creating pipes containing the business logic, "the function itself becomes part of the digital infrastructure." YES!

[@singlepv]

Many thanks for sharing this content!

[@4.0Solutions]

You're welcome ❤️

[@mithsindia5150]

can you suggest if Oracle EBS /WMS be connected to AGVs readily or do we have to connect via a 3rd party integration system

[@willemhaifetz-chen1588]

SAP not in TESLA, SAP also not in TOYOTA imho

[@edonsequeira5957]

Hello Sir,
What is the name of your firm?

[@4.0Solutions]

We’re 4.0 Solutions! Walker also has an integration firm named Intellic Integration as well.

[@user-gs6mc2bc4e]

What are you talking about? A transaction can be seen as an event. A rich event full of rich and complex data. What you should avoid is try to represent a rich complex event with a key/value dataset like your Ignition tag system. Treat complex and relational data in one way and machine data and timeseries in a different way, but dont mix things up.

[@4.0Solutions]

This is right and wrong - right: a transaction can be seen as an event (because an event is something that happened and when). What is important to note - data is never complex, never rich. Data is always just a value and a timestamp and it is never actionable. Data is transformed into information - either through relational context and/or aggregation - to make it actionable.
Wrong: data and information is treated differently at the producer and the consumer - but not within the digital infrastructure. We will shoot a short today to clarify. Thanks for the comment!