Frequently asked questions

Excel files such as daily work reports, repair logs, maintenance star charts, purchase order lists and equipment registers, against Maximo assets, specifications, locations, classifications, work orders, PMs, items, inventory and other object structures the JSON API can read and write. Changes that need Maximo's own actions, such as deleting records, are not made in MX Stage; they are listed with counts, to be done in the Maximo application.

No. Maximo keeps closed work orders as history and refuses changes to them. Tidy the failure and purchase details while the work orders are completed (COMP), then close them.

Each row gets a status from its dates: finished work is completed (or closed, if you choose that for the connection), work started but not finished is in progress, and planned work is waiting for approval. Existing work orders keep their status while their contents are corrected. Statuses are changed with Maximo's own status change, so Maximo's rules (allowed moves, status history) apply.

A Maximo partner company. Partners tune MX Stage's Skills for each project and deliver the work to their customers, from sorting out the data issues to proposing Maximo solutions. TSUNAGI provides advisory to partners and keeps the tool up to date; it does not take on project work. If you use Maximo, ask us and we will introduce a partner. Partners

No. MX Stage runs on a Windows PC with the AI assistant you choose, and your data never reaches us. How a partner handles your data during a project is set in your contract with that partner.

Try the built-in demo first: a virtual Maximo and five sample Excel files run on your own PC. Then contact us about partner terms, which are agreed with each partner. Partners

Tell TSUNAGI (mxstage@tsunagi.app, or GitHub Issues). What happened, the steps, the version number and any error shown in the work screen help us fix it quickly. Do not send Maximo data or API keys (GitHub Issues are public). Fixes ship in the next version of MX Stage.

Ways of reading and rules used only in one project can be added by tuning Skills. For features many projects can use, or changes that need MX Stage itself improved, talk to TSUNAGI. TSUNAGI plans and develops them as needs arise and ships them in MX Stage updates. Rights in improvements to MX Stage belong to TSUNAGI; rights in new solutions created in a project belong to the partner company. Roles

Yes. The AI reads what each row says, such as the subject, plant and period, and links only the rows that point to exactly one record. Rows with several candidates, or that disagree with a value already in Maximo, are not guessed; they come back as a list with the evidence.

Load the records into MX Stage, ask your AI assistant to make the change and give a reason, review the cell-by-cell diff, and press Commit to Maximo. MX Stage writes one record first and lets you check it before sending the rest. Records someone else changed after you loaded them are skipped and listed.

Rehearse the fixes on a test environment for free, turn the steps into reusable Skills (procedures your AI assistant follows), and apply them to production at go-live. Only committing to production needs a license.

Yes. MX Stage is a local MCP (Model Context Protocol) server and work screen for IBM Maximo and Maximo Application Suite (Manage). Your AI assistant loads Maximo data into a staging sheet, proposes fixes, and a person reviews the diff and approves before anything is written to Maximo.

Most Maximo MCP servers let the AI call the REST API directly. MX Stage puts a staging sheet in between: the AI edits the sheet, you see a diff with reasons, you can undo any batch, and only a person can commit. A diff report and a write log are kept.

Officially: Claude Desktop, ChatGPT desktop in Codex or Work mode (Chat mode cannot use local MCP servers), Antigravity and IBM Bob. Claude Code and the Codex CLI also work.

Maximo and Maximo Application Suite (Manage) that provide the JSON API at /maximo/api, using an API key. Environments that allow only login authentication (MAXAUTH) or LDAP are not supported yet.

Yes. In the workbench, Settings → Demo downloads fictional data for three waste incineration plants (about 10 MB) and connects to a virtual Maximo on your PC, with sample Excel files to match. Commits change only the copy on your PC, and no license is needed.

The work screen reads Excel (.xlsx, .xlsm) and CSV files; it has no PDF reader. Excel files laid out as forms (such as one daily report per page) are read as they are. For PDFs, you may be able to write a custom Skill in which your AI assistant turns the PDF into Excel or CSV before importing it. This relies on each vendor's AI, and MX Stage does not test or support it. The PDF's contents are also sent to the AI provider, under the customer's contract with that provider.

No. MX Stage runs on your PC; there is no MX Stage cloud and no telemetry. It talks to your Maximo and your AI assistant, and otherwise only when you choose to (checking for and downloading updates, downloading the demo data). What the AI assistant does with the data you give it is covered by your agreement with the AI provider. Security and data flow

If you choose "Save on this PC", the bridge encrypts it with a key protected by Windows data protection (DPAPI) and saves it on this PC; it is given neither to the work screen nor to the AI. If you connect without saving, it stays only in the work screen tab's memory and locks after 30 minutes without use.

No. The AI's tools cannot write to Maximo. Only a person pressing Commit to Maximo in the work screen can.

It is free for test environments and for loading, analysing and editing production data. Committing to a production Maximo needs a license: US$4,800 per production environment per year (excl. tax). Production license

No. One license covers one production environment for everyone in your organization, on any number of PCs.

Yes. Loading, analysing and editing production data are free, so you can review the full diff before buying. Only committing to production needs the license.

Yes, one production license per production environment. The partner can arrange it as part of the project.

Yes. It is free for test environments; committing to a client's production needs a license for that production environment. Partners

The source code is public under the Business Source License 1.1. Each version becomes open source under the Apache License 2.0 four years after it is released.