iKIproKINTEGRATED PROJECT KNOWLEDGE
IPROK · INTERACTIVE SCHEMA ATLAS

See the structure.
Follow the connections.

Author & developerVenkatesh Kone

A visual map of schedule, resources, cost and their integration. Drag a concept, follow a labelled relationship, or select a node to discover what it means.

The IproK network

28 classes · 5 modules
Drag nodes · drag background to pan · scroll to zoom
Published IproK 0.1.0 · source declarationsGuided module walkthrough ↓Search all properties ↓
START WITH THE MEANING

Five modules. One connected structure.

PUBLISHED IPROK SCHEMA

Choose a module to see its purpose and connections. Then follow a question through the model or inspect any term. Explanations are editorial guides; source assertions remain available at every step.

INSIDE THE MODULE

Concepts below may belong to neighbouring modules. The relationships on the right are declared in the selected module.
READ THE CONNECTIONS
FOLLOW A QUESTION

See how the pieces connect.

□ Class: a kind of thing→ Property: a declared relationshipSelect either to inspect the source
01 · STRUCTURE

The ontology defines the meanings.

Task, ResourceAllocation and Resource are classes. taskHasResourceAllocation and allocationAssignsResource are relationships between those classes.

02 · RECORDS

The graph connects actual records.

Illustrative only: “Task A → Allocation A → Crane A”. These would be project instances using the schema. This website contains no actual project records.

03 · BOUNDARIES

Read what is declared.

The published IproK schema has schedule, resource, cost, integration and shared modules. A building-model module is not declared in this release. Niyoj is available separately as later development, with its own namespace.

ASK THE STRUCTURE

How are these concepts connected?

Choose two classes. Trace a shortest path through declared object-property domains and ranges, then see a SPARQL pattern for that path. Connections can be followed in either direction; inverse steps are marked.

Read the corresponding SPARQL pattern

Generated from the displayed schema path. No query runs here. Use a populated graph with matching predicates; inspect dataset, graph scope and authorisation before execution. Domain/range declarations can be multiple and are not validation rules.

THE KNOWLEDGE STRUCTURE

Ontology explorer Loading

Loading schema…

Loading the retained schema…

TRACEABLE BY DESIGN

From source to schema.

Every count comes from the selected RDF files. Browse complete assertions in the inspector and download the retained schema for your own checks.

Source hashes & declaration audit ↗Publication & verification procedure ↗

Published IproK files

View RDF source ↗

Declared relationships & assertions