ATT Risk Log 8.6.2013 v1

This document has been provided for reference purposes only.
Every slide in this document must be modified and tailored to your client’s spe
objectives and reapproved by the Partner and GB&RC as per formal approval processes. The materials contained within the document may ha
different member firm and may not have relevance, or may have a different meaning, in your jurisdiction.
[Apptio Client 1]
Risks & Issues Log:
Apptio IT Financial Understanding

Implementation
For Internal Use Only
[2013]
*Confidential*
Risk Mitigation Target Status Update
Risk Title Impact Description Priority Reported by Reported Date Escalation Owner Status Strategy Mitigation Steps (Resource - Date) Comments Mitigated Risk
ID Date Date
Model refinement could Given the large and complex calculations in
60 lead to recurring the model, refinement and changes could H All [2013] [Name] [Name] TBD Closed [2013] Control & Deploy updates in a controlled method; One major workstream Creating a revised environment and y
Mitigate at a time, validating all months after the changes are made data migration process.
environment issues lead to more environment issues
Model refinement could Given the large and complex calculations in
60 lead to recurring the model, refinement and changes could H All [2013] [Name] [Name] TBD Closed [2013] Control & Deploy updates in a controlled method; One major workstream Creating a revised environment and y
Mitigate at a time, validating all months after the changes are made data migration tracking document
environment issues lead to more environment issues
The requirement to be able to reproduce

Budget Restatement results according to the various budget Control &
61 H [Name] [2013] [Name] [Name] [2013] Closed [2013] Evaluate Apptio solutions ([Name] - 4/25) y
Solutions restatements could require a complex, costly, Mitigate
and performance inhibiting solution

Budget Restatement results according to the various budget Control & [Name] has a documented process that
61 H [Name] [2013] [Name] [Name] [2013] Closed [2013] Decide and implement a solution ([Name]- TBD) has been tested. Need to review y
Solutions restatements could require a complex, costly, Mitigate results and get final approval
There is a risk that an additional contract

Contract Extension in extension for KPMG resources will not be Control & Work with [Name] to answer questions from Finance regarding
67 Jeopardy signed prior to (or upon) completion of H [Name] [2013] [Name] [Name] [2013] Closed [2013] Mitigate extension Moved to an Issue Y
current
There is a risk that an additional contract

67 Contract Extension in extension for KPMG resources will not be H [Name] [2013] [Name] [Name] [2013] Closed [2013] Control & Expedite transition Plan to [Apptio client name] Financial Moved to an Issue Y
Jeopardy signed prior to (or upon) completion of Mitigate Understanding Team ([Name],[Name],[Name],[Name])
current
Received e-mail confirmation on scpoe

adjustment for Showback ([Name]); Bill
68 Client Correspondance Need to collect client correspondence to L [Name] [2013] [Name] [Name] [2013] Closed [2013] Control & Collect e-mail for Bill of IT Scope adjustment of IT risk mitigated based on SOW Y
clarify scope Mitigate
wording and the capabilities we have
enabled for Bill of IT
Need to collect client correspondence to Control & Collect e-mail for Innotas implementation for Apptio Acceleration Received e-mail confirmation on scpoe
68 Client Correspondance L [Name] [2013] [Name] [Name] [2013] Closed [2013] Y
clarify scope Mitigate Plan adjustment ([Name])
Environment issues may Given the consistent issues with the Most environment improvement
59 cause delay in success environment, we are at risk for missing future M All [2013] [Name] [Name] TBD Closed [2013] Eliminate See issue #58 activities have been completed ([Name] y
Risk Event
deliverables deliverables deadlines - 5/21)
Manage Requirements and Change Requests; Check requests

Requirements change Frequent changes in requirements may lead Control &
8 frequently to an increase in defects and project delays L [Name] [2012] [Name] [Name] TBD Closed [2012] Mitigate against Project Plan and Critical Path; Sign-off for Change Same as risk #17 y
Requests
Transition from There is a risk that knowledge could be lost in

65 Development Team to the transition from the development team to L [Name] [2013] [Name] [Name] [2013] Open [2013] Control & Create run book for each work stream (All) n
Mitigate
Production Team the production team

Control &
65 Development Team to the transition from the development team to L [Name] [2013] [Name] [Name] [2013] Open [2013] Mitigate Script online training video (TBD) n
There is a risk that additional data sources Control & Most environment improvement
66 New Data Sources M [Name] [2013] [Name] [Name] TBD Closed [2013] Fix all current performance issues and risks ([Name]) activities have been completed ([Name] y
could negatively affect performance Mitigate - 6/11 )
There is a risk that additional data sources Control & Evaluate if Apptio has capacity to accept new data sources given
66 New Data Sources could negatively affect performance M [Name] [2013] [Name] [Name] TBD Closed [2013] Mitigate the environment at the time of request ([Name] & [Name]) y
13 Contingency planning has Contingency planning has not been developed L [Name] [2012] [Name] [Name] TBD Closed [2012] Eliminate Develop contingency plans; incorporate into project planning Combined with #19 y
not been addressed Risk Event
Enterprise or stakeholder communications are Develop communication plan and hierarchy; Conduct weekly
Insufficient Communication lacking, which could result in poor Control & status meetings; Identify Key Communication Checkpoints; Build
1 with clients/stakeholders requirements, scope, risk, status, and L [Name] [2012] [Name] [Name] TBD Closed [2013] Mitigate excel spreadsheet with what we are going to communicate, to y
duplicity of work who, when, communication method, purpose ([Name] - 10/12)
Enterprise or stakeholder communications are

1 Insufficient Communication lacking, which could result in poor L [Name] [2012] [Name] [Name] TBD Closed [2013] Control & Review communication plan with [Name] and [Name] ([Name] - Communication plan incorporated into y
with clients/stakeholders requirements, scope, risk, status, and Mitigate [2013]) weekly status ([Name] - 1/28)
duplicity of work
Frequent changes in requirements may result

Requirements change Control & Define change processes; leverage stage gates and agile methods
16 frequently in material changes to the agreed upon design L [Name] [2012] [Name] [Name] TBD Closed [2012] Mitigate to deter scope creep Same as risk #17 y
and result in project delays and scope creep
ID Date Date
Resources are not adequate to deliver Work Break Structure has been created
Lack of resources for solutions in parallel work streams, which Control & Develop Resource Plan; Ensure additional Apptio resources are distributing work across all resources.
2 L [Name] [2012] [Name] [Name] [2012] Closed [2013] made available to the engagement; Proactive communication y
parallel work streams could cause delays in configuration and Mitigate with Apptio resource managers Work structure is a cyclical with
delivery mutliple simultaneous workstreams
Lack of client SME support Appropriate users are not available to

3 during requirements participate in requirements elicitation and L [Name] [2012] [Name] [Name] TBD Closed [2013] Control & Identify SMEs; Start communications early and obtain buy-in from y
Mitigate appropriate stakeholders
activities analysis
Identify data sources and owners; Begin collection and analysis

May cause delays in schedule, a number of Control & efforts early; Proactively manage communication and collection
4 Client Data Availability other activities are dependant on getting data L [Name] [2012] [Name] [Name] TBD Closed [2013] Data collection process is underway y
in a timely manner Mitigate efforts; Develop data request log (complete); Communicate
request log to appropriate client stakeholders
Work with internal stakeholders, Data Center, and Apptio to

19 Production Environment Production environment hardware and H [Name] [2012] [Name] [Name] TBD Closed [2012] Eliminate order, install, and stand-up HW and SW; VPMO = 112473 [Name] Became an issue (#1) n
not ready or available software are not ready for use Risk Event
- [2012])
Production Environment Production environment hardware and Eliminate
19 H [Name] [2012] [Name] [Name] TBD Closed [2012] Define contingency planning ([Name] - [2013]) Became an issue (#1) n
19 Production Environment Production environment hardware and H [Name] [2012] [Name] [Name] TBD Closed [2012] Eliminate Develop a plan for cutover from development to production Became an issue (#1) n
not ready or available software are not ready for use Risk Event environments ([Name] - [2012])
Once Apptio team and KPMG Apptio expert
roll off the project, there may be a lack of Eliminate Configuration lead will be staffed from KPMG Apptio Dallas COE This will not be happening ([Name] -
32 Configuration Lead Risk H [Name] [2012] [Name] [Name] TBD Closed [2013] n
configuration experience and Apptio expertise Risk Event resource through Q2 2013 1/28)
on the team
Work Break Structure has been created

Leverage status and stand-up meetings to disseminate distributing work across all resources.
Teams/resources working in Teams work in silos to develop requirements Control & Configuration resources are included in
5 silos and design, resulting in integration issues L [Name] [2012] [Name] [Name] [2012] Closed [2013] Mitigate information, and ensure configurators are aware of all work being status meetings and internal daily y
performed meetings to set priorities and ensure
everyone is connected
Lack of business user

participation in system Lack of business user participation in the Control & Identify business users and owners; Begin collection and analysis We are working with stakeholders in
6 system design and validation, may result in L [Name] [2012] [Name] [Name] TBD Closed [2013] efforts early; Proactively manage communication and each work stream to ensure expert y
design and validation decreased quality Mitigate participation efforts (ongoing) advice is heeded ([Name] - 1/28)
activities
Work Break Structure has been created

distributing work across all resources.
Lack of Controls or No strategy to govern time, resources, and Develop work breakdown structure and project plan; Manage
7 Governance regarding configuration within Apptio; resulting in L [Name] [2012] [Name] [Name] [2012] Closed [2013] Control & communication across all resources; Proactively manage status Work structure is a cyclical with y
Mitigate mutliple simultaneous workstreams.
configuration diminished deliverables and stand-up meetings involving resources Weekly status meetings and internal
meetings are established
9 Environment/Instance The Apptio environment/instance is slow or L [Name] [2012] [Name] [Name] TBD Closed [2013] Control & Incorporate performance tuning into the project plan ([Name] - Performance tuning is a part of the y
performance issues experiencing communication errors Mitigate ongoing monitoring) Work Breakdown structure
Data conversion taking longer than expected

10 Data conversion lacks data due to incomplete data mapping, L [Name] [2012] [Name] [Name] TBD Closed [2013] Control & Plan for data mapping and gap analysis within the project plan See additional risks and issues for y
mapping configuration and development issues Mitigate and stage gates specific data source risks and issues
We do not currently have a backup Eliminate

24 No backup environment L [Name] [2012] [Name] [Name] [2012] Closed [2012] We will develop a backup and recovery plan ([Name] - [2012])) Same issue as #23 y
environment set up for development Risk Event
Both processs will be run in parallel for

Inadequate depth and breadth of cutover
11 Lack of comprehensive cut- planning, or cutover planning has not yet L [Name] [2012] [Name] [Name] [2012] Closed [2013] Eliminate Define cut-over plan, including back-up plan; run both versions in 3 months. After a variance anlysis, the y
over planning for CAT Risk Event parallel to start ([Name] - 9/28) final decision to conver to the Apptio
started CAT version will be made.
Timelines and budgets Timeline and budget constraints limit amount Control & Develop comprehensive testing plan and incorporate UAT into
12 of testing that can be complete before the L [Name] [2012] [Name] [Name] TBD Closed [2013] y
constrain testing system is placed into production Mitigate plan; define production change windows
KPMG, KGS, and Apptio resources are

Insufficient time and Insufficient time and resources to build and Control & Utilize additional resources from Apptio, KGS, and KPMG; fully engaged to assist with Build Phase.
14 unit test may result in delayed project L [Name] [2012] [Name] [Name] [2012] Closed [2013] y
resources for build phase deliverables Mitigate leverage internal knowledge and stakeholders for build Work Breakdown Structure includes
adequate timing for Build components
ID Date Date
Project teams are encouraged to configure

Configuration without Control & Add field to the design document that defines what the testing
26 testing the model without appropriate testing, which L [Name] [2012] [Name] [Name] TBD Closed [2012] Mitigate plans are ([Name] - [2012])) Same as risk #21 y
could lead to errors and delays
We currently do not have a plan to cut over

Complete the installation, take a snapshot of development
27 Production environment cut from the current development environment M [Name] [2012] [Name] [Name] TBD Closed [2012] Control & environment, and then put that snapshot into development Combined with #19 y
over plan to the production environment which could Mitigate
result in lost data and work ([Name] - [2012]))
Ambiguous requirements leading to

15 Ambiguous requirements inconclusive test cases and scenarios and poor L [Name] [2012] [Name] [Name] TBD Closed [2013] Control & Assess requirements at each stage gate; ensure stakeholder and y
Mitigate configurator sign-off at each stage gate
quality of configuration
17 No lock down of Lack of oversight or end date for L [Name] [2012] [Name] [Name] TBD Closed [2013] Control & Add requirements section to design document ([Name] - ongoing) Add design doc, tracker, etc y
requirements requirements changes (ie. Scope creep)* Mitigate
17 No lock down of Lack of oversight or end date for L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Create new reports request tracker ([Name] - [2012])) Add design doc, tracker, etc y
requirements requirements changes (ie. Scope creep)* Risk Event
Lack of resource training may result in an All developer resources have gone to
18 Need for developing inability for resource to deliver client L [Name] [2012] [Name] [Name] [2012] Closed [2013] Control & Ensure resources receive adequate training and ability to learn by Apptio training or are Apptio y
resource skills Mitigate working directly with the system,
requested functionality and project delays employees.
We need to develop a process for gathering

30 New requirements new requirements or else we will not meet L [Name] [2012] [Name] [Name] TBD Closed [2012] Eliminate Develop a requirements gathering plan ([Name] - TBD) Mitigated with risk #17 y
gathering Risk Event
client expectations
If we don't change the resource mix on the
31 Financial Risk engagement, we will have a shortfall at the H [Name] [2012] [Name] [Name] TBD Closed [2012] Eliminate Accelerate KGS engagement ([Name] - TBD) Not accelerating KGS Resources y
Risk Event
engagement close
If we don't change the resource mix on the Zuna Resource joining project 12/17,
31 Financial Risk engagement, we will have a shortfall at the M [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Accelerate roll off of Sr. Associates and communicate plan with and Sr. Associate rolling off project y
Risk Event stakeholders ([Name] - TBD)
engagement close 1/2013
31 Financial Risk engagement, we will have a shortfall at the H [Name] [2012] [Name] [Name] TBD Closed [2012] Eliminate Find alternative engagement codes for engagement management No alternative project codes y
Risk Event ([Name] - TBD)
engagement close
If we don't change the resource mix on the Eliminate Review Apptio burn rate versus original budget and determine Apptio burn rate proceeding according
31 Financial Risk engagement, we will have a shortfall at the L [Name] [2012] [Name] [Name] TBD Closed [2012] y
engagement close Risk Event financial plan ([Name] - [2012])) to schedule
Ineffective Knowledge Insufficient knowledge transfer from the Control & Incorporate knowledge transfer and end user training into project Operations run books and training
20 Transfer and End User project team to end users may cause usability L [Name] [2012] [Name] [Name] TBD Closed [2013] plan. Provide training/reference documentation. Set aside being provided to production staff y
Training issues Mitigate transfer additional checkpoints. ([Name] - 1/28)
Control &
21 UAT Testing Need to define UAT L [Name] [2012] [Name] [Name] TBD Closed [2013] Mitigate Add UAT section to design documents ([Name] - ongoing) y

32 Configuration Lead Risk roll off the project, there may be a lack of H [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Discussion will be held with new project leadership to determine Moved to issue (#36) n
configuration experience and Apptio expertise Risk Event longterm configuration lead ([Name] - [2013]))
on the team
52 Data Source Reconiliation We do not have a position on restatements H [Name] [2013] [Name] [Name] TBD Closed [2013] Control & We need to document a process for reconciliation (TBD) Consolidated with Risk# 61 n
and reconciliations Mitigate
If we use comment fields in the GL to map
22 Using comment fields as costs to cost pools, we risk losing data L [Name] [2012] [Name] [Name] TBD Closed [2013] Control & Discuss with team different mapping strategies and if this does Not using comment fields y
keys in GL mapping linkages as time continues as the comments Mitigate not work ask finance for a better field to key on
are often ignored or changed
We do not know who is responsible for

Current development maintaining and backing up the current Eliminate Determine who is responsible for maintaining and backing up the [Name] says Apptio takes daily backup;
23 development environment. If it were to go L [Name] [2012] [Name] [Name] [2012] Closed [2013] no tests on backups have been y
environment responsibility down or break, we would have to restart the Risk Event current working environment ([Name] - [2012]). performed yet
project
We do not know who is responsible for

maintaining and backing up the current [Name] says Apptio takes daily backup;
23 Current development development environment. If it were to go L [Name] [2012] [Name] [Name] [2012] Closed [2013] Eliminate Develop an understanding of our backup capabilities (([Name] - no tests on backups have been y
environment responsibility Risk Event [2012]))
down or break, we would have to restart the performed yet
project
Lack of data acquisiton We do not have a data acquisition process Eliminate

25 establsihed, which could lead to delays in data L [Name] [2012] [Name] [Name] [2012] Closed [2013] Develop a data inventory ([Name] - [2012]) y
process acquistion and thus delays in the project Risk Event
We do not have a data acquisition process

25 Lack of data acquisiton establsihed, which could lead to delays in data L [Name] [2012] [Name] [Name] [2012] Closed [2013] Eliminate Develop a formal data request document ([Name] - [2012]) y
process Risk Event
acquistion and thus delays in the project
ID Date Date
We do not have a data acquisition process

Lack of data acquisiton Eliminate
25 process establsihed, which could lead to delays in data L [Name] [2012] [Name] [Name] [2012] Closed [2013] Risk Event Assign a point person for all data requests ([Name] - ongoing) y
acquistion and thus delays in the project
If we do not have plan for what cost pools or

28 Work Stream 2 does not products to map first, we will not know our L [Name] [2012] [Name] [Name] [2012] Closed [2013] Control & Work with [Name] to develop a priority listing of our working Review each iteration plan with y
have a detailed plan Mitigate objects ([Name] - [2012]) [Name]and [Name]
status and potentially delay the product

Work Stream 2 does not Control & Review each iteration plan with [Name]
28 have a detailed plan products to map first, we will not know our L [Name] [2012] [Name] [Name] [2012] Closed [2013] Mitigate Develop and maintain a 90 day work plan ([Name] - [2012]) and [Name] y

28 Work Stream 2 does not products to map first, we will not know our L [Name] [2012] [Name] [Name] [2012] Closed [2013] Control & Finalize work plan and stakeholdered ([Name] - [2012]) Review each iteration plan with y
have a detailed plan Mitigate [Name]and [Name]
If we do not continuously update LCAP we will Determine if we need to add resources to continue updating LCAP [Name] spoke with [Name] and
go live with a cost model that is out of date Control & confirmed we should focus on Apptio
29 LCAP not being updated and will require significant immediate updates L [Name] [2012] [Name] [Name] [2012] Closed [2013] Mitigate or go forward with the notion we will go live with an outdated and not updating LCAP going forward y
model ([Name] - [2012])
to be relevant (10/1/2012)
We cannot keep up with changes in the GL

34 Changing GL and RC and RC structure so our analysis could be M [Name] [2012] [Name] [Name] TBD Closed [2012] Control & Try to be proactive by having an open dialogue with finance and y
Structure delayed and impacted as we resolve breakage Mitigate solve issues once they arise ([Name] - TBD[Name] - [2012])
on a monthly basis

31 Financial Risk engagement, we will have a shortfall at the L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Add tab to financial management workbook to manage Apptio y
Risk Event costs ([Name] - [2012])
engagement close
31 Financial Risk engagement, we will have a shortfall at the L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Build director hours into project addendum ([Name] - [2012]) y
Risk Event
engagement close
57 Move from 2 Bell If we move from the 2 Bell location, we may L [Name] [2013] [Name] [Name] TBD Closed [2013] Control & Work remotely from KPMG office y
experience a decrease in productivity Mitigate

32 Configuration Lead Risk roll off the project, there may be a lack of L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Transition Apptio resources into reviewers rather than doers Y
configuration experience and Apptio expertise Risk Event ([Name] - [2012])
on the team

roll off the project, there may be a lack of Eliminate Build a process to approve and review KGS configuration ([Name]
32 Configuration Lead Risk L [Name] [2012] [Name] [Name] TBD Closed [2013] Y
configuration experience and Apptio expertise Risk Event - [2012])
on the team

32 Configuration Lead Risk roll off the project, there may be a lack of L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Develop design plan for 2013 [Name] - [2012]) Y
configuration experience and Apptio expertise Risk Event
on the team
If we move from the 2 Bell location, we may Control &

57 Move from 2 Bell experience a decrease in productivity L [Name] [2013] [Name] [Name] TBD Closed [2013] Mitigate Find new space at [Apptio client] y

Offline solution created; KGS
61 Budget Restatement results according to the various budget L [Name] [2013] [Name] [Name] [2013] Closed [2013] Control & Develop an "off line" solution to extract dataset from current Resources are running offline process Y
Solutions restatements could require a complex, costly, Mitigate Apptio model; Enable KGS Resources to perform extraction
and performance inhibiting solution on a monthly basis.
33 GL Pull Risk Need to confirm the fields for the GL pull so L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Work with finance to finalize the GL pull ([Name] - [2012]) GL pull is correct ([Name] - 2/19) y
the correct data is pulled each month Risk Event
Employees do not use new Employees may be slow to adapt and use Control & Create a communication document for the ITO newsletter to RPOCs have provided training and we
35 PMTs, thus reducing the effectiveness of the L [Name] [2012] [Name] [Name] TBD Closed [2013] will be doing compliance testing y
PMTs PMT Realignment effort Mitigate inform employees of upcoming change ([Name] - [2012]) ([Name] - 1/28)
Employees may be slow to adapt and use RPOCs have provided training and we
Employees do not use new Control & Create a training document for employeese to use ([Name] -
35 PMTs PMTs, thus reducing the effectiveness of the L [Name] [2012] [Name] [Name] TBD Closed [2013] Mitigate [2012]) will be doing compliance testing y
PMT Realignment effort ([Name] - 1/28)
Employees may be slow to adapt and use RPOCs have provided training and we
Employees do not use new Control & Set up a meetings with all of the RPOCs and define the new PMT
35 PMTs, thus reducing the effectiveness of the L [Name] [2012] [Name] [Name] TBD Closed [2013] will be doing compliance testing y
PMTs Mitigate process and their responsibilities ([Name] - [2012])
PMT Realignment effort ([Name] - 1/28)
36 RPOCS may not load new A delay in the loading of the PMT codes could L [Name] [2012] [Name] [Name] TBD Closed [2013] Control & Ensure that the Chief of Staff is in charge of loading the PMTs All organizations have entered new y
PMTs delay effective reporting Mitigate ([Name] - 11/30) PMT codes (12/13/2012)
If RPOCs do not control the maintenance of
RPOCS may not load new Control & Ensure that the Chief of Staff is in charge of loading the PMTs All organizations have entered new
36 PMTs the PMT codes, they could grow in number L [Name] [2012] [Name] [Name] TBD Closed [2013] Mitigate ([Name] - 11/30) PMT codes (12/13/2012) y
and complexity again
ID Date Date
If RPOCs do not control the maintenance of Have a soft rollout of the new PMTs for certain groups that are
RPOCS may not load new Control & All organizations have entered new
36 PMTs the PMT codes, they could grow in number L [Name] [2012] [Name] [Name] TBD Closed [2013] Mitigate ready to use the new PMTs and complete the transition in January PMT codes (12/13/2012) y
and complexity again with the reamining organizations ([Name] - [2012])
If a person is not identified for maintaining

Maintenance of [Apptio Team knows the process for opening a
37 Client Name]'s Apptio the [Apptio Client Name] Apptio Production L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Identify the person responsible for monitoring storage capacity ticket with Apptio Technical Operations y
environment, there is a risk of overrunning Risk Event and memory usage ([Name] - TBD)
Production environment storage capacity and memory Center (12/13/2012)
LCAP testing is running long, which could

41 LCAP Testing Running Long result in the team missing the 12/14 testing L [Name] [2012] [Name] [Name] [2012] Closed [2013] Eliminate Work with Apptio to understand Event Count model configuration Testing complete ([Name] - 2/19) y
Risk Event ([Name] - [2012])
deadline, thus delaying the go-live
LCAP testing is running long, which could Eliminate

41 LCAP Testing Running Long result in the team missing the 12/14 testing L [Name] [2012] [Name] [Name] [2012] Closed [2013] Rebuild reports ([Name] - [2012]) Testing complete ([Name] - 2/19) y
deadline, thus delaying the go-live Risk Event
LCAP testing is running long, which could

41 LCAP Testing Running Long result in the team missing the 12/14 testing L [Name] [2012] [Name] [Name] [2012] Closed [2013] Eliminate Run pass 2 of event count and cycle time tests ([Name] - [2012]) Testing complete ([Name] - 2/19) y
Risk Event
deadline, thus delaying the go-live
LCAP testing is running long, which could Eliminate

41 LCAP Testing Running Long result in the team missing the 12/14 testing L [Name] [2012] [Name] [Name] [2012] Closed [2013] Accelerate hours, headcount, and cost testing ([Name] - [2012]) Testing complete ([Name] - 2/19) y
deadline, thus delaying the go-live Risk Event
If the design document isn't finalized shortly, Eliminate Decision has been to keep design
42 TCO Design Document Delay configuration and implementation will be L [Name] [2012] [Name] [Name] [2012] Closed [2013] Complete and finalize high level design overview ([Name] - [2012]) document an internal focus ([Name] - y
delayed Risk Event 2/4/2013)
If the design document isn't finalized shortly, Eliminate Add resources to aid in finalizing document and to aid in Decision has been to keep design
42 TCO Design Document Delay configuration and implementation will be L [Name] [2012] [Name] [Name] [2012] Closed [2013] document an internal focus ([Name] - y
delayed Risk Event configuration ([Name] - TBD) 2/4/2013)
If the design document isn't finalized shortly, Eliminate Decision has been to keep design
42 TCO Design Document Delay configuration and implementation will be L [Name] [2012] [Name] [Name] [2012] Closed [2013] Accelerating configuration to ensure design is valid ([Name] - TBD) document an internal focus ([Name] - y
delayed Risk Event 2/4/2013)
If a person is not identified for maintaining

Maintenance of [Apptio Team knows the process for opening a
37 Client Name]'s Apptio the [Apptio Client Name] Apptio Production L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Identify the person responsible for updates, patches, and bug ticket with Apptio Technical Operations y
environment, there is a risk that the tool Risk Event fixes ([Name] - TBD)
Production environment could miss upgrades, patches, and bug fixes Center (12/13/2012)
We need to onboard the new client Eliminate

38 Change in client leadership leadership into the project to ensure the L [Name] [2012] [Name] [Name] TBD Closed [2013] Update client on history and status of project ([Name] - TBD) y
project is proceeding on the correct path Risk Event
We need to onboard the new client

Eliminate Create a high level Financial Understanding history deck for [Name] has created deck with slides
38 Change in client leadership leadership into the project to ensure the L [Name] [2012] [Name] [Name] TBD Closed [2013] Risk Event discussion ([Name] - 1/2013) that can be reused y
project is proceeding on the correct path
Eliminate Discuss project plan and strategy going forward with new client
38 Change in client leadership leadership into the project to ensure the L [Name] [2012] [Name] [Name] TBD Closed [2013] Risk Event ([Name] - 1/2013) Reviewing initial draft on 12/14 y
If we do not get the IBM software data in
Eliminate
45 Software data time, we will not have enough time to H [Name] [2013] [Name] [Name] TBD Closed [2013] Risk Event Speak with [Name] and get software data ([Name] - 1/24/2013) Information received ([Name] - 1/28) y
perform adequate analysis
38 Change in client leadership leadership into the project to ensure the L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Discuss plan for January meeting with [Name] to look at where y
Risk Event Apptio is going ([Name] - 1/2013)
38 Change in client leadership leadership into the project to ensure the L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Discuss plan for January meeting with [Name] to look at where y
Risk Event Apptio is going ([Name] - 1/2013)
We need to clarify the organizational scope of
48 IT vs. ITO Scope Clarification work to ensure we produce the correct M [Name] [2013] [Name] [Name] [2013] Closed [2013] Eliminate Define the scope ([Name] - TBD) [Name] will add memo to the work y
Risk Event papers
reports
We need to determine how to best build and
39 Apptio COE Capabilities use the capabilities of the KPMG Apptio COE L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate As the COE is more fully developed, create plans for [Apptio Client y
longterm Risk Event Name] support([Name] - TBD)
We need to determine how to best build and Eliminate As Zuna's capabilities are ascertained, create plans for [Apptio
39 Apptio COE Capabilities use the capabilities of the Zuna Resources L [Name] [2012] [Name] [Name] TBD Closed [2013] y
COE longterm Risk Event Client Name] support ([Name] - TBD)
ID Date Date
If the Ito Reorganization occurs over the next
5-7 weeks, significant changes will need to be Eliminate Discuss specific LCAP implications and develop revised technical
40 ITO Reorganization made to our project plan, resource plan, and L [Name] [2012] [Name] [Name] TBD Closed [2013] Risk Event plan aligned with pending reorg ([Name] - 12/3/2012) y
deliverables
Delay in additional KGS If the hiring of an additional KGS resource is Eliminate Resource is on project ([Name] -
43 delayed, it could delay the delivery of TCO and L [Name] [2013] [Name] [Name] TBD Closed [2013] Speak with [Name] ([Name] - 1/25/2012) y
Resource additional Apptio deliverables Risk Event 2/4/2013)
Resource plan for If we don't get the resources for acceleration Eliminate Work with Zuna and Apptio to quickly identify and allocate
44 in a timely manner, we will miss the window L [Name] [2013] [Name] [Name] [2013] Closed [2013] In progress ([Name] -1/28) y
acceleration of acceleration needed to get the work done Risk Event resources to the project ([Name] - 1/25)
If we don't get the resources for acceleration

Resource plan for Eliminate Develop Statement of Works for Zuna and Apptio to enable new
44 acceleration in a timely manner, we will miss the window L [Name] [2013] [Name] [Name] [2013] Closed [2013] Risk Event resources to begin working ([Name] - TBD) In progress ([Name] -1/28) y
of acceleration needed to get the work done
Resource plan for If we don't get the resources for acceleration Eliminate Streamline onboarding process: badges, cubes, ATT Connect
44 in a timely manner, we will miss the window L [Name] [2013] [Name] [Name] [2013] Closed [2013] y
acceleration of acceleration needed to get the work done Risk Event ([Name] - TBD)
Production Environment Production environment hardware and Eliminate

19 L [Name] [2012] [Name] [Name] TBD Closed [2012] Confirm validity of weekly backups ([Name] - 10/23) Became an issue (#1) n
We need to be aware of and monitor any
Control & Ensure that [Name] and [Name] keep KPMG team in the loop for
46 LCAP+ Design Changes change the LCAP+ design methodology in L [Name] [2013] [Name] [Name] N/A Closed [2013] Mitigate model changes y
order to maintain structural integrity
We need to define the scope for what is

Eliminate
47 TCO Scope Definition included in TCO A3 (Data Center) or else we L [Name] [2013] [Name] [Name] [2013] Closed [2013] Risk Event Define the scope ([Name] - 2/8) y
risk not meeting the requirement in the SOW
There is a risk that the ITO towers will not Eliminate LCAP being communicated by [Name]
49 LCAP+ Communication cooperate with the LCAP+ effort L [Name] [2013] [Name] [Name] TBD Closed [2013] Risk Event Create training documents ([Name] - TBD) and [Name] (4/16) y
There is a risk that the ITO towers will not Eliminate LCAP being communicated by [Name]
49 LCAP+ Communication L [Name] [2013] [Name] [Name] TBD Closed [2013] Create communication documents ([Name] - TBD) y
cooperate with the LCAP+ effort Risk Event and [Name] (4/16)
50 Environment Maintenance We need to be more prepared to onboard the L [Name] [2013] [Name] [Name] [2013] Closed [2013] Eliminate Create a draft roles and responsibilities and send to [Name] and [Name], [Name], and [Name] are all on y
Chief Architect Risk Event [Name] for input ([Name] - 3/5) the team and working (4/16)
50 Environment Maintenance We need to be more prepared to onboard the L [Name] [2013] [Name] [Name] [2013] Closed [2013] Eliminate Go through existing slideware and create a Financial [Name], [Name], and [Name] are all on y
Chief Architect Risk Event Understanding & Apptio story ([Name] - 3/7) the team and working (4/16)
We need a process around User ID Eliminate Operational with [Name] and [Name]
50 Environment Maintenance administration L [Name] [2013] [Name] [Name] [2013] Closed [2013] Risk Event Assign this responsibility to a client team member ([Name] - 3/15) (4/16) y
[Name] Potential Loss of We may not have the ability to pull AOTS Eliminate [Name] should download the tool and be able to pull tickets
58 H [Name] [2013] [Name] [Name] [2012] Closed [2013] [Name] has tool y
AOTS tool tickets if [Name] lost his AOTS tool Risk Event ([Name] - 4/20)
58 [Name] Potential Loss of We may not have the ability to pull AOTS H [Name] [2013] [Name] [Name] [2012] Closed [2013] Eliminate [Name] should redownload the tool and instruct the team how to [Name] has tool y
AOTS tool tickets if [Name] lost his AOTS tool Risk Event download it if is lost ([Name] - 4/27)
50 Environment Maintenance We need a process around User ID L [Name] [2013] [Name] [Name] [2013] Closed [2013] Eliminate Create the process documentation ([Name] - 3/15) Operational with [Name] and [Name] y
administration Risk Event (4/16)
We do not know how utilized the KGS Control & We need to document a process for managing KGS resources KGS Activity Tracker in use ([Name] -
51 KGS Activity Insight resources are and what their role will be going L [Name] [2013] [Name] [Name] TBD Closed [2013] y
forward Mitigate (TBD) 3/26)

61 Budget Restatement results according to the various budget H [Name] [2013] [Name] [Name] [2013] Closed [2013] Control & Discuss and finalize requirements with [Name] ([Name] - 4/23) Y

32 Configuration Lead Risk roll off the project, there may be a lack of L [Name] [2012] [Name] [Name] TBD Closed [2013] Eliminate Apptio will be configuration lead through Q1 2013 n
on the team

61 Budget Restatement results according to the various budget H [Name] [2013] [Name] [Name] [2013] Closed [2013] Control & Build offline solution ([Name] - 4/25) Y
We do not have a good mechanism to validate

Control & Schedule recurring weekly meetings with stakeholders to deep [Name] scheduled recurring meeting
53 Results Validation results without extensive, recurring meetings L [Name] [2013] [Name] [Name] [2013] Closed [2013] Mitigate dive into one specific topic ([Name] - 3/8) (3/5) y
with stakeholders
62 Environment partition for How do we partition the environment for H [Name] [2013] [Name] [Name] TBD Closed [2013] Control & Apptio developed att-sandbox environment ([Name] - 4/30) Sandbox is up and running (JMS 5/14) y
future development development after July 2013? Mitigate
ID Date Date
The business objects reporting tool is down

Control &
63 May 2013 MOTS Pull which may cause us to miss the May 1 H [Name] [2013] [Name] [Name] TBD Closed [2013] Mitigate Do the pull as soon as Business Objects is back up ([Name] - TBD) MOTS pull occurred (JMS 5/14) y
requirement to pull MOTS information
We need to build a relationship with Cody Control &

54 Relationship with finance Reed so we can effectively build Apptio L [Name] [2013] [Name] [Name] [2013] Closed [2013] Mitigate Schedule meeting with [Name] ([Name] - 3/13) [Name] held meeting on 3/13 y

65 Development Team to the transition from the development team to M [Name] [2013] [Name] [Name] [2013] Closed [2013] Control & Assign production team member to each work stream ([Name]) y
Mitigate
We need to ensure we have multiple contacts

Control &
54 Relationship with finance within finance in case there are organizational L [Name] [2013] [Name] [Name] [2013] Closed [2013] Mitigate Team has many finance contacts y
changes
Indirect allocation How do we restrict indirect allocations to Control & Work with stakeholders to identify these restrictions during Strategies in place as of 4/12 deadline
55 L [Name] [2013] [Name] [Name] [2013] Closed [2013] y
restrictions known asset buckets? Mitigate discovery and enhance during stakeholder validations (TBD) (4/17)
We need a procedure and artifacts to share

with KGS to keep them informed of model Control & Schedule a regular, recurring review session with KGS ([Name] -
56 KGS Model Knowledge enhancements and changes so they are in L [Name] [2013] [Name] [Name] TBD Closed [2013] Mitigate 3/15); twice a month for now y
sync with the on-shore dev teams

32 Configuration Lead Risk roll off the project, there may be a lack of L [Name] [2012] [Name] [Name] TBD Closed [2012] Eliminate Accelerate hiring of KGS resource ([Name] - 11/2012) y
on the team

roll off the project, there may be a lack of Eliminate Discuss Apptio post July 2013 maintenance plan with [Name]
32 Configuration Lead Risk L [Name] [2012] [Name] [Name] TBD Closed [2012] y
configuration experience and Apptio expertise Risk Event ([Name] - 12/2012)
on the team

32 Configuration Lead Risk roll off the project, there may be a lack of L [Name] [2012] [Name] [Name] TBD Closed [2012] Eliminate Determine roll off of current Apptio Architecht so succession plan y
configuration experience and Apptio expertise Risk Event can be developed ([Name] - 10/30)
on the team

roll off the project, there may be a lack of Eliminate KPMG team will develop multiple roles and responsibilities
32 Configuration Lead Risk L [Name] [2012] [Name] [Name] TBD Closed [2012] scenarios for longterm Apptio/Financial Understanding support y
configuration experience and Apptio expertise Risk Event for [Name]'s to consider ([Name] - 12/30)
on the team
TCO clean up efforts may Current resources are staffed on multiple,

64 delay execution of new concurrent work streams and may be delayed L [Name] [2013] [Name] [Name] TBD Closed [2013] Control & TBD y
Mitigate
work streams in executing new work activities
Front Door process is up and running.

66 New Data Sources There is a risk that additional data sources L [Name] [2013] [Name] [Name] TBD Closed [2013] Control & Send all new requests through the Apptio front door (All) New work is discussed, prioritized, and Y
could negatively affect performance Mitigate
distributed to team for completion
Conducted review meeting with

Apptio Release 11 Risk of creating issues within our current Control & Reach out to [Name] (KPMG Apptio team) for recommendations
68 Implementation model. M [Name] [2013] [Name] [Name] [2013] Closed [2013] Mitigate and insight [Name] to get insight into Apptio V11 y
upgrade
68 Apptio Release 11 Risk of creating issues within our current M [Name] [2013] [Name] [Name] [2013] Closed [2013] Control & Reach out to Zuna to get perspective on upgrade Receive feedback from Zuna on y
Implementation model. Mitigate upgrade
68 Apptio Release 11 Risk of creating issues within our current L [Name] [2013] [Name] [Name] [2013] Closed [2013] Control & Request meeting with Apptio to discuss Release 11 & impact to Mitigated y
Implementation model. Mitigate [Apptio Client Name] implementation
We are not allocating ITO Labor associated

69 Tickets to Apps Labor with Applications to ITO Assets; Currently it is M [Name] [2013] [Name] [Name] [2013] Closed [2013] Eliminate Discuss implications with [Name]s Reviewed with [Name]during status y
Risk Event meeting.
being allocated directly to the App
We are not allocating ITO Labor associated

Eliminate per [Name]s we are not changing the
69 Tickets to Apps Labor with Applications to ITO Assets; Currently it is L [Name] [2013] [Name] [Name] [2013] Closed [2013] Risk Event Determine when/if we need to adjust our allocation strategy allocation Y
being allocated directly to the App
We are not approved to work on any activities Eliminate Will leverage [Name] and [Name]'s guidance on prioritizing Will leverage [Name]and [Name]'s
70 New Requests from Finance related to providing new reports/data to L [Name] [2013] [Name] [Name] [2013] Closed [2013] guidance on prioritizing activities via y
Finance Risk Event activities via the Front Door process. the Front Door process.
Apptio Release 11.1 Current release of Apptio already has a patch Control &
71 M [Name] [2013] [Name] [Name] [2013] Open [2013] Current release must mature prior to an [Apptio Client 1] Upgrade n
Implementation fix and there questions about stability. Mitigate
Apptio Release 11.1 Current release of Apptio already has a patch Control &
71 Implementation fix and there questions about stability. M [Name] [2013] [Name] [Name] [2013] Open [2013] Mitigate Apptio to provide information regarding stability of release n
Issue Mitigation Status Update
ID Issue Title Impact Description Priority Reported by Reported Date Escalation Owner Target Date Status Date Strategy Mitigation Steps (Resource - Date) Comments Closed Issue
Delay in Apptio Installation of Apptio hardware and

1 environment software at [Apptio Client] has been H [Name] 9/25/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event Ensure Apptio environment installed DR completed 12/12/2012 y
installation delayed leading to recovery and backup correctly ([Name] - 11/15)
risks
Delay in Apptio Installation of Apptio hardware and Notify Apptio leadership that 11/15
software at [Apptio Client] has been
1 environment delayed leading to recovery and backup H [Name] 9/25/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event completion date cannot slide ([Name] - DR completed 12/12/2012 y
installation risks 10/31)
Installation of Apptio hardware and

Delay in Apptio software at [Apptio Client] has been
1 environment L [Name] 9/25/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event Get delivery date from VPMO data Apptio planned to be installed by 10/23 y
installation delayed leading to recovery and backup ([Name] - 10/12)
risks
[Name] discussed with [Name]. UAT

will consist of the following:
Need to define UAT for Workstream 2 1. Compare KPIs involving headcount,
2 UAT Testing and Workstream 3 H [Name] 9/19/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event Discuss with [Name] ([Name] - 9/26) hours, and event counts to LCAP y
2. Put UAT in design document and
evaluate versus that
Training Material We have not defined or planned support

3 and training activities for eventual end M [Name] 9/19/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event Moved to risk log as it has not occurred Deleted from risk log as duplicate y
Development yet already existed
users
We do not currently have the

Lack of defined requirements for how often Apptio
4 reporting H [Name] 9/20/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event Top 10 Reporting Requirements List as y
reports must be created and distributed directed by business([Name] - 10/12)
requirements for WS2 for WS2
Lack of defined We do not currently have the Develop 90 day work plans ([Name] -
4 reporting requirements for how often Apptio H [Name] 9/20/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event 10/12) y
requirements for WS2 reports must be created and distributed
for WS2
Lack of defined We do not currently have the

4 reporting requirements for how often Apptio H [Name] 9/20/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event Design documents describing the y
reports must be created and distributed requirements ([Name] - ongoing)
requirements for WS2 for WS2
We have not assigned a resource to be Assign resource to focus/concentrate KGS has been assigned to be primarliy
5 Reporting resource not responsible for the creation and H [Name] 9/20/2012 [Name] [2012] Closed [2012] Eliminate Issue Event on building Apptio reports; Include responsible for configuring Apptio y
assigned distribution of Apptio reports specific activities in the Work reports
Breakdown Structure
We do not have assignments for who Create invetory list of all data sources;
6 Data providers not will be providing data for input into H [Name] 9/20/2012 [Name] [2012] Closed [2012] Eliminate Issue Event Leverage contacts and work completed Data providers for all data sources have y
assigned Apptio in Apptio POV; Leverage contacts from been identified
current CAT and LCAP process
Transition from WS1 We have not discussed the timeframe 1. Create and publish CAT playbook and
7 CAT to WS2 CAT not where WS2 starts and how to transition H [Name] 9/21/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event cutover to Apptio implementation plan Potential for WS1 CAT to be run until y
defined from WS1 CAT to WS2 CAT ([Name] - 10/2012) completion of WS3
Historical data We can load historical totals as needed,

8 requirements for WS2 We have not developed historical data H [Name] 9/21/2012 [Name] TBD Closed [2012] Eliminate Issue Event but all data sources may not have y
not defined requirements for WS2 historical data
Should management We have not determined how Discuss with [Name] and consider
9 be included in LCAP management salaries will flow through H [Name] 9/24/2012 [Name] [Name] TBD Closed [2012] Eliminate Issue Event contacting IT Finance and HR to finalize This is a question, not an issue y
the conceptual model or how the HR
KPIs reports align with GL categories decision ([Name] - 10/12)
Explain variance to stakeholders and fix Discussed with client and fixed in future
10 Nilson error in Error in formula in CAT Report by VP L [Name] 9/1/2012 [Name] TBD Closed [2012] Control & Mitigate in CAT Report by VP document ([Name] y
historical CAT document from 2010 - June 2012 - 9/27) CAT output
In order for drill down reporting to

occur, the event mapping must align Work with the event structure to align
11 RC to Event Mapping with the RC heirarchy. However, LCAP L [Name] 9/26/2012 [Name] [Name] TBD Closed [2013] Control & Mitigate better with the RC structure ([Name] - No plans to do this ([Name] 2/5/2013) y
Not Aligned was not designed with RC's in mind 10/12)
directly leading to a disconnect in
certain instances
In order for drill down reporting to

occur, the event mapping must align
11 RC to Event Mapping with the RC heirarchy. However, LCAP L [Name] 9/26/2012 [Name] [Name] TBD Closed [2013] Control & Mitigate Update LCAP in the future along lines of No plans to do this ([Name] 2/5/2013) y
Not Aligned was not designed with RC's in mind RCs rather than COC ([Name] - ongoing)
directly leading to a disconnect in
certain instances
We currently do not have a good

12 GL starting point understanding of which file is our H [Name] 9/28/2012 [Name] [Name] [2012] Closed [2012] Eliminate Issue Event Develop a starting GL file ([Name] - Starting with May 2012 y
unclear starting GL 10/5/2012)
KGS resource does not Without access to [Apptio Client]

13 have access to the internet, the KGS resource experiences H [Name] 9/28/2012 [Name] [Name] [2012] Closed [2012] Eliminate Issue Event Work with KGS and [Apptio Client] to y
[Apptio Client] intranet delays in client delivery provide access ([Name] - 10/5/2012)
This one to many relationship makes

14 XCs mapping to mapping XC relationships much more L [Name] 10/9/2012 [Name] [Name] [2012] Closed [2012] Eliminate Issue Event Discuss with finance ([Name] - 10/16) y
multiple Report Lines difficult and less clean
Given that an individual RC in the GL can

map to multiple LCAP events, it makes Get April and June 2012 and test vs.
15 LCAP Complexity the initial mapping and subsequent H [Name] 10/11/2012 [Name] [Name] [2012] Closed [2012] Control & Mitigate May mapping to determine RC fallout Breakage determined to be y
maintenance effort extremely complex and how many RCs map to multiple IT manageable ([Name] - 10/18)
and unmaintainable resources ([Name] - 10/19)

map to multiple LCAP events, it makes
15 LCAP Complexity the initial mapping and subsequent L [Name] 10/11/2012 [Name] [Name] [2012] Closed [2013] Control & Mitigate Finalize requirements for LCAP+ phase Design document approved ([Name] - y
maintenance effort extremely complex ([Name] - 10/19) 2/5)
and unmaintainable

map to multiple LCAP events, it makes Building a SharePoint site so LCAP
15 LCAP Complexity the initial mapping and subsequent L [Name] 10/11/2012 [Name] [Name] [2012] Closed [2013] Control & Mitigate contacts can put volumes on site to SharePoint built ([Name] - 2/5) y
maintenance effort extremely complex ease in effort to load Apptio ([Name] -
and unmaintainable 10/30)

map to multiple LCAP events, it makes
15 LCAP Complexity the initial mapping and subsequent L [Name] 10/11/2012 [Name] [Name] [2012] Closed [2013] Control & Mitigate Run labor breakage reports ahead of Process is made ([Name] - 2/5) y
maintenance effort extremely complex formalized monthly reporting
and unmaintainable
We cannot keep up with changes in the Try to be proactive by having an open

16 Changing GL and RC GL and RC structure so our analysis M [Name] 10/11/2012 [Name] [Name] TBD Closed [2012] Control & Mitigate dialogue with finance and solve issues Moved to risk log y
Structure could be delayed and impacted as we once they arise ([Name] - TBD)
resolve breakage on a monthly basis
Vendor contract regulations prohibit

17 Vendor Contract detailed viewing by 3rd party H [Name] 10/12/2012 [Name] [Name] TBD Closed [2012] Control & Mitigate Escalate to leadership ([Name] - TBD) n
Regulations contractors
Vendor Contract Vendor contract regulations prohibit Investigate Apptio's ability to hide fields Apptio can block certain user types
17 Regulations detailed viewing by 3rd party H [Name] 10/12/2012 [Name] [Name] TBD Closed [2012] Control & Mitigate and data sets ([Name] - 10/15) from seeing certain information n
contractors (12/13/2012)
Request legal to review current vendor Per [Apptio Client] Legal, KPMG NDA
Vendor Contract Vendor contract regulations prohibit contract language and KPMG NDA are not sufficient to gain access to MAC
17 Regulations detailed viewing by 3rd party H [Name] 10/12/2012 [Name] [Name] TBD Closed [2012] Control & Mitigate forms to see if they suffice ([Name] - HW and SW information ([Name] - n
contractors TBD) 10/29)
Vendor contract regulations prohibit Have [Name] load confidential data into [Name] or [Apptio Client] profile can be
17 Vendor Contract detailed viewing by 3rd party H [Name] 10/12/2012 [Name] [Name] TBD Closed [2012] Control & Mitigate set up with exclusive access to secured n
Regulations private data set ([Name] - TBD)
contractors data (12/13/2012)
Ask Apptio to provide an approach

Vendor Contract Vendor contract regulations prohibit paper to send to stakholders, Technical information received,
17 Regulations detailed viewing by 3rd party H [Name] 10/12/2012 [Name] [Name] TBD Closed [2012] Control & Mitigate leadership, and legal for approval given summary made, and presentation has n
contractors that KPMG and Apptio cannot get been given to ALM team (12/10/2012)
detailed MAC data ([Name] - 10/31
Vendor contract regulations prohibit Create an executive summary of the Technical information received,
17 Vendor Contract detailed viewing by 3rd party H [Name] 11/26/2012 [Name] [Name] TBD Closed [2012] Control & Mitigate Apptio provided redaction document summary made, and presentation has n
Regulations contractors ([Name] - 11/30) been given to ALM team (12/10/2012)
Vendor contract regulations prohibit Hold meeting with Audit and Legal
17 Vendor Contract detailed viewing by 3rd party H [Name] 11/26/2012 [Name] [Name] TBD Closed [2012] Control & Mitigate teams to get sign off on redaction
Not necessary as converstaion with n
Regulations ALM team is sufficient (12/10/2012)
contractors summary document ([Name] - TBD)
Vendor contract regulations prohibit ALM team will provide information

17 Vendor Contract detailed viewing by 3rd party H [Name] 11/26/2012 [Name] [Name] TBD Closed [2013] Control & Mitigate related to IBM Software contract and Data received ([Name] - 1/28) n
Regulations contractors Apptio will prove allocation strategies
using IBM data ([Name] - 1/25)
Vendor Contract Vendor contract regulations prohibit Receive software rate card from ALM Software rate card received ([Name] -
17 Regulations detailed viewing by 3rd party H [Name] 11/26/2012 [Name] [Name] TBD Closed [2013] Control & Mitigate team ([Name] - 1/25) 2/5) n
contractors
Vendor contract regulations prohibit Agenda for meeting: Apptio demo,

Vendor Contract Establish meeting date with [Name] and redaction overview, results of IBM
17 Regulations detailed viewing by 3rd party H [Name] 11/26/2012 [Name] [Name] TBD Closed [2013] Control & Mitigate [Name] ([Name] - 1/25) $150M allocation, set up monthly n
contractors meeting with [Name]
Confirm that meeting with [Name] and

Vendor contract regulations prohibit Rebecca occurred (4/9); still need to
17 Vendor Contract detailed viewing by 3rd party H [Name] 11/26/2012 [Name] [Name] TBD Closed [2013] Control & Mitigate Finalize plan for software (TBD) implement and test redaction; [Name] y
Regulations
contractors and [Name] committed to completing
redaction by (4/29)
Get an extract of sensitive data with

Vendor contract regulations prohibit
17 Vendor Contract detailed viewing by 3rd party L [Name] 10/12/2012 [Name] [Name] TBD Closed [2013] Control & Mitigate fields set to 0's and have [Name] upload ALM Team has decided what they're n
Regulations contractors to Apptio so model can be configured giving us ([Name] - 1/28)
([Name] - 10/30)
Vendor contract regulations prohibit Provide ALM team specific fields, data
17 Vendor Contract detailed viewing by 3rd party L [Name] 11/26/2012 [Name] [Name] TBD Closed [2013] Control & Mitigate types, data usages, and report viewers ALM Team has decided what they're n
Regulations contractors for all potential Apptio use cases giving us ([Name] - 1/28)
([Name] - TBD)
[Name] does not have access to [Apptio

18 KGS Access to [Apptio Client] network so he has difficulty H [Name] 10/16/2012 [Name] [Name] [2012] Closed [2012] Eliminate Issue Event Approve [Name]'s soft token request [Name] is completely set up ([Name] - y
Client] Network accessing data ([Name] - 10/19) 10/29)
The delay in the design document only

19 Delay in LCAP+ Design delays sign off but does not delay H [Name] 11/12/2012 [Name] [Name] [2012] Closed [2012] Eliminate Issue Event Complete the design document and y
Document configuration as the design strategy has have signed ([Name] - 11/16)
been completed
If the ITO Reorganization occurs over the Plan to revise Apptio project plan based Workstream has been mobilized to
20 ITO Reorganization next 5-7 weeks, significant changes will L [Name] 12/3/2012 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event on engagement leadership ([Name] - address organizational changes in our Y
need to be made to our project plan, 2/1/2013) Model; Specifically LCAP+ and TCO
resource plan, and deliverables Labor.
Delay in TCO p. A We need to finalize the design Revise the milestone and priority list to
21 Design Document document so configuration can be H [Name] 12/3/2012 [Name] [Name] [2012] Closed [2012] Eliminate Issue Event determine where TCO fits ([Name] - Does not apply to TCO p. A Design Doc y
(12/13/12)
finalization completed TBD)
Delay in TCO p. A We need to finalize the design We are not providing design
21 Design Document document so configuration can be L [Name] 12/3/2012 [Name] [Name] [2012] Closed [2013] Eliminate Issue Event Create a high level overview to socialize documents, we will only be providing a
with stakeholders ([Name] - 12/14) y
finalization completed definition and allocation plan
Delay in TCO p. A We need to finalize the design We are not providing design
21 Design Document document so configuration can be L [Name] 12/3/2012 [Name] [Name] [2012] Closed [2013] Eliminate Issue Event Finish the design document and review documents, we will only be providing a y
finalization completed with stakeholders ([Name] - TBD) definition and allocation plan
If finance restates a GL and we have Discuss with client stakeholders to [Name] will work with [Name] to get
22 GL Restatements already published results, are we L [Name] 12/17/2012 [Name] TBD TBD Closed [2013] Eliminate Issue Event determine what they want to do (TBD) new employee reports. [Name] says y
responsible for publishing new results? not to worry about restatements
We are currently not tying to the FVR Work with finance to recreate the
23 FVR Report Accuracy reports at the Felts level L [Name] 12/17/2012 [Name] TBD TBD Closed [2013] Eliminate Issue Event correct pull and RC Hierarchy ([Name] - [Name] completed y
TBD)
Environment Data We are currently experience extended Discuss with Apptio to investigate
24 Load Time in Staging load time when we load the Apptio L [Name] 1/3/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate performance of staging environment - y
environment Staging environment. TBD
Environment Data We are currently experience extended Determine appriopriate projects to
25 Load Time in Staging load time when we load the Apptio L [Name] 1/3/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate y
retain in each environment - TBD
environment Staging environment.
26 Icons not available for Reporting surface does not display all L [Name] 1/3/2013 [Name] [Name] TBD Closed [2013] Eliminate Issue Event Load correct Icon into all environments y
Reporting Icons (1/4)
TCO p. A1 definition We do not have a consistent definition
27 and allocation strategy of what TCO p. A1 is and what the H [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Meet with [Name] and define TCO TCO p. A1 is hardware (midrange, y
not defined allocation strategy is ([Name] - 1/25) mainframe)
TCO p. A1 definition We do not have a consistent definition Review Statement of Work and TCO p. A1 is hardware (midrange,
27 and allocation strategy of what TCO p. A1 is and what the H [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event determine what we're contractually mainframe) y
not defined allocation strategy is bound to provide ([Name] - TBD)
TCO p. A1 definition We do not have a consistent definition Create a TCO scoping document to
27 and allocation strategy of what TCO p. A1 is and what the H [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event define TCO and our future deliverables TCO p. A1 is hardware (midrange, y
not defined allocation strategy is ([Name] - TBD mainframe)
28 Bill of IT not defined We do not have a consistent definition L [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Meet with [Name] and define Bill of IT [Name] and [Name] determining y
of what Bill of IT is ([Name] - 1/25) prioritization (TBD)
Review Statement of Work and
28 Bill of IT not defined We do not have a consistent definition L [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event determine what we're contractually [Name] and [Name] determining y
of what Bill of IT is prioritization (TBD)
bound to provide ([Name] - TBD)
Create a Bill of IT scoping document to
28 Bill of IT not defined We do not have a consistent definition L [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event define Bill of IT and our future [Name] and [Name] determining Y
of what Bill of IT is deliverables ([Name] - TBD prioritization (TBD)
29 Showback not defined We do not have a consistent definition L [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Meet with [Name] and define [Name] and [Name] determining y
of what Showback is Showback ([Name] - 1/25) prioritization (TBD)
Review Statement of Work and
29 Showback not defined We do not have a consistent definition L [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event determine what we're contractually [Name] and [Name] determining y
of what Showback is bound to provide ([Name] - TBD) prioritization (TBD)
Send email to [Name] asking him to Doing showback for groups that do not
29 Showback not defined We do not have a consistent definition L [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event document showback priortization currently have a showback report (JMS y
of what Showback is ([Name] - 3/8) 5/14)
Priority was determined. Showback

Create a Showback scoping document report will focus on those
29 Showback not defined We do not have a consistent definition L [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event to define Showback and our future metrics/areas not currently being y
of what Showback is deliverables ([Name] - TBD reported on. (Desktop Support /
Telepresence)
TCO p. B definition and We do not have a consistent definition

30 allocation strategy not of what TCO p. A is and what the H [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Meet with [Name] and define TCO TCO p. B will be budget view y
([Name] - 1/25)
defined allocation strategy is
TCO p. B definition and We do not have a consistent definition Review Statement of Work and
30 allocation strategy not of what TCO p. A is and what the H [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event determine what we're contractually TCO p. B will be budget view y
defined allocation strategy is bound to provide ([Name] - TBD)
TCO p. B definition and We do not have a consistent definition Create a TCO scoping document to
30 allocation strategy not of what TCO p. A is and what the H [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event define TCO and our future deliverables TCO p. B will be budget view y
defined allocation strategy is ([Name] - TBD
TCO p. A2 definition We do not have a consistent definition Meet with [Name] and define TCO
31 and allocation strategy of what TCO p. A2 is and what the H [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event ([Name] - 1/25) TCO p. A2 is end user, storage y
not defined allocation strategy is
TCO p. A2 definition We do not have a consistent definition Review Statement of Work and
31 and allocation strategy of what TCO p. A2 is and what the H [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event determine what we're contractually TCO p. A2 is end user, storage y
not defined allocation strategy is bound to provide ([Name] - TBD)
TCO p. A2 definition We do not have a consistent definition Create a TCO scoping document to
31 and allocation strategy of what TCO p. A2 is and what the H [Name] 1/21/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event define TCO and our future deliverables TCO p. A2 is end user, storage y
not defined allocation strategy is ([Name] - TBD
Decision on whether to decouple Discuss options with stakeholders
32 Software decopling Software object from GL is needed H [Name] 2/11/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event ([Name] - 2/15) Yes. Decouple y
33 Total Hardware costs Need Total HW costs within MAC from H [Name] 2/14/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Review MAC Data ([Name] - 2/15) Closed as issues 41-43 are more y
ALM Team detailed
33 Total Hardware costs Need Total HW costs within MAC from H [Name] 2/14/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Escalate to ALM Leadership ([Name] - Closed as issues 41-43 are more y
ALM Team 2/15) detailed
Need Total HW costs within MAC from Closed as issues 41-43 are more
33 Total Hardware costs ALM Team L [Name] 2/14/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Review IBM Kodiak ([Name] - 2/15) detailed y
34 EDIT Scope We need to finalize EDIT Scope H [Name] 2/14/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Need detailed EDIT Requirements y
Requirements requirements ([Name] -TBD)
34 EDIT Scope We need to finalize EDIT Scope H [Name] 2/14/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Front Door Process for Apptio ([Name] y
Requirements requirements - TBD)
Different versions between Dev / Stage / Confirmed issues will not impact our
35 Environment Upgrade Prod environments. Cannot migrate H [Name] 2/14/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event implementation. We are not leveraging n
projects out-of-box ([Name] - 2/14)
We are currently experiencing

35 Environment Upgrade significant performance issues with the H [Name] 3/12/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Open ticket with Apptio ([Name] - 3/12) Complete y
Dev environment as a result of the 10.2
upgrade from 3/11-3/13
We are currently experiencing [Name] and [Name] working Apptio to

35 Environment Upgrade significant performance issues with the H [Name] 3/12/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event resolve and won't close until root cause Complete y
Dev environment as a result of the 10.2 identified ([Name] - 3/12)

significant performance issues with the Apptio restored 10gb memory removed
35 Environment Upgrade Dev environment as a result of the 10.2 H [Name] 3/12/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event from env during 10.2 upgrade Complete y

35 Environment Upgrade significant performance issues with the H [Name] 3/12/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Instituted policy of all data loading to be Complete y
Dev environment as a result of the 10.2 performed in stage env

35 Environment Upgrade significant performance issues with the H [Name] 3/12/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event General cleanup of data files and Complete y
Dev environment as a result of the 10.2 project within dev

[Name] log in to Dev, Stage, and
35 Environment Upgrade significant performance issues with the H [Name] 3/12/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Production environments every Complete y
Dev environment as a result of the 10.2
upgrade from 3/11-3/13 morning at 6am CST ([Name] - daily
Different versions between Dev / Stage /

35 Environment Upgrade Prod environments. Cannot migrate L [Name] 2/14/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Upgrade environments to same version n
([Name] - 2/22)
projects
Different versions between Dev / Stage /
35 Environment Upgrade Prod environments. Cannot migrate L [Name] 2/14/2013 [Name] [Name] [2013] Closed [2013] Eliminate Issue Event Force migration of select projects n
projects ([Name] - 2/22)
[Apptio Client] is not adopting and usign Evangelize LCAP+ during Felts staff
36 LCAP+ Adoption LCAP+ M [Name] 2/14/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate meetings ([Name] - TBD) [Name] sent email to [Name] y
Once Apptio team and KPMG Apptio

Discussion will be held with new project
37 Configuration Lead expert roll off the project, there may be M [Name] 12/3/2012 [Name] [Name] TBD Closed [2013] Eliminate Risk Event leadership to determine longterm [Name] joined the team (4/2013) y
Risk a lack of configuration experience and configuration lead ([Name] -1/2013)
Apptio expertise on the team
The most recent mainframe data

38 Conflicting Mainframe conflicts with prior data, and we are M [Name] 2/22/2013 [Name] [Name] TBD Closed [2013] Eliminate Risk Event Decide on reconciliation approach We need an overall reconcilation y
data unsure how to proceed ([Name] - 3/1) strategy
The Fuetsch differential is too high due Change the differential calculation
39 January CAT Results - to Apptio incorrectly missing the M [Name] 2/26/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event configuration to go on RC rather than y
Fuetsch Differential
Macauda/Fuetsch org change name ([Name] - 2/27)
40 Change in user
permissions
User permissions mysteriously changed
causing data security concerns H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Create ticket with apptio and solve the Complete
issue ([Name] - 3/1) y
Set up unique roles for Apptio Admins,

40 Change in user User permissions mysteriously changed H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Admins, Power Users, Business Users Complete y
permissions causing data security concerns and Analysts ([Name])
Give permissions to current members

40 Change in user User permissions mysteriously changed H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event of the Apptio team ([Apptio Client], Complete y
permissions causing data security concerns KPMG & Zuna), the LTM’s and their
delegates and our Finance Partners
Budget info for We need the budget data for TCO A Meet with [Name] to discuss request
41 IBM/Kodiak MR allocation H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event ([Name] - 2/25) Received (3/5) y
Servers
Budget info for
41 IBM/Kodiak MR We need the budget data for TCO A H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Send request to [Name] ([Name] - Received (3/5) y
Servers allocation 2/25)
Need HW
42 Maintenance cost for Need HW Maintenance cost for H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Send request to [Name] ([Name] - 2/26) Done n
purchased servers in purchased servers in MAC
MAC
Need HW
42 Maintenance cost for Need HW Maintenance cost for
purchased servers in purchased servers in MAC H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Review data and send extract of
required servers ([Name] - 2/26) Done n
MAC
Need HW
42 Maintenance cost for Need HW Maintenance cost for H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Receive data ([Name] - 3/1) Need redaction to occur n
purchased servers in purchased servers in MAC
MAC
Need HW
42 Maintenance cost for Need HW Maintenance cost for H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Utilize finance provided files ([Name] - y
purchased servers in purchased servers in MAC 3/22)
MAC
Possible OS Type Need to validate OS Type across Server

mismatch or Mismatches or incomplete data could
43 incomplete data for invalidate our results H [Name] 2/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event data stores to make sure reporting y
Servers surface is accurate ([Name] - 2/27)
44 Need DES Data for top We cannot create an accurate allocation H [Name] 2/25/2013 [Name] [Name] TBD Closed [2013] Eliminate Risk Event ALM to provide schedule for completing All DES Data (3/19) y
SW Vendors without this data activities ([Name] - 3/8))
44 Need DES Data for top We cannot create an accurate allocation H [Name] 2/25/2013 [Name] [Name] TBD Closed [2013] Eliminate Risk Event ALM to provide information for Oracle All DES Data (3/19) y
SW Vendors without this data ([Name] - 3/8))
Need detailed SW We cannot create an accurate allocation ALM to provide schedule for completing Commitment is 3/30/2013
45 contract info for top H [Name] 2/25/2013 [Name] [Name] TBD Closed [2013] Eliminate Risk Event y
SW vendors without this data activities ([Name] - 3/31)
The upgrade of Stage and Prod resulted

46 Upgrade Issues in a loss of all data and modelling H [Name] 3/5/2013 [Name] [Name] TBD Closed [2013] Eliminate Risk Event [Name] working to resolve (TBD) y
Users accessing wrong Users accessing wrong environment and Provide prod access to all individuals
47 environment could affect development H [Name] 3/7/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event ([Name] - 3/8) Complete y
47 Users accessing wrong Users accessing wrong environment and

environment could affect development H [Name] 3/7/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Send email redirecting them to the
correct site ([Name] - 3/8) Complete y
If contractors do not receive VPN acess,

48 Contractor VPN they risk missing emails and M [Name] 3/8/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate Provide VPN Access ([Name] - 3/15) Not going to pursue y
communications from teammates when
they are not at [Apptio Client]
If contractors do not receive VPN acess, Communicate to team that individuals

48 Contractor VPN they risk missing emails and M [Name] 3/8/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate must receive email on their own Not going to pursue y
communications from teammates when company address when away ([Name] -
they are not at [Apptio Client] 3/15)
Daily status needs to be redesigned so

49 Daily status redesign that progress percentage means the H [Name] 3/8/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Modify status slide ([Name] - 3/11) Complete y
percent of dollars assigned from the GL
directly to the Asset
Daily status needs to be redesigned so

that progress percentage means the Communicate to the team this new
49 Daily status redesign percent of dollars assigned from the GL H [Name] 3/8/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event direction ([Name] - 3/11) Complete y
directly to the Asset
User permission errors Users are having difficulty viewing CAT Pass meeting to [Name] & [Name]
50 in Prod environment reports in Prod environment H [Name] 3/12/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event ([Name] - 3/12) y
Cannot identify servers There is a material number of servers

51 from a cost that we cannot identify the manual H [Name] 3/12/2013 [Name] [Name] [2013] Closed [2013] Control & Mitigate Try to find costs using a sample size of Have vendor list y
perspective maintenance cost for 10 unmatched servers ([Name] - 3/15)
Mainframe, Data Quality – Modeling and Meeting with SME’s to review current
52 Mainframe Data cost allocations using most recent lag H [Name] 3/19/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event model state and accuracy of most y
Quality files recent lag files ([Name] - 3/19)
Unclear process for copying data and

53 Projet
to Dev
copy from Stage configuration from Stage to Dev
environments leads to uncertainty in H [Name] 3/26/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Meeting afternoon of 3/26 ([Name] -
3/26) Process clear y
work completedness
54 Incomplete AOTS Data TM Tickets missing ticket ID H [Name] 3/22/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Repull AOTS TM Tickets ([Name] - 3/26) [Name] did pull y
CM Tickets not matchable to assets and Utilize forward schedule of change tool
54 Incomplete AOTS Data applications H [Name] 3/22/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event ([Name] - 3/29) [Name] did pull y
We do not have a formal production

55 Production Issue environment issue resolution process, so H [Name] 3/29/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Develop a formal plan and distribute to Y
Resolution Process errors cause a firedrill and panic team ([Name] - 4/5)
We do not have an up to date,

trustworthy source of AOTS CM & TM LCAP Sharepoint us up and running.
tickets to organization mapping at the
56 AOTS to Organization same granularity as LCAP. The impact is M [Name] 4/2/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate Create a section on the LCAP SharePoint Will serve as our source for mapping Y
Mapping our event counts will be off until this and create the source ([Name] - TBD) AOTS CM and TM tickets to the
source is identified and integrated into organization
the model

trustworthy source of AOTS CM & TM
AOTS to Organization tickets to organization mapping at the Implement TM and CM tickets into
56 Mapping same granularity as LCAP. The impact is L [Name] 4/2/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate model using current mappings ([Name] Implemented in Apptio (4/16) y
our event counts will be off until this - 4/5)
source is identified and integrated into
the model

trustworthy source of AOTS CM & TM
LCAP Sharepoint us up and running.
AOTS to Organization tickets to organization mapping at the Will serve as our source for mapping
56 Mapping same granularity as LCAP. The impact is M [Name] 4/2/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate Find a definitive source (J. Berger - TBD) AOTS CM and TM tickets to the Y
our event counts will be off until this organization
source is identified and integrated into
the model
The DEV, Stage, and Prod environments [Apptio Client] should receive weekly Apptio is responsible for OS Level
58 Recurring continue to perform poorly on a regular H All 5/14/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate maintenance reports from Apptio maintenance. Will provide monthly Y
performance issues
basis ([Name] - TBD) report to [Name]
Completed mitigation step; EDIT team
66 Cloud Data Source We need a definitive data source to H [Name] 6/25/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Send issue to EDIT Team. This should be made recommendation; Waiting on y
identify all Cloud Assets one of their top priority items status
We are not approved to work on any
67 New Requests from activities related to providing new H [Name] 6/6/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Refrain from any activities related to y
Finance reports/data to Finance new reports for Finance

67 New Requests from
Finance activities related to providing new H [Name] 6/6/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Work to mitigate issue between Finance
and ITO y
reports/data to Finance
The DEV, Stage, and Prod environments

58 Recurring continue to perform poorly on a regular L All 4/9/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate Clean up projects ([Name]) y
performance issues
basis
58 Recurring
performance issues continue to perform poorly on a regular L All 4/9/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate Clean up datasets ([Name]) y
basis
58 Recurring continue to perform poorly on a regular M All 4/9/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate Limit access to projects in DEV, Stage, Adjust working hours as needed to stay y
performance issues basis and Prod ([Name]) on schedule and target (JMS 5/14)
Recurring The DEV, Stage, and Prod environments Report root cause and remedy of all
58 performance issues continue to perform poorly on a regular M All 4/9/2013 [Name] [Name] TBD Closed [2013] Control & Mitigate outages (All) y
basis
[Name] does not have access to
59 [Name] Computer historical emails and normal computer H [Name] 4/15/2013 [Name] [Name] [2013] Closed [2013] Control & Mitigate [Name] is using a loaner PC [Name] has PC back y
Crash functionality
[Name] does not have access to
59 [Name] Computer historical emails and normal computer H [Name] 4/15/2013 [Name] [Name] [2013] Closed [2013] Control & Mitigate [Name] should check to ensure major [Name] has PC back y
Crash files have not been lost ([Name] - 4/27)
functionality
59 [Name] Computer No other resource on the team has the H [Name] 4/15/2013 [Name] [Name] [2013] Closed [2013] Control & Mitigate [Name] should download the AOTS tool [Name] has AOTS access y
Crash ability to pull AOTS tickets ([Name] - 4/20)
Differing values in App

60 Total Values between We need to figure out why there are
different values in the environments H [Name] 4/30/2013 [Name] [Name] TBD Closed [2013] Eliminate Risk Event [Name] and [Name] investigating GL XC
fallout ([Name] - 4/30) Fixed (JMS 5/14) y
environments
Application Cost
61 Breakout by HW, SW, The current model does not support this
report being created easily H [Name] 4/30/2013 [Name] [Name] TBD Closed [2013] Eliminate Risk Event Create the applications object report
([Name] - 5/3) y
and Labor
Application Cost
61 Breakout by HW, SW, The current model does not support this H [Name] 4/30/2013 [Name] [Name] TBD Closed [2013] Eliminate Risk Event Create the report in Apptio the correct y
and Labor report being created easily way ([Name] - TBD)
Software vendor name This impacts configuration between Mapping table for vendors should be
62 discrepancy in budget budget and cost models H [Name] 5/9/2013 [Name] [Name] [2013] Closed Eliminate Risk Event created to map cost vendors to budget y
and GL [2013]
vendors.
"Ghost" records in "Ghost" records cause the Apptio Remove totals column from report to Known bug in Apptio. Must not show
63 reports spanning calculated totals to differ from totals H [Name] 5/14/2013 [Name] [Name] TBD Closed Control & Mitigate remove confusion total row in these reports ([Name] y
multiple time periods when extracted into Excel 5/21/2013)
[2013]
"Ghost" records in "Ghost" records cause the Apptio Revert report to a legacy reporting Known bug in Apptio. Must not show
63 reports spanning calculated totals to differ from totals H [Name] 5/14/2013 [Name] [Name] TBD Closed Control & Mitigate total row in these reports ([Name] y
multiple time periods when extracted into Excel standard to correct issue 5/21/2013)
[2013]
64 PC Lease Data Needed PC Lease Data Needed H [Name] 5/21/2013 [Name] [Name] TBD Closed Eliminate Risk Event [Name] needs help contacting [Name] y
[2013]
65 Model Breakages Breakages in ticket object, software H [Name] 5/21/2013 [Name] [Name] [2013] Closed Eliminate Risk Event Undoing the audit log y
object, and business services object [2013]
[Name] and [Name] will build a project
65 Model Breakages Breakages in ticket object, software H [Name] 5/21/2013 [Name] [Name] [2013] Closed Eliminate Risk Event promotion checklist and will execute for y
object, and business services object future promotions
[2013]
67 New Requests from activities related to providing new H [Name] 6/6/2013 [Name] [Name] [2013] Closed Eliminate Risk Event Continue all in-flight Finance Reports y
Finance reports/data to Finance (CAT & TCO)
[2013]
No concensus on Impacts our ability to create Platform Discuss with EDIT team to get their We are using the standard that the
72 definition of cores Analysis or Operational Metrics reports H [Name] 7/9/2013 [Name] [Name] [2013] Closed Eliminate Risk Event point of view on how to achieve a ALM Team is using. DDMI definition of Y
with ITO that will be widely accepted [2013]
common definition Core
Lack of data quality is preventing Tape
57 Storage Data Quality data from being integrated & modeled L [Name] 4/3/2013 [Name] [Name] TBD Closed Control & Mitigate Does not affect reporting, but this data We are able to tie Tape data directly to Y
within TCO will be desired in the future a server
[2013]
The DEV, Stage, and Prod environments Investigate server configuration and
58 Recurring continue to perform poorly on a regular M All 5/14/2013 [Name] [Name] TBD Closed Control & Mitigate evaluate upgrades / replacements / Closed based on mitigation of #58 Y
performance issues basis additional servers ([Name] & [Name] -
TBD)
[2013]
All WITT ESX servers are not appering in
68 ESX Servers our Services object M [Name] 6/24/2013 [Name] [Name] [2013] Closed Eliminate Risk Event Investigate details of ESX Servers y
[2013]
No concensus on Impacts our ability to create Platform Ask [Name]: Does Apptio need to
72 definition of cores Analysis or Operational Metrics reports H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event report on cores as it related to cost or n
processing/operational metrics
No concensus on Impacts our ability to create Platform We are using the standard that the
72 definition of cores Analysis or Operational Metrics reports H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event Get defintion of "cores" from ALM team ALM Team is using. DDMI definition of Y
([Name])
Core
We need to adjust the way we Confirm strategy for identifying virtual
69 IEDS Virtual Servers determine virtual servers in IEDS M [Name] 6/1/2013 [Name] [Name] [2013] Closed Eliminate Risk Event servers in IEDS y
[2013]
Lack of data quality is preventing NAS Does not affect reporting, but this data
57 Storage Data Quality data from being integrated & modeled L [Name] [2013] [Name] [Name] [2013] Open Control & Mitigate n
will be desired in the future
within TCO [2013]
68 ESX Servers All WITT ESX servers are not appering in M [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event Revised data loads to include ESX Data set has been incorporated into our Y
our Services object [2013] Servers (as appriopriate) dataset
All WITT ESX servers are not appering in Update configuration to ensure ESX Data set has been incorporated into our
68 ESX Servers our Services object M [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event servers appear in Servers object dataset Y
[2013]
69 IEDS Virtual Servers We need to adjust the way we M [Name] 6/1/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Update configuration to revise IEDS virtual logic has been updated y
determine virtual servers in IEDS virtual server logic
Detemine strategy for using priority /
71 Ticket Weighting We need to weight trouble tickets in our M [Name] 6/24/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event severity to set a trouble ticket y
model based on priority / severity weighting
71 Ticket Weighting We need to weight trouble tickets in our M [Name] 6/24/2013 [Name] [Name] [2013] Closed [2013] Eliminate Risk Event Adjust configuration to implement y
model based on priority / severity trouble ticket weighting solution
We need to incorporate server Determine source of data for Server

70 Depreciation depreciation calculations and metrics H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event depreciation metrics n
into our model [2013]
We need to incorporate server Determine allocation strategy for
70 Depreciation depreciation calculations and metrics H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event assigning depreciation to servers in our n
model
We need to incorporate server
70 Depreciation depreciation calculations and metrics H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event Implement server depreciation solution n
Unsubstantiated core
73 data in our Apptio Apptio reporting on CORE is inaccurate H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event Remove CORE from Apptio; Blank it out n
model that needs to until #72 is resolved
be corrected
[2013]
Production
User cannot user production Complete current configurations in Dev
74 Environment does not environment; Latest configuration/data H [Name] 7/16/2013 [Name] [Name] [2013] Closed Eliminate Risk Event and complete configuration Completed Y
have the latest is not represented in all envirnoments documentation
configuration
[2013]
Production User cannot user production Configurations have been promoted to
74 Environment does not environment; Latest configuration/data H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event Promote configuration to Stage and Prod; But there are still additonal n
have the latest is not represented in all envirnoments validate changes that need to be promoted.
configuration
[2013]
Production
Environment does not User cannot user production Received Stage warming report from [Name] to provide results of warming
74 have the latest environment; Latest configuration/data H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event Apptio showing improvements prior to analysis n
configuration is not represented in all envirnoments the promotion to Stage/Prod
[2013]
Additional contract
extension for KPMG
resources has not KPMG working on a temporary
Work with [Name] to answer questions extension (via e-mail) using the current
75 been signed, and H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event n
current SOW from Finance regarding extension contract terms
completion data has
passed Contract resources cannot work past [Date];
KPMG resources cannot work past [Date] [2013]
Additional contract
extension for KPMG KPMG working on a flexible extension
resources has not Expedite transition Plan to [Apptio
75 been signed, and H [Name] [2013] [Name] [Name] [2013] Open Eliminate Risk Event Client 1] Financial Understanding Team solution to accommodate requirements n
current SOW ([Names]) from Finance to reduce length of
completion data has proposed SOW
passed Contract resources cannot work past [Date];
KPMG resources cannot work past [Date] [2013]

ATT Risk Log 8.6.2013 v1

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ATT Risk Log 8.6.2013 v1

Uploaded by

Copyright:

Available Formats

This document has been provided for reference purposes only.

Risks & Issues Log:

Apptio IT Financial Understanding

For Internal Use Only

The requirement to be able to reproduce

The requirement to be able to reproduce

There is a risk that an additional contract

There is a risk that an additional contract

Received e-mail confirmation on scpoe

Manage Requirements and Change Requests; Check requests

Transition from There is a risk that knowledge could be lost in

Transition from There is a risk that knowledge could be lost in

Enterprise or stakeholder communications are

Frequent changes in requirements may result

Lack of client SME support Appropriate users are not available to

Identify data sources and owners; Begin collection and analysis

Work with internal stakeholders, Data Center, and Apptio to

Work Break Structure has been created

Lack of business user

Work Break Structure has been created

Data conversion taking longer than expected

We do not currently have a backup Eliminate

Both processs will be run in parallel for

KPMG, KGS, and Apptio resources are

Project teams are encouraged to configure

We currently do not have a plan to cut over

Ambiguous requirements leading to

We need to develop a process for gathering

Once Apptio team and KPMG Apptio expert

We do not know who is responsible for

We do not know who is responsible for

Lack of data acquisiton We do not have a data acquisition process Eliminate

We do not have a data acquisition process

We do not have a data acquisition process

If we do not have plan for what cost pools or

If we do not have plan for what cost pools or

If we do not have plan for what cost pools or

We cannot keep up with changes in the GL

If we don't change the resource mix on the

Once Apptio team and KPMG Apptio expert

Once Apptio team and KPMG Apptio expert

Once Apptio team and KPMG Apptio expert

If we move from the 2 Bell location, we may Control &

The requirement to be able to reproduce

If a person is not identified for maintaining

LCAP testing is running long, which could

LCAP testing is running long, which could Eliminate

LCAP testing is running long, which could

LCAP testing is running long, which could Eliminate

If a person is not identified for maintaining

We need to onboard the new client Eliminate

We need to onboard the new client

If we don't get the resources for acceleration

Production Environment Production environment hardware and Eliminate

We need to define the scope for what is

The requirement to be able to reproduce

Once Apptio team and KPMG Apptio expert

The requirement to be able to reproduce

We do not have a good mechanism to validate

The business objects reporting tool is down

We need to build a relationship with Cody Control &

Transition from There is a risk that knowledge could be lost in

We need to ensure we have multiple contacts