DOCSLIB.ORG

IDEF Methods for BPR to Support CALS

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IDEF Methods for BPR to Support CALS IDEF Methods for BPR to Support CALS Comprehensive Solutions for a Complex World IDEF and CALS • CALS technologies enable paperless environments or the electronic flow of information. •The implementation of CALS technologies require a re-engineering of enterprises. IDEF and BPR • Business Process Reengineering (BPR) assists in re-engineering the enterprises and the successful implementation of CALS. • IDEF Methods support BPR activities (e.g., knowledge acquisition, As-Is analysis, To -Be design, project planning, and implementation). What are Methods? Methods: A structured approach to capturing knowledge that maximizes accuracy but is also flexible enough to capture the real-world characteristics of that knowledge. What are IDEF Methods? Integration DEFinition methods Knowledge Acquisition, Analysis, and Design tools Languages that include both graphics (diagrams) and text Formal procedures for constructing models or ditifdescriptions of a parti tilcular aspect tf of an organization Why IDEF? IDEF: The IDEF Family of Methods was co- developed by industry and government. Their pppurpose is to provide a com prehensive yet flexible framework for describing, analyzing, and evaluatinggp business practices. The y are not proprietary and are supported by international standards. Characteristics of an IDEF Method Designed to address specific aspects of a problem, or provide different perspectives of the same problem Provide an explicit mechanism for integrating the results of the application of one IDEF with another Embody the knowledge of good practice for the targeted fact collection, analysis, design, or fabrication activity Desidigned to raihise the per formance ofif a novice pract iiitioner to that of a more experienced practitioner Enforce formal techniques to ensure understandable communication Continuing Evolution of IDEF IDEFØ Function Modeling IDEF1 Information Modeling IDEF1X Data Modeling IDEF3 Process Modeling IDEF4 Object-oriented Design/Analysis IDEF5 Ontology Description IDEF9 Bus iness Cons tra in t Discovery Original IDEF Methods Origgpinal plan was for the creation of several Integrated IDEFs from the ICAM Project The initial step was the development of the first 3 methods: Function/Activity Modeling (IDEFØ) In forma tion M od eli ng (IDEF1) Dynamic Modeling (IDEF2) Where to use IDEF CALS Implementations--transitioning from paper to electronic systems Business Process Reengineering / Improvement BiBusiness /Mfti/ Manufacturing S Stystem Documentation/ISO 9000 Compliance Software/Information System Development Manufacturing Systems Analysis and Design In The Beginning. IDEF0 - Activity Modeling IDEF1 - Information Modeling IDEF1X - Logical Data Modeling The Next Generation IDEF3 - Process Modeling IDEF4 - Object-Oriented Design and Analysis IDEF5 - Ontology Descrip tion IDEF9 - Business Constraint Description Support for Systems Development IDEFØ is used to document what the enterprise does. IDEF3 models how the enterprise does what it does. IDEF1/1X capture how information is used to support what the enterprise does and how it does it. With IDEF, systems development is based on real-world knowledge, not unrealistic goals. Support for BPR Efforts Capture Activities and Their Relationships; Identify Core Activities; Identify Activities for Reengineering Describe Business Processes; Redesign Processes for Improvement; Use Process Descriptions for Simulation Capture How Data and Information Are Used to Support Business Processes Next Generation of IDEF Methods Currently Envisioned Methods IDEF6 - Design Rationale Capture IDEF7 - Information System Audit Method IDEF8 - Human-System Interaction Modeling IDEF9 - Business-Constraint Discovery Method IDEF10 - Implementation Architecture Modeling IDEF11 - Information Artifact Modeling IDEF12 - Organizational Design Method IDEF13 - 3-Schema Architecture Design Method IDEF14 - Network / Distribution Design Method IDEFØ Captures What an Enterprise Does Why Develop An IDEFØ Activity Model? To identify, document , and communicate an enterprise’s core activities. To understand how activities relate to one another. To identify value-added and non-value-added activities. To identify activities that need to be improved . Benefits of Activity Modeling Documents current activities. Reduces the learning curve for new activity users. Cappytures and analyzes As-Is activities. Facilitates the design/redesign of activities for To-Be scenarios. An IDEFØ Activity Box Controls (constraints on an activity, e.g., procedures, budgets, etc.) Inputs Function or Outputs (what is required AiiActivity (what is produced by an before an activity can (Verb Phase) activity, e.g., reports, occur, e.g ., purchase products, etc.) order, supervisor’s signature, etc.) Mechanisms (what enables an activity, e .g ., equipment , personnel assignments, etc.) Context, Purpose, and Viewpoint: The context defines the boundaries of Personnel Regulations your model—iei.e., Department Policy what will be included Supervisor Instructions in the model. Manning Conditions Applicant Data Perform Personnel Action For example, Customer Request Personnel Actions Reports Employee/Position Employee/Position Data Data comes from outidthtside the mod dlel. Supplies & Equipment Personnel Office Staff Information System Context, Purpose, and Viewpoint: We define purpose as the reason to develop Personnel Regulations this particular activity Department Policy Supervisor Instructions model. Manning Conditions AliDApplicant Data Perform Personnel Action Purpose: To document Customer Request Personnel Actions Reports the activities Employee/Position Data associtdiated with managing Personnel Supplies & Equipment Actions and identify Personnel Office Staff non-value-added Information System activities that might be eliminated. Context, Purpose, and Viewpoint: Viewpoint can be Personnel Regulations thoug ht of as th e Department Policy Supervisor Instructions perspective of the Manning Conditions Applicant Data Perform person/group Personnel Action Customer Request Personnel Actions Reports developpging the Employee/Position model. Data Supplies & Equipment Personnel Office Staff Viewpoint: Information System Personnel Officer Decomposition: An Example Company guidelines Budget guidelines Maintain Correct ledger Purchase request Accounts Payment Payable Invoice A0 Order Accounting staff Decomposition: An Example Company guidelines Process guidelines Purchase Process Order request requestrequest A1 Invoice guidelines Process Invoice invoice PtPayment A2 Ledger guidelines Apply purchase Correct ledger to books A3 Accounting staff IDEFØ As a Standard Federal Information Processing Standards Publication (FIPS PUB) 183-Integrated Definition for Function Modelingg( (IDEFØ) Published December 1993 DoD 8020.1-M established that “IDEFØ is the DoD standard methodology used for activity modeling” Currently, ANSI Standard Being Developed IDEF3 Captures How an Enterprise Does What It Does Why Develop An IDEF3 Process Model? To describe the process view of a process. To describe the OSTN view of a process. To capture timing and decision logic of processes. To support descriptions at any desired level of detail through Decompositions. To employ the concepts of Scenarios to simplify the structure of complex process flow descriptions. To support the capture of multiple viewpoints. Benefits of Process Modeling Document current processes for standardization. Provide guidelines for new process members to redhliduce the learning curve. Capture and analyze As -Is processes. Design/redesign process for To-Be scenarios. Test the design of a new process before embarking on an expensive development project . Precedence Link Process 1 will need to be finished before you can do Process 2. Process 1 Process 2 1 2 Referents . simply point the reader to some other aspect o f the mo de l tha t nee ds to be considered. Object: Pur. Req. Identify Negotiate Supplier price with vendor 2 3 Receive Prepare and request for & & dispatch purchase purchase order 1 J1 J2 5 Receive request for purchase 4 Scenario / Ordering Contracted Object / parts Contracted Parts Establish Scenario Objectives: (Viewpoint, Purpose, and Context) Viewpoint Determines what can be seen and from what perspective. Purpose Establishes the goal of the communication intended by the description. Defines why the description is being developed, and specifies how it will be used. Context Establishes the subject of a description. Establishes the subject as a part of a larger whole. Creates a boundary within the environment. Decompositions: PhPurchase OdEOrder Examp le Customer Supplier Del. Svc. Customer Places Processes Transports Rec./Dis. Order Order Materials Materials 1.1 2.1 3.1 4.1 Top-level Scenario: As-Is Order Process Decompositions: PhPurchase OdEOrder Examp le Customer Supplier Del. Svc. Customer Places Processes Transports Rec./Dis. Order Order Materials Materials 1.1 2.1 3.1 4.1 Decomposition: Customer Places Order Operator Sys. Cross System Open Enters Item Ref. Part # Generates Channel/Send Description w/Order Pick Ticket File to Target Details File Printer 5.1 6.1 7.1 8.1 OSTN Referent OST N Scenario Object Referent State II Diagram Object UOB SSeVtate IV Object Referent State I Object State III Allows constructi on of an obj ect-centeredid view. Summarizes allowable transitions of an object in the domain. Document data life cycles. Cuts across the process flow diagrams. Characterizes dynamic behavior of objects. Paint
Load more

Recommended publications
  • Modelling, Analysis and Design of Computer Integrated Manueactur1ng Systems
    MODELLING, ANALYSIS AND DESIGN OF COMPUTER INTEGRATED MANUEACTUR1NG SYSTEMS Volume I of II ABDULRAHMAN MUSLLABAB ABDULLAH AL-AILMARJ October-1998 A thesis submitted for the DEGREE OP DOCTOR OF.PHILOSOPHY MECHANICAL ENGINEERING DEPARTMENT, THE UNIVERSITY OF SHEFFIELD 3n ti]S 5íamc of Allai]. ¿Hoot (gractouo. iHHoßt ¿Merciful. ACKNOWLEDGEMENTS I would like to express my appreciation and thanks to my supervisor Professor Keith Ridgway for devoting freely of his time to read, discuss, and guide this research, and for his assistance in selecting the research topic, obtaining special reference materials, and contacting industrial collaborations. His advice has been much appreciated and I am very grateful. I would like to thank Mr Bruce Lake at Brook Hansen Motors who has patiently answered my questions during the case study. Finally, I would like to thank my family for their constant understanding, support and patience. l To my parents, my wife and my son. ABSTRACT In the present climate of global competition, manufacturing organisations consider and seek strategies, means and tools to assist them to stay competitive. Computer Integrated Manufacturing (CIM) offers a number of potential opportunities for improving manufacturing systems. However, a number of researchers have reported the difficulties which arise during the analysis, design and implementation of CIM due to a lack of effective modelling methodologies and techniques and the complexity of the systems. The work reported in this thesis is related to the development of an integrated modelling method to support the analysis and design of advanced manufacturing systems. A survey of various modelling methods and techniques is carried out. The methods SSADM, IDEFO, IDEF1X, IDEF3, IDEF4, OOM, SADT, GRAI, PN, 10A MERISE, GIM and SIMULATION are reviewed.
    [Show full text]
  • H)EF3 Technical Report Version 1.0 Chard J. Mayer Christopher P
    L. H)EF3 Technical Report Version 1.0 _| i L, _chard J. Mayer Christopher P. Menzel : i_:_pa_la S.D. Mayer Know!edge Based Systems Laboratory L Depar tment- 0 fin-dustrial Engineering Texas A&M University College Station TX 77843 Reviewed by Michad-K, Painter, Capt, USAF Armstrong Laboratory Logistics Research Division Wright-Patterson =Air Force Base, Ohio 45433-6503 :_ _=_January 1991 i _: ?_ | - , i (NASA-CR-I90279) {RESEARCH ACCOMPLISHED AT N92-26587 THE KNOWLEDGE BASED SYSTEMS LAB: IDEF3, VERSION 1.0] (Texas A&M Univ.) 56 p Unclag G]/_I 0086873 L == ; IDEF3 Technical Report Version 1.0 Richard J. Mayer Christopher P. Menzel Paula S.D. Mayer Knowledge Based Systems Laboratory Department of Industrial Engineering Texas A&M University College Station TX 77843 Reviewed by Michael K. Painter, Capt, USAF Armstrong Laboratory Logistics Research Division Wright-Patterson Air Force Base, Ohio 45433-6503 January 1991 umd w _- :7. m w Preface This paper describes the research accomplished at the Knowledge Based Systems Laboratory of the Department of Industrial Engineering at Texas A&M University. Funding for the Laboratory's research in Integrated Information System Development Methods and Tools has been provided by the Air Force Armstrong Laboratory, Logistics Research Division, AFWAL/LRL, Wright-Patterson Air Force Base, Ohio 45433, under the technical direction of USAF Captain Michael K. Painter, under subcontract through the NASA RICIS Program at the University of Houston. The authors and the design team wish to acknowledge the technical insights and ideas provided by Captain Painter in the performance of this research as well as his assistance in the preparation of this report.
    [Show full text]
  • Product Realization Process Modeling
    NAT’L INST. OF STAND & .TECH R I.C III! Ill" I" 'I mill mill II ml II II AlllDM NISTIR 5745 Product Realization Process Modeling: A study of requirements, methods and and research issues Kevin W. Lyons U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 Michael R. Duffey Richard C. Anderson George Washington University QC 100 NIST .056 NO. 5745 1995 Product Realization Process Modeling: A study of requirements, methods and and research issues Kevin W. Lyons U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 Michael R. Duffey Richard C. Anderson George Washington University June 1995 c U.S. DEPARTMENT OF COMMERCE Ronald H. Brown, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director . r•^ - . 'it'/ ' ' ' ' - ' ' -•*'1 X' . r • ^.,' v./f/v ’• '^^,. • T,?. - ^ •' V.y' ’ ' :AIa ' / ><- l> r / PRP Modeling: Page 2 1. Introduction 7 2. Definition of a PRP Model 8 3. Overview of PRP Methods and Modeling Issues in Manufacturing Industries 9 3.1 PERT-based Models 9 3.2 IDEF-based Models 10 3.3 Traditional PRP Modeling Practices 12 3.4 Emerging PRP Model Applications in Industry 14 3.5 Industry Requirements for PRP Models 14 4. Modeling Issues for Advanced PRP Computer Tools 16 4. 1 Activity Network Representations 17 4.2 Representing Design Iteration and Activity "Overlapping" 18 4.3 Uncertainty Modeling of a PRP 20 4.3.1 Some Simulation Considerations 20 4.3.2 Activity Duration Uncertainty 21 4.3.3 Concurrent Activities and Stochastic Modeling 22 4.3.4 Alternative Representations of Uncertainty 23 4.4 Representing Economic Information 24 4.5 Data Collection and Validation Issues for PRP Models 27 4.6 Knowledge-Based Representations in PRP Models 28 5.
    [Show full text]
  • Multi-Level Modeling of Complex Socio-Technical Systems Report No
    Multi-Level Modeling of Complex Socio-Technical Systems Report No. CCSE-2013-01 Dr. William B. Rouse, Stevens Institute of Technology Dr. Douglas A. Bodner, Georgia Institute of Technology Report No. CCSE-2013-01 June 11, 2013 Copyright © 2013 Stevens Institute of Technology, Systems Engineering Research Center This material is baseD upon work supporteD, in whole or in part, by the U.S. Department of Defense through the Systems Engineering Research Center (SERC) unDer Contract H98230-08-D-0171. SERC is a feDerally funDeD University AffiliateD Research Center manageD by Stevens Institute of Technology The authors gratefully acknowledge the helpful comments anD suggestions of John Casti anD HarolD Sorenson Any opinions, finDings anD conclusions or recommenDations expresseD in this material are those of the author(s) anD Do not necessarily reflect the views of the UniteD States Department of Defense. NO WARRANTY THIS STEVENS INSTITUTE OF TECHNOLOGY AND SYSTEMS ENGINEERING RESEARCH CENTER MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. STEVENS INSTITUTE OF TECHNOLOGY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. STEVENS INSTITUTE OF TECHNOLOGY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. Center for Complex Systems & Enterprises Report No. CCSE-2013-01 June 11, 2013 2 ABSTRACT This report presents a conceptual framework for multi-level moDeling of complex socio- technical systems, proviDes linkages to the historical roots anD technical unDerpinnings of this framework, anD outlines a catalog of component moDels for populating multi-level moDels.
    [Show full text]
  • Improved Product, Process and Rationale Representation and Information Organisation to Support Design Learning
    INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN, ICED’07 28 - 31 AUGUST 2007, CITE DES SCIENCES ET DE L'INDUSTRIE, PARIS, FRANCE IMPROVED PRODUCT, PROCESS AND RATIONALE REPRESENTATION AND INFORMATION ORGANISATION TO SUPPORT DESIGN LEARNING M D Giess 1, Y M Goh 1, L Ding 1 and C A McMahon 1 1University of Bath, UK ABSTRACT Many companies are moving from a product provision business model to a product-service model, where the producing company retains ownership of the product and supports it through life. In such a scenario it becomes possible to obtain a greater richness of information relating to product performance. However, in order for this information to be usefully deployed in improving design and manufacturing practices it is necessary to reconsider the means by which the design record is represented and organised such that linkages between the design record and the emergent outcomes as seen in service are explicit. In this manner, design episodes which continually lead to suboptimal or undesirable performance in service may be identified and remedial action taken. Current representation practices focus upon a generally topological or geometric depiction of product, structured according to the Bill of Materials, which is supported by primarily textual depictions of the process followed and rationale employed. Although an engineer may be able to retrieve and assimilate information contained within these representations, it is difficult to provide a unified view of a specific episode as distinct elements within these representations
    [Show full text]
  • Information to Users
    Group data modeling support for business process reengineering. Item Type text; Dissertation-Reproduction (electronic) Authors Lee, James David. Publisher The University of Arizona. Rights Copyright © is held by the author. Digital access to this material is made possible by the University Libraries, University of Arizona. Further transmission, reproduction or presentation (such as public display or performance) of protected items is prohibited except with permission of the author. Download date 07/10/2021 07:23:08 Link to Item http://hdl.handle.net/10150/187368 INFORMATION TO USERS This manuscript,has been reproduced from the microfilm master. UMI films the text directly from the original or copy submitted. Thus, some thesis and dissertation copies are in typewriter face, while others may be from any type of computer printer. The quality of this reproduction is dependent upon the quality of the copy submitted. Broken or indistinct print, colored or poor quality illustrations and photographs, print bleedthrough, substandard margins, and improper alignment can adversely affect reproduction. In the unlikely event that the author did not send UMI a complete mannscript and there are missing pages, these will be noted Also, if unauthorized copyright material had to be removed, a note will indicate the deletion. Oversize materials (e.g., maps, drawings, charts) are reproduced by sectioning the original, beginning at the upper left-hand comer and continuing from left to right in equal sections with small overlaps. Each original is also photographed in one exposure and is included in reduced form at the back of the book. Photographs included in the original manusaipt have been reproduced xerograpbically in this copy.
    [Show full text]
  • Introduction to IDEF0/3 for Business Process Modelling. Contents Tables & Figures
    Introduction to IDEF0/3 for Business Process Modelling. Contents Introduction ............................................................................................................................................ 2 Introduction to IDEF0 and IDEF3: ....................................................................................................... 2 Parent and Child Maps ........................................................................................................................ 2 Tunnelling ........................................................................................................................................ 3 Construction of IDEF Maps ................................................................................................................. 3 Branches and Joins .......................................................................................................................... 3 Starting an IDEF0 Map ............................................................................................................................ 4 Root definition .................................................................................................................................... 4 The IDEF0 Numbering Convention ...................................................................................................... 5 Creating a model ..................................................................................................................................... 5 Decomposition ...............................................................................................................................
    [Show full text]
  • Appendices MISQ Archivist for Business Process Change: a Study of Methodologies, Techniques and Tools
    Appendices MISQ Archivist for Business Process Change: A Study of Methodologies, Techniques and Tools By William J. Kettinger James T.C. Teng Subashish Guha A total of eight appendices (Appendix 1 through Appendix 8) and an associated reference for these appendices have been placed here. In addition, there is currently a search engine located at http://theweb.badm.sc.edu/bpr/ to assist users in identifying BPR techniques and tools. 1 Appendices 1-8 Contained in MISQ Archivist Appendix 1: Detailed Description of the Research Methodology Appendix 2: Sources of Research Data Appendix 3: Mapping and Reliability of Stages to BPR Methodologies Appendix 4: BPR Techniques Description and Mapping Appendix 5: BPR Tools Description & Mapping Appendix 6: Hierarchical Mapping of BPR Techniques and Tools to the Stage-Activity Framework Appendix 7: IT/Process Analysis Appendix 8: Categories of BPR Techniques Appendix References 2 Appendix 1: Detailed Description of the Research Methodology Referring to Table 1, the researchers conducted the following research steps: Steps 1&2: Literature Review and Market Assessment The authors conducted a literature search on the current state of BPR MTTs using secondary research sources which include scholarly and trade literature, CD- ROM product data bases, on-line market intelligence services such as Computer Select, ABI/Inform, and reports from market research firms such as IDC, Seybold's and Gartner Group, product announcements, public bulletin boards, as well as recently published books and periodicals (e.g., Spurr, Layzell, Jennison & Richards, 1994; Hansen, 1994). This effort produced a list of initial sources of research data as shown in Appendix 2, which classifies these sources into two groups: 1) BPR Market Researchers and Consultants, and 2) BPR Tools and Technology Vendors.
    [Show full text]
  • SADT — Structured Analysis & Design Technique
    Workshop: SADT: Structured Analysis & Design Technique SADT — Structured Analysis & Design Technique Yuling Li 12/5/16 1 Workshop: SADT: Structured Analysis & Design Technique How to Make a Pizza? 2 Workshop: SADT: Structured Analysis & Design Technique 3 Workshop: SADT: Structured Analysis & Design Technique How to Make a Pizza (Process/Activities) Systematically? • Analysis Determine what the system will do • Design Define subsystems and their interfaces • Implementation Create the subsystem independently • Integration Combine the subsystems into a single unit • Testing Verify the system workings • Installation Make the system operational • Operation Use the system 4 Workshop: SADT: Structured Analysis & Design Technique “M models A if M answers questions about A” ---- Douglas T. Ross 5 Workshop: SADT: Structured Analysis & Design Technique Contents 1 Overview of SADT 2 Syntax and Semantics 3 SADT Diagrams 4 Cases 6 Workshop: SADT: Structured Analysis & Design Technique 1 Overview of SADT SADT IDEF0 IDEF Family 7 Workshop: SADT: Structured Analysis & Design Technique Emergent 1950s “hierarchic, layered modular system” SA Box ➕ 1960s “system of systems for building systems” SA Decomposition “top-down hierarchic decomposition” ➕ Cell 1970s “Hori’s Human-directed activity cell model” modelling “language for blueprinting systems” SADT • Douglas T. Ross developed SADT (1969-1973 ) • SADT is a trademark of SofTech, Inc. (After 1973) 8 Workshop: SADT: Structured Analysis & Design Technique Develop • During the 1970s, the U.S. Air Force Program
    [Show full text]
  • Business Modelling: UML Vs. IDEF
    Griffith University School of Computing and Information Technology Domain: Advanced Object Oriented Concepts Business Modelling: UML vs. IDEF available electronically at: http://www.cit.gu.edu.au/~noran © Ovidiu S. Noran Table of Contents. 1 Introduction....................................................................................................1 1.1 The objectives of this paper..............................................................................1 1.2 Motivation.........................................................................................................1 1.3 Some Important Terms.....................................................................................2 1.3.1 Models. .............................................................................................................. 2 1.3.2 Business Process Models.................................................................................. 2 1.3.3 Information Systems Support. ........................................................................... 3 1.3.3.1 The Business Model as a Base for Information Systems.......................... 3 1.3.3.2 'Legacy' Systems....................................................................................... 4 1.3.4 Business Improvement vs. Innovation............................................................... 4 1.4 Business Concepts...........................................................................................4 1.4.1 Business Architecture. ......................................................................................
    [Show full text]
  • Process Based Agile Supply Chain Model According to BPR and IDEF 3.0 Concepts
    Contemporary Engineering Sciences, Vol. 2, 2009, no. 3, 117 - 138 Process Based Agile Supply Chain Model According to BPR and IDEF 3.0 Concepts Abbas Toloie Eshlaghy1 Industrial Management Department Ponak St. Hesarak Ave. I.A.U.Science and Research Branch, Tehran, Iran. [email protected] ; [email protected] Ali Rajabzadeh Ghatari Tarbiat Modares University IMPSC(Iranian Management Productivity Study Center) Management Department, Tehran, Iran [email protected], [email protected], [email protected] Hashem Nikoomaram Business Management Ponak St. Hesarak Ave.I.A.U.Science and Research Branch, Tehran, Iran [email protected] Hessam Zandhessami Industrial Management Department Ponak St. Hesarak Ave. I.A.U.Science and Research Branch, Tehran, Iran. [email protected] Abstract Nowadays, growth and survival of organizations is due to applying an effective method for systematic planning and executing that plan through the organization. During earlier years, different concepts for organizational change have been propounded and business processes has considered as a conceptual framework for designing the structure of an organization. Appro- priate identification, definition and mapping of key processes (Process Map) would coordinate organizational component in order to achieve its objectives. Process approach and process orientation are important issues that pioneer 1Corresponding author 118 A. Toloie Eshlaghy et al organizations should take care about. Acceptance of change with applying different known approaches like: Reengineering, Kaisen (Japanese continual improvement) and TQM are based on a primary assumption that organi- zations should focus on their main mission i.e. satisfying customer needs. Success in applying processes as organization constituents in this survey per- suade researchers to develop a process based model to achieve agile supply chain.
    [Show full text]
  • Categorization and Representation of Functional Decomposition by Experts
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Calhoun, Institutional Archive of the Naval Postgraduate School Calhoun: The NPS Institutional Archive Theses and Dissertations Thesis Collection 2008-09 Categorization and representation of functional decomposition by experts Melancon, Paul W. Monterey, California. Naval Postgraduate School http://hdl.handle.net/10945/3950 NAVAL POSTGRADUATE SCHOOL MONTEREY, CALIFORNIA THESIS CATEGORIZATION AND REPRESENTATION OF FUNCTIONAL DECOMPOSITION BY EXPERTS by Paul W. Melançon September 2008 Thesis Advisor: Gary O. Langford Second Reader: John Osmundson Approved for public release; distribution is unlimited THIS PAGE INTENTIONALLY LEFT BLANK REPORT DOCUMENTATION PAGE Form Approved OMB No. 0704-0188 Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instruction, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188) Washington DC 20503. 1. AGENCY USE ONLY (Leave blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED September 2008 Master’s Thesis 4. TITLE AND SUBTITLE Categorization and Representation of Functional 5. FUNDING NUMBERS Decomposition by Experts 6. AUTHOR(S) Paul W. Melançon 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION Naval Postgraduate School REPORT NUMBER Monterey, CA 93943-5000 9.
    [Show full text]