Nimble Cognitive Digital Twin ecosystem
The building blocks for your Digital Twin
Discover, inspect, validate and install reusable ontologies, instance models, physics and ML models, notebooks, rules, crosswalks and templates — then compose them inside Nimble.
- Packages
- 35
- Open licensed
- 29
- Verified
- 26
- Publishers
- 22
Discover → Inspect → Validate → Install
Browse by domain
Domains, solution areas, artifact types and tags are catalog data — a package can belong to several at once.
Nimble Core
4 packages · 2 solution areas
The universal CDT foundation
ExploreCybersecurity
16 packages · 18 solution areas
Controls, frameworks and threat knowledge
ExploreManufacturing & Industrial
12 packages · 12 solution areas
Plants, equipment and production systems
ExploreCritical Infrastructure
12 packages · 10 solution areas
Water, energy, transport and OT
ExploreDefense & Aerospace
8 packages · 10 solution areas
Mission systems and digital engineering
ExploreUAV & Autonomous Systems
7 packages · 17 solution areas
Flight, payloads, autonomy and counter-UAS
ExploreFeatured
Curated, verified, ready to compose
Packages that consistently anchor new twins.
Nimble Core Ontology
v1.2.0nimble.core
The universal semantic foundation every Cognitive Digital Twin builds on.
Nimble · Ontology, Instance Template, Validation Rules
MITRE ATT&CK Enterprise (STIX 2.1)
v17.1mitre.attack.enterprise
Adversary tactics, techniques and mitigations as a threat knowledge graph.
MITRE · Ontology Mapping, Instance Dataset, Reference Dataset
Cybersecurity Core Ontology
v1.1.0nimble.cyber.core
Shared security vocabulary: controls, assets, threats, vulnerabilities, risks and evidence.
Nimble · Ontology, Validation Rules
SOSA / SSN Sensor and Observation Ontology
v2017.1w3c.sosa-ssn
The W3C standard for sensors, actuators, samplers and observations.
W3C · Ontology, Ontology Alignment
NIST SP 800-53 Rev 5 Control Catalog (OSCAL)
v5.1.1nist.800-53r5.oscal
The full NIST security and privacy control catalog in machine-readable OSCAL form.
NIST · Instance Dataset, Reference Dataset, Compliance Mapping
NASA C-MAPSS Turbofan Degradation Pack
v1.3.0nasa.cmapss.rul
Run-to-failure turbofan data plus a remaining-useful-life notebook and model.
NASA · Instance Template, ML Model, ML Notebook
Nimble Core
One semantic foundation
Core carries only universal CDT concepts — Entity, Asset, System, Component, Person, Organization, Location, Event, Observation, Measurement, State, Activity, Process and Document — plus universal relationships and properties. Domain knowledge extends Core; it never leaks into it.
Cybersecurity Core Ontology
nimble.cyber.core
Nimble Core Ontology
nimble.core
Nimble Temporal Alignment (OWL-Time)
nimble.core.time
Nimble Units & Quantities Alignment (QUDT)
nimble.core.units
Popular
What teams install most
Nimble Core Ontology
v1.2.0nimble.core
The universal semantic foundation every Cognitive Digital Twin builds on.
Nimble · Ontology, Instance Template, Validation Rules
MITRE ATT&CK Enterprise (STIX 2.1)
v17.1mitre.attack.enterprise
Adversary tactics, techniques and mitigations as a threat knowledge graph.
MITRE · Ontology Mapping, Instance Dataset, Reference Dataset
Cybersecurity Core Ontology
v1.1.0nimble.cyber.core
Shared security vocabulary: controls, assets, threats, vulnerabilities, risks and evidence.
Nimble · Ontology, Validation Rules
SOSA / SSN Sensor and Observation Ontology
v2017.1w3c.sosa-ssn
The W3C standard for sensors, actuators, samplers and observations.
W3C · Ontology, Ontology Alignment
NIST SP 800-53 Rev 5 Control Catalog (OSCAL)
v5.1.1nist.800-53r5.oscal
The full NIST security and privacy control catalog in machine-readable OSCAL form.
NIST · Instance Dataset, Reference Dataset, Compliance Mapping
NASA C-MAPSS Turbofan Degradation Pack
v1.3.0nasa.cmapss.rul
Run-to-failure turbofan data plus a remaining-useful-life notebook and model.
NASA · Instance Template, ML Model, ML Notebook
For the Nimble platform
Every package is machine-readable
Nimble discovers, inspects, resolves dependencies, checks compatibility and downloads packages through the Marketplace API — with an MCP surface planned on top of the same contract.
View the API contract