OPTANO Architect II

The OPTANO Architect Story continues. Today, we want to take a closer look at the workflow of this application. During our research we noticed that it has something in common with movies and the theater. Curious? Then read on…

The story so far…

In our last blog entry, the-optano-story-optano-architect-part-1 ,we focused on the advantages of this application as one of the five components of 360° OR intelligence on the OPTANO platform: based on the platform’s technology, OPTANO Architect profits enormously from its flexibility.

OPTANO Architect – fast and effective

In part two of our new series, the spotlight is on this main actor and its acting abilities – because OPTANO Architect has its very own talents. It is the ideal choice when there is little time to introduce optimization software but the demands are still high. It develops data and optimization models rapidly. The result is a high-performance software which is an ideal instrument for consultants and optimization experts since it doesn’t require any prior knowledge in programming and it doesn’t take up precious time.

The OPTANO Architect workflow – a three-act show

Just like in many movies and theater performances, OPTANO Architect’s workflow is divided into three parts. In dramaturgy, these are known as acts –typically “exposition”, “development” and “denouement”. In the OPTANO Architect workflow these three acts are: “definition of a data model and views”, “the integration of optimization models” and “customizing”. These are dealt with in more detail below…

In step one of the workflow, we define the data model* and views. This includes defining entities, relationships and attributes. The business analyst/modelling experts decide which entities are to be a component of the master data and scenarios and also which of these are to be permanent for all scenarios. Views (tables, columns, sequences, pivot charts, charts, etc.) and their position in the navigation are also specified.

Definition Default Architect

Diagram 1 – Definition of a data model and default view


Default Architect

Diagram 2 – Completed default view


In step two, we integrate the optimization model. This can be an optimization model that is already available or a new one. In order to support the development of a model as best as possible, OPTANO generates a template based on the data model. The developer can thus focus on the modeling itself and doesn’t need to invest any time in the database connection.

Step three of the OPTANO Architect workflow – customizing – is optional. Software developers can make customized  adjustments such as adding interfaces to other programs. Here, the custom code and the code generated by OPTANO remain separate from one another. Subsequent changes in OPTANO Architect are then integrated into existing projects automatically so there is little work required at a later date.

Take a bow -the curtain falls!

And the audience is enthralled! With OPTANO Architect we wanted to develop an application which impresses customers with its rapid optimization results. And we’ve done just that : using OPTANO Architect enables consultants and optimization experts to focus solely on data modeling. Data collection and storage is easier and timely data validation is possible. Thanks to this, we’re sure that consultants will receive a round of applause from their customers at workshops.

And while we’re on the subject of movies, here’s the right film to go with OPTANO ARCHITECT: