Resources: iDef0, Document Map, Work Diagrams, Rendered Process Map, Pitfalls of Process Mapping
• iDef0 ‐ IDEFØ is a method designed to model the decisions, actions, and activities of an organization or system. IDEFØ was derived from the a graphical language, the Structured Analysis and Design Technique (SADT). The United States Air Force commissioned the developers of SADT to develop a function modeling method for analyzing and communicating the functional perspective of a system. IDEFØ models are often created as one of the first tasks of a system development effort. There are many types of iDef’s used for a variety of applications, from BPR tosoftware development (i.e. iDef0, iDef1, iDef3, etc.).
• Document Map – Used to access data held in a collection of documents or knowledge base.
• Work Diagrams – Flow The assembly line is probably the most famous example of a work flow.
• Rendered Process Map – A computer generated map showing the relationship between associated objects (i.e. geospatial layers in a map layout, which may include geometric, raster, map grid, and/or pinmap layers)
• Org Charts, relationship maps, etc.
Pitfalls of Process Mapping
• The understanding of how a process actually works is often unknown; even management may not know for sure.
• Processes often vary by the leaders. For example a team of Project Engineers who each run their projects in their own way; often a source of variation.
• Ad‐hoc process are common in smaller organizations and/or new projects or organizations.
• People will sometimes give you information p g y on how they think the process should work rather than the way it actually works. Walk the process your self when ever possible; imagine yourself as the part or information flowing through the process.
• On many occasions, the process may not be consistent from day to day.
• Consensus reaching may be required when the process is not well defined.