Network mapping
Record the connections into your critical systems, who owns them and what depends on them.
Where your Control design is engineered. For your environment, not a template.
Control Studio is Firevault's design and engineering environment. It is where we map your critical connections, choose the Control Plans that fit, decide where physical control applies and document the design your teams will rely on.
Map the connections
Select the Plans
Place the Modules
Document the design
01 · What Studio does
From your network to a design you can deploy.
Modules are the technology, Plans are the solutions and Blueprints show the industry context. Studio is where Firevault brings them together for one customer environment.
Control Plan selection
Match each connection problem to the Control Plans that address it.
Module placement
Decide where physical control applies, and which Modules suit each connection.
Operating-state assessment
Agree each connection’s normal state, who can change it and what must keep running.
Deployment documentation
Produce the design, acceptance checks and records your teams will work from.
02 · A fictional example
Northbrook Water, before and with Control.
Northbrook Water is an invented utility. Its suppliers, engineers and business systems all have routes into treatment operations. This is the kind of concept view Studio produces publicly; the full design stays with the customer.
Concept view · Northbrook Water (fictional)FromSuppliers and business IT
- Supplier remote supportAlways connected
- Vendor modem at a pumping stationAlways connected
- Business IT to operationsAlways connected
- Telemetry and local controlStays connected, assessed
ToTreatment operations
Relay
Lock
IsolateA simplified concept, not a network design. Device placement, connections and operating sequences are designed for your environment in Control Studio.
Request a Studio design sessionFictional organisation. The view is simplified and does not represent a real network or a recommended configuration.
03 · Who sees what
Three levels of access.
We publish the intelligence that earns trust, not the intelligence that makes our expertise easy to replicate. Studio separates what is public, what is yours and what stays with Firevault engineering.
Demonstrations
What you can see on this website.
- Simplified Before / With Control concept views
- Fictional or anonymised examples
- The Plans and Modules that may apply
Approved customer access
For organisations working with Firevault on their own design.
- Your network map and selected connections
- Your Control Plans and operating states
- Your design and deployment documentation
Firevault engineering
Kept within Firevault engineering.
- Reference designs and templates
- Selection rules and validation logic
- Configuration and project engineering outputs
04 · Your next step
Bring one critical connection to a Studio design session.
Customer access to Control Studio is not open yet. Today, Firevault engineers run Studio with you in a design session and share the outputs that belong to you.