Kinetic MES overview
Kinetic MES is the shop-floor menu (clock in and out, start and end activities, report quantity, material requests) rebuilt as a Kinetic application. It runs in the browser or the Kinetic desktop wrapper, and its screens are customized with Application Studio layers like any other Kinetic screen. Classic MES customizations don’t carry over. If you’re coming from Classic, Classic MES overview and Migrating to Kinetic explain what has to be rebuilt.
Customizing Kinetic MES
Section titled “Customizing Kinetic MES”- Open the MES screen (or the program it launches, such as End Activity) in Application Studio and create a layer, as described in Application Studio overview.
- Hide or add fields in the Layout designer, react to buttons with events, and style or hide things with data rules. Base MES screens already use data rules to hide sections your licence doesn’t cover; see End Activity: the Actions grid and stuck activities.
- Keep business logic on the server. A button’s event should call an Epicor Function or a BPM-backed method rather than stringing together many client-side calls; see Report quantity from an Epicor Function.
- Barcode scanners behave the same as in Classic: they type. The advice on letting MES validate the job before the next field arrives applies unchanged; see Barcode scanning in MES.
In this section
Section titled “In this section”| Page | What it covers |
|---|---|
| MES screen tweaks | A home-page link to browser MES, and a live clock on an MES screen with no server calls |
| End Activity: the Actions grid and stuck activities | Why the Actions section is hidden, and how to end an activity an employee can’t end themselves |
| Report quantity from an Epicor Function | Reporting quantity for one or many operations server-side, called from an MES button |
| Per-employee language in MES | Why MES can’t switch language per clocked-in employee, and what to avoid while trying |