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:
Functional modeling allows to make complex business processes simple. One of the basic methods is IDEF0 and one of the most effective also. To create a business model, use flowchart symbols. The IDEF0 library, supplied with ConceptDraw IDEF0 Diagrams solution contains 18 IDEF0 basic notation symbols. All symbols are the vector graphic images what means, that one can customize their size preserving the stable quality. Another library of IDEF0 symbols can be find out in the the Business Process Diagrams solution, included to the Business Processes section of ConceptDraw Solution Park. These libraries composed from just vector objects and are totally compatible. You can apply the IDEF0 symbols from both libraries at your flowcharts, if needed.IDEF0 Flowchart Symbols
Picture: IDEF0 Flowchart Symbols
Related Solution:
The most easier way of creating the visually engaging and informative Sales Process Flowchart is to create the new ConceptDraw document and to use the predesigned vector symbols offered in 6 libraries of the Sales Flowchart Solution. There are more than six types of sales process flow diagrams, ConceptDraw DIAGRAM software is flowchart maker which include six collections of extended flowchart symbols for effective diagramming. There are main collections of color coded flowchart symbols: Sales Department, Sales Steps, Sales Workflow, Sales Symbols and special set of Sales Arrows and Sales Flowchart.Sales Process Flowchart Symbols *
Picture: Sales Process Flowchart Symbols
Related Solution:
You need design the Functional Block Diagram and dream to find the useful tools to draw it easier, quickly and effectively? ConceptDraw DIAGRAM offers the Block Diagrams Solution from the Diagrams Area which will help you!Functional Block Diagram *
Picture: Functional Block Diagram
Related Solution:
ConceptDraw DIAGRAM extended with Chemistry solution is effective for drawing various organic chemistry schemes, diagrams, illustrations thanks to the included collection of predesigned organic chemistry symbolsOrganic Chemistry Symbols
Picture: Organic Chemistry Symbols
Related Solution:
ConceptDraw Business Finance Illustration examples and libraries contain vector clip art for drawing different Business and Finance Illustrations. You may find Advertising example, Project Management example, Business Model example and many more.Business and Finance Illustrations Example *
Picture: Business and Finance Illustrations Example
Related Solution:
A Data Flow Diagram (DFD) is a graphical technique which allows effectively model and analyze the information processes and systems. The ability to fast and easy create the DFDs is made possible with Data Flow Diagrams solution from the Software Development area of ConceptDraw Solution Park. For designing the Data Flow Diagrams are used simple DFD flowchart symbols which are connected each other by arrows depicting the data flow from one step to another.DFD Flowchart Symbols *
Picture: DFD Flowchart Symbols
Related Solution:
A database is a data collection, structured into some conceptual model. Two most common approaches of developing data models are UML diagrams and ER-model diagrams. There are several notations of entity-relationship diagram symbols and their meaning is slightly different. Crow’s Foot notation is quite descriptive and easy to understand, meanwhile, the Chen notation is great for conceptual modeling. An entity relationship diagrams look very simple to a flowcharts. The main difference is the symbols provided by specific ERD notations. There are several models applied in entity-relationship diagrams: conceptual, logical and physical. Creating an entity relationship diagram requires using a specific notation. There are five main components of common ERD notations: Entities, Actions, Attributes, Cardinality and Connections. The two of notations most widely used for creating ERD are Chen notation and Crow foot notation. By the way, the Crow foot notation originates from the Chen notation - it is an adapted version of the Chen notation.ERD Symbols and Meanings
Picture: ERD Symbols and Meanings
Related Solution:
Chemical and Process Engineering solution contains variety predesigned process flow diagram elements relating to instrumentation, containers, piping and distribution necessary for chemical engineering, and can be used to map out chemical processes or easy creating various Chemical and Process Flow Diagrams in ConceptDraw DIAGRAM.Process Flow Diagram Symbols
Picture: Process Flow Diagram Symbols
Related Solution:
ConceptDraw
DIAGRAM 18