Implementing Panatrack – Overview

This article will provide you with the overview of the PanatrackerGP implementation.

Planning

The first step of any successful implementation is the planning. This includes:

  • Project setup. Panatrack will set up a project and assign a project lead. The standard project lists are imported and any additional project steps specific to your organization are added.
  • Kick Off Meeting. The kick-off meeting is an important step as it provides you, as the new customer, with an overview of our implementation and connects you with those on the Panatrack team that will be working with you. Typically, the timeline is established based on go-live date.

IMPORTANT INFORMATION ON SETTING A GO-LIVE DATE

Although we can get the system installed in the matter of a few hours; here are things to consider when looking to define a go-live date.

  1. Configuration. PanatrackerGP has hundreds of setting options. As you go through your first training session, settings are adjusted based on the workflows you discuss with us.
  2. Training. Panatrack typically completes a train-the-trainer approach. This provides the ability for you to develop a champion within your organization to support additional training and address questions from the users during their onboarding.
  3. Testing. It is recommended that you have a test company database (or test environment) set up to support training activities as well as testing. Once the initial configuration and training is complete, it is recommended that you use the system within a test environment for several weeks prior to your actual go-live date. This allows you to confirm and test your configuration setup and make adjustments, and also confirms that your GP database is setup based on the functionality that you are using.
  4. Changes to Workflows or GP Setup. It is not uncommon that adding PanatrackerGP will result in evaluation of processes and workflows, as well as enabling GP features that are currently not being used. A good example is enabling multiple-bin functionality in GP. Enabling this feature requires additional planning that may add on to the implementation timeline.

System Prerequisites. Confirming prerequisites are in place to support the PanatrackerGP install.

  • Microsoft Dynamics GP installed and configured.
  • Microsoft eConnect installed and configured.
    • eConnect needs to be installed on the same server.   We do the triggering, so there is no “pulling” or “pushing”.
  • Functionality Currency in Dynamics GP setup.
  • SMTP for email alerts.
  • Microsoft IIS installed and configured.
  • .NET 4.5.1 or later (If NiceLabel purchased .NET 4.7.1 or later) framework installed.
  • Wireless 802.11a/b/g network implemented.
  • Mobile computer devices connected to the wireless network.

Hardware selection and shipping. Panatrack will work with you in your hardware selection. Selecting hardware early gives us the opportunity to reserve the hardware (during times of hardware shortages). When you purchase hardware through Panatrack, we typically schedule the shipment of the hardware to arrive 3-5 days prior to the scheduled install date. We don’t want to ship hardware too soon based on the return policies of our distributors.

Install

The actual install typically takes only a few hours. It will require our team to work with your technical resources.

  1. The server side of the install is completed first.
  2. Panatrack will work with your technical resource to go through the steps of installing to the device. Your technical resources are responsible for connecting your devices to your network prior to the install. Any additional device configuration steps will also be reviewed. Your technical resource will then complete the install to the balance of the devices.
  3. Panatrack will provide a quick review of the portal and may make a few configuration adjustments. Assuming the first device is setup to a test environment, Panatrack will run a quick adjustment transaction from the device to confirm communication and GP compatibility.
  4. Setup of email notification.
  5. Integration setup (running of scripts to support additional extended features).
  6. Label printing setup (if purchased). This is often completed independent of the install step.

Training

Panatrack typically uses a train-the-trainer approach. Training is scheduled with your training lead resource based on the install date. Panatrack offers both remote or on-site training as options. On-site training requires scheduling for travel and therefore needs to be identified as the training option during the planning steps. When training is remote, there are often multiple shorter sessions scheduled. Training includes:

  • Review of the Panatracker portal administrative tools and concepts.
  • Setting up profiles and users.
  • Review of configuration options.
  • Walkthrough of each transaction with adjustments to configuration settings based on desired workflows.

On-site training will typically include process and workflow review. Depending on the solution being implemented, plan 1-2 days for on-site training.

Testing and Go-Live

Panatrack recommends at least two weeks for testing to finalize and establish workflow changes. The testing step is important for a smooth transition to your go-live. Ideally, the training lead(s) will complete the testing and then train the balance of the users. Panatrack can also be contracted to complete all end-user training.

It is recommended to inform Panatrack of your go-live date. This allows us to make sure we have the support and implementation team available should any additional questions or issues come up. If you will be transitioning to go-live outside of standard business hours or if you would like a Panatrack resource on-site for your go-live, please contact Panatrack to coordinate.

Once you are live with PanatrackerGP, any questions or issues should be reported through the Panatrack support infrastructure.

Approximately 30 days after training (or known go-live date), you will be contacted by the Panatrack project coordinator to confirm your success and answer any additional questions. Your project will then be closed, and you will be transitioned out of the implementation phase.

Was this helpful?