College Finder
English flagItalian flagKorean flagChinese (Simplified) flagGerman flagFrench flagSpanish flagJapanese flagArabic flagRussian flagGreek flagDutch flagBulgarian flagCzech flagCroat flagDanish flagFinnish flagHindi flagPolish flagRumanian flagSwedish flagNorwegian flag
By N2H




Business Process reengineering BPR Business Process reengineering BPR

August 5, 2008 August 5, 2008

If you're new here, you may want to subscribe to my RSS feed . Hvis du er ny her, kan du ønsker at abonnere på min RSS-feed. Thanks for visiting and have a nice day! Tak for besøg og få en hyggelig dag!

BPR is a form of organizational improvement. It aims to improve a business through restructuring of processes. BPR er en form for organisatorisk forbedring. Det har til formål at forbedre en virksomhed gennem omstrukturering af processer. BPR is given force by the thinking that old ways of organizing work are no longer appropriate for a competitive business environment. BPR er givet kraft af den tankegang, at gamle måder at organisere arbejdet, ikke længere er passende for et konkurrencedygtigt erhvervsklima. The ultimate aim of re-engineering processes to achieve better quality, service and innovativeness. Det endelige mål med re-engineering processer for at opnå bedre kvalitet, service og innovation. The radical restructuring entailed in BPR is risky and uncertain. Den gennemgribende omstrukturering medførte i BPR er risikabelt og usikkert.
Theoretical Foundations of BPR: Teoretiske grundlag for BPR:
For hundreds of years, commercial activity has been based on the Adam Smith principle of Division of Labor. For hundrede år, kommercielle aktivitet har været baseret på Adam Smith princippet om, Division of Labor. Division of labor encourages specialization and thereby leads to improved productivity. Division arbejdskraft tilskynder specialisering og dermed fører til øget produktivitet.
The classical enterprise also exhibits the concepts of: Den klassiske virksomhed også udstiller begreberne:

  • Hierarchical control:- the classical layers of management Hierarchical kontrol: - klassisk lag af ledelsen
  • Mass production of largely uniform goods/services Masse produktion af stort set ensartede varer / tjenesteydelser

An organization based on these principles is successful in a stable market environment, characterized by growing demand for uniform goods/services. En organisation baseret på disse principper er en succes i et stabilt marked, miljø, karakteriseret ved voksende efterspørgsel efter ensartede varer / ydelser. In a changed market environment characterized by sever competition, globalization, more demanding customers, smaller profit margins etc, the classical organizational models are less and less appropriate. BPR provides one alternative to the old methods of organizing business processes. I et ændret marked karakteriseret ved skille konkurrence, globalisering, mere krævende kunder, mindre avancer etc, den klassiske organisatoriske modeller er mindre og mindre hensigtsmæssigt. BPR giver en alternativ til de gamle metoder til organisering af forretningsprocesser. The goals of BPR can be started in expanded form as either cost objectives or service objectives. Målet med BPR kan startes i udvidet form, enten som koster mål eller service-mål.

Cost Objectives: Omkostninger Mål:

  • Reducing stocks: New materials or Intermediate goods Reduktion af lagre: Nye materialer eller mellemprodukter
  • Economies of scale in procurement Stordriftsfordele ved indkøb
  • Reduced staff costs (administrative costs) Reducerede personaleomkostninger (administrative udgifter)
  • Competitive pricing of goods/services Konkurrencedygtig prissætning af varer / tjenesteydelser

Service Objectives: Service Mål:

  • More reliable delivery system Mere pålidelige leveringssystem
  • Stock availability Stock tilgængelighed
  • Good after sales service God kundeservice
  • Quick Response/adaptation to market changes Quick Response / tilpasning til markedets ændringer
  • Reduced product development lifecycle Reduceret produktudvikling lifecycle

Qualities of Re-engineered Processes: Kvaliteter af omlagte Processer:

  • Several jobs are combined into one. Flere arbejdspladser er kombineret i én. This implies a reversal of the Adam Smith principle of division of labor and function. Dette indebærer en vending af Adam Smith princippet om deling af arbejdskraft og funktion. Workers make decisions, actual work and decision making are integrated. Arbejdstagere træffe beslutninger, faktiske arbejde og beslutningstagning, er integreret.
  • Processes are reorganized so that tasks are done in the most sensible/logical order. Processer er omlagt, således at opgaverne er udført i den mest fornuftige / logisk rækkefølge.
  • Checks and controls are reduced. The checks and controls are reduced to the minimum acceptable level. The checks and controls are also deferred. Kontrol og kontrol er reduceret. Kontrollen og kontrollen er reduceret til et minimum acceptabelt niveau. Kontrollen og kontrollen er også udskudt.
  • Reconciliation is minimized. Forsoning er minimeret.
  • A case manager is appointed to oversee the re-engineering process. En sag manager er udpeget til at overvåge reengineering-proces.
  • Hybrid processes that combine centralization and decentralization by use of communication technology are often adopted. Hybrid processer, der kombinerer centralisering og decentralisering ved brug af kommunikations-teknologi ofte er vedtaget.
  • Processes have multiple versions (polymorphic) – the process is re-designed to include capabilities to deal with custom orders. Processer har flere versioner (polymorf) - processen er re-designet til at omfatte kapaciteter til at beskæftige sig med brugerdefinerede ordrer.

Contribution/Role of IT in BPR: Bidrag / Rolle af IT i BPR:

  • IT is all essential enable of BPR; it enables processes to be re-engineered. Det er alt afgørende mulighed for BPR; det sætter processer, der skal re-manipuleret.
  • It supports the re-engineered process Det støtter den omlagte proces
  • Leading edge technology products can be particularly useful in process innovation. They can even lead the innovation process. Førende teknologi-produkter kan være særlig nyttig i processen innovation. De kan endda føre innovationsprocessen.
  • IT also facilitates process integration. Det skal også lette processen integration.
  • It has been argued that the most effective contribution of IT in business redesign is to enable an enterprise to do things that it was not doing before – extending the capabilities of the enterprise. Det er blevet fremført, at den mest effektive bidrag af IT i erhvervslivet redesign er at gøre det muligt for en virksomhed at gøre ting, var det ikke gør før - at udvide kapaciteten inden for virksomheden.

Candidates for BPR: Kandidater til BPR:
In theory, any business process can be subject to BPR; but in practice, certain processes can benefit more from BPR than others. I teorien kan enhver forretningsproces kan gøres til genstand for BPR, men i praksis er visse processer kan drage større fordel BPR end andre. Such processes have the following qualities Sådanne processer har følgende kvaliteter

Dysfunction: The process is visibly out of order, it is problematic. Dysfunktion: Processen er synligt ud af, at det er problematisk. Dysfunction in a process occurs when the process is slow (frustratingly slow), occasional complaints, generates errors etc. Dysfunktion i en proces opstår, når processen er langsom (frustrerende langsomme), lejlighedsvise klager, genererer fejl osv.

Importance: Important processes that have a prominent place in the value chain. They contribute directly to the delivery of goods and services to the end consumer. Vigtighed: Vigtige processer, der har en fremtrædende plads i værdikæden. De bidrager direkte til levering af varer og tjenesteydelser til den endelige forbruger.
Feasible: From the managers stand point the BPR project is technically, economically and socially feasible/viable. Feasible: Fra ledere står pege BPR projektet er teknisk, økonomisk og socialt gennemførlige / levedygtig. Processes that require high capital input, or enjoy limited management support are less feasible for BPR. Processer, der kræver stor kapital input, eller nyde en begrænset ledelsesmæssig støtte er mindre muligt for BPR.

What causes BPR projects to fail? Hvad er årsagen til BPR projekter til at mislykkes? (Pitfalls in BPR): (Faldgruber i BPR):

  • Inadequate funding Utilstrækkelig finansiering
  • Insufficient management commitment/support Utilstrækkelig forvaltning engagement / support
  • Poor project leaders Dårlige projektledere
  • Inadequate feasibility evaluation Utilstrækkelig feasibility-evaluering
  • Resistance to process change Modstand mod proces forandring
  • Failure to focus on most process re-design and dwelling on improving the existing process. Undladelse af at fokusere på de fleste proces re-design og bolig på at forbedre den eksisterende proces.
  • Quitting too early or declaring victory too soon. Afslut for tidligt eller at erklære sejr for tidligt.

Re-engineering computer system: Re-engineering edb-system:
At a minimum a computer system comprises of an ordered collection of hardware, software, and data resources. På et minimum et edb-system består af en bestilt indsamling af hardware, software og data ressourcer. Computer systems are the basis for automated information system. Edb-systemer er grundlaget for automatiske informationssystem.

  • Re-engineering computer systems means examining, rethinking and re-implementing such systems in a new form. Re-engineering edb-systemer betyder, at undersøge, nytænkning og re-gennemførelse af sådanne systemer i en ny form.
  • The process is usually carried out on legacy options, re-implementing them in a more modern form. Processen foregår normalt på arven valgmuligheder, re-gennemføre dem på en mere moderne form.
  • Re-engineering computer systems can be seen as a management response to the challenge of keeping old systems alive within a changing environment. Re-engineering edb-systemer kan ses som et management løsning på udfordringen med at holde de gamle systemer i live inden for et skiftende miljø.

Merits Realiteten

  • The useful life of a system is increased Levetiden for et system er steget
  • The business value of such a system also increases De forretningsmæssige værdi af et sådant system øger også
  • Future maintenance costs are reduced Fremtidige vedligeholdelsesomkostningerne reduceres
  • The morale of maintenance staff may improve; because they know they are working in a modern system ie the systems become more maintainable. Den moral vedligeholdelsespersonale kan forbedre, fordi de ved, de arbejder i et moderne system, dvs systemerne bliver mere vedligeholdelse.

Steps for BPR Trin for BPR

  • Identify process for innovations Identificer proces for nyskabelser
  • Manage business Manage business
  • Manage people and work Administrer folk og arbejde
  • Identify change levels ( technology etc) Identificer ændre niveauer (teknologi etc.)
  • Develop process vision – what you want to process must fit with the strategic direction of the organization (IS) Udarbejde proces vision - hvad du ønsker at processen skal passe ind i den strategiske ledelse af organisationen (IS)
  • Understand existing processes – study current process and understand necessary changes Forstå eksisterende processer - undersøgelse igangværende proces og forstå de nødvendige ændringer
  • Design and prototype new process/create design of new process. Design og prototype ny proces / skabe design af ny proces.

Approaches to re-engineering computer systems: Løsningsmodeller til omlægning af edb-systemer:
When a system is re-engineered any of the following changes may occur: Når et system er omlagte nogen af følgende ændringer kan forekomme:

  • It may be placed in a distributed platform. Det kan være anbragt i et distribueret platform.
  • It will usually be re-documented Det vil normalt være re-dokumenteret
  • The data may be migrated to a new database platform De data kan flyttes til en ny database platform
  • The code may be restricted Koden kan begrænses
  • The code may be written in a different language Koden kan være skrevet på et andet sprog

Automatic Source Code Conversion: Automatisk Kildekode Konvertering:
This entails the use of software tools to convert source code in a given language. Dette indebærer anvendelse af software-værktøjer til at konvertere kildekoden i et givet sprog.

  • to code in a newer version eg Cobol 74’ to Cobol 90’ at kode i en nyere version f.eks COBOL 74 'til COBOL 90'
  • to code in a different language eg Cobol 74’ to Oracle at kode på et andet sprog f.eks COBOL 74 "til Oracle

The software tools cannot achieve 100% conversion and hence has to be supplemented with manual conversion. Den software-værktøjer kan ikke opnå 100% omstilling og dermed er nødt til at blive suppleret med manuel konvertering.

Automated Program Restructuring Automatiseret Program Omstrukturering

When code is maintained over an extended period, its structure and hence its efficiency, deteriorate. Når koden er opretholdt over en længere periode, dens struktur og dermed dets effektivitet, forværres. Indeed, the more a software product has been maintained, the more it costs to maintain it in future. Faktisk er det mere et software-produkt er blevet opretholdt, jo mere koster det at fastholde den i fremtiden. When the program is re-structured: Når programmet er re-struktureret:

  • irreconcilable code is detected and removed uforsonlige kode er fundet og fjernet
  • complex control structures are simplified komplekse kontrol strukturer er forenklet
  • program modularity is enhanced program modularitet er forbedret

Use of software tools may not be fully effective. Manual rewriting of code may still be applied. Brug af software-værktøjer kan ikke være fuldt ud effektive. Håndbog omskrivning af koden kan stadig blive anvendt.

Automated program and Data Restructuring: Automatiseret program og Data omstrukturering:
When the existing data structures are re-structured then even the programs that process the data have to be reviewed. Når de eksisterende data strukturer er re-struktureret derefter selv de programmer, der behandler de data, der skal revideres. When data is restructured: Når data er omstruktureret:

  • The overall model may be re-organized into one database. Den samlede model kan være re-organiseret i en database.
  • Data in a relational model may be modified to suit the needs of a different relational DBMS. Data i en relationel model kan ændres, så de passer til behovene i en anden relationel DBMS.

Re-engineering or Re-developing? Re-engineering eller Re-udvikler?
Systems targeted for re-engineering have 2 qualities Systems målrettet for re-engineering har 2 kvaliteter

  • They are heavily/regularly used De er stærkt / jævnligt benyttes
  • They are currently being maintained a lot De bliver i øjeblikket opretholdes en masse

Re-engineering usually has two main merits over re-developing. Re-engineering har normalt to største fortjenester over igen at udvikle. These are: Disse er:

  • Lower costs: re-engineering costs about ¼ of redeveloping Lavere omkostninger: Re-engineering koster ca ¼ af Sanering
  • Reduced risk: lower likelihood of making mistakes. Reduceret risiko: lavere risiko for at begå fejl.

When deciding whether to re-engineer or to redevelop you may consider such issues as: Når der træffes beslutning om at omlægge eller ombygningsprojekt kan du overveje sådanne spørgsmål som:

  • budget provisions or costs constraints budget bestemmelser eller omkostninger begrænsninger
  • current state of the old system; the old system may be so old and messy that it may not be susceptible to re-engineering nuværende situation for det gamle system; det gamle system kan være så gamle og rodet, at det måske ikke er modtagelige for re-engineering
  • Time limitations: re-engineering is likely to be quicker than to redevelop Tidsbegrænsninger: Re-engineering må formodes at være hurtigere end at ombygningsprojekt
  • Scope ie system scope; if the scope of the existing system is to be excluded substantially then it may be more practical to redesign and re-implement the system instead of re-engineering it. Anvendelsesområde dvs system anvendelsesområde, hvis rækkevidden af det eksisterende system er at blive udelukket væsentligt derefter kan det være mere praktisk at redesign og re-implementere systemet i stedet for re-engineering det.
  • Perceived risk level; Risk arises from the combined effect of many factors. Risikoopfattelsen plan; Risk udspringer af den kombinerede effekt af mange faktorer. If the perceived project risk is high then it might be safer to re-engineer the system than to redevelop it. Hvis de opfattede projektet risikoen er høj, så det kan være sikrere at omlægge systemet end at ombygningsprojekt det.

Link between reengineering of computer systems and BPR: Link mellem reengineering af edb-systemer og BPR:

Computer systems are usually embodied within business processes/systems such as accounts receivable, production planning, marketing and distribution, human resources etc. When such process/systems are re-engineered, then the supporting technology infrastructure also needs to be reviewed. Edb-systemer er normalt indeholdt i forretningsprocesser / systemer såsom debitorer, produktionsplanlægning, markedsføring og distribution, menneskelige ressourcer osv. Når sådanne processer / systemer er ombygget, så den fornødne teknologi, infrastruktur skal også revideres.

The overall aim of reengineering a computer system should be to re-align it with the existing business goals. Det overordnede formål med reengineering et edb-system skal være at genskabe den tilpasses de eksisterende forretningsmæssige mål. The goals of a BPR project require an altered IT infrastructure then the existing infrastructure should be reengineered or re-developed. Målene for en BPR projekt kræver en ændret IT-infrastruktur, så den eksisterende infrastruktur bør reengineered eller re-udviklet.


Page copy protected against web site content infringement by Copyscape

Comments Kommentarer

Got something to say? Har du noget at sige?

You must be logged in to post a comment. Du skal være logget på for at skrive en kommentar.

FireStats ikon Powered by FireStats Powered by FireStats