Coming soon
PrecisionDCOS Reference Architecture Library
A controlled collection of composable architecture briefs that translate the PrecisionDCOS product family into repeatable operating patterns for major critical-infrastructure and compute environments.
- Access
- Open access
- Resource type
- Reference architecture collection
- Primary audience
- Owners, developers, architects, engineers, operators, EPCs, integrators and solution partners
- Product scope
- All PrecisionDCOS components
Repeatable without becoming generic
Use a common operating architecture, then adapt it through the Basis of Design.
The PrecisionDCOS Reference Architecture Library will provide reusable operating patterns for common facility, compute, network, connectivity, security, data and assurance environments.
Each brief will identify the project context, assumptions, selected PrecisionDCOS components, retained customer or OEM systems, monitoring authority, local and hosted roles, network zones, data paths, failure behavior, service responsibility, acceptance and lifecycle considerations.
The library is intended to accelerate discovery and design review. It will not replace site investigation, engineering, hazard analysis, customer standards, code review, detailed design, approved submittals or commissioning.
A reference architecture is a governed starting point—not a preapproved project design.
Initial library families
Architecture briefs will be organized by operating environment.
Composable across adoption patterns and authority tiers
AI and HPC campuses
High-density compute environments with liquid and air cooling, accelerator and fabric monitoring, management and OOB networks, carrier backhaul, customer and cluster boundaries, 24/7 operations, security and evidence. Variants: pilot or initial pod; multi-hall campus; remote high-density site; local NX, hosted NX-Cloud and hybrid monitoring; customer-authoritative fabric with PrecisionDCOS operating integration.
Cloud and colocation
Multi-tenant or enterprise data centers requiring facility and customer-management boundaries, carrier ecosystems, access and visitor control, service desk, DCIM/CMMS integration, customer evidence and portfolio operations. Variants: single-site colocation; regional portfolio; customer-managed suite; managed overlay on existing BMS, DCIM and security platforms.
Digital-asset and ASIC compute
Large repeatable electrical and thermal loads with container, modular or building-based infrastructure, remote operations, fleet monitoring, network and power dependencies, security, field service and asset lifecycle. Variants: modular container campus; building-based deployment; utility-adjacent or behind-the-meter site; customer-led and fully managed operating models.
Private and industrial compute
Enterprise, research, manufacturing, utility, process or industrial facilities combining compute with OT, physical I/O, local autonomy, private networking, controlled remote access and customer-specific assurance. Variants: private enterprise compute; industrial edge or plant compute; air-gapped or sovereign local NX; managed overlay on customer OT and corporate standards.
Utility and energy-integrated infrastructure
Data centers and compute facilities integrated with microgrids, onsite generation, BESS, utility interconnection, electrical protection, gas systems and energy-management platforms. Variants: islanded or limited-grid microgrid; utility-interactive campus; generation-adjacent compute; mixed-OEM generation and independent protection; monitor-only PrecisionDCMS with separate EMS and P&C authority.
Modular and remote sites
Small or rapidly deployed sites with constrained staffing, packaged power and cooling, cellular or limited carrier access, local protection, OOB recovery, pre-staged racks and centralized operations. Variants: PrecisionDCMS Field Standalone; Field + NX-Cloud; NX-Cloud Only with independently monitored facility systems; rack-based site edge; remote-hub connectivity.
Consistent technical format
Every architecture brief will answer the same operating questions.
- 01
Use case and operating objective
Environment, scale, stakeholders and outcome
- 02
Assumptions and exclusions
Conditions that make the pattern valid
- 03
Selected components
PrecisionDCMS, Network, Connect, Secure, Operations, Data Fabric, Assurance and Cloud roles
- 04
Retained systems
Customer, OEM and third-party systems that remain authoritative
- 05
Monitoring authority
Field, local NX, NX-Cloud or another accepted source
- 06
Authority schedule
Read, acknowledge, administer, approve, command and protect
- 07
Physical architecture
Site, rooms, racks, enclosures and failure domains
- 08
Network zones and conduits
OT, OOB, campus, security, customer and edge paths
- 09
Connectivity
Carrier, hub, Internet, cloud, customer and recovery paths
- 10
Data architecture
Sources, quality, historian, event ledger, APIs and datasets
- 11
Security architecture
Physical and cyber control boundaries
- 12
Operations
NOC/SOC, service desk, CALS, field response and operating tier
- 13
Failure and degraded modes
Node, path, source, site and hosted impairments
- 14
Acceptance
FAT, SAT, commissioning and operational-readiness gates
- 15
Shared responsibility
Customer, PrecisionX, provider, OEM, partner and assessor roles
- 16
Order-specific decisions
Items that must be resolved in the Basis of Design
Discovery accelerator
Compare the pattern to the project, then record every difference.
- 01
Select the closest environment
Choose the family that most closely resembles the project's operating conditions.
- 02
Review assumptions
Confirm which scale, interface, staffing, network, safety and customer assumptions are valid.
- 03
Mark retained systems
Identify BMS, EPMS, EMS, DCIM, CMMS, ITSM, VMS, PACS, network, carrier and customer platforms that remain.
- 04
Select authority and deployment
Determine Field, local NX, NX-Cloud, full-stack, overlay, hybrid and operating-tier choices.
- 05
Record deviations
Capture every site, customer, code, vendor and service difference rather than silently editing the reference.
- 06
Develop the Basis of Design
Convert the accepted pattern and deviations into project-controlled requirements.
- 07
Validate through acceptance
Test the resulting configured and installed system; do not “accept by reference.”
Reference is not evidence of a customer deployment
Distinguish architecture patterns from case studies and performance claims.
Library entries are reference architectures and illustrative scenarios unless PrecisionX has documented customer permission, verified implementation evidence and an approved public case study.
Do not add fictional customer names, logos, quotes, installed capacities, availability results, savings, timelines or certification claims. Do not describe a proposed or lab architecture as “deployed,” “proven in production” or “used by leading operators” without controlled evidence.
- Reference Architecture
- A reusable engineering and operating pattern
- Illustrative Scenario
- An example showing how the pattern may be applied
- Validated Configuration
- A configuration tested within a defined accepted envelope
- Customer Case Study
- A separately approved public record with customer permission and evidence
Controlled release
Publish complete briefs rather than placeholders.
The library is being prepared in controlled stages. Do not publish an empty card, fabricated PDF, draft file, countdown timer or unsupported release date.
A resource becomes available only when its scope, assumptions, diagrams, terminology, authority boundaries, technical review and access level are complete. Public, request and NDA access may differ by architecture and detail.
- Environment family
- Greenfield, brownfield or hybrid
- Local, hosted, hybrid or private
- Field, NX or NX-Cloud pattern
- Customer-led, co-managed or fully managed
- Full-stack, managed overlay or hybrid modernization
- Single site, campus or portfolio
- Public, request or NDA access
- Primary operating domain
- Reference Architecture, Illustrative Scenario, Validated Configuration or Customer Case Study
Planned search and filters will be enabled only when released content exists; zero-result filter categories are not shown before content exists.
Register the environment you are evaluating
- Tell us which architecture family and decision stage matter to you
- PrecisionX will record the request
- An active project may be routed to an architecture review before the general library release
Frequently asked
Questions and answers
- When will the library be released?
- The page does not publish an unapproved date. Entries will be released as their technical review, diagrams, assumptions, access classification and supporting records are complete.
- Can a project use a reference architecture before the public library launches?
- Yes. An active project can request an architecture review. PrecisionX may use controlled reference material within the appropriate project and confidentiality boundary.
- Is a reference architecture a final design?
- No. It is a starting pattern. Site, customer, code, utility, carrier, hazard, OEM, scale, authority, responsibility and lifecycle requirements are resolved through the project Basis of Design and detailed engineering.
- Will the library contain case studies?
- It may include separately approved case studies when customer permission and controlled evidence exist. Reference architectures and illustrative scenarios will be labeled clearly and will not be presented as customer deployments.
- Will every architecture be publicly downloadable?
- Not necessarily. Access will depend on technical depth, security sensitivity, customer or provider information and document maturity. Each released item will show its access state.
Related resources
PrecisionDCOS Platform Overview
Review the product family and common operating contract behind every architecture.
Read resourcePrecisionDCMSField vs NX Selection Guide
Select the PrecisionDCMS monitoring authority used within a reference pattern.
Read resourceArchitecture BriefsAuthority and Safety Boundary Brief
Apply consistent read, command and local-protection boundaries.
Read resourceApply the reference model now
An active project does not need to wait for the public library.
Describe the environment, stage, scale and decisions in front of you. PrecisionX will route the request to an architecture review or the appropriate controlled reference material.