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:
It’s very easy, quick and convenient to draw the Event-driven Process Chain (EPC) diagrams in ConceptDraw DIAGRAM diagramming and vector drawing software using the Event-driven Process Chain Diagrams Solution from the Business Processes area of ConceptDraw Solution Park.Event-Driven Process Chain Diagram Software *
Picture: Event-Driven Process Chain Diagram Software
Related Solution:
ConceptDraw - Perfect Network Diagramming Software with examples of Backbone Network Diagrams. ConceptDraw Network Diagram is ideal for network engineers and network designers who need to draw Backbone Network diagrams.Network Diagram Software<br>Backbone Network *
Picture: Network Diagram SoftwareBackbone Network
The popularity of Block Diagrams grows day by day. The existence of powerful software for their design is an excellent news! ConceptDraw DIAGRAM Block Diagram Software offers the Block Diagrams Solution from the Diagrams Area.Block Diagram Software *
Picture: Block Diagram Software
Related Solution:
UML Activity Diagram illustrate the business and operational step-by-step workflow of components in a system and shows the overall flow of control.UML Activity Diagram. Design Elements *
Picture: UML Activity Diagram. Design Elements
A perfect tool to draw network diagram for bandwidth management. Computer & Networks solution provides the symbol libraries with pre-designed network graphic elements. Use Computer & Networks solution to draw the network diagrams for bandwidth management for Cisco networks, Apple networks, IVR networks, GPRS networks, wi-fi networks, LAN and WAN.Network Diagrams for Bandwidth Management *
Picture: Network Diagrams for Bandwidth Management
Planning a computer network can be a challenge for a junior specialist. However, knowing how to draw a computer network diagrams isn’t a rocket science anymore. There are a lot of special software for creating such diagrams with predesigned templates and examples. The core for Network Fault Tolerance System presented here, is the equipment of Cisco. You can see here the certified Cisco equipment icons. Generally, ConceptDraw DIAGRAM libraries contain more than half of a thousand objects representing the standardized images of Cisco equipment. ConceptDraw solution for network diagramming is a great network diagramming tool for any level skills - from students to network guru.How to Draw a Computer Network Diagrams
Picture: How to Draw a Computer Network Diagrams
Related Solution:
When we think of an hierarchy, we intuitively imagine a pyramid. Thus, a lot of management tools use pyramid charts as examples or illustrations of various documents or models. You can create any type of triangle diagram using ConceptDraw DIAGRAM. A triangle (pyramid) diagram is often used in marketing to show the data hierarchy. This pyramid diagram represents the Top Brand Model. It illustrate the model of rebranding strategy. It can be used by marketing agency dealing with rebranding strategies development. It’s critical for marketing diagrams to be both clear and eye catching. ConceptDraw Pyramid diagrams solution meet all these requirements and can be successfully applied for creating and presenting various marketing pyramidal diagrams.Pyramid Chart Examples *
Picture: Pyramid Chart Examples
Related Solutions:
Use Case Diagrams technology. IDEF1x standard - for work with relational data bases. IDEF1x standard is meant for constructing of conceptual schemes which represent the structure of data in the context of the concerned system, for example, a commercial organization.IDEF1X Standard *
Picture: IDEF1X Standard
UML Object Diagram shows the structure of a modeled system at a specific time. ConceptDraw Rapid UML solution delivers libraries contain pre-designed objects fit UML notation, and ready to draw professional UML Object Diagram.Diagramming Software for Design <br>UML Object Diagrams *
Picture: Diagramming Software for Design UML Object Diagrams
Related Solution:
Use Case Diagrams describes the functionality provided by a system in terms of actors, their goals represented as use cases, and any dependencies among those use cases.Diagramming Software for Design UML Use Case Diagrams *
Picture: Diagramming Software for Design UML Use Case Diagrams
ConceptDraw
DIAGRAM 18