Our goal is to create an application that covers all operational processes currently not covered by our ERP and accounting software. For this, we are using the LOW CODE application TABIDOO, which consists of tables (with a database in the background) and scripts through which we define business processes if a certain level of automation is required. Initially, we would organize training sessions to introduce the system's usage and briefly explain the rules we follow to ensure a more or less standardized approach. https://tabidoo.cloud/en
Business processes are divided by departments and by tasks performed. This means that, for example, a project task would actually encompass the execution of business processes for a department of the company, such as marketing. Attached is a diagram of how the business process roughly looks.
Everything below THEATRICAL BUDGET PLANNING belongs to the marketing segment of the business.
The list of tables we minimally need (the list of fields and data, as well as statuses indicating the step of automation, will be defined through communication and user preferences):
- CAMPAIGNS BOOKING
- PRODUCTION ORDER – This is already done as part of another module and just needs to be connected
- DELIVERY ORDER – This is already done as part of another module and just needs to be connected
- INCOMING INVOICES – A primitive form of registering incoming invoices where invoice items with corresponding data are linked to planned amounts
- P&A CAPACITIES
- MEDIA MATERIAL LIST – This is already done as part of another module and just needs to be connected
- LICENSOR REPORT 1 – Report in table form with the ability to save in several different templates
- LICENSOR REPORT 2 – Report in table form with the ability to save in several different templates
- EVENTS PLANNING
- LICENSOR APPROVAL – It can be a table or just a status or trigger
- COSTS & EFFECTS ANALYSIS – Table or report
The attached diagram shows the relationships between tables, and since each table more or less represents the movement of data from table to table and vice versa with its recordset and document of the same name, it is controlled through the status of the recordset or document. The status is also tracked on the recordset if it has also been transferred to another table or the next step in the process or another document.
In addition to operational tables, we also have tables that are essentially code lists, which are also shown in the diagram below:
- MEDIA GROUPS
- ADVERTISERS CRM
- DELIVERY DEADLINES