Microsofts latest ERP push: What does it mean for SAP, Duet?

It has been apparent for a couple years now that Microsoft was pushing upwards in the Enterprise space. But are they really ready for prime time? They seem to think they are. Here is an article from an SAP site about Steve Ballmer’s keynote speach in San Diego this past week.

———————————

Microsoft had some strong words about SAP at last weeks Convergence conference in San Diego. Does this signal the end of the happy union between the two companies?

Microsoft CEO Steve Ballmer called SAP his companys “big competitor” in the enterprise market and said that Dynamics has a simpler set of processes, requiring less customization than SAP and that it is “enterprise-ready.” “When it comes to scale, reliability, transaction volume, theres nothing in our design mentality, philosophy or anything else that should hold us back,” Ballmer said. “We want to give people the capabilities they want, the capabilities that their users can use, and the capabilities that you can get implemented at whatever size, whatever volume you are.”

Microsofts latest ERP push: What does it mean for SAP, Duet?
Microsofts latest ERP push: What does it mean for SAP, Duet?
By Jon Franke, News Editor
21 Mar 2007 | SearchSAP.com

Software Implementation Projects And Six Sigma

Software Implementation Projects And Six Sigma
Tony Jacowski

Six Sigma concepts were originally developed for use in the manufacturing sector, but are now increasingly being used in the services sector as well. Use of Six Sigma concepts in the software industry has become quite common, but what many people do not know is that Six Sigma concepts can also be used in software implementation. People who have experience in software implementation projects know that such projects often do not take off as planned and may be subjected to schedule overruns and recurring problems. This is why many software companies opt for employing Six Sigma concepts during the process of software implementation at a clients site.

Common Implementation Problems

The two most common problems faced during software implementation projects include customer requirement problems and schedule estimation problems. By employing Six Sigma concepts in software implementation projects, professionals can better understand the needs and business objectives of the client. This way, they can make sure that the software implementation project is successfully completed within the stipulated timeframe. Employing Six Sigma will also ensure that no additional costs are incurred during the implementation process.

Understanding Client Requirements

Software products are normally designed for increasing the efficiency of a business process in accordance with the goals and objectives of the client. Most of the problems related to the software arise during the implementation stage when the client finds out that the software is unable to achieve desired objectives. This situation arises when the client passes vague information about requirements to software developers or when developers are unable to clearly comprehend client requirements.

Six Sigma helps in avoiding problems during the software implementation stage by bridging the gap between actual requirements of the client and what is eventually understood by software developers. Many people believe that Six Sigma is only limited to the use of statistical methods. What they do not know is that Six Sigma follows a disciplined approach that can solve any type of problem, whether it is quantitative or qualitative. This is evident from software companies that have successfully employed Six Sigma concepts in solving qualitative problems that arise during software implementation projects.

Generating Schedule Estimates

Schedule estimation is another common problem faced during software implementation. Mistakes in schedule estimation can affect the outcome of an implementation project; as such projects are often required to be completed in a specific timeframe and within available budgets. Implementation projects are often delayed because planners make the implementation schedule without considering indirect factors that might affect the project. Planners often fail to foresee that implementation can get affected due to the size of the software, location where it is being implemented, internal politics, authority, and governance.

Employing Six Sigma concepts in preparing schedule estimations will help planners to effectively include all these factors which may indirectly affect software implementation projects. Based on the past records of the client, Six Sigma statistical tools will generate an efficiency chart, which provides details about all types of problems faced with the client during software implementation projects. The chart displays the time taken to resolve such problems and techniques that were employed to solve such problems.

The chart also displays any additional time or costs that went into the completion of the project. Planners can use the information given in the chart for giving due consideration to all the indirect factors that can affect software implementations. This will help in generating true schedule estimates, necessary for the success of software implementation projects.

Tony Jacowski is a quality analyst for The MBA Journal. Aveta Solutions Six Sigma Online offers online six sigma training and certification classes for lean six sigma, black belts, green belts, and yellow belts.

Exposing The 7 Hidden Costs Of Putting-off Your ERP Upgrade

One you are up on an ERP system, for how long to you continue to pay maintenance? The answer is indefinitely if you want to keep current on the software. Hopefully, you have not modified the core software, such that you have broken your upgrade path. If you haven’t then you can move along with the software as it develops and matures.

This article shows the key things you need to keep in mind as to why you should continue on maintenance and continue to upgrade your software. Keeping current will provide you with added benefits that you may not be aware of.

Exposing The 7 Hidden Costs Of Putting-off Your ERP Upgrade
Margaret Hunnicutt

It’s very easy for business managers to put off an enterprise application
upgrade. The tendency is to only look at the immediate and obvious impact on
cash flow. There are other factors so often overlooked that also impact cash
flow. While they may seem less tangible, these seven factors directly effect the
medium term and more importantly the long term, profitability of your
organisation.

First, let’s explode the two most common myths to delay
taking up an ERP software upgrade.

Excuse #1: �Upgrades are by the vendor
and for the vendor.�

It’s true, and it’s not true.

Having worked
as a developer in a software house and in the customer support team, I can say
from first-hand experience that customers demand enhancements. This means
existing customers and prospective customers ultimately drive
upgrades.

The true part is yes, vendors want new customers and so they
will adapt the software to be more attractive to new customers.

The false
part is that many software houses earn more money per year from their existing
customer base than from new customers. To stay in business, the vendors must
listen to and respond to their existing customer base. Over the last 10-15
years, we’ve all seen the impact on even the large software manufacturers that
didn’t get this right.

To suggest the only benefactors of upgrades are
the software vendors is not correct. To suggest that your business will
necessarily benefit from every upgrade is also not correct.

The rate at
which upgrades are offered is not going to suit all customers all of the time.
So the rate at which your business adopts the upgrades is certainly in your
complete control. You have the challenge of finding the right balance between
the benefits of the upgrade and when you adopt them, relative to your
environment and industry.

Excuse #2: �If it ain’t broke � don’t fix
it.�

If we’re going to throw adages around, this one could equally be
discredited with �if you’re standing still, you’re falling
behind�.

Exposing the 7 costs

1) Skilled resources � it’s
perfectly natural and normal for people to want to be skilled up on the �new
thing�. I don’t mean the leading-edge of technology, I mean current.

a.
From an employee’s perspective, any future employer is going to look favourably
on an applicant with updated skills, and far less favourably on a
skilled-but-outdated applicant.

b. From a contractor’s perspective, you
can usually find more work in the �new� area and its usually more
interesting.

c. From a business perspective � quality skilled resources
of older skills become harder and harder to find and more costly over time.
Current staff become stagnant and stale, and prospective employees you would
want to attract will be more attracted to your competitors.

2)
Competitiveness � the fast paced world we all live in demands your business
adapts as well. Software vendors rely on a combination of customer requests and
best-business practice of the day to form their enhancements strategy and
direction. If your business is still using the best practice of 10 years ago,
your business is struggling. Software upgrades give the enhanced functionality
and efficient business processes to help keep your business
competitive.

3) Return on investment � if you prefer the DIY approach to
updating your software, you will be weakening the investment the business made
in selecting the enterprise application.

It costs more to develop the
software in-house than to adopt the enhancements produced by the software
vendor. And even if you don’t see staff costs as direct costs to the business,
or you get developers at rock-bottom prices, you will be missing out on the
strategic integration of those enhancements to the product core. The end result
is you will be spending more and benefiting less from IT than your
competitors.

4) Compliance � software manufacturers stay on well informed
on legislative changes that may impact the design or flow of information in
their systems. Why re-invent the wheel?

5) Innovation � when businesses
develop in-house systems, they become reliant on internal knowledge. Another way
of looking at it is they become insular or stale. If your business systems are
in large part �stock standard� then you can easily infuse new ideas from outside
consultants, experts from other industries, and even from new staff, to help
foster growth and excellence across the enterprise.

6) Productivity –
Software upgrades provide the perfect catalyst for a business to adopt and
effect process change and gain productivity.

7) Staying on the same page
– This is one of the most common �opportunity cost� mistakes made, even by
companies that keep their software versions current.

Upgrades serve as a
reminder that business technology needs to stay in touch with the business it
serves, and visa versa. This is a perfect opportunity to review the business
strategy and the IT strategy, and re-align both to the same long-term
goals

Proper analysis of the risks and costs should be done as part of
the normal planning process of an upgrade. Pro-active engagement by the business
and planning by the business overall (not just seeing it as a technical
exercise) will help your organisation achieve and realise value out of your
software investment.

If you are looking to draw out the best functionality and efficiency from your
existing investment in IT, call us now. Our specialty is JD Edwards applications
post-installation professional services. � Qsolve Pty Ltd, all rights reserved
www.Qsolve.com.au

ERP Products

There are quite a few ERP Products around. In fact, ERP goes beyond just simply selling software. There are ERP products such as RF Devices, Bar Code Printers, POS terminals, various interface devices, etc. There is a multitude of people selling all sorts of associated ERP Products.

You may or may not need these items, but they are definitely worth considering into your ERP Budget.

You might want to take a look at the ERP vendors page on this site to find out about ERP software. For other products, we have listed below are some of the ERP products that you might need to consider along with the software.

ERP Products

Workstations
Servers
Storage Devices
Networked storage
Diskless workstations (ie. winterms)
Printers
Label Printers
Bar Code label printers
RF Readers
RFID tags (Passive and Active)
RFID readers
POS terminals
POS Tape Printers
CAM (computer aided manufacturing) products
Tool Crib Storage devices
Network devices (routers, switches, VPN devices, etc.)
Biometric Devices for Time and Attendance

Are there any other ERP related products that we missed. Let us know!

The Importance of Assigning Tasks and Resources in Project Management

One of the key success factors in an ERP, CRM, or other implementation is that there is good project management. This article touches on some of the features of managing the project: managing Tasks and managing Resources.

The Importance of Assigning Tasks and Resources in Project Management
John Reynolds

There are two major ways to estimate the lengths (i.e., durations) of tasks. The simplest way is to estimate the elapsed time of a task.

If someone says it will take him a week to do a particular task, he is probably offering an elapsed-time estimate. They generally mean that it will take him one work week to get a task done, not that it will take them 40 hours. When estimating elapsed time, people generally account for not working on the project tasks full-time, and for working on other, higher-priority tasks first.

In most projects, however, lengths should be estimated based on the amount of work, not the amount of time. That way, adding resources will shorten a task, and using resources only part-time will lengthen a task. Tasks that fluctuate like this depending on the resources assigned are called resource-constrained tasks.

There are several ways to estimate the resource time for a task. One is to let the project manager calculate the estimates based on an employees performance on similar tasks. Another is to let the employees performing the tasks calculate their estimates, generally based on how they performed on similar tasks. A third way to estimate is to use standard metrics for generic tasks.

Although many project managers like to follow the standards established by these generic metrics, their plans are generally more accurate when they and their employees do their own estimating. It usually takes three to five projects to become proficient, but the eventual accuracy is worth the delay. Sometimes tasks will not be resource-constrained and can be estimated based on the elapsed times. Examples would be training classes or project meetings. Even though two or more people may attend a class or meeting, the length of the task does not shorten. These types of tasks are called time-constrained.

Good project management requires excellent communication forms and documentation. Get professional project manager templates to help you with your next ERP, CRM, or other technology project.

If estimates are being provided from standard metrics or project managers, them resources (i.e., employees) should be assigned after task lengths are determined. If estimates are coming from the employees performing the tasks, obviously these steps will be reversed. Regardless of the order of these two steps, one or more employees should be picked for each task that is resource-constrained.

Employees assigned to multiple tasks are often scheduled for too much work while there are simultaneous tasks to complete and not enough work when there are no task assignments. To maintain a consistent workload, resources need to be ‘leveled.’ There are only two main ways to level resource allocations: by adjusting the task schedule or adjusting the resource assignments. Project management packages generally adjust the schedule to increase the amount of time it takes to finish the project.

Remember these basic principles for assigning task lengths and resources to improve your management proficiency.

John Reynolds has been a practicing project manager for nearly 20 years and is the editor of an informational website rating project management software products. For more information on project management and project management software, visit Project Management Software Web.

Nozbe