Version 2.

1
Data Warehouse Implementation Project Calculator November
2007

PURPOSE The model allows work effort driver information to be entered and used along with a range of parameter settings and core staff resourcing information
to determine the work effort, duration and cost of a data warehouse implementation project.

ASSUMPTIONS The project consists of four phases - requirements, design & build, test and deploy.
There are four core work types or roles that are effort based - business analyst, ETL builder, data modeller and front end builder.
There are three management roles that are time based - technical lead, project manager and project support.

DESCRIPTION The CORE WORK section represents the quantitative drivers for each area of core work. These are converted to general "notional units of work" to
provide an intermediate expression of the magnitude of work required. The general notional units are then transposed into notional units for each core
work type (or role) in preparation for conversion to actual units of work.

CORE STAFFING allows staffing resources and skill levels to be defined for the core work types. The notional units by core work type are converted
to actual days of effort based on a representation of the productivity that takes account of skill levels. The actual days of effort are converted to
elapsed phase durations and FTE by phase for each core work type based on the work profile for each core work type across the project phases.

SCALING FACTORS represent circumstances that affect the overall work effort favourably or unfavourably. These factors are rated and converted to
scaling values that represent the degree of favourable or unfavourable impact. These scaling values are then applied as appropriate to the actual
work effort to adjust it accordingly.

The COSTING MODEL applies charge rates to the actual work effort to convert it to cost. This includes calculating and costing the work effort for
time-based roles.

DURATION AND FTE summarises the phase durations and FTE by phase for the project. It also provides the option to apply overrides to calculated
phase durations or staffing, and resize and recalculate the project accordingly. Override details for both durations and staff can be specified, but only
one at a time can be applied (since they conflict). The Phase Duration Limit Work Area is used to specify overrides for some or all of the calculated
phase durations with shorter ones. The Core FTE Override Work Area is used to specify overrides for some or all of the calculated core FTE levels by
phase per core work type with increased staffing levels.
 Version 2.1
Data Warehouse Implementation Project Calculator November
2007

CORE WORK CORE WORK DRIVER VOLUMES VOLUME CONV FACTORS RAW NOTIONAL UNITS OF WORK WORK FACTOR PER WORK TYPE NOTIONAL UNITS PER WORK TYPE LEGEND
Complexity Table P1 Table C1 Table P9 Table C12 Table identifier Table id
Table E1 Low Medium High Total Work in notional units (NU) Work in notional units (NU) Total NU Analyst ETL Model F/E B/A ETL Model F/E Item heading text Heading
Data source systems High DQ 0 0 0 0 3 6 9 0 0 0 0 0.5 1 0.5 0.2 0 0 0 0 Parameter value Parameter
Medium DQ 12 0 0 12 6 9 12 72 0 0 72 1 1 0.5 0.2 72 72 36 14 Entered data Entered
Low DQ 3 0 0 3 9 12 15 27 0 0 27 1.5 1 0.5 0.2 41 27 14 5 Calculated data Calculated
Important data Alert
Size Table P2 Table C2 Table P10 Table C13 Reserved for validation Reserved
Table E2 Small Medium Large Total Work in notional units (NU) Work in notional units (NU) Total NU Analyst ETL Model F/E B/A ETL Model F/E Error indicator or message ERROR
Data source tables # Tables 14 28 3 45 3 6 9 42 168 27 237 0.2 1 0.2 0.2 47 237 47 47

Size Table P16 Table C26 Table P17 Table C27

Generic Profiling Table E12 Small Medium Large Total Work in notional units (NU) Work in notional units (NU) Total NU Analyst ETL Model F/E B/A ETL Model F/E
Tables to profile # Tables 14 28 3 45 0.5 0.5 0.5 7 14 1.5 22.5 1 1 0 0 23 23 0 0
Tests/table 10 10 10
Total tests 140 280 30 450 0.1 0.1 0.1 14 28 3 45 1 1 0 0 45 45 0 0

Complexity Table P18 Table C28 Table P19 Table C29

Specific Profiling Table E13 Low Medium High Total Work in notional units (NU) Work in notional units (NU) Total NU Analyst ETL Model F/E B/A ETL Model F/E
Business rule tests # Tests 10 10 5 25 0.2 0.3 0.6 2 3 3 8 1 1 0 0 8 8 0 0

Complexity Table P3 Table C3 Table P11 Table C14

Access, Analytics and Delivery Table E3 Low Medium High Total Work in notional units (NU) Work in notional units (NU) Total NU Analyst ETL Model F/E B/A ETL Model F/E
Cubes Count 0 2 0 2 3 6 9 0 12 0 12 2 0.5 1 1 24 6 12 12
Summary attributes Count 0 50 0 50 1 2 3 0 100 0 100 1 0 0.1 0.5 100 0 10 50
Screen outputs Count 0 2 0 2 1 1.5 2.5 0 3 0 3 2 0 0.1 1 6 0 0 3
Report outputs Count 0 2 0 2 1 1.5 2.5 0 3 0 3 2 0 0.1 1 6 0 0 3
Special automation Count 0 2 0 2 1 2 3 0 4 0 4 0.2 0 0.1 0.5 1 0 0 2
Advanced Information Delivery
Advanced User Interactivity Count 0 2 0 2 1 1.5 2.5 0 3 0 3 2 0 0.1 1 6 0 0 3
Advanced Analytics Count 0 2 0 2 3 6 9 0 12 0 12 2 0 0.5 2 24 0 6 24
Knowledge Management
Collaboration Count 0 5 0 5 3 6 12 0 30 0 30 1 0 0.5 2 30 0 15 60

User Type Table P4 Table C4 Table P12 Table C15

Table E4 Executive Manager Analyst Total Work in notional units (NU) Work in notional units (NU) Total NU Analyst ETL Model F/E B/A ETL Model F/E
BI Users Count 100 30 50 180 0.2 0.5 1 20 15 50 85 0.3 0 0 0.2 26 0 0 17

Site size Table P5 Table C5 Table P13 Table C16

Table E5 Small Medium Large Total Work in notional units (NU) Work in notional units (NU) Total NU Analyst ETL Model F/E B/A ETL Model F/E
Sites Count 0 0 3 3 3 4 5 0 0 15 15 0.5 0 0 0.1 7.5 0 0 1.5

TOTAL NOTIONAL UNITS OF WORK

Table C17
B/A ETL Model F/E
465 418 141 243

CORE STAFFING CORE TEAM RESOURCES PRODUCTIVITY FACTORS CONVERT NOTIONAL TO ACTUAL UNITS WORK TYPE PROFILE BY PHASE UNADJUSTED ELAPSED TIME AND FTE PER PHASE BY WORK TYPE
Table C6
Skill level Table P6 Effective Total Raw Scaled Table P14 Table C18 Table C19
Table E6 Basic Seasoned Expert Total NU to actual multiplier multiplier notional actual actual Reqs D&B Test Deploy Reqs D&B Test Deploy Reqs D&B Test Deploy
Analyst Headcount 0 3 3 6 1.3 1 0.7 0.9 465 395 826 40% 20% 20% 20% 55.1 27.5 27.5 27.5 6.0 2.7 5.3 5.3 Analyst
ETL builder Headcount 0 4 2 6 1.3 1 0.7 0.9 418 376 458 10% 50% 30% 10% 7.6 38.2 22.9 7.6 0.8 3.7 4.4 1.5 ETL builder
Modeller Headcount 0 2 1 3 1.3 1 0.7 0.9 141 127 144 20% 60% 20% 0% 9.6 28.7 9.6 0.0 0.5 1.4 0.9 0.0 Modeller
Front end Headcount 0 2 0 2 1.3 1 0.7 1.0 243 243 311 20% 40% 20% 20% 31.1 62.1 31.1 31.1 1.1 2.0 2.0 2.0 Front end
Calculated elapsed time per phase Total core FTE per phase
55.1 62.1 31.1 31.1 8.5 9.7 12.7 8.8
Total sequential elapsed time 179

SCALING FACTORS RATING OF SCALING FACTOR DRIVERS SCALING FACTORS EFFECTIVE SCALING FACTORS SCALING APPLICABILITY PHASE DURATION LIMIT WORK AREA
Table C7 Table E10 Table C21
Rating Table P7 Effective Table P15 Specified phase duration limit Core FTE adjusted for phase duration limits
Table E7 Low Medium High Scaling loading factors scaling B/A ETL Model F/E Reqs D&B Test Deploy
Requirements Clarity x 2 1 0.7 2.0 100% 20% 10% 20% 6.0 2.7 5.3 5.3 Analyst
Data model Overlap x 1.8 1 0.7 1.0 0% 0% 10% 0% 0.8 3.7 4.4 1.5 ETL builder
Technical Complexity x 0.8 1 1.2 1.2 0% 10% 0% 10% Table C20 0.5 1.4 0.9 0.0 Modeller
Management Complexity x 0.8 1 1.2 1.0 10% 0% 0% 0% Adjusted elapsed time per phase 1.1 2.0 2.0 2.0 Front end
Organisational Change Change x 0.7 1 1.3 1.3 30% 0% 10% 20% Total core FTE per phase
Enter "x" to select rating Table C11 55.1 62.1 31.1 31.1 Adjusted total core FTE per phase
x Loading percentage Total adjusted elapsed time 179 8.5 9.7 12.7 8.8
109% 22% 13% 28%

CONVERSION OF WORK TO COST

COSTING MODEL RATES BY SKILL LEVEL BY ROLE Table C10 CORE FTE OVERRIDE WORK AREA
(with time based work) Skill level Scaled Weighted Extended Table E11
Table E8 Basic Seasoned Expert actual ave rate cost Override core FTE per phase by work type
Business analyst Daily rate 500 800 1,200 TIME-BASED WORK 826 £1,000.00 £826,428 Reqs D&B Test Deploy
ETL builder Daily rate 500 800 1,200 Table P8 Table C8 Table C9 458 £933.33 £427,854 Analyst
Modeller Daily rate 500 800 1,200 Rate of Elapsed Scaling 144 £933.33 £134,027 ETL builder
Front end Daily rate 500 800 1,200 effort days loading 311 £800.00 £248,525 Modeller
Technical architect These time based roles 800 (Phases 1-3 only) 50% 93 19 56 £800.00 £44,734 Front end
Project manager assume one rate 800 (Whole project duration) 100% 179 0 179 £800.00 £143,486
Project support with FTE in Table P8 800 (Whole project duration) 50% 179 179 179 £800.00 £143,486 Table C22 Table C23

NOTE - Rates nominally exclude VAT TOTALS Time per phase adjusted for override FTE Core FTE adjusted for override FTE
TOTAL COSTS (MAIN SDLC) Table E9 Percentage 2154 £914.01 $1,968,540 Reqs D&B Test Deploy Reqs D&B Test Deploy
INCREMENTAL COST FOR CR Standard 10% 215 £914.01 £196,854 55.1 27.5 27.5 27.5 6.0 2.7 5.3 5.3 Analyst
INCREMENTAL COST FOR DECOM Standard 15% £295,281
 Version 2.1
Data Warehouse Implementation Project Calculator November
2007

INCREMENTAL COST FOR OPS Percentage 20% £393,708 7.6 38.2 22.9 7.6 0.8 3.7 4.4 1.5 ETL builder
TOTAL COSTS/SDLC INCREMENT £2,854,383
9.6 28.7 9.6 0.0 0.5 1.4 0.9 0.0 Modeller
DURATION AND FTE (MAIN SDLC) ADJUSTMENT CONTROLS DURATION AND FTE BY PHASE (including adjustments) 31.1 62.1 31.1 31.1 1.1 2.0 2.0 2.0 Front end
(including adjustments) Table E10 Summary of elapsed time per phase Adjusted elapsed time per phase Adjusted total core FTE per phase
Phase duration limits Use for costing? NO Table C24 Reqs D&B Test Deploy 55.1 62.1 31.1 31.1 8.5 9.7 12.7 8.8
Core FTE overrides Use for costing? NO Elapsed 55.1 62.1 31.1 31.1 Total adjusted elapsed time 179
YES days Total 179.4
NO Elapsed 11 13 7 7
weeks Total 38

Summary of FTE by phase

Table C25 Reqs D&B Test Deploy
FTE 9.5 11.2 14.2 9.8
Source High Medium Low
Census 0 4 10
Sen 0 0 3
EY Census 0 2 1
FSP 0 1 0
KS1 0 2 0
KS2 0 3 0
KS3 0 3 0
KS4 1 2 0
KS5 1 4 0
ILR 1 1 0
Key Skills 0 1 0
Connections 0 3 0
Optional Tests 0 1 0
Neet 0 1 0

Sum 3 28 14
Capability Capability Area
Search Information Access

Advanced Analytics Information Reporting, Analytics and

Delivery
Advanced User Interactivity Information Reporting, Analytics and
Delivery

Collaboration Information Reporting, Analytics and

Delivery

Services Oriented Architecture Architecture

Initial Baseline Infrastructure Infrastructure

Ongoing Change Reqests Operations

Ongoing Infrastructure Support Operations

Data Analyst Support Information Reporting, Analytics and

Delivery

Decommissioning Operations

Organisational Change Organisation

Scaling Factors
Number of sources, results returned

Number of analytical models, model complexity

Number of user interfaces, interface complexity

Number of users, scope of work

Number of reusable interfaces

This will be done most easily based on typical numbers

from DCSF.

10% of cost of implemented solution

20% of cost of implemented solution

This is most effectively based on ongoing team size

15% for each solution increment

Configurable scaling factor based on complexity

Assumptions Calculated Yes
In the context of this project, search may be used as another access Implied
mechanism to the BI Repository or to access multiple federated
repositories. Many of the issues (e.g. data quality) will present the same
challenges for search as it does for a traditional DW.

Advanced analytics are estimated on a per-model basis Yes

Advanced user interactivty relates to custom web development on the Yes

front end that makes use of contemporary techniques.

Collaboration is difficult to estimate without more specific requirements. Yes

As a starting point some assumptions are made around the content and
work required to build incorporate collaborative techniques around a
specific work area.

In this instance the main drives for common interfaces are to external user Implied
groups. SOA in "normal" delivery cycle does not impact estimates.
Should decrease roles from other areas and make ops cost lower over
time.

It could be expected that the initial baseline install of development, test No

and production environments will take a team of 4 - 6 from 2 - 4 months
within DCSF. Adding in additional advanced capabilities will add 20 - 40%
on top of this effort.

Can be added to the bottom of the model or can just be calculated on an Yes
annual basis. Infrastructure added at 3 levels: initial baseline, team
support, ongoing operational
Will also cover ongoing infrastructure costs. Can be added to the bottom Yes
of the model or can just be calculated on an annual basis.

To determine this information a baseline of existing team size is needed. No

Introducing efficiencies should mean this team would either get smaller or
move into high-value roles.
This assumption is based on the rationale that functionality will be turned Yes
off incrementally over time. The solution may be more complex - this is
used as a guiding figure.
This is an overhead factor that will be applied for DCSF to the significant Yes
change of this project
Additional Comments
For purposes of this estimate, search has not been explicity estimated separately from
ETL data integration. Some guidelines on estimating specifc search interfaces would
include less complexity or requirements and data modelling, but it would not be
appropriate in some instances. It may also be appropriate to use it as just an
information access mechanism.

Advances in product capabilities may mean that the current workloads associated
with this capabiltiy can be removed.

Should introduce efficiences across the departmnet and make operational cost lower
over time.

Due to level of detail, SOA is not included into this estimating model. Should decrease
operational costs over time.

In the model but may want to make it so it uses specific resources

It should be noted that this is a percentage increase on a different skill set. Most of
the resources will be infrastures skills such as DBAs, Sys Admins and Network
support. This figure includes operational support for development and testing as well
as production.

In the model but may want to make it so it uses specific resources

Version Date Details
1.1 Nov-03 Initial release
1.2 Mar-05 Correction of minor errors
Updated commentary material
Released for inclusion in MIKE2 methodology
2.0 Dec-05 Revised and added commentary material
Added ability to include data profiling work effort
Revised labelling
2.1 Nov-07 Added advanced capability areas