Sales @ 844 291 4430

Benefits of BRIE compared to the MIF

Benefits of BRIE Compared to the MIF

1) While the Application MIF includes a “preview import” feature, any errors that occur are not cumulative errors, it will run until it hits the FIRST error and stop there. BRIE, on the other hand, attempts to gather all errors during the “validate only” import and present them to the user for bulk corrections. This allows BRIE to be quicker at data correction/re-execution process, reducing the amount of iterative process of “preview-correct first error-preview-correct next error” etc.

2) With Application MIF, both XML and flat-files are prone to data entry error edit incorrectly, especially flat files where data in particular columns is difficult to decode/understand/edit. In XML files, required data could be removed/missed, and-or inadvertently changed. XML and flat files are a non-user friendly file to manage. By using MS Access, BRIE has a stronger table/object structure which tends to keep the user from fiddling with the object structures, just editing data.

3) For very large datasets, BRIE provides better feedback to users about the status of import processing. With the import/export UI within Maximo, if a dataset takes more than a specific timeout to process (as it does these synchronously through service call, not asynchronously through JMS queues), users will not get feedback on what is happening with their import, or if it ultimately succeeds or fails. With BRIE, you can check on the status of a long-running import throughout the import process.

Maximo Implementation Casestudy

4) BRIE has a strong object relationship structure for insertion of new objects, especially with regards to autonumbering of new objects and cross-references to those new autonum values. When asset record is inserted and Maximo assigns it autonum 12345, this asset can be used immediately within other records, such as job plans or PMs, within the SAME transaction. No need to build additional complex hierarchies or “imbed” asset data within the PM record data. BRIE handles mapping of autonumbers back to dataset objects for you. You simply refer the local BRIE ID value and you’re set.

5) Application MIF does not support the transaction for modifying physical count update. BRIE does. This is used to perform physical inventory count adjustments, cycle count, etc.

6) eSig Support – Out-of-box MIF “Application Import” (importing XML or flat files through UI by end-users) does not support electronic signatures. Users can submit changes through MIF which would normally require electronic signatures through the UI, but when submitted through MIF do not prompt the user for an eSig. You can enable electronic signatures for the “application import” action, which does prompt user for eSig but only prompts AFTER the import has already been processed. If the user enters an invalid eSig when prompted, the change has already been processed and isn’t rolled back. Customization and/or PMRs submitted to IBM would be required to change eSig functionality for MIF import.

7) Application MIF needs to be configured for each application, including the creation of the MIF objects, and the adding of the toolbar icon, per application that is intended to use it.

8) BRIE’s intended end user is the ‘Maximo Super User’ (Supervisors, Administrators, etc.). It does not require IT resources, such as DBAs, Websphere admins, etc. In fact, a general knowledge of Microsoft Access is all a user needs to know and get started. The more advanced knowledge a user has of MS Access, the more powerful BRIE will be to the organization.


  • Get in Touch

    Corporate HQ
    2000 Lenox Drive
    Lawrenceville NJ 08648
    Email Us


    400 Jean-Lesage Boulevard Suite 348 Quebec City, QC, Canada G1K 8W1 Phone: +1 (418) 525-0606


    Herriotstrasse 1 60528 Frankfurt Germany Phone: +49 (0) 696 773 3456


    1st Floor, TEK TOWERS No.11, OMR, Chennai-600097, Tamil Nadu, India.

  • Products

    Labwise Pristima SEND-Savante eQCM QMS-OT Compliance Builder VitalPath Emidence

  • Quick Access

    Why Xybion Leadership Customer Support Events Privacy Policy Terms of Use Blog Contact Us

  • Stay Connected

    Subscribe to Xybion Buzz, Updates and Newsletters