HMGforum.com

Then, what you want is resource planning with non overlapping events...

Interesting !

One or many resources in the same screen ?

I'm building application for production planning. I need to test workers and workplaces availability in time. Very complex idea...
I need to present production plan.

I am sure you can get ideas from https://www.openproject.org/

I'm guessing it's custom-serial production as in a printing shop, pharmaceutical lab or packaging outsurcing.
Every product has a different production path (workflow), but available machines and personnel are fixed, an the goal are to program production queues and querying a prouction order status.
I have some ideas, but I think this all is WAY beyond a software GUI forum.
Some ideas are clear, it is not a appointment system, it's not a project manager.
This is a BIG system worth very big BUCKS.
Maybe worth an open source initiative maybe not.

Just my POV.
Best Regards
Angel

Marek, a thousand apologies for answering so late

Acept events Daily, weekly and monthly, this are stored in tables, when you are in the aplication ,
this monitors the events to see if there are any on this day, but you could have selected it for a long time ago
Works with a multitude of users and can only see their appointments

Rathinagiri wrote: ↑Thu Jul 27, 2017 4:25 pm I am sure you can get ideas from https://www.openproject.org/

Thanks for pointing me this solution. I've done too much my work, to left it. I'm almost on finish, I think.

apais wrote: ↑Thu Jul 27, 2017 4:49 pm I'm guessing it's custom-serial production as in a printing shop, pharmaceutical lab or packaging outsurcing.
Every product has a different production path (workflow), but available machines and personnel are fixed, an the goal are to program production queues and querying a prouction order status.
I have some ideas, but I think this all is WAY beyond a software GUI forum.
Some ideas are clear, it is not a appointment system, it's not a project manager.
This is a BIG system worth very big BUCKS.
Maybe worth an open source initiative maybe not.

Just my POV.
Best Regards
Angel

In essence is a typical problem of Operations Research (OR). It is necessary to apply mathematical techniques like Queueing Theory, PERT/CPM and Linear Programming among others.
My favorites books of OR are:
1) Hiller-Lieberman
2) Taha

Mol:

Maybe I'm late to offer my modest contribution, but just in case ...

It would be to work on a file that we can call MOMENTS.

At all times, an worker will be in one place, and that place will have an worker. Of course, only the moments of activity will exist, being those of inactivity those that do not exist.

The file would have at least four indexes:

1º / WORKER + DATEstart + TIMEstart + DATEend + TIMEend
2º / PLACE + DATEstart + TIMEstart + DATEend + TIMEend
3º / WORKER + DATEend + TIMEend
4º / PLACE + DATEend + TIMEend

The first offers where the worker is, when it starts and when it ends. (I have not written it backwards : I have worker and times, and in the 2nd field / index I have the place).

The second offers which worker occupies the position, when it begins and when it ends. (Idem).

The third, when will be the worker free.

The fourth, when will be the place free.

All these data refer to A CONCRETE MOMENT. If I want to know the availability of an operator or place, I look back on the 3rd and 4th indices respectively. And if I want to know the working time of an operator or place, I have the indexes 1 and 2. These indexes also allow me to know the "gaps"; and at the same time, to know if an operator is occupied or place at a certain time, preventing any overlap. (When I speak of "hour," it assumes HH: MM: SS)

For times that exceed the day would be necessary to establish a work schedule, which can be individual or collective: if the day is from 8:00 a.m. to 4:00 p.m., a work that starts today at 3:00 p.m. and lasts 3 hours, will end tomorrow at 10:00 a.m.

Each record would also have other descriptive fields if needed.

(Ahora en español, porque igual en inglés no se me entiende ni papa y otro forero lo puede traducir mejor que yo).

Quizá llego tarde para ofrecer mi modesta aportación, pero por si acaso…

Se trataría de trabajar sobre un fichero que podemos denominar MOMENTOS.

En cada momento, un operario estará en un lugar, y ese lugar contará con un operario. Como es lógico, solo existirán los momentos de actividad, siendo los de inactividad aquellos que no existen.

El fichero tendría al menos cuatro índices:

1º/ OPERARIO+FECHAini+HORAini+FECHAfin+HORAfin
2º/ LUGAR+FECHAini+HORAini+FECHAfin+HORAfin
3º/ OPERARIO+FECHAfin+HORAfin
4º/ LUGAR+FECHAfin+HORAfin

El primero ofrece dónde está el operario, cuándo empieza y cuándo termina. (No lo he escrito al revés: tengo operario y tiempos, y en el 2º campo/índice tengo el lugar).

El segundo ofrece qué operario ocupa el puesto, cuándo empieza y cuándo termina. (Idem).

El tercero, cuándo estará el operario libre.

El cuarto, cuándo quedará el lugar libre.

Todos estos datos se refieren a UN MOMENTO CONCRETO. Si quiero saber la disponibilidad de un operario o lugar, busco hacia atrás en los índices 3º y 4º respectivamente. Y si quiero saber el tiempo de trabajo de un operario o lugar, tengo los índices 1º y 2º. Estos índices también me permiten conocer los “huecos”; y a la vez, saber si está ocupado un operario o lugar a determinada hora, impidiendo cualquier solapamiento. (Cuando hablo de “hora”, se supone HH:MM:SS)

Para momentos que superen la jornada sería preciso establecer un horario de trabajo, que puede ser individual o colectivo: si la jornada es de 8:00 a 16:00, un trabajo que comienza hoy a las 15:00 y dura 3 horas, terminará mañana a las 10:00.

Cada registro contaría también con otros campos descriptivos si hiciera falta.

Thank you!