|
|
Demand Management
-
1. New Issues
- New Issues may originate nearly
anywhere within an enterprise. They may appear in
current projects, customer service departments, help
desk groups, and external systems. Highly diverse issues
may be tracked even if they contain data or data
structures that are unique to the organization, or to
the project itself.
- 2. Routing Rules
- Routing Rules define the resolution
path for that issue. Assignments, roles, flow,
placement, review, approval process, and other
requirements for success are determined here.
- 3. Notification
- Notification by email may be sent
automatically as needed to facilitate collaboration and
synchronization via user-defined software settings.
- 4. Review
- Issues may be automatically routed
to projects, tasks, teams, individuals, or may be routed
to a person who evaluates and re-routes them. Further,
if a review is not required at the time for certain
issues, they may be automatically linked together for
ease of approval later on.
- 5. Issue Assignment
- Issues can control workflow by
being linked to projects, tasks, or other issues.
- 6. Issue Approval
- Issue tracking may or may not be
set to require a final approval before being declared
complete.
- 7. Issue Completion
- Users are automatically notified of
any relevant status changes including completion.
Approval flows may be set up in almost any manner. For
example, a group of linked issues may be declared
complete whenever one of the linked issues is marked as
completed.
- 8. Reports
- Reports may be generated quickly
and easily by searching the enterprise's project
databases. The project manager may wish to report on
outstanding issues or on issues completed this week.
Timely reports help project stake holders and
organization managers stay interested, up to date, and
in the business loop. Search capabilities include
grouping, filtering, and/or aggregating the information.
|