Digital Creek references

The company uses several online marketing tools that needed to be integrated with the ERP system.

• Sale
• Warehouse management
• Built-in CRM
• Attendance list
• Event-based emailing (users can edit email templates that are sent to customers when a specific event occurs; the template is populated with the customer's data)
• Receivables management
• Dynamic product pricing (based on campaigns and other conditions, the price changes automatically)

• Facility Management
• Office management
• Warehouse management (office supplies, such as printers, chairs, etc.)
• Booking optimization (for short-term bookings [hours, days], customers don't care which office they get, so the system tries to pack them tightly to maximize utilization
• Cleaning planning
• Invoicing
• Complex authorization system (managers, receptionists, cleaners, etc., each with different rights to view and edit data)

As part of an extended outsourcing/nearshoring operation of a German group, several software and infrastructure teams were to be established in Budapest at the same time. More than 30 positions were transferred or newly filled.

The resulting savings for the customer amount to approximately €864,000 per year.

The operation of a security-relevant log analyzer system was transitioned for the customer. The customer lacked the in-house expertise to operate the solution according to standards. We supported an external service provider in handling the project.

The solution was to modernize the existing table management system from COBOL/IDMS to WOLA/Java.
Migration of the IDMS data with ETL. Unloading the IDMS data into sequential files and loading the files into a staging area.

For an ongoing, temporary project, our customer needed four service support employees, a software developer and a system administrator to cover a restructuring phase and a provider change. The specifics of this requirement were that support and operations also had to take place on weekends and holidays.

Over €200,000 in total costs per year could be saved as part of the outsourcing.

Various departments of the customer had their own mission critical applications based on Informix databases. The central and operational system had already been migrated to ORACLE. There was no longer any support for the Informix databases.

An artificial interface between ORACLE and Informix had to be created. This transformation was necessary because a new data warehouse (DWH) system was being developed that had to be supplied with information from these departments, but which was actually only possible from within the ORACLE architecture.

Source architecture:
Informix databases, SQL scripts, SQL reports, shell scripts, cronjobs.

Target architecture:
ORACLE databases, ORACLE SQL, PL/SQL, ORACLE scheduler and UNIX shell scripts.

Solution:
Automated conversion of SQL scripts. Setup of the shell scripts and ORACLE scheduler. A parallel operation with automated test cases generated from a predefined template provided by the business department. Fully automated evaluation of the test results, a check whether the ORACLE results correspond to the Informix data.

Challenge:
An operating and business downtime were not allowed.

The test case and SQL converter had to be adapted. The automated test-result alignment. With each new run and each new result, 4,000 test cases had to be run automatically every day during parallel operation. The steps consisted of create, run, and check results/discrepancies.

Our role:
The analysis, design and complete implementation. The creation of the SQL converter, the test case generator and the result evaluation.

AS400 ran 5 million LOC (Lines of Code) in RPG.
The entire business was based on these programs and only a few external RPG programmers were available to support them. This created a huge dependency and there was no application or program documentation. In case of requirements by the legislator, changes had to be made in the program, which could have been done only with an enormous effort.

Architecture of origin:
Partly AS 400 and partly RPG.

Target architecture:
Technical specifications and, in some cases, technologies remain secret at the customer's request.
The system had to be documented. Emergence of a repository. Provision of various information from the repository for dynamic queries.

Challenge:
Performing analysis using Application Understanding for RPG. Tracking the lifecycles from input to output.

Solution:
Adaptation of the Application Understanding Analyzer to RPG. Then a replacement of the system by a standard software and a transformation of the legacy program.

The aim was also to simplify the feasibility of changes and maintenance. As part of this, an adaptation of the Change & Maintenance process was carried out.
The replacement of the sole knowledge carriers was targeted as part of the process, and the relocation of know-how was also a must-have for the customer.

Our role:
Performing the analysis with the Application Understanding. Bringing in additional RPG developers. The documentation of the system. The creation of a requirements and specifications document based on the analysis performed. Recommendations and advice on the adaptation of the Change & Maintenance procedure.

Three areas at the customer had to be separated organizationally. The requirement was for uniform IT support that could serve all three areas independently.

Original architecture:
The master data system was used by all IT systems. This included dynamic IDMS tables. The CiCS COBOL/IDMS/DB2 applications ran on a zOS mainframe.

Target architecture:
CiCS COBOL, Websphere (WOLA), Remote DB2 Access, Java.

Solution:
The CiCS COBOL / IDMS /DB2 application on a zOS mainframe had to be divided, so that the original application remained CiCS COBOL.
The IDMS/DB2 access module had to be changed, so that no access to the IDMS/DB2 databases happens, but everything is accessed via Websphere (Optimal Local Adapter / WOLA) Remote DB2. The maintenance was done by Java applications and the data access happened via a persistency layer.

Challenge:
Swapping the access module with access via Websphere.

Our role:
The creation of the technical concept, design and implementation.