Shift Calendar

Set it up in your plant

Setting up Shift Calendar in your plant. Shift Calendar gives your plant and its lines their shifts and crews: which shift and crew it is now, a roster supervisors change, working-time limits and staffing kept as breaches, planned time, and services run at shift start or end.

1. Install itIT

   On the plant's OpenCore MES server, in its plant folder: sign in once with a licence token from your account at suites.opencoremes.com (one token per installation: production, test, training), install the suite, then restart OpenCore MES (opencore-mes start, or the service that runs it). The start log then lists it.

   opencore-mes suite login

   opencore-mes suite install shifts

2. Try it on a test installation firstIT

   Install it on a test or training installation before production. There, load its sample records (Designer → From the suites → Load its sample records) and walk the screens with the people who will use them. Samples never go on production.

3. Prepare People & departmentsAdministrator

   The suite's designs give their roles to the groups production (supervisors and planners) and the people on the crews. Check those groups exist in People & departments with the right people (or rename them in the change, next step), and that each department that must approve has its representatives.

4. Take its designs through a changeDesigner

   Designer → From the suites → Start a change from it. The change holds the plant's calendar, calendar changes, the shift handover and its service, a calendar and crew on each Person, and the shift board. Change what differs in your plant before submitting (labels, fields, limits, screens). Run the fitness test: every transaction's scenarios run in a sandbox. Submit; a reviewer passes it; Production approve it; it goes live as one change, all of it or none.

   • Nothing goes live until it is approved: the suite only offers its designs.
   • Once live they are your plant's own designs: they keep working if the suite is removed.
5. Draw your calendarDesigner

   Designer → the shift calendar: your shifts (start, hours, breaks, colour), your crews, the cycle (fixed shifts a cycle of 7 from a Monday; 2-2-3, 4-on-4-off, DuPont their length), planned stops, staffing (people at least and at most a shift) and working-time limits (days in a row, hours in so many days, rest). A calendar for some lines is its own element. The editor draws the next two weeks as you type.

6. Put people on crewsProduction

   On each Person, set their calendar and crew (Excel import for many). The roster then shows who is on each shift; absences, swaps, extra shifts and crew moves are made there by supervisors.

7. Use the shift in your designsDesigner

   Put the shift board, the shift now or the roster on screens; stamp the shift on records with ctx.shifts.at in a service; run a service at every shift start or end (a schedule of kind shift start/end); read planned time (ctx.shifts.planned) for OEE.

8. Go liveProduction

   Check the first two weeks on the roster with the supervisors, then watch the breaches list (limits and staffing) for the first month.

The same guide is in FLAMES once the suite is installed: Designer, From the suites, Set-up guide.