Internal use only

Project name
Programme/Project Cluster name
(if applicable)

Project Initiation Document (PID)

PID Template Version 3.2

Author
Project Code
Document id
Date last updated
Version
Status

61392773.doc
dd-month-yyyy
0.1
Working Draft

Project name
Project Initiation Document (PID)

MANAGEMENT SUMMARY
Project Name
Project Code
Programme/Proj.Cluster Name (if app.)
Programme Code (if applicable)
Programme Manager (if applicable)
Initiating Organisation Unit
Value/Support Chain (if applicable)
Final Authoriser
Senior Responsible Owner
Executive
Project Manager
Portfolio Category
Brief Description of the Project
Target Project (Execution) Start Date
Estimated Project End Date
Target Approval date*
The document contains additional clarifications (on top of the short help sentences) as Comment, which are
visible if Markup is activated (see View menu in Word).
*All estimates regarding time scales and costs are dependent on meeting this date.

Project Summary ( )

Cost Benefit Summary ( )

Copy the amounts from the cost benefit analysis spreadsheet, replace the first year by the appropriate calendar year
(year in which the project starts), is default currency. Alternatively copy an image containing the items below.
Amounts x 1000
Investments
Total Project Cost
Total Baseline Cost Imp.
Total Income/Savings
Total P&L Impact

2007

2008

2009

2010

2011

2012 Total
0
0

Investments: Assets to be depreciated (Hardware, Software, Other)

Total Project Cost: is including depreciation of investments
Total P&L Impact: Income/Savings Project Cost Baseline Cost Impact

Costs for future years should be re-stated before the start of each year, at least as input for the MTP.
Contact your project office for local rules for how to do the restatement.

Financial metrics ( )
NPV (state the used discount rate)
IRR

Payback Period
ROI year 5

( ) Besides Financials (Cost & Financial Benefits) these sections are also part of the BUSINESS CASE.
Describing the rationale of a project also includes objectives, proposed solution, key risks and timelines.
Document: 61392773.doc
V0.1 Working draft

Page 2 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)
Additional information for Project Portfolio Management
Refer to local organisation specific procedures if any additional information is to be provided and in what format.

Document: 61392773.doc
V0.1 Working draft

Page 3 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)

PROJECT AUTHORISATION
Authorisation List
List the persons to authorise the Project including the budget allocation for the coming year.
* = Add/delete as appropriate, refer to the appropriate project governance procedure for guidance
**If the project has SOX impact, the process owner has to approve the start of the project.

Authoriser
Function / Title

Authoriser
Name

Signature (or
Refer to approval)

Date

Executive
Senior Responsible Owner
Final Authoriser
Acceptant Groups
* Commerce
.

* Operations & IT
.

* Finance Tax &Risk**

.

* Staff & Support

..
*

Please note that the persons mentioned below (Supplier) have agreed to supply the resources for the project (see
also section 5.2) from the following ING organisation units / third parties:

Supplier Function / Title

Supplier Name

Organisation unit

Cost Allocation
List all beneficiaries for this project and the share of the project costs (after Initiation) that will be charged to them.

Business Line /
Support Function

Legal entity

Country

Share Authoriser
of costs Name

Signature (or refer

to approval)

100%

Total
Please explain below the rationale behind the allocation key.

For Information
If appropriate list the persons or groups to send a copy for information, which are all stakeholders that do not have
to authorise the project.

Function / Title

Document: 61392773.doc
V0.1 Working draft

Name

Page 4 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)

TABLE OF CONTENTS
AUTHOR..................................................................................................................................................1
PROJECT CODE.....................................................................................................................................1
DOCUMENT ID.......................................................................................................................................1
61392773.DOC..........................................................................................................................................1
DATE LAST UPDATED.........................................................................................................................1
DD-MONTH-YYYY.................................................................................................................................1
VERSION..................................................................................................................................................1
0.1...............................................................................................................................................................1
STATUS....................................................................................................................................................1
WORKING DRAFT.................................................................................................................................1
MANAGEMENT SUMMARY................................................................................................................2
............................................................................................................................................................4
............................................................................................................................................................4
............................................................................................................................................................4
TABLE OF CONTENTS.........................................................................................................................5
1 PROJECT OVERVIEW.......................................................................................................................7
1 PROJECT OVERVIEW.......................................................................................................................7
1.1 Background & Current Situation ......................................................................................................7
1.2 Project Objectives .............................................................................................................................7
1.3 Scope ................................................................................................................................................7
1.4 Requirements ....................................................................................................................................7
1.5 Proposed solution .............................................................................................................................7
1.6 Overview of Project Deliverables .....................................................................................................7
1.7 Impact of the Project Result...............................................................................................................7
1.8 Strategic Business Alignment............................................................................................................7
2 PROJECT COSTS AND FINANCIAL BENEFITS ..........................................................................8
2 PROJECT COSTS AND FINANCIAL BENEFITS ..........................................................................8
3 NON-FINANCIAL BENEFITS............................................................................................................8
3 NON-FINANCIAL BENEFITS............................................................................................................8
DESCRIBE AND EXPLAIN THOSE BENEFITS THAT DO NOT HAVE DEFINITIVE
REVENUE OR COST IMPACT. BENEFIT CATEGORIES PROVIDED ARE FOR GUIDANCE
ONLY, PLEASE DELETE OR ADD AS APPROPRIATE. SCORE THE IMPORTANCE BY H=
HIGH, M= MEDIUM, L= LOW..............................................................................................................8
4 PROJECT ORGANISATION..............................................................................................................9
4 PROJECT ORGANISATION..............................................................................................................9
4.1 Project Organisation Chart.................................................................................................................9
4.2 Roles and responsibilities..................................................................................................................9
5 PROJECT PLAN.................................................................................................................................10
5 PROJECT PLAN.................................................................................................................................10
Document: 61392773.doc
V0.1 Working draft

Page 5 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)
5.1 Planned lifecycle..............................................................................................................................10
5.2 Resource Planning...........................................................................................................................10
5.3 Dependencies ..................................................................................................................................10
OUTLINE ANY DEPENDENT ITEMS THAT LIE OUTSIDE OF THE SCOPE OF THE
PROJECT UPON WHICH THE SUCCESS OF THE PROJECT DEPENDS (E.G. INTERFACES,
FUNCTIONALITY DEVELOPED BY OTHER PROGRAMMES/PROJECTS) OR ANY
PROJECTS THAT DEPEND ON THE SUCCESS OF THIS PROJECT. STATE PER
DEPENDENCY WHAT IT ENTAILS AND, IF APPLICABLE, THE PROGRAMME/PROJECT.
...................................................................................................................................................................10
5.4 Quality Management.......................................................................................................................10
5.5 Reporting & Communication...........................................................................................................10
6 PROJECT RISKS................................................................................................................................11
6 PROJECT RISKS................................................................................................................................11
6.1 Project Delivery Risk.......................................................................................................................11
6.2 Project Result Risk..........................................................................................................................11
6.3 Critical Success Factors ..................................................................................................................11
7 PROJECT TECHNICAL SUMMARY..............................................................................................12
7 PROJECT TECHNICAL SUMMARY..............................................................................................12
7.1 Technical Solution Summary...........................................................................................................12
THE SECTIONS IN THIS CHAPTER ONLY NEED TO BE COMPLETED FOR PROJECTS
WITH OPERATIONS & IT IMPACT..................................................................................................12
DESCRIBE BRIEFLY THE TECHNICAL ARCHITECTURE THAT SUPPORTS THE
(BUSINESS) SOLUTION. .....................................................................................................................12
7.2 IT Standards ....................................................................................................................................12
DESCRIBE ANY ELEMENTS OF THE IT SOLUTION WHICH DO NOT COMPLY WITH
THE ING GROUP & LOCAL IT POLICIES AND STANDARDS AND CONSIDER THEIR
ORGANISATIONAL IMPACT. ...........................................................................................................12
7.3 Strategic IT Alignment....................................................................................................................12
7.4 Information Risk Management Requirements .................................................................................12
7.5 BCP/ DR Requirements...................................................................................................................12
APPENDIX 1: OPS&IT BANKING SERVICES.................................................................................13
APPENDIX 1: OPS&IT BANKING SERVICES.................................................................................13

History log
Version

Document: 61392773.doc
V0.1 Working draft

Date

Related documents

Page 6 of 13

Short description modification

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)

1 PROJECT OVERVIEW
1.1 Background & Current Situation
Describe the Current Business conditions that have created the project requirement.

1.2 Project Objectives

Describe all (e.g. Business, Organisational, Financial, Technical, Control and Process Improvement) objectives.

1.3 Scope
What boundaries define the project (explain inclusions and exclusions to the project scope regarding products,
processes, organisational units, locations etc). Describe also starting points, preconditions and constraints.

1.4 Requirements
List the key requirements (e.g. those business, policies, rules &regulations requirements, which can be regarded as
acceptance criteria) for the project. Copy from the Feasibility Study.

1.5 Proposed solution

Give an outline of the solution proposed, including key business processes. Copy a brief summary of the alternative
solutions (e.g. reuse, buy, make) and conclusions from the Feasibility Study (including the arguments for choosing the
proposed solution).

1.6 Overview of Project Deliverables

Give an overview of all key (end) deliverables of the project.

1.7 Impact of the Project Result

Describe the consequences of the project result, only if not stated in other sections. For SOX impact see section 6.2.

1.8 Strategic Business Alignment

Describe the contribution and alignment of the project result to officially stated strategic business objectives.
Consider alignment on ING/ Regional/Organisation unit level

Document: 61392773.doc
V0.1 Working draft

Page 7 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)

2 PROJECT COSTS AND FINANCIAL BENEFITS

REFER TO THE ATTACHED COST BENEFIT ANALYSIS SPREADSHEET
Contact your project office which cost benefit analysis template is to be used. Consider copying the (summary page)
of the spreadsheet into this section.
Describe for each cost/benefit item the major assumptions that underlie the calculation of the amount, e.g. for staff
costs: manpower rates used, % contingency added. Contact your project office for manpower rates.

3 NON-FINANCIAL BENEFITS
Describe and explain those benefits that do not have definitive revenue or cost impact. Benefit categories provided are
for guidance only, please delete or add as appropriate. Score the Importance by H= High, M= Medium, L= Low

Benefit Category

Explanation of the benefit including benefit targets where

possible (specify verifiable and measurable indicators)

Importance

Customer
Satisfaction
Business Operations:
quality, flexibility,
security, control etc.
Management and
Customer
information
Image
Employees
Value of future
flexibility provided
Regulatory Demands
Other

Document: 61392773.doc
V0.1 Working draft

Page 8 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)

4 PROJECT ORGANISATION
4.1 Project Organisation Chart
Copy into this section the project organisation chart of the project management team that is worked out to Team
Manager level.

4.2 Roles and responsibilities

Include all project management team roles (see previous section), all project internal roles and project external roles
during the entire lifecycle of the project.
* Delete or add as appropriate

Role
*Project Board
Executive
Senior User
Senior Supplier

Name (if known)

Responsibility

*ING Involvement
See section 5.2
*3rd Party Involvement

Document: 61392773.doc
V0.1 Working draft

Page 9 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)

5 PROJECT PLAN
5.1 Planned lifecycle
Describe the major milestones and deliverables for the project in each phase. Adapt the table to the project needs,
however in compliance with GPL and/or local guidelines.

Phase

Major Milestones Planned (or finished)

Start up

Project Brief approved

Initiation

Feasibility Study agreed

PID approved

Stage Report approved

Stage Report approved

Execution & Control

Phase 1
Execution & Control
Phase 2
Execution & Control
Phase 3
Project Close

(Planned)
Delivery Date

Lessons Learned Report

End Project Report approved

5.2 Resource Planning

List the resources needed for the entire project (Execution + Close). For agreement on resource delivery by the
Suppliers, see the Authorisation List page.

Area / Department /
3rd Party

Role (and Name if known)

Effort in
hours

Period

If Ops&IT Banking is involved in this project, the additional requirements of Appendix 1 apply.
5.3 Dependencies
Outline any dependent items that lie outside of the scope of the project upon which the success of the project depends
(e.g. interfaces, functionality developed by other programmes/projects) or any projects that depend on the success of
this project. State per dependency what it entails and, if applicable, the programme/project.

5.4 Quality Management

Describe the approach for managing quality within the project. Indicate if this section will be more detailed in a
separate Quality Plan.

5.5 Reporting & Communication

Describe briefly the reporting approach (type of document, time scales) regarding project management issues i.e.
information and communication from the project to involved parties. Indicate if this section will be more detailed in a
separate Communication Plan.

Document: 61392773.doc
V0.1 Working draft

Page 10 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)

6 PROJECT RISKS
6.1 Project Delivery Risk
The main implication and associated mitigation of any major project delivery risks (risks that are related to problems
that may endanger successful project completion) should be analysed and summarised below. Score the risks, taking
into account probability and impact by H=High, M=Medium, L=Low. Risk Owner is generally the Project Manager.

Risk Category

Explanation of Risk and Mitigation

Required

Project External
& Governance
Project Contents
(scope and other
changes)
(Application)
Complexity
Technology &
Vendor
Skills & Quality
Project Internal
Organisation
Other [Specify]

Prob. Imp.

Score

Risk Owner

H/M/ H/M/ H/M/

L
L
L

6.2 Project Result Risk

The main implication and associated mitigation of any major project result risks (risks that affect the achievement of
the stated objectives or that may arise when using the project result in day-to-day business) should be analysed and
summarised below. Score the risks, taking into account probability and impact by H= High, M= Medium, L= Low.
In this process it is mandatory to consult the functional stakeholders, refer to the Result Risk guide for details.

Risk Category

Explanation of Risk and Mitigation

Required

Prob. Imp.

Score

Risk Owner

Market Risk
Operational Risk
Credit Risk
Insurance Risk
Compliance Risk
Other [Specify]
Does the project have SOX impact: Yes/No
If yes, outline the SOX consequences here.

6.3 Critical Success Factors

Outline the critical success factors of the project.

Document: 61392773.doc
V0.1 Working draft

Page 11 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)

7 PROJECT TECHNICAL SUMMARY

7.1 Technical Solution Summary
The sections in this chapter only need to be completed for projects with Operations & IT impact
Describe briefly the technical architecture that supports the (business) solution.

7.2 IT Standards
Describe any elements of the IT solution which do not comply with the ING Group & local IT Policies and
Standards and consider their organisational impact.

7.3 Strategic IT Alignment

Describe the alignment of the project to officially stated Operations &IT objectives and IT Architectures that apply
within the scope of the project. If the use of IFSA is mandatory for your organisation unit attach the IFSA Compliance
Checklist as an appendix to the PID.

7.4 Information Risk Management Requirements

Report the results of the conducted (together with your local IRM department) Business Impact Assessment (BIA).
The purpose of the BIA is to assess the business risk associated with the system and to classify the system as a whole
in terms of criticality to the business, to derive the ING classification level for the information system and to identify
the level of protection needed. The results of the BIA are captured here

ING HIGH-LEVEL INFORMATION SYSTEM CLASSIFICATION

Confidentiality
Integrity
C_
I_

Availability
A_

Security Requirements
Related to the above mentioned BIA rating appropriate security requirements should be mentioned here

7.5 BCP/ DR Requirements

The solution implemented by this project will support business critical activities?
(Yes/No)
If the answer to the above is Yes, then please describe how Business Continuity will be supported for the business
critical activities. (The project budget should reflect the cost of implementing the disaster recovery solution.).

Document: 61392773.doc
V0.1 Working draft

Page 12 of 13

Date last updated: dd-month-yyyy

Internal use only

Project name
Project Initiation Document (PID)

APPENDIX 1: OPS&IT BANKING SERVICES

Note: This appendix only applies if Ops&IT Banking (OIB) is involved in the project. Please delete this
appendix if OIB is not involved, otherwise fill in the tables below.
IFSA Application Domain Type
Cross Border

Yes / No

The services provided by Ops&IT Banking as described in this PID are subject to the Project Cost Sharing
Agreement (PCSA) between the Ops&IT Banking Supplier legal entities listed below and the project
beneficiary legal entities as listed in the Cost Allocation table in the PID. The PCSA is subject to the
General Terms and Conditions Ops&IT Banking.
Estimated project costs per Legal Entity
Please fill in the table(s) below with the budgets that are supplied by the legal entities. Legal entities mentioned below
are the suppliers of the Ops&IT service. Budgets need to be split per legal entity per country. If more than one legal
entity supplies the budget, please split the budget per legal entity per country. .

ING Bank NV Netherlands

Year

2006

2007

2008

Staff costs
Outsourcing
Other
Total costs
ING Belgium NV Belgium
Year

2006

2007

2008

Staff costs
Outsourcing
Other
Total costs

Document: 61392773.doc
V0.1 Working draft

Page 13 of 13

Date last updated: dd-month-yyyy

Internal use only