FLOWCHAR

1
 OBJECTIVES

o To know what Flowchart is, it’s history and its types

o To know the use and when to use Flowchart

o To know the Advantages and Disadvantages of Flowchart

o To be able to know the symbols used in flowcharts

o To know to make a Flowchart

2
FLOWCHART
o A flowchart is a diagram that depicts a process, system or computer
algorithm.
o They are widely used in multiple fields to document, study, plan,
improve and communicate often complex processes in clear, easy-to-
understand diagrams.
o Flowcharts, sometimes spelled as flow charts, use rectangles, ovals,
diamonds and potentially numerous other shapes to define the type of
step, along with connecting arrows to define flow and sequence.
o They can range from simple, hand-drawn charts to comprehensive
computer-drawn diagrams depicting multiple steps and routes.

3
 FLOWCHART
o If we consider all the various forms of flowcharts,
they are one of the most common diagrams on the
planet, used by both technical and non-technical
people in numerous fields.
o Flowcharts are sometimes called by more
specialized names such as Process Flowchart,
Process Map, Functional Flowchart, Business
Process Mapping, Business Process Modeling and
Notation (BPMN), or Process Flow Diagram (PFD).
o They are related to other popular diagrams, such as
Data Flow Diagrams (DFDs) and Unified Modeling
Language (UML) Activity Diagrams.
 HISTORY OF FLOWCHART

Flowcharts to document business processes came into use in

the 1920s and ‘30s.

In 1921, industrial engineers Frank and

Lillian Gilbreth introduced the “Flow
Process Chart” to the American Society of
Mechanical Engineers (ASME).

5
In the early 1930s, industrial engineer
Allan H. Mogensen used Gilbreth’s tools
to present conferences on making work
more efficient to businesspeople at his
company.
In the 1940s, two Mogensen students, Art
Spinanger and Ben S. Graham, spread the
methods more widely. Spinanger
introduced the work simplification
methods to Procter and Gamble. Graham,
a director at standard register industrial,
adapted flow process charts to information
processing.
In 1947, ASME adopted a symbol system
for Flow Process Charts, derived from the
Gilbreths’ original work.

6
Also, in the late ‘40s, Herman Goldstine
and John Van Neumann used flowcharts to
develop computer programs, and
diagramming soon became increasingly
popular for computer programs and
algorithms of all kinds. Flowcharts are
still used for programming today,
although pseudocode, a combination of
words and coding language meant for
human reading, is often used to depict
deeper levels of detail and get closer to a
final product.
In Japan, Kaoru Ishikawa (1915-1989), a key figure in quality
initiatives in manufacturing, named flowcharts as one of the
key tools of quality control, along with complementary tools
such as the Histogram, Check Sheet and Cause-and-Effect
Diagram, now often called the Ishikawa Diagram.

8
 TYPES OF FLOWCHART

Because flowcharts are such a powerful tool, they’re used across many fields and
industries. Whether it’s in education, sales and marketing, business, engineering, or
manufacturing, flowcharts can be found virtually anywhere.

Depending on the type of process you’re aiming to visualize, you’ll want to use a
different type of flowchart. Different authors describe various types of flowcharts in
different terms. These people include published experts such as MARK A. FRYMAN,
ALAN B. STERNECKERT, ANDREW VERONIS AND MARILYN BOHL.
ACCORDING TO MARK A. FRYMAN AND HIS 2002 BOOK
QUALITY AND PROCESS IMPROVEMENT, THERE ARE FIVE
TYPES OF FLOWCHARTS FROM A BUSINESS PERSPECTIVE:

o A decision flowchart helps to explain steps that are taken to

justify a decision. This type of flowchart can be helpful in
anticipating the consequences of different decisions.
o A logic flowchart is applied to uncover loopholes, bottlenecks, or
constraints in the process which could cause disruptions or issues.
o A system flowchart represents how data flows in a system.
They’re often used in the accounting world.
o A product flowchart visualizes the product creation process and
order of sequences. This type of flowchart can be a helpful piece
of documentation when you’re launching a new product or
improving the production process.
o A process flowchart displays how a process will achieve a
certain outcome. You will likely create a process flowchart to
improve an existing process or establish a new one. An example
for a process flowchart is a swimlane diagram.

10
ACCORDING TO STERNECKERT, IN HIS
2003 BOOK CRITICAL INCIDENT
MANAGEMENT, LISTED FOUR POPULAR
FLOWCHART TYPES, FRAMED AROUND
THE CONCEPT OF FLOW CONTROLS
RATHER THAN THE FLOW ITSELF:

11
VERONIS , IN HIS 1978 BOOK
MICROPROCESSORS: DESIGN
AND APPLICATIONS, OUTLINED
THREE FLOWCHART TYPES
BASED ON SCOPE AND LEVEL
OF DETAIL:
o System Flowchart: Identifies the
devices to be used.
o General Flowchart: Overview.
o Detailed Flowchart: Increased detail.

BOHL, IN HER 1978 BOOK A GUIDE FOR

PROGRAMMERS, LISTED ONLY TWO:
 ADDITIONAL FLOWCHART TYPES
DEFINED BY OTHERS INCLUDE:

Swimlane Diagram, a.k.a To delineate who does what in cross-team

Swimlane Flowchart
processes.

Workflow Flowchart ​Todocument workflows, often involving tasks,

documents and information in offices.

Event-Driven Process To document or plan a business process.

Chain (EPC) Flowchart

Specification and Description

Language (SDL) Flowchart​ To brainstorm computer algorithms using three
basic components: system definition, block and
process.

13
 USE OF
FLOWCHART
In any field:

o Document and analyze a process.

o Standardize a process for efficiency and

quality.

o Communicate a process for training or

understanding by other parts of the
organization.

o Identify bottlenecks, redundancies and

unnecessary steps in a process and improve it.

14
USE OF FLOWCHART IN
ENGINEERING
o Represent process flows or system flows.
o Design and update chemical and plant processes.
o Assess the life cycle of a structure.
o Chart a reverse-engineering flow.
o Demonstrate the design and prototype phase of a new structure
or product.

15
 WHEN TO USE FLOWCHART?

Document a process
A flowchart is a wonderful way to map out and
document a collaborative project or process.
Simplify and visualize complex ideas or processes
Not everyone on your team will have the time (or
resources) to read through a complicated and lengthy
process document. A flowchart allows everyone to
follow the workflow, understand the tasks, and
analyze the individual steps quickly and easily.
Organize your team and assign tasks effectively
Visually representing a process can make it easier for
you to assign tasks to team members and organize
your team’s work so it all flows better.

16
Make and justify decisions
Decisions often look way less intimidating and complicated when they’re
mapped out in a flowchart. A flowchart can also help you see the consequences of
your decisions, which makes it easier to anticipate and justify next steps.
Identify and prevent bottlenecks or issues
Flowcharts help you uncover bottlenecks or problems before they become
issues. By mapping out the entire process with this visual guide, you can follow each
step and ensure that you allocate enough time and resources to every task.
Standardize processes
Once your flowchart is done, you can reuse it for similar projects and
processes. This can save you and your team time—and stress—in the long run.
Track a project’s progress
Since it’s so easy to follow the steps in your flowchart, you can always
pinpoint where your team is currently at in the project or process. This makes
tracking progress very easy and also gives you a great overview of the tasks that still
need to be completed.

17
 ADVANTAGES AND DISADVANTAGES OF
FLOWCHART
ADVANTAGES
o Communication: Flowcharts are better way of communicating the logic of a system to all
concerned.
o Effective analysis: With the help of flowchart, problem can be analyzed in more effective
way.
o Proper documentation: Program flowcharts serve as a good program documentation, which
is needed for various purposes.
o Efficient Coding: The flowcharts act as a guide or blueprint during the systems analysis and
program development phase.
o Proper Debugging: The flowchart helps in debugging process.
o Efficient Program Maintenance: The maintenance of operating program becomes easy with
the help of flowchart. It helps the programmer to put efforts more efficiently on that part.

18
 DISADVANTAGES
Although a flowchart is a very useful tool, there are a few limitations in using flowcharts which are listed
below:

o Complex logic: Sometimes, the program logic is quite complicated. In that case, flowchart becomes complex
and clumsy.
o Alterations and Modifications: If alterations are required the flowchart may require re-drawing completely.
o Reproduction: As the flowchart symbols cannot be typed, reproduction of flowchart becomes a problem.
o The essentials of what is done can easily be lost in the technical details of how it is done.

19
FLOWCHART SYMBOLS

Flowcharts vary from quickly hand-drawn visualizations to help document or plan a

process to comprehensive workflow diagrams created with a designated software. To
make it easier for you to understand flowcharts across teams, departments, and even
industries, the American National Standards Institute (ANSI) set official standards in the
1960s which were adopted by the International Organization for Standardization (ISO) in
1970 and are continuously updated and improved. The latest version of this standard was
confirmed in 2019.

When reading a flowchart, follow the Western standard, meaning you’ll read it from the
top to the bottom and from the left to the right.

20
 MOST COMMONLY USED FLOWCHART SYMBOLS, THEIR
NAMES, AND MEANING.

o Flowline: The flowline shows the process’s direction by connecting two blocks with one another.

o Termina or Terminator: The terminal or terminator represents the start or end points of a flowchart process.

o Process: The process symbol is the most common component of a flowchart and indicates a step in the process.

o Comment or Annotation: You can indicate additional information about a step with a comment or annotation.

21
o Decision: This symbol represents a decision you or your team need to make to get to the next step
of the process. Typically, it’s a true or false decision or a yes or no question that you need to answer.

o Stored data: This symbolizes a data file or database.

o “Or” symbol: This indicates that the process flow continues in three or more branches.

o Input/Output: The input/output symbol represents the process of in- or outputting external data.

22
o Display: This indicates a step that displays relevant information.

o Document: This symbol represents a single document.

o Delay: This symbol allows you to plan and represent any delay periods that will be part of the process.

o Manual input: This symbol represents data or information that needs to be manually entered into a system.

23
o Manual operation: This symbolizes a manual operation or adjustment to the process.

o Off-page connector: This symbol is used to connect two symbols that are of different pages.

o On-page connector: This dot can connect two symbols and replace long lines which allows for a cleaner
flowchart.

o Summoning junction symbol: This symbol is used to converge multiple branches back into a single process.

24
Alternate process: The lines to this symbol are usually dotted. The symbol itself stands for an alternative to the
normal process step in case one is needed.

Predefined process: This symbol indicates a process that is already defined elsewhere.

Multiple documents: This symbolizes multiple documents.

Preparation or initialization: This symbol indicates a preparation or initialization step in the process.

25
 HOW TO MAKE A FLOWCHART
1. Define the purpose and scope. Before you hit the
drawing board or open your flowchart maker, define your
project scope and process purpose. Ask yourself what
your project should accomplish and what appropriate
beginning and end dates are.
2. Put your tasks in chronological order. Depending on the
kind of flowchart you’re creating, you may want to
review existing documentation, interview team members
on their past experiences, or observe an existing process.
It can help to write down some of the steps as a list before
you create your first flowchart draft.
3. Organize your tasks by type and flowchart symbol.
Once you have all of your tasks written out and organized
chronologically, assign them to their corresponding
symbol so you’re prepared to draw your flowchart.
4. Draw your flowchart. You can sketch it out by hand or
use a flowchart maker or flowchart software to create a
flowchart that you can easily share with your team.
5. Confirm and refine your flowchart. Getting a second,
third, or even fourth set of eyes on your flowchart will
help you uncover bottlenecks or potential problems and
allow you to refine the flowchart before the process starts.

26
SAMPLES
 FLOWCHART FOR CONCRETE CASTING

FORM REBAR EMBEDDED SUBMIT

WORK WORK SERVICES CHECKLIST

NO
INSPECTI
ON

POUR ORDER YES

CONCRETE CONCRETE

28
 APPLY CONSTRUCTION QUALITY MAMAGEMENT
FLOWCHART

The Apply Construction Quality Management process changes depending on the Construction Project
Structure and Contract Type. Construction Quality Management Methodology recommends the assignment of a
Construction Quality Management Manager in the early phases of the Construction Project Management,
however, depending on the Size of the project and assigned Construction Quality Management Assets of an
organization, the activities of this process may be distributed to different Project Team members but in all cases,
to deliver Quality Results the Project Superintendent will assume responsibilities for work performance and
Project Manager is always accountable for Project Outputs!

29
30
 PRECONSTRUCTION PHASE

The Apply CQM Processes during the Pre-Construction Phase is to set the specifications, standards,
scope of Quality Requirements. They are generated from reviewing Contract Documents, Drawings and
Specifications to Update the Quality Manual and create a Site-Specific Quality Plan with appropriate
Checklists to Quality Control Work Performed. This might be a reiterative continuous quality improvement
cycle where changes are made due to new Design Bulletins, Substitutions, and/or Owner Requirements.

20XX PRESENTATION TITLE 31

 QA/QC
ASSIGNMEN
T
Apply CQM Process Flow Chart During Preconstruction Phase

Is the QP-003
project Per Approved
Self-Perform Review Contract
Self- Quality Manual,
Drawings and
Perform Prepare Site-
Specifications
or Specific Quality
CM/GC? Plan

CM Or
GC Obtain Quality
Manuals and Submit changes to
Quality Plans with A/E as RFI for
Review Contract QC Checklists from Approval
Requirement for Subs and Suppliers
QMS Process

QP-001 QP-002
Update Project Perform a Quality Review and
Quality manual and Orientation and Approve IWP for
Obtain Owner Introduction to each DFoW
Approval AWP

Once the requirement management process is completed, the subcontractors are instructed to provide an Installation Work
Package for each Definable Feature of Work. This is done during Quality Orientation and Advance Work Package Training.

32
 APPLY CONSTRUCTION QUALITY MANAGEMENT DURING
CONSTRUCTION PHASE

The Apply CQM is simplified to be customized to small projects as it is designed to be

expanded for a large project. Therefore, depending on the project size, the Quality Control
Checklists will provide further instruction for more extensive steps to be taken and forms to
be filled as the project requires. However, a c c o r d i n g to the flow chart below the most
important steps to consider in the Apply CQM process are the following:

o Set Requirements
o M o n i t o r C o o r d i n a t i o n o f wo r k t h r o u g h I n s t a l l a t i o n Wo r k P a c k a g e s
o Tr a c k S c o p e C h a n g e s t h r o u g h R F I s a n d S u b m i t t a l C o m m e n t s
o Hold Quality Preparatory Meetings to set CQM Expectations
o C o o r d i n a t e T h i r d - P a r t y Te s t i n g a n d I n s p e c t i o n s
o H o l d D a i l y P l a n o f t h e D a y M e e t i n g t o r e v i e w wo r k r e q u i r e m e n t s
o P e r f o r m Q u a l i t y I n s p e c t i o n s , Q u a l i t y Ta l k , Wa l k , a n d Vi s i t s
o R e p o r t a n d L o g Q u a l i t y Ob s e r v a t i o n s a s Q u a l i t y I n c i d e n t s o r N o n - C o n f o r m a n c e
o R e v i e w Te s t a n d I n s p e c t i o n R e p o r t s f o r m a j o r c o n c e r n s
o Follow up on Corrective Actions and Close Observation Reports
o R e p o r t Q u a l i t y - R e l a t e d Vi s i t s a n d Ac t i v i t i e s t o S t a k e h o l d e r s
33
 Review Submittals
QP-004
and RFIs for Scope
Upload Inspection
& Quality
Checklists or Create
Requirement
New in ProCore
Changes

Attend Scheduling QP-0007 QP-008

& BIM
Hold daily POD File a ProCore
Coordination
inspection Report on
Meetings for IWP Meetings with
the performed work
Development Foreman using the QC Checklist

Attend Scheduling
Would Quality
& BIM Observations
Coordination Require A/E
Meetings for IWP Input through
Development NO an RFI? YES

Attend Scheduling QP-010

QP-005 QP-009 File a Non-
& BIM Hold a Quality Conformance Report
Coordination Preparatory Meeting File a Quality incident
and close upon
Meetings for IWP two-weeks ahead of Reports and close upon Approval of the
completion of the work
Development stary of every IWP Corrective Action

Review and Collect

Perform Quality QP-006
Quality Assurance
QP-011
Talk, Quality Walk,
Test Reports,
Fabrication Visits, Coordinate a Third- Update QA/QC
As-builts, and
Factory Witness Party Testing and Documentations in
Commissioning
Test Inspections ProCore System
Documents

QP-012
Report Quality Related
Apply CQM flow chart – During Construction Phase Visits & Activities for
Weekly & Monthly 34
Progress Meetings
 As mentioned, this process is part of an integrated project delivery
mindset for a multilayered quality management system where supply
chain will perform their own Quality Control and GC will be the
Quality Assurance Party, and the Construction Team Quality Control
will be assured by Third Party to verify the CQM Implementation.
Periodic Quality Audits will be required from the CQM Director to
assure and verify that the Apply CQM Process is performed and
documented accordingly.

Closing the Apply CQM Process

The outcome of the Apply CQM Process would be to close every IWP
created for each DFoW. The closed IWP will be used in Project
Closeout Documentation and Project Knowledge Management Assets.
The performance of each Supply Chain entity will be evaluated in a
scorecard for the future prequalification process. The Outcome of this
process will be used as an input to the rest of CQM Implementation
Quality and Risk Management Processes as Business Intelligence
useful to the organization.
35
THANK YOU


36