Additional bookings
Availabilities, additional information and coordinated steps around your booking process.
Plugin development · 06 / 06
Your industry has its own processes. I complement booking, administration and specialist systems with the function that fits it.
Services and project questions in detail
Availabilities, additional information and coordinated steps around your booking process.
Own fields, overviews or exports for the information your team needs on a daily basis.
Transfer information between industry-specific programs and other applications, as far as suitable interfaces are available.
A possible example
For a booking, your team needs special information or a suitable resource. An extension brings this information together and prepares the date for further processing.
You show me a typical process and your specialist system used. I check possible extension points, the required data and limits of the system. This results in a clearly defined first step.
Services in detail
An industry solution already covers many tasks. Sometimes, however, exactly the connection to a special form, resource or internal release is missing. An individual addition addresses this specific bottleneck and takes into account the possibilities of the existing specialist system.
An appointment may require additional information, qualifications or a specific resource. We go through the process from the entrance to the conclusion. This makes it visible which information remains in the specialist system and which data should provide a supplementary interface.
Documented interfaces, extension points or regulated export routes determine the scope. If a direct extension is not provided, a separate tool may be suitable. The chosen route should enable traceable data transfers and be compatible with the operation of the specialist system.
Technical implementation
An industry expansion must take into account the special rules of your company and at the same time fit into the existing specialist system.
A term such as released, booked or completed can mean something different for each system. We assign conditions and mandatory information to a specific process. Exceptions are described with examples before new rules are implemented.
Documented interfaces, manufacturer conditions and used versions determine the possible intervention. We check which data can be read or changed. Common identifiers connect the extension to the existing data sets.
If a connection fails, it must remain clear which step has already taken place. Logging, manual post-processing and later voting are scheduled. An introduction in stages facilitates the comparison with the previous technical process.
Helpful are the name and version of the specialist software, typical special cases, manufacturer documentation and a complete example process.
Which of these questions is crucial for your project? Briefly describe your process and the existing systems.
Discuss technical requirementsThis depends on the provided extension points and interfaces. If no direct intervention is possible, we check suitable supplementary tools or regulated data paths.
Often a targeted supplement is sufficient. I first check how the desired process can be implemented with the existing system.
A typical process with inputs and outputs is a good start. Also helpful are the places where you manually supplement, ask or collect data again today.
This is possible if data access and technical rules allow it. We clarify shared resources, site-specific responsibilities and the visibility of processes before a common overview is created.
Changes to interfaces or data formats may require adjustments. The relevant transfers and appropriate test procedures shall be documented. Responsibility and scope of subsequent maintenance are agreed separately.
A description of the system, a typical sequence and available interface documentation. Often a sketch with inputs and outputs already shows, where today double recording or manual reworking is carried out.
Describe your industry, your system and a typical process.