So I guess we need to define the use-case for the new object. Here's what I've come up with:
In a practical scenario, I may have multiple (<10 to >500) people, that have independent schedules (different start/stop break times), need to link with different "resources" to do the work on an entity. Within this "working" time they could work on different (but specific) servers with a priority setting. There is a variability in their daily/shift setup time, a setup per batch and a run time per entity.
Let me give an example:
You have a number of doctors working in a hospital around the clock with an overlapping shift pattern. They need access to their respective tools (X-Ray machine, Operating Theatres etc.) to serve their patients. Some doctors may be able to change their roles if they are certified for different treatments (e.g. an anaesthetist may work in ER), if their primary role does not have a demand and their secondary role has a requirement for them. At the start of their day they need time to get into their scrubs (daily setup), Start up / warm up their machines (daily setup). They may then need to do some activities every time they change roles (setup per batch) and the time they need to treat each patient.
As an input to the above, you might have the doctors with their shift schedules, skillsets in one file. Another file denoting the tasks (maybe departments) along with required resources, resource time between failures, etc. and startup, setup, run times to serve each patient and a third file showing the incoming workstream of patients.
Is that the sort of functionality we would like to see achievable using (amongst other objects) the "new" object? Anything to add/subtract from the above?