DAT-01 / INTELLIGENCE DATA

Plintir Nexus

Turn heterogeneous sources into trusted intelligence context without losing source markings, evidence, identity history or lineage.

Core intelligence outcome
Intelligence Data Fabric & Mission Ontology

When multiple records are resolved into one intelligence entity, Nexus keeps the underlying source records and the evidence behind the resolution available for review. A merge can be challenged; source history is not discarded.

SOURCESCONNECTED
ENTITIESRESOLVED + REVIEWABLE
LINEAGESOURCE TO ASSESSMENT
Product experience

Intelligence in context, with the next decision already in view.

PLINTIR / NEXUSLIVE
INTELLIGENCE DATA FABRIC & MISSION ONTOLOGYSTATUS: OPERATIONALUTC
SOURCESCONNECTEDLIVE
ENTITIESRESOLVED + REVIEWABLEVISIBLE
LINEAGESOURCE TO ASSESSMENTCONTROLLED
CONFIDENCE0.86ASSESSED
Connected sources · 152
SourceClassVolume / dayHandlingLineageQuality
SRC-0118Streaming412 GBCONTROLLEDCOMPLETE
98%
SRC-0204Imagery1.9 TBOFFICIALCOMPLETE
94%
SRC-0311Legacy DB84 GBCONTROLLEDCOMPLETE
89%
SRC-0356Reporting12 GBRESTRICTEDCOMPLETE
100%
SRC-0402Open source220 GBPUBLICPARTIAL
61%
SRC-0455Sensor feed760 GBCONTROLLEDDEGRADED
34%
Entity resolution · review queue
VES-4471 ↔ VES-88020.91 MERGE
PER-3341 ↔ PER-90140.58 ANALYST
ORG-1174 ↔ ORG-22050.31 REJECT
FAC-0093 ↔ FAC-01210.44 ANALYST
ACC-7712 ↔ ACC-77190.77 ANALYST
Automatic merge is disabled above the review threshold. Every merge keeps its source records and can be reversed.
Detailed capabilities

What Nexus does.

CAP-01

Connect sources without losing context

Bring together batch feeds, streams, APIs, documents, geospatial data and legacy systems while retaining source reliability, handling context and time.

Legacy + modernStreamingDocumentsGeospatial
CAP-02

Resolve entities, preserve evidence

Consolidate records that likely describe the same person, organization, platform or asset while retaining the source records, match evidence and analyst review history.

Candidate matchingConfidenceAnalyst reviewReversible decisions
CAP-03

Create reusable mission meaning

Represent entities, observations, tracks, events, relationships, locations, tasks and assessments consistently so intelligence products do not drift into incompatible definitions.

Shared entitiesRelationshipsTime validityReusable context
CAP-04

Keep lineage through every intelligence product

Trace material facts and derived values back to their source so an assessment can be challenged, reviewed and defended long after publication.

ProvenanceQualitySource ownershipAuditability
Interface detail

An assessment can be defended line by line, months later.

PLINTIR / NEXUS · LINEAGELIVE
Derived valueAppears inTransform chainOriginal sourceTraceable
ENT-00921 positionASM-0091correlate → resolve → assessSRC-0118 · 0912ZFULL
Vehicle count 11Brief 08-15extract → enrichSRC-0204 · IMG-7714FULL
Reliability B3ASM-0088review → reviseAnalyst decision · 1120ZFULL
Network communityCaseGraphresolve → expand → cluster9 source recordsFULL
Coverage 82%COLLECT-042aggregate → projectSAT-A2 access windowsFULL

Lineage is not a diagram, it is a query. Any figure in a published product resolves back through each transform to the original record and the analyst decisions applied along the way.

One entity does not erase its sources.

When multiple records are resolved into one intelligence entity, Nexus keeps the underlying source records and the evidence behind the resolution available for review. A merge can be challenged; source history is not discarded.

Intelligence flow

From information to Actionable Intelligence Data.

STEP 01

Connect

Authorized data enters with source and handling context.

STEP 02

Normalize

Information is made consistent without flattening its provenance.

STEP 03

Resolve

Entities and relationships are linked with confidence and evidence.

STEP 04

Publish

Trusted intelligence context becomes reusable across products and teams.

Mission use cases

Designed around intelligence outcomes.

UC-01

Intelligence Data Modernization

Connect legacy mission systems while improving access, lineage and entity context.

UC-02

Enterprise Intelligence Hub

Create governed intelligence context shared by multiple analyst and operational applications.

UC-03

Entity-Centric Intelligence

Build reusable entity, relationship and event context for fusion, investigations and AI.

Product briefing

See Nexus against a real intelligence workflow.

Start with sources analysts currently reconcile manually and an intelligence question that depends on matching identities, events or relationships across them.