My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
DELOITTE CONSULTING 1
Clerk
>
Contracts / Agreements
>
INACTIVE CONTRACTS (Originals Destroyed)
>
D (INACTIVE)
>
DELOITTE CONSULTING 1
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/3/2015 2:58:29 PM
Creation date
1/24/2005 10:53:19 AM
Metadata
Fields
Template:
Contracts
Company Name
Deloitte Consulting
Contract #
A-2004-245
Agency
Fire
Council Approval Date
11/15/2004
Expiration Date
6/30/2005
Destruction Year
2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
20
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
only effective when the four key threads are considered together. Technology must be planned and designed while <br />considering the business requirements that are driving the plan as well as how the eventual technology solution is <br />going to be owned, governed and funded. <br />When you undertake a technology planning project (especially in a multi -agency multi jurisdiction environment) <br />with full consideration of the business requirements, governance and funding, the resulting recommendations and <br />plan are realistic. They can be implemented in the environment in which they must exist, are structured in a way <br />that supports the business requirements and can be managed over the long term. <br />Scope of Work <br />Inside each of the phases of the project outlined in the methodology diagram above are a set of tasks that make up <br />the work. The following table outlines the tasks and proposed durations for each phase of work. <br />Task <br />Description <br />Duration <br />(Days) <br />Startup Activities <br />Meet with project <br />The project commences with meetings with the <br />1 d <br />management <br />client project management team to review the <br />workplan, schedule and deliverables outlined in <br />the proposal and confirm them. Where necessary, <br />required changes are identified. A key part of <br />these meetings is the determination of reporting <br />and communications protocols for the project. <br />Confirm project plan <br />Based on the outcome of the initial meetings and <br />2d <br />the actual start date of the project and staff <br />availability, the project plan is adjusted and the <br />finalized plan approved by the client project <br />managers. Meeting schedules are expanded <br />from the high level definitions in the project plan <br />and initial steps are taken to formally schedule <br />meetings and workshops. <br />Meet with 2-3 Key <br />Meetings are held with 2 to 3 key stakeholders. <br />2d <br />Stakeholders <br />These are likely to be dispatch center managers <br />and fire chiefs. These meetings allow for initial <br />confirmation of project goals and strategic <br />priorities and help shape that work in the coming <br />weeks. <br />Current <br />Assessment <br />Compile and Release <br />A survey questionnaire is compiled as a tool to <br />ld <br />Survey <br />assist in the interview and site visit process. It <br />provides a standard list of questions and outlines <br />the information to be gathered. The questionnaire <br />covers both the current situation as well as plans <br />for the future and integration requirements directly <br />associated with this project. The survey is sent <br />out to all project participants and they are <br />encouraged to complete as much of it as possible <br />in advance of the site visits and interviews. Man <br />13 <br />
The URL can be used to link to this page
Your browser does not support the video tag.