|
|
|
|
|
Pr
Project Tracker
|
|
Case
Study – Custom Project Tracking Software By
Vikrant Nadkarni, |
|
Scadex Business
Solutions, LLC |
|
Ewing Engineers |
|
Background: Ewing Engineers is an Engineering
contractor doing electrical and construction projects for
several large companies. Some of their customers include,
Merck Pharmaceuticals, NASA and Averon. At one point in time
B&D works on 20 running projects, with an approximate
total budget of 50 million dollars. Apparently, there is no
system in place, which keeps track of several project
variables before Scadex built their Project Management
software.
Problem: Growing business and increasing number of
projects made it difficult to manage several projects at a
time. The senior executives wanted to keep track project
profitability. The project manager wanted to keep projects
under budget, which includes keeping track of project
invoices, project receivables, employee time and project
changes.
Scope: Build an automated system for project management purposes.
The system will incorporate all the processes over the period of a
project’s life. This includes, writing a proposal, tracking the rejected
proposals, converting an accepted proposal into a project, tracking
several project specific variables (payables, receivables, change orders,
PO, invoices, and scheduling) and finally, making decision support tools
and generating reports. The output should facilitate decision-making abilities for
the project managers and senior executives. The output will have queries
and reports with drill-down capabilities. The database should be in
3NF and it should maintain referential integrity, for example, it should
block a creation of a receivable against a project, which does not exist
in the project database. The software should be error proof and it should have
all necessary error checks.
The interface should be intuitive and user friendly. Also, create
the security features as addressed in the Security section.
| | |
Solution: Scadex analysts were sent to the Corporate Headquarters of Ewing Engineers, based in Exton, PA. We conducted business
analysis, interviewed key users. The user needs and requirements were
carefully assessed. The requirements document was made, and a relational
database was created in compliance with standard database modeling
methods. The IT staff of EE then approved the
designs and flowcharts. All the requirements were
sent to our development center. Our highly skilled developers and Software
Engineers built EE Project Management Software. The software was
carefully tested for every detail and parallel prototype was launched.
After, the test phase was completed and necessary modifications were done,
the old system was replaced with our New Project Management system. The
following flowchart describes a high level overview of the
process.
|
| |
| Project Management Flow
Chart |
 |
| Click Here for a
clear view |
| PM Software Features: |
|
Customized – Interface and Industry Specific Vocabulary |
|
Project Centric |
|
Output Compatibility – Payroll, Accounting, and Finance
programs |
|
Access Database and Visual Interface
|
|
Graphs functions |
|
Scheduling functions |
|
Time line, Activity Diagrams, Critical Path
|
|
Decision-making functions and drill-down capabilities. The
following screen-shot is an example of drill-down capabilities. The users
can select “All” or “Specific” project with a specified time period.
Further he / she can specify a category and get a detailed report on the
final selection. |
|
|
|
Sample output Screen |
 |
| Click here For
a clear view |
|
Time and Cost:
Activity |
Weeks |
Man Hours |
Rate/hr |
Extended |
|
Requirements Definition ®
|
1 |
40 |
$ 100 |
$ 4,000 |
|
Design ® |
1 |
40 |
$ 100 |
$ 4,000 |
| |
|
|
|
|
|
Development ® |
3 |
120 |
$ 50
|
$ 6,000 |
|
First Version and Testing ®
|
2 |
80 |
$ 50
|
$ 4,000 |
|
Final Version ® |
½ |
20 |
$ 50
|
$ 1,000 |
|
Documentation and Manual
|
2 |
80 |
$ 20 |
$ 1,600 |
Total |
9½
|
380 |
|
$ 21,600
(Taxes not Included)
|
®
= Required Activity
Note:
The rate and time are approximates for information purposes. They may
change depending upon the nature of projects. |
|
|
|