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 storage is a fundamental aspect of the cloud platform. Microsoft offers scalable, durable and elastic cloud Azure Storage which can be available from any type of application whether it’s running in the cloud and anywhere in the world. ConceptDraw DIAGRAM diagramming and vector drawing software extended with Azure Architecture Solution from the Computer and Networks area of ConceptDraw Solution Park provides a lot of useful tools which give you the possibility effectively illustrate Microsoft Azure cloud system, Azure services, Azure storage and its components.Azure Storage *
Picture: Azure Storage
Related Solution:
All about prototyping. GUI Prototyping with ConceptDraw. Download prototyping software.GUI Prototyping with ConceptDraw DIAGRAM
Picture: GUI Prototyping with ConceptDraw DIAGRAM
It doesn’t matter what kind of business you have, a bar or a gym, there are common concepts for any of them. One of those concepts is accounting, and to facilitate the work with the figures, you can use accounting flowchart symbols and create a clear and representative scheme. You can create flowchart for auditing, tax accounting and even for planning your own budget. A graphical tool for displaying successive processes is flowchart. This method is mostly suited to represent an accounting process. The sequence of steps in the accounting process usually consists of standard accounting procedures, that can be depicted by using a minimal number of symbols, applied for the basic flowcharting. The advanced opportunity to create professional Accounting Flow charts is provided by ConceptDraw Accounting Flowcharts solution. It includes contains a library of accounting flowchart symbols used when drawing the accounting process flow.Accounting Flowchart Symbols
Picture: Accounting Flowchart Symbols
Related Solution:
ConceptDraw DIAGRAM is a powerful Network Engineering software thanks to the Vehicular Networking Solution and many other networking solutions from the Computer and Networks Area of ConceptDraw Solution Park.Network Engineering *
Picture: Network Engineering
Related Solution:
ConceptDraw - Organigram software allows quickly create Organigrams and much more. ConceptDraw DIAGRAM is an ideal tool for Administrative staff to clearly demonstrate the company orgchart professional.Organigrams with ConceptDraw DIAGRAM  *
Picture: Organigrams with ConceptDraw DIAGRAM
Related Solution:
Business process maps help you evaluate and manage quality in a work process chain, placing an emphasis on corporate performance and optimization. Business Mapping Software a versatile collection of libraries and templates, that allow you to create business process and SIPOC diagrams, using the Six Sigma methodology.Business Mapping Software *
Picture: Business Mapping Software
Related Solution:
Swim lanes are visual elements used in Business Process Maps, Process Flow Diagrams and Flowcharts. ConceptDraw DIAGRAM diagramming and vector drawing software extended with Business Process Mapping Solution from the Business Processes Area of ConceptDraw Solution Park is ideal for drawing Business Process Maps and Swim Lanes Flowcharts.Swim Lanes *
Picture: Swim Lanes
Related Solution:
ConceptDraw DIAGRAM extended with IDEF Business Process Diagrams solution from the Business Processes area of ConceptDraw Solution Park is an ideal software for effective database design and drawing IDEF diagrams visually representing all steps of database design process.Database Design *
Picture: Database Design
Related Solution:
ConceptDraw has 142 vector stencils in the 8 libraries that helps you to start using software for designing own Business Process Diagrams. Use Swimlanes library with 20 objects from BPMN.Business Process Elements: Swimlanes *
Picture: Business Process Elements: Swimlanes
Related Solution:
In software engineering, it is important to understand how the system would cooperate with external sources, like data sources. To give this information a visual representation, data flow diagrams (DFD) were used for years. The entire system is usually divided into smaller ones, and all of them process data flows in appropriate ways. The visualizing business processes which engages the data transfer, is commonly preformed using DFDs (data flow diagrams). DFD is used to show the data flow processing and transformation. This DFD represents the electronic system of a customer purchase. It was created using Gane/Sarson notation. Data flow diagrams helps you to sort through and clarify transferring process making it available for analysis, and representation. ConceptDraw DFD solution introduces the vector library, containing the full set of icons from DFD notations.Data Flow Diagram (DFD) *
Picture: Data Flow Diagram (DFD)
Related Solution:
ConceptDraw
DIAGRAM 18