The Purpose of the I.T. Dashboard System:
IWS provides the ability for documents to be routed around an organization in a logical organized fashion. The system allows for department administrators to specify their business processes, through rules, giving the ability to automate a department's workflow. The IWS platform provides robust security features which enable department administrator to control processor functions. All queues, document types, and indexes, are defined by department administrators. This gives organizations the ability to deploy IWS under almost any business process. - The I.T. Dashboard project system allows the IT leaders, managers, and staff to keep project dashboardsin a web based system. This system provides an easily accessible interface for I.T. and business users and keeps a historical record of each dashboard project for each update made.
| Info |
|---|
This documentation contains information regarding all areas of the Dashboard system including areas that may not be accessible to all users. |
Common Terms Used in the Dashboard System:
Index
Information about the document that can be used for retrieval and rules processing. The information attached to the document should be as unique as possible for easy document searching. Examples of indexes include; client number, social security number, member ID, dollar amount, date, client name, etc. Indexes are the key data elements you can use to identify which member/applicant/client/account each document belongs to that enters the IWS system.
Indexing
The act of data entering a user defined index (above) to go along with a new document when it is brought into IWS.
Document Type
A general categorization to assign to a document in the system. Examples; Enrollment Form, HCFA form, Proposal, Contract, Payables Form, etc. Document types are defined and customized by each department in IWS.
Queue
These are the digital “inboxes” of IWS. Think of them as the “in basket” on someone’s desk, or their mailbox in the mail room. Queues can be setup for individual access, or for multiple staff to work from. You can name a queue anything you want. Like Document Types, Queues are customized and defined by each department.
Queue Rule
A rule, or set of "if" conditions (Queue Logic), defined in the system by a user. A rule tells the system to what queue(s) (Queue Flow) the new document should be routed. The rule is based on the index data attached to the document.
Queue Logic
"If statements" used on a Queue Rule to evaluate document indexes. Example: If the Index field EMPLOYEE_STATE equals "TX" then route the Document to the TEXAS DATA ENTRY Queue.
Queue Flow
Dashboard or Project
Both terms refer to a single instance of a "project dashboard" in the system. The goal of each dashboard is to provide the business units with an ongoing status of large I.T. projects.
Status
Each dashboard will display an overall status and a status for each milestone within the project. Status examples: On Track, Delayed, At Risk, Complete. Each status is color coded for quick reference.
Milestones
Milestones are indicated on each dashboard and represent a specific goal or main element to complete during the project.
Main Menu
This term refers to the primary menu options listed in the main header section of the Dashboard system. Depending on the specific security access granted to the user, only certain menu options will be visible. This documentation contains information regarding all areas of the Dashboard system including areas that may not be accessible to all usersA list of Queues attached to a Queue Rule to which a document gets routed through when the Queue Logic rule is found to be true.
Related pages
| Content by Label | ||
|---|---|---|
|