under FOI - Bureau of Meteorology
Transcript of under FOI - Bureau of Meteorology
Released: Error! Reference source not found.
Error! Reference source not found.5 Supercomputer Programme Management Plan
Page 4 of 22
Contents 1. Programme Background ................................................................................................................. 6
2. Programme Objective ..................................................................................................................... 6
3. Product Descriptions .................................................................................................................... 7
4. Programme Scope ................................................................................................................... ..... 7
4.1. In Scope ................................................................................................................. ........ .. 7
4.2. Out of Scope ...................................................................................................... .... .......... 7
5. Key Assumptions ................................................................................................................ ......... 7
6. Dependencies ................................................................................................. ............................ 7
7. Constraints ........................................................................................... ...... ..... ..................... 8
8. Programme Approach ................................................................. ..... ....... ............................ 8
9. Projects within the Programme .............................................. ......... ........................................ 9
10. Programme Roles and Management Structure ............. ..... ........................................ 10
11. Key Stakeholders .......................................................... .......... ................................................ 14
12. Project Tolerances ..................................................... ...... ....................................................... 15
12.1. Escalation Process ................ .................. ..... ............................................................... 15
13. Project Definition Documentation .. ... ................................................................................... 16
14. Monitoring and Control.................. ......... . ............................................................................... 16
14.1. Schedule ................ ..... ... ............................................................................................ 16
14.2. Costs and Budget ........ ................................................................................................ 16
14.3. Financial Management ......................................................... Error! Bookmark not defined.
14.4. Quality A surance Plan...................................................................................................... 16
1 5. Chang Management Plan ................................................................................................ 17
14 6. Risk and Issue Management ............................................................................................. 17
14.7. Procurement Plan ............................................................................................................. 17
14.8. Resources .......................................................................................................................... 17
14.9. Information and Documentation Management ............................................................... 17
14.10. Lessons Learnt ................................................................................................................... 17
15. Product Acceptance Plan .............................................................................................................. 17
15.1. Product Acceptance Criteria ............................................................................................. 18
Releas
ed un
der F
OI
Released: Error! Reference source not found.
Error! Reference source not found.5 Supercomputer Programme Management Plan
Page 5 of 22
15.2. Product Gateway Planning ................................................................................................ 18
15.3. Product Accountability Matrix .......................................................................................... 18
15.4. Testing ............................................................................................................................... 20
16. Project Interdependencies ............................................................... Error! Bookmark not defined.
17. Commissioning Plan ................................................................................................................. .. 21
18. Communication Plan ........................................................................................................ ....... .. 21
18.1. Project Reporting .......................................................................................... .......... ...... 2
18.2. Programme Reporting ....................................................................................... ............ 22
Releas
ed un
der F
OI
Error! Reference source not found. Released: Error! Reference source not found.
Error! Reference source not found. Programme Management Plan Page 6 of 22
1. Programme Background
Numerical Weather Prediction (NWP) is a core capability of the National Meteorological and Hydrological Services of most developed countries, and increasingly of developing nations. It is essential for the provision of fast response, high impact, and high value weather services. All nations recognise that timely, specific and accurate warnings and forecasts for their region offer distinct national security, economic and social benefits. NWP necessitates the use of a high performance supercomputer to run complex models of the highly dynamical atmosphere/land/ocean system. These models produce weather forecasts over various timescales and at different levels of spatial resolution which are then used to issu warnings and general advice to end users.
2. Programme Objective
The objective of the Supercomputer Programme is to replace the existing supercomputer which will
reach end of life in 2016, and enable the Bureau to meet demand for enhanced NWP forecast
services and products into the future.
Material redacted in black is removed under s 34(3)
Releas
ed un
der F
OI
Error! Reference source not found. Released: Error! Reference source not found.
Error! Reference source not found. Programme Management Plan Page 8 of 22
There are some projects in the Bureau that need to have planning integrated with HPC to
assure alignment and benefits.
7. Constraints
The procurement of Supercomputers is highly specialist and quir s some additional steps
and approaches that are not inconsistent with Commonwealth P ocurement Rules but add
complexity to the process;
and
Applicable Bureau policies need t be adhered to by the projects and programme.
8. Programme Approach
Under the leadership of the Prog mme SRO, Dr. Lesley Seebeck, the approach of the programme is
to direct, support and govern th delivery of the projects within the programme, but not to directly
run the projects within the programme as this is the accountability of the individual project
executives, projec teams and project boards. This includes:
Ensuring the Supercomputer funds are spent in line with the funding allocations.
Ensu ing an appropriate level of project documentation is produced and approved by the
r levant Project Executive;
Providing a shared resource pool to realise efficiencies across the programme, functions to
be provided include project management, business analysis, programme administration and
change acceptance management;
Quality assurance of project documentation; and
Advice on options and approaches to achieve the best outcomes in regards to risks and
issues.
Coordination of communication regarding the programme, including production and
distribution of the Programme Report and management of the programme intranet site.
Material redacted in black is removed under s 34(3)Material redacted in grey is removed under s 47E(d)
Releas
ed un
der F
OI
Error! Reference source not found. Released: Error! Reference source not found.
Error! Reference source not found. Programme Management Plan Page 17 of 22
14.4. Change Management Plan
Refer to the file
14.5. Risk and Issue Management
Risk Management Process:
Issue Management Process:
HPC and Data Centre Risk and Issue Plan and Register:
Refer to the files:
14.6. Procurement Plan
Refer to the file:
14.7. Resources
The resources for the Programme consist of the pr gramm team, support staff and executive
programme board members. Full resour e planning fo the projects will occur when the
procurement outcomes are known.
14.8. Information and Documentation Management
Information and document managemen will be controlled through the Enterprise Portfolio
Management Office.
14.9. Lessons Learnt
Many lessons learned have been gathered from the first Supercomputer implementation that has
been onsid ed d ring this procurement. The Programme Manager and Director will manage new
lessons le rned for the HPC and data centre projects.
15. Product Acceptance Plan
The acceptance plan for each product will be undertaken in a staged approach. Each product will
have clearly defined planning, execution and commissioning stages with gateways requesting
authority to proceed. This process will ensure business and technical requirements are well defined,
implemented, tested and signed off.
Filepaths redacted in grey are removed by consentFile names redacted in grey are removed under s 47E(d)
Releas
ed un
der F
OI
Error! Reference source not found. Released: Error! Reference source not found.
Error! Reference source not found. Programme Management Plan Page 18 of 22
15.1. Product Acceptance Criteria
Each specialist product will have clearly defined acceptance criteria, established during the planning
stage and will form part of the documentation and highlighted in the product descriptions.
15.2. Product Gateway Planning
Each specialist product will have clearly defined gateways to pass before moving to the next stage.
Business products will vary in content to technical products however the following illustrates a igh
level generalised representation of the product gateways
15.3. Product Accountabil ity Matrix (further development)
As each product is developed, various stakeholders will be accountable for aspe s of specific items
and activities. The following matrix indicates how each stakeholder group is likely t be accountable.
Material redacted in black is removed under s 34(3)
Releas
ed un
der F
OI
Error! Reference source not found. Released: Error! Reference source not found.
Error! Reference source not found. Programme Management Plan Page 19 of 22
Material redacted in black is removed under s 34(3)
Releas
ed un
der F
OI
Error! Reference source not found. Released: Error! Reference source not found.
Error! Reference source not found. Programme Management Plan Page 20 of 22
15.4. Testing
Areas considered for the Testing comprises of the following components, not all forms of testing
may be required:
Unit Testing
Functional Testing
Usability Testing
Accessibility Testing
User Acceptance Testing
Unit Testing
The developer wil ensure he code/scripts are working as expected before the product is deployed
into the test vironment for functional testing. This will ensure the code deployed into the test
environment is quality tested by the developer.
Function l Testing
he unc onal testing is done by a test analyst to ensure that the product deployed into the test
en iro ment reflects the business requirements. The test analyst should raise defects if there is any
discrepancy in the product.
Usability Testing
The Usability Testing is a phase of functional testing and this is where the Tester ensures all usability
issues have been resolved before the product is deployed into the UAT Environment.
Accessibility Testing
Material redacted in black is removed under s 34(3)
Releas
ed un
der F
OI
Error! Reference source not found. Released: Error! Reference source not found.
Error! Reference source not found. Programme Management Plan Page 21 of 22
Accessibility Testing is where the product is tested to ensure compliance with WCAG 2.0. The Digital
Data Delivery team will be required to test for accessibility and work with the team to ensure all
accessibility issues have been resolved before the product is deployed into the UAT Environment.
User Acceptance Testing (UAT)
User Acceptance Testing is the phase where Business users get to review the product in the UAT
environment. The Users review the product against the agreed acceptance criteria, raising JIRA
entries for items that do not meet the criteria. This is a critical step prior to any product being
released in to Production.
If the Business has worked with the Developer during the development phases as plan ed here will
be a reduced likelihood of product failure during UAT. At a minimum, two iterations of UAT should
be planned for each product.
16. Commissioning Plan
The HPC and Data Centre projects will follow the approved Transition t Ope tions plan as defined
by ISS when commissioning products in to the Production environment. A many products will be
planned, executed and commissioned in parallel, the defined T ansit n o Operations plan will be
applied for each major product as it is due for release to t e Produ tion environment.
The Readiness Gateway planned for the end of the Execu ion Stage is the major point at which
approval to deploy the product is obtained. Approval stakeholders will vary depending upon the
product in question and is documented in he Product Descriptions.
This leads in to the Commissioning Stag where he product/s will be deployed in to the Production
environment once it has passed th Read ess Gateway; BAU Acceptance and training/support
documentation is handed over t BAU. Business Engagement during the Commissioning Stage will
involve user training and su ort uring the parallel run period, whereby a product Acceptance
Certificate will be sought confi m ng Business acceptance of the product.
17. Commun cation Plan
The HPC a d D ta Centre - Stakeholder Engagement and Communication Strategy involves
proacti ely d termining the information needs of stakeholders, what information needs to be
coll ted and when, who needs the information, when and in what form.
The strategy and plan cover:
methods used to gather and store information,
Limits, if any, on who may give direction and to whom,
reporting relationships,
list of contact information of all stakeholders,
schedule for distribution of information, and
Material redacted in grey is re removed under s 47E(d)
Releas
ed un
der F
OI
Error! Reference source not found. Released: Error! Reference source not found.
Error! Reference source not found. Programme Management Plan Page 22 of 22
provides a method to update the communications management plan as the projectprogresses.
Refer to the files:
17.1. Project Reporting
TBD – subject of Executive Meeting outcomes.
17.2. Programme Reporting
TBD – subject of Executive Meeting outcomes.
Filepaths redacted in grey are removed by consentFile names redacted in grey are removed under s 47E(d)
Releas
ed un
der F
OI