The plan does not change behind your back

A plan that changes without a word is worse than a plan that refuses. This release removes two places where Orkyo moved work quietly, and it makes the lists agree with the site you select.

An entered schedule stays as you entered it

If you give a request a start and an end, Orkyo keeps both times. The request is saved with the window you typed.

Before this release, the create form moved such a request. A job entered for 08:00 on September 2 was saved for 06:00 on September 4, because the window met non-working time. Nothing said so. The edit form always kept an entered window, and the create form now makes the same promise.

If the window meets non-working time or an absence, Orkyo saves it and reports a conflict. A red flag on the board is more useful than a plan that is already wrong.

If you give only a start, Orkyo calculates the end from the minimal duration. This calculation skips non-working hours, weekends, and absences. The form then shows the new date in a message that starts with Moved to.

Orkyo also examines every resource on the request before it selects a slot. A time that is free for the machine is not free if the operator is absent.

Documentation: Scheduling and availability

Machine downtime flags the work already booked

An absence on a resource is now its own conflict kind, Resource Unavailable. The severity is error.

A closure at the site tells you that the hours are unusual. An absence tells you that the resource is gone. Only the second condition makes the booking wrong, and the two conditions now read differently.

Conflicts are calculated at the time you read them. If you block a machine for maintenance today, the jobs already booked on it become conflicts immediately.

Absences on a resource without a home site are also examined. Before this release, a person on leave with no home site never made a conflict.

Documentation: Conflicts

Conflicts has its own page

Conflicts is now an entry in the main navigation. It shows the same list at the same address.

The list and the Insights overview count different things, and each one now says which. The list counts every conflict in the workspace. The overview counts the conflicts in the period and the site that you select.

The lists follow the site you select

The station lists, the asset lists, and the requests list obey the site selector in the top bar. The board always did.

A resource belongs to a site through its home site, or through work that it does at that site today. Select All sites to see a resource that has neither.

Blocking time on a resource

The dialog that blocks time is named Block Time. It takes the dates from the period you select on the schedule, and its type is Unavailable.

The previous dialog was named Add Absence and its type was Vacation. Both words read strangely for a machine.

Time navigation moves one period

The arrows beside the date move one whole period on every tab. At the week scale, the arrow moves one week.

The timeline grids moved one day at the week scale. The label above them did not change, and the control looked broken.