In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |

  •     QAD Glossary

  • PEM Components
    This section describes the basic components of PEM.
    Master Shipping Plan
    The master shipping plan contains sequences of:
    Expected events for the journey of a package.
    System-generated alerts/exceptions that can be raised automatically when an event does not occur as planned.
    EOD Process and SOA Blackbox Message Actions
    These actions attach an appropriate shipping plan to each package in each shipment in an EOD batch. Standard PRECISION rules and rule books determine which shipping plan to use.
    Attach Shipping Plan
    This process also designates a CT, CA, and CC-type user group as the owner of the shipment pack plan. The group assigned as owner is based on:
    The packing location used to ship the shipment.
    The carrier account associated with the packing location.
    CT, CA, and CC Owners
    You have visibility of the shipment plan in the Web UI according to the data segregation configuration associated with your user ID. Initially, the CT team is assigned management of a pack-related exception. However, after the CT team reviews the exception, ownership can pass to the carrier for feedback.
    Note: For more information on user permissions, see Data Partitions.
    The carrier sends EDI or CSV files containing tracking data and status updates. PEM uses this information to match the tracking numbers in the carrier files to existing PRECISION shipment packs. However, if the carrier data relates to shipments that were not shipped using PRECISION, no match is found. In this case, the system can create a skeleton or light shipment transaction. You can then record tracking information in the PRECISION database for subsequent tracking and alert management in PEM.
    Note: For more information on configuring light shipments, see Light Shipments.
    Carrier-Provided Codes
    Each carrier has many different statuses with their own specific codes for events and alerts. Therefore, the carrier-provided codes are mapped to a reduced set of generic status codes for use in PEM.
    Generic Status Codes
    The mapped generic status code determines which event has taken place. The event indicates if the shipment pack is still on course according to the shipping plan or contains an alert or exception.
    In the shipping plan, each event can be allocated a time frame during which the system expects a further event update subsequent to the last status. For example, if the current carrier status is Manifested, you can expect to receive the next event update of In Transit within a three-hour time frame.
    System-Generated Alerts
    If no scheduled event activity is received in the prescribed time frame, a system-generated alert is raised. The alert means that the shipment is in an exception status and has deviated from the shipping plan.
    Shipping Plan Updates
    When the mapped generic status code indicates that the carrier has issued an alert or exception instead of an expected event, the shipping plan is updated with the relevant alert or exception type. The update includes a default priority that indicates the severity-level of the alert or exception.
    Web UI
    The Web UI enables you to monitor shipments and review current statuses such as Last Event and Last Alert raised. Generally, you only review a subset of shipments at any one time. Specify the subset by applying filter criteria.
    Search Options
    You can perform searches based on:
    Explicit transaction criteria
    Use this type of criteria to manage packages when it is not necessarily known if there are alerts/exceptions. You can query for packages where other information is known about the package, such as the tracking number.
    Alert/Exception criteria
    Use this type of criteria to manage packages when an alert or exception has been raised in the system; for example, because the packages are undelivered.
    If the CT identifies an issue with the package, they can raise a tracer request with the carrier to initiate an investigation into the package. The CT can trigger the tracer request using the PEM Portal. A tracer form is e-mailed to the carrier, who then records the tracer in the carrier network.