Digitization of processes involved in one cycle time in

construction industry

Mayur Ghanavat 199278034

Bratati Das 199278044
Puneet Srivastava 199278077
Richa Sharma 199278093
 Vision and Goal
Vision of the project is to digitalize and integrate verification and checklist
processes of one cycle time in a residential construction industry

Goals:
• Formulate a system that has less dependency on manual work and can be accessed from
various locations without a need to be physically present at site
• Ensure transparency in the end to end system of verification which involves multi
department co-ordination and reporting to client
• Eliminate time lags between processes by putting in place a robust application that updates
checklist verifications in real time so that handovers between departments is smooth
• Formulate a system that helps in efficient record keeping of processes that is not
lost/damaged during project progress
 Scope of Work: Process flow

Project Scheduling Project allocation Pre Pour Checklists Quality Checks

Project manager will Site engineer Project starts. Site Finally Quality dept
make a work allocates himself to engineer sends approves checklist on
breakdown structure particular project and inspection requests to app and notification
and schedule and notifications are sent safety department is sent to client and
upload on to formwork and which happens at the batching plant to
application. reinforcements start. Post “safe to decide on the amount
Notification of this department for pre start card” update, of concrete. Post pour
will be sent to project prep. Once formwork, checklist is also
formwork, done, they approve reinforcements and approved by quality
reinforcements, project start on the MEP and sent to client for
safety, MEP, application (mech,elec&plumb) final verification
plumbing update checklists
Scope of Work: Stakeholders
Key Stakeholders Description
Project Manager Plans the schedule of the project
and work breakdown structure
Department Head Each department has its head who
can view updates of all engineers in
that department
Site Engineer As representative of execution
department, they co-ordinate
checklists with other departments
and monitor work progress on site
Department Engineer Safety, MEP, Quality all have their
respective engineers for inspection
Client Builders for whom construction
would be done
Batching Plant Engineer Concrete pouring is done by them
Scope of Work: Software/Hardware

Software Requirement
OS Microsoft® Windows® 8/7/10(64-bit) ,
MacOS( Elcaption )

Android SDK 24.4

Web Server Apache Tomcat

Database MySQL Server

IDE Windows Eclipse, Android Studio

IDE MacOS Xcode (Programming Language – Swift/Objective C)

Virtual VMware vSphere 4.0

Infrastructure

Front End UI Jboss, Xamp v3.2.1 MySQL Workbench

Back End Web App Jboss, Xamp v3.2.1 MySQL Workbench

Dev

Cloud Hosting Amazon Web Service

Scope of Work: Software/Hardware

Hardware Requirement
RAM 8 GB

Hard-Disk Space 15 GB

Processor (CPU) Intel i5 -6xxx or equivalent

Screen Resolution 1600 x 900 or better

Network Adapter 802.11ac 2.4/5 GHz wireless adaptor

Device (for Testing) IPad, IPhone 4 and above, Android

Devices of different resolution
 Functional Requirements
Login – View rights of all department engineers given to department head so that at any
point he can monitor project clearances at each site. Each department engineer has
access to update and approve checklists of his department for all his allotted projects.
Site Engineer has rights to send requests to each department.

Scheduling Project – Project manager updates the project schedule and work
breakdown structure and overall timeline on the app. He also allocates a site engineer to
the project.

Checklist Update and Approvals – Before Project start, formwork, reinforcements and safety
update their pre project checklists, post structure formation, formwork, reinforcements and
MEP update and approve their checklists post which quality updates its pre pour checklist
which is then send to batching plant and finally post pour checklists are updated and sent to
project manager as well as client
 Non functional requirements

Accessibility Transparency Performance Security Reliability

• Mobile application • The app should be • Database queries
should be accessible visible to leadership,
on personal phones department heads,
on personal project managers.
networks so that • Any changes made
engineers aren’t by any department
required to be to the workflow
present on site to should be visible to
approve and send others • Throughput of the
to next department • Different users have
different login
access like view/
edit etc
• Records cannot be • 99% uptime of
should be real time tampered with and application
and updation of data integrity across • Application should
checklists should be all sites and projects
not crash under
sent as notifications should be
multiple
to respective maintained
simultaneous logins
departments • Login access to
immediately • Application should
Project manager,
be able to work
leadership,
decently well under
app should be able department heads
moderate networks,
to support around and engineers,
since connectivity is
500 users logged in clients should all
not always strong in
at a time have different sets
construction sites
of access
 Statement Of Work
Project analysis slide 7
Detailed deliverables list (Work Intermediate deliverables Referred Task in Estimated Efforts
Product) Project schedule involved

Design
Design Workflow  Integrated design

Data Architecture Design  Database schema design Design 54 days

 Data Collection
Design 34 days
Data Processing System Design  Source target mapping
 ETL processing
 SSIS
 MSSQL
Development 20 days
Automation System Design  Job Processes
 Custom Scripting
 Service Development
Core mobile client application  Front end design
Development 10 days
design 
 Add new checklist Development
System Administration Design 10 days
 Manage users

9
 Work break down structure
Project analysis slide 7
Requirement Developmen
Design Testing / QA Deployment Maintenance
s Analysis t
3.1 Database
2.1 Data 4.1 Create Test 5.1 Create 6.1 Create Training
1.1 Project Scope architecture
architecture design Cases Contingency Plan Modules for users
Creation
2.2 Design
1.2 Stakeholder's 3.3 App 5.2 Signoff from all 6.2 Bug Fix after
Application for 4.2 Unit testing
Identification Development stakeholders deployment
Android and iOS
1.3 Joint
6.3 Identify
Requirement 2.3 Technical 3.4 Integration 4.3 Integration 5.3 Deployment resources to
Development(JRD) design document Development Testing
support the system
sessions
1.4 Identify key 2.4 Flow of 4.4 User 6.4 Regular Health
milestones processes Acceptance Testing check of system

1.5 Create Use

2.5 Reports layout 4.5 Bug fixing cycle
cases
1.6 Infrastructure
Requirement
Analysis
1.7 Software
Requirements
Specification(SRS)
document
10
 Individual effort estimation
(Using Delfi Estimation)

Project analysis slide 7

Name
Goal Statement
XYZ
Estimation of time for the digitalization of process  
Date
Units
29-09-2020
Days
 
WBS# Task Name Initial Est. Delta 1 Delta 2 Delta 3 Delta 4 Final Assumptions
1 Project Scope 10 2         Availability of Stakeholder
2 Stakeholder identification and requirement 15 3          
Requirements from stakeholders are
3 Create Use cases 10 1         clear
4 Infrastructure requirement analysis 5 5          
5 Software requirement specification 10 2          
6 Design Workflow 20 3          
7 Application design 20 4          
8 Database architecture design 15 -1          
9 Database architecture creation 20 2          
10 Application development 20 -1          
11 Integration Development 15 3          
12 Testing 10 3         Development on Time
13 Deployment 3 1          
14 Maintenance 8 -2          
 
  Delta   25  
  Total 181 206  

11
 Assembled effort estimation
(Using Delfi Estimation)

Project analysis slide 7

Name A,B,C,D
 
Date 29-09-2020
Goal Statement Estimation of time for the digitalization of process Units Days
 
Best Worst Averag
WBS# Task Name A B C D Notes
case case e
1 Project Scope 10 12 8 10 8 12   Availability of Stakeholder
2 Stakeholder identification and requirement 15 17 13 17 13 17    
Clear requirements from
3 Create Use cases 10 9 10 11 9 11  
stakeholders
4 Infrastructure requirement analysis 5 6 5 7 5 7    
5 Software requirement specification 10 12 14 9 9 14    
6 Design Workflow 20 18 17 23 17 23    
7 Application design 20 24 21 20 20 24    
8 Database architecture design 15 11 14 13 11 15    
9 Database architecture creation 20 20 18 19 18 20    
10 Application development 20 18 16 15 15 20    
11 Integration Development 15 14 12 6 6 15    
12 Testing 10 9 11 10 9 11   Development on Time
13 Deployment 3 4 6 8 3 8    
14 Maintenance 8 9 7 6 6 9    
 
  Delta                
  Total 181 183 208 233        
12
 Personnel Billing
Project analysis slide 7
Weekly Resource Requirement
Salary per Total(Man-
Project Team Cost per week Cost to project
annum(in Rs) Weeks)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Project Manager ₹ 18,00,000 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 24.0 ₹ 34,615.4 ₹ 8,30,769.2

Project Leader ₹ 10,00,000 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 24.0 ₹ 19,230.8 ₹ 4,61,538.5

Analysts ₹ 8,00,000 1.0 1.0 1.0 1.0 1.0 1.0 0.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 19.0 ₹ 15,384.6 ₹ 2,92,307.7

Programmers ₹ 5,50,000 2.0 2.0 2.0 2.0 2.0 2.0 5.0 5.0 5.0 5.0 5.0 4.0 2.0 2.0 1.0 1.0 1.0 1.0 1.0 50.0 ₹ 10,576.9 ₹ 5,28,846.2
 
System-testers ₹ 4,50,000 2.0 2.0 2.0 2.0 2.0 2.0 4.0 4.0 4.0 4.0 4.0 4.0 2.0 2.0 1.0 1.0 1.0 1.0 1.0 45.0 ₹ 8,653.8 ₹ 3,89,423.1

Total ₹ 46,00,000     Total ₹ 25,02,884.6

13
 Client Billing
(Using Delfi Estimation)

Project analysis slide 7

Project Team Client Billing(₹) Efforts in Man-Weeks Total Billing(₹)
Project Manager 1400 19 1064000
Project Leader 1190 19 904400
Analysts 910 14 509600
Programmers 840 45 1512000
System-testers 770 40 1232000
Total     5222000

Customer Support
Software Technical Support 910 4 145600
Infrastructure Support 1470 4 235200
Total     380800

Software Tools
Operating System 700 per 5 users 6500
Database 5000 per 15 users 19500
Others 50% of OS cost 3250
Total   29250

Total(₹)     5632050

14
Work Schedule & Resource
Working
 USE CASE 1
Project analysis slide 3
Name Progress Monitoring

Summary Progress of the project can be monitored at different levels from PMs, to site engineers

Rationale Instead of calling each site engineer individually for individual progress, management can get a centralized progress report daily, weekly and
monthly and can directly compare it with scheduled objectives through in app tools. Site Engineers can track their progress against work
schedule
User Project Manager, Department Heads, Site Engineer,Client

Precondition 1. All staff should have their accounts on the app

MARKET TECHNICAL FINANCIAL ECONOMIC ECOLOGICAL
2. Site Engineers should update their progress reports periodically and correctly
ANALYSIS ANALYSIS ANALYSIS ANALYSIS ANALYSIS
Basic course of 1. User create account and enters the necessary credentials like name, mail id, phone number, employee ID etc.
action 2. Based on the clearance given to the employee, progress can be monitored
Lorem ipsum dolor
3. sit
ManagementLorem
willipsum dolor to
have access sit reports Lorem
of wholeipsum dolor sit
site, Department HeadLorem ipsum
will have dolor
report sit for their
access Lorem ipsum dolor
department sit
and site
amet, consectetur engineers foramet,
theirconsectetur
area. amet, consectetur amet, consectetur amet, consectetur
Alternateadipiscing
Path elit,Manual
sed dotracking adipiscing
using tools elit,
like sed
Exceldocan be done adipiscing
by takingelit,individual
sed do inputs from
adipiscing elit, sed and
site engineers do then can adipiscing elit,and
be collated sedcirculated
do
eiusmod tempor eiusmod tempor
among themselves on daily basis. eiusmod tempor eiusmod tempor eiusmod tempor
incididunt
Post Condition ut labore et Tracking
Centralized incididunt
can beutdone
labore et any discrepancies.
without incididunt ut labore et incididunt ut labore et incididunt ut labore et
dolore magna aliqua. dolore magna aliqua. dolore magna aliqua. dolore magna aliqua. dolore magna aliqua.
 USE CASE 2
Project analysis slide 3
Name Record Keeping

Summary Physical records can be eliminated saving considerable costs and efforts at the same time bringing enhanced transparency.

Rationale For every concrete process, there are on an average 5 checklists, resulting in huge inventories of records which are expensive to hold and
maintain but is also susceptible to tempering. All this cost and efforts can be saved by having a centralized database in which the records
can be stored directly form the app.
User Internal and External Audit Teams, Site Management

Precondition 1. No concrete shall be done without following SOP including the app.
MARKET TECHNICAL FINANCIAL ECONOMIC ECOLOGICAL
2. Batching of concrete shall be done only after getting all necessary authorization from the app
ANALYSIS ANALYSIS ANALYSIS ANALYSIS ANALYSIS
Basic course of 1. Site Engineer fill the respective checklist properly before raising request to respective department
action 2. Upon authorization, checklist will be saved in a central database
Lorem ipsum dolor
3. sit
While doing Lorem ipsum
audits, dolor
records cansitbe fetched
Lorem
fromipsum
centraldolor sit with convenience
database, Lorem ipsumand dolor sit
maintaining Lorem
the ipsum
integrity of dolor
data sit
amet, consectetur
Alternate Path amet, in
Checklists can be stored consectetur amet,
hard copies in designated consectetur
rooms. amet, consectetur amet, consectetur
adipiscing elit, sed do adipiscing elit, sed do adipiscing elit, sed do adipiscing elit, sed do adipiscing elit, sed do
Post Condition Ease of creating, maintaining
eiusmod tempor and fetching the dataeiusmod tempor
eiusmod tempor eiusmod tempor eiusmod tempor
Integrity
incididunt ut labore et of the data is ensured
incididunt ut labore et incididunt ut labore et incididunt ut labore et incididunt ut labore et
dolore magna aliqua. dolore magna aliqua. dolore magna aliqua. dolore magna aliqua. dolore magna aliqua.
 USE CASE 3
Project analysis slide 3
Name Placing order in Batching Plant

Summary The quantity of concrete required can be calculated in-app and can be directly notified to the batching plant present.

Rationale 1. Huge time saving can be achieved if batching plant can be directly notified instead of taking slip the concrete requirement in person.
2. Concrete quantity can be calculated using in app algorithms eliminating the scope of human error.
User Batching Plant, Site Engineer

Precondition All previous checklists should be authorized before placing order for concrete

Basic course ofMARKET

1. TECHNICAL
Upon authorization of pre concrete checklists,FINANCIAL
shape and dimensions shouldECONOMIC ECOLOGICAL
be given as input by site engineer
action ANALYSIS
2. ANALYSIS
App will calculate ANALYSIS
the amount of concrete required ANALYSIS
and notify the batching plant of the same ANALYSIS
3. Batching Plant will notify the site engineer upon dispatch eliminating waiting time and risk of segregation
AlternateLorem
Path ipsum dolor
Calculating
sit the quantity manually
Lorem ipsum andsitcarrying Lorem
dolor the slip ipsum
physically
dolorto batching
sit plant
Lorem ipsum dolor sit Lorem ipsum dolor sit
amet, consectetur amet, consectetur amet, consectetur amet, consectetur amet, consectetur
Post Condition Time saving and wastage elimination for concrete
adipiscing elit, sed do adipiscing elit, sed do adipiscing elit, sed do adipiscing elit, sed do adipiscing elit, sed do
eiusmod tempor eiusmod tempor eiusmod tempor eiusmod tempor eiusmod tempor
incididunt ut labore et incididunt ut labore et incididunt ut labore et incididunt ut labore et incididunt ut labore et
dolore magna aliqua. dolore magna aliqua. dolore magna aliqua. dolore magna aliqua. dolore magna aliqua.
 USE CASE 4
Project analysis slide 3
Name Resource Monitoring

Summary Summary of workforce and machinery distribution can be accessed through app by department heads to optimize the distribution

Rationale Often specialized workforce and machinery is limited, hence, to ensure optimum utilization of both, it is necessary to keep track of their
distribution on the site. App can provide a single stop allocation reports to the department heads and site management.
User Department Head, Site Management

Precondition All site engineers should fill in correct numbers of workmen required in their areas

Basic course ofMARKET

1. TECHNICAL
Department Heads FINANCIAL
will have a daily report about ECONOMIC
their resource allocation which ECOLOGICAL
they can download directly and can use the same to
action ANALYSIS ANALYSIS
plan for the future. ANALYSIS ANALYSIS ANALYSIS
2. Generally hiring and firing cost for both workforce and the machinery is substantial hence, proper planning can be done using in-app
features. Lorem ipsum dolor sit
Lorem ipsum dolor sit Lorem ipsum dolor sit Lorem ipsum dolor sit Lorem ipsum dolor sit
Alternate Path Coordinating
amet, consectetur with every site engineer
amet, consectetur individually and keeping track
amet, consectetur using tools like excel.
amet, consectetur amet, consectetur
adipiscing elit,Better
Post Condition sed do adipiscing
optimization elit, resulting
if resources sed do in better
adipiscing elit, sed do
efficiency. adipiscing elit, sed do adipiscing elit, sed do
eiusmod tempor eiusmod tempor eiusmod tempor eiusmod tempor eiusmod tempor
incididunt ut labore et incididunt ut labore et incididunt ut labore et incididunt ut labore et incididunt ut labore et
dolore magna aliqua. dolore magna aliqua. dolore magna aliqua. dolore magna aliqua. dolore magna aliqua.
 Risk & Challenges
Project analysis
Connectivity slide 6Training Complacency
Usually the construction sites are Users needs to be trained to Managers might approve the
in remote location and app work on the application checklist, without visiting the site
might not function in case of
poor connectivity.

User adoption Power backup

Moving employees from Phone with long battery lives are
traditional to digital platform. required as the application
would be required through out
the day.
 Change Management
System
Deployment
• System deployment will include
installation and commissioning
of hardware and software
systems, as well as developing
the new procedures
• Configuration and deployment of
database structures and tools
that will use the database.
• Configuration of apis for taking
and uploading photographs for
various approvals.
• Configuration of various services
needed for the installation of the
tool on actual devices.
Documentation of the data and changes done is equally important during the process of change management.
Change
Management
•Current policies and procedures
and even management practices
may need to be modified to
facilitate the adoption of the
new system.
•People tend to resist change
because familiar practices will
become obsolete  ‐ there is
anxiety about unknown factors
such as the impact of the new
system
•Management should be sensitive
to those problems. New
management practices may
involve new divisions of labour
or coordination and
communication with multiple
stakeholders
Training
• Users need to receive training on
technical operations of the
system and basic information
about the system
• Training of various options in an
app that will cater to various
functions at once.
• It is also essential to provide
users with practical training so
that they will have hands‐on
experience in using the new
system and the changed process
Rollout
• Obtain Technical approvals for
Go-Live.
• Obtain Management approval
for Go-Live.
• Presence of implementation
team members during early days
of launch.
• Training to deal with
unanticipated or unresolved
questions after the Go-Live.
 Benefit Analysis
Benefits
• Tracking ability for the management.
• Reliable and accurate database.
• Time saving in execution of tasks.
• Reduction in Time Lag/Delay.
• Environment Friendly.
• Removal of Interdependency.
• Easier to develop an analytics platform
to monitor the data.
Concerns
• Stable Network infrastructure is
needed.
• Battery and power backup is needed.
• Need to handle employee resistance in
adopting to the new technology.
Thank You