WEEK 5

Respond to the following: Many experienced ERP implementation will say there are two rules you should follow when implementing these systems:

1.Do no customise your ERP.

2. See Rule 1.

Why do you think this is? what are the risks of customisation? what does a need to customise say about the willingness or an organisation to effect BPR?

ANSWER:

Numerous of the discussions and decisions before implementing ERP needs to start to make a decision to revise the ERP system is the key. Both the above rules by experienced ERP implementers point of view is reflected, nobody can escape sarcasm behind these laws, it is difficult to read the rules and ignore them. But they provide very good newsflash. I consider that this view prevailed ERP paybacks anticipated budgets could easily exceed main reason for the review.

Customized ERP results suggest that despite devastating, it is still used in some form with mixed results. It requires very little customization to say ‘good’ or ‘bad’, it is and why it is important to understand that. Most of the research rational reason for ERP package customization is focused upon. Moreover, their approach to enforcement attention upon their reasons is. If, for example, customisations can perform the functionality is missing, to include the cost of the system, system operation and package look more attractive to different users to maximize the performance is desired. However, what this research is packaged software cannot expect others to customize the starting point agenda. Thus, fuelling product development process ERP packages vendors as necessary, maybe. It may be, as some customisations failed product development can be seen? I moved back to the organization, it is also possible to view various relevant social groups. Implementation of a team, using custom control mechanisms as a pluralistic or can facilitate user acceptance. Another administration the ‘best practices’ working around or customisations using the system for recognition and increase performance by adding the value of the current process to maintain staff are looking do. Further research on these topics, amplified are especially relevant social groups influence are diverse. In summary, customisations to consumers as a form of rehabilitation organization because they see it or packaged software is required due to the nature of the industry. Due to the nature of industry specific products and everything – Customisation where it is not even may be demonstrated. In addition, custom user environment where organizational capabilities around product or products over time may be misunderstanding the nature of expectations shift may be due. Finally, a custom as a form of resistance or protection can be.

Why this research can be customized ERP packages that I have attempted to provide insight. The other types of packaged software customization are useful for understanding the facility. In view of this, more evidence, judgment or reasoning behind the lack of empirically study conducted here as eluded to customize the software can be. Custom projects typically are considered as the home activities. However, in his home in information systems with functions and commercialization course, to develop customized using external contractors, future research is also applicable to a market-based approach to customized development of Inspection is considered.

Obviously, there are other reasons for customization, so here reported reasons should not be taken as definitive list. Of course, other reasons for customization to locate a further avenue for future research might be. For example, in this study sociotechnical integration of basic research currently being shown in efforts to help define the role of customisations. The purpose here was merely represents the maximum customization to fit the needs for function.

REFERENCE:

Light, B 2005, ‘Going beyond ‘misfit’ as a reason for ERP package customisation’, Computers in industry, Vol. 56, no. 6, pp. 606-609.

WEEK FOUR (4)

What are the implementation for organisations adopting an ERP? Do you think the text captured the complexity of this? why / why not?

ANSWER:

The data flow chart to implement several activities that an ERP system is essential to the performance shown.

Step 1: Manager Feasibility study of the current situation and availability of hardware, software, databases, and computer skills in house analysis by reviewing the organization’s needs, and ERP integration is essential to the It is necessary to implement the decision. It aims to improve the process to establish goals, and the break points and benefits of this expensive investment that would be received should be determined based.

Step 2: After education and other notable clients include recruitment process involved in the process.

Step 3: Manager all functional areas of a project team or steering committee to lead the project consists of building experts.

Step 4: Select ERP implementation approach is supported. In most cases, the consultant team best modules are designed to suit the company’s operations (manufacturing, financial, human resources, logistics, forecasting, etc.), system configuration, and supply chain such as business recommended applications for business management, customer relationship management, e-procurement, e-marketplace.

Step 5: Adequate employee and manager training all businesses, managers, end users, customers, and stakeholders, including vendors must be provided, before the system is implemented. This type of training is usually customized and any internal or external training can be provided by.

Step 6: System installation process, the setup software, hardware acquisition, and software testing will solve the problem.

Step 7, 8 and 9: ERP system database used in the form of data and information and should be changed servers and networks need to be upgraded. Amendment needs to be met during this period.

ERP solutions to companies in the production of goods and services have been revolutionised. Many organisations use ERP systems tightly by the overall organisation bring different departments. ERP systems are large and complex, and a careful planning and implementation process is needed. They are not just software, they affect how a successful ERP implementation, writing a business itself. The holding up strong commitment from top management is implemented as existing business practical as well as major changes include heavy investment outlays.

Kumar, P 2010, ‘Successful implementation of ERP on large organisation’, International journal of engineering science and Technology, Vol. 2, no. 7, pp. 3218-3214.

WEEK THREE (3)

What are the implication of organisation adopting ERP? Do you think the text captured the complexity of this? Why / Why not?

Answer:

A standard methodology to facilitate the selection and implementation of an ERP system has been developed. The methodology consists of seven phases:

Phase 1 – Vision and Commitment

Implementation of a new business planning control system represents a significant investment. It is therefore essential that the organization creates a common understanding of what they seek to create and at what cost and for what benefit. During this phase, the following are established:

Phase 2 – Business Process Engineering

Using a vision, the company personnel to draw key business processes as they are today. They then simplify and streamline these where possible.

Phase 3 – Statement of Requirements and invitation to tender

Statement of Requirement (SOR) and ERP system based on the new process models is developed. This defines how the company wants to manage their business using the new systems. The use of a well-defined methodology is an important foundation on which the implementation of an ERP system. Many factors have contributed to the success are the conditions under which the method is executed.

Phase 4 – Selection of systems and contract negotiation

Three to five suppliers are shortlisted based on the responses received. Pre-qualified suppliers are invited for presentations and further discussion. The shortlist is reduced to two or three suppliers whose reference sites are visited by the project team.

A decision is made with a preferred supplier and contract details are negotiated. At this stage, it is strongly recommended that the response of the ITT providers will be formally incorporated into the contract. This provides protection in case of misunderstanding or ignoring supplier requirements.

Phase 5 – Implementation Planning

A series of workshops are to develop a detailed implementation plan. The project manager and the project team and support staff providers attend these workshops.

Phase 6 – Implementation

This is done according to the plan of implementation agreed at the previous phase. With minimal interference from the outside, the meetings of the Steering Committee regular reviews throughout and at critical moments during the implementation.

Phase 7 – review of the implementation of Posts and Fine Tuning

At the end of the implementation and once the system is installed, a test is performed on the new systems and processes to those originally intended. An action statement is produced to refine the system and processes to maximize the business benefits achieved by the system. A separate report describing the business benefits achieved, is also produced.

The use of a well-defined methodology is an important foundation on which the implementation of an ERP system. Many factors have contributed to the success are the conditions under which the method is executed, such as attention to detail, the stability of team member-ship, ERP / IT skills, etc. So there were changes in methodology at a micro level to accommodate retail business in particular, the variation of the success of ERP implementation can be attributed to individuals in the organization and culture.

Their analyses key lessons on project management, philosophy implementation, the project team, awareness, stability of business and attention to detail. ERP implementations in the future this summary may be used as a basis for verification checklist to assess the health of the project and highlight areas of interest such structure.

Ball, PD, MIOM & Bittici, US 2001, ‘Implementing ERP systems – organisational implications’, FIOM University of strathclyde, pp 17 – 23

Week TWO (2)

Possible suggested causes of Shadow systems in an organistaion, what threat do these systems pose to integration? who or what else might be threatened by the existence of these systems?

Answer:

Ongoing burden for alteration generates an ongoing burden to analysis data in different means also acquire material rapidly into the fingers of persons who want that. Merely via innovative plus elastic recording are trades able to show fresh leanings also classify different chances quickly enough to get the complete benefit of them.

The sort of data examination which supreme repeatedly requires the growth or buying of Shadow Systems typically originates from the requirements of the end user. As the integrated information systems section typically intelligences to the administration’s CFO or COO, the structures which they grow are intended for their requirements. The requirements of departmental bosses are habitually fairly dissimilar, demanding additional comprehensive study which combines variables not enclosed in the answer planned by the central information systems division. Pretty correctly, while a recording system is placed together by IT experts, they have to study whole features of exactly how the structure of the system will be used.

The significantly improved control of individual computer hardware and software examination apparatuses has intended that single users nowadays have all of the computing power they must right before them. Big databanks comprise entirely of an organization’s client, contractor, or accounting statistics.

Shadow Data Systems frequently struggle from deprived plan. Naturally, Shadow Data Systems remain simply utilized by only single person or by two people. Until they are established by skilled computer programmers, it might be challenging to balance them equal to backing few or heaps of end users.

Shadow Data Systems grasp large portions of business data plus can contain private facts regarding clients, contractors or employees. The admission switch procedures for these systems are frequently far more negligent than for a unified business database plus may be they do not even occur in the least. Materially finding complex data on any desktop or laptop computers can leave an association way too unprotected when the computer is whipped.

Shadow systems present on a solo processor are a lot not frequently backed up. This is the finest to have these systems on your desktop or laptop computer that is habitually backed up or on a server.

shadow systems are not morally destructive systems that should just be eradicated. Instead administrations should pursue to examine plus recognise the related issues after the growth of shadow systems. It is concluded this understanding that the association may be able to recover its procedure by getting the source causes behind the expansion of shadow systems inside their organization.

WordPress 2003, The rise and fall of a shadow system: Lessons for enterprise system implementation, Viewed 10th December 2012, http://davidtjones.wordpress.com/publications/the-rise-and-fall-of-a-shadow-system-lessons-for-enterprise-system-implementation/

Wikipedia, The free encyclopaedia 2010, Shadow System, Viewed on 10th December 2012, http://en.wikipedia.org/wiki/Shadow_system

 

Hello world!

Welcome to WordPress.com! This is your very first post. Click the Edit link to modify or delete it, or start a new post. If you like, use this post to tell readers why you started this blog and what you plan to do with it.

Happy blogging!