Track 1Modern AI integration through open MCP
Instead of forcing your data into a proprietary AI vendor’s walled garden, JanusKS deploys standardised MCP server endpoints directly over your operational knowledge graph.
Structured semantic resources
Expose project critical paths, resource capacity matrices, trade overlaps and compliance hold points as deterministic MCP resources.
Algorithmic simulation tools
Expose the JanusKS constraint solver as an MCP tool. AI models can ask: “Run a scenario where Supplier B slips by 10 days and return margin impact.”
Dynamic context pruning
Removes prompt bloat and runaway token costs by feeding models only the sub-graphs relevant to the immediate query.
Model neutrality
Switch freely between Anthropic Claude, OpenAI ChatGPT, Google Gemini, GitHub Copilot, Cursor, or private open-weight models (Llama, Mistral, Qwen) on local runtimes such as Ollama or LM Studio.
Track 2Enterprise systems connectivity
Connect with tools that do not speak AI protocols, with no disruption to daily workflows.
High-throughput REST APIs
Universal data querying
Query your multi-dimensional knowledge graph, temporal baselines and scenario branches using RESTful APIs.
Fine-grained payloads
Request full sub-graphs, calculated formula metrics or specific entity states using predictable, documented JSON payloads.
Interactive API documentation
Full OpenAPI 3.0 / Swagger specifications and SDKs for rapid engineering integration.
Event-driven webhooks and real-time triggers
Bidirectional sync
Listen for state changes across your project platforms, such as a new permit approved in Procore or a purchase order issued in SAP, and ingest them into the graph in milliseconds.
Outbound operational alerts
Dispatch automated alerts and prescriptive recommendations directly to collaboration tools such as Slack, Microsoft Teams and PagerDuty.
Enterprise message queues and streaming
High-volume telematics and IoT
Ingest continuous equipment telematics, GPS vehicle feeds and biometric badge data through Kafka, RabbitMQ or MQTT message brokers.
Automated writeback to systems of record
Once human leadership approves a scenario in JanusKS, the engine writes schedule updates, contractor reassignments or contingency allocations directly back into Primavera P6, SAP S/4HANA or Oracle ERP.
Enterprise integration matrix
| System category | Typical source platforms | Integration vectors supported | Operational data exchanged |
|---|---|---|---|
| Frontier and local AI |
|
Open Model Context Protocol (MCP), local stdio/SSE endpoints | Semantic graph context, constraint tools, scenario simulations. |
| Enterprise ERP |
|
REST API, OData connectors, automated batch drops (SFTP), webhooks | Budgets, actuals, procurement orders, vendor rate cards, billing milestones. |
| Capital and scheduling |
|
XML/XER parsers, native cloud REST APIs, webhook listeners | Master Gantt tasks, trade allocations, daily site logs, subcontracts. |
| Team collaboration |
|
Inbound and outbound webhooks, bot notifications, interactive cards | Anomaly alerts, root-cause reports, one-click intervention approvals. |
| Data warehouses and BI |
|
Parquet/JSON-LD exports, JDBC/ODBC, automated S3/Blob sync | Verified temporal data extracts, graph metrics, executive KPI feeds. |
Security, access control and governed execution
Connecting AI models and enterprise tools across a single data layer demands rigorous perimeter controls.
Unified identity and RBAC/ABAC
All API calls, webhook events and MCP tool executions map to enterprise identities through single sign-on (SAML 2.0, LDAP or Active Directory). A project engineer’s MCP agent cannot query financial nodes that the engineer’s API token lacks permission to view.
Human-in-the-loop writeback gates
Systems can ingest data and run simulations autonomously. State-altering writebacks, such as releasing a budget hold in SAP or shifting contractual milestones in P6, need authenticated human sign-off.
Cryptographic in-transit security
All REST endpoints, webhook deliveries and MCP sessions are encrypted with TLS 1.2 or 1.3, with HMAC signature validation on all incoming webhooks to ensure message provenance.