Skip to content
MAS Tools
ProductsFiedler Data ToolsFiedler Data ImportFiedler Data ExportFiedler Data Explorer
Installation
Release notes
About
Contact
Ask for a trial

Fiedler Data Export

Export IBM Maximo Manage records into Excel workbooks as the signed-in user, in the format Fiedler Data Import reads, so a changed workbook imports back as it is.

Installation guideRelease notesRead the series
An isometric tower sends orange and teal tiles along a conveyor onto a large slab, whose grid of cells the tiles fill; a second conveyor carries tiles from the slab back into the tower's base

Fiedler Data Export takes records out of IBM Maximo Manage, in the Maximo Application Suite (MAS), into Excel workbooks. You choose an application and a saved query, Manage counts the records, and the app writes them into a workbook. It reads as you, so the workbook holds exactly the records you may see in Manage.

The workbook has the format that Fiedler Data Import reads. So you export the records, change them in Excel, and import the workbook again. The round trip needs no conversion between the two steps.

What it does

  • It plans first. Manage counts the records, and the plan shows the sheets and their columns. The app reads nothing until you press Export.
  • It writes one sheet per kind of record. The main records go on one sheet. Related records, such as an asset’s meters, go on their own sheets, next to the record they belong to. A classification can get a sheet of its own with its specification attributes.
  • It offers layouts. Records writes every attribute. Transfer leaves out the unique id and the generated numbers, for a load into another system. With children adds the relationships you pick. Multilevel writes a whole hierarchy on one sheet, up to five levels. A layout can be saved and shared with a security group.
  • It takes a workbook as the layout. Drop an earlier export or a template, and the new file gets the same columns. So Excel is the column editor.
  • It makes import templates. A layout gives an empty workbook for a new import. Row 3 describes each column’s attribute in your language, so whoever fills in the template sees what each column needs.
  • It has two ways to read. The business object path reads every column, child and language. The object structure path reads through a structure of your choice, and the screen greys out what the structure cannot carry, with the reason.
  • It only reads. An export never changes a record in Manage.

The Export page: assets with a saved query and the layout With children

An Extended sheet: each asset with its meters on the rows below it

How it runs

Fiedler Data Export is a companion app, like Fiedler Data Import: a container in the MAS cluster on OpenShift, next to Manage. Inside Manage it needs four small automation scripts and its own application for the rights. Its administration screen installs them, and the same screen removes them again. Both apps share the workbook engine, so a workbook means the same to both.

A large export runs in the background as a job. It reads Manage page by page, and it splits into several files when one file would get too large for Excel or for the import. Every job stays in the history with its log and its files until the retention period ends.

For scripts and scheduled work, the command line client fde exports the same way. The installation guide includes a nightly export as a Kubernetes CronJob, and metrics, alerts and a dashboard come with the app.

Who it is for

Maximo administrators and data teams who need data out of Manage: to review and correct master data in Excel, to move records into another system, to build an import template, or to keep a regular extract. And everyone who uses Fiedler Data Import, because the export writes the workbooks it reads.

Editions

Fiedler Data Export shares one licence with Fiedler Data Import, the licence of Fiedler Data Tools. The free edition exports up to 200 records at a time, for up to three users. The Fiedler Data Tools page describes both editions.

The series

A series of articles explains Fiedler Data Export, from the round trip to running it:

  1. Out to Excel and back in: the round trip, and why the export writes the import’s format
  2. Layouts: Records, Transfer, With children, saved layouts and your own workbook
  3. Two ways to read: business objects and object structures
  4. Measured: a million records: why a large export splits its files
  5. Running it: install and removal, nightly exports, retention and monitoring
  6. Several levels deep: a whole hierarchy on one sheet, and back into Manage
  7. What the export tells you: the count, header notes, text columns and the cells Manage could not deliver

The articles appear below as they are published.

Talk to us

Want to see Fiedler Data Export on your own data? 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

Out to Excel and Back In: The Round Trip of Fiedler Data Export

An export to Excel is half of the job. The other half is the way back into Manage. Fiedler Data Export writes the format that Fiedler Data Import reads, so a changed workbook goes back as it is. We follow one round trip, and we list what our round-trip cases found while we built the export.

Part 2

Layouts: Choose the Sheets and Columns of Your Manage Export

The same records can leave Manage in different shapes, depending on what the file is for. A layout decides the sheets and the columns. This article explains the six ways to choose one, how saved layouts are shared, why Excel is the column editor, and how a template starts a new import.

Part 3

Two Ways to Read Manage: Business Objects and Object Structures

Fiedler Data Export has two ways into Manage. The business object path reads everything an export can hold. The object structure path lets a structure decide what is visible. This article explains when each one fits, why the Export page checks a layout against the structure before the plan, and how both paths end in the same workbook.

Part 4

Measured: A Million Records in Fiedler Data Export, Split into Six Files

An export of a million records can fail in two ways: the pod runs out of memory, or the file is too large to open. We measured both. A million records stayed far below the pod's memory limit, two such jobs at once did too, and the export split them into six files that Fiedler Data Import reads at its default limits.

Part 5

Running Fiedler Data Export: Install and Removal, Nightly Exports, Retention and Monitoring

The last article of the series is for the people who run Fiedler Data Export. It covers what the export adds to running a companion app: an install and a removal from one screen, nightly exports, how long exported files stay, who exported what, and what the monitoring watches.

Part 6

Several Levels Deep: Multilevel Export and Import

Some Manage data is a tree. Failure codes go from a class to problems, causes and remedies, and assets hang below other assets. The Multilevel layout of Fiedler Data Export writes such a tree on one sheet, one relationship per level. We show how to build a path, what the sheet looks like, and how it goes back into Manage.

Part 7

What the Export Tells You: Counts, Header Notes and the Cells Manage Could Not Deliver

Before an export, Fiedler Data Export counts the records and lets you take only the first ones or the header rows. In the file, row 2 carries a note on every attribute, and text columns stay text. After the run, the log names every cell Manage could not deliver.

See Fiedler Data Export on your own data.

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

Get in touchoffice@fiedler-it.at