Manage operational evidence across critical infrastructure.

Energy, utilities, transport and infrastructure operators need to distinguish operational systems from the evidence used in incident, maintenance and assurance decisions.

17

Critical Infrastructure Intelligence Technology - AICThree separated lanes showing NERVE to CORTEX linkage, isolated GTK2.0 exchange, and PAL.NET access to supported Palantir services.Illustrative capability mapPLATE 01010203INDEX / MODEPORTFOLIONERVECORTEXDocumented evidence interfaceGTK 2.0Configured exchangePAL.NETSupported Palantirservices.NET access to supported Palantir servicesInterfaces and deployment scope requireconfirmation.

Keep operational and source records distinct

An incident assessment may draw on approved documents, inspection records and imagery. Preserve the source, processing history and authority to use it. An evidence workflow should not be described as replacing the operator’s control systems or safety processes.

Map product roles to the assessment

Assess NERVE for governed source discovery, GTK 2.0 for relevant imagery and geography, and CORTEX for traceable review and reporting. Confirm formats, receiving systems and information-handling policies. Product suitability depends on the actual workflow.

Prepare for constrained sites

Where a supported disconnected profile is required, identify local storage, dependencies, updates and export arrangements. Use approved maintenance or incident-assessment material in a representative site test. Confirm what happens when network access returns.

Assurance and privacy questions

Which records include personal or commercially sensitive information? Who may approve an export? How is an earlier assessment reconstructed? What assurance evidence does the operator require? No regulatory certification or approval for infrastructure operators is implied by the portfolio relationship.