Dependency chains show the work at risk
Insights now lists each chain of dependent open work with its deadline and slack, most at risk first. The demo workspace has routings to start a work order from.
This release replaces the critical path table on the Bottlenecks tab. The new table shows the chains of dependent work that are closest to a missed deadline. An update from 1.0.0 is a normal update with no manual step.
Dependency chains replace the critical path table
The old table listed every request with a dependency. It measured each request against the last finish date of the whole network. A chain that ended in April showed months of float that it did not have. Finished work stayed at the top of the list.
The new Dependency chains table shows one row for each chain of linked open work:
- Where the chain starts and ends, and its earliest deadline
- Its Slack: the time between the earliest finish of the chain and its deadline
- A Late by badge when the chain misses its deadline
The chains with the least slack are at the top. Select a chain to see its requests, with their float and the Critical badge. Select a request to open it.
Orkyo now measures each chain against its own finish. Finished work does not count, and unscheduled work starts no earlier than now. The date range selects which chains appear.
Documentation: Insights and Dependencies and the critical path
Change for API and AI clients
The critical path result has a new chains list. Each node has a chainId. The
durationMinutes field is removed, because one duration across unconnected chains has no
meaning. The get_critical_path tool returns the same result.
Documentation: API and AI access
The demo workspace has routings
The demo now includes three routings: a drive shaft, an aerospace bracket and a product unit. Open Requests → New from routing to create a work order from one of them. Each step targets the correct machine type and skill, so the scheduler can place it.
Documentation: Routings