1. Able to import data directly from Microsoft Excel (*.xls), Microsoft Access (*.mdb), and DBase/FoxPro/Clipper (*.dbf), Fixed Width ASCII, and EBCDIC files. This feature does NOT require MS Access or MS Excel to be installed on the end-user's computeri .
2. Because Asset Manager can dynamically re-map the source fields to the appropriate Asset OnSite® fields, Asset Manager does not require the incoming fields be in any pre-defined order or naming convention.
3. Asset Manager can convert client code values (i.e., domain codes or "lookup codes") to Asset OnSite® codes.
4. Data mappings can be saved and re-used for subsequent file imports. Mapping to the Asset OnSite® system is done from a data dictionary - if the database changes, simply change the entries in the data dictionary.
5. Asset Manager offers a full-featured scripting interface and engine, thereby allowing sophisticated expressions, logic and algorithms to be applied to data on an as needed basis.
6. Asset Manager can be automated to run in an unattended, scheduled mode, enabling off-hour "tape cracking".
7. Although implemented as a windows desktop application, Asset Manager is Internet-enabled. Users can perform data mappings and transformations on Asset Manager locally, then automatically transfer asset data and mapping specifications securely over the Internet for "cracking" into the hosted Asset OnSite® database.
Figure 1: Asset Manager
i MS Access and MS Excel also offer support for a broad range of input formats. As a result, if MS Excel or MS Access were to be used as an intermediate conversion utility, the number of file formats supported is only limited to the extent MS Excel and MS Access are currently limited.