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:
The term “cloud” is very popular and widely used now, it is a server, data processing centre, or a network which lets to store the data and software, provides access to them, allows to run applications without installation and gives the possibility to process data hosted remotely via the Internet connection. For documenting the Cloud Computing Architecture with a goal to facilitate the communication between stakeholders are successfully used the Cloud Computing Architecture diagrams. It is convenient and easy to draw various Cloud Computing Architecture diagrams in ConceptDraw DIAGRAM software with help of tools of the Cloud Computing Diagrams Solution from the Computer and Networks Area of ConceptDraw Solution Park.How to Build Cloud Computing Diagram<br>Principal Cloud Manufacturing *
Picture: How to Build Cloud Computing DiagramPrincipal Cloud Manufacturing
Related Solution:
Use ConceptDraw DIAGRAM software with Flowcharts Solution to create Process Flow Charts, Flow Chart Process Maps, and High-Level Process Flow Charts to illustrate ✔️ high-level processes in industrial, chemical, and process engineering, ✔️ major plant processes, ✔️ minor detailsProcess Flow Chart
Picture: Process Flow Chart
Related Solution:
Being usually a very complex process that requires a lot of skills, patience, time, and artistic abilities, the concept mapping process now is incredibly easy thanks to the Concept Maps Solution from the Diagrams Area of ConceptDraw Solution Park.Concept Mapping *
Picture: Concept Mapping
Related Solution:
Data Flow Diagram is used to depict the flow of data through the system, where it enters and exits the system, as well as where it is stored. To simplify the process of drawing a data flow diagram (DFD), ConceptDraw DIAGRAM provides a DFD Library - design elements that will help you make your diagram as informative, streamlined and understandable as possible. Data flow diagrams are useful to create a general overview of the system or to document major data flows. Here are the library of symbols used in data flow diagrams (DFD). Data Flow diagrams are graphic means of business process visualization. Any business process may involve the data transfer. It can be easily shown using data flow diagrams. DFDs are used to represent the processing and transformation of data within a business process. One can find out the Vector library of DFD symbols, that is a component of ConceptDraw solution for Data Flow Diagramming and is welcome to use in as addition to the common Conceptdraw DIAGRAM diagramming facilities.DFD Library — Design elements *
Picture: DFD Library — Design elements
Related Solution:
The vector stencils library COM and OLE from the solution Software Engineering contains 15 symbols of the COM and OLE objects for ConceptDraw DIAGRAM software.COM and OLE Diagram
Picture: COM and OLE Diagram
UML Apartment Plan. This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the UML Class Diagram library of the Rapid UML Solution from the Software Development area of ConceptDraw Solution Park. This sample show the detailed plan of the apartment and is used by building companies, design apartments, real estate agencies, at the buying / selling of the realty.UML Class Diagram Example -  Apartment Plan *
Picture: UML Class Diagram Example - Apartment Plan
Related Solution:
ConceptDraw DIAGRAM diagramming and vector drawing software offers the Fault Tree Analysis Diagrams Solution from the Industrial Engineering Area of ConceptDraw Solution Park for quick and easy creating the Fault Tree Diagram of any degree of detailing.Fault Tree Diagram *
Picture: Fault Tree Diagram
Related Solution:
Nowadays, any architect or landscape designer can't do without a pack of digital tools for designing and projecting. Thus, there will be no problem to develop any landscape architecture plan with ConceptDraw DIAGRAM , especially since there are so many ready-to use templates and examples included. It's just as easy as drawing sketches on paper. If you using ConceptDarw DIAGRAM there is no needs to have a professional skills on landscape and garden design. As well as you don't need to be an expert in architectural charts and plans drawing. The all you need is the Landscape and Garden solution. This solution contains a unique collection of the professional designed vector objects depicting flower and grass, bushes and trees, garden furniture, pools and accessories. In one word - the full set of graphical elements enabling to focus on the creativeness while creating your landscape and garden plan.Landscape Architecture with ConceptDraw DIAGRAM  *
Picture: Landscape Architecture with ConceptDraw DIAGRAM
Related Solution:
You need design a Bank UML Diagram? Now, thanks to the ConceptDraw DIAGRAM diagramming and vector drawing software extended with ATM UML Diagrams Solution from the Software Development Area, you can design without efforts any type of Bank UML Diagram you want - Class, Activity, Communication, Component, Composite structure, Deployment, Interaction overview, Object, Package, Profile, Sequence, State machine, Timing, Use case.Bank UML Diagram *
Picture: Bank UML Diagram
Related Solution:
ConceptDraw DIAGRAM is the best software for illustration the network topologies. It's very easy and quickly to design the network topology diagrams of any kinds and complexity in ConceptDraw DIAGRAM diagramming and vector drawing software using the Computer and Networks solution from Computer and Networks area of ConceptDraw Solution Park.Network Topology Illustration *
Picture: Network Topology Illustration
Related Solution:
ConceptDraw
DIAGRAM 18