Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Prepared by: Ian Baldwin Standards Policy and Data Quality 18 December 2012
This document must not be made available to persons outside Western Power without prior written approval of Western Power Released to the University of Adelaide for Marking Purposes only
Uncontrolled document when printed. Printed copy expires one-week from print date. Refer to DMS for current version Print date: 27 May 2013
Distribution list
When this document is updated, the following people must receive a copy of the updated version: Name Position/title
Andy Neemann
Nicholas Howard Ian Baldwin David Fyfe Gavin Forrest Marinko Gaspar Sharon Braiding
18/12/2012
N/A
I. Baldwin
Initial
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
Related/referenced documents
Note all documents are to be held in the project folder with in Western Powers Document Management System (DMS) inline with Western Powers Records Keeping Policy. All signed documents are to be scanned and entered into the DMS. All documents referenced are to be prefixed by DM # then the DMS Number. All project Documents are to be controlled through the Project Document Register.
Document title Document ID (DM #)
EWD Project Charter Information Needs Management Plan IT Service Management Change Management Risks, Issues and Dependency Log Implementation Approach Business Case for CIP CIP Scope EWD Risks & Issues Log Project Status Report Project Handover BI Checklist for P2S Project Document Matrix
DM#6826913 DM# 5235062 DM#2010374 DM# 5236897 DM# 5463504 DM#9202721 DM#10114737 DM#9689902 DM#5294191 DM#8747465 DM#9752358
Approval
Name Andy Neemann Role Project Sponsor Signature Date
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
Contents
1 Purpose of document.............................................................................1 2 Executive Summary of Project Charter................................................1
2.1 Value proposition....................................................................................1 2.2 Impact to Stakeholders...........................................................................1
3 Project agreements.................................................................................2
3.1 Approval..................................................................................................2 3.2 Project description...................................................................................2 3.3 Scope......................................................................................................2 3.4 Assumptions...........................................................................................3 3.5 Constraints..............................................................................................4 3.6 Acceptance.............................................................................................4 3.7 Critical success factors...........................................................................4 3.8 Project costs..........................................................................................5 3.9 Budget tracking.......................................................................................6 3.10 Business Benefits..................................................................................8 3.11 Safety..................................................................................................12
4 Project approach...................................................................................13
4.1 4.2 4.3 4.4 4.5 Overview...............................................................................................13 Implementation Approach.....................................................................14 Outline...................................................................................................14 Software Development Lifecycle (SDLC) Methodology.........................14 Organisation Processes and Enterprise Deliverables............................14
Purpose of document
This Project Management Plan is written by SP&DQs Principal Project Coordinator with support from the project team and is approved by the Project Sponsor. It describes what the team plans to produce (interim and final deliverables) and what resources are needed to produce it. It is used to: Demonstrate the Project Manager's understanding of the project requirements. Guide project execution. Document project planning assumptions and decisions. Provides a baseline for progress measurement and project control. Facilitate communication among stakeholders.
2.1
Value proposition
This data warehouse solution will consolidate the equipment and works related data from these multiple sources into an integrated and validated source to improve reporting and enhance analysis. This will allow the business to make more informed decisions by making the right information, at the right levels of granularity, at the right time, readily accessible to the right people in the organisation.
2.2
Impact to Stakeholders
The business Impact of this Project will be through the provision the ability for Western Power to make more informed decisions by providing accurate and timely information. The outcome will be the streamlining of Western Powers management reporting processes and removing the reliance on custom reporting solutions currently provided in MS Access and MS Excel, and which are supported and maintained by key business users. The Project Charter can be accesses in detail at (DM#6826913)
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
3
3.1
Project agreements
This section defines key management outcomes in the project.
Approval
The Equipment & Works Data Warehouse Continuous Improvement Business Case was signed by the CEO on 21/10/12. The Business Case covers the project which relates to the build, test, and deployment of the previous descoped, partially delivered, unresolved defects and enhancements identified in previous EWD projects. This project was initiated with the release of interim funding for Business Case EWD CIP DM#9202721. This project covers the enhancements as outlined in Section 3.3, for the duration of FY 12/13 and all phases, stages and iterations achievable during the time frame. This Project Management Plan covers the EWD CIP. It will be periodically revisited and updated through out the life of the project.
3.2
3.2.1
Project description
To deliver unresolved components of the Enterprise Data Warehouse.
Location
The EWD CIP will be conducted and built on site at Western Powers Head Office 363 Wellington Street Perth WA 6000.
3.3
3.3.1
Scope
In Scope
In scope items for the EWD Continuous Improvement Project are outlined in the CIP Scope Register DM#10114737 and approved in the Business Case DM#9202721. Below is a list of those items approved for delivery in this project. For additional information about each requirement refer to the Scope Register DM#10114737. For test cases that relate to the deliverable, utilise the Requirement Unique Identifier in Quality Centre, Western Powers Testing and Defect Management Tool, under EWD CIP Project: Time Based Reporting Old MS Access Snapshots into Oracle. Query and View SPIDA Data via SPIDA. View All Network Asset Data Spatial and non-Spatial by time. Management of Abandoned Attributes. Historical Streetlight Data. Network Topology Subject Area. Incorporation of SPIDA - Only Electrical Components in EWD. Removal of Redundant Fields. Access Data Sources External to COGNOS. Inclusion of Carrier Data. Spatial Indexing. EWD Notifications.
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version Page 2 [Template 743689]
DM#: 9987158v1
3.3.2
Out of scope
The following are excluded from the scope of the project: Operational reporting needs and information outputs required in real time. Data not related to relevant Equipment and Works processes and functions. Changes to underlying systems except where it is necessary to produce an Extract, Transform, and Load (ETL) output for population in the data warehouse. Improving the quality of the underlying Equipment and Works data in the underlying source systems. General user training relating to the use of reporting tools such as Cognos (except for new users exposed). Requirements which cannot be met due to the lack of support from the current underlying business processes. Anticipating future requirements as a result of new, to-be-defined business processes.
3.4
Assumptions
An evaluation period of 5 years was utilised in financially assessing the considered options. Western Power's information needs will largely stay the same even with the introduction of new operational systems and business processes. Should a change result in the redesign of a part of the data warehouse, this will be accommodated through a Change Request. Data quality issues identified by this project will be addressed by existing Western Power business units responsible for this function and not by the project. Ongoing operating costs are based on: An additional 50% of a Business Intelligence resource will be required to support this component of the warehouse on an ongoing basis; hardware costs of $10,000 p.a. based on ITs assessment
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
3.5
Constraints
Operational priorities may take preference over projects, therefore the implementation of the recommended project will need to be cognisant of, and operate within these constraints. The overall project is delivering to a predefined platform in terms of hardware, database and Business Intelligence software. ISAM and EWD projects are dependent on some aspects of each other (interproject dependencies); the two projects may also have specific tasks that depend on each other (cross-project links). Although this will be tracked and managed, there is a potential for scheduling shifts and can become a constraint.
3.6
Acceptance
The Project will be considered accepted when all key project deliverables as listed in Section 3.3.1 have been approved and signed off by the relevant stakeholders inline with the exit criteria for each requirement as per the Scope Register DM#10114737.
3.7
DM#: 9987158v1
The following table provides a summary of the project priorities: Constrain Cost Time Scope Y Y Y Accept Enhance
Constraints The budget and time is to be constrained. The scope will be adjusted and reviewed at the end of each cycle to ensure that balanced focus is maintained on business operational pressures and alignment to strategic goals. Business priorities will dictate changes to the schedule and opportunities to bring forward deliverables may be explored. Any significant changes required or caused by ISAM or any other upstream project i.e. Non or late delivery of dependant data or systems will have an adverse effect on the priority of projects scope items.
3.8
Project costs
The expected costs for the EWD CIP are outlined in this section. The figures depicted in this section are derived from the EWD CIP Business Case Finance Work Sheet (DM#907623) and should be referred to if more detail is sought.
3.8.1
Capex costing
Below are the rolled up costs for the Capex component of the EWD Project 2012/13 2013/14 1 $1,500,0 00 1 Option One 2012/13 2013/14 $875,000 $875,0 00 $1,500,0 00 875,000 87 ,500.00 962 ,500.00 total option one $1,500,0 00 $1,500,0 00 $150,000 $1,650,000
$87 5,000
$2,612,500.00
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
3.8.2
Below is the estimate of ongoing OPEX cost attributed to support the solution once the first iteration has gone live. Cost Category Training Hardware BI Support Totals $M Year 1 $M $0.01 $0.01 $0.09 $0.11 Year 2 $M $0.01 $0.01 $0.09 $0.11 Year 3 $M $0.01 $0.01 $0.09 $0.11 Year 4 $M $0.01 $0.01 $0.09 $0.11 Year 5 $M $0.01 $0.01 $0.09 $0.11 Totals $M $0.05 $0.05 $0.45 $0.55
Training Costs based on 5 people trained per year for a 2 day training by a technical specialist Technical Specialist Hourly rate $123 2 Day Course rate $1,850 BI Support Agreed through discussion with IT (DM#9123737), Estimated at 50% of a BI Analyst resource BI Analyst Hourly Rate $93 Yearly Cost $181,994 Support and Hardware Requirements agreed through consultation with IT (DM#9123737 and DM#9123738)
3.9
Budget tracking
The projects budget will be tracked and reported on fortnightly by the Business Project Manager utilising the Budget Tracking Spreadsheet DM#5612430. Budgets will be reconciled at the end of the Month against figures provided from Group Commercial extracted from Ellipse ERP.
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
3.10
Business Benefits
Western Power's Business benefits definition can be found in DM#8811026. Details of the benefits realisation plan for this project can be found in DM#9057766. In addition it must be remembered that this project will return functionality in certain areas that was not transferred in previous EWD projects due to descoping and removing negative benefit. Type Type 1 Description Decrease in cost Increase in revenue Increase in productivity Increase in liquidity Cost avoidance Obligations: Statutory Contractual Internal policies & standards Board or Executives directive Investment Decision Requirements if primary driver NPV positive Evidence of realisation Cashable: $ budget journal Demonstrate direct impact to P&L or Balance Sheet Use financial ratios Non-Cashable Evidence of reinvestment Compliance breach register And appropriate authority validation (R&C, health check, internal audit, external audit, regulatory submission)
NPV positive Demonstrate it is mandatory Demonstrate the proposed option is the most cost effective way to meet requirements Demonstrate consequences of non compliance: - Financial (fines) - Non-financial (reputation)
Demonstrate strategic alignment Demonstrate the current risk is above tolerance & target risk is acceptable Uncontrolled document printed. copy expires Demonstrate the valuewhen at risk using Printed adequate one week from print date. Refer to DMS for current version metrics and indirect impact to P&L or Balance Sheet Demonstrate the proposed option is the most cost effective way to meet objectives Opportunity cost of not investing in the initiative
Evidence of strategic direction Risk measure before and after investment using branch risk register & Page 8 rating And[Template appropriate authority validation 743689] (R&C, health checks, internal audit, external audit, regulatory submission)
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
3.10.1.1
This project will have no direct budget reduction impact as the primary objective is to improve information quality and deliver functionality that should have been delivered to replace legacy systems in previous EWD projects.
3.10.1.2
Type II Benefits Economic Value - $833,544 Present value over AA3 period The use of the EWD tool across the business will result in the reduction and some cases the avoidance of field visits. The main identified motion time saved. The areas of the business that own and will realise theses benefits as well as the breakdown can be found at DM#9057766.
File#: TT/119/3427(7N)V1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
10
3.10.1.4
Title
Specific T3 Benefits
Description & Assumptions Governance and Compliance Impact Metric to be used for evidencing benefits Evidencing is problematic as benefit is distributed across numerous projects and investigations.
Page 11 [Template 743689]
The EWD system will support the validation of the assets location data contained in Western Powers records which are currently not always sufficiently accurate to enable planning work to be carried out without field visit. EWD will support the data quality effort but is not
Minor
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
Customer service
Customers & External stakeholders The up to date and historical view of Minor location of assets provided by EWD will enable improved accuracy and speed of reply to customer queries. It may also enable recovery of costs from customers that would not have previously been supported by sufficient evidence.
Reputation
EWD forms part of the enabling initiatives that Western Power is undertaking to strengthen its internal governance and ensure that decisions are made based on accurate data. This will contribute to deter public criticism of Western Power's governance and safeguard reputation Environment EWD will contribute to improve the quality of planning, prioritising and implementation process of works management with up to date reports of Western Powers Assets. People & Culture A transparent process and fact based decisions making may result in an improved OCI rating.
Minor
High
Auditing and reporting against contracted works to track and log instances of contractor omission. Evidencing is problematic as benefit is also impacted by factors outside this project.
Accountability culture
Moderate
3.11
Safety
All project personnel, including contractors, will be governed by the Western Power Safety Manual (DM#3403146) and will undergo the relevant site inductions prior to commencing work at the site.
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
4
4.1
Project approach
Overview
Given the expected level of change within Western Power over the life of this project, a flexible approach to project delivery will be required. As a result, a staged approach to implementation will be adopted. Each stage or Iteration will target one or more information subject areas and will be treated as a deliverable in its own right. Iteration will deliver the following: The reporting subject areas for ad-hoc analysis A set of standard, pre-built reports (the exact reports that will be delivered will be determined in the detailed analysis of each sub-phase) Training for end users Metadata to provide visibility of the source of the data and the transformations that have been applied to it
The subject areas to be delivered during the project are listed below. One or more subject areas will be delivered within each sub-phase. This sequence is aligned with the business priority and needs: Modify data feeds into the data warehouse to source equipment and defects information from Ellipse; Modify data feeds into the data warehouse for Transmission Wood Pole information from Ellipse rather than TLS and TRIS; Data warehouse modification to cater for work order and project structure changes initiated by Mobile Workforce Solution and ISAM. Changes to impacted business reports will need to be undertaken by the business power users; Load snapshots of historical DFMS data, which is currently stored in a standalone database, into the data warehouse and decommission the stand-alone database; Create reports that are currently provisioned from TIPD and DAMP databases to allow business continuity as underlying systems are replaced; Enhancements to previous delivered prebuilt reports and creation of new reports that will ensure business continuity and the take-up by the business is maximised; Requirements and/or Analysis Phase of the following items: Secondary Systems Asset Reporting with a view to replacing current reporting systems as the assets get moved into Ellipse; Enhance the view of equipment in the data warehouse to provide a topological view, showing connectivity relationships between individual pieces of equipment; Automate the reliability reporting back end process to eliminate manual data extracts and consolidation, including sourcing TCS data from the data warehouse; Incident Reporting for Feeders; and
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version Page 13 [Template 743689]
DM#: 9987158v1
4.2
Implementation Approach
The method in which the Project plans to deliver the Equipment and Works Management data warehouse is detailed in full within the Implementation Approach document (DM #5463504). The remaining subject areas as identified in the Implementation Approach document may be addressed in a future phase of the project and is outside the scope of this Project Management Plan.
4.3
Outline
Once into the build phase the project will run on a 6 week iterative cycle. The list of approved scope items are those identified as required at the start of the project. At week five of the iteration cycle a review of the requirements will be conducted. Any new requirement raised at the EWD Focus Group will be prioritised with the existing requirements and recommendation as to what will be in the next iteration will be presented to the Steering Committee with sign off by the Project Sponsor, within the limitations and constraints as outline at 3.7.
4.4
4.5
A document outlining the approach, together with the scope, duration, assumptions, issues, risks and constraints. Physical data model for the subject areas within the scope of this Statement of Work* developed in the Power Designer tool. Requirement Specification for the Equipment Conditions and Condition
Project Sponsor
BI Manager
Conditions Requirement
DM#: 9987158v1
Project Sponsor
Page 14 [Template 743689]
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
Project Sponsor
Project Sponsor
BI Manager
Project Sponsor
Project Sponsor
BI Manager
Project Sponsor
Project Sponsor
ETL Specification for the Network Incident subject area. Data warehouse and reporting solution for Network Incident subject area tested and deployed in production Requirement Specification for the Work Summary subject area.
BI Manager
Project Sponsor
Project Sponsor
ETL Specification for the Work Summary subject area. Data warehouse and reporting solution for Work Summary subject area tested and deployed in production
BI Manager
Project Sponsor
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
5.1
Risk management
For the purposes of this plan, a risk is defined as: Any item that is foreseen to potentially affect the project from being completed on time, within budget, or from meeting its objectives. The risk management process described in this plan is, as far as is reasonably practicable, consistent with Western Powers corporate risk management framework. A risk log is maintained for the project. It will be used to provide an overview of the status of the identified risks and will support the development of mitigation and contingency plans. The project manager will review the risk log on a fortnightly basis and key risks will be tabled at each project team meeting and included in the project status reports that are sent to all stakeholders. The risks identified for the project are listed in the table below
Risk description (Inherent Risk) Inherent Risk Mitigation / Containment / Treatment/ Accept Residual Risk
Insufficient Western Power resources are available to meet the proposed timelines Quality of source data not known or overestimated adding significant time for data cleansing activities.
Extreme
Communicate resourcing requirements early and regularly. Bring in external parties where possible. Conduct data analysis early and provide results to Data Quality project for correction; Implement cleanest data first; categorise data quality and provide to users. Agree requirements and put under strong change control. Use conference room pilots to validate requirements early. Commence applicable build activities only when ISAM design and source to target mapping has been completed, and delivery schedules are firm. Build warehouse based on common process and terminology.
High
Extreme
High
Scope continues to expand as new requirements are identified during the project Dependent projects do not meet their published schedule, jeopardising the implementation timeframes of this project Significant changes are imposed on this project resulting from changes to source operational systems.
Extreme
High
Extreme
High
Extreme
Moderate
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
The scope of deliverables cut across a number of existing subject areas in the data warehouse with the potential to implement duplicated functionality
Extreme
High
The complete list of risks and issues can be found in the EWD Issues, Risk and Change Log (DM#9689902). An extraction of the Risk Log being built at the time of this PMP is shown below
5.2
Issue Management
An issue can be defined as A risk that has come to fruition An issues log will be maintained for the project in the EWD Issues, Risk and Change Log (DM#9689902). It will be used to support control of outstanding issues. The project manager will review the issues log on a fortnightly basis and key issues will be tabled at each project team meeting and included in the project status reports that are sent to all stakeholders.
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
5.3
Change Management
All project changes shall be detailed in the project change control log contained in the EWD Issues, Risk and Change Log (DM#9689902) The Sponsor, together with the Network Performance Branch Manager will approve any changes that impact scope, quality, benefits, cost, or schedule. Approval for minor changes will be controlled via Email or meeting minutes (decisions). Other changes of significance will use a formal change request process and templates to clearly quantify the impact of change. Such changes include any changes to scope, budget, and/or schedule. An extraction of the Change Register being built at the time of this PMP is shown below:
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
5.4
Quality Management
The following quality management activities will be performed: All documentation prepared by this project will be peer checked and will undergo review and approval process for acceptance by relevant support groups. All documents are to be captured in the project file TT/119/3427(7N)V1 in the Document Management System (DMS). An extraction of the Document Register being built at the time of this PMP is shown below:
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
The Architectural Review Group (ARG) will be engaged for review and acceptance of Technical Solution; All Server builds will be built in accordance with standard build and testing processes to the Standard Operating Environment (SOE) standard; All applications developed/configured by the project will be system tested by Quality Centre team and Defects prioritised and addressed. Testing report discussed and approved by project sponsor prior to production implementation; All deliverables produced by the External Service Provider (Wipro) will be reviewed by the Western Power BI Team to ensure adherence to Western Power architectural and technical standards; End user training will be provided for all users requiring access to the solution. A combination of internal training as well as external (vendor) training will be provided where appropriate for the expected level and type of use of the system; User Acceptance Testing will be completed and signed off 1 week prior to production implementation, and All implementations and production changes will comply with Western Powers IT Service Management Change Management policy and criteria (DM#2010374).
5.5
Inter-dependencies
Dependencies are recorded in the EWD Issues, Risk and Change Log (DM#9689902) under the interdependencies tab. The list of dependencies will be updated as the project progresses and as other project come online.
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
6
6.1
Communications Management
Stakeholder Assessment
This section identifies all parties who are impacted by the implementation of the project or who have an interest in the outcome. Table 1 below lists each stakeholder and identifies strategies for gaining support or minimising negative impacts.
Table 1: Stakeholder Analysis Matrix
Stakeholder Stakeholder Interest(s) in the Project Assessment of Impact Potential Strategies for Gaining Support or Reducing Obstacles
Andy Neemann
Project Sponsor
Responsible for governance of data warehouse and addressing data quality issues. His people will be key users of information. Ultimate approver of documents/decisions.
1. Regular project status updates 2. Information about how change is being managed understanding any resistance of the business 3. Business buy-in 4. Measuring success of the project improvements after implementation
End users
Will utilise the information made available through the solution delivered
Require access to the new EDW change to the way the task is performed so require training
1. Project Status Updates 2. Go-live date and key dates 3. Training and support available 4. Overview of the project, rationale, expected benefits / outcomes and new system, out of scope 5. How to obtain access to the new EWD
Other Foundation
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
Business Intelligence
IT Service Desk
6.2
Communications Plan
Progress reports and briefings will be provided by a combination of meetings, emails and memos. This may be followed up with more detailed documentation. Possible reports and communication briefings are shown in Table 2. Table 2: Progress Reporting and Briefings
Report or Briefing type Type Audience When/Regularity
Project team members Project team, technical support staff, IT Branch team leaders and steering committee.
Daily/weekly/monthly 6th working day of each month for the duration of the project
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
7.1
Resource Plan
The following resources will be working on the project:
Role Project Manager Business Project Manager IT Project Sponsor Name Nicholas Howard Marinko Gaspar Andy Neemann Responsibilities Overall Project Delivery IT Project Delivery Provides scope and vision. Involved in status and risk review. Makes business resources available Provide overall project governance and point of escalation for administrative issues. Act as a change champion for the solution. Take accountability for the solution design and the functional specification. Provide leadership to the core team, SMEs and Business Representatives when they are involved in designing the solution in detail. Validate solution design from the perspective of the other projects within the Asset and Works subprogram. Provide input to the project on the proposed solution of their respective projects. Responsible for designing and building a solution that satisfies the business requirements. Provide knowledge transfer to the WP BI Team on When Full time for the duration of the project Full time for the duration of the project Intermittently for the duration of the project
Program Manager
Ian Baldwin
Sundy Thjin
Solution Implementer
Wipro
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
BI Architect
Intermittently for the duration of the project. Intermittently for the duration of the project.
7.2
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
File#: TT/119/3427(7N)V1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
7.2.1
7.2.2
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
7.2.3
7.2.4
Equipment and Works Data Warehouse Solution Lead (Client Rep) Sundy Thjin
The Solution Lead is accountable for defining a solution which will deliver the Sponsor and stakeholders the organisational transformation required. Along with the Project Manager, the Solution Lead is a key player in the Project Management Team. The Solution Lead is responsible for: Taking accountability for the solution design and the functional specification. Being Western Powers evangelist for the Equipment and Works Data solution. Acting as a change champion for the solution and project. Taking an enterprise perspective on the solution to ensure an integrated Whole of Business solution is designed and developed over time. Appling his knowledge of Western Powers processes and systems and industry best practice to define the best solution for the projects business requirements. Drive the identification and acceptance of feasible alternative solutions, recognising constraints such as system functionality, user impact, level of change, and time to implement; taking a clear position on what they believe is the optimal solution for Western Power. Transferring the appropriate business and technical knowledge to project team members as required.
7.2.5
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
7.2.6
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
8
8.1
8.2
Schedule The schedule below shows the rolled up components to be implemented. The content and priority of delivering scope items are dependent on other projects (i.e. ISAM2) meeting their implementation schedules. The project schedule is designed to controlled and monitor the project. It is the responsibility of the Project Manager to monitor and maintain the schedule. The schedule is reported on fortnightly in the Project Status Report and reviewed by the Program Manager for quality purposes DM#5294191. Schedules are to be rebase lined after change requests and up dated fortnightly to reflect progress.
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version
DM#: 9987158v1
Uncontrolled document when printed. Printed copy expires one week from print date. Refer to DMS for current version