NewSAP Digital Manufacturing, the manufacturing execution system
In the last 30 days
28 changes
Sat 24
alisonjiadded to the atlas
ankitshah25added to the atlas
Chris Perumaladded to the atlas
Claire Westadded to the atlas
Show 14 more
Eason-Lingadded to the atlas
elenaylzadded to the atlas
i307698added to the atlas
ilias-gmailadded to the atlas
levwzadded to the atlas
msaravanabhavanadded to the atlas
oksanazubchenkoadded to the atlas
PrayasDas03added to the atlas
Selvakumar Shanmugamadded to the atlas
Tarang Guptaadded to the atlas
VidyaDasCVadded to the atlas
Vivekadded to the atlas
zhouwei0115added to the atlas
詹斯迪added to the atlas
Tue 20
avijitshadded to the atlas
Cogniacadded to the atlas
huschlekadded to the atlas
mgcogniacadded to the atlas
Show 4 more
Philipp Domschkeadded to the atlas
RajashekarD26added to the atlas
robertriedeladded to the atlas
robertriedel09-blipadded to the atlas
Sat 17
New POD 2.0 Framework: The New Generation of SAP Digital Manufacturing Worker UIspublishedThe opening post of SAP's sixteen-part series on POD 2.0, the UI framework inside SAP Digital ManufacturingSAP Digital ManufacturingSAP's manufacturing execution system for running production on the shop floor, run by SAP as software as a service. The product behind the SAP Digital Manufacturing door: what is entered there is what people build for it, such as plugins for its Production Operator Dashboard, and the product itself is not an option. for building worker-facing execution screens: it replaces the architectural foundation of the existing POD model, drops the fixed POD types such as Work Center and Order in favour of POD templates, and exposes contextual execution data directly to the UI layer. The edge to POD pluginsPOD pluginsExtending SAP Digital Manufacturing's Production Operator Dashboard with plugins of your own: a view, a panel or an action that runs inside the operator's POD, packaged as an extension the product loads. Distinct from launchpad plugins, which extend a launchpad's shell around many apps.Community only holds on what it states about plugins themselves: the large monolithic plugins of the old framework have been broken into smaller, focused components, and layout, dialogs, buttons and actions that previously required UI extensions or custom plugins are configured in a WYSIWYG designer instead. It stops at the direction, with no code, no API and no packaging steps: new execution features will target the new framework and the legacy POD architecture will gradually phase out, while the designer, custom dialogs, dynamic PODs and notifications are left to the fifteen later posts the series list names.POD plugins
Thu 1
SAP Archivefirst recorded in the atlas
