NEW YORK DEPARTMENT OF TRANSPORTATION - PROJECT2
New York City Department of Transportation Project CHENSCAN
Milestone Two - Project Charter
Darian Hodge (Team Lead)
Ahmed, Riaz Uddin
Paredes, Aurelio
Patel, Dhavalkumar
Patel, Raj Maheshkumar
Philsidor, Jean
Keller Graduate School of Management
System Analysis, Planning, and Control
MIS-581-61261
Dr. Sunil G. Samanta
29 July 2015
Running head: NEW YORK DEPARTMENT OF TRANSPORTATION - PROJECT1
NEW YORK DEPARTMENT OF TRANSPORTATION - PROJECT7
TABLE OF CONTENTS
1Introduction
1.1Purpose of Project Charter
2project And Product Overview
3Justification
3.1Business Need
3.2Public Health and Business Impact
3.3Strategic Alignment
4Scope
4.1Objectives
4.2High-Level Requirements
4.3Major Deliverables
4.4Boundaries
5Duration
5.1Timeline
6BUDGET ESTIMATE
7Assumptions, Constraints And Risks
8.1Assumptions
8.2Constraints
8.3Risks
8 COMMUNICATION
9project Charter approval
APPENDIX A: cost breakdown
APPENDIX B: KEY TERMS
IntroductionPurpose of Project Charter
The CHENSCAN project charter documents and tracks the necessary information required by decision maker(s) to approve the project for funding. The project charter should include the needs, scope, justification, and resource commitment as well as the project’s sponsor(s) decision to proceed or not to proceed with the project. It is created during the Initiating Phase of the project.
The intended audience of the CHENSCAN project charter is the project sponsor and senior leadership.project And Product Overview
The New York City Department of Transportation Pavement Maintenance Operations (PMO) will proceed with a pilot program employing the CHENSCAN towed array in September of 2015 until August of 2016. The pilot program area will be located in Flushing, New York and will target specific problematic road surfaces. JustificationBusiness Need
An accurate survey of pavement conditions is lacking for the PMO. Consequently, materials, human capital, budgets, funds allocations, safety, and customer satisfaction are all below satisfactory standards. Public and Business Impact
CHENSCAN will benefit the public by providing timely and quality maintenance of pavements that ensure safe and comfortable driving conditions. Businesses will also benefit due to increased traffic and safer cargo carrying conditions.ScopeObjectives
The objectives of the CHENSCAN project are as follows:
· Provide accurate, real-time pavement surface analysis
· Provide interactive dashboard to harvest CHENSCAN data and make the data actionable
· Show substantial savings in cost and time for PMO pavement maintenance projects resource allocations. High-Level Requirements
Req. #
I Requirement Description
1
Secure PMO Senior Leadership Buy-in
2
Deploy CHENSCAN Team to the target area
3
Execute 12 month pilot program
4
Secure Senior Leadership Buy-in for the next four yearsMajor Deliverables
Major Deliverable
I Deliverable Description
CHENSCAN Towed Array
Pavement surface a.
EPANDING THE CONTENT OF AN OUTLINE using notes.pptx
NEW YORK DEPARTMENT OF TRANSPORTATION - PROJECT2N.docx
1. NEW YORK DEPARTMENT OF TRANSPORTATION -
PROJECT2
New York City Department of Transportation Project
CHENSCAN
Milestone Two - Project Charter
Darian Hodge (Team Lead)
Ahmed, Riaz Uddin
Paredes, Aurelio
Patel, Dhavalkumar
Patel, Raj Maheshkumar
Philsidor, Jean
Keller Graduate School of Management
System Analysis, Planning, and Control
MIS-581-61261
Dr. Sunil G. Samanta
29 July 2015
Running head: NEW YORK DEPARTMENT OF
TRANSPORTATION - PROJECT1
NEW YORK DEPARTMENT OF TRANSPORTATION -
PROJECT7
TABLE OF CONTENTS
1Introduction
2. 1.1Purpose of Project Charter
2project And Product Overview
3Justification
3.1Business Need
3.2Public Health and Business Impact
3.3Strategic Alignment
4Scope
4.1Objectives
4.2High-Level Requirements
4.3Major Deliverables
4.4Boundaries
5Duration
5.1Timeline
6BUDGET ESTIMATE
7Assumptions, Constraints And Risks
8.1Assumptions
8.2Constraints
8.3Risks
8 COMMUNICATION
9project Charter approval
APPENDIX A: cost breakdown
APPENDIX B: KEY TERMS
IntroductionPurpose of Project Charter
The CHENSCAN project charter documents and tracks the
necessary information required by decision maker(s) to approve
the project for funding. The project charter should include the
needs, scope, justification, and resource commitment as well as
the project’s sponsor(s) decision to proceed or not to proceed
with the project. It is created during the Initiating Phase of the
project.
The intended audience of the CHENSCAN project charter is the
project sponsor and senior leadership.project And Product
Overview
3. The New York City Department of Transportation Pavement
Maintenance Operations (PMO) will proceed with a pilot
program employing the CHENSCAN towed array in September
of 2015 until August of 2016. The pilot program area will be
located in Flushing, New York and will target specific
problematic road surfaces. JustificationBusiness Need
An accurate survey of pavement conditions is lacking for the
PMO. Consequently, materials, human capital, budgets, funds
allocations, safety, and customer satisfaction are all below
satisfactory standards. Public and Business Impact
CHENSCAN will benefit the public by providing timely and
quality maintenance of pavements that ensure safe and
comfortable driving conditions. Businesses will also benefit
due to increased traffic and safer cargo carrying
conditions.ScopeObjectives
The objectives of the CHENSCAN project are as follows:
· Provide accurate, real-time pavement surface analysis
· Provide interactive dashboard to harvest CHENSCAN data and
make the data actionable
· Show substantial savings in cost and time for PMO pavement
maintenance projects resource allocations. High-Level
Requirements
Req. #
I Requirement Description
1
Secure PMO Senior Leadership Buy-in
2
Deploy CHENSCAN Team to the target area
3
Execute 12 month pilot program
4
Secure Senior Leadership Buy-in for the next four yearsMajor
Deliverables
Major Deliverable
4. I Deliverable Description
CHENSCAN Towed Array
Pavement surface analyzer with real-time data upload
CHENSCAN Data Analysis Software
Graphical and numerical representations of pavement surfaces
with required resource analysis for maintenance Boundaries
CHENSCAN and the CHENSCAN software package are used as
an interactive, real-time, diagnostic platform that precisely
maps road surfaces to within two millimeters and then leverages
that data to allocate resources e.g. human capital, materials,
funding, and budget plans. CHENSCAN is not designed to be
used vertically, over non-traffic areas, over liquid, or biological
constructs. DurationTimeline
Budget estimateDuring the 12 month program, CHENSCAN will
cost PMO $1,505.332. Years two and three will be identical in
cost with years four and five increasing by 2% to $1,535,429.
Please see Appendix A. Assumptions, Constraints And
RisksAssumptions
1. CHENSCAN will collect onsite data and upload directly to
the CHENSCAN data analysis software on PMO provided IT
platforms.
2. It is also assumed the PMO will also indemnify CHENSCAN
operations overall for the entirety of the pilot phase.
Constraints
This section identifies any limitation that must be taken into
consideration prior to the initiation of the project.
1. Senior leadership buy-in is key to this project and the PMO’s
budget is highly constrained at present.
2. Startup costs not borne by the PMO will be $65,000 to create
the three prototypes for the project.Risks
Risk
Mitigation
Traffic Congestion
Conduct Operations at non-peak times
5. Data Loss
Provide Multiple Communications Redundancies
Software Incompatibilities
Provide joint team of PMO and CHENSCAN software experts to
address problems
Force Majeure
Prepare alternate timelines and schedule in the event of natural
disasterscommunicationStakeholders (Internal and External)
1. Internal stakeholders will consist of senior PMO
management, New York City Department of Information
Technology (DOIT), New York City Police Department
(NYPD), and the Mayor’s Office of Technology and Innovation.
2. External stakeholders include the public of New York City
specifically Flushing, and investors.
project Charter approval
The undersigned acknowledge they have reviewed the project
charter and authorize and fund the CHENSCAN project.
Changes to this project charter will be coordinated with and
approved by the undersigned or their designated representatives.
Signature:
Date:
Print Name:
Bill DeBlasio
Title:
Mayor
Role:
Senior Champion
7. APPENDIX A: COST BREAKDOWN
APPENDIX B: KEY TERMS
The following table provides definitions for terms relevant to
this document.
Term
Definition
CHENSCAN
Towed pavement condition assessment array
CHENSCAN Analysis Software
Analyzes data from the CHENSCAN device to provide
actionable information for resource planning and allocation
Pavement
Road surfaces used by normal vehicles within an urban setting.
IT Platform
Information Technology hardware and communications
equipment
8/1/20158/31/20169/1/201512/1/20153/1/20166/1/20168/1/2015
SENIOR LEADERSHIP BUY-IN9/1/2015DEPLOY CHENSCAN
TEAM11/30/2015 - 4/30/2016WINTER INTERVAL9/2/2015 -
11/29/2015PHASE ONE DATA COLLECTION5/1/2016 -
7/31/2016PHASE TWO DATA
COLLECTION8/3/2016PRESENT FINAL ANALYSIS TO
SENIOR LEADERSHIP10/29/2015PRESENT PHASE ONE
ANALYSIS TO SENIOR LEADERSHIP
7/1
12/30
9/1/2015
12/1/2015
10. New York Department of Transportation - Project Management
Improvements
Milestone One
Darian Hodge (Team Lead)
Ahmed, Riaz Uddin
Paredes, Aurelio
Patel, Dhavalkumar
Patel, Raj Maheshkumar
Philsidor, Jean
Keller Graduate School of Management
System Analysis, Planning, and Control
MIS-581-61261
Dr. Sunil G. Samanta
19 July 2015
Running head: NEW YORK DEPARTMENT OF
TRANSPORTATION - PROJECT1
NEW YORK DEPARTMENT OF TRANSPORTATION -
PROJECT8
Abstract
This paper postulates the New York Department of
Transportation (NYDOT) is ineffective in how it approaches
maintenance and repair of city streets. After an analysis of how
11. the NYDOT executes maintenance and repair of city streets, a
solution will be proffered to ensure NYDOT’s projects
execution ensures proper funds allocation, staffing, and
timeliness while observing cost effectiveness, efficiency, and
needs-based prioritization.
NEW YORK DEPARTMENT OF TRANSPORTATION -
PROJECT3
New York Department of Transportation - Project Management
Improvements
Business Problem Statement
New York City infrastructure repair and inspection insofar as
street maintenance is concerned, is seemingly haphazard. For
the purpose of the project, from now on to be known has
“Smooth Travel”, the geographic scope will be confined to the
borough of Queens, Blocks 4971 to 4978.
For the New York City Department of Transportation (DOT) to
maintain and repair streets properly, they must have specific
information (NYCDOT, 2015, p. 34-38). For example, they
need to know the available funding, project scope, conceptual
design, stakeholders involved, and other considerations. These
facets of project management are common regardless of what is
being done. What is apparently lacking for DOT, as a
technological challenge, is real-time awareness of street
conditions. This is essential information so projects can be
scoped, funded, assigned, and tracked.
Project Goal
To provide real-time street conditions, the DOT cannot simply
send teams around to the five boroughs or even our target area.
Cameras cannot reveal the necessary three-dimensional data
required and neither can a worker without closing down the
street. What we propose is a towed array of sonic imagers
known as CHENSCAN (xxx, 2015). These imagers will be
affixed to city vehicles including buses, street sweepers, NYPD,
and NYDOT vehicles. The three-dimensional data will be
12. uploaded via satellite link and downloaded to a central image
repository that will display a constant update of the road
surface.
Business Requirements
Context Level Data Flow Diagram
Figure 1
Figure 2
Use Case List
Scoping (1–4 Months)
DOT plans and designs its projects internally. To plan a project,
agency teams conduct site visits, chat to stakeholders and
collect applicable information, which characteristically includes
some or all of the following (NYDOT, 2015):
1. Crash data
2. Traffic speeds
3. Pedestrian, bicycle, and motor vehicle volumes
4. Turning-movement counts
5. Parking utilization
6. Contextual information, particularly local land uses, parking
regulations, bus/truck route information, etc.
7. Inventory of present infrastructure, including fire hydrants,
drains, manholes, sidewalks curbs, and curb cuts, etc.
8. Initial design concepts often materialize from initial data
13. collection and information from stakeholders.
Design (6–12 Months)
DOT studies the project site and creates a base map to record
existing conditions. Agency teams then design improvements
according to the project goals. DOT may also collect additional
information should other nearby intersections in need of
modification.
DOT checks with Fire Department New York (FDNY) to
address any apprehensions about the influence of the designs on
its operations. DOT also presents the initial concepts to the
applicable community board and elected officials for input. If
the project is a major transportation project, the New York City
Police Department (NYPD) may also be consulted. Other
considerations may lay with the Department of Small Business
Services, Mayor’s Office for People with Disabilities and the
Department of Sanitation (DSNY) when a design will plainly
impact its operations.
Implementation (2–90 Days)
Once a project design is finished, the applicable DOT
component and/or outside contractors commence the project.
The work season is usually between mid-April and mid-
November.
After the project is completed, DOT personnel monitor and
study crash data at the project site for up to three years. DOT
also compares pre- and post-implementation motor vehicle,
bicycle, and pedestrian data to measure any impact the project
had on mobility. Should an issue arise, DOT may go back to the
project to make changes.
Use Case Diagram
Figure 3
Use Case Scenario
In figure 3, we see a communicative relationship between DOT
14. and action of inspecting and maintaining the streets. The
implication here is that DOT has the sole responsibility to do
this and is also liable for any outcomes. We also see, in the
next diagram in figure 3, inclusive relationships. This describes
the situation where maintenance and repair contain behaviors
that are common (Kendall 33) like funds, design, and scope. In
the generalization model, we see that Citizen Safety generalizes
DOT. In other words, the major set is Citizen Safety and the
sub-set, here, is DOT. The last diagram in figure 3 shows the
extension relationship. Here the one use case, Stakeholders,
possesses the behavior that permits the new use case, Design, to
handle a variation or an exception from the Stakeholders.
(Kendall 33)
References
Kendall, Kenneth E., Julie Kendall. Systems Analysis and
Design, 9th Edition. Pearson Learning
Solution
s, 01/2013. VitalBook file.
NYDOT. (2015). Street Design Manual [City Guide]. New York
City: New York City Department of Transportation.
Context Level Data Flow DiagramDiagram 0 (Current
Process)NYDOT INSPECTOR OR OTHER CITY
AGENCYCITIZENRYCOMMUNITY BOARDDesign (6–12
Months)Consult with FDNY, NYPD, the Department of Small
Business Services, and the Mayor͛ s Office for People with
Disabilities, The Department of of Sanitation
(DSNY)Implementation (2–90 Days)Scoping(1–4 Months)
15. NYDOT
Context Level Data Flow Diagram
Diagram 0 (Current Process)
NYDOT
INSPECTOR OR OTHER CITY AGENCY
CITIZENRY
COMMUNITY
BOARD
Design (6–12 Months)
Consult with FDNY, NYPD, the Department of Small Business
Services, and the Mayor’s Office for People with Disabilities,
The Department of of Sanitation (DSNY)
Implementation (2–90 Days)
Scoping
(1–4 Months)
D1
Crash data
Traffic speeds
Pedestrian, bicycle, and motor vehicle volumes
D2
creates a base map to establish existing conditions
D3
Monitor and analyze crash data up to three years, compare pre-
16. and post-implementation motor vehicle, bicycle, and pedestrian
data
Context Level Data Flow DiagramDiagram 0 (Improved
Process)Design (6–12 Months)Consult with FDNY, NYPD, the
Department of Small Business Services, and the Mayor͛ s Office
for People with Disabilities, The Department of of Sanitation
(DSNY)Implementation (2–90 Days)Scoping(1–4
Months)D1Real TimeSurface ConditionsNYDOT INSPECTOR
OR OTHER CITY AGENCYCOMMUNITY BOARDSTREET
SURFACE ANALYSIS PLATFORM
NYDOT
Context Level Data Flow Diagram
Diagram 0 (Improved Process)
Design (6–12 Months)
Consult with FDNY, NYPD, the Department of Small Business
Services, and the Mayor’s Office for People with Disabilities,
The Department of of Sanitation (DSNY)
Implementation (2–90 Days)
Scoping
(1–4 Months)
D2
Crash data
17. Traffic speeds
Pedestrian, bicycle, and motor vehicle volumes
D3
creates a base map to establish existing conditions
D4
Monitor and analyze crash data up to three years, compare pre-
and post-implementation motor vehicle, bicycle, and pedestrian
data
D1
Real Time
Surface Conditions
NYDOT
INSPECTOR OR OTHER CITY AGENCY
COMMUNITY
BOARD
Street Surface Analysis
Platform
DOTINSPECT &MAINTAIN STREETSCOMMUNICATES
RELATIONSHIPMAINTAIN &REPAIR STREETSGET
FUNDSDEFINE
SCOPEDESIGN<<include>><<include>><<include>>DOTCITI
ZENSAFETYGENERALIZESDOT'S
MOTIVATIONDESIGNSTAKEHOLDERS<<extend>>STAKEH
OLDERSPROVIDE INPUT