Being able to tailor your WMS solution to your needs without having to customize your the sore software solution is key to any best of breed software solution today. In the past companies tended to either sell "out of the box" solutions that could not be adjusted to a companies needs or "customizable solutions" that could be changed as a company requires. Unfortunately the solutions that allowed for customization generally become so specific that when a new version of the solution was released, the company could not upgrade without major redevelopment.
DATASCOPE WMS has been built with a range of tailoring tools that allow your company to install the core software solution and then integrate tailored solutions without compromising the core software. This is done with the following solutions:
E.Net API Layer
This API layer has been developed to allow for 3rd party integration to our core software layer while maintaining the business rules set within the DATASCOPE software. A customer can now develop a fully customized solution that replicates a key aspect of the DATASCOPE software but includes a host of specific functions only needed by this customer. The custom solution is installed and integrated to the core DATASCOPE WMS via this e.net API layer. The integration layer makes use of XML schemas which typically do not change. This allows the DATASCOPE WMS to upgrade to future versions with little impact on customized 3rd party software. In fact much of the core software applications transact through these same API components making the layer particularly robust.
All major transaction screens include the ability to add VB script to a host of fields and buttons. This allows a customer to edit a traditional screen to include some extra prompts, check boxes or enter fields during normal processing. For instance a pack station checkout screen can be integrated extensively to a 3rd party logistics solution by simply adding VB scripted functions into one of the standard DATASCOPE checkout screens. The user would not even know that the final solution includes customizations to automate all LSP label printing for instance.
A range of triggers have been included into the software to allow for a range of automation. For instance on releasing an invoice we may configure a trigger to log user specific data into a log table, or we may add an automated trigger to fire a 3rd party software program when a user skips a line of a picking slip. These triggers are typically used for the following:
- Pop up warnings to a user
- Pop up an additional data entry screen
- Fire of an automated email
- Run an external project
- Write a log to a log table