Fiix

I love the cross-integration between my field technicians, accounting, and warehousing. My equipment has all of the attached parts information that relates back to my warehouse as we consume materials and notifies my accounting and warehousing teams when we're below our required threshold. This is incredible software, it's able to keep all of our invoicing together and associate it with a track record of each part's purchasing history and cost over time. Very excited to use this to its fullest.

There are some things that would be nice for the initialization phase of creating all of the assets, namely that "save and create another" asset should carry over much of the prior item's data. For those of us without a csv to upload into Fiix, it seems easiest to go through each plant by asset type, so much of the data stays the same from asset to asset, until that type is finished. Often times, I ended up going back through to double check my new assets before moving on to creating the next new type of asset (i.e. AHU to RTU to MAU, etc. ).
Also, it would be nice to have a standard daily report that can include a technician's work from the day, including the actual photos uploaded by them, and have it sent to a set list of email addresses.

Work orders are easy to generate and scheduled maintenance setup is straightforward.
Nested PMs and event triggers are great for "if-then" scenarios where more work is required based on the results of a regular PM.
Reports are customizable with the upper-tier account.
Inventory management is quick and easy when the system is used on a tablet or smart device.
The mobile app is easy to set up and use.
Permissions for highly customizable for user groups.

Asset codes and model number are not visible on the asset list; The user has to view the asset to see the information.
Only a Grainger account can be linked for inventory lookup. Most inventory cannot be populated automatically by part number. However, in Fiix's defense, it may be difficult to get permission from vendors.
The report writer uses SQL code, but all of the SQL functions are not available in the interface.
WO review and approval from technician to engineer to management is not automated.

The open architecture and ease of adding assets and PMs

The same as what we originally liked. The open architecture allows users to create assets without much of the info needed within a PM system. Asset creation should be more structured and then allow additional inputs for special info but asset should require info about model serial number purchase and current cost. Since we began the entries without this info, I can add it later but info won't be standard for all assets unless I remove each and add back once I determine all info needed for each. It was nice not to need this info in beginning but makes the product I have less useful that it would have been if we were forced to add this standard information from the begining