In 1996 we built “ITworx” designed to run on Win3.1 with 8Mb of memory. It was pen aware, had a seamless map base and scale dependent display, a Street Gazetteer, it would read and write CAD files, had an MS-Access data store, interfaces to Smallworld GIS, Intergraph, MapInfo and SAP R/3 Batch Input (equipment, functional location, notification, work order) – we sold it exactly once as it was technology- and not business-driven, and far too advanced to ignite the imagination of business decision makers.
LatLonGO/HERE Integration with SAP-ERP
Business process client embedding results in a very tight integration, for example the LatLonGO two-way online integration with SAP Classic or NWBC based Plant Maintenance (SAP-PM), Multi Resource Planning (SAP-MRS) or the two-way off-line SAP-WorkManager Integration mentioned earlier.
An even higher degree of client sophistication has been developed in form of a LatLonGO/HERE special edition branded cableScout mobile for the business requirements of the global Telco Cable Management industry.
cableScout mobile has been specifically developed for field crews who rely on up-to-date information for their work, namely the efficient and effective organisation of the operation and fault suppression of managed networks. The major benefit of cableScout mobile for the user is that he always has all the important information available offline on his tablet.
The entire network infrastructure of buildings, ducts, micro-ducts, cables, cabinets, components and signals is implemented on the device so no internet connection is required.
Feature-rich functions support the user in his daily work: For example, the system can search for a faulty signal and the corresponding route can be displayed both in the schematic plan and on the map itself.
By inputting an OTDR measurement value at the relevant port, the location of a fiber fault can also be visualised in the map. The navigation function navigates the user directly to the relevant location when required.
With cableScout mobile the user can respond immediately to faults without having to return to the office to fetch relevant documentation. This is particularly important when routes with Service Level Agreements fail and where the cause of the fault has to be found and removed as quickly as possible.