EN DE
Clarify a planning question

Method

Method: from material flow to system responsibility

Tidira's method is designed for phases in which requirements are still moving but decisions are already being made. The aim is to make operations, building constraints, automation scope and system ownership clear enough for the next project decision.

01

Set the operating baseline

Flows, volumes, load carriers, handling classes, exceptions and constraints are captured so the assumptions behind the concept can be reviewed.

  • Material-flow and process baseline
  • Load carriers, storage logic, buffers and returns
  • Open points, assumptions and decision log
02

Translate logistics into building requirements

Material flow is converted into spaces, routes, docks, shafts, clear heights, floor loads, staging areas and expansion reserves.

  • Docks, shafts, clear heights, floor loads and fire compartments
  • Staging, vertical logistics, traffic and expansion reserves
  • SIA-phase-compatible planning input
03

Define system and supplier boundaries

ERP, SAP EWM, Microsoft Dynamics 365 Business Central, WMS, WCS, MES, MFS/MFC and automation suppliers receive clear responsibility boundaries.

  • System boundary and responsibility matrix
  • Labels, handling units, master data and quality status
  • Exceptions, confirmations and evidence ownership
04

Prepare decisions, tests and acceptance

Tender inputs, scoring logic, FAT/SAT/SIT/UAT structure, cutover and handover criteria are prepared so decisions can be taken on evidence.

  • Tender and supplier comparison baseline
  • Test strategy and acceptance evidence
  • Readiness gates, cutover and hypercare structure

Outputs used in decisions

Typical outputs include material-flow baselines, layout comments, system-boundary matrices, supplier clarification logs, test structures and decision notes. They are prepared for workshops, tenders and gate decisions.

See experience