User:Devgenious/sandbox

This is the user sandbox of Devgenious. A user sandbox is a subpage of the user's user page. It serves as a testing spot and page development space for the user and is not an encyclopedia article. Create or edit your own sandbox here.

Other sandboxes: Main sandbox | Template sandbox

Finished writing a draft article? Are you ready to request review of it by an experienced editor for possible inclusion in Wikipedia? Submit your draft for review!

Comment: Reviewed and reversed my CSD. Is about concept rather than product. If you believe I have erred by restoring, please send to MFD.Dlohcierekim (talk) 17:26, 22 May 2017 (UTC)

Cloud MES are Manufacturing Execution Systems (MES) that run in a public cloud^[1]^[2]. Traditionally, a Manufacturing Execution System is installed and deployed on the internal infrastructure of a single organization. The MES software is conventionally sold as a perpetual license and the software runs on own private servers, databases, networks and work stations. Maintenance, support, installations and changes are usually handled by the internally IT department or by a hired third-party.

Cloud MES is different^[3]^[4]. It is a so-called 'Software As A Service (SaaS)' solution, meaning that the software runs over the Internet in a public Cloud and in which software is licensed on a subscription basis. Such a license model offers a recurring monthly/annual expense. There is no major requirement for buying and deploying server hardware, purchasing software or hiring support personnel.

Cloud MES vendors typically develop and manage their own software and offer it to a large number of customers as a SaaS solution in the Cloud. The idea behind a Cloud MES is that it should be flexible for many customers and already contains the features and functions that are typically used in different types of Manufacturing Execution Systems such as managing work orders, tracking and tracing, inventory management, barcode reading, resource management, reporting and documentation.

Customers that subscribe to a Cloud MES will start with configuring the build-in objects and flows to model their manufacturing processes and organization. The user interface of a Cloud MES runs in the browser and is usually implemented in HTML-5. After the configuration task has been completed and tested, a Cloud MES is deployed by the customer for execution by sharing the URL and giving users online access that matches their role. Some Cloud MES support connections to production equipment via an open Application Programming Interface. Allowing Cloud MES to gather production data in an automated manner.

References edit

^ Riley, Darren. "The Sky's the Limit – Enterprise MES Moves to the Cloud". apriso.com. Retrieved 10 March 2015.
^ Hennessey, Tom. "The Cloud, MES and Centers of Excellence". apriso.com. Retrieved 2 July 2015.
^ Fortunel, Christian. "Deploying MES in the Cloud: Challenges & Solutions, Part I". contractpharma.com. Retrieved 9 November 2016.
^ Fortunel, Christian. "Deploying MES in the Cloud Challenges & Solutions, Part II". contractpharma.com. Retrieved 26 January 2017.

[1] Riley, Darren. "The Sky's the Limit – Enterprise MES Moves to the Cloud". apriso.com. Retrieved 10 March 2015.

[2] Hennessey, Tom. "The Cloud, MES and Centers of Excellence". apriso.com. Retrieved 2 July 2015.

[3] Fortunel, Christian. "Deploying MES in the Cloud: Challenges & Solutions, Part I". contractpharma.com. Retrieved 9 November 2016.

[4] Fortunel, Christian. "Deploying MES in the Cloud Challenges & Solutions, Part II". contractpharma.com. Retrieved 26 January 2017.

[1]

[2]

[3]

[4]