So why run MODS?
Roaming is typically handled by people with mixed competences that are placed in different parts of the organisation. IREG testing is an engineering task, TADIG a IT/Billing task, Roaming management might be product management and ensuring everybody involved does the right ting means that a common repository for priorities, directions and status is maintained. In most cases, a simple Excel file on the LAN is the solution.
We all know the problems that Excel file on LAN brings - only one person at a time can have write access, and what is the IREG team wants to report progress if the roaming coordinator had it open while leaving the office for the day.
The other option is that everybody maintains their own file, with regular coordination meetings. Keeping versions in sync is then the challenge and new instructions on priorities aren't propagated until the next meeting.
The solutions can be as complex as you like, but MODS has been built to accommodate:
- A coherent view for all participants on priorities, status and progress
- A multi-user environment where all users can read and write data
- An application on top of a database, as that enables reporting from an arbitrary set of criteria in the database
- A database that doesn't require any dedicated hardware nor software. Database servers are expensive and this is quite unnecessary for a small application and small volumes
With a common interface to a database, it's possible for persons in different parts of your company