PLANNING

Service support overview

System Planning & Concept Design takes the transformation themes defined in IT / Digital Strategy and similar initiatives and shapes them into business and system initiatives that can actually be executed. We structure current issues and lay out the To-Be for business and systems, the system scope, the core structure of functions, data and integration, investment estimates, and the migration approach. Our goal is to take the concept down to a level of detail at which requirements definition, RFPs and design can begin.

Areas we support

In each area, we go beyond listing support themes. We make clear how Dirbato frames the issues and how we connect them to concepts and decisions, and then translate that into concrete work.

• Current-state analysis and issue structuring

  We do not treat a comprehensive inventory of current business processes and systems as an end in itself; we analyze them to clarify why change is needed. Working across business, systems, data and operations, we separate symptoms from causes and sort out the issues the future concept must solve and the constraints to be accepted as given.

  • As-Is business and system visualization
  • Issues, causes and impact
  • Stakeholder requirements
  • Constraints and assumptions

• To-Be business and system concept

  Rather than starting from replacing current functions, we work backward from how future business, customer experience and decision-making should look to define the capabilities required. Instead of designing business and systems separately, we draw roles, business functions, system functions and data flows as one picture to create the overall To-Be.

  • To-Be business processes
  • Business and system functions
  • Division of responsibilities
  • To-Be system overview

• System policy and scope design

  Rather than systematizing every request, we distinguish what should remain as business practice, what should be standardized through systems, and what can make use of existing assets. Comparing value, feasibility and future potential, we decide what to change, keep or retire, including Build / Buy / Reuse and standardization versus customization.

  • In scope / out of scope
  • Build / Buy / Reuse
  • Standardization and customization
  • Continue, renew or retire

• Grand design of functions, data and integration

  Before deciding on specific products or technical approaches, we fix the overall structure at a level that keeps later design decisions from becoming locally optimized. We organize business and system functions, ownership of key data and information flows between systems, and clarify the technical issues to be explored in depth with Technology Advisory.

  • Function allocation and key components
  • Conceptual data model
  • Information flows / interfaces
  • Basic policy for non-functional requirements

• Modernization and migration concept

  Instead of a binary choice between full replacement and life extension, we assess current assets by function, data, technology and operations, and decide what to keep, change or retire. Starting from business continuity and migration risk, we build up renewal units and design a migration scenario that delivers value step by step. This area covers renewal units and migration scenarios for the target theme; whether the chosen technical approach is viable is validated together with Technology Advisory.

  • Renewal and cutover units
  • Data migration
  • Parallel operation
  • Phased migration scenario

• Investment estimates and execution roadmap

  Our goal is not simply to complete a concept document, but to make it concrete enough that decisions do not have to be revisited in the next phase. We lay out the investment, benefits, dependencies and risks for each delivery unit, define the project breakdown and execution sequence, and make explicit the decisions and open issues to be handed over to the RFP and requirements definition. We also organize the RFP structure and evaluation criteria, the proposal evaluation axes and the vendor selection process at a level of detail that avoids reopening the discussion later.

  • Estimated costs and benefits
  • Project breakdown
  • Dependencies and roadmap
  • RFP and evaluation criteria design
  • Vendor selection process

Methodology & evaluation framework

System planning and concept design is neither a redo of higher-level strategy nor the selection of products or technical approaches. We confirm the objectives and constraints of the target theme, structure the current state, define the To-Be and execution scope, and then connect it to the next phase.

Deliverables

Our deliverables do more than describe a future state; they are structured as decision-making material from which requirements definition, RFPs and design can begin.

Support style

Not a concept document, but a state ready for the next decision

The goal of system planning and concept design is not to draw a polished picture of the future. We clarify the full picture of business, systems and data, along with the scope of change, investment, migration and remaining issues, so that the next phase of requirements definition, RFPs and design can begin. Issues that require specialist judgment are addressed together with Technology Advisory and Security.

Why clients choose Dirbato

Dirbato does not stop at drawing a system concept. We translate management and business requirements into a concrete picture of business and systems, carry it through to investment, migration and the roadmap, and support you until it connects to requirements definition, RFPs and design.