Common capabilities
Identity and scope, policy, connectors, workflow, evidence, and verification are candidates for reuse as they are implemented and validated.
NGCC5 LLC | Platform architecture
Reuse validated capabilities. Design for the domain.
AIOP is NGCC5's intended reusable platform foundation. It connects common operational capabilities with domain-specific requirements so later products can build on work already implemented and validated.
AIOP connects the first product to the broader strategy
AIOP stands for Autonomous Intelligent Operations Platform. It is NGCC5's intended reusable foundation for domain products. The economic objective is to avoid recreating useful common capabilities for each new application.
Domain-specific work
Terminology, assets, information sources, approval rules, user needs, and operating requirements still need to be designed for each market.
The economic test
Evaluate engineering work retained, integration effort avoided, tests reused, and new work required. The objective is to improve the economics of delivering each subsequent product.
The roadmap carries this approach forward: validate capabilities in Pion, then assess their fit and economic value in each new domain.
A common foundation with controlled variation
The intended AIOP architecture combines ontology, graph, policy, connectors, execution, evidence, and verification. Together, these capabilities describe how a domain product can retain context and govern a decision through to its outcome.
- 01
Describe the domain
Define the assets, relationships, identities, observations, and evidence that matter to the product.
- 02
Define the operating rules
Specify permitted capabilities, authorization, state transitions, verification conditions, and exception handling.
- 03
Retain the evidence
Carry source context, reasoning, decisions, and observed results through the workflow.
- 04
Validate before reuse
Establish which implemented components and tests are suitable for the next domain and which requirements remain different.
These are architecture objectives. The current implementation limits are described in Pion's development status.
The operating model
One governed lifecycle, from signal to record.
The core operating model from NGCC5's Feature Guide, condensed.
Design intent · not the current build
- 01Receive signals
- 02Establish tenant, client, site, system, device, user and time context
- 03Correlate and normalize
- 04Assess severity, impact, urgency and confidence
- 05Generate findings, recommendations and candidate actions
- 06Classify the action: read-only, simulated, approval-gated or executable
- 07Route approvals
- 08Send approved commands
- 09Capture responses, results, failures and rollback
- 10Preserve the audit trail
- 11Close and report — technical, client, compliance, executive
- 12Retain context for learning
Company roadmap
Pion first. Future platforms follow a defined purpose.
NGCC5's roadmap places healthcare after Pion and Teaching/Training later. Each proposed expansion will be evaluated against customer demand, available resources, and the capabilities already validated.
Platform
Pion
Purpose
Governed operational command for IT and operational technology.
Stage and decision conditions
In development. Establish connected capability, measured client value, and repeatable delivery.
Platform
Healthcare
Purpose
A planned environment for healthcare-related collaboration, knowledge sharing, and governed research participation.
Stage and decision conditions
Planned after Pion; not built in this stage. Validate the specific user need, privacy requirements, partners, and reusable capabilities.
Platform
Teaching/Training
Purpose
Interactive learning using curriculum, reasoning, application, and demonstrated understanding.
Stage and decision conditions
Planned for roughly year five, after Series A funding; not built in this stage. Progress depends on validated learning needs and the resources required.
| Platform | Purpose | Stage and decision conditions |
|---|---|---|
| Pion | Governed operational command for IT and operational technology. | In development. Establish connected capability, measured client value, and repeatable delivery. |
| Healthcare | A planned environment for healthcare-related collaboration, knowledge sharing, and governed research participation. | Planned after Pion; not built in this stage. Validate the specific user need, privacy requirements, partners, and reusable capabilities. |
| Teaching/Training | Interactive learning using curriculum, reasoning, application, and demonstrated understanding. | Planned for roughly year five, after Series A funding; not built in this stage. Progress depends on validated learning needs and the resources required. |
The planned healthcare platform focuses on collaboration and knowledge sharing. Pion's intended role in a hospital is support for its IT and operational infrastructure.