How to organize the work of the dispatcher?

Question

Database

Good day.
It is necessary to somehow organize the work of the dispatcher, there are 7 jobs, in a separate room a personnel officer and an accountant at their desks. It is necessary to organize the work so that dispatchers can work with a single database, which is planned to be on a separate local server.
At the moment I plan to try 1C-Management of a small enterprise, it suits, and there are contractors there, just what you need. It is with this database that dispatchers will work. But as far as I know, you cannot work with one document at a time. That is, I have no idea how to organize it all. Putting a copy of the database on each computer is not an option. It is constantly replenished and running to update is a headache.
Perhaps there is another software (advice is welcome), how the dispatchers work and all this is organized, alas, I don’t know, the search did not give a particular result.

Answer 1

1C controls versions of objects.
For example, employees A and B opened a document. Changes were made, then employee A wrote it down. The version of the object in the database has changed. When B. presses "write", 1C will compare the version that B. has with the version in the database and, if they do not match, it will give an error and will not allow writing. This is standard behavior. It can be reprogrammed.
If you have data that is associated with the counterparty (for example, the dispatcher records the time and essence of the last call to the counterparty), then these data can be written to another table (information register / directory), indicating a specific counterparty there. Then there will be no problem with version conflict.
You need a more specific description of the task, then, perhaps, I will advise something else.

Answer 2

As I was taught in her time, in order to draw up a competent technical task for software, the developer must sit next to the user and see how everything really happens (and not in the customer’s head) for a day or two. After that, the developer submits his proposals and, together with the customer and users, brings them to a competent technical task.
If you do not know how users work, then you cannot offer them anything worthwhile.