"ERPWEB produces desktop according to work the employee has to do. Companies with ERPWEB let people spend less time learning to use technology and more time doing their jobs. ERPWEB also enables employees to work from their homes. ERPWEB has integrated major discrete solutions and softwares available in market into one complete package. It's the only software required to run your entire business. Build your hi-tech business infrastructure with ERPWEB". 

ePortal is central tool contolling entire ERPWEB right from Applications, Business Logic, users, devices, roles & documents. From here, users can access all the systems and applications they need to do their work. Each ePortal Workbench is configured according to the industry sector and user roles involved. Preconfigured self-service are an important aspect of this core element.

For each employee, the Portal can be customized to address specific job needs. Customization takes place using role templates that draw functionality, data and services from ERPWEB, non-ERPWEB, Local and Web-based service and software components.

ePortal Workbench can also be configured for Customers, Suppliers, Banks, Government, Dealers & Distributors, Business Associates, Financers and Share Holders.

ePortal Workbench can also be configured for ERPWEB Customization Engineers, Implementation Consultants, Trainers & System Administrators.

Most of this Role based workbench are available pre-configured with ERPWEB which can be customized for every Business Scenarios & Business Tasks

Corporate Portal provides role based single point of access via a universal client called web browser. That means to any Internet Users it becomes website, for Accountant it becomes an Accounting package, for Shopfloor operator it becomes Lot Tracking tool, for Management it becomes PKI Reporting Tool.

ERPWEB Workbench helps cut through the maze. An innovative enterprise portal, it gives people a single point of access to information, applications, and services -- everything from other erpweb.com solutions to Web content, online exchanges, and enterprise systems. So people can quickly and easily get to everything they need to do their jobs.

Helping People Work Together -- and Work Smarter

With ERPWEB Workbench, your employees can collaborate with co-workers down the hall -- or across the globe. They can even reach across organizational boundaries, enabling you to forge closer relationships with customers, suppliers, and business partners. The result is seamless collaboration with an entire community of stakeholders.
Above all, ERPWEB Workbench frees people from information overload, helping them work faster and smarter. That means they can solve problems, seek new business opportunities, and explore new ways of working -- on issues that really matter to your business.

Workflow Applications

Workflow applications are primarily constructed around three concepts, which are known as the three Rs—Roles, Routes, and Rules:

• Roles. A role is the logical representation of a person or an application in a workflow process—for example, an expense report approver. Roles can change dynamically depending on who is involved in the particular workflow process. They allow you to easily abstract the different functions people perform in a workflow process. In ERPWEB you can define roles using ERPWEB Workflow Managers. You can assign Document's function level rights for particular users.
• Routes. A route defines what information will route and who will receive it. Routes can be sequential, parallel, conditional, or any combination of these. In ERPWEB you can define routes using Application Manager by way of various flags. Generally APPROVE, ONHOLD, REJECT, DONEFLAG, POSTED, etc. names are used. The flags becomes off & on on various conditions tp define the document route. Each locations in route is termed as Functions. Function rights are given to users as per assigned roles.
• Rules. A rule is conditional logic that assesses the status of the workflow process and determines the next steps. Here's an example of a rule: if the manager approves the expense report, route the report to accounting, or else send the expense report back to the submitter. A rule can be based on the properties of a message or on some other data source. Rules are defined by way of business logic in ERPWEB using ERPWEB Application Manager using SQL - Structured Query Language.

Let's take a brief look at a few workflow samples. The Expense Report application is one example of a workflow application that you can build with eApplication Server. Here's how such a workflow application might function: a user submits expense reports from a web application, and based on the total amount of the expense reports, a particular workflow process is started. If the expense is under $1,000, the expense report is automatically approved; if the expense is over $1,000, the report is routed to the user's manager for approval. The manager either approves or rejects the expense report, and based on his decision, another workflow process is initiated to either pay the expense report or inform the user that the expense report has been denied. Finally, if the manager does not approve or reject the expense report in a certain period of time, the workflow application reroutes the expense report to the manager's manager for approval.

Another example of a workflow application is a document routing application, in which a document to be reviewed is routed to users in parallel, user feedback is collected within a certain period of time and consolidated into a single message, and the consolidated message is sent to the originator of the workflow application.

Erpweb is full of workflow applications. Every business process operations in erpweb are based on this concept. e.g. Sales Process: Inquiry --> Order --> delivery --> invoice --> payments

"Setup Code of Conduct for your eBusiness. Design your eBusiness Rules with SQL Programming Tool. eRules allows you to customize your eBusiness Applications unto document level. Define SQL Logic & Database structure for each and every documents".

7 steps of ERPWEB System Design: 1. Project Costing: Man / Machine Utilization 2. Project Planning: PERT/CPM Charts 3. Function Design: Function module Diagrams 4. Process Design: Process Flow Diagrams 5. Organization Design: Hierarchy charts 6. Workbench Role Design:  Role Mapper 7. e-Documents Application Design: Register View SQL Logic Add / Edit View SQL Logic Print View SQL Logic Personalization DHTML CSS Logic Features VB Script Logic Database Structure for this document Tables Views Stored Procedures Triggers

Total Cost= Project Development cost as mentioned above + Cost of Developing above Plan & Design + Cost of Project Management