M2M Standards

Posted By stevenchung 6/13/2013 4:55:38 PM
Add to Favorites1
Author Message
stevenchung
 Posted 6/13/2013 4:55:38 PM
Forum Expert

Forum Expert - (750 reputation)Forum Expert - (750 reputation)Forum Expert - (750 reputation)Forum Expert - (750 reputation)Forum Expert - (750 reputation)Forum Expert - (750 reputation)Forum Expert - (750 reputation)Forum Expert - (750 reputation)Forum Expert - (750 reputation)

Group: Forum Members
Last Active: 7/1/2013 8:51:43 PM
Posts: 1, Visits: 7
750
Hello

I am new to M2M and I've been reading a lot of this technology. I have a doubt:

From what I understand, the MTConnect Institute defines standards for communication between machines. What is the difference between the work of MTConnect and the one from oneM2M?

Thanks
Steven

M2M
jdneidig
 Posted 7/19/2013 2:09:17 PM
Supreme Being

Supreme Being - (21,505 reputation)Supreme Being - (21,505 reputation)Supreme Being - (21,505 reputation)Supreme Being - (21,505 reputation)Supreme Being - (21,505 reputation)Supreme Being - (21,505 reputation)Supreme Being - (21,505 reputation)Supreme Being - (21,505 reputation)Supreme Being - (21,505 reputation)Supreme Being - (21,505 reputation)

Group: Forum Members
Last Active: 1/27/2016 9:40:29 PM
Posts: 44, Visits: 156
Steven,

Very good question, and I'll do my best to answer it. I may rephrase your question to differentiate "why MTConnect is different from other machine-to-machine standards or protocols like oneM2M?" To quote mtconnect.org, "MTConnect is a set of open, royalty-free standards intended to foster greater interoperability between controls, devices and software applications by publishing data over networks using the Internet Protocol." MTConnect is a protocol based on XML, widely recognized and very extensible. Just browsing oneM2M.org, I see it has a steering committee and working groups much like MTConnect and most standards. But MTConnect spawned from a need where Manufacturing didn't have a standard by which equipment, devices, software(i.e. ERP, MES, CRM, MRP, Machine Monitoring, the list goes on) would speak to one another without having to purchase proprietary systems. MTConnect is not only geared toward Manufacturing, but Manufacturing had the most need and was like the wild-west when it came to a machine standard protocol. MTConnect is all about open-source and bringing a community together to develop a really sustainable standard, which I'm sure oneM2M is as well. The MTConnect Institute also develops memorandums of understandings with other standards or institutes when necessary, especially when the goals, mindsets, and technology are the similar with another standard. For example, MTConnect has a Memorandom of Understanding with OPC Foundation called MTConnectOPCUA, basically cross compatibility so MTConnect compliant apps and equipment have the capability to communicate with OPC compliant systems and vice versa. I could see the same thing happening with oneM2M, what it comes down to is user implementation and which do the OEMs, Developers, and End-Users prefer. I find MTConnect to be extremely user friendly and understandable. I hope that answers your question...


Thanks


-Joel

Similar Topics

Expand / Collapse

Reading This Topic

Expand / Collapse

Back To Top

Advertisements