(Enhancements below are available in the 6/12/25 Feature Release)
This month’s list of feature releases are geared towards streamlining several day-to-day processes within EBIS, as well as make it easier to find and review specific data within the system.
New Features & Enhancements
Streamlined Processes:
- Add New Item: Quickly “Add New Item” from a Work Order List Items view. Users can now add new items to the Work Order without navigating to a specific item record.
- FAA Tail Number Search: Use the FAA Database search when creating an Aircraft from anywhere in the system. This search allows users to enter the tail number and pull FAA data into EBIS, including the owner information, etc. Previously this was only available when creating an Aircraft while creating a new Work Order.
- Repair Order Details: When creating a new “R/O Detail” record within a Repair Order, it will now automatically enter the City’s Cert Number into the “FAA/Govt. Auth” field, eliminating the manual step of typing the cert for each Repair Order.
- Purchase Order Quick Receive: When using the Quick Receive workflow on the Purchase Order, users can now indicate a part’s condition at that time without having to navigate to the Stock Qty record.
- Compliance “End-of-Month” Due Date: Users can now set certain items to automatically come due at the end of the month instead of exactly 12 months or 365 days from the completion date. For example, if a 12 month item is completed on 6/15/25, it will show a Due Date of 6/30/26.
- QuickBooks Online Supporting Items: When syncing to QBO, only changed values will get sent, and supporting items move to the end of the sync queue to avoid ancillary errors that occurred when pushing to QBO.
Improved Visibility
- Stored Discrepancies and Corrective Actions: It’s now easier for users to see, filter and add available pre-canned verbiage for Discrepancies and Corrective Actions.
- Outstanding Parts Columns: Users can now quickly see the “Needed Date” and “Supplier” information from the Outstanding Parts screen.
- Work Order Tech Activity: Within the Technician Activity tab on a Work Order, when users select the “Detail” dropdown view, you can now quickly see which Tech Group each Technician belongs to within the system. This info is also available via export.
- Compliance Reporting: Any null or blank values will no longer be displayed on Compliance reports, making it easier for users to quickly identify which items are coming due and how much time is remaining.
Parts Kit Enhancements:
New Parts Kit display functionality on the Work Order Invoice and Estimate. Parts Kits can now be displayed as a single Work Order line item with a “rolled up” price so individual parts in the kit do not have to be displayed to customers:
- Kits tab added to Work Orders to quickly identify any Parts Kits associated with the Work Order
- New settings: City Level config options “Invoice: Expand Parts Kits” can be toggled off and “Invoice: Show Part Kit Header” can be toggled on to show a Parts Kit as a single line item on the Work Order.
- On the List Parts tab in a Work Order, the Price (Ea) field now shows “(Kit)” when part of a Kit.
- The value for “Use Kit Retail” shows up on the Work Order line item.
Release Notes Overview Video:
Why These Updates?
As EBIS grows and evolves, we continue to get feedback on how customers actually use the system on a daily basis and where we could improve. The features in this release are recurring asks from customers, primarily geared toward streamlining or eliminating tasks that range from a few seconds to a few hours.
We'll continue to streamline workflows in the upcoming year and build the best aircraft maintenance management system possible for our customers. Stay tuned, we have some exciting new releases over the next few months.
Feedback:
Since day one, EBIS has been built on customer feedback. If applicable to you, please check out these resources, test out the functionality, and let us know what you think.
You can submit direct feedback on this feature to support@datcomedia.com with the subject line "Feedback:".
COMMENTS