The Request Management System

    Workflow existed before computers.     In pre-computer days, workflow consisted of a slip of paper known as
    a routing slip. What everyone really needs is a simple application that replaces that critical piece of paper.

    Max Rosenblatt, 2006

Workflow is now and has always been important to managing businesses. Workflow pre-predates computers by years. It was always an essential in managing businesses. Workflow is a part of the most recent generations of computer applications. Workflow insures tasks are moved along to completion.

However, not everything done in a modern organization fits neatly within their computer applications. Very often, tasks also span organizational boundaries. One alternative would be to spend the time and energy to build the comprehensive mega-application that included all business processes for all parts of the organization. The risks associated with such a project are so great that very few organizations would undertake this project.

An alternative to this approach are specialized workflow management systems. These are sometimes known as Service Delivery Management systems. These enable workflows that cross application and organizational boundaries. These are the modern replacement for the routing slip or traveler.

"By 2005, 35 percent of North American and 65 percent of European internal service organizations will have implemented a service based business model. Enterprises are increasing their focus on internal cost savings and process efficiency. Managing service requests and delivery tasks with a standardized service catalog is one necessary component to improving service delivery capabilities and efficiencies."

Colleen Young,
Research Director, Gartner

The Request Management System (rm^s) is designed to do exactly this. rm^s contains four elements that make it ideal for implementing BPM solutions that cross application and organizational boundaries. These are:

· Easy to implement, forms presented the users with a standard Internet browser.
· Workflow, built with point-and-click tools, which supports complex workflows that include main forms,
branches and common forms.
· Built in, automatic email notifications for request owners, request fulfillers and workflow managers.
· Reporting to help managers control work and identify process bottlenecks.

Setting up rm^s is easy. In fact, IT OnTime’s experience shows that it takes up to ten times as long to develop a logical workflow as it does to implement it within rm^s. An experienced rm^s administrator with good workflow definition skills can set up a typical catalog in two hours

WHEN TO USE rm^s

Any business process going through multiple hands that requires tracking and a traveler document. Especially true where the person requesting the work wants feedback of progress of the work. Examples are:
		Any business process that requires a saving track record of activities for compliance to regulations such as Sarbanes-Oaxley
		Loan processing
		Customer service fulfillment
		Legal document preparation
		Complex documents such as budgets or requisitions with multiple review steps
		Any internal service provided internally where fulfillment crosses organizationa and application boundaries.

Just about any situation where the person wanting the work done wants to know the progress of their request and multiple people participate in fulfilling it.

You can try rm^s by clicking here or order rm^s by clicking here.