A Windows CE/Android-based mobile computer that has a touch screen interface, generally a 1D or 2D barcode scanner, with the Qwix WMS application installed and configured.
The Windows-based desktop application presents the user with grid-based data “Views”. These views have powerful data representation tools such as filters, groups, and sorting capabilities. The Application allows users to View and manage various data sources related to a process.
A View is a grid-based representation of data from our SQL database. The views may incorporate multiple sources of data represented in a relational way (typically master & detail). This may also include several “Action buttons” and Reports. Views are the primary mechanism used by administrators to manage a process.
An action is represented as a button in a View. These buttons are often context/selection sensitive and may contain several execution parameters requiring entry from the user. Action buttons allow controlled manipulation of the selected data/process flow.
A report is a formatted representation of data. The report is normally formatted for printing on paper stock, alternatively, it can be formatted so that it is more appropriate for exporting to an external program such as MS Excel. Some reports are displayed/printed from the Qwix Admin Application, whilst others are automatically printed by Qwix AIR in the background.
a set of criteria applied to the columns in a View that limits the visible data.
A process used to integrate two data systems. Typically, an external system and Qwix WMS. Data is often integrated bi-directionally. Data can be imported from the external system into the Qwix Database. Similarly, data can also be exported from the Qwix database to the external system. The mechanisms used can vary from system to system.
A process that actions a set of data manipulation steps, when certain criteria are met. This allows for either real-time or scheduled automation that facilitates the workflow related to a process as implemented in Qwix.
In Qwix an instruction is deemed to be any task that is initiated by the Qwix System and is to be executed by a mobile device to satisfy the manipulation/movement of stock items through a process/space.
The execution of an unsolicited (not instructed) task on a Mobile Device. No instruction was generated by the system, and the task was initiated by the user.
The software that managed the scheduled running of scripts. AIR is typically used to manage the running of scripts that are responsible for Integration and Automation, as well as server-based Printing.
This module/process is the Qwix Standard template for this process/module. It forms part of the Qwix WMS product suite, all intellectual property of the software and its configuration remain the property of Qwix Technology.
This document outlines the Automation, User Interaction, Reporting, and Technical definition (SQL and Integration) of business logic and process flow, for the Qwix Standard Module.
The design of each process/module and its implementation are not tailored to suit a custom process. Any requirements to deviate from the Qwix Standard Template will be specifically outlined in a separate customer specification document. The implementation of any customizations introduces unknowns and risks to the project. Not only in its own impact on scope but also the secondary impact on affected modules and processes. Care should be taken to understand these risks, to accept them, or to reject the customizations where possible in favour of re-aligning the process to standard.
The various functions must be able to execute in a similar or faster timeframe compared to the current method. This is dependent on the new environment performance being adequate, and the various new functions being optimized for performance. Where possible Realtime executions will be used in favor of scheduled sequences.
Users log in via usernames and password both on the mobile devices and the Qwix Admin Application. User Functions on the Admin Application may be limited by role through configuration. The system also supports the use of an active directory as an authentication method.
The basis of the application is tested thoroughly, and as such is inherently stable and reliable. Any implementation thereof becomes a customized solution as it is usually tailored to the needs of the customer. As such the system is not guaranteed in ANY way to be error free.
Errors will be identified as part of the normal implementation life cycle, or as part of the Qwix support service. Remedying of errors is seen as a normal part of our service offering and may be billed for accordingly irrespective of the cause of the error.
As part of an implementation, this document will form part of several documents similar in format and scope. Together, they form the FULL scope of implementation. The combined documents will include at least the following information:
To define the module/process, it is broken up into THREE main sections:
This section aims to provide all the information pertaining to what the required inputs are that will satisfy the initiation of the process. These generally include Integration, Automation
This section is more pertinent to the Users, as it mostly defines the ways that users interact with the system, but also how the system is set up to handle exceptions, and track and report on data. Trackable data is the lifeblood of the system, and every effort is made to make as much data accessible to the user via the desktop administration in the form of grids as well as defined reports. The user interactions implemented for the mobile application are also defined in this section.
After the user(s) have executed the related instructions via the mobile application. Process conclusion needs to happen in several ways. That can be automated, or user-driven interactions. The net result will again be the processing of data into another form, to be posted or applied. This section outlines the steps that are taken to end the process.
Although Configuration options are referenced throughout the other sections, they are listed and explained again for easy reference, and can also be used here to outline the selected options at a glance.
A List of all the automations, and automation branches is listed here in summary again for purposes of configuration. It provides an easy summary to be filed for implementation purposes.
A Full list of all STANDARD reports relevant to this module.