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:
Data structure diagram (DSD) is intended for description of conceptual models of data (concepts and connections between them) in the graphic format for more obviousness. Data structure diagram includes entities description, connections between them and obligatory conditions and requirements which connect them. Create Data structure diagram with ConceptDraw DIAGRAM.Data structure diagram with ConceptDraw DIAGRAM
Picture: Data structure diagram with ConceptDraw DIAGRAM
Definition, examples, layout options, best practices, and common mistakes for cross functional flowcharts (swimlane diagrams).Cross functional flowchart structure showing workflow across sales, finance, and operations swimlanes with decision and handoff
Picture: Cross Functional Flowchart (Swimlane Diagram): Definition, Structure, Examples, and How to Create
Related Solution:
ConceptDraw DIAGRAM is the best BPMN software for ✔️ modeling business processes, ✔️ graphical documenting processes, ✔️ analysis processes, ✔️ optimization business processes, ✔️ identifying inefficiencies, ✔️ efficient decision-making based on created Business Process Diagrams and Business Process ModelsConceptDraw DIAGRAM — The Best Business Process Modeling Software
Picture: The Best Business Process Modeling Software: Comprehensive Guide
Related Solution:
The Rapid UML solution provides diagram examples, templates and vector stencils libraries for quick and easy drawing all types of UML 2.x and 1.x diagramsUML Business Process
Picture: UML Business Process
Related Solution:
A Venn diagram, sometimes referred to as a set diagram, is a diagramming style used to show all the possible logical relations between a finite amount of sets. Having ConceptDraw DIAGRAM software one allows anyone who cares for their drawings to look not only nice but also smart and professional.Venn Diagram Examples for Problem Solving. Chomsky Hierarchy
Picture:
Venn Diagram Examples for Problem Solving
Computer Science. Chomsky Hierarchy
Related Solution:
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:
If your company is in chaos in clutter and no one understands their rights and responsibilities, maybe it's time to change that. One of the ways to put the company in order is to draw an organization chart that would reflect the structure and show the relationships among departments and positions. This is a very useful and easy to understand scheme. This is example of the one of the most typical kind of organizational chart. It depicts an organizational structure of the hierarchical type. Its construction is similarv to pyramid. The single main position on the top - in this case, the mayor's position followed by sub-levels of authority in his command. Each position in the pyramid reports only to his supervisor, and takes only a report of direct subordinates. Such scheme limits the number of communications. This organizational structure is effectively used in public organizations. Also it is suitable for any organization with the need for multiple levels of middle managers. The ability to create organizational charts of different types is supplied with ConceptDraw Ogrcharts solutions.How to Draw an Organization Chart *
Picture: How to Draw an Organizational Chart
Related Solution:
The PERT Chart is constructed as part of the process in creating a schedule of corrective actions. The PERT Chart shows the logical connections and consequence of tasks to be performed. It displays the time period for problem solving and the implementation of all activities through the critical path. ConceptDraw Office suite is a software for corrective actions planning.CORRECTIVE ACTIONS PLANNING. PERT Chart *
Picture: CORRECTIVE ACTIONS PLANNING. PERT Chart
If neither of 45 vector shapes of the Cross-Functional Flowcharts solution don't fit your needs, you will want to learn How to create a unique Cross-Functional flowchart. ConceptDraw Arrows10 Technology - This is more than enough versatility to draw any type of diagram with any degree of complexity. Drawing software lets you to make horizontal and vertical, audit, opportunity and many more flowcharts.How to Create a Cross Functional Flow Chart *
Picture: How to Create a Cross Functional Flow Chart
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:
ConceptDraw
DIAGRAM 18