Enterprise access
Deployment scope is defined with your security, procurement, architecture, integration, data residency, support, and capacity requirements in mind.
Assessment, modernization, procurement, Project Pulse, integrations, MBSE interoperability, and future agent operations are explicitly provisioned.
Identity, roles, auditability, data handling, deployment boundaries, and support obligations are aligned to the agreement.
The commercial process supports evaluation, security review, contracting, implementation planning, and governed rollout. Evaluation itself is a time-bounded provisioned organization—not an anonymous public trial.
Buyer evidence
A one-page packet for procurement, security, and architecture review. Algorithm-parameter appendices stay off the public site until a named reviewer asks. Published posture is on Compliance.
AIM owns the SaaS application, the assessment record, scores, documents, Pulse, Pulse Sustainment, and the operational artifacts AIM issues. The customer owns identity, membership, and what they enter. The host owns transport encryption and the customer environment. Public AIM is not a FedRAMP authorization boundary.
A valid AIM signature means the artifact is authentic. Authorization to run a later action in production is recorded by the customer's designated authorities. Mission Control covers observe, propose, rehearse, and signed preflight. Changing a live environment stays with the organization's own approval path.
The seventh RAO dimension applies with current product evidence and an explicit organizational tolerance. Buyers see what was reviewed for each product. Read the method.
Organization agreement after consultation, security review, data-boundary alignment, and governed onboarding. Evaluation is a time-bounded provisioned workspace. Pulse, Mission Control, and Agent Orchestration appear only when they are entitlements.
Sit through the decision tape on One complete decision, then compare AIM with discounted AI and workflow tools.