Platon A/S 2006-2007


Consultant

Timeframe and context

Period
August 2006 through March 2007.
Work form
On site.
Location
Østerbro, (projects in Humlebæk and Ballerup).
Role
Consultant.
Interfaces
Primarily other consultants, as well as the client's relevant stakeholders.

Pitch

During the period from August 2006 through March 2007, consultancy work was delivered from Platon A/S. Tasks ranged from data conversion based on legacy code to establishing a reporting foundation for a payment system. The work was performed on-site (based in Østerbro with projects in Humlebæk and Ballerup) within a setup where deliveries were driven by collaboration with other consultants and client stakeholders. In practice, the focus was on transforming data and making it usable in client environments—even when prerequisites were unclear, tools were missing, or the history lived in code that no one could anymore read.

Key outcomes

Work in detail

Background and goals

The task was solved as a consultancy delivery from Platon A/S during the period from August 2006 through March 2007. The purpose was to make data usable for reporting and further processing in client environments. Deliveries in practice ranged from classic reporting support to very pragmatic data conversion, meaning the focus was not on building something new and polished, but on making something concrete work in a reality of existing logic, limited prerequisites, and a need to deliver without starting over every time.

Coloplast (legacy code, DataStage, and data conversion)

At Coloplast, the task began with legacy code that had to be read and understood because it functioned as the actual recipe for how data had previously been converted. Since neither language knowledge nor original software was necessarily available, the solution became translating the existing logic into DataStage transformations. This ensured data could be transformed into a database in a way that continued the existing conversion method, without the goal of establishing an actual data warehouse.

ETL, data integration, and transformation logic

The task included ETL and data integration, where transformation logic needed to be clear enough to be maintained and adjusted. Consequently, the work involved ensuring data flow was correct and stable while simultaneously working with data modeling and optimization to prevent solutions from becoming unnecessarily heavy or complex once in operation.

KMD (reporting solution for payment system)

At KMD, work was performed on a reporting solution linked to a system for the payment of public funds for municipalities. The data foundation was modeled using Platon's "hub and spoke" data model, allowing reporting to be built on a consistent structural foundation without inventing details about the system's internal domain model or specific reporting requirements not provided.

Collaboration and delivery format

The work was performed on-site (based in Østerbro with projects in Humlebæk and Ballerup). The primary interfaces were other consultants and client stakeholders, which suited tasks where clarifications, prioritizations, and changes are often decided in dialogue close to the solution, and where deliveries must be finalized quickly without losing structure and traceability.

Technologies

Primary

Company

Platon A/S was a consultancy firm specializing in delivering solutions within IT (including database management, integration, and development). The company described its focus as helping organizations optimize data processing and the decision-making foundation through data solutions and technological advice.