By
Aviation Data integration with Maximo
Airport operations can benefit from integration with Maximo through a number of use cases. The table below outlines some of the use cases:
| Use Case | Implementation Options | ||
|---|---|---|---|
| 1 |
|
|
|
|
|
||
|
Locations: Location hierarchy can be updated from Revit to ModelStream. The locations in Maximo are built based on the Revit Model. Locations in Maximo do not flow back to Revit. | ||
|
Assets: Assets are tagged with the GUID from the Revit Model. Once the asset is created in Revit, the Maximo asset will need to be updated with the GUID. After that information can be exchanged. After this the location information can be updated by using ModelStream. | ||
|
Documentation is passed from the Revit model to Maximo, where the files are placed in the Maximo file system. If a 3rd party system is used (i.e. SharePoint) the ModelStream tool will preserve and activate (i.e. make clickable) the URL used in the Revit Model. As you create the Geometry in Revit, the GUID is assigned (currently am manual process) to the existing assets in Maximo. You can then use ModelStream to update the assets with current information. Assets that do not exist in either system, can be added to a Revit Model (LOD 100) and synchronized with Maximo using ModelStream. |
||
|
In this case we are decommissioning an Asset in Maximo and Commissioning a new Asset. What’s key here is that the GUID from the Old asset is copied over to the new asset. Once that is done ModelStream will update the Revit model with the new asset information. | ||
|
When an asset is decommissioned in Maximo it is removed from service. However, due to limitations in the changes in Geometry this asset is not automatically removed from Revit. Currently these are two separate operations. If you copy the GUID from the retired asset to the new asset then you can continue to synchronize information. Alternatively if you create the new asset in Revit, it will create the Asset in Maximo via ModelStream. | ||
|
Through the ModelStream interface you can pull the asset information in Maximo and update the Revit model with the current information. Civil 3D will need to be updated from the GIS which is synchronized with Maximo Spatial. |
||
|
ModelStream has the ability to pass back to Revit a MX parameter (Temporary Parameter). This parameter can be a calculated or fixed value in Maximo. Revit can then be Themed to display this value. |
Overall the data that is contained the Airside operations is going to be contained in the Autodesk Civil 3D files. These files will contain, airport runway locations, In Pavement and Elevated Lighting structures, Underground vaults and Storm Water Systems to name a few. All of which are subject to FAA regulation. It’s critical for these assets to be updated in Maximo so that they can be incorporated into the regulatory Preventive Maintenance Routines.
In order to facilitate the movement of data between Civil 3D and Maximo, an intermediate data system must be used. Since we are talking about spatially located data sets, the natural connection for this data is the Maximo Spatial Module which is integrated with the Enterprise GIS system.
Airfield Assets that would be integrated with the GIS are those that are subject to FAA Regulation including:
-
Airport Lighting Vaults,
-
Runway and Taxiway Elevated Edge Lights,
-
In-pavement Runway and Taxiway Lighting,
-
Rotating Beacons, Lighted Wind Cones,
-
Precision Approach Path Indicator (PAPI),
-
Visual Approach Slope Indicator (VASI),
-
Runway End Identifier Lights,
-
Medium Approach Lighting System (MALSR),
-
Hazard Beacons and Obstruction Lights,
-
Standby Emergency Power Systems, Illuminated Guidance Signs
Maximo for FAA Part 139 Compliance
The following table shows the FAA 139 Regulations and how Maximo can be used to ensure compliance with them.
| FAA Regulation Section | Implementation in Maximo | Visualization through | |
|---|---|---|---|
| 1 |
139-339. (a) Condition of locations and assets |
Report – this can be demonstrated by showing details of completed and outstanding work against 'anything' – the report would be generated using the current status of planned, in progress and completed work - with extended time histories (when the problem was reported, when the work was started, what the work actually was and when it was completed - who signed the work off etc. | Maximo Spatial |
| 2 |
139-339 (c) Airport Condition Reporting |
Report – Similar to item #1, but with the addition of Spatial information to easily identify movement areas. Permit to work information can also be tracked to ensure that workers are adhering to instructions and safe working practices - workers / contractors and managers signing off against these instructions - which would be attached to work orders which reference the procedures. | Maximo Spatial |
| 3 |
139-339 (c-1) Construction or maintenance activity |
On the construction side of things, we could actually pick up potential construction and operational issues well in advance of construction starting - you would be able to do virtual audits, plan processes in the virtual work (all managed inside Maximo using the BIM integration) | ModelStream / Revit |
| 4 |
139-339(c-2) Surface irregularities |
Surface irregularities would be highlighted during inspection and service request / work orders raised - again using Spatial to identify on the map exactly where the problems are - and management the work using Maximo. Further integration with the Pavement Management System can be achieved by aligning the data between the two systems. | Maximo Spatial / Integration with Pavement Management System |
| 5 |
139-339(c-3) Snow, ice, slush, or water |
Snow moving equipment and de-icing equipment can be tracked in Maximo. PMs against equipment, planned to carry out more maintenance in the winter - ability to show what is in plan, what may not be serviceable due to other reasons Reports showing what equipment is available can be built. |
Reporting |
| 6 |
139-339(c-4) Snow piled or drifted |
Spatial element (outside of Maximo) can be displayed on the Maximo Spatial to show what areas of work are not available. | Reporting |
| 7 |
139-339(c-6) Malfunction of any lighting system |
Inspection of lights based on location of the light (Spatial) - locations linked to lights. Reports built to show the status of lighting equipment and how long it was out of service. | Maximo Spatial |
| 8 |
139-339(c-8) Non-availability of any rescue and firefighting capability |
Emergency vehicles and their status can be tracked in Maximo. Reports can be built showing the status of equipment. | Reporting |
In addition to the above table the following escalation rules will be put into place and can be visualized in the Maximo Spatial (GIS) module:
Runway Edge Lights (RWY E/L)
85 % operable for visual, non-precision or CAT RWYs
95% operable for CAT II & III RWYS
Runway End/Threshold Light
75% operable (no more than two lights inoperable at any runway end)
Runway Centerline Lights ( RWY C/L)
95% operable
Runway Touchdown Zone Lights ( RWY TDZ)
90% operable
Taxiway Centerline Lights (TWY C/L)
90% operable, in addition an unserviceable light shall not be adjacent to another unserviceable light.
Elevated Runway Guard Lights
No more than one light in a fixture unserviceable
In-pavement Runway Guard Lights
No more than three lights per location unserviceable nor two adjacent lights unserviceable
There are other lighting systems such as obstruction lights that do not have such stringent criteria but must be maintain in accordance to Part 139.
