Skip to content
MAS Tools

Fiedler Data Import

Import Excel workbooks into IBM Maximo Manage: a plan for every row before anything is written, as the signed-in user, from Excel workbooks your team already knows.

An isometric conveyor carries a spreadsheet's rows through a scanning gate into a machine; the rows get teal check marks and one orange flag, and an orange line leads back to a returned sheet with the same marks

Fiedler Data Import brings data from Excel workbooks into IBM Maximo Manage, in the Maximo Application Suite (MAS). You upload a workbook, the app plans what each row will do, you look at the plan, and then you run it. The app writes as you, with your own rights, so Manage checks every record as if you had typed it in.

It reads Excel workbooks, because Excel is widely known and easy to use: the people who prepare the data already work in it, and anyone can read and correct a workbook. A library of import workbooks that took years to build keeps working on MAS. Fiedler Data Import itself is a new product, written from scratch with its own code base and no Java.

What it does

  • It plans first. For every row the plan says whether it inserts, updates, deletes or skips a record, or why it cannot. Manage stays untouched until you run the plan.
  • It works as you. The app signs you in through MAS. You can change only what Manage lets you change, and every record carries your name in Manage.
  • It handles real structures. Main records with their child records in one sheet, such as job plans with their tasks and labor, assets with spare parts, items with their texts in more languages, failure code hierarchies and classification specifications.
  • It writes the results back into your workbook. After a run you download your workbook with a result text for every row, and colours on the cells that need a look. Fix the failed rows in place and upload it again.
  • It keeps a history. Every job has its log, its files and its result. A job that stopped halfway resumes where it stopped and never sends a row twice.
  • It has two ways into Manage. The business object path writes through Manage’s business rules. The object structure path writes through an object structure of your choice, also your own.

A planned job: two assets to insert, and one row skipped because it is marked update-only

A result workbook: the error row in red, a read-only value in lavender, and the id Manage gave a new asset in green

How it runs

Fiedler Data Import is a companion app: a container in the MAS cluster on OpenShift, next to Manage. Inside Manage it needs four small automation scripts, which it installs itself, and its own application for the rights. It adds no Java code, and it changes none of the existing Maximo applications. An administrator controls it through settings in a ConfigMap, and its metrics feed Prometheus.

For scripts and build servers, a command line client does the same as the screens: upload, plan, run, results and test suites.

Who it is for

Maximo administrators and data teams who load and maintain master data and configuration in Manage: during a go-live, a migration to MAS, or the daily work. And teams who move to MAS with a library of Excel import workbooks from Maximo 7 and want it to keep working.

Editions

Fiedler Data Import shares one licence with Fiedler Data Export, the licence of Fiedler Data Tools. The free edition imports up to 200 rows of each sheet, for up to three users. The Fiedler Data Tools page describes both editions.

The series

A series of articles follows Fiedler Data Import from the idea to the running product:

  1. Built from scratch for the Maximo Application Suite: the history, and why Fiedler Data Import is a new tool
  2. The workbook format: why your old workbooks still import
  3. A companion app beside Manage: how Fiedler Data Import fits into MAS
  4. Plan first, then run: how every row is checked before anything is written
  5. It works as you: rights, sign-in and what the log keeps
  6. Results you can act on: colours, write-backs, resume and review
  7. Four layers of settings, and callbacks: how Fiedler Data Import is configured
  8. Measured: 10,000 job plans and a million rows: the numbers from our test system
  9. Running and scripting it: install, metrics, backup, the command line and test suites
  10. Values Manage owns: dates and time zones, spaces, audit columns, generated keys and the application a job uses

The articles appear below as they are published.

Example library

The example library is free to download: 37 workbooks that set up a small demo system in Manage, in load order. Each one is also a template for your own data.

Talk to us

Want to see Fiedler Data Import on your own workbooks? Get in touch. We work in English and German.

IBM and Maximo are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

The series

Read it in order

Part 1

Fiedler Data Import: Built from Scratch for the Maximo Application Suite

I was the lead developer of a Maximo data management tool for more than a decade. In 2026 I started a new product from scratch: Fiedler Data Import, with its own code base and no Java, designed for the Maximo Application Suite. It shares one thing with the old tool: the workbook format.

Part 2

The Workbook Format: Why Your Old Workbooks Still Import

Fiedler Data Import reads Excel workbooks, because Excel is widely known and easy to use. This article shows what the format expresses: sheets, rows, headers, child records and control columns.

Part 3

A Companion App Beside Manage: How Fiedler Data Import Fits into MAS

Fiedler Data Import runs beside Manage, as a container in the MAS cluster, with four automation scripts inside Manage. This article explains the split, how the app works as you, and how it is deployed.

Part 4

Plan First, Then Run: How Fiedler Data Import Checks Every Row Before It Writes

Fiedler Data Import plans every import before it writes. This article shows what the plan checks, how a row finds its record, what the plan screen shows, and why the run keeps to the plan.

Part 5

It Works as You: Rights, Sign-In and What the Log Keeps in Fiedler Data Import

Fiedler Data Import has no Manage account of its own for imports. This article shows how your sign-in reaches Manage, which rights decide a row, who sees a job, and what the log keeps and leaves out.

Part 6

Results You Can Act On: Colours, Write-Backs, Resume and Review in Fiedler Data Import

After a run, Fiedler Data Import gives your workbook back with a result for every row. This article shows what the result holds, what Manage writes back, and how a stopped job finishes without sending a row twice.

Part 7

Four Layers of Settings, and Callbacks: How Fiedler Data Import Is Configured

A job's settings in Fiedler Data Import come from four layers, and a lower layer can only make a job gentler on Manage. This article shows the layers, the CONFIG sheet, the configuration script and the five callback points.

Part 8

Measured: 10,000 Job Plans and a Million Rows in Fiedler Data Import

Claims about scale are cheap, so we measured. This article shows 10,000 job plans with their tasks and labor imported and deleted again, and a workbook of a million rows planned and written back inside the app's 2 GiB.

Part 9

Running Fiedler Data Import: Installation, Monitoring, Backup, the Command Line and Test Suites

Fiedler Data Import is run by the people who run MAS. This article shows the deploy, the Manage side, the metrics and alerts, backup and restore, the command line client and the test suites.

Part 10

Values Manage Owns: Dates, Spaces, Audit Columns and Keys in Fiedler Data Import

A workbook can hold values that Manage owns: dates in a time zone, outer spaces, ENTERBY and CHANGEDATE, generated unique ids, work order tasks, STATUSDATE. This article shows how Fiedler Data Import treats each of them, with what we measured on our test system.

Guides

More on Fiedler Data Import

See Fiedler Data Import on your own data.

Ask us for a price, a trial licence or a demo. We work in English and German.