|
Architecture - Workstation Management
Workstation Management is a layer designed to provide a standardized framework
for user screen application development. These standard features are exposed to
the top visibility layer allowing management level insight into user activities,
both at the aggregate and granular levels.
Within LIT Process Management, user activities are parsed into individual task
action called “Screen Applications”. These user applications match up with
either a work queue task, or start a workflow as part of an initial process. An
example of a related process task is an authorization step waiting approval or
rejection. An example of a manually started user application might be a screen
or set of screens to create a purchase order. In the manual example, a workflow
is selected and started to track along with the application to complete the PO
creation process of possible authorization, inventory checks, translating and
transporting of the PO.
Most simple manual applications typically start a corresponding workflow to
provide logging and visibility to internal system activities. It is good business
to design formal business processes for user activity and to follow them. The payback
comes over time as processes are evaluated, reviewed and modified. This powerful
capability allows action to be taken immediately or outputs can be fed to a
formal management methodology, such as Six Sigma or Total Quality Management (TQM).
 Work Group Queue Association
The first standardized feature is a set of coordinating filters to local pending
work queue tasks. This is done by defining which user work groups are
responsible for which swim lanes in the work queue. An example work group might
be “Dock Supervisor” which could be associated with several work swim lanes,
“Authorizations over $10k”, “QA Test”, “Missing in Action”, etc.
Company and Division information is included in the association to allow the
same named groups, tasks, swim lanes, and other fields within the work queue or
company user groups. Users are then limited in their view to only the work
authorized by workflow association of their work groups. As an example, Mary
may be included in several work groups with each work group associated to
several swim lanes.
Field Filters
After the work queue is associated, the view can be reduced further by using
user-defined field filters. These are filters based on field level variables
included in the work queue. User can view and select from the list or hand type
a text mask limiting what work they wish to act upon. An example might be
setting “IBM” for the company user field or date less than “Jan 1, 1932” against
a date field.
Assignment Maximum
Work Group Queue Associations and Field Filters can are used with a background
work queue manager to “Pull” and assign work to each specific user. The
Assignment Maximum is a total number of work tasks which should be assigned at
any given time to a user. The maximum is available for each work group opened
by the user.
Auto “Pull” Assignments
This is a background process which “Pulls” work from the work queue by following
the associations, filters, and maximums set above. A user screen allows the
setting of these association features and then opens the user workstation for
“Auto Work Assignment” or “Manual Work Assignment”. Towards the end of a shift,
the workstation can be set back to manual to work off any assigned tasks.
Remaining tasks can be pushed back into the work queue by selecting “Shutdown
and Reassign Work” instead of “Shutdown”.
The background process will write current status and the user’s names into the
work queue. By having a user name in the field, the work tasks is know to be
assigned and will not be assigned to someone else. Users however, may reassign
their work to other users at anytime.
Assigned Tasks
These are tasks assigned by a supervisor or other user moving their work to
another user. These work tasks are counted against the work group and will
throttle back the automated assignment feature.
Manual Assignments
Users are allowed to manual search and select any work they are authorized by
inclusion in their work groups. These work tasks are counted against the work
group and will throttle back the automated assignment feature.
Personal Work Queue Task List
All assigned work or tasks are now visible as a Work Task List which a user
selects from. Selecting a work task will bring up an associated user
application screen or screens to complete the specific task. Once the user
application completes or is cancelled, the user is returned to the Work Task
List screen to select the next waiting work task.
If the “Auto Work Assignment” mode is selected, the list is checked for
available space and filled with the next highest priority match of the set
filters.
Process Automation Suites
The LIT Process Automation Core seen on the left side of the diagram includes an
interface called the Workflow application Bus. The design allows Process
Automation Suites the ability to install and deploy user application code and
database structures enabling other suites access to their features. In this
way, suites can be designed as base applications or suites which extend other
suites. Suites can be designed with a narrow focus meeting specific
requirements for communications, RFID, special add-on screens, etc.
Work Group Association & Filters
Suites must include the names and associations of work queues, work groups, and
any user-defined filter variables.
Manual Menu Tasks
As explained above, not all work tasks are part of a current workflow process.
Many tasks are user initiated. It is expected that a default screen for user
login, including access to manual tasks, is supplied as part of the suite where
the home URL is deployed during the suite install.
Manual tasks will typically start a BPM process workflow for logging and
management visibility even if the workflow is simplistic. The standardized BPM
features are then used to monitor user actions and allow high-level process
evaluations and modifications including other coordinated operations or
asynchronous tasks.
Like all other user application tasks, tasks should be parsed into small single
step application screens. If any one task requires more than a few screens, BPM
process flow may be used to break the task into smaller manageable pieces. In
this way, workflow steps a user through the formal business process.
For User Applications which require multiple screens and steps to be immediately
performed, workflow may be designed in coordination with its steps and signals
to precede parallel to the user screen execution. In this way, monitoring
features maintain critical visibility.
Task to Screen Application Association
The reason for this association is to allow suites to identify and select the
specific application screen to be used with the current step (task), company,
swim lane, etc. Application screens are first developed as the default screen
application for a task. Additional application screens can be developed for
special specific requirements. The actual associations defined here are
deployed with the suite and available to other suites.
Screen Application Library
Once the application screen name is associated, a warehouse call is made to call
the proper application screen set.
User Business Application & User Interfaces
The user application screen includes the proper HTML code to call the
appropriate business logic. Calling the proper webpage is enough to implement
the user application.
Any number of User Interface styles can be used with each screen application and
are selected by use of the Task to Application Screen Association.
Field level visibility can be managed using a specific UI based on any of the
work queue fields, work group fields, user, or any other consideration.
|
