Deployment
From the testbench to the portfolio.
Choose where Nimrod runs, from a local workstation to a cloud instance or an on-premises data center.
The right place to run Nimrod depends on the systems it needs to reach and the people who will use it. A local testbench, a building workstation, and a portfolio deployment have different network and infrastructure requirements.
The operating model remains useful across those arrangements. Choose the deployment boundary around your connectivity, administration, and governance needs, then configure the hosts and resources that connect the facility data.
Start at the bench or in the building.
Nimrod Manager provides a local starting point for development and testbench work. A workstation connected to automation devices lets an engineer explore an integration near the systems being configured.
The same local approach can place the application on a building network, with a workstation connected alongside its controllers and other network participants. Plan the network reachability and host resources around the intended operating workload.
[ 04 / FLEXIBLE DEPLOYMENT ]
Run it where
you need it.
A laptop at the bench. A workstation in the building. Campus networks or individual devices connected to the cloud. Your own data center. Choose the setup that fits your operation.
The saved five-option deployment illustration: local development, a building workstation, campus cloud, individual devices in multiple buildings, and an on-premises data center.
Connect a campus or individual devices to the cloud.
A cloud instance gives a distributed team a shared application endpoint. A campus connection can use BACnet/SC through a configured hub; individual devices in different buildings can also participate in an appropriate SC arrangement.
The drawings show the SC hub as the connectivity endpoint beside the Nimrod server. Cloud placement does not remove the need to configure device enrollment, certificates, and the network paths required for the chosen topology.
Use your own infrastructure when required.
An on-premises data center is another deployment option for organizations that need the application within their own infrastructure. Portfolio access, site connectivity, and operational responsibility should be considered together.
Discuss an enterprise deployment in terms of the facilities being modeled, the sources being collected, the people who need access, and the standards the organization needs to maintain. Those requirements help shape an appropriate deployment plan.
Keep administration and operations within reach.
Nimrod Cloud brings account access, cloud instances, provisioning, and approved downloads into one place. BACnet/SC hub management, enrolled nodes, and instance bindings support the connectivity side of that operating picture.
Start by downloading Manager for local work, launching a cloud instance, or contacting Nimrod about enterprise requirements. Detailed configuration and approved software remain available through a Nimrod account.