Trace

Know what could break before you change a system

Trace is AIM’s shared record of your systems, what depends on them, and the designs you’ve approved. Before a patch, upgrade, or replacement, use it to find what must keep working, what to test, and what evidence supports the funding request.

Replacing a city’s sign-in service

In this example, a security flaw affects the city’s unsupported sign-in software. Follow the change from the first alert through testing and approval.

Paused · click the picture to resumeScene 1 of 4. The security flaw affects the version the city has installed.

The security flaw affects the version the city has installed.

Permit portalWhere residents apply for permits
Staff consoleWhere city staff review applications
Sign-in serviceChecks who can enter either appVersion 2.8 installed
The highlighted card is the service being replaced.

Does the alert apply here?

Each card represents a system. The team checks the installed version of the sign-in service against the security notice and confirms that the vendor has ended support.

The city plans to replace the service while residents and staff continue to use both applications.

What to check before taking a device offline

The UK’s National Cyber Security Centre expects AI to accelerate and scale existing attacks. A shared record helps engineering, security, and operations answer the same questions quickly, from deciding which updates to prioritize to verifying what was installed. NCSC threat review · NIST patch management guide

  1. Is this version affected?

    Match the advisory to the version observed in the environment and check the date and source of that observation.

  2. What will the change affect?

    Follow the recorded dependencies. If a link is uncertain or the analysis reaches a boundary, ask the service owner to verify what still needs checking.

  3. Can people still do their work?

    Use the requirements to decide what to test in each dependent service and when to revert the change if a test fails.

One approved design from assessment to operations

A released baseline is the exact design version the team approved and released for use. It keeps the linked systems, requirements, and tests together. Teams can cite that version through delivery and return to it for the next change.

  1. Assess the current system

    Architects and engineers record what the system does, what runs today, and which services depend on it.

  2. Approve the work and cost

    Technical reviewers weigh the tests and recovery plan. Funding leaders can weigh costs against the service the work protects.

  3. Verify the delivery

    Project managers use PULSE to check the delivered work against the approved design and requirements.

  4. Keep the record current

    In PSM, operations can refer back to the approval when comparing the plan with what actually went live.

Use Trace with the tools your teams already have

Requirements, models, and inventory

Teams can keep authoring requirements or running simulations in specialist tools and use Trace for the shared change record. Trace offers one-way exports for handoff, with ReqIF for released requirements and SysML v2 or a Cameo XMI seed for architecture. Test an exchange with your own records and agree which tool owns updates.

An organization can also connect version observations from its inventory. Keeping the source and observation date with the record lets teams compare what’s running with what was approved.

Your organization’s AI can cite the evidence

Ask which services could be affected by changing a component. With permission, the AI can retrieve the approved design, documented dependency paths, and dated operating evidence. A reviewer can check what it cited and decide whether to accept any proposed requirement or dependency.

AIM has exercised the workflow with sample records. Check data freshness and coverage when reviewing answers. Access requires AIM’s agent capability and permission for the relevant records. How agent access works · NIST guidance on verifying AI sources

When does Trace pay for itself?

A shared record can save staff from rebuilding the same dependency map and gathering the same evidence for every review. Compare that time across the changes you expect to review with Trace against the cost of adopting it and keeping the record current.

Estimate the value of adopting Trace

The starting inputs describe an example workload. Replace them with your review volume and measured time per change.

Workload and staff time
Adoption costs

Include migration, setup, and training once. Include subscriptions, integration upkeep, and time to maintain the record each year. Count existing spend only if you expect it to end.

Illustrative results

Review hours freed per year
360
Annual value of that time
$18,320

Enter setup and annual costs to estimate net value and break-even volume.

Results assume a full year at the entered workload and costs. Break-even counts the value of staff time and any spend removed. Staff time measures capacity, so track actual spending separately for cash savings. The starting hourly rate is the May 2025 U.S. median systems analyst wage. Use your own rate including benefits and overhead. BLS wage data

Measure one service before expanding

Start with one service and compare similar changes under your current process and in Trace. Measure staff hours spent tracing impact and collecting evidence, time to a signed decision, and time spent keeping the record current. For people who rely on the service, track interrupted work and whether they can complete critical tasks after the rollout.

Expand where teams can reuse the evidence and measured benefits justify the cost. GAO cost estimating guide

Research and vendor benchmarks

In a controlled study with 71 participants, people with requirements links completed the studied maintenance tasks 24% faster and produced 50% more correct solutions. Participants sketched solutions for two software projects. Read the study

Dassault lists a five-day Cameo systems modeling course and training provider SmarterProcess lists a two-day DOORS Next introduction. IBM documents ReqIF exchange, and Cameo DataHub documents how to connect to DOORS Next. Budget for the training and exchange work your own deployment needs. Cameo course · DOORS Next course · IBM exchange docs · Cameo connection docs

See a full modernization decision in AIM

Follow a decision from the systems and requirements through the cost comparison and the delivery plan.

Explore the worked decision
Trace | Freedom AIM