| FastERPWEB: ERPWEB Business Solutions Implementation Framework |
| ERPWEB is e-Business Operating System |
The real problem is how to deploy big-company technology—specifically, ERP applications—without spending big-company money. The answer lies in Fast ERPWEB. Second name of Fast ERPWEB is fast track ERPWEB or Accelerated ERPWEB.
FastERPWEB is ERPWEB's rapid implementation methodology specifically designed for enterprises that establishes tight time constraints for ERPWEB implementation. The value proposition of FastERPWEB is faster results, more certain outcomes to reach a live production status. The valuation of "fast, on-time, and on-budget" ERPWEB Implementation is extremely important to the market because of a prevailing myth that ERP requires years rather than months, to implement, and runs significant risks of over-running the consulting budget.
FastERPWEB customers are very likely to meet six ( or nine) month target schedules, can have a high confidence level in their target budgets, and are likely to achieve the majority of their expected business benefits.
FastERPWEB provides the "process glue"- a structured methodology that guides, supports, and integrates the activities of ERPWEB employees and partners - as well as specific tools to speed and assure the quality of the implementation.
FastERPWEB project plan is based on the underlying strategy of:
Implement today and begin a process of continuous change after implementation.
The core of FastERPWEB is shared learning of ERPWEB best implementation practices - reflected in project management tools, decision support tools, change management tools, and automated software configuration tools.
Another core concept of ERPWEB is that of Business systems, like the manufacturing process, can be viewed as a "flow," not in isolation. In reality, however, purchasing or sales, for example, are not functions to be optimized but single steps in the flow of a larger process. ERPWEB takes Just In Time(JIT) approach of job shop to simplify & connect processes into logical flow. ERPWEB has 4 basic hierarchy connected by way of Department --> Procedures --> Documents --> Functions. e.g each Departments like Sales has Procedures like Sales Order Entry, each such Procedures has documents linked to it like Sales Order, each such Documents has Functions like Create, Edit, Delete, Approve, OnHold, OffHold, Reject, Print this documents. Each concerned user will be given rights to operate that documents with functions. Each Document has shared folder for general purpose document sharing among that Document users. Document list produced before selecting a perticular document can also be considered as register. Thus ERPWEB is designed as virtual analogy of real business. Plus you can sequence your Procedures & Documents as per business flow.
Another core concept of ERPWEB is that of "Extended ERP System". That means ERPWEB has Intelligent components like Manufacturing Execution Systems(MES) & Advanced Planning System(APS) . This intelligent features gives ERPWEB power of IRP(Intelligent Resource Planning). Plus ERPWEB's XML based document exchange system based on Rosettanet standards gives ERPWEB power of XRP(Exchange Resource Planning). MPS provides real-time WIP and equipment status as essential inputs to APS Engine. While APS System then calculates accurate ATP Dates for customers. Thus IRP(MES+APS) with XRP(XML&Rosettanet) with (Web based)ERP makes ERPWEB very advanced tool.
FOLLOWING THINGS NEED TO BE UNDERSTOOD WELL BEFORE GOING FOR FAST TRACK ERPWEB:
The fast track isn't without its speed bumps, however. First, there is a greater
need to stick to the plain vanilla version of the package, with as little
customization as possible. There are also unexpected costs that pop up outside
the scope of the fixed-price contract. Although they are simpler than their
bigger brethren, the systems are still at the mercy of people—it's essential
to manage expectations and resistance to change, and provide thorough training.
Enter fast-track ERP. For the most part, fast-track packages are built like
their older siblings, based on best-practices templates. These templates are
designed to maximize efficiency and minimize customization, based on the
processes and applications that have proven most efficient. Smaller companies
often have undeveloped or underdeveloped processes, so they're willing to take
the advice of ERP vendors that have attempted to refine those processes. They
can learn from the suffering of their larger counterparts. There is less room
for change but at the same time, less room for error.
The biggest difference between traditional and fast-track ERP implementations is customization, or the lack thereof.
Traditional
ERP packages are often heavily customized, requiring consultants, time and
money. The price tag on the doomed ERP project, for instance, totaled more than
$1 million, according to the press reports. By contrast, most ERPWEB rapid
implementations cost less than $50,000.
It's important to keep an open mind when
considering changing business processes to fit ERP packages, experts say.
Customizing packages should be a last resort, as the practices included in rapid-implementation plans are usually
better than existing practices. That's a major break from traditional ERP, which
often relies heavily on customization to integrate applications and processes.
Given a choice between custom and preconfiguration, choose the
preconfiguration.
If you think you've developed some terrific process to do purchasing or sales contracts or whatever process you're doing, I've got a funny feeling that ERPWEB probably has a good way for you to do it. You need to get in the mind-set that you just changed jobs, you are working for a new company, and you are learning a new way to do your job. It is the best practices that are key. Don't think about trying to replicate the bad process you had. Think about the ideal process you want to get to.
Fast-track ERP contracts aren't like traditional ERP agreements. These contracts fix a time line, a price or both, in advance.
The
project planning process, therefore, becomes more important in a fast-track
setting than in a traditional ERP setting. The fast-track contract guarantees
both what the vendor will give and what the buyer will get. There is little room
for application customization with the fast-track route. Companies have to know
what they need and make sure they bargain for it up front. The vendor will then
be able to base its implementation plan on those decisions.
Another regular speed bump involves integrating existing systems. There are
often surprises lurking in legacy systems and processes.
Generally speaking, surprises aren't good. They're even more shocking for a company trying to contain costs and schedules. Just as in setting up a contract, planning is paramount. Replacing systems that automate the way a company does business is rarely easy, but it can be more complicated for a company trying to move from simple tools to sophisticated ERP applications. Often, that move is accompanied by growth that sparks the need for an upgrade. A smaller company that begins an implementation without sophisticated systems or processes needs to ensure the selected package works for a company of its size.
Technology gets a lot of attention during a fast-track implementation, but it ends up being only as effective as the willingness of the people who use it to do their jobs. Ultimately, employees, IT staff and even customers will determine a project's success. The time to start communicating is as soon as the project begins. Managing its scope is often a hidden difficulty. On one hand, some employees will be reluctant to use a new system and will have trouble thinking outside the constraints under which they already work. On the other hand, some employees might expect too much from new technology. Those expectations might lead to requests to add more functionality—which can ultimately defeat the purpose of installing a plain vanilla, template-based, fixed-price or fixed-time package. Fast-track ERP packages offer full functionality, but additional features cost money, and determining how much is necessary is one of the most important steps in planning an implementation.For details read our ERPWEB Implementation Strategy: Detailed Presentation in PowerPoint(66kb)
| ERPWEB provides complete e-Business Infrastructure at lowest costs |
| This document last updated on |