A design your team can use.
Decide whether AKTDesign™ fits your next engineering decision.
Good fit
New facilities, migrations, or operating plants that need an agreed design before implementation.
What you receive
The agreed architecture, specifications, and acceptance criteria for your project stage.
Operating boundary
Design and owner-side engineering support. Implementation and managed operations are separately scoped.
Two drawings. One operating reality.
A process drawing shows what the plant must do. A control-network drawing shows the systems and access paths that can influence it. Read together, they give security its operational context.
Trace the loop. Follow the instrument, controller and final element as one function.
Trace the access. Identify the engineering sessions, services and connections that can change that function.
Specify the boundary. Translate approved access into a documented, testable design decision.
02 / Define the boundaries
One plant. A more deliberate architecture.
Watch the flat network become an illustrative design with zones, controlled crossings and monitoring. Explore five phases, eight example zones and ten numbered conduits. The findings and schedule explain the design decisions.
The drawing plays when visible. Select a phase to pause and explore it, or choose “Zoom for labels” for a closer look.
Illustrative architecture, not a customer plant or a universal blueprint. Zone boundaries, safety interfaces, read-only paths and any one-way enforcement must be specified and validated for the application. Monitoring and managed operations shown here are separately scoped services.
03 / Make the design buildable
From architecture to a specification your team can build against.
We support the owner’s engineering team or work alongside your integrator. The scope is agreed around the project stage, operating constraints and interfaces that need a decision.
Control system architecture and specification
Control narratives, controller and I/O architecture, redundancy, failure behaviour, operator interfaces and the requirements used to procure DCS, SCADA or PLC systems.
Industrial network and segmentation design
Zones and conduits, industrial DMZ services, topology, traffic flows and configuration requirements informed by ISA/IEC 62443 and the needs of the operation.
Safety interface and independence
Safety-system separation, engineering access, bypass management and interfaces reviewed with the functional safety engineer.
Identity, access and remote support
Identity, approved remote-access paths, session boundaries, access ownership and revocation requirements for maintenance and support.
Data, historian and edge architecture
Historian replication, edge placement and defined enterprise or cloud interfaces, including dependencies and the controls each path requires.
Factory and site acceptance testing
Security requirements expressed as acceptance tests, with evidence, pass criteria and a process for recording outstanding items.
Deliverables
The decisions become a usable drawing set.
An agreed package of documents connects the design intent to procurement, testing and handover.
Functional and security design specification
Control philosophy and security requirements written together, with responsibilities and design assumptions made explicit.
Network architecture and zone model
Architecture drawings, zone boundaries and a conduit register describing approved flows, direction, purpose and ownership.
Safety-interface review and action register
Safety-system separation, engineering access and bypass management reviewed with the functional safety engineer, with the actions and their accountable owners recorded.
FAT and SAT security test schedule
Witnessable tests, pass criteria, evidence requirements and a punch list for unresolved items at handover.
04 / Choose the right moment
The same requirement. Different work at each project stage.
Watch the short film, then select a phase to see what can still be decided. Earlier decisions can avoid later rework; the actual cost and timing depend on your project.
What can still be decided
Architecture options, zone strategy, external interfaces, safety-system dependencies and the requirements that inform supplier selection.
What a change costs here
A change is usually handled in design work before major commitments, subject to the project scope and estimate.
Illustrative project stages. Contract scope, design maturity, safety review and operating windows determine the work required.
Fit
Start with the decision your project needs next.
AKTDesign™ is relevant when
- A new plant, unit or migration needs architecture and security requirements before procurement.
- An integrator or equipment supplier’s design needs an owner-side technical review.
- An operating plant needs a target architecture and a migration plan that respects its change windows.
Start elsewhere when
- You first need to understand operational exposure — explore GoSecure™.
- The design is agreed and you need help implementing controls — explore AKTSecure™.
- You need ongoing monitoring and response — explore InnovAKT Shield™.
Before we start
Practical answers for your project.
What does an AKTDesign™ engagement include?
The scope can include control-system specifications, network architecture, zones and conduits, access design, safety-interface review and acceptance criteria. We agree the deliverables around your project stage and the decisions you need to make.
Can you work on an existing plant?
Yes. We can define a target architecture and a phased migration plan around the plant’s operating constraints, maintenance windows and change process. The implementation scope is agreed separately.
Will you work with our integrator and chosen suppliers?
Yes. We can support the owner’s engineering team or work alongside your integrator, reviewing designs and writing requirements against the agreed project scope. Commercial authority and approvals remain with the client.
Does AKTDesign™ include the monitoring shown in the sketch?
The illustration shows how the design can connect to monitoring and managed operations. AKTDesign™ defines the architecture and requirements; implementation, monitoring and managed services are scoped separately.
Does the drawing represent a required or certified architecture?
No. It is an illustrative design, not a customer plant or a universal blueprint. The right boundaries and safeguards depend on the process, risk assessment, operating needs and applicable requirements.
How much does designing security in early save?
There is no universal multiplier. Earlier decisions can reduce rework and procurement changes, but the effect depends on design maturity, contract terms and operating constraints. We explain the assumptions for your project.
Can you work to our standards and engineering requirements?
Applicable standards, client specifications, acceptance criteria and responsibilities are agreed at scoping. The client retains its obligations. Where a licensed engineering sign-off is required, the role of the engineer of record must also be agreed.
What do you need to start?
Your project stage, the decision you are facing and the operating constraints are enough for a first conversation. We can then agree which available drawings, specifications or studies would be useful to review.
Next step
Let’s define your next design decision.
Tell us where the project stands, what needs to change and the constraints your operation must respect. We will help establish a practical starting point and the information needed for a useful review.