Made with
ConceptDraw
DIAGRAM 18

IDEF3 Standard

In contrast to IDEF0 standard, IDEF3 standard is more particularly specialized. This standard is intended for description and further analysis of technological processes of an enterprise. Using IDEF3 standard it is possible to examine and model scenarios of technological processes. Scenario is a description of consecution of properties changes of an object which takes part in the technological process, e.g. half-finished product which is under processing. Each scenario is documented correspondingly. For documenting of the scenario there are two types of documents: documents, which describe properties and consecution of the process execution (standards, methods and technologies description) and documents, which describe results of the process execution (reports and work statistics). IDEF3 standard allows to get information about process and attendant documentation and to analyze it for increasing of the process management effectiveness. Using IDEF3 standard you can collect and document information about processes key points, define the degree of influence on the course of processes execution and model scenarios without change of the production process itself.

There are two types of diagrams in IDEF3 standard. These diagrams describe the same technological process from different sides. First type of diagram is Process Flow Description Diagrams (PFDD). The second type - Object State Transition Network (OSTN) diagrams.

For instance if it is necessary to describe the process of stamping the detail from a billet, the PFDD diagram will contain a description of consecution of actions which are executed with the billet during the given process, and the OSTN diagram will contain the detail states on each process stage.

Rectangular blocks on the diagram are called functional units or Units of Behavior (UOB). Each UOB has the name in the verb form and a unique number and denotes an event within the limits of the process (a stage, an action or decision making). UOB are connected by arrows in consecution of the process execution. There are 3 different kinds of arrows: Precedence arrow - a solid line, which is drawn from left to right or top-down; Relational Link - a dotted line, used for description of relations between UOB; Object Flow - an arrow with two arrow-heads. Such arrow denotes that the object is used in two or more subruns. For example, when the object is created in one subrun and is used in another one.

The block marked with the cross on the diagram is called a Junction. Such blocks are used for indication of decision makings during the process. Accordingly to IDEF3 standard there are two types of Junctions: for confluence (Fan-in Junction) and branching (Fan-out Junction) of arrows. Simultaneous junction and branching is not allowed. Junctions can be of different types. The junction type is denoted on the diagram.

Indication Name Fan-in Junction Fan-out Junction
Asynchronous AND Asynchronous AND All preceding subruns must be completed All subsequent subruns must be started
Synchronous AND Synchronous AND All preceding subruns must be completed simultaneously All subsequent subruns must be started simultaneously
Asynchronous OR Asynchronous OR One or several preceding subruns must be completed One or several subsequent subruns must be started
Synchronous OR Synchronous OR One or several preceding subruns must be completed simultaneously One or several subsequent subruns must be started simultaneously
Synchronous OR XOR (Exclusive OR) Only one preceding process must be completed Only one subsequent process must be started

All junctions in PFDD are numerated, each number has prefix "J", e.g. J1, J2 and so on.

Each UOB can be represented in the form of sequence of blocks with the necessary degree of detailed elaboration. For example the block “Testing of a detail” can be represented in the form of sequence of blocks, which in their turn will form PFDD diagram. Such diagram will be called a Child diagram, and the initial diagram – a Parent diagram.

The OSTN diagram represents a list of object state and descriptions of influences which correspond to UOB blocks from the corresponding PFDD diagram. Object states are represented by circumferences and their changes – by directed lines, which are signed the same way as corresponding UOB blocks.

IDEF3 Standard *

TEN RELATED HOW TO's:
If you want to find a way to understand complex things in minutes, you should try to visualize data. One of the most useful tool for this is creating a flowchart, which is a diagram representing stages of some process in sequential order. There are so many possible uses of flowcharts and you can find tons of flow charts examples and predesigned templates on the Internet. Warehouse flowchart is often used for describing workflow and business process mapping. Using your imagination, you can simplify your job or daily routine with flowcharts. Warehouse flowcharts are used to document product and information flow between sources of supply and consumers. The flowchart provides the staged guidance on how to manage each aspect of warehousing and describes such aspects as receiving of supplies; control of quality; shipment and storage and corresponding document flow. Warehouse flowchart, being actual is a good source of information. It indicates the stepwise way to complete the warehouse and inventory management process flow. Also it can be very useful for an inventory and audit procedures.Warehouse Flowchart
Picture: Flow Chart Example: Warehouse Flowchart
Related Solution:
The Total Quality Management Diagram solution helps you and your organization visualize business and industrial processes. Create Total Quality Management diagrams for business process with ConceptDraw software.TQM Software — Build Professional TQM Diagrams *
Picture: TQM Software — Build Professional TQM Diagrams
Related Solution:
There are many tools to manage a process or to illustrate an algorithm or a workflow. Flowcharting is one of those tools. However, it may be difficult to show complex processes that require multiple attributes or several people in a simple flowchart, so a cross-functional flowchart would be a solution for that situation. To create such flowchart, group processes and steps to labeled rows or columns, and divide those groups with horizontal or vertical parallel lines. It is worth mentioning that there are different types of cross-functional flowcharts, like opportunity or deployment flowchart. This diagram shows a cross-functional flowchart that was made for a trading process. It contains 14 processes, distributed through 5 lines depicting the participants who interact with the process. Also there are connectors that show the data flow of information between processes. The cross-functional flowchart displays a detailed model of the trading process, as well as all participants in the process and how they interact with each other. The lines in the flowchart indicates the position, department and role of the trading process participants.Cross-Functional Flowchart
Picture: Cross-Functional Flowchart
Related Solution:
The UML Diagrams are widely used by software developers and software engineers. They can draw the UML Diagrams manually on the paper, but it is incredibly convenient to use the special UML diagramming software. The UML diagramming software allows you to draw the UML Diagrams in a few minutes.UML Diagram Software *
Picture: UML Diagram Software
Related Solution:
If you are an advanced diagramming software user, you might use it daily. Traversing the Internet in searching of alternative to MS Visio for MAC and PC, you can fulfill all your requirements with ConceptDraw DIAGRAM. Don’t hesitate to transfer your documents to another operating system. When looking for a smart and simple tool for business diagrams as alternative to MS Visio for Apple OS X platform, ConceptDraw DIAGRAM certainly is the best choice. Making many kinds of business charts, numerous technical drawings is what ConcepDraw DIAGRAM is the best. One can easy create any diagram and complete it perfectly and quickly. The big collection of vector object libraries, templates and samples, make it the best Microsoft Visio alternative: ConceptDraw DIAGRAM is simpler to use, less expensive, and supports project management and mind mapping methods.Alternative to MS Visio for MAC and PC
Picture:
In Searching of Alternative to MS Visio for Mac and PC
with ConceptDraw DIAGRAM
Being involved in the process of planning some system of interacting the objects, or in other words, being engaged in the object-oriented design in order to solve some software problem as one of the approaches used in the software design, you may find the ConceptDraw DIAGRAM diagramming and drawing software a really useful tool for making the needed drawings, such as the IDEF Business Process Diagrams.Object-Oriented Design *
Picture: Object-Oriented Design
Related Solution:
Is it possible to develop a diagram as quickly as the ideas come to you? The innovative ConceptDraw Arrows10 Technology included in ConceptDraw DIAGRAM is a powerful drawing tool that changes the way diagrams are produced. While making the drawing process easier and faster.How to draw a Cross-Functional Flowchart *
Picture: How to draw a Cross-Functional Flowchart
Related Solution:
Use Case Diagrams technology. An effective management of changes is significantly facilitated by way of definition and documenting of business-requirements.IDEF9 Standard *
Picture: IDEF9 Standard
Use Case Diagrams technology. Using visual graphical objects IDEF1 standard allows to model information interrelations.IDEF1 standard *
Picture: IDEF1 standard
ConceptDraw DIAGRAM is a flowchart creating software. This software includes over 20 vector stencils in libraries. These objects allow you to create well-designed flowcharts. Put an initial object from library to a page and use RapidDraw technology clicking on direction arrows to add new objects to the flowchart. This way you can make flowchart quickly.How To Create a Flow Chart in ConceptDraw *
Picture: How To Create a Flow Chart in ConceptDraw
Related Solution:
ConceptDraw
DIAGRAM 18