|
|
|
ESAMS: ENGINE-ONLY SHIPPING AND MANIFESTING SOLUTION
ScanData deploys its Traffic Management components, selected Data Management — Inbound/Outbound components, and its electronic Automated Processing (processing engine only) and Manifest Management components in order to interface with multiple existing systems in an enterprise and provide high-performance data processing and resultant electronic carrier compliant communications. UTILIZING ESAMS Before any packages are processed using ScanData's ESAMS product, traffic managers (in conjunction with ScanData's training personnel) use the Traffic Management components to configure the system according to their company's specific transportation business rules. These Traffic Management components are mainly used during system parameterization to set the system up and are then only used sporadically to maintain system configurations. With a fully parameterized system in place, daily processing can take place. Package Level Detail (PLD) data is passed to ScanData via one of the mechanisms in the Data Management - Inbound component grouping, and carton processing takes place automatically as either a piggy-back on the inbound data processing or as processing triggered by another communications feed from a physical processing device, such as a sorter. Once processing is complete, ScanData generates all required carrier compliant electronic communications as well as passes processed data to an archive and/or host system via one of the mechanisms in the Data Management — Outbound component grouping. If an archive exists, traffic managers can also use the delivery confirmation and reconciliation modules of the Traffic Management component grouping to research carrier delivery and charge information and reconcile it against manifesting data to support carrier billing reconciliation.
| |||||||||||||||||||||||||||||||||||||
|
|