Integration

In recognition that software applications do not exist on their own and unconnected in a solutions framework, we have developed significant skills with respect to interface development.

​

The experience gained in building interfaces between the SmartAsset predecessor product FMMS, and ERPs such as SAP, MIMS, JDE and Oracle Financials played an integral part of the interface design process for SmartAsset where particular use of the multi-tiered architecture to address interface requirements held a strong focus.

​ ​

The success of this design work was borne out when interfaces between SmartAsset and two of the Microsoft Dynamics products ie. AX and GP, were successfully delivered to new SmartAsset customers.

​ ​

In addition, an interface to plant monitoring/recording systems has been implemented whereby equipment meter readings including clock hours and kilometers traveled are being automatically uploaded into SmartAsset for the express purposes of scheduling preventative maintenance activities.

Multi-Tiered Approach

By utilising a multi-tiered approach to addressing interface requirements, SmartAsset enables:

• Tailored libraries to provide bi-directional access to external data designed to meet customer’s specific requirements.
• Upgrades to core product may be implemented without impacting interface tiers, thereby protecting customer investment in specific interface development.
• Double-handling of data is minimized.
• Clients can implement the SmartAsset product knowing that the interfaces that they require to their existing installed software are available or may be developed.
• The forced compromise in selecting monolithic ‘fully integrated’ suites of software that claim to meet all business functions can be avoided. ​​
• These solutions typically entrap the user into altering business methods to suit those of the package.

By utilising a multi-tiered approach to addressing interface requirements, SmartAsset enables:

3rd Party Integration

Integration to third party products is an important requirement in the quest for a common business interface. This is particularly significant to owners of linear assets, where visualisation of such assets and the information relating to them is critical. We use a ‘docking’ approach for this purpose.

For example SmartAsset provides the ability to dock and use Virtual Earth to display assets and associated maintenance activities. This is further complemented with the GPS capabilities (originally added to SmartAsset) for displaying geographically dispersed assets including those of a linear nature. The TasRail infrastructure GPS data that was recorded by traversing their Railway track and provided to us as a spreadsheet has been migrated to a SmartAsset database and used for overlaying the mapping capability of Virtual Earth via the .NET based callback and embedded capabilities provided in that tool.