ZGANTT a Mechanized Gantt Software system
Mechanized Gantt is the name of the most modern Project Management system, Just like PERT and Critical
Path Method, are names of different system concepts. ZGANTT is our software version of the Mechanized
Gantt concepts.
The Mechanized Gantt system is a combination of PERT, CPM, Line of Balance, and Gantt, formed into
the most modern visual linear time status control system. It is a network in linear time. Because time is
linear at the base of the ZGANTT charts, we can link and layer to a Project’s sub-Projects. Multi Project
People workloads become visible. The Project Budget is a summation of people’s work time at burdened
rates, plus external purchases, and contracts. Project updates are superimposed on plan data, so that a
Project Manager can see the true status of the work. Status is maintained in Journals so a project
manager can look back at the project status historically. Time to completion is used to help managers
project projects end dates.
Project on time completion probability makes use of Monte Carlo assessment techniques. In this process,
each task that contains three estimates is put through a random time generator. Project time completion
simulations calculate the overall project and generate a Probability characteristic curve. Instead of
calculating a single completion time, all of the possible completion times are visible. A project manager
can negotiate realistic schedules with clients or senior management. The next few pages will show some
of ZGANTT’s features. When you have reviewed the data, we can discuss the cost of individual copies,
site licenses, and evaluation copies.
A Project Work Breakdown Structure (WBS)
ISD: Information System Development
1: Install System
2: Forms & Manuals
3: Alpha Tests
4: System Ready
Phase 1.1: System Study
1: Develop System Concepts
2: Concept Analysis
3: Market Analysis
4: Customer Focus
5: Select Optimum System
6: Quality Assurance Req.
7: Detailed Project Scope
Phase 1.4: System Cost Analysis
1: Software development Cost
2: Hardware Evaluation
3: Component Evaluation
4: Cost Analysis
Phase 1.7: Data Requirements
1: Customer Survey
2: Data Analysis
3: Market Study
4: Recommendations
5: Custommer Approval
Phase 1.2: System Design
1: S/W Evaluation
2: Document Control
3: Control Procedures
4: Develop Project Book
5: H/W Evaluation
6: System Proposal
Phase 1.5: Approval
1: Project Approval Report
2: Approval Meeting
Phase 1.8: Customer Data
1: Facility Survey
2: Regulatory Compliance
3: Permits
4: Env. Health & Safety
5: Certification Report
Phase 1.3: Evaluation of Vendors
1: Develop Vendor Lists
2: RFQ's
3: Vendor selection
Phase 1.6: Place Orders
1: RFQ from Vendors
2: Computer PO's
3: Order Special Computers
4: Input/Output Devices
5: Fabricate Parts
6: Assemble Units
7: Invoice Payments
8: Purchases Complete
Phase 1.9: Software Development
1: Develop System Algorithms
2: Simulate Graphics & Charts
3: Prototype GUI's
4: Customer Focus Meeting
5: Program in C++
6: Preliminary Debug
7: Alpha Test
8: Preliminary S/W Manual
9: Package S/W for shipment
Mid Project Status for ISD
Task
Dependencies
Aug Sep
1999
2000
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep
2001
Slack Days to
Oct Nov Dec Jan Feb days end
(Phase 1.1) : System Study
FS: 9/1/1999 12:00:00 AM
Steve Zukerman
Done Done
(Phase 1.2) : System Desig
FS: (Phase 1.1) 7: Detailed
Bill Williams
Done Done
(Phase 1.3) : Evaluation o
FS: (Phase 1.1) 3: Market A
Sam Spade
Done Done
(Phase 1.4) : System Cost
Anna Yung
FS: (Phase 1.1) 3: Market A
Done Done
(Phase 1.5) : Approval
Ham Herman
FS: (Phase 1.2) 6: System P
Done Done
(Phase 1.6) : Place Orders
FS: (Phase 1.5) 2: Approval
Sam Spade
70.2
88.6
(Phase 1.7) : Data Require
FS: (Phase 1.5) 2: Approval
David Naddor
-7.8
66.0
(Phase 1.8) : Customer Da
FS: (Phase 1.7) 3: Market S
Anna Yung
39.2
150.1
(Phase 1.9) : Software Dev
FS: (Phase 1.7) 5: Customm
David Naddor
-7.8
232.5
1: Install System
Lud Delmastro
FS: (Phase 1.8) - 1 month
39.2
185.6
2: Forms & Manuals
Liz Smith
FS: (Phase 1.7)
150.0 167.5
3: Alpha Tests
David Naddor
FS: (Phase 1.9)
-7.8
325.3
FS: 3: Alpha Tests
-7.8
325.3
4: System Ready
Today
Plan
TL plan
Actual
TL current
Projected
Dependencies
ISD, 15 February 2000 Budget Update
1999
Dollars Aug Sep
2000
Oct Nov Dec Jan Feb Mar Apr May Jun
Jul
2001
Aug Sep
Oct Nov Dec Jan Feb
$800,000.00
$700,000.00
Projected budget @
Project Completion
$600,000.00
$500,000.00
$400,000.00
$300,000.00
$200,000.00
$100,000.00
$0.00
Plan Material
Current Material
Plan Labor
Current Labor
Plan Total
Current Total
Today
ISD Project Department Histograms
1999
2000
Hours Aug Sep Oct Nov Dec Jan Feb Mar
Apr
May Jun
Jul
800.0
700.0
600.0
500.0
400.0
300.0
200.0
100.0
0.0
Today
IT
Engineering
Operations
Administration
Marketing
Finance
QA/QC
2001
Aug Sep Oct Nov Dec Jan Feb
Project Probability based on People Availability for ISD Project
Probability
September 2000
29
28
27
26
Tue Wed Thu Fri
30
Sat
2
1
Sun Mon
5
4
3
Tue Wed Thu
October 2000
9
8
7
6
Sat Sun Mon
Fri
12
11
10
Tue Wed Thu
13
Fri
100%
90%
80%
People are not working on
the weekend
70%
60%
50%
Work Ends @
5:00 PM
40%
30%
20%
Work Starts @
8:00 AM
10%
0%
Most likely
Project probable completion for
all paths ending by the middle
estimate of the Critical Path
Tell us the date that you would like to complete the project and we will tell you the probability of completing on
that date, with the resources assigned to this project, or tell us the probability that you feel comfortable with and
we will tell you the likely completion date.
14
Sat