-f

Firearms Control System Project

Addendum 03 ~r

Date 2006-02middot10

WAYMARK ~INOTECH

J

Addendum 3 to the Contract between WAYMARK INFOTECH (PTY) LTD and the South African Police Service for the supply of a Firearm Control System for the South African Police Service

Entered into between

WAYMARKINFOTECH(PTY)LTD (Company registration number 200300436607)

(Hereinafter referred to as Waymark)

Herein represented by Pikie Monaheng In his capacity as CEO - Waymark

and

THE SOUTH AFRICAN POLICE SERVICE (Hereinafter referred to as the Service)

Herein represented by Assistant Commissioner (F) MMeyer In her capacity as

Head Information and Systems Management

WHEREASthe Contract for the supply of a Firearm Control System orlted 30 September 2004 (hereinafter referred to as the Contract) provides for the amendment of the Contract in circumstances where it is necessary for the successful implementation and support of the system

AND WHEREAS circumstances exist where it is necessary to amend certain provisions of the Contract

NOW therefore the Parties agree as follows shy

1 Acceptance Procedure - Annexure C

The Acceptance Procedure contained in Annexure Cof the Contract is withdrawn and replaced by the Acceptance Procedure contained in Annexure A of this Addendum

2 Bill of Material- Annexure D

The Bill of Material contained in Annexure 0 of the Contract is withdrawn and replaced by the Bill of Material contained in Annexure B of this Addendum

FCS Addendum 03 Date 2006-02-06 1 out of 5

3 Project Schedule Deliverables and Costs Schedule - Annexure E

The FCS Deliverable and Cost Schedule (Project Schedule and Cash flow) contained in Annexure E of the Contract is withdrawn and replaced by the FCS Deliverable and Costs Schedule (Project Schedule and Cash Flow) contained in Annexure Cof this Addendum

4 Commencement

This Addendum will commence on the Signature Date Anything done in terms of this Addendum before the Signature Date shall be deemed to have been done in terms of this Addendum

it SIGNED at Pretoria on 10 February 2006

AS WITNESSES

-1

for ana~n behalf of Waymark duly authorized thereto

SIGNED at Pretoria on I11( February 2006

AS WITNESSES

for and~n behalf of the Service1lulv authorized thereto

~ll~ C~~ff

1)r0V1(tZ

FCS Addendum 03 Dale iVVG-Vi-VG 2out of 5 ~J

Firearms Control System Project

Review of FCS Project Schedule

File Reference Number 32131144 (19)(4)

Date 2006-02-10

Version 50

CD ~- fvTAE ~ ~ 4lf~

----

321311144 Confidential Review of FCS Schedule

Approval Page

Title Review of FCS Project Schedule

Number 32131144 (19)(4)

Version Version 5 0

Date 2006-02-10

Classification Project Confidential

Prepared by WAYMARK INFOTECH

Approved for WAYMARK INFOTECH by

)(J 2- LvOh Date Time ~he

Program Director

Approved for SAPS by

2~ -pgt-~ I~-~

Date Time

Copyright of this work is reserved under the Copyright Act of the Republic of South Africa (No 98 of 1978) and the provisions of the Berne Convention

This work or any part thereof may not be reproduced in any form or by any means without prior permission in writing of

the SAPS unless in pursuance of the recommendations contained herein

-----_ _-__ ----~-~

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page i of iii

~

32131144 Confidential

Table of Contents

1 Introduction 1

2 Factors Considered for the Revised Project Schedule 1

3 Revised Project Execution 8

4 Cost and Schedule Comparison 10

5 Alternative Schedule and Cost option 15

6 Appendix A Additional Factors Previously Considered 17

Annexures

Annexure A Revised Project Schedule

Annexure B Detail Activity Cornparison between Contract Baseline Schedule and Revised Schedule

Date 2006-02-10 PrOject iiiVersion Date 2006-02-10 06 31 Version 50 Page ii of Ill

t

32131144 ProjecL~onfi~~tial Review of FCS Project Schedule ~- - -_-

Abbreviations

Description

c

Police Service

16 SQL

17 TBD

18 UAT

19 VB

20 WDK

21 WMI ~_~YMARK INFOTECH

Privacy Information

This document may contain information of a sensitive nature This information may not be given to persons other than those who are working on the FCS project or who will become involved during the project life cycle

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50

Confidential Review of FCS Prolect Schedule 32131144

1 Introduction

11 The FCS Project Management Team was requested by the Steering Committee to prepare a revised project schedule in response to addendums to the contract

12 This report contains the results of the factors considered and decisions of the FCS Project Management Team taken at planning sessions held during the past months by the SAPS team led by Director Wv Meyer and WAYMARK INFOTECHs team led by Mr J Mpshe (Director)

2 Factors Considered for the Revised Project Schedule

21 The following factors have been considered in this review of the Project Schedule

211 Late availability of the office and related IT infrastructure

212 Delay in establishing the functional baseline

213 Amendment to the deliverable sign-off (approval) process

214 Additional requirements including interfacing with the existing Firearms Register System (FRS)

22 Baseline Schedule

221 The baseline schedule as contained in the contract is shown in Diagram 1 below with the exception that the development phase as indicated below has been corrected to succeed the design phase In the orlgir31 schedule the devF~ori11r-t phase was not linked to the design phase and as such indicated a start date of 2004-10-04 which was incorrect The end date for the development phase remains unchanged

Initiation Phase

Des ign Phase

Developmet Phase bull 2005-07-07

Testing Phase 2006middot01middot19

Documentation Phase

Trairu-g Phase

TransitnPhase

23 Project Office and IT Infrastructure Availability

231 The late availability of office and related IT infrastructure has delayed the completion of the Project Setup Phase with 3 months (indicated in red in Diagram 2below) resulting in the Project Initiation Phase only starting on 7 March 2005 as illustrated in Diagram 2 below - See line item 4

Jl Print Date 2006middot02middot10 Project Confidential ------------~p-age1 of 23 ~ Version Date 2006-02-10 0631 Version 50

Review of FCS Project Scheel lie32131144

~_____ _ w_p _ _ ~_R _

2004-10-04 2004-i2-06

2005middot03-04

2005-037 2005o5~27

200so5-10 2005middot09middot20

200amp-09middot21 100644-20

2006--04-21 2006-067

Phase 2~0-ltgt1-27 200S~06-07

200$06-ltgt8 2006-47-12

2006-ltgt7-13 2006-105

232 As illustrated above the direct effect of this slip was that the project completion would slip from the baseline completion date of 5 July 2006 to 5 October 2006

24 Requirements Definition Complexities

241 The primary factor that has influenced the requirement definition and contributed to the delay in the completion thereof has been the additional User Profile development work This was identified in late April 2005 (5 weeks prior to the planned delivery date for the System Design Framework (SDF)) and as a result the following additional activities that were previously not planned for in the contract her)ule as part of the functio31 b3s-~~r 2- t-gtformed

2411 Acquire Universal Modeling Language (UML) modeling software and product training (two weeks refer revised WBS number 36131 in Annex AampB)

2412 Use case modeling for an estimated 36 cases (four weeks refer revised WBS number 36132 in Annex AampB)

2413 User Profile development and documentation work (four weeks refer to revised WBS 36133 in Annex AampB)_

2414 Due to the fact that some of the activities took place in parallel the net schedule effect has been around six weeks of elapsed time

242 The extent of changes required to the original User Profiles as recorded in the contractual baseline is highlighted in Table 1 below

___Table 1 Extent of User Profile Changes ~ Total New I Deleted _ --I~unchanCied shy

Total Profiles defined during the user profile definition exercise (Original PTech had 37 profiles)

not previously defined in PTech

Profiles that were CFR Deciding

Officer CFR Import Export Official CFR Official CFR Recommendation Officer ISM FCS ISM Official

PTech Profiles that have been unchanged (ie as originally stated) or renamed

91 61 7 30

Percentage 62 7 31 --~--

Print Date 2006~02-1 0 Confidential Version Date 2006-02-10 0631 Version 50 Page 2 of 23

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

Addendum 3 to the Contract between WAYMARK INFOTECH (PTY) LTD and the South African Police Service for the supply of a Firearm Control System for the South African Police Service

Entered into between

WAYMARKINFOTECH(PTY)LTD (Company registration number 200300436607)

(Hereinafter referred to as Waymark)

Herein represented by Pikie Monaheng In his capacity as CEO - Waymark

and

THE SOUTH AFRICAN POLICE SERVICE (Hereinafter referred to as the Service)

Herein represented by Assistant Commissioner (F) MMeyer In her capacity as

Head Information and Systems Management

WHEREASthe Contract for the supply of a Firearm Control System orlted 30 September 2004 (hereinafter referred to as the Contract) provides for the amendment of the Contract in circumstances where it is necessary for the successful implementation and support of the system

AND WHEREAS circumstances exist where it is necessary to amend certain provisions of the Contract

NOW therefore the Parties agree as follows shy

1 Acceptance Procedure - Annexure C

The Acceptance Procedure contained in Annexure Cof the Contract is withdrawn and replaced by the Acceptance Procedure contained in Annexure A of this Addendum

2 Bill of Material- Annexure D

The Bill of Material contained in Annexure 0 of the Contract is withdrawn and replaced by the Bill of Material contained in Annexure B of this Addendum

FCS Addendum 03 Date 2006-02-06 1 out of 5

3 Project Schedule Deliverables and Costs Schedule - Annexure E

The FCS Deliverable and Cost Schedule (Project Schedule and Cash flow) contained in Annexure E of the Contract is withdrawn and replaced by the FCS Deliverable and Costs Schedule (Project Schedule and Cash Flow) contained in Annexure Cof this Addendum

4 Commencement

This Addendum will commence on the Signature Date Anything done in terms of this Addendum before the Signature Date shall be deemed to have been done in terms of this Addendum

it SIGNED at Pretoria on 10 February 2006

AS WITNESSES

-1

for ana~n behalf of Waymark duly authorized thereto

SIGNED at Pretoria on I11( February 2006

AS WITNESSES

for and~n behalf of the Service1lulv authorized thereto

~ll~ C~~ff

1)r0V1(tZ

FCS Addendum 03 Dale iVVG-Vi-VG 2out of 5 ~J

Firearms Control System Project

Review of FCS Project Schedule

File Reference Number 32131144 (19)(4)

Date 2006-02-10

Version 50

CD ~- fvTAE ~ ~ 4lf~

----

321311144 Confidential Review of FCS Schedule

Approval Page

Title Review of FCS Project Schedule

Number 32131144 (19)(4)

Version Version 5 0

Date 2006-02-10

Classification Project Confidential

Prepared by WAYMARK INFOTECH

Approved for WAYMARK INFOTECH by

)(J 2- LvOh Date Time ~he

Program Director

Approved for SAPS by

2~ -pgt-~ I~-~

Date Time

Copyright of this work is reserved under the Copyright Act of the Republic of South Africa (No 98 of 1978) and the provisions of the Berne Convention

This work or any part thereof may not be reproduced in any form or by any means without prior permission in writing of

the SAPS unless in pursuance of the recommendations contained herein

-----_ _-__ ----~-~

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page i of iii

~

32131144 Confidential

Table of Contents

1 Introduction 1

2 Factors Considered for the Revised Project Schedule 1

3 Revised Project Execution 8

4 Cost and Schedule Comparison 10

5 Alternative Schedule and Cost option 15

6 Appendix A Additional Factors Previously Considered 17

Annexures

Annexure A Revised Project Schedule

Annexure B Detail Activity Cornparison between Contract Baseline Schedule and Revised Schedule

Date 2006-02-10 PrOject iiiVersion Date 2006-02-10 06 31 Version 50 Page ii of Ill

t

32131144 ProjecL~onfi~~tial Review of FCS Project Schedule ~- - -_-

Abbreviations

Description

c

Police Service

16 SQL

17 TBD

18 UAT

19 VB

20 WDK

21 WMI ~_~YMARK INFOTECH

Privacy Information

This document may contain information of a sensitive nature This information may not be given to persons other than those who are working on the FCS project or who will become involved during the project life cycle

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50

Confidential Review of FCS Prolect Schedule 32131144

1 Introduction

11 The FCS Project Management Team was requested by the Steering Committee to prepare a revised project schedule in response to addendums to the contract

12 This report contains the results of the factors considered and decisions of the FCS Project Management Team taken at planning sessions held during the past months by the SAPS team led by Director Wv Meyer and WAYMARK INFOTECHs team led by Mr J Mpshe (Director)

2 Factors Considered for the Revised Project Schedule

21 The following factors have been considered in this review of the Project Schedule

211 Late availability of the office and related IT infrastructure

212 Delay in establishing the functional baseline

213 Amendment to the deliverable sign-off (approval) process

214 Additional requirements including interfacing with the existing Firearms Register System (FRS)

22 Baseline Schedule

221 The baseline schedule as contained in the contract is shown in Diagram 1 below with the exception that the development phase as indicated below has been corrected to succeed the design phase In the orlgir31 schedule the devF~ori11r-t phase was not linked to the design phase and as such indicated a start date of 2004-10-04 which was incorrect The end date for the development phase remains unchanged

Initiation Phase

Des ign Phase

Developmet Phase bull 2005-07-07

Testing Phase 2006middot01middot19

Documentation Phase

Trairu-g Phase

TransitnPhase

23 Project Office and IT Infrastructure Availability

231 The late availability of office and related IT infrastructure has delayed the completion of the Project Setup Phase with 3 months (indicated in red in Diagram 2below) resulting in the Project Initiation Phase only starting on 7 March 2005 as illustrated in Diagram 2 below - See line item 4

Jl Print Date 2006middot02middot10 Project Confidential ------------~p-age1 of 23 ~ Version Date 2006-02-10 0631 Version 50

Review of FCS Project Scheel lie32131144

~_____ _ w_p _ _ ~_R _

2004-10-04 2004-i2-06

2005middot03-04

2005-037 2005o5~27

200so5-10 2005middot09middot20

200amp-09middot21 100644-20

2006--04-21 2006-067

Phase 2~0-ltgt1-27 200S~06-07

200$06-ltgt8 2006-47-12

2006-ltgt7-13 2006-105

232 As illustrated above the direct effect of this slip was that the project completion would slip from the baseline completion date of 5 July 2006 to 5 October 2006

24 Requirements Definition Complexities

241 The primary factor that has influenced the requirement definition and contributed to the delay in the completion thereof has been the additional User Profile development work This was identified in late April 2005 (5 weeks prior to the planned delivery date for the System Design Framework (SDF)) and as a result the following additional activities that were previously not planned for in the contract her)ule as part of the functio31 b3s-~~r 2- t-gtformed

2411 Acquire Universal Modeling Language (UML) modeling software and product training (two weeks refer revised WBS number 36131 in Annex AampB)

2412 Use case modeling for an estimated 36 cases (four weeks refer revised WBS number 36132 in Annex AampB)

2413 User Profile development and documentation work (four weeks refer to revised WBS 36133 in Annex AampB)_

2414 Due to the fact that some of the activities took place in parallel the net schedule effect has been around six weeks of elapsed time

242 The extent of changes required to the original User Profiles as recorded in the contractual baseline is highlighted in Table 1 below

___Table 1 Extent of User Profile Changes ~ Total New I Deleted _ --I~unchanCied shy

Total Profiles defined during the user profile definition exercise (Original PTech had 37 profiles)

not previously defined in PTech

Profiles that were CFR Deciding

Officer CFR Import Export Official CFR Official CFR Recommendation Officer ISM FCS ISM Official

PTech Profiles that have been unchanged (ie as originally stated) or renamed

91 61 7 30

Percentage 62 7 31 --~--

Print Date 2006~02-1 0 Confidential Version Date 2006-02-10 0631 Version 50 Page 2 of 23

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

3 Project Schedule Deliverables and Costs Schedule - Annexure E

The FCS Deliverable and Cost Schedule (Project Schedule and Cash flow) contained in Annexure E of the Contract is withdrawn and replaced by the FCS Deliverable and Costs Schedule (Project Schedule and Cash Flow) contained in Annexure Cof this Addendum

4 Commencement

This Addendum will commence on the Signature Date Anything done in terms of this Addendum before the Signature Date shall be deemed to have been done in terms of this Addendum

it SIGNED at Pretoria on 10 February 2006

AS WITNESSES

-1

for ana~n behalf of Waymark duly authorized thereto

SIGNED at Pretoria on I11( February 2006

AS WITNESSES

for and~n behalf of the Service1lulv authorized thereto

~ll~ C~~ff

1)r0V1(tZ

FCS Addendum 03 Dale iVVG-Vi-VG 2out of 5 ~J

Firearms Control System Project

Review of FCS Project Schedule

File Reference Number 32131144 (19)(4)

Date 2006-02-10

Version 50

CD ~- fvTAE ~ ~ 4lf~

----

321311144 Confidential Review of FCS Schedule

Approval Page

Title Review of FCS Project Schedule

Number 32131144 (19)(4)

Version Version 5 0

Date 2006-02-10

Classification Project Confidential

Prepared by WAYMARK INFOTECH

Approved for WAYMARK INFOTECH by

)(J 2- LvOh Date Time ~he

Program Director

Approved for SAPS by

2~ -pgt-~ I~-~

Date Time

Copyright of this work is reserved under the Copyright Act of the Republic of South Africa (No 98 of 1978) and the provisions of the Berne Convention

This work or any part thereof may not be reproduced in any form or by any means without prior permission in writing of

the SAPS unless in pursuance of the recommendations contained herein

-----_ _-__ ----~-~

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page i of iii

~

32131144 Confidential

Table of Contents

1 Introduction 1

2 Factors Considered for the Revised Project Schedule 1

3 Revised Project Execution 8

4 Cost and Schedule Comparison 10

5 Alternative Schedule and Cost option 15

6 Appendix A Additional Factors Previously Considered 17

Annexures

Annexure A Revised Project Schedule

Annexure B Detail Activity Cornparison between Contract Baseline Schedule and Revised Schedule

Date 2006-02-10 PrOject iiiVersion Date 2006-02-10 06 31 Version 50 Page ii of Ill

t

32131144 ProjecL~onfi~~tial Review of FCS Project Schedule ~- - -_-

Abbreviations

Description

c

Police Service

16 SQL

17 TBD

18 UAT

19 VB

20 WDK

21 WMI ~_~YMARK INFOTECH

Privacy Information

This document may contain information of a sensitive nature This information may not be given to persons other than those who are working on the FCS project or who will become involved during the project life cycle

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50

Confidential Review of FCS Prolect Schedule 32131144

1 Introduction

11 The FCS Project Management Team was requested by the Steering Committee to prepare a revised project schedule in response to addendums to the contract

12 This report contains the results of the factors considered and decisions of the FCS Project Management Team taken at planning sessions held during the past months by the SAPS team led by Director Wv Meyer and WAYMARK INFOTECHs team led by Mr J Mpshe (Director)

2 Factors Considered for the Revised Project Schedule

21 The following factors have been considered in this review of the Project Schedule

211 Late availability of the office and related IT infrastructure

212 Delay in establishing the functional baseline

213 Amendment to the deliverable sign-off (approval) process

214 Additional requirements including interfacing with the existing Firearms Register System (FRS)

22 Baseline Schedule

221 The baseline schedule as contained in the contract is shown in Diagram 1 below with the exception that the development phase as indicated below has been corrected to succeed the design phase In the orlgir31 schedule the devF~ori11r-t phase was not linked to the design phase and as such indicated a start date of 2004-10-04 which was incorrect The end date for the development phase remains unchanged

Initiation Phase

Des ign Phase

Developmet Phase bull 2005-07-07

Testing Phase 2006middot01middot19

Documentation Phase

Trairu-g Phase

TransitnPhase

23 Project Office and IT Infrastructure Availability

231 The late availability of office and related IT infrastructure has delayed the completion of the Project Setup Phase with 3 months (indicated in red in Diagram 2below) resulting in the Project Initiation Phase only starting on 7 March 2005 as illustrated in Diagram 2 below - See line item 4

Jl Print Date 2006middot02middot10 Project Confidential ------------~p-age1 of 23 ~ Version Date 2006-02-10 0631 Version 50

Review of FCS Project Scheel lie32131144

~_____ _ w_p _ _ ~_R _

2004-10-04 2004-i2-06

2005middot03-04

2005-037 2005o5~27

200so5-10 2005middot09middot20

200amp-09middot21 100644-20

2006--04-21 2006-067

Phase 2~0-ltgt1-27 200S~06-07

200$06-ltgt8 2006-47-12

2006-ltgt7-13 2006-105

232 As illustrated above the direct effect of this slip was that the project completion would slip from the baseline completion date of 5 July 2006 to 5 October 2006

24 Requirements Definition Complexities

241 The primary factor that has influenced the requirement definition and contributed to the delay in the completion thereof has been the additional User Profile development work This was identified in late April 2005 (5 weeks prior to the planned delivery date for the System Design Framework (SDF)) and as a result the following additional activities that were previously not planned for in the contract her)ule as part of the functio31 b3s-~~r 2- t-gtformed

2411 Acquire Universal Modeling Language (UML) modeling software and product training (two weeks refer revised WBS number 36131 in Annex AampB)

2412 Use case modeling for an estimated 36 cases (four weeks refer revised WBS number 36132 in Annex AampB)

2413 User Profile development and documentation work (four weeks refer to revised WBS 36133 in Annex AampB)_

2414 Due to the fact that some of the activities took place in parallel the net schedule effect has been around six weeks of elapsed time

242 The extent of changes required to the original User Profiles as recorded in the contractual baseline is highlighted in Table 1 below

___Table 1 Extent of User Profile Changes ~ Total New I Deleted _ --I~unchanCied shy

Total Profiles defined during the user profile definition exercise (Original PTech had 37 profiles)

not previously defined in PTech

Profiles that were CFR Deciding

Officer CFR Import Export Official CFR Official CFR Recommendation Officer ISM FCS ISM Official

PTech Profiles that have been unchanged (ie as originally stated) or renamed

91 61 7 30

Percentage 62 7 31 --~--

Print Date 2006~02-1 0 Confidential Version Date 2006-02-10 0631 Version 50 Page 2 of 23

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

Firearms Control System Project

Review of FCS Project Schedule

File Reference Number 32131144 (19)(4)

Date 2006-02-10

Version 50

CD ~- fvTAE ~ ~ 4lf~

----

321311144 Confidential Review of FCS Schedule

Approval Page

Title Review of FCS Project Schedule

Number 32131144 (19)(4)

Version Version 5 0

Date 2006-02-10

Classification Project Confidential

Prepared by WAYMARK INFOTECH

Approved for WAYMARK INFOTECH by

)(J 2- LvOh Date Time ~he

Program Director

Approved for SAPS by

2~ -pgt-~ I~-~

Date Time

Copyright of this work is reserved under the Copyright Act of the Republic of South Africa (No 98 of 1978) and the provisions of the Berne Convention

This work or any part thereof may not be reproduced in any form or by any means without prior permission in writing of

the SAPS unless in pursuance of the recommendations contained herein

-----_ _-__ ----~-~

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page i of iii

~

32131144 Confidential

Table of Contents

1 Introduction 1

2 Factors Considered for the Revised Project Schedule 1

3 Revised Project Execution 8

4 Cost and Schedule Comparison 10

5 Alternative Schedule and Cost option 15

6 Appendix A Additional Factors Previously Considered 17

Annexures

Annexure A Revised Project Schedule

Annexure B Detail Activity Cornparison between Contract Baseline Schedule and Revised Schedule

Date 2006-02-10 PrOject iiiVersion Date 2006-02-10 06 31 Version 50 Page ii of Ill

t

32131144 ProjecL~onfi~~tial Review of FCS Project Schedule ~- - -_-

Abbreviations

Description

c

Police Service

16 SQL

17 TBD

18 UAT

19 VB

20 WDK

21 WMI ~_~YMARK INFOTECH

Privacy Information

This document may contain information of a sensitive nature This information may not be given to persons other than those who are working on the FCS project or who will become involved during the project life cycle

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50

Confidential Review of FCS Prolect Schedule 32131144

1 Introduction

11 The FCS Project Management Team was requested by the Steering Committee to prepare a revised project schedule in response to addendums to the contract

12 This report contains the results of the factors considered and decisions of the FCS Project Management Team taken at planning sessions held during the past months by the SAPS team led by Director Wv Meyer and WAYMARK INFOTECHs team led by Mr J Mpshe (Director)

2 Factors Considered for the Revised Project Schedule

21 The following factors have been considered in this review of the Project Schedule

211 Late availability of the office and related IT infrastructure

212 Delay in establishing the functional baseline

213 Amendment to the deliverable sign-off (approval) process

214 Additional requirements including interfacing with the existing Firearms Register System (FRS)

22 Baseline Schedule

221 The baseline schedule as contained in the contract is shown in Diagram 1 below with the exception that the development phase as indicated below has been corrected to succeed the design phase In the orlgir31 schedule the devF~ori11r-t phase was not linked to the design phase and as such indicated a start date of 2004-10-04 which was incorrect The end date for the development phase remains unchanged

Initiation Phase

Des ign Phase

Developmet Phase bull 2005-07-07

Testing Phase 2006middot01middot19

Documentation Phase

Trairu-g Phase

TransitnPhase

23 Project Office and IT Infrastructure Availability

231 The late availability of office and related IT infrastructure has delayed the completion of the Project Setup Phase with 3 months (indicated in red in Diagram 2below) resulting in the Project Initiation Phase only starting on 7 March 2005 as illustrated in Diagram 2 below - See line item 4

Jl Print Date 2006middot02middot10 Project Confidential ------------~p-age1 of 23 ~ Version Date 2006-02-10 0631 Version 50

Review of FCS Project Scheel lie32131144

~_____ _ w_p _ _ ~_R _

2004-10-04 2004-i2-06

2005middot03-04

2005-037 2005o5~27

200so5-10 2005middot09middot20

200amp-09middot21 100644-20

2006--04-21 2006-067

Phase 2~0-ltgt1-27 200S~06-07

200$06-ltgt8 2006-47-12

2006-ltgt7-13 2006-105

232 As illustrated above the direct effect of this slip was that the project completion would slip from the baseline completion date of 5 July 2006 to 5 October 2006

24 Requirements Definition Complexities

241 The primary factor that has influenced the requirement definition and contributed to the delay in the completion thereof has been the additional User Profile development work This was identified in late April 2005 (5 weeks prior to the planned delivery date for the System Design Framework (SDF)) and as a result the following additional activities that were previously not planned for in the contract her)ule as part of the functio31 b3s-~~r 2- t-gtformed

2411 Acquire Universal Modeling Language (UML) modeling software and product training (two weeks refer revised WBS number 36131 in Annex AampB)

2412 Use case modeling for an estimated 36 cases (four weeks refer revised WBS number 36132 in Annex AampB)

2413 User Profile development and documentation work (four weeks refer to revised WBS 36133 in Annex AampB)_

2414 Due to the fact that some of the activities took place in parallel the net schedule effect has been around six weeks of elapsed time

242 The extent of changes required to the original User Profiles as recorded in the contractual baseline is highlighted in Table 1 below

___Table 1 Extent of User Profile Changes ~ Total New I Deleted _ --I~unchanCied shy

Total Profiles defined during the user profile definition exercise (Original PTech had 37 profiles)

not previously defined in PTech

Profiles that were CFR Deciding

Officer CFR Import Export Official CFR Official CFR Recommendation Officer ISM FCS ISM Official

PTech Profiles that have been unchanged (ie as originally stated) or renamed

91 61 7 30

Percentage 62 7 31 --~--

Print Date 2006~02-1 0 Confidential Version Date 2006-02-10 0631 Version 50 Page 2 of 23

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

----

321311144 Confidential Review of FCS Schedule

Approval Page

Title Review of FCS Project Schedule

Number 32131144 (19)(4)

Version Version 5 0

Date 2006-02-10

Classification Project Confidential

Prepared by WAYMARK INFOTECH

Approved for WAYMARK INFOTECH by

)(J 2- LvOh Date Time ~he

Program Director

Approved for SAPS by

2~ -pgt-~ I~-~

Date Time

Copyright of this work is reserved under the Copyright Act of the Republic of South Africa (No 98 of 1978) and the provisions of the Berne Convention

This work or any part thereof may not be reproduced in any form or by any means without prior permission in writing of

the SAPS unless in pursuance of the recommendations contained herein

-----_ _-__ ----~-~

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page i of iii

~

32131144 Confidential

Table of Contents

1 Introduction 1

2 Factors Considered for the Revised Project Schedule 1

3 Revised Project Execution 8

4 Cost and Schedule Comparison 10

5 Alternative Schedule and Cost option 15

6 Appendix A Additional Factors Previously Considered 17

Annexures

Annexure A Revised Project Schedule

Annexure B Detail Activity Cornparison between Contract Baseline Schedule and Revised Schedule

Date 2006-02-10 PrOject iiiVersion Date 2006-02-10 06 31 Version 50 Page ii of Ill

t

32131144 ProjecL~onfi~~tial Review of FCS Project Schedule ~- - -_-

Abbreviations

Description

c

Police Service

16 SQL

17 TBD

18 UAT

19 VB

20 WDK

21 WMI ~_~YMARK INFOTECH

Privacy Information

This document may contain information of a sensitive nature This information may not be given to persons other than those who are working on the FCS project or who will become involved during the project life cycle

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50

Confidential Review of FCS Prolect Schedule 32131144

1 Introduction

11 The FCS Project Management Team was requested by the Steering Committee to prepare a revised project schedule in response to addendums to the contract

12 This report contains the results of the factors considered and decisions of the FCS Project Management Team taken at planning sessions held during the past months by the SAPS team led by Director Wv Meyer and WAYMARK INFOTECHs team led by Mr J Mpshe (Director)

2 Factors Considered for the Revised Project Schedule

21 The following factors have been considered in this review of the Project Schedule

211 Late availability of the office and related IT infrastructure

212 Delay in establishing the functional baseline

213 Amendment to the deliverable sign-off (approval) process

214 Additional requirements including interfacing with the existing Firearms Register System (FRS)

22 Baseline Schedule

221 The baseline schedule as contained in the contract is shown in Diagram 1 below with the exception that the development phase as indicated below has been corrected to succeed the design phase In the orlgir31 schedule the devF~ori11r-t phase was not linked to the design phase and as such indicated a start date of 2004-10-04 which was incorrect The end date for the development phase remains unchanged

Initiation Phase

Des ign Phase

Developmet Phase bull 2005-07-07

Testing Phase 2006middot01middot19

Documentation Phase

Trairu-g Phase

TransitnPhase

23 Project Office and IT Infrastructure Availability

231 The late availability of office and related IT infrastructure has delayed the completion of the Project Setup Phase with 3 months (indicated in red in Diagram 2below) resulting in the Project Initiation Phase only starting on 7 March 2005 as illustrated in Diagram 2 below - See line item 4

Jl Print Date 2006middot02middot10 Project Confidential ------------~p-age1 of 23 ~ Version Date 2006-02-10 0631 Version 50

Review of FCS Project Scheel lie32131144

~_____ _ w_p _ _ ~_R _

2004-10-04 2004-i2-06

2005middot03-04

2005-037 2005o5~27

200so5-10 2005middot09middot20

200amp-09middot21 100644-20

2006--04-21 2006-067

Phase 2~0-ltgt1-27 200S~06-07

200$06-ltgt8 2006-47-12

2006-ltgt7-13 2006-105

232 As illustrated above the direct effect of this slip was that the project completion would slip from the baseline completion date of 5 July 2006 to 5 October 2006

24 Requirements Definition Complexities

241 The primary factor that has influenced the requirement definition and contributed to the delay in the completion thereof has been the additional User Profile development work This was identified in late April 2005 (5 weeks prior to the planned delivery date for the System Design Framework (SDF)) and as a result the following additional activities that were previously not planned for in the contract her)ule as part of the functio31 b3s-~~r 2- t-gtformed

2411 Acquire Universal Modeling Language (UML) modeling software and product training (two weeks refer revised WBS number 36131 in Annex AampB)

2412 Use case modeling for an estimated 36 cases (four weeks refer revised WBS number 36132 in Annex AampB)

2413 User Profile development and documentation work (four weeks refer to revised WBS 36133 in Annex AampB)_

2414 Due to the fact that some of the activities took place in parallel the net schedule effect has been around six weeks of elapsed time

242 The extent of changes required to the original User Profiles as recorded in the contractual baseline is highlighted in Table 1 below

___Table 1 Extent of User Profile Changes ~ Total New I Deleted _ --I~unchanCied shy

Total Profiles defined during the user profile definition exercise (Original PTech had 37 profiles)

not previously defined in PTech

Profiles that were CFR Deciding

Officer CFR Import Export Official CFR Official CFR Recommendation Officer ISM FCS ISM Official

PTech Profiles that have been unchanged (ie as originally stated) or renamed

91 61 7 30

Percentage 62 7 31 --~--

Print Date 2006~02-1 0 Confidential Version Date 2006-02-10 0631 Version 50 Page 2 of 23

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

32131144 Confidential

Table of Contents

1 Introduction 1

2 Factors Considered for the Revised Project Schedule 1

3 Revised Project Execution 8

4 Cost and Schedule Comparison 10

5 Alternative Schedule and Cost option 15

6 Appendix A Additional Factors Previously Considered 17

Annexures

Annexure A Revised Project Schedule

Annexure B Detail Activity Cornparison between Contract Baseline Schedule and Revised Schedule

Date 2006-02-10 PrOject iiiVersion Date 2006-02-10 06 31 Version 50 Page ii of Ill

t

32131144 ProjecL~onfi~~tial Review of FCS Project Schedule ~- - -_-

Abbreviations

Description

c

Police Service

16 SQL

17 TBD

18 UAT

19 VB

20 WDK

21 WMI ~_~YMARK INFOTECH

Privacy Information

This document may contain information of a sensitive nature This information may not be given to persons other than those who are working on the FCS project or who will become involved during the project life cycle

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50

Confidential Review of FCS Prolect Schedule 32131144

1 Introduction

11 The FCS Project Management Team was requested by the Steering Committee to prepare a revised project schedule in response to addendums to the contract

12 This report contains the results of the factors considered and decisions of the FCS Project Management Team taken at planning sessions held during the past months by the SAPS team led by Director Wv Meyer and WAYMARK INFOTECHs team led by Mr J Mpshe (Director)

2 Factors Considered for the Revised Project Schedule

21 The following factors have been considered in this review of the Project Schedule

211 Late availability of the office and related IT infrastructure

212 Delay in establishing the functional baseline

213 Amendment to the deliverable sign-off (approval) process

214 Additional requirements including interfacing with the existing Firearms Register System (FRS)

22 Baseline Schedule

221 The baseline schedule as contained in the contract is shown in Diagram 1 below with the exception that the development phase as indicated below has been corrected to succeed the design phase In the orlgir31 schedule the devF~ori11r-t phase was not linked to the design phase and as such indicated a start date of 2004-10-04 which was incorrect The end date for the development phase remains unchanged

Initiation Phase

Des ign Phase

Developmet Phase bull 2005-07-07

Testing Phase 2006middot01middot19

Documentation Phase

Trairu-g Phase

TransitnPhase

23 Project Office and IT Infrastructure Availability

231 The late availability of office and related IT infrastructure has delayed the completion of the Project Setup Phase with 3 months (indicated in red in Diagram 2below) resulting in the Project Initiation Phase only starting on 7 March 2005 as illustrated in Diagram 2 below - See line item 4

Jl Print Date 2006middot02middot10 Project Confidential ------------~p-age1 of 23 ~ Version Date 2006-02-10 0631 Version 50

Review of FCS Project Scheel lie32131144

~_____ _ w_p _ _ ~_R _

2004-10-04 2004-i2-06

2005middot03-04

2005-037 2005o5~27

200so5-10 2005middot09middot20

200amp-09middot21 100644-20

2006--04-21 2006-067

Phase 2~0-ltgt1-27 200S~06-07

200$06-ltgt8 2006-47-12

2006-ltgt7-13 2006-105

232 As illustrated above the direct effect of this slip was that the project completion would slip from the baseline completion date of 5 July 2006 to 5 October 2006

24 Requirements Definition Complexities

241 The primary factor that has influenced the requirement definition and contributed to the delay in the completion thereof has been the additional User Profile development work This was identified in late April 2005 (5 weeks prior to the planned delivery date for the System Design Framework (SDF)) and as a result the following additional activities that were previously not planned for in the contract her)ule as part of the functio31 b3s-~~r 2- t-gtformed

2411 Acquire Universal Modeling Language (UML) modeling software and product training (two weeks refer revised WBS number 36131 in Annex AampB)

2412 Use case modeling for an estimated 36 cases (four weeks refer revised WBS number 36132 in Annex AampB)

2413 User Profile development and documentation work (four weeks refer to revised WBS 36133 in Annex AampB)_

2414 Due to the fact that some of the activities took place in parallel the net schedule effect has been around six weeks of elapsed time

242 The extent of changes required to the original User Profiles as recorded in the contractual baseline is highlighted in Table 1 below

___Table 1 Extent of User Profile Changes ~ Total New I Deleted _ --I~unchanCied shy

Total Profiles defined during the user profile definition exercise (Original PTech had 37 profiles)

not previously defined in PTech

Profiles that were CFR Deciding

Officer CFR Import Export Official CFR Official CFR Recommendation Officer ISM FCS ISM Official

PTech Profiles that have been unchanged (ie as originally stated) or renamed

91 61 7 30

Percentage 62 7 31 --~--

Print Date 2006~02-1 0 Confidential Version Date 2006-02-10 0631 Version 50 Page 2 of 23

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

32131144 ProjecL~onfi~~tial Review of FCS Project Schedule ~- - -_-

Abbreviations

Description

c

Police Service

16 SQL

17 TBD

18 UAT

19 VB

20 WDK

21 WMI ~_~YMARK INFOTECH

Privacy Information

This document may contain information of a sensitive nature This information may not be given to persons other than those who are working on the FCS project or who will become involved during the project life cycle

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50

Confidential Review of FCS Prolect Schedule 32131144

1 Introduction

11 The FCS Project Management Team was requested by the Steering Committee to prepare a revised project schedule in response to addendums to the contract

12 This report contains the results of the factors considered and decisions of the FCS Project Management Team taken at planning sessions held during the past months by the SAPS team led by Director Wv Meyer and WAYMARK INFOTECHs team led by Mr J Mpshe (Director)

2 Factors Considered for the Revised Project Schedule

21 The following factors have been considered in this review of the Project Schedule

211 Late availability of the office and related IT infrastructure

212 Delay in establishing the functional baseline

213 Amendment to the deliverable sign-off (approval) process

214 Additional requirements including interfacing with the existing Firearms Register System (FRS)

22 Baseline Schedule

221 The baseline schedule as contained in the contract is shown in Diagram 1 below with the exception that the development phase as indicated below has been corrected to succeed the design phase In the orlgir31 schedule the devF~ori11r-t phase was not linked to the design phase and as such indicated a start date of 2004-10-04 which was incorrect The end date for the development phase remains unchanged

Initiation Phase

Des ign Phase

Developmet Phase bull 2005-07-07

Testing Phase 2006middot01middot19

Documentation Phase

Trairu-g Phase

TransitnPhase

23 Project Office and IT Infrastructure Availability

231 The late availability of office and related IT infrastructure has delayed the completion of the Project Setup Phase with 3 months (indicated in red in Diagram 2below) resulting in the Project Initiation Phase only starting on 7 March 2005 as illustrated in Diagram 2 below - See line item 4

Jl Print Date 2006middot02middot10 Project Confidential ------------~p-age1 of 23 ~ Version Date 2006-02-10 0631 Version 50

Review of FCS Project Scheel lie32131144

~_____ _ w_p _ _ ~_R _

2004-10-04 2004-i2-06

2005middot03-04

2005-037 2005o5~27

200so5-10 2005middot09middot20

200amp-09middot21 100644-20

2006--04-21 2006-067

Phase 2~0-ltgt1-27 200S~06-07

200$06-ltgt8 2006-47-12

2006-ltgt7-13 2006-105

232 As illustrated above the direct effect of this slip was that the project completion would slip from the baseline completion date of 5 July 2006 to 5 October 2006

24 Requirements Definition Complexities

241 The primary factor that has influenced the requirement definition and contributed to the delay in the completion thereof has been the additional User Profile development work This was identified in late April 2005 (5 weeks prior to the planned delivery date for the System Design Framework (SDF)) and as a result the following additional activities that were previously not planned for in the contract her)ule as part of the functio31 b3s-~~r 2- t-gtformed

2411 Acquire Universal Modeling Language (UML) modeling software and product training (two weeks refer revised WBS number 36131 in Annex AampB)

2412 Use case modeling for an estimated 36 cases (four weeks refer revised WBS number 36132 in Annex AampB)

2413 User Profile development and documentation work (four weeks refer to revised WBS 36133 in Annex AampB)_

2414 Due to the fact that some of the activities took place in parallel the net schedule effect has been around six weeks of elapsed time

242 The extent of changes required to the original User Profiles as recorded in the contractual baseline is highlighted in Table 1 below

___Table 1 Extent of User Profile Changes ~ Total New I Deleted _ --I~unchanCied shy

Total Profiles defined during the user profile definition exercise (Original PTech had 37 profiles)

not previously defined in PTech

Profiles that were CFR Deciding

Officer CFR Import Export Official CFR Official CFR Recommendation Officer ISM FCS ISM Official

PTech Profiles that have been unchanged (ie as originally stated) or renamed

91 61 7 30

Percentage 62 7 31 --~--

Print Date 2006~02-1 0 Confidential Version Date 2006-02-10 0631 Version 50 Page 2 of 23

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

Confidential Review of FCS Prolect Schedule 32131144

1 Introduction

11 The FCS Project Management Team was requested by the Steering Committee to prepare a revised project schedule in response to addendums to the contract

12 This report contains the results of the factors considered and decisions of the FCS Project Management Team taken at planning sessions held during the past months by the SAPS team led by Director Wv Meyer and WAYMARK INFOTECHs team led by Mr J Mpshe (Director)

2 Factors Considered for the Revised Project Schedule

21 The following factors have been considered in this review of the Project Schedule

211 Late availability of the office and related IT infrastructure

212 Delay in establishing the functional baseline

213 Amendment to the deliverable sign-off (approval) process

214 Additional requirements including interfacing with the existing Firearms Register System (FRS)

22 Baseline Schedule

221 The baseline schedule as contained in the contract is shown in Diagram 1 below with the exception that the development phase as indicated below has been corrected to succeed the design phase In the orlgir31 schedule the devF~ori11r-t phase was not linked to the design phase and as such indicated a start date of 2004-10-04 which was incorrect The end date for the development phase remains unchanged

Initiation Phase

Des ign Phase

Developmet Phase bull 2005-07-07

Testing Phase 2006middot01middot19

Documentation Phase

Trairu-g Phase

TransitnPhase

23 Project Office and IT Infrastructure Availability

231 The late availability of office and related IT infrastructure has delayed the completion of the Project Setup Phase with 3 months (indicated in red in Diagram 2below) resulting in the Project Initiation Phase only starting on 7 March 2005 as illustrated in Diagram 2 below - See line item 4

Jl Print Date 2006middot02middot10 Project Confidential ------------~p-age1 of 23 ~ Version Date 2006-02-10 0631 Version 50

Review of FCS Project Scheel lie32131144

~_____ _ w_p _ _ ~_R _

2004-10-04 2004-i2-06

2005middot03-04

2005-037 2005o5~27

200so5-10 2005middot09middot20

200amp-09middot21 100644-20

2006--04-21 2006-067

Phase 2~0-ltgt1-27 200S~06-07

200$06-ltgt8 2006-47-12

2006-ltgt7-13 2006-105

232 As illustrated above the direct effect of this slip was that the project completion would slip from the baseline completion date of 5 July 2006 to 5 October 2006

24 Requirements Definition Complexities

241 The primary factor that has influenced the requirement definition and contributed to the delay in the completion thereof has been the additional User Profile development work This was identified in late April 2005 (5 weeks prior to the planned delivery date for the System Design Framework (SDF)) and as a result the following additional activities that were previously not planned for in the contract her)ule as part of the functio31 b3s-~~r 2- t-gtformed

2411 Acquire Universal Modeling Language (UML) modeling software and product training (two weeks refer revised WBS number 36131 in Annex AampB)

2412 Use case modeling for an estimated 36 cases (four weeks refer revised WBS number 36132 in Annex AampB)

2413 User Profile development and documentation work (four weeks refer to revised WBS 36133 in Annex AampB)_

2414 Due to the fact that some of the activities took place in parallel the net schedule effect has been around six weeks of elapsed time

242 The extent of changes required to the original User Profiles as recorded in the contractual baseline is highlighted in Table 1 below

___Table 1 Extent of User Profile Changes ~ Total New I Deleted _ --I~unchanCied shy

Total Profiles defined during the user profile definition exercise (Original PTech had 37 profiles)

not previously defined in PTech

Profiles that were CFR Deciding

Officer CFR Import Export Official CFR Official CFR Recommendation Officer ISM FCS ISM Official

PTech Profiles that have been unchanged (ie as originally stated) or renamed

91 61 7 30

Percentage 62 7 31 --~--

Print Date 2006~02-1 0 Confidential Version Date 2006-02-10 0631 Version 50 Page 2 of 23

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

Review of FCS Project Scheel lie32131144

~_____ _ w_p _ _ ~_R _

2004-10-04 2004-i2-06

2005middot03-04

2005-037 2005o5~27

200so5-10 2005middot09middot20

200amp-09middot21 100644-20

2006--04-21 2006-067

Phase 2~0-ltgt1-27 200S~06-07

200$06-ltgt8 2006-47-12

2006-ltgt7-13 2006-105

232 As illustrated above the direct effect of this slip was that the project completion would slip from the baseline completion date of 5 July 2006 to 5 October 2006

24 Requirements Definition Complexities

241 The primary factor that has influenced the requirement definition and contributed to the delay in the completion thereof has been the additional User Profile development work This was identified in late April 2005 (5 weeks prior to the planned delivery date for the System Design Framework (SDF)) and as a result the following additional activities that were previously not planned for in the contract her)ule as part of the functio31 b3s-~~r 2- t-gtformed

2411 Acquire Universal Modeling Language (UML) modeling software and product training (two weeks refer revised WBS number 36131 in Annex AampB)

2412 Use case modeling for an estimated 36 cases (four weeks refer revised WBS number 36132 in Annex AampB)

2413 User Profile development and documentation work (four weeks refer to revised WBS 36133 in Annex AampB)_

2414 Due to the fact that some of the activities took place in parallel the net schedule effect has been around six weeks of elapsed time

242 The extent of changes required to the original User Profiles as recorded in the contractual baseline is highlighted in Table 1 below

___Table 1 Extent of User Profile Changes ~ Total New I Deleted _ --I~unchanCied shy

Total Profiles defined during the user profile definition exercise (Original PTech had 37 profiles)

not previously defined in PTech

Profiles that were CFR Deciding

Officer CFR Import Export Official CFR Official CFR Recommendation Officer ISM FCS ISM Official

PTech Profiles that have been unchanged (ie as originally stated) or renamed

91 61 7 30

Percentage 62 7 31 --~--

Print Date 2006~02-1 0 Confidential Version Date 2006-02-10 0631 Version 50 Page 2 of 23

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

32131144 (1 Confidential Review of FCS Pr()lect Schedule ~~--

243 The initial effect was that the first version of the System Design Framework was delivered on the 8th of July 2005 instead of the planned date of 30 May 2005 (28 February 2005 plus the Setup Phase 3 months slip refer Contract Baseline WBS number 80 and revised WBS number 361 in Annex AampB) This resulted in a slip of 15 months (6 working weeks) - See line item 6 indicated in red in Diagram 3 below The effect of this delay in addition to the initial 3 months delay was that the expected system handover date would move from 5 October 2006 as detailed above to 16 November 2006 (15 months 6 working weeks)

Plamed Project Setup 2004-10J4

Scredtie slippage due to infrastJUClcre (3 monihs) 20Q4-12~7 2005middot03middot04

200so3-07 2005-67-08

2005--03-07 2005~05-27

Scredule slippage due to requirement eslablishme 2005middot05-30 2005-07 middot08 cornntfxities (15 months)

ooso7middot11 2005-11-01

2005--0711 2005middot11-01 -2005-11il2 200~o1

ioos ilmiddotn 2006~OO~01shy

2OQamp-06o2 200~01~19

Establishment Effect

iDocumentation Phase 200amp-03-10 2006-01middot19

200$-01~20 2006-M~23

200amp-08~24 2006--11-16

244 It must be noted that the additional User profiles and changes will have a further knock-on effect in regards to the development of the applicable design and build specifications This knock-on effect will result from the additional level of detail

-~~shymiddotfiSht4~~~_

ain influence will be on revised WBS numbers 413 r-~jlt~---- _~__ _ _ t ~

User Profiles Specifications and 4211 Finalise User Profile Specs 416 Reporting amp BI Design Specification 418 System Design Specification 419 Competency amp Accreditation Build Specifications 426 General Enquiry Function Design and 51031 Design Firearm Control Processe~lbJsect~9diti~~ ~nSt~ilIJ~~~~gr~~- QLvvAYMe-BI5J~EQltQI1 withi(1 the proposed neW aeslgn and development ph~s~ SGb~9Vle a(19Clciviti~s bull

245 It has since been decided that the PTech models will be updated accordingly by the SAPS to enhance the baseline (Refer revised WBS number 4212)

246 WAYMARK INFOTECH will proceed with the system design with the changed shyUser Profiles as currently known Upon completion of the PTech model update a review will be held to determine jf further design changes are required which if required will be handled as formal changes (Refer revised WBS numbers 4213 to 4217)

25 Delay in Functional Baseline Review and Approval Process

251 The review and approval process turn around time has been excee contractual review and approval period as illustrated below

Print Date 2006-02-1 o----c---middot-~----middot-~---middot-middot-~~-~---shyProject Co nfidentialmiddot

Version Date 2006-02-100631 Version 5 0

Project Confidential Review of FCS Schedule312113111144

2511 The Functional Data Sheets (revised WBS 3611) were delivered on 2005-05shy04 and the feedback from SAPS was received on 2005-08-22 (16 weeks revised WBS 3631) The Functional Data Sheets are approximately 1800 pages in total and were also reviewed with the System Design Framework The updated Functional Data Sheets were delivered on 2005-10-17 (8 weeks revised WBS 3704) for approval after completion of the System Design Framework review as well to ensure correct referencing and technical integrity between the documents

2512 The System Design Framework was delivered on 2005-07-08 and due to its size and complexity on both the technical and functional size the document went through various review cycles to ensure that all comments from all relevant roll players were incorporated This resulted in the final deliverable being submitted for approval on the 2005-10-17

2513 The main contributing factors to the extended review and update periods are the complexity of the system physical size of the documents impact of the additional User profiles availability of the key decision makers and the slips leading to the updates and additional reviews having to be done in parallel to Design Phase work that had already started

252 The Functional Baseline should have been completed in time for the Design to start on the 2005-07-18

253 If the design Phase started in August parallel to the Functional Baseline review process taking only 1 month (4 working weeks) of the extended review and approval duration into consideration as indicated in line item 7 (in red) in Diagram 4 below the fin31 delive-y date vIill slip to 2006-12-14 as shown in Diag r

Diagram 4 D~lay in Functional Baseline Review and ApprovaL_~__~ ID jTaskName S~at j Finish ( ~- - 2005 - bull Imiddotmiddot -~--2006 ~~----Y--~l

I I I LL Q4-01T-Q2~Q3I~T~Q2 Uamp_-I~ I Q I___I~______~____~~____~~_~___ -~~----T~S ~O ~ J F MI AiM ~ Jll~_L~lQlll4l lEl~ampJYI Ji rA 1 0 NjDiTj F I 1 iProjeetSetup 2004-10-44 200Il-00lt14 iiiiiiii =--J bull I I I

i I i I i I i~ Plamed Project Setup z004-10-o4 1004middot12middot06 I iIiiiiiiiIi 1

3 SchedLle slippage due to infrastnlctlle (3 months) 2004-12-01 2005-03middot04 ~ ~4-ilnitlatlon Phase 20S-ltl1r 2005-10middot11

I Ptamed Initiation Ptase 200503 -0 1 2005-05middot27

Schedule slippage due to requirementeslablistvne 2005 05middot30 2005-07-08 complexities (15 monlhs) Schedule slippage due to exterded review and approvalprocess (1 month) Final Update$ and~provaJ-1Design Phase

~~m 13 1Testing Phase

TsIDocumenlation Phase

-UTraining Phase

~--~J 19 iTransilion Phase

2005middot07middot11 2005-08-05

2005-0S-08 2005-10-17

Zbullbull ZOO5-11middot29

2005-11-3 2006-00middotZ5

2006-06JO 2009-04middot19

2oo1l-04-or 2006-08-16

200$lt)bullbull17 2006Qg~20

tOOamp-O~21 2006middot12middot14

(dlJ Print Date 2006-02-10 Prn~ ~ Version Date 2006-02-100631middot Version 50 Page 4 of 23

32131144 1 _ ___~~~--J-- Co~fidential Review oj FCS Proje~t~~hedule

26 Extended Review and Approval Process

261 In addition to the additional work involved in the protracted and extended review and approval process the primary effect is the slip in and recycling of follow on design work It was estimated that to increase the average approval period frorn 5 to 15 days as propo5ed during the August Steering Committee meeting would cause the end date to slip by one year to late into 2007 (The approximately 50 remaining reviewapproval activities at 5 days additional each with overlap taken into consideration represent 250 additional working days)

262 This clearly indicates that it is not viable to extend the review and approval time significantly beyond the contracted 5 day period This was however extended to a 7 -day period in the revised project schedule The work load on the SAPS functional and technical quality assurance teams being Supt (f) Geldenhuys and Mrs Le Roux and Mrs Pienaar and Mr Mollentze respectively is of such a magnitude that it necessitates additional time

27 Additional Requirements

271 Increased Core System Scope

2711 Discussions with the SAPS Project Team in August 2005 have indicated a requirement to increase the scope of the Core System beyond what was originally planned for the Core System

2712 This request was considered and tre irnpact assessed as detailed in APIshyA paragraph 61

2713 In summary it was estimated that this change would delay the review of the Core System well into 2007 which would put a serious risk on the completion of the production release well before the end of 2007

2714 After this implication was reviewed this requirement was withdrawn and it was agreed to keep to the scope and approach as contracted with the exclusion of the Declaration of Unfitness process The latter will be replaced with Specialized Printing which will require that the FCS must be able to print to the Eltron 720 Zebra printer

272 Updates to the Requirements Baseline (PTech models)

2721 Two main deficiencies in the PTech Models have since been identified during the execution of some of the design work

27211 ENQUIRY FUNCTIONS associated with the varioLls processes were not defined in the PTech models or requirements baseline

272111 A list of the envisaged Systems Enquiry functions was provided to WAYMARK INFOTECH This has been included in revised WBS 426

272112 The PTech models will be updated accordingly by the SAPS (revised WBS ~ 4211) to enhance the baseline The updated requirements baseline will be presented to WAYMARK INFOTECH to review (revised WBS 4213 and assess if there are further implications on development (if any) for implementation as a formal change

deg4i4J1 bull IPrint Date 2006-02~1 0 Confidential )I

Version Date 2006-02-100631 Version 50 Page 5 of 23 ~

32131144 1 _ ___~~~--J-- Co~fidential Review oj FCS Proje~t~~hedule

26 Extended Review and Approval Process

261 In addition to the additional work involved in the protracted and extended review and approval process the primary effect is the slip in and recycling of follow on design work It was estimated that to increase the average approval period frorn 5 to 15 days as propo5ed during the August Steering Committee meeting would cause the end date to slip by one year to late into 2007 (The approximately 50 remaining reviewapproval activities at 5 days additional each with overlap taken into consideration represent 250 additional working days)

262 This clearly indicates that it is not viable to extend the review and approval time significantly beyond the contracted 5 day period This was however extended to a 7 -day period in the revised project schedule The work load on the SAPS functional and technical quality assurance teams being Supt (f) Geldenhuys and Mrs Le Roux and Mrs Pienaar and Mr Mollentze respectively is of such a magnitude that it necessitates additional time

27 Additional Requirements

271 Increased Core System Scope

2711 Discussions with the SAPS Project Team in August 2005 have indicated a requirement to increase the scope of the Core System beyond what was originally planned for the Core System

2712 This request was considered and tre irnpact assessed as detailed in APIshyA paragraph 61

2713 In summary it was estimated that this change would delay the review of the Core System well into 2007 which would put a serious risk on the completion of the production release well before the end of 2007

2714 After this implication was reviewed this requirement was withdrawn and it was agreed to keep to the scope and approach as contracted with the exclusion of the Declaration of Unfitness process The latter will be replaced with Specialized Printing which will require that the FCS must be able to print to the Eltron 720 Zebra printer

272 Updates to the Requirements Baseline (PTech models)

2721 Two main deficiencies in the PTech Models have since been identified during the execution of some of the design work

27211 ENQUIRY FUNCTIONS associated with the varioLls processes were not defined in the PTech models or requirements baseline

272111 A list of the envisaged Systems Enquiry functions was provided to WAYMARK INFOTECH This has been included in revised WBS 426

272112 The PTech models will be updated accordingly by the SAPS (revised WBS ~ 4211) to enhance the baseline The updated requirements baseline will be presented to WAYMARK INFOTECH to review (revised WBS 4213 and assess if there are further implications on development (if any) for implementation as a formal change

deg4i4J1 bull IPrint Date 2006-02~1 0 Confidential )I

Version Date 2006-02-100631 Version 50 Page 5 of 23 ~

32131144 (19)(41 ____ ~__________~_______-_____Confidential Review of FCS Project Schedule

2721_2 jiiiifIILfiUUlillbullbull-(~~~~Ifm~of~Tvarl9us ~CJWL(UIIa1o~~--appJOVEf~1 iyenm~~~ ~tdlfN-middot -

The FeS side of the interfaces inclusive of the Interface Control Document (ICD) will be done as contracted while the SAPS will ensure that the other side of the interface will be done by the respective Systems as required

272122 The effect of this approach is that ad J~~ wili have to be spent [see -~~~_ 2 in the addendum to this report] on interacting with the

teChnical teams of the different systems to ensure the resultant specification (interfaces) are mutually acceptable This has no additional scb~~~~

~eJ~_~itJc0_y)lif~tgtrf~~~ -- - impact - ~_~_n ~~r

273 Concurrent operability of the FCS and existing Firearms Register System

2731 The contract schedule provided for a once-off small window migration from the old to the new system As the actual implementation situation will require an extended period of concurrent operation an investigation must be done ~o establish a design and execution approach toenableconcurrent operability Concurrent operations will provide the SAPS with the ability to concurrently use the FRS and the FCS until all sites have been converted to the FCS

2732 The FCS Project Management Team reviewed the information currently available and proposed the design and execution approach as summarised below

27321 The solution must ensure that a complete Firearms Control Process can be Exeruted regardless of which system (FRS or FCS) each of the involved Centres are working on

27322 The requirement that the solution must ensureaneff~ctiv IE I _II _II It tQJheFBsectrnuststill be fUlli investigat~d_ JIIIIbullbulll bullbullbullbullilT diiJiJ hi Ire ~~ Ii II 7 I S Jin the addendum to this report

27323 A geographically phased transition approach will be followed to convert sites from the FRS to the FeS

27324 Design and development of the interfacing will be done as an integral part of the development and testing of the FeS to ensure all requirements for the solution are taken into consideration as early as possible to prevent rework and reduce technical risk

27325 Integration and extended testing of the interfaced solution will be done at the Numerus Beta test site using an as is version of the FRS and data

27326 The activities for this have been included in the revised project schedule as presented in paragraph 33 below [See revised WBS items 420 428 and 5102 in the addendum to this report]

2733 Roll-out definition and approach must be finalized in time (ie well before Design Baseline freeze) to accommodate specific requirements that could influence system build to support a specific roll-out approach

274 Interfacellntegration of the FCS with GIS

2741 The interface requirements for FCSGIS interface were not established in the PTech model From the initial FCSGIS interface JAD work seSSIOn the following approach will be followed ~ 1

~ ~4---~-~--~-~--~-----~---~------~~--______________ _7 Print Dale 2006-02-10 Project Confidential I-- Version Dale- 2006-02~10 0631 Version 50 Page 6 of -gt3 t

I

32131144 ( Confidential Review of FCS Project Schedule

2742 Tables and standards for addresses must be correct (as for the GIS system) but contained in the FCS Data will be captured in the FCS to ensure the FCS can operate on its own

2743 The FCS will provide the address information to the GIS system GIS type reports will be generated by the GIS system The interface JAD work session(s) must still proceed to define the interface details

275 tnterfacellntegration of the FCS with Code System

2751 A central code system and standardised code sets do not yet exist For the FCS its own codes and data tables will be created The possibility to interface to a standard system (later) should not be excluded When such a system becomes available the impact of this will be assessed for possible inclusion

2752 Where other codes (ie crime vehicle gender etc) are required these should be obtained from the respective source system via interfaces This must be identified and specified during the interface JAD sessions

276 Integration with a SAPS wide Identity Management solution

2761 At this point in time Identity Management for the FCS will be built as contracted (FCS Stand Alone)

2762 When a SAPS decision on such a corporate system has been made and it becomes a requirement to use it for the FCS the impact of this will be assessed for possible inclusion

277 Design and Development of a Database Independent Solution

2771 The request ~c deveiop a database indepenccnt scictic1 that uses neutra~ middleware for integration to systems external to the FCS will be considered (Refer to Appendix A 62)

2772 It was agreed that acceptable good design and development practices to ensure an effective maintainable system with acceptable performance characteristics will be followed but that WAYMARK INFOTECH must focus on the design and delivery of the FCS as currently contracted

278 Additional Functionality Considered

2781 Additional functions and systems listed below have been discussed for possible interfaces to andor inclusion in the FCS These items will not be included in the FCS WAYMARK INFOTECH must focus on the design and delivery of the FCS as currently contracted Should it be required that any of the additional functions or systems be considered later on it will be handled as formal changes

27811 Business Intelligence System

27812 Firearms Identification System (Extension to 3D image viewing)

27813 SAPS 13 System

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page 7 of

ConfioRntial Review of FCS Schedule

3 Revised Project Execution

31 Revised Execution Principles

311 Finalise the interface concept between the existing Firearms Register System and the new FCS and a preliminary FCS roll-out approach before end January 2006 to include the interface design in the completion of the FCS Design Baseline

312 Roll-out definition must be finalized to include in the Design Baseline freeze to ensure specific requirements that could influence System Build to support a specific roll-out approach are covered

313 In order to complete FCS System Integration at the Beta test site as scheduled the development of the FCS will start in late March 2006 in parallel with the completion of the FCS Design Baseline approval

I 314 _~4

Where required changes to the FRS need to be done by the SAPS service provider for the FRS in liaison with WAYMARK INFOTECH as a parallel activity to ensure that concurrent operation of the two systems and databases can be

~ achieved as planned

1 The 0 rigin al ~_~_~~lt~~WIIl be ~ ljle ~testingas~ctGc~e-f1ilot Operation-middottestrAllr as

~eHyptanned-i 316 Integration testing and User testing of the interfaced solution will be done at and

r~Ttely to the Numerus Beta test site JJrlirnsmiddotp~gt~_WiS extended to inchJde-thetesttngofmiddotthemiddotdafa Iiltgratlonand canCUfrentopembiRty of the FRS and FCS

31 7 ~~~~~Jppmentteeta)middotmiddotteampt eFWirenment must DeopampratKmei middottomiddotmiddotmiddotmiddotS~middotmiddottfie 111$ 11alUse This includes the existing FRS for testing the FRSFCS

interface and data transfer and access to other SAPSexternalinterfaces

318 Due to the complexity and number of interfaces the time allowed for system integration and testing has been increased to reduce risk and improve user participation This includes additional integration testing by WAYMARK INFOTECH at the Beta test site as well as SAPS Beta testing and Field testing time

319 Approval of deliverables must be achieved within the agreed seven day period Approvals (sign-off) must be final and not provisional in accordance with the acceptance procedure The formal change control process as detailed in the FCS Quality Assurance and Configuration Management Plans will be used to deal with all further requirements and changes requested after the seven day approval period

32 Critical Assumptions

321 Work on the deSign of the FRSFCS interfacing solution (revised WBS 428) will commence by 20 February 2006 to ensure that the revised schedule as depicted in Annexure A can be achieved

322 Users and facilities scheduled in advance will be available as indicated or potentially re-scheduled if required This includes the ability to test the FCS interfaces to SAPS internal and external systems The schedule does not make

1) Print Date 2006-02-10 Project Version Date 2006-02-100631 Version 50 Page 8 of 23 (1

32131144 Project Confidentlal ________~ __ Review of FCS Projet SchdliF

provision for extraordinary delays due to unavailability of facilities systems or resources

323 The review and approval period will not exceed 7 days

33 Revised FCS Project Schedule

331 The revised FCS project schedule was constructed based on the delays described in paragraphs 23 and 232 the additional requirements considered in paragraph 27 as well as the approach and critical assumptions listed above

332 The projects activities with ~f)Ofation of tha~sjnterfaGr and increased testing have been re-organised where possible and ~ng jmprpved to reduce the impact of the delays and ~dditional activities on the project end date The following must be noted

3321 The estimated net additional time required for the Interfaced FRSPOS solution is fettrmh1tls~WOfking time (2 month design and 3 month development integration and testing time) Combined with t~sect~menth~j1l~ntioned abov~ this represents ten and half months in total as summarised in the -table below

3322 Scheduling of activities in parallel resulted in 1 month (working time) of the above mentioned 15 months being offset The net delay is 105 months calendar time and 95 months working time

333 In summary the total delay in the project is as follows

Table 2 Total De

334 The major milestones are now as follows

3341 Approval to commence with the FCSFRS Interface work by 2006-02-20 3342 Core System Internal Review by 2006-02-16 (Refer revised WBS 4302) 3343 Design Baseline approved by 2006-05-26 (Refer revised WBS 4605) 3344 FCS Suppliers integration tests at the beta site are completed by 2007-01-31

(Including FRS interfaced solution) (Refer revised WBS 5404) 3345 ~~t1tlftted byen tg~k~_(lncluding FRS interfaced solution)

(Refer revised WBE b ur 3346 FCS Pilot System Operation completed by 2007-05-18 (Refer revised WBS

730)

i~Project Confidential

Version Date 2006-02-100631 Version 50 Page 9 of 23

l

31213111~4( Confidential Review of FCS Schedule

4 Cost and Schedule Comparison

41 Introduction

411 This paragraph contains the following

4111 Cost Comparison Results of the commercial implications of the factors considered in the FCS project schedule revision compared to the contract baseline

4112 Revised Project Schedule Detail view of all activities on the project schedule (Annexure A)

4113 Detail Activity Comparison between contract baseline schedule and revised schedule (Annexure 8)

42 Cost Comparison

421 The cost comparison between the current contract baseline and proposed new contract baseline is presented in the table on pages 11 to 14 following hereafter

422 Provision has also been made for a 10 Management Risk Reserve (determined by the SAPS FCS Project Director) for additional work that might be required subject to prior authorisation by the Head Information and Systems Management

423 Please note that the original contract baseline (September 2004) WBS numbers are used in this comparison table (Column B)

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page 10 of 23

32131144 Confidential Review of FCS Schedule

5 Alternative Schedule option

51 Introduction

511 The FCS Project Management Team was requested by the Steering Committee Chairman to prepare an alternative project schedule that separates deployment preparation activities from application development activities

52 Alternative Separate Development and Deployment Preparation Phases

521 Schedule

5211 The development completion and hand over date of the FCS after User Beta Test acceptance is 2007-03-22 as shown in Diagram 5 below Deployment preparation starts in parallel and ends on 2007-05-18

Diagram 5 Schedule for Separate Development and Deployment Preparation Phases

522 Cost

5221 The cost split between the Application Development Phase and the Deployment Preparation Phase is shown in Table 3 below

Print Date 2006-02-10 Project Confidential Version Date 200602-100631 Version 50 Page 15 of 23

~

3213114411 Confidential Review of FCS Schedule ~---------------~-------~-- _

6 Appendix A Additional Factors Previously Considered

61 Increased Core System Scope

611 Discussions with the SAPS Project Team in August 2005 have indicated a requirement to increase the scope of the core system beyond what was originally planned for the Core System

612 These requirements as presented requested the following additional functionality to what was planned in the scope of the core system It must be noted that these process steps already exist within the schedule but were intended to be developed in a later phase

6121 Manage information on annual report by accredited entity

6122 Update Central Firearm Register with new responsible person for juristic person

6123 Cease to carryon business

6124 Issue firearm warrant to involved party (only as applicable to competency and accreditation)

6125 Update Central Firearms Register with change in address

6126 Update Central Firearms Register with change in circumstances

6127 Update Centra F~re3rms Register with correct infc-mation

6128 Process cancellation of firearm warrant application

6129 Enquiresearch functions for Accreditation and Competency

61210 Interfaces to Internal SAPS systems as indicated in the various processes

612101 PERSAl

612102 NPIS

612103 CRIM

612104 CAS

612105 POlFIN

61211 Reports as indicated in the various processes

613 It might seem that the increase of scope of the core system does not have a direct influence over the planned handover date This is largely due to the fact that one is taking activities from one phase and moving them to another phase

Resultnt Design Phan

f

Print Date 2006-02-10 Project (~ IitVOO oe 2006-02-10 0631 Vioo 50 Pgo 17 0123 lt ~

32131144 ( Confidential Review of FCS Project Schedule

2742 Tables and standards for addresses must be correct (as for the GIS system) but contained in the FCS Data will be captured in the FCS to ensure the FCS can operate on its own

2743 The FCS will provide the address information to the GIS system GIS type reports will be generated by the GIS system The interface JAD work session(s) must still proceed to define the interface details

275 tnterfacellntegration of the FCS with Code System

2751 A central code system and standardised code sets do not yet exist For the FCS its own codes and data tables will be created The possibility to interface to a standard system (later) should not be excluded When such a system becomes available the impact of this will be assessed for possible inclusion

2752 Where other codes (ie crime vehicle gender etc) are required these should be obtained from the respective source system via interfaces This must be identified and specified during the interface JAD sessions

276 Integration with a SAPS wide Identity Management solution

2761 At this point in time Identity Management for the FCS will be built as contracted (FCS Stand Alone)

2762 When a SAPS decision on such a corporate system has been made and it becomes a requirement to use it for the FCS the impact of this will be assessed for possible inclusion

277 Design and Development of a Database Independent Solution

2771 The request ~c deveiop a database indepenccnt scictic1 that uses neutra~ middleware for integration to systems external to the FCS will be considered (Refer to Appendix A 62)

2772 It was agreed that acceptable good design and development practices to ensure an effective maintainable system with acceptable performance characteristics will be followed but that WAYMARK INFOTECH must focus on the design and delivery of the FCS as currently contracted

278 Additional Functionality Considered

2781 Additional functions and systems listed below have been discussed for possible interfaces to andor inclusion in the FCS These items will not be included in the FCS WAYMARK INFOTECH must focus on the design and delivery of the FCS as currently contracted Should it be required that any of the additional functions or systems be considered later on it will be handled as formal changes

27811 Business Intelligence System

27812 Firearms Identification System (Extension to 3D image viewing)

27813 SAPS 13 System

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page 7 of

ConfioRntial Review of FCS Schedule

3 Revised Project Execution

31 Revised Execution Principles

311 Finalise the interface concept between the existing Firearms Register System and the new FCS and a preliminary FCS roll-out approach before end January 2006 to include the interface design in the completion of the FCS Design Baseline

312 Roll-out definition must be finalized to include in the Design Baseline freeze to ensure specific requirements that could influence System Build to support a specific roll-out approach are covered

313 In order to complete FCS System Integration at the Beta test site as scheduled the development of the FCS will start in late March 2006 in parallel with the completion of the FCS Design Baseline approval

I 314 _~4

Where required changes to the FRS need to be done by the SAPS service provider for the FRS in liaison with WAYMARK INFOTECH as a parallel activity to ensure that concurrent operation of the two systems and databases can be

~ achieved as planned

1 The 0 rigin al ~_~_~~lt~~WIIl be ~ ljle ~testingas~ctGc~e-f1ilot Operation-middottestrAllr as

~eHyptanned-i 316 Integration testing and User testing of the interfaced solution will be done at and

r~Ttely to the Numerus Beta test site JJrlirnsmiddotp~gt~_WiS extended to inchJde-thetesttngofmiddotthemiddotdafa Iiltgratlonand canCUfrentopembiRty of the FRS and FCS

31 7 ~~~~~Jppmentteeta)middotmiddotteampt eFWirenment must DeopampratKmei middottomiddotmiddotmiddotmiddotS~middotmiddottfie 111$ 11alUse This includes the existing FRS for testing the FRSFCS

interface and data transfer and access to other SAPSexternalinterfaces

318 Due to the complexity and number of interfaces the time allowed for system integration and testing has been increased to reduce risk and improve user participation This includes additional integration testing by WAYMARK INFOTECH at the Beta test site as well as SAPS Beta testing and Field testing time

319 Approval of deliverables must be achieved within the agreed seven day period Approvals (sign-off) must be final and not provisional in accordance with the acceptance procedure The formal change control process as detailed in the FCS Quality Assurance and Configuration Management Plans will be used to deal with all further requirements and changes requested after the seven day approval period

32 Critical Assumptions

321 Work on the deSign of the FRSFCS interfacing solution (revised WBS 428) will commence by 20 February 2006 to ensure that the revised schedule as depicted in Annexure A can be achieved

322 Users and facilities scheduled in advance will be available as indicated or potentially re-scheduled if required This includes the ability to test the FCS interfaces to SAPS internal and external systems The schedule does not make

1) Print Date 2006-02-10 Project Version Date 2006-02-100631 Version 50 Page 8 of 23 (1

32131144 Project Confidentlal ________~ __ Review of FCS Projet SchdliF

provision for extraordinary delays due to unavailability of facilities systems or resources

323 The review and approval period will not exceed 7 days

33 Revised FCS Project Schedule

331 The revised FCS project schedule was constructed based on the delays described in paragraphs 23 and 232 the additional requirements considered in paragraph 27 as well as the approach and critical assumptions listed above

332 The projects activities with ~f)Ofation of tha~sjnterfaGr and increased testing have been re-organised where possible and ~ng jmprpved to reduce the impact of the delays and ~dditional activities on the project end date The following must be noted

3321 The estimated net additional time required for the Interfaced FRSPOS solution is fettrmh1tls~WOfking time (2 month design and 3 month development integration and testing time) Combined with t~sect~menth~j1l~ntioned abov~ this represents ten and half months in total as summarised in the -table below

3322 Scheduling of activities in parallel resulted in 1 month (working time) of the above mentioned 15 months being offset The net delay is 105 months calendar time and 95 months working time

333 In summary the total delay in the project is as follows

Table 2 Total De

334 The major milestones are now as follows

3341 Approval to commence with the FCSFRS Interface work by 2006-02-20 3342 Core System Internal Review by 2006-02-16 (Refer revised WBS 4302) 3343 Design Baseline approved by 2006-05-26 (Refer revised WBS 4605) 3344 FCS Suppliers integration tests at the beta site are completed by 2007-01-31

(Including FRS interfaced solution) (Refer revised WBS 5404) 3345 ~~t1tlftted byen tg~k~_(lncluding FRS interfaced solution)

(Refer revised WBE b ur 3346 FCS Pilot System Operation completed by 2007-05-18 (Refer revised WBS

730)

i~Project Confidential

Version Date 2006-02-100631 Version 50 Page 9 of 23

l

31213111~4( Confidential Review of FCS Schedule

4 Cost and Schedule Comparison

41 Introduction

411 This paragraph contains the following

4111 Cost Comparison Results of the commercial implications of the factors considered in the FCS project schedule revision compared to the contract baseline

4112 Revised Project Schedule Detail view of all activities on the project schedule (Annexure A)

4113 Detail Activity Comparison between contract baseline schedule and revised schedule (Annexure 8)

42 Cost Comparison

421 The cost comparison between the current contract baseline and proposed new contract baseline is presented in the table on pages 11 to 14 following hereafter

422 Provision has also been made for a 10 Management Risk Reserve (determined by the SAPS FCS Project Director) for additional work that might be required subject to prior authorisation by the Head Information and Systems Management

423 Please note that the original contract baseline (September 2004) WBS numbers are used in this comparison table (Column B)

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page 10 of 23

32131144 Confidential Review of FCS Schedule

5 Alternative Schedule option

51 Introduction

511 The FCS Project Management Team was requested by the Steering Committee Chairman to prepare an alternative project schedule that separates deployment preparation activities from application development activities

52 Alternative Separate Development and Deployment Preparation Phases

521 Schedule

5211 The development completion and hand over date of the FCS after User Beta Test acceptance is 2007-03-22 as shown in Diagram 5 below Deployment preparation starts in parallel and ends on 2007-05-18

Diagram 5 Schedule for Separate Development and Deployment Preparation Phases

522 Cost

5221 The cost split between the Application Development Phase and the Deployment Preparation Phase is shown in Table 3 below

Print Date 2006-02-10 Project Confidential Version Date 200602-100631 Version 50 Page 15 of 23

~

3213114411 Confidential Review of FCS Schedule ~---------------~-------~-- _

6 Appendix A Additional Factors Previously Considered

61 Increased Core System Scope

611 Discussions with the SAPS Project Team in August 2005 have indicated a requirement to increase the scope of the core system beyond what was originally planned for the Core System

612 These requirements as presented requested the following additional functionality to what was planned in the scope of the core system It must be noted that these process steps already exist within the schedule but were intended to be developed in a later phase

6121 Manage information on annual report by accredited entity

6122 Update Central Firearm Register with new responsible person for juristic person

6123 Cease to carryon business

6124 Issue firearm warrant to involved party (only as applicable to competency and accreditation)

6125 Update Central Firearms Register with change in address

6126 Update Central Firearms Register with change in circumstances

6127 Update Centra F~re3rms Register with correct infc-mation

6128 Process cancellation of firearm warrant application

6129 Enquiresearch functions for Accreditation and Competency

61210 Interfaces to Internal SAPS systems as indicated in the various processes

612101 PERSAl

612102 NPIS

612103 CRIM

612104 CAS

612105 POlFIN

61211 Reports as indicated in the various processes

613 It might seem that the increase of scope of the core system does not have a direct influence over the planned handover date This is largely due to the fact that one is taking activities from one phase and moving them to another phase

Resultnt Design Phan

f

Print Date 2006-02-10 Project (~ IitVOO oe 2006-02-10 0631 Vioo 50 Pgo 17 0123 lt ~

ConfioRntial Review of FCS Schedule

3 Revised Project Execution

31 Revised Execution Principles

311 Finalise the interface concept between the existing Firearms Register System and the new FCS and a preliminary FCS roll-out approach before end January 2006 to include the interface design in the completion of the FCS Design Baseline

312 Roll-out definition must be finalized to include in the Design Baseline freeze to ensure specific requirements that could influence System Build to support a specific roll-out approach are covered

313 In order to complete FCS System Integration at the Beta test site as scheduled the development of the FCS will start in late March 2006 in parallel with the completion of the FCS Design Baseline approval

I 314 _~4

Where required changes to the FRS need to be done by the SAPS service provider for the FRS in liaison with WAYMARK INFOTECH as a parallel activity to ensure that concurrent operation of the two systems and databases can be

~ achieved as planned

1 The 0 rigin al ~_~_~~lt~~WIIl be ~ ljle ~testingas~ctGc~e-f1ilot Operation-middottestrAllr as

~eHyptanned-i 316 Integration testing and User testing of the interfaced solution will be done at and

r~Ttely to the Numerus Beta test site JJrlirnsmiddotp~gt~_WiS extended to inchJde-thetesttngofmiddotthemiddotdafa Iiltgratlonand canCUfrentopembiRty of the FRS and FCS

31 7 ~~~~~Jppmentteeta)middotmiddotteampt eFWirenment must DeopampratKmei middottomiddotmiddotmiddotmiddotS~middotmiddottfie 111$ 11alUse This includes the existing FRS for testing the FRSFCS

interface and data transfer and access to other SAPSexternalinterfaces

318 Due to the complexity and number of interfaces the time allowed for system integration and testing has been increased to reduce risk and improve user participation This includes additional integration testing by WAYMARK INFOTECH at the Beta test site as well as SAPS Beta testing and Field testing time

319 Approval of deliverables must be achieved within the agreed seven day period Approvals (sign-off) must be final and not provisional in accordance with the acceptance procedure The formal change control process as detailed in the FCS Quality Assurance and Configuration Management Plans will be used to deal with all further requirements and changes requested after the seven day approval period

32 Critical Assumptions

321 Work on the deSign of the FRSFCS interfacing solution (revised WBS 428) will commence by 20 February 2006 to ensure that the revised schedule as depicted in Annexure A can be achieved

322 Users and facilities scheduled in advance will be available as indicated or potentially re-scheduled if required This includes the ability to test the FCS interfaces to SAPS internal and external systems The schedule does not make

1) Print Date 2006-02-10 Project Version Date 2006-02-100631 Version 50 Page 8 of 23 (1

32131144 Project Confidentlal ________~ __ Review of FCS Projet SchdliF

provision for extraordinary delays due to unavailability of facilities systems or resources

323 The review and approval period will not exceed 7 days

33 Revised FCS Project Schedule

331 The revised FCS project schedule was constructed based on the delays described in paragraphs 23 and 232 the additional requirements considered in paragraph 27 as well as the approach and critical assumptions listed above

332 The projects activities with ~f)Ofation of tha~sjnterfaGr and increased testing have been re-organised where possible and ~ng jmprpved to reduce the impact of the delays and ~dditional activities on the project end date The following must be noted

3321 The estimated net additional time required for the Interfaced FRSPOS solution is fettrmh1tls~WOfking time (2 month design and 3 month development integration and testing time) Combined with t~sect~menth~j1l~ntioned abov~ this represents ten and half months in total as summarised in the -table below

3322 Scheduling of activities in parallel resulted in 1 month (working time) of the above mentioned 15 months being offset The net delay is 105 months calendar time and 95 months working time

333 In summary the total delay in the project is as follows

Table 2 Total De

334 The major milestones are now as follows

3341 Approval to commence with the FCSFRS Interface work by 2006-02-20 3342 Core System Internal Review by 2006-02-16 (Refer revised WBS 4302) 3343 Design Baseline approved by 2006-05-26 (Refer revised WBS 4605) 3344 FCS Suppliers integration tests at the beta site are completed by 2007-01-31

(Including FRS interfaced solution) (Refer revised WBS 5404) 3345 ~~t1tlftted byen tg~k~_(lncluding FRS interfaced solution)

(Refer revised WBE b ur 3346 FCS Pilot System Operation completed by 2007-05-18 (Refer revised WBS

730)

i~Project Confidential

Version Date 2006-02-100631 Version 50 Page 9 of 23

l

31213111~4( Confidential Review of FCS Schedule

4 Cost and Schedule Comparison

41 Introduction

411 This paragraph contains the following

4111 Cost Comparison Results of the commercial implications of the factors considered in the FCS project schedule revision compared to the contract baseline

4112 Revised Project Schedule Detail view of all activities on the project schedule (Annexure A)

4113 Detail Activity Comparison between contract baseline schedule and revised schedule (Annexure 8)

42 Cost Comparison

421 The cost comparison between the current contract baseline and proposed new contract baseline is presented in the table on pages 11 to 14 following hereafter

422 Provision has also been made for a 10 Management Risk Reserve (determined by the SAPS FCS Project Director) for additional work that might be required subject to prior authorisation by the Head Information and Systems Management

423 Please note that the original contract baseline (September 2004) WBS numbers are used in this comparison table (Column B)

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page 10 of 23

32131144 Confidential Review of FCS Schedule

5 Alternative Schedule option

51 Introduction

511 The FCS Project Management Team was requested by the Steering Committee Chairman to prepare an alternative project schedule that separates deployment preparation activities from application development activities

52 Alternative Separate Development and Deployment Preparation Phases

521 Schedule

5211 The development completion and hand over date of the FCS after User Beta Test acceptance is 2007-03-22 as shown in Diagram 5 below Deployment preparation starts in parallel and ends on 2007-05-18

Diagram 5 Schedule for Separate Development and Deployment Preparation Phases

522 Cost

5221 The cost split between the Application Development Phase and the Deployment Preparation Phase is shown in Table 3 below

Print Date 2006-02-10 Project Confidential Version Date 200602-100631 Version 50 Page 15 of 23

~

3213114411 Confidential Review of FCS Schedule ~---------------~-------~-- _

6 Appendix A Additional Factors Previously Considered

61 Increased Core System Scope

611 Discussions with the SAPS Project Team in August 2005 have indicated a requirement to increase the scope of the core system beyond what was originally planned for the Core System

612 These requirements as presented requested the following additional functionality to what was planned in the scope of the core system It must be noted that these process steps already exist within the schedule but were intended to be developed in a later phase

6121 Manage information on annual report by accredited entity

6122 Update Central Firearm Register with new responsible person for juristic person

6123 Cease to carryon business

6124 Issue firearm warrant to involved party (only as applicable to competency and accreditation)

6125 Update Central Firearms Register with change in address

6126 Update Central Firearms Register with change in circumstances

6127 Update Centra F~re3rms Register with correct infc-mation

6128 Process cancellation of firearm warrant application

6129 Enquiresearch functions for Accreditation and Competency

61210 Interfaces to Internal SAPS systems as indicated in the various processes

612101 PERSAl

612102 NPIS

612103 CRIM

612104 CAS

612105 POlFIN

61211 Reports as indicated in the various processes

613 It might seem that the increase of scope of the core system does not have a direct influence over the planned handover date This is largely due to the fact that one is taking activities from one phase and moving them to another phase

Resultnt Design Phan

f

Print Date 2006-02-10 Project (~ IitVOO oe 2006-02-10 0631 Vioo 50 Pgo 17 0123 lt ~

32131144 Project Confidentlal ________~ __ Review of FCS Projet SchdliF

provision for extraordinary delays due to unavailability of facilities systems or resources

323 The review and approval period will not exceed 7 days

33 Revised FCS Project Schedule

331 The revised FCS project schedule was constructed based on the delays described in paragraphs 23 and 232 the additional requirements considered in paragraph 27 as well as the approach and critical assumptions listed above

332 The projects activities with ~f)Ofation of tha~sjnterfaGr and increased testing have been re-organised where possible and ~ng jmprpved to reduce the impact of the delays and ~dditional activities on the project end date The following must be noted

3321 The estimated net additional time required for the Interfaced FRSPOS solution is fettrmh1tls~WOfking time (2 month design and 3 month development integration and testing time) Combined with t~sect~menth~j1l~ntioned abov~ this represents ten and half months in total as summarised in the -table below

3322 Scheduling of activities in parallel resulted in 1 month (working time) of the above mentioned 15 months being offset The net delay is 105 months calendar time and 95 months working time

333 In summary the total delay in the project is as follows

Table 2 Total De

334 The major milestones are now as follows

3341 Approval to commence with the FCSFRS Interface work by 2006-02-20 3342 Core System Internal Review by 2006-02-16 (Refer revised WBS 4302) 3343 Design Baseline approved by 2006-05-26 (Refer revised WBS 4605) 3344 FCS Suppliers integration tests at the beta site are completed by 2007-01-31

(Including FRS interfaced solution) (Refer revised WBS 5404) 3345 ~~t1tlftted byen tg~k~_(lncluding FRS interfaced solution)

(Refer revised WBE b ur 3346 FCS Pilot System Operation completed by 2007-05-18 (Refer revised WBS

730)

i~Project Confidential

Version Date 2006-02-100631 Version 50 Page 9 of 23

l

31213111~4( Confidential Review of FCS Schedule

4 Cost and Schedule Comparison

41 Introduction

411 This paragraph contains the following

4111 Cost Comparison Results of the commercial implications of the factors considered in the FCS project schedule revision compared to the contract baseline

4112 Revised Project Schedule Detail view of all activities on the project schedule (Annexure A)

4113 Detail Activity Comparison between contract baseline schedule and revised schedule (Annexure 8)

42 Cost Comparison

421 The cost comparison between the current contract baseline and proposed new contract baseline is presented in the table on pages 11 to 14 following hereafter

422 Provision has also been made for a 10 Management Risk Reserve (determined by the SAPS FCS Project Director) for additional work that might be required subject to prior authorisation by the Head Information and Systems Management

423 Please note that the original contract baseline (September 2004) WBS numbers are used in this comparison table (Column B)

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page 10 of 23

32131144 Confidential Review of FCS Schedule

5 Alternative Schedule option

51 Introduction

511 The FCS Project Management Team was requested by the Steering Committee Chairman to prepare an alternative project schedule that separates deployment preparation activities from application development activities

52 Alternative Separate Development and Deployment Preparation Phases

521 Schedule

5211 The development completion and hand over date of the FCS after User Beta Test acceptance is 2007-03-22 as shown in Diagram 5 below Deployment preparation starts in parallel and ends on 2007-05-18

Diagram 5 Schedule for Separate Development and Deployment Preparation Phases

522 Cost

5221 The cost split between the Application Development Phase and the Deployment Preparation Phase is shown in Table 3 below

Print Date 2006-02-10 Project Confidential Version Date 200602-100631 Version 50 Page 15 of 23

~

3213114411 Confidential Review of FCS Schedule ~---------------~-------~-- _

6 Appendix A Additional Factors Previously Considered

61 Increased Core System Scope

611 Discussions with the SAPS Project Team in August 2005 have indicated a requirement to increase the scope of the core system beyond what was originally planned for the Core System

612 These requirements as presented requested the following additional functionality to what was planned in the scope of the core system It must be noted that these process steps already exist within the schedule but were intended to be developed in a later phase

6121 Manage information on annual report by accredited entity

6122 Update Central Firearm Register with new responsible person for juristic person

6123 Cease to carryon business

6124 Issue firearm warrant to involved party (only as applicable to competency and accreditation)

6125 Update Central Firearms Register with change in address

6126 Update Central Firearms Register with change in circumstances

6127 Update Centra F~re3rms Register with correct infc-mation

6128 Process cancellation of firearm warrant application

6129 Enquiresearch functions for Accreditation and Competency

61210 Interfaces to Internal SAPS systems as indicated in the various processes

612101 PERSAl

612102 NPIS

612103 CRIM

612104 CAS

612105 POlFIN

61211 Reports as indicated in the various processes

613 It might seem that the increase of scope of the core system does not have a direct influence over the planned handover date This is largely due to the fact that one is taking activities from one phase and moving them to another phase

Resultnt Design Phan

f

Print Date 2006-02-10 Project (~ IitVOO oe 2006-02-10 0631 Vioo 50 Pgo 17 0123 lt ~

31213111~4( Confidential Review of FCS Schedule

4 Cost and Schedule Comparison

41 Introduction

411 This paragraph contains the following

4111 Cost Comparison Results of the commercial implications of the factors considered in the FCS project schedule revision compared to the contract baseline

4112 Revised Project Schedule Detail view of all activities on the project schedule (Annexure A)

4113 Detail Activity Comparison between contract baseline schedule and revised schedule (Annexure 8)

42 Cost Comparison

421 The cost comparison between the current contract baseline and proposed new contract baseline is presented in the table on pages 11 to 14 following hereafter

422 Provision has also been made for a 10 Management Risk Reserve (determined by the SAPS FCS Project Director) for additional work that might be required subject to prior authorisation by the Head Information and Systems Management

423 Please note that the original contract baseline (September 2004) WBS numbers are used in this comparison table (Column B)

Print Date 2006-02-10 Project Confidential Version Date 2006-02-100631 Version 50 Page 10 of 23

32131144 Confidential Review of FCS Schedule

5 Alternative Schedule option

51 Introduction

511 The FCS Project Management Team was requested by the Steering Committee Chairman to prepare an alternative project schedule that separates deployment preparation activities from application development activities

52 Alternative Separate Development and Deployment Preparation Phases

521 Schedule

5211 The development completion and hand over date of the FCS after User Beta Test acceptance is 2007-03-22 as shown in Diagram 5 below Deployment preparation starts in parallel and ends on 2007-05-18

Diagram 5 Schedule for Separate Development and Deployment Preparation Phases

522 Cost

5221 The cost split between the Application Development Phase and the Deployment Preparation Phase is shown in Table 3 below

Print Date 2006-02-10 Project Confidential Version Date 200602-100631 Version 50 Page 15 of 23

~

3213114411 Confidential Review of FCS Schedule ~---------------~-------~-- _

6 Appendix A Additional Factors Previously Considered

61 Increased Core System Scope

611 Discussions with the SAPS Project Team in August 2005 have indicated a requirement to increase the scope of the core system beyond what was originally planned for the Core System

612 These requirements as presented requested the following additional functionality to what was planned in the scope of the core system It must be noted that these process steps already exist within the schedule but were intended to be developed in a later phase

6121 Manage information on annual report by accredited entity

6122 Update Central Firearm Register with new responsible person for juristic person

6123 Cease to carryon business

6124 Issue firearm warrant to involved party (only as applicable to competency and accreditation)

6125 Update Central Firearms Register with change in address

6126 Update Central Firearms Register with change in circumstances

6127 Update Centra F~re3rms Register with correct infc-mation

6128 Process cancellation of firearm warrant application

6129 Enquiresearch functions for Accreditation and Competency

61210 Interfaces to Internal SAPS systems as indicated in the various processes

612101 PERSAl

612102 NPIS

612103 CRIM

612104 CAS

612105 POlFIN

61211 Reports as indicated in the various processes

613 It might seem that the increase of scope of the core system does not have a direct influence over the planned handover date This is largely due to the fact that one is taking activities from one phase and moving them to another phase

Resultnt Design Phan

f

Print Date 2006-02-10 Project (~ IitVOO oe 2006-02-10 0631 Vioo 50 Pgo 17 0123 lt ~

32131144 Confidential Review of FCS Schedule

5 Alternative Schedule option

51 Introduction

511 The FCS Project Management Team was requested by the Steering Committee Chairman to prepare an alternative project schedule that separates deployment preparation activities from application development activities

52 Alternative Separate Development and Deployment Preparation Phases

521 Schedule

5211 The development completion and hand over date of the FCS after User Beta Test acceptance is 2007-03-22 as shown in Diagram 5 below Deployment preparation starts in parallel and ends on 2007-05-18

Diagram 5 Schedule for Separate Development and Deployment Preparation Phases

522 Cost

5221 The cost split between the Application Development Phase and the Deployment Preparation Phase is shown in Table 3 below

Print Date 2006-02-10 Project Confidential Version Date 200602-100631 Version 50 Page 15 of 23

~

3213114411 Confidential Review of FCS Schedule ~---------------~-------~-- _

6 Appendix A Additional Factors Previously Considered

61 Increased Core System Scope

611 Discussions with the SAPS Project Team in August 2005 have indicated a requirement to increase the scope of the core system beyond what was originally planned for the Core System

612 These requirements as presented requested the following additional functionality to what was planned in the scope of the core system It must be noted that these process steps already exist within the schedule but were intended to be developed in a later phase

6121 Manage information on annual report by accredited entity

6122 Update Central Firearm Register with new responsible person for juristic person

6123 Cease to carryon business

6124 Issue firearm warrant to involved party (only as applicable to competency and accreditation)

6125 Update Central Firearms Register with change in address

6126 Update Central Firearms Register with change in circumstances

6127 Update Centra F~re3rms Register with correct infc-mation

6128 Process cancellation of firearm warrant application

6129 Enquiresearch functions for Accreditation and Competency

61210 Interfaces to Internal SAPS systems as indicated in the various processes

612101 PERSAl

612102 NPIS

612103 CRIM

612104 CAS

612105 POlFIN

61211 Reports as indicated in the various processes

613 It might seem that the increase of scope of the core system does not have a direct influence over the planned handover date This is largely due to the fact that one is taking activities from one phase and moving them to another phase

Resultnt Design Phan

f

Print Date 2006-02-10 Project (~ IitVOO oe 2006-02-10 0631 Vioo 50 Pgo 17 0123 lt ~

3213114411 Confidential Review of FCS Schedule ~---------------~-------~-- _

6 Appendix A Additional Factors Previously Considered

61 Increased Core System Scope

611 Discussions with the SAPS Project Team in August 2005 have indicated a requirement to increase the scope of the core system beyond what was originally planned for the Core System

612 These requirements as presented requested the following additional functionality to what was planned in the scope of the core system It must be noted that these process steps already exist within the schedule but were intended to be developed in a later phase

6121 Manage information on annual report by accredited entity

6122 Update Central Firearm Register with new responsible person for juristic person

6123 Cease to carryon business

6124 Issue firearm warrant to involved party (only as applicable to competency and accreditation)

6125 Update Central Firearms Register with change in address

6126 Update Central Firearms Register with change in circumstances

6127 Update Centra F~re3rms Register with correct infc-mation

6128 Process cancellation of firearm warrant application

6129 Enquiresearch functions for Accreditation and Competency

61210 Interfaces to Internal SAPS systems as indicated in the various processes

612101 PERSAl

612102 NPIS

612103 CRIM

612104 CAS

612105 POlFIN

61211 Reports as indicated in the various processes

613 It might seem that the increase of scope of the core system does not have a direct influence over the planned handover date This is largely due to the fact that one is taking activities from one phase and moving them to another phase

Resultnt Design Phan

f

Print Date 2006-02-10 Project (~ IitVOO oe 2006-02-10 0631 Vioo 50 Pgo 17 0123 lt ~

32131144 __ ~e-~~_of FCS Project Schectule

614 However there is a direct influence in that duplication of testing may occur resulting in an increase of effort In addition there may not necessarily be resources available to execute the work as a result of other commitments already scheduled within the earlier scheduled design phase In addition it must be noted that the removal of components from the development phase may not necessarily result in a reduction in phase time as it will depend on whether or not there are corresponding parallel activities

_---------- shy Total Time -------------

Resultant 006ign PMaae

615 During discussion with the SAPS Project Team it was agreed that it is not practical to include the internal interfaces within the scope of the core system as a result of the time it will still take to finalise the Interface Control Documentation

616 It must be noted that the extent of work required is not only limited to the building of the applicable functionality associated with the indicated process steps but also implies that some of the general components that were not planned for this phase will now have to be available as a part of the core system These components include

0161 Electronic receipt of documents

6162 System Notifications

6163 Enquiry and Search Function

6164 Specialised Printing

6165 System Notifications

6166 System Audits

6167 The implication of the scope changes are summarized in the following table

Activity Duration (work days)

CQMpO~ot middot$l~m tliPtlfiqtWJIlSc- -shy

included in

i Build General Component - System Audits

FCS Process Step - Ma nage information on a nnua I report entity

FCS Process Step - Update Central Firearm Register person for juristic person

FCS Process Step - Cease to carry 011 business

10 days (Was included in Returns and Deactivation)

7 days

----~---------------~-~------- --------Pnnt Date 2006-02~10 VerSion Date 2006-02~10 0631

Project Confidential Version 50 Page 18 of 23

HZ (tA~

32131144 Confidential

Activity

Step - Update Central Firearms Register with

Process cancellation of firearm warrant

to the competency and accreditation process

Review of FCS Schedule

617 The actual schedule impact of the above can only be established during the process of revising the detailed work schedules as the duration is inter alia dependent on resource availability Initial estimates indicate a 4 month increase in the Core System timescale

618 For this reason it was proposed that the Design Baseline be completed as soon as possible independently of the Core System development

619 After this implication was reviewed this requirement was withdrawn and it was agreed to keep to the scope and app each as contracted with the exclusion of the Declaration of Unfitness process The latter will be replaced with Specialized Printing which will require that the FCS must be able to print to the Eltron 720 Zebra printer

6110 It was also agreed that the Core System as indicated in the contract will be built to keep as close as possible to the original schedule

62 Design and Development Influence

621 The primary influence is the request to develop a database independent solution that uses neutral middleware

622 WAYMARK INFOTECH will apply generally acceptable good design and development practices to ensure an effective maintainable system with acceptable performance characteristics

623 It must however be kept in mind that the proposed and contracted solution is an Oracle technology based solution using Oracle Database Portal Forms Security and Identity Management In order for WAYMARK INFOTECH to deliver the contracted solution on time and on acceptable performance limits there is no alternative than to use Oracle store procedures and triggers and standard Oracle functions The current schedule and budget do not allow for redevelopment of standard Oracle functionality in a middleware or other PlatformDatabase independent solution

624 If requested WAYMARK INFOTECH will be willing to investigate how to alter the software design to allow for future migration to alternative database

middot0~ -----~ ----c~ ~~

Project Confidential - shyVersion Date 2006-02-10 0631 Version 50 Page 19 of 23 (

S jO jno t pound0 wnpueppV SJi

(Iepalew )0 illS) 8 aJnxauuv

32131144 Confidential Review of FCS Schedule

Annexure A Revised Project Schedule

11 Print Date 2006-02-10 Project Confidential Version Date 2006-02-10 0631 Version 50 Page 22 of 23

Projecl Confidenlial FCSProJecISchedule-Revlslon2006003fda

2iillL1oru-__l20~as~1l1J

2004middot10middot04 200S-03-04 100 days [[ HJ i 642days 0 Vii 11 ~ v I~~~ -l__l n oJL~ J-Jv ~i--1 J_~

2001 Contract Official Signing 2004-10-04 2004-10-04

2002 Project Staffing 2004-10-26 2005-01-10

2003 Accommodation Allocation 2004-10-05 2004-12-10

2004 Finalize and agree to Office Layout 2005-01-10 2005-01-14

210 Office Infrastructure Acquisition 2004middot11-02 2005middot02-28

2101 Furniture acquisition 2004-11-02 2005-01middot03

2102 Telephone line acquisition 2004-11-02 2005l2-28

220 Hardware Acquisition 2004middot11middot02 200S-03-04

220 Office Hardware AcquiSition 2004-11-02 2005middot03-04

2202 Development Hardware AcqUlsition 2004middot11-02 2005l3middot04

230 Software Acquisition 2004middot11-02 20DS-OJ-04

2301 Office Software Acquisition 2004-11-02 2005-03-04

2302 Development Software Acquisition 2004middot11-02 2005-03-04

240 Data Line AcqUisition 2004middot11-02 2005-03-04

2401 Agree to dala line specifications 2004-11-02 2004-11-08

2402 Obtain required authorisations 2004-12-13 2005-03middot04

300 Project Initiation Phase 2005middot03-07 2005middot10middot17

310 Project Team Organisation 2005-03-07 200S-03middot16

3101 Conduct Orientation Work-shop(s) 2005-03-07 2005-03-10

l102 Defina and agree on OrganisatiOnal Siructure (ref ES 020 CDM) 200Sl3middot14 2005-03middot15 3103 Define and agree on work methods amp Procedures 2005l3-14 2005-03-15

3104 Identify and designate SAPS PrOjeCI team members 2005-03-16 2005-03-16

320 Project Management System 2005-03middot17 2005-05-04

321 Establish Project Governance Structures 200S-03-17 2005-03middot30

3211 Establish Project Steering Committee 2005l3-17 2005-03-23

3212 Establish FCS Project Management Team 2005l3-17 2005-03middot23

3213 Davelop and agree to Project Charier 2005l3-17 2005-03-30

322 Risk amp Issue Management System 2005-03middot17

3221 Develop the risk management plan 2005-03-17

3222 Approve riSK management pian 2005-04-28 2005-04-28 1 day

3223 Define and establish nsk and issue recording syslem 2OOSl4-29 200S-05-04 4 days

323 Time Recording System 2005l3middot17 200S-03middot23 5 days

3231 Define time recording methOd 2005-03-17 2005-03-17 1 day

3232 Establish time recording system 2005middot03-18 2005-0323 4 days

3233 Approved time recording system 2005-03-23 2005-03middot23 odays

324 Financial Management System 2005-03middot17 200Smiddot04-01 12 days

3241 Define Procurement Procedures 2005middot03-17 2005-03-22 4 days

3242 Define Financial Reporilng Procedures 2005-03-17 2005-03-23 5 days

-3243 Define Invoicing Procedures 2005-03-24 2005l3-25 2 days

3244 Establish Financial Recording and Reporting System 2005-03-24 2005l3-29 4 days

3245 Define and agree to project budget 2005-03-30 200Sl3-30 1 day

3246 Define and agree to Paymenl Schedule 2COSl3-31 2005-04middot01 2 days

3247 Approved Financial System 200S-04l1 2005-04-01 odays

325 Project Staffing 200S-03-17 325 Establish Project Staffing Plan 2005-03-17

49 days

5 days

7S days

35 days

75 days

79 days

79 days

79 days

79 days

79 days

79 days

79 days

5 days

50 days

158 days

8 days

4 days

2 days

2 days

1 day

35 days

10 days

5 days

5 days

10 days

35 days

30 days

ti I

13-23

bull

middot middot middot middot middot middot

middotmiddot

middotmiddot middot middot middot middot I

middot middot middot middot middot middotImiddotI

middot I

of25

------

Projecl Management System Operational 2005-05-04 2005-05-04

330 Quality Management System 2005-03middot14 2005-04-01

3301 Deline and agree 10 QA standards 2005-03middot14 200503middot16 3 days

3302 Define Quality Management Plan 2005-03-17 2005middot03-30 10 days

3303 Define Communication Plan 2005-03middot 17 2005-03-30 10 days

3305 Approve Quality Management System 2005-03middot31 2005-04middot01 2 days

3304 Define test Plan 2005-03middot 14 2005-03-29 12 dayS

3306 Establish Compuware QACenter Repository 2005-03middot 14 2005-03middot 18 5 days

3307 Train Personnel on Quality Management System 2005-03-21 2005-03-25 5 days

3308 Implement QMS Procedures and Stds 2005-03-28 2005-04-01 5 days

3309 QA System Operational 2005-04-01 2005-04 -0 1 odays

340 Configurallon Management System 200~-O3-14 200~-O4-O4 16 days 3401 Define and agree to documentation standards 2005-03-14 2005middot03middot18 5 days

3402 Define Configuration Management System 2005-03-21 2005middot04middot01 10 days

3403 Define Change control procedure 2005-03middot14 2005-04-01 15 day

3404 Establish Asset Control Procedures and Metliods 2005-03-14 2005-03-18 5 days

3405 Approve Config Management System 2005-04-04 2005-04-04 day

3406 Estabsh Project Documentum Repository 2005-03-21 2005-03middot24 4 days

3407 Transfer SAPS Project related Statutory Documents 2005-03-25 2005middot03middot31 5 days

3408 Transfer Busineoss Analysis Baseline 2005-03-25 2005-03-31 5 day

3409 Train Project Personnel on the use of Documentum 2005-04-01 2005-04-04 2 days

34010 Configuration Management System Operational 2005-04-04 2005-04-04 oday

350 ProjectOffIce Set-up 200~-O3-14 2005-05middot20 50 days

351 Data Line Setup 2005-03middot14 2005-04-01 15 days

3511 Implement amp tesl data lines 2005-03-14 2005-04-01 1S days

352 Environment Conflg 2005-03middot14 2005middot04-1~ 25 days

3521 Configure Office IT Environment 2005-03-14 2005-03-25 10 days

3522 Configure Development IT Environment 2005-03-28 2005-04middot15 15 days

353 Setup ProtOtype System 2005-04middot18 200~middot05middot20 25 days 3531 Configure software 2005-04middot18 2005middot05-13 20 days

3532 Test configuration 2005-05-16 2005-05-20 5 days

360 Finalise and Approve Functional Baseline 2005-03middot11 200~-O8middot22 15 days

361 Compile System Design Framewor1lt 2005-03-11 200~-O7-O8 85 dayS

3611 Compile Functional Data Sheets 2005-03-11 2005-05-04 39 days

3612 Develop and Compile SDF document 2005-05middot11 2005-07-08 42 days 36121 Define Documentation Standards 2005-05-11 2005middot05-24 10 days

36122 Define System Architecture 2005middot05middot25 2005-05middot31 5 days

36123 Define Security Framework 2005middot06middot01 2005-06-14 5 days

36124 Define User Interface Concep 2005middot05middot25 2005-06-14 15 days

30125 Define conceptual data model 2005-05-25 2005-06-14 15 days

36126 Define System Interfacing Concepl 2005middot06-08 2005-06middot1 5 days

36127 Produce SDF document 2005-06middot15

3613 Agree to scope of wor1lt defined in Functional DeSign Specifil 2005-0414

36131 UML Software Acquisition and Training 2005middot04middot14

36132 BUild Use Cases 2005-05-04

36133 Develop user profiles 2005-05-18

2 uf 25 I

32131144 Confidential

Activity

Step - Update Central Firearms Register with

Process cancellation of firearm warrant

to the competency and accreditation process

Review of FCS Schedule

617 The actual schedule impact of the above can only be established during the process of revising the detailed work schedules as the duration is inter alia dependent on resource availability Initial estimates indicate a 4 month increase in the Core System timescale

618 For this reason it was proposed that the Design Baseline be completed as soon as possible independently of the Core System development

619 After this implication was reviewed this requirement was withdrawn and it was agreed to keep to the scope and app each as contracted with the exclusion of the Declaration of Unfitness process The latter will be replaced with Specialized Printing which will require that the FCS must be able to print to the Eltron 720 Zebra printer

6110 It was also agreed that the Core System as indicated in the contract will be built to keep as close as possible to the original schedule

62 Design and Development Influence

621 The primary influence is the request to develop a database independent solution that uses neutral middleware

622 WAYMARK INFOTECH will apply generally acceptable good design and development practices to ensure an effective maintainable system with acceptable performance characteristics

623 It must however be kept in mind that the proposed and contracted solution is an Oracle technology based solution using Oracle Database Portal Forms Security and Identity Management In order for WAYMARK INFOTECH to deliver the contracted solution on time and on acceptable performance limits there is no alternative than to use Oracle store procedures and triggers and standard Oracle functions The current schedule and budget do not allow for redevelopment of standard Oracle functionality in a middleware or other PlatformDatabase independent solution

624 If requested WAYMARK INFOTECH will be willing to investigate how to alter the software design to allow for future migration to alternative database

middot0~ -----~ ----c~ ~~

Project Confidential - shyVersion Date 2006-02-10 0631 Version 50 Page 19 of 23 (

S jO jno t pound0 wnpueppV SJi

(Iepalew )0 illS) 8 aJnxauuv

32131144 Confidential Review of FCS Schedule

Annexure A Revised Project Schedule

11 Print Date 2006-02-10 Project Confidential Version Date 2006-02-10 0631 Version 50 Page 22 of 23

Projecl Confidenlial FCSProJecISchedule-Revlslon2006003fda

2iillL1oru-__l20~as~1l1J

2004middot10middot04 200S-03-04 100 days [[ HJ i 642days 0 Vii 11 ~ v I~~~ -l__l n oJL~ J-Jv ~i--1 J_~

2001 Contract Official Signing 2004-10-04 2004-10-04

2002 Project Staffing 2004-10-26 2005-01-10

2003 Accommodation Allocation 2004-10-05 2004-12-10

2004 Finalize and agree to Office Layout 2005-01-10 2005-01-14

210 Office Infrastructure Acquisition 2004middot11-02 2005middot02-28

2101 Furniture acquisition 2004-11-02 2005-01middot03

2102 Telephone line acquisition 2004-11-02 2005l2-28

220 Hardware Acquisition 2004middot11middot02 200S-03-04

220 Office Hardware AcquiSition 2004-11-02 2005middot03-04

2202 Development Hardware AcqUlsition 2004middot11-02 2005l3middot04

230 Software Acquisition 2004middot11-02 20DS-OJ-04

2301 Office Software Acquisition 2004-11-02 2005-03-04

2302 Development Software Acquisition 2004middot11-02 2005-03-04

240 Data Line AcqUisition 2004middot11-02 2005-03-04

2401 Agree to dala line specifications 2004-11-02 2004-11-08

2402 Obtain required authorisations 2004-12-13 2005-03middot04

300 Project Initiation Phase 2005middot03-07 2005middot10middot17

310 Project Team Organisation 2005-03-07 200S-03middot16

3101 Conduct Orientation Work-shop(s) 2005-03-07 2005-03-10

l102 Defina and agree on OrganisatiOnal Siructure (ref ES 020 CDM) 200Sl3middot14 2005-03middot15 3103 Define and agree on work methods amp Procedures 2005l3-14 2005-03-15

3104 Identify and designate SAPS PrOjeCI team members 2005-03-16 2005-03-16

320 Project Management System 2005-03middot17 2005-05-04

321 Establish Project Governance Structures 200S-03-17 2005-03middot30

3211 Establish Project Steering Committee 2005l3-17 2005-03-23

3212 Establish FCS Project Management Team 2005l3-17 2005-03middot23

3213 Davelop and agree to Project Charier 2005l3-17 2005-03-30

322 Risk amp Issue Management System 2005-03middot17

3221 Develop the risk management plan 2005-03-17

3222 Approve riSK management pian 2005-04-28 2005-04-28 1 day

3223 Define and establish nsk and issue recording syslem 2OOSl4-29 200S-05-04 4 days

323 Time Recording System 2005l3middot17 200S-03middot23 5 days

3231 Define time recording methOd 2005-03-17 2005-03-17 1 day

3232 Establish time recording system 2005middot03-18 2005-0323 4 days

3233 Approved time recording system 2005-03-23 2005-03middot23 odays

324 Financial Management System 2005-03middot17 200Smiddot04-01 12 days

3241 Define Procurement Procedures 2005middot03-17 2005-03-22 4 days

3242 Define Financial Reporilng Procedures 2005-03-17 2005-03-23 5 days

-3243 Define Invoicing Procedures 2005-03-24 2005l3-25 2 days

3244 Establish Financial Recording and Reporting System 2005-03-24 2005l3-29 4 days

3245 Define and agree to project budget 2005-03-30 200Sl3-30 1 day

3246 Define and agree to Paymenl Schedule 2COSl3-31 2005-04middot01 2 days

3247 Approved Financial System 200S-04l1 2005-04-01 odays

325 Project Staffing 200S-03-17 325 Establish Project Staffing Plan 2005-03-17

49 days

5 days

7S days

35 days

75 days

79 days

79 days

79 days

79 days

79 days

79 days

79 days

5 days

50 days

158 days

8 days

4 days

2 days

2 days

1 day

35 days

10 days

5 days

5 days

10 days

35 days

30 days

ti I

13-23

bull

middot middot middot middot middot middot

middotmiddot

middotmiddot middot middot middot middot I

middot middot middot middot middot middotImiddotI

middot I

of25

------

Projecl Management System Operational 2005-05-04 2005-05-04

330 Quality Management System 2005-03middot14 2005-04-01

3301 Deline and agree 10 QA standards 2005-03middot14 200503middot16 3 days

3302 Define Quality Management Plan 2005-03-17 2005middot03-30 10 days

3303 Define Communication Plan 2005-03middot 17 2005-03-30 10 days

3305 Approve Quality Management System 2005-03middot31 2005-04middot01 2 days

3304 Define test Plan 2005-03middot 14 2005-03-29 12 dayS

3306 Establish Compuware QACenter Repository 2005-03middot 14 2005-03middot 18 5 days

3307 Train Personnel on Quality Management System 2005-03-21 2005-03-25 5 days

3308 Implement QMS Procedures and Stds 2005-03-28 2005-04-01 5 days

3309 QA System Operational 2005-04-01 2005-04 -0 1 odays

340 Configurallon Management System 200~-O3-14 200~-O4-O4 16 days 3401 Define and agree to documentation standards 2005-03-14 2005middot03middot18 5 days

3402 Define Configuration Management System 2005-03-21 2005middot04middot01 10 days

3403 Define Change control procedure 2005-03middot14 2005-04-01 15 day

3404 Establish Asset Control Procedures and Metliods 2005-03-14 2005-03-18 5 days

3405 Approve Config Management System 2005-04-04 2005-04-04 day

3406 Estabsh Project Documentum Repository 2005-03-21 2005-03middot24 4 days

3407 Transfer SAPS Project related Statutory Documents 2005-03-25 2005middot03middot31 5 days

3408 Transfer Busineoss Analysis Baseline 2005-03-25 2005-03-31 5 day

3409 Train Project Personnel on the use of Documentum 2005-04-01 2005-04-04 2 days

34010 Configuration Management System Operational 2005-04-04 2005-04-04 oday

350 ProjectOffIce Set-up 200~-O3-14 2005-05middot20 50 days

351 Data Line Setup 2005-03middot14 2005-04-01 15 days

3511 Implement amp tesl data lines 2005-03-14 2005-04-01 1S days

352 Environment Conflg 2005-03middot14 2005middot04-1~ 25 days

3521 Configure Office IT Environment 2005-03-14 2005-03-25 10 days

3522 Configure Development IT Environment 2005-03-28 2005-04middot15 15 days

353 Setup ProtOtype System 2005-04middot18 200~middot05middot20 25 days 3531 Configure software 2005-04middot18 2005middot05-13 20 days

3532 Test configuration 2005-05-16 2005-05-20 5 days

360 Finalise and Approve Functional Baseline 2005-03middot11 200~-O8middot22 15 days

361 Compile System Design Framewor1lt 2005-03-11 200~-O7-O8 85 dayS

3611 Compile Functional Data Sheets 2005-03-11 2005-05-04 39 days

3612 Develop and Compile SDF document 2005-05middot11 2005-07-08 42 days 36121 Define Documentation Standards 2005-05-11 2005middot05-24 10 days

36122 Define System Architecture 2005middot05middot25 2005-05middot31 5 days

36123 Define Security Framework 2005middot06middot01 2005-06-14 5 days

36124 Define User Interface Concep 2005middot05middot25 2005-06-14 15 days

30125 Define conceptual data model 2005-05-25 2005-06-14 15 days

36126 Define System Interfacing Concepl 2005middot06-08 2005-06middot1 5 days

36127 Produce SDF document 2005-06middot15

3613 Agree to scope of wor1lt defined in Functional DeSign Specifil 2005-0414

36131 UML Software Acquisition and Training 2005middot04middot14

36132 BUild Use Cases 2005-05-04

36133 Develop user profiles 2005-05-18

2 uf 25 I

S jO jno t pound0 wnpueppV SJi

(Iepalew )0 illS) 8 aJnxauuv

32131144 Confidential Review of FCS Schedule

Annexure A Revised Project Schedule

11 Print Date 2006-02-10 Project Confidential Version Date 2006-02-10 0631 Version 50 Page 22 of 23

Projecl Confidenlial FCSProJecISchedule-Revlslon2006003fda

2iillL1oru-__l20~as~1l1J

2004middot10middot04 200S-03-04 100 days [[ HJ i 642days 0 Vii 11 ~ v I~~~ -l__l n oJL~ J-Jv ~i--1 J_~

2001 Contract Official Signing 2004-10-04 2004-10-04

2002 Project Staffing 2004-10-26 2005-01-10

2003 Accommodation Allocation 2004-10-05 2004-12-10

2004 Finalize and agree to Office Layout 2005-01-10 2005-01-14

210 Office Infrastructure Acquisition 2004middot11-02 2005middot02-28

2101 Furniture acquisition 2004-11-02 2005-01middot03

2102 Telephone line acquisition 2004-11-02 2005l2-28

220 Hardware Acquisition 2004middot11middot02 200S-03-04

220 Office Hardware AcquiSition 2004-11-02 2005middot03-04

2202 Development Hardware AcqUlsition 2004middot11-02 2005l3middot04

230 Software Acquisition 2004middot11-02 20DS-OJ-04

2301 Office Software Acquisition 2004-11-02 2005-03-04

2302 Development Software Acquisition 2004middot11-02 2005-03-04

240 Data Line AcqUisition 2004middot11-02 2005-03-04

2401 Agree to dala line specifications 2004-11-02 2004-11-08

2402 Obtain required authorisations 2004-12-13 2005-03middot04

300 Project Initiation Phase 2005middot03-07 2005middot10middot17

310 Project Team Organisation 2005-03-07 200S-03middot16

3101 Conduct Orientation Work-shop(s) 2005-03-07 2005-03-10

l102 Defina and agree on OrganisatiOnal Siructure (ref ES 020 CDM) 200Sl3middot14 2005-03middot15 3103 Define and agree on work methods amp Procedures 2005l3-14 2005-03-15

3104 Identify and designate SAPS PrOjeCI team members 2005-03-16 2005-03-16

320 Project Management System 2005-03middot17 2005-05-04

321 Establish Project Governance Structures 200S-03-17 2005-03middot30

3211 Establish Project Steering Committee 2005l3-17 2005-03-23

3212 Establish FCS Project Management Team 2005l3-17 2005-03middot23

3213 Davelop and agree to Project Charier 2005l3-17 2005-03-30

322 Risk amp Issue Management System 2005-03middot17

3221 Develop the risk management plan 2005-03-17

3222 Approve riSK management pian 2005-04-28 2005-04-28 1 day

3223 Define and establish nsk and issue recording syslem 2OOSl4-29 200S-05-04 4 days

323 Time Recording System 2005l3middot17 200S-03middot23 5 days

3231 Define time recording methOd 2005-03-17 2005-03-17 1 day

3232 Establish time recording system 2005middot03-18 2005-0323 4 days

3233 Approved time recording system 2005-03-23 2005-03middot23 odays

324 Financial Management System 2005-03middot17 200Smiddot04-01 12 days

3241 Define Procurement Procedures 2005middot03-17 2005-03-22 4 days

3242 Define Financial Reporilng Procedures 2005-03-17 2005-03-23 5 days

-3243 Define Invoicing Procedures 2005-03-24 2005l3-25 2 days

3244 Establish Financial Recording and Reporting System 2005-03-24 2005l3-29 4 days

3245 Define and agree to project budget 2005-03-30 200Sl3-30 1 day

3246 Define and agree to Paymenl Schedule 2COSl3-31 2005-04middot01 2 days

3247 Approved Financial System 200S-04l1 2005-04-01 odays

325 Project Staffing 200S-03-17 325 Establish Project Staffing Plan 2005-03-17

49 days

5 days

7S days

35 days

75 days

79 days

79 days

79 days

79 days

79 days

79 days

79 days

5 days

50 days

158 days

8 days

4 days

2 days

2 days

1 day

35 days

10 days

5 days

5 days

10 days

35 days

30 days

ti I

13-23

bull

middot middot middot middot middot middot

middotmiddot

middotmiddot middot middot middot middot I

middot middot middot middot middot middotImiddotI

middot I

of25

------

Projecl Management System Operational 2005-05-04 2005-05-04

330 Quality Management System 2005-03middot14 2005-04-01

3301 Deline and agree 10 QA standards 2005-03middot14 200503middot16 3 days

3302 Define Quality Management Plan 2005-03-17 2005middot03-30 10 days

3303 Define Communication Plan 2005-03middot 17 2005-03-30 10 days

3305 Approve Quality Management System 2005-03middot31 2005-04middot01 2 days

3304 Define test Plan 2005-03middot 14 2005-03-29 12 dayS

3306 Establish Compuware QACenter Repository 2005-03middot 14 2005-03middot 18 5 days

3307 Train Personnel on Quality Management System 2005-03-21 2005-03-25 5 days

3308 Implement QMS Procedures and Stds 2005-03-28 2005-04-01 5 days

3309 QA System Operational 2005-04-01 2005-04 -0 1 odays

340 Configurallon Management System 200~-O3-14 200~-O4-O4 16 days 3401 Define and agree to documentation standards 2005-03-14 2005middot03middot18 5 days

3402 Define Configuration Management System 2005-03-21 2005middot04middot01 10 days

3403 Define Change control procedure 2005-03middot14 2005-04-01 15 day

3404 Establish Asset Control Procedures and Metliods 2005-03-14 2005-03-18 5 days

3405 Approve Config Management System 2005-04-04 2005-04-04 day

3406 Estabsh Project Documentum Repository 2005-03-21 2005-03middot24 4 days

3407 Transfer SAPS Project related Statutory Documents 2005-03-25 2005middot03middot31 5 days

3408 Transfer Busineoss Analysis Baseline 2005-03-25 2005-03-31 5 day

3409 Train Project Personnel on the use of Documentum 2005-04-01 2005-04-04 2 days

34010 Configuration Management System Operational 2005-04-04 2005-04-04 oday

350 ProjectOffIce Set-up 200~-O3-14 2005-05middot20 50 days

351 Data Line Setup 2005-03middot14 2005-04-01 15 days

3511 Implement amp tesl data lines 2005-03-14 2005-04-01 1S days

352 Environment Conflg 2005-03middot14 2005middot04-1~ 25 days

3521 Configure Office IT Environment 2005-03-14 2005-03-25 10 days

3522 Configure Development IT Environment 2005-03-28 2005-04middot15 15 days

353 Setup ProtOtype System 2005-04middot18 200~middot05middot20 25 days 3531 Configure software 2005-04middot18 2005middot05-13 20 days

3532 Test configuration 2005-05-16 2005-05-20 5 days

360 Finalise and Approve Functional Baseline 2005-03middot11 200~-O8middot22 15 days

361 Compile System Design Framewor1lt 2005-03-11 200~-O7-O8 85 dayS

3611 Compile Functional Data Sheets 2005-03-11 2005-05-04 39 days

3612 Develop and Compile SDF document 2005-05middot11 2005-07-08 42 days 36121 Define Documentation Standards 2005-05-11 2005middot05-24 10 days

36122 Define System Architecture 2005middot05middot25 2005-05middot31 5 days

36123 Define Security Framework 2005middot06middot01 2005-06-14 5 days

36124 Define User Interface Concep 2005middot05middot25 2005-06-14 15 days

30125 Define conceptual data model 2005-05-25 2005-06-14 15 days

36126 Define System Interfacing Concepl 2005middot06-08 2005-06middot1 5 days

36127 Produce SDF document 2005-06middot15

3613 Agree to scope of wor1lt defined in Functional DeSign Specifil 2005-0414

36131 UML Software Acquisition and Training 2005middot04middot14

36132 BUild Use Cases 2005-05-04

36133 Develop user profiles 2005-05-18

2 uf 25 I

32131144 Confidential Review of FCS Schedule

Annexure A Revised Project Schedule

11 Print Date 2006-02-10 Project Confidential Version Date 2006-02-10 0631 Version 50 Page 22 of 23

Projecl Confidenlial FCSProJecISchedule-Revlslon2006003fda

2iillL1oru-__l20~as~1l1J

2004middot10middot04 200S-03-04 100 days [[ HJ i 642days 0 Vii 11 ~ v I~~~ -l__l n oJL~ J-Jv ~i--1 J_~

2001 Contract Official Signing 2004-10-04 2004-10-04

2002 Project Staffing 2004-10-26 2005-01-10

2003 Accommodation Allocation 2004-10-05 2004-12-10

2004 Finalize and agree to Office Layout 2005-01-10 2005-01-14

210 Office Infrastructure Acquisition 2004middot11-02 2005middot02-28

2101 Furniture acquisition 2004-11-02 2005-01middot03

2102 Telephone line acquisition 2004-11-02 2005l2-28

220 Hardware Acquisition 2004middot11middot02 200S-03-04

220 Office Hardware AcquiSition 2004-11-02 2005middot03-04

2202 Development Hardware AcqUlsition 2004middot11-02 2005l3middot04

230 Software Acquisition 2004middot11-02 20DS-OJ-04

2301 Office Software Acquisition 2004-11-02 2005-03-04

2302 Development Software Acquisition 2004middot11-02 2005-03-04

240 Data Line AcqUisition 2004middot11-02 2005-03-04

2401 Agree to dala line specifications 2004-11-02 2004-11-08

2402 Obtain required authorisations 2004-12-13 2005-03middot04

300 Project Initiation Phase 2005middot03-07 2005middot10middot17

310 Project Team Organisation 2005-03-07 200S-03middot16

3101 Conduct Orientation Work-shop(s) 2005-03-07 2005-03-10

l102 Defina and agree on OrganisatiOnal Siructure (ref ES 020 CDM) 200Sl3middot14 2005-03middot15 3103 Define and agree on work methods amp Procedures 2005l3-14 2005-03-15

3104 Identify and designate SAPS PrOjeCI team members 2005-03-16 2005-03-16

320 Project Management System 2005-03middot17 2005-05-04

321 Establish Project Governance Structures 200S-03-17 2005-03middot30

3211 Establish Project Steering Committee 2005l3-17 2005-03-23

3212 Establish FCS Project Management Team 2005l3-17 2005-03middot23

3213 Davelop and agree to Project Charier 2005l3-17 2005-03-30

322 Risk amp Issue Management System 2005-03middot17

3221 Develop the risk management plan 2005-03-17

3222 Approve riSK management pian 2005-04-28 2005-04-28 1 day

3223 Define and establish nsk and issue recording syslem 2OOSl4-29 200S-05-04 4 days

323 Time Recording System 2005l3middot17 200S-03middot23 5 days

3231 Define time recording methOd 2005-03-17 2005-03-17 1 day

3232 Establish time recording system 2005middot03-18 2005-0323 4 days

3233 Approved time recording system 2005-03-23 2005-03middot23 odays

324 Financial Management System 2005-03middot17 200Smiddot04-01 12 days

3241 Define Procurement Procedures 2005middot03-17 2005-03-22 4 days

3242 Define Financial Reporilng Procedures 2005-03-17 2005-03-23 5 days

-3243 Define Invoicing Procedures 2005-03-24 2005l3-25 2 days

3244 Establish Financial Recording and Reporting System 2005-03-24 2005l3-29 4 days

3245 Define and agree to project budget 2005-03-30 200Sl3-30 1 day

3246 Define and agree to Paymenl Schedule 2COSl3-31 2005-04middot01 2 days

3247 Approved Financial System 200S-04l1 2005-04-01 odays

325 Project Staffing 200S-03-17 325 Establish Project Staffing Plan 2005-03-17

49 days

5 days

7S days

35 days

75 days

79 days

79 days

79 days

79 days

79 days

79 days

79 days

5 days

50 days

158 days

8 days

4 days

2 days

2 days

1 day

35 days

10 days

5 days

5 days

10 days

35 days

30 days

ti I

13-23

bull

middot middot middot middot middot middot

middotmiddot

middotmiddot middot middot middot middot I

middot middot middot middot middot middotImiddotI

middot I

of25

------

Projecl Management System Operational 2005-05-04 2005-05-04

330 Quality Management System 2005-03middot14 2005-04-01

3301 Deline and agree 10 QA standards 2005-03middot14 200503middot16 3 days

3302 Define Quality Management Plan 2005-03-17 2005middot03-30 10 days

3303 Define Communication Plan 2005-03middot 17 2005-03-30 10 days

3305 Approve Quality Management System 2005-03middot31 2005-04middot01 2 days

3304 Define test Plan 2005-03middot 14 2005-03-29 12 dayS

3306 Establish Compuware QACenter Repository 2005-03middot 14 2005-03middot 18 5 days

3307 Train Personnel on Quality Management System 2005-03-21 2005-03-25 5 days

3308 Implement QMS Procedures and Stds 2005-03-28 2005-04-01 5 days

3309 QA System Operational 2005-04-01 2005-04 -0 1 odays

340 Configurallon Management System 200~-O3-14 200~-O4-O4 16 days 3401 Define and agree to documentation standards 2005-03-14 2005middot03middot18 5 days

3402 Define Configuration Management System 2005-03-21 2005middot04middot01 10 days

3403 Define Change control procedure 2005-03middot14 2005-04-01 15 day

3404 Establish Asset Control Procedures and Metliods 2005-03-14 2005-03-18 5 days

3405 Approve Config Management System 2005-04-04 2005-04-04 day

3406 Estabsh Project Documentum Repository 2005-03-21 2005-03middot24 4 days

3407 Transfer SAPS Project related Statutory Documents 2005-03-25 2005middot03middot31 5 days

3408 Transfer Busineoss Analysis Baseline 2005-03-25 2005-03-31 5 day

3409 Train Project Personnel on the use of Documentum 2005-04-01 2005-04-04 2 days

34010 Configuration Management System Operational 2005-04-04 2005-04-04 oday

350 ProjectOffIce Set-up 200~-O3-14 2005-05middot20 50 days

351 Data Line Setup 2005-03middot14 2005-04-01 15 days

3511 Implement amp tesl data lines 2005-03-14 2005-04-01 1S days

352 Environment Conflg 2005-03middot14 2005middot04-1~ 25 days

3521 Configure Office IT Environment 2005-03-14 2005-03-25 10 days

3522 Configure Development IT Environment 2005-03-28 2005-04middot15 15 days

353 Setup ProtOtype System 2005-04middot18 200~middot05middot20 25 days 3531 Configure software 2005-04middot18 2005middot05-13 20 days

3532 Test configuration 2005-05-16 2005-05-20 5 days

360 Finalise and Approve Functional Baseline 2005-03middot11 200~-O8middot22 15 days

361 Compile System Design Framewor1lt 2005-03-11 200~-O7-O8 85 dayS

3611 Compile Functional Data Sheets 2005-03-11 2005-05-04 39 days

3612 Develop and Compile SDF document 2005-05middot11 2005-07-08 42 days 36121 Define Documentation Standards 2005-05-11 2005middot05-24 10 days

36122 Define System Architecture 2005middot05middot25 2005-05middot31 5 days

36123 Define Security Framework 2005middot06middot01 2005-06-14 5 days

36124 Define User Interface Concep 2005middot05middot25 2005-06-14 15 days

30125 Define conceptual data model 2005-05-25 2005-06-14 15 days

36126 Define System Interfacing Concepl 2005middot06-08 2005-06middot1 5 days

36127 Produce SDF document 2005-06middot15

3613 Agree to scope of wor1lt defined in Functional DeSign Specifil 2005-0414

36131 UML Software Acquisition and Training 2005middot04middot14

36132 BUild Use Cases 2005-05-04

36133 Develop user profiles 2005-05-18

2 uf 25 I

Projecl Confidenlial FCSProJecISchedule-Revlslon2006003fda

2iillL1oru-__l20~as~1l1J

2004middot10middot04 200S-03-04 100 days [[ HJ i 642days 0 Vii 11 ~ v I~~~ -l__l n oJL~ J-Jv ~i--1 J_~

2001 Contract Official Signing 2004-10-04 2004-10-04

2002 Project Staffing 2004-10-26 2005-01-10

2003 Accommodation Allocation 2004-10-05 2004-12-10

2004 Finalize and agree to Office Layout 2005-01-10 2005-01-14

210 Office Infrastructure Acquisition 2004middot11-02 2005middot02-28

2101 Furniture acquisition 2004-11-02 2005-01middot03

2102 Telephone line acquisition 2004-11-02 2005l2-28

220 Hardware Acquisition 2004middot11middot02 200S-03-04

220 Office Hardware AcquiSition 2004-11-02 2005middot03-04

2202 Development Hardware AcqUlsition 2004middot11-02 2005l3middot04

230 Software Acquisition 2004middot11-02 20DS-OJ-04

2301 Office Software Acquisition 2004-11-02 2005-03-04

2302 Development Software Acquisition 2004middot11-02 2005-03-04

240 Data Line AcqUisition 2004middot11-02 2005-03-04

2401 Agree to dala line specifications 2004-11-02 2004-11-08

2402 Obtain required authorisations 2004-12-13 2005-03middot04

300 Project Initiation Phase 2005middot03-07 2005middot10middot17

310 Project Team Organisation 2005-03-07 200S-03middot16

3101 Conduct Orientation Work-shop(s) 2005-03-07 2005-03-10

l102 Defina and agree on OrganisatiOnal Siructure (ref ES 020 CDM) 200Sl3middot14 2005-03middot15 3103 Define and agree on work methods amp Procedures 2005l3-14 2005-03-15

3104 Identify and designate SAPS PrOjeCI team members 2005-03-16 2005-03-16

320 Project Management System 2005-03middot17 2005-05-04

321 Establish Project Governance Structures 200S-03-17 2005-03middot30

3211 Establish Project Steering Committee 2005l3-17 2005-03-23

3212 Establish FCS Project Management Team 2005l3-17 2005-03middot23

3213 Davelop and agree to Project Charier 2005l3-17 2005-03-30

322 Risk amp Issue Management System 2005-03middot17

3221 Develop the risk management plan 2005-03-17

3222 Approve riSK management pian 2005-04-28 2005-04-28 1 day

3223 Define and establish nsk and issue recording syslem 2OOSl4-29 200S-05-04 4 days

323 Time Recording System 2005l3middot17 200S-03middot23 5 days

3231 Define time recording methOd 2005-03-17 2005-03-17 1 day

3232 Establish time recording system 2005middot03-18 2005-0323 4 days

3233 Approved time recording system 2005-03-23 2005-03middot23 odays

324 Financial Management System 2005-03middot17 200Smiddot04-01 12 days

3241 Define Procurement Procedures 2005middot03-17 2005-03-22 4 days

3242 Define Financial Reporilng Procedures 2005-03-17 2005-03-23 5 days

-3243 Define Invoicing Procedures 2005-03-24 2005l3-25 2 days

3244 Establish Financial Recording and Reporting System 2005-03-24 2005l3-29 4 days

3245 Define and agree to project budget 2005-03-30 200Sl3-30 1 day

3246 Define and agree to Paymenl Schedule 2COSl3-31 2005-04middot01 2 days

3247 Approved Financial System 200S-04l1 2005-04-01 odays

325 Project Staffing 200S-03-17 325 Establish Project Staffing Plan 2005-03-17

49 days

5 days

7S days

35 days

75 days

79 days

79 days

79 days

79 days

79 days

79 days

79 days

5 days

50 days

158 days

8 days

4 days

2 days

2 days

1 day

35 days

10 days

5 days

5 days

10 days

35 days

30 days

ti I

13-23

bull

middot middot middot middot middot middot

middotmiddot

middotmiddot middot middot middot middot I

middot middot middot middot middot middotImiddotI

middot I

of25

------

Projecl Management System Operational 2005-05-04 2005-05-04

330 Quality Management System 2005-03middot14 2005-04-01

3301 Deline and agree 10 QA standards 2005-03middot14 200503middot16 3 days

3302 Define Quality Management Plan 2005-03-17 2005middot03-30 10 days

3303 Define Communication Plan 2005-03middot 17 2005-03-30 10 days

3305 Approve Quality Management System 2005-03middot31 2005-04middot01 2 days

3304 Define test Plan 2005-03middot 14 2005-03-29 12 dayS

3306 Establish Compuware QACenter Repository 2005-03middot 14 2005-03middot 18 5 days

3307 Train Personnel on Quality Management System 2005-03-21 2005-03-25 5 days

3308 Implement QMS Procedures and Stds 2005-03-28 2005-04-01 5 days

3309 QA System Operational 2005-04-01 2005-04 -0 1 odays

340 Configurallon Management System 200~-O3-14 200~-O4-O4 16 days 3401 Define and agree to documentation standards 2005-03-14 2005middot03middot18 5 days

3402 Define Configuration Management System 2005-03-21 2005middot04middot01 10 days

3403 Define Change control procedure 2005-03middot14 2005-04-01 15 day

3404 Establish Asset Control Procedures and Metliods 2005-03-14 2005-03-18 5 days

3405 Approve Config Management System 2005-04-04 2005-04-04 day

3406 Estabsh Project Documentum Repository 2005-03-21 2005-03middot24 4 days

3407 Transfer SAPS Project related Statutory Documents 2005-03-25 2005middot03middot31 5 days

3408 Transfer Busineoss Analysis Baseline 2005-03-25 2005-03-31 5 day

3409 Train Project Personnel on the use of Documentum 2005-04-01 2005-04-04 2 days

34010 Configuration Management System Operational 2005-04-04 2005-04-04 oday

350 ProjectOffIce Set-up 200~-O3-14 2005-05middot20 50 days

351 Data Line Setup 2005-03middot14 2005-04-01 15 days

3511 Implement amp tesl data lines 2005-03-14 2005-04-01 1S days

352 Environment Conflg 2005-03middot14 2005middot04-1~ 25 days

3521 Configure Office IT Environment 2005-03-14 2005-03-25 10 days

3522 Configure Development IT Environment 2005-03-28 2005-04middot15 15 days

353 Setup ProtOtype System 2005-04middot18 200~middot05middot20 25 days 3531 Configure software 2005-04middot18 2005middot05-13 20 days

3532 Test configuration 2005-05-16 2005-05-20 5 days

360 Finalise and Approve Functional Baseline 2005-03middot11 200~-O8middot22 15 days

361 Compile System Design Framewor1lt 2005-03-11 200~-O7-O8 85 dayS

3611 Compile Functional Data Sheets 2005-03-11 2005-05-04 39 days

3612 Develop and Compile SDF document 2005-05middot11 2005-07-08 42 days 36121 Define Documentation Standards 2005-05-11 2005middot05-24 10 days

36122 Define System Architecture 2005middot05middot25 2005-05middot31 5 days

36123 Define Security Framework 2005middot06middot01 2005-06-14 5 days

36124 Define User Interface Concep 2005middot05middot25 2005-06-14 15 days

30125 Define conceptual data model 2005-05-25 2005-06-14 15 days

36126 Define System Interfacing Concepl 2005middot06-08 2005-06middot1 5 days

36127 Produce SDF document 2005-06middot15

3613 Agree to scope of wor1lt defined in Functional DeSign Specifil 2005-0414

36131 UML Software Acquisition and Training 2005middot04middot14

36132 BUild Use Cases 2005-05-04

36133 Develop user profiles 2005-05-18

2 uf 25 I

------

Projecl Management System Operational 2005-05-04 2005-05-04

330 Quality Management System 2005-03middot14 2005-04-01

3301 Deline and agree 10 QA standards 2005-03middot14 200503middot16 3 days

3302 Define Quality Management Plan 2005-03-17 2005middot03-30 10 days

3303 Define Communication Plan 2005-03middot 17 2005-03-30 10 days

3305 Approve Quality Management System 2005-03middot31 2005-04middot01 2 days

3304 Define test Plan 2005-03middot 14 2005-03-29 12 dayS

3306 Establish Compuware QACenter Repository 2005-03middot 14 2005-03middot 18 5 days

3307 Train Personnel on Quality Management System 2005-03-21 2005-03-25 5 days

3308 Implement QMS Procedures and Stds 2005-03-28 2005-04-01 5 days

3309 QA System Operational 2005-04-01 2005-04 -0 1 odays

340 Configurallon Management System 200~-O3-14 200~-O4-O4 16 days 3401 Define and agree to documentation standards 2005-03-14 2005middot03middot18 5 days

3402 Define Configuration Management System 2005-03-21 2005middot04middot01 10 days

3403 Define Change control procedure 2005-03middot14 2005-04-01 15 day

3404 Establish Asset Control Procedures and Metliods 2005-03-14 2005-03-18 5 days

3405 Approve Config Management System 2005-04-04 2005-04-04 day

3406 Estabsh Project Documentum Repository 2005-03-21 2005-03middot24 4 days

3407 Transfer SAPS Project related Statutory Documents 2005-03-25 2005middot03middot31 5 days

3408 Transfer Busineoss Analysis Baseline 2005-03-25 2005-03-31 5 day

3409 Train Project Personnel on the use of Documentum 2005-04-01 2005-04-04 2 days

34010 Configuration Management System Operational 2005-04-04 2005-04-04 oday

350 ProjectOffIce Set-up 200~-O3-14 2005-05middot20 50 days

351 Data Line Setup 2005-03middot14 2005-04-01 15 days

3511 Implement amp tesl data lines 2005-03-14 2005-04-01 1S days

352 Environment Conflg 2005-03middot14 2005middot04-1~ 25 days

3521 Configure Office IT Environment 2005-03-14 2005-03-25 10 days

3522 Configure Development IT Environment 2005-03-28 2005-04middot15 15 days

353 Setup ProtOtype System 2005-04middot18 200~middot05middot20 25 days 3531 Configure software 2005-04middot18 2005middot05-13 20 days

3532 Test configuration 2005-05-16 2005-05-20 5 days

360 Finalise and Approve Functional Baseline 2005-03middot11 200~-O8middot22 15 days

361 Compile System Design Framewor1lt 2005-03-11 200~-O7-O8 85 dayS

3611 Compile Functional Data Sheets 2005-03-11 2005-05-04 39 days

3612 Develop and Compile SDF document 2005-05middot11 2005-07-08 42 days 36121 Define Documentation Standards 2005-05-11 2005middot05-24 10 days

36122 Define System Architecture 2005middot05middot25 2005-05middot31 5 days

36123 Define Security Framework 2005middot06middot01 2005-06-14 5 days

36124 Define User Interface Concep 2005middot05middot25 2005-06-14 15 days

30125 Define conceptual data model 2005-05-25 2005-06-14 15 days

36126 Define System Interfacing Concepl 2005middot06-08 2005-06middot1 5 days

36127 Produce SDF document 2005-06middot15

3613 Agree to scope of wor1lt defined in Functional DeSign Specifil 2005-0414

36131 UML Software Acquisition and Training 2005middot04middot14

36132 BUild Use Cases 2005-05-04

36133 Develop user profiles 2005-05-18

2 uf 25 I

Project Confidentiat

Sottware Function Definition 2005-06-06

362 Update System Oeign Framework 2005-07-14 2005-08-03

3621 Update appendices 2005-07-14 2005-08-03 15 days

3622 Update main document 2005-07middot14 2005-08-03 15 days

363 Review and approve System Design Framework 2005-06-05 2006-08-22 76 days

363f Review and approve Functional Data Sheets 2005-05-05 2005-08-22 76 days

3632 Review and approve System Design Framework 2005-08-04 2005-08-22 12 days

370 Finalisatlon of Project Initiation Activities 2oo5-OlH6 2005-10-17 44 days

3701 Review and approve QA CM amp Risk plans (by SAPS Directors) 2005-08-16 2005-10-17 44 days

3702 Review and approve Project Charter (by SAPS Directors) 2005-08-16 2005-10-17 44 days

3703 Review and approve Communicalions and HR plans (by SAPS Direct 2005middot06-16 2005middot10-17 44 days

3704 Review and approve Functional Data Sheets (by SAPS Directors) 2005-08-23 2005middot10-17 39 days

3705 Review and approve SDF (by SAPS Directors) 2005-08-23 2005-10-17 39 dys

3706 Functional Baseline Approved 2005-10-17 200510-17 o days

400 Design Phase 2005-09-05 2006-05-26 171 days

410 FCS System DeSign 2005-09-05 middot 2006-05-16 163 days

411 Finalise Physical Data Model 2005-09-05 2006-02middot16 106 days

4111 Study Source Informalion 2005-09-05 2005-09-07 3 days

4112 Conduct JAD Sesslon 10 discuss data model 2005-09-08 2005-09-08 1 day

4113 Develop Documentum Object Model 2005-09-05 2005-09-19 11 days

4114 Define middotFirearm Register PhYSical data entity model 2005-09-05 2005-09-19 11 days

4115 First Review of Data amp Object Model 2005-09-20 2005-09-28 6 days

4116 Compile Data Model Speciflcation 2005-09middot29 2005-10-12 10 days

4117 Investigate data interfaces and integration 2005-09-29 2005-10middot05 5 days

4118 Define GIS interface 2005-10-13 2005-11-09 20 days

4119 Populate Oracle DeSigner repository 2005-11-10 2005middot11-16 5 days

41110 Final ReVIew of Data and Object Model 2005-11-10 2006-02-03 50 days

41111 Deliver Data Model Specification 2006middot02-06 middot 2006-02-07 2 days

12 SAPS Approve Dala Model Specification 2006-02-06 2006-02middot16 7 days

412 User Interfaces Specification 2005-09-05 2005middot11-07 45 days

4121 Sludy Source Information 2005-09-05 2005-09-09 5 days

4122 Conduct JAD Session to discuss User Interface 2005-09-12 2005-09-12 1 day

4123 Compile SClllen Layout Templates 2005-09middot13 2005middot10-06 17 days

41 231 Compile Menu Hierarchies 2005-09-13 2005-09-14 2 days

41232 Compile Portal Screen templates 2005-09-15 2005-09-21 5 days

41233 Compile Oracle Form Screen templates 2005-09-22 2005-09-29 5 days

~1234 Compile WebTop Screen templates 2005-09-30 2005-10-06 5 days

41235 Compile scanning amp Indexing Screen tempiates 2005-09-13 2005-09-19 5 days

41236 Compile public website screen templates 2005middot09middot20 middot 2005-09-27 5 days

41237 Compile enquiry function screen layout 2005-09-28 2005-10-04 5 days

4124 Review User Interface Sp~cilication 2005-10-05 2005-10-11 5 days

4125 AddiHonal review time 2005-10-12 2005-10-13 2 days

4126 Update amp Deliver User Interface Specification 2005-10-14 2005-10-27 10 days

4127 SAPS Approve User Interface Specification middot2005-10-28 2005-11-07 7 ~ays

413 User Profiles Specification (Core System) 2005-09-05 2006-02-03 97 days

4131 Develop User Profiles for Core Processes 2005-09-05 2005-08-23 15 days

I

I I I I

I I I

I

I

I I I

I I

I I 1

4 middot1

~ 1~i IImiddot ~~---

3 of 25 _ V~cslon 40~ _l~c-(~___________________________________________~p~roJ~ec Confidentiar

----------------------------------

2005middot09~29 2005middot10middot26

413A Additional review period 2005-10-27 2005-11-16 15 days

4135 Deliver Spec 2005-11middot17 2005-11-18 2 days

4136 SAPS Approve Spec for Core Processes 2005middot11-21 2006-02-03 43 days

414 ICT Architecture SpeCification 2006-01middot23 2006-03middot27 45 days

4141 Develop ICT Architecture Specification 2006-01-23 2006-03-15 38 days

4142 Internal review and refine 2006-03-02 2006-03-15 10 days

4143 SAPS Approve ICT Architecture 2006middot03-16 2006middot03middot27 7 days

415 System Securlty Model SpeCification 2005-09middot27 2006-03-27 117 days

4151 Develop System Security Model 2005-09middot27 2005middot10-24 20 days

4152 Compile security specification 2005-10-25 2006-02middot03 62 days

4153 Internal Review of System Security Model speCification 2006)2-06 2006-03middot15 28 days

4154 SAPS Approve Securily Model 2006-03-16 2006middot03-27 7 days

416 Reporting amp Bi O sign Specification 2005-09-05 2006middot02middot10 I 02 days

4161 Develop Reporting amp 61 Specification 2005middot09-05 2005-09-16 10 days

4162 Develop Design Solution for BI amp Reporting 200S)9-19 2005-10-03 10 days

4163 Finalise Reporting amp BI Specification (Documenl) 2005-10-04 2005-10-31 20 days

4164 Review Reporting amp BI Specification 2005-11-01 2005-11-21 15 days

4165 Deliver Reporting amp BI Specification 2005-11-22 2005-12-02 9 days

4166 SAPS Approve BI and Reporlting Specification 200512-05 2006middot02middot10 38 days

417 Workflow Build ReqUirements Specification 2005-09-05 2006middot01middot18 85 days

4171 Conduct workflow JAO session 200S)9-05 2005-09-09 5 days

4172 Develop Workflow Models 2005)9middot12 200S-09-23 10 days

4173 Peer Review Workflow Models 200S)9-27 2005middot10middot24 20 days

4174 Compile Workflow Build Requirements Specification 200S-10middot25 2005middot11middot03 8 days

4175 Revlew Workflow Build Requirements SpeCification 2005-11-04 2005-11middot14 7 days

4176 SAPS Approve Workflow Build Requirements Specificalion 2005middot1F15 2006middot01middot18 35 days

418 System Design Specification 2005-09middot19 2006-03-07 109 days

4181 General Components Design Speclflcations 2005-09middot19 2006middot02middot28 104 days

41811 Develop General Components TDS 2005-09middot19 2005-10-26 27 days

41812 Review Gelleral Components T[IS 2005middot1027 2005middot11middot21 18 days

41813 Update Genera Component TDS 2005-11-22 2005-12-12 15 days

41814 Internal review of concept deSign using core build 2005-12-13 2006-02-17 37 days

41815 SAPS Approve updated specification 2006-02middot20 2Q06-02-28 7 days

4182 Documentum Design Specifications 2005-09-19 2006-03-07 09 days

41821 Develop Documentum TDS 2005-09-19 2005-10-17 20 days

41822 Refine Documentum TDS 2005middot10-18 2006middot02middot17 77 days

41823 Internal review of Docurnenlurn TOS 2006middot02-20 2006middot02middot24 5 days

41824 SAPS Approve Documentum TDS 2006-0227 2006-03-07 7 days

4183 Oracle Design Specification 2005-10-24 2006-03-07 85 days

41831 Develop Oracle TDS 2005-10middot24 2005middot11middot2-lt 24 days

41832 Refine Oracle TDS 2006-01-09 2006-02middot7 30 days

41833 Internal review of Oracle TDS 2006-02middot20 2006-02-24 5 days

41834 SAPS Approve Oracle 1 DS 2006-02-27 2006middot03-07 7 days

Competency amp Accreditation Build SpeCification 2005middot09-30 2006-03middot30 116

Specification for Competency Certificates 2005-09-30 2006-02-03 68

Proleot Confidential 40125 V~rsion 40

----------------------------------

2005middot09~29 2005middot10middot26

413A Additional review period 2005-10-27 2005-11-16 15 days

4135 Deliver Spec 2005-11middot17 2005-11-18 2 days

4136 SAPS Approve Spec for Core Processes 2005middot11-21 2006-02-03 43 days

414 ICT Architecture SpeCification 2006-01middot23 2006-03middot27 45 days

4141 Develop ICT Architecture Specification 2006-01-23 2006-03-15 38 days

4142 Internal review and refine 2006-03-02 2006-03-15 10 days

4143 SAPS Approve ICT Architecture 2006middot03-16 2006middot03middot27 7 days

415 System Securlty Model SpeCification 2005-09middot27 2006-03-27 117 days

4151 Develop System Security Model 2005-09middot27 2005middot10-24 20 days

4152 Compile security specification 2005-10-25 2006-02middot03 62 days

4153 Internal Review of System Security Model speCification 2006)2-06 2006-03middot15 28 days

4154 SAPS Approve Securily Model 2006-03-16 2006middot03-27 7 days

416 Reporting amp Bi O sign Specification 2005-09-05 2006middot02middot10 I 02 days

4161 Develop Reporting amp 61 Specification 2005middot09-05 2005-09-16 10 days

4162 Develop Design Solution for BI amp Reporting 200S)9-19 2005-10-03 10 days

4163 Finalise Reporting amp BI Specification (Documenl) 2005-10-04 2005-10-31 20 days

4164 Review Reporting amp BI Specification 2005-11-01 2005-11-21 15 days

4165 Deliver Reporting amp BI Specification 2005-11-22 2005-12-02 9 days

4166 SAPS Approve BI and Reporlting Specification 200512-05 2006middot02middot10 38 days

417 Workflow Build ReqUirements Specification 2005-09-05 2006middot01middot18 85 days

4171 Conduct workflow JAO session 200S)9-05 2005-09-09 5 days

4172 Develop Workflow Models 2005)9middot12 200S-09-23 10 days

4173 Peer Review Workflow Models 200S)9-27 2005middot10middot24 20 days

4174 Compile Workflow Build Requirements Specification 200S-10middot25 2005middot11middot03 8 days

4175 Revlew Workflow Build Requirements SpeCification 2005-11-04 2005-11middot14 7 days

4176 SAPS Approve Workflow Build Requirements Specificalion 2005middot1F15 2006middot01middot18 35 days

418 System Design Specification 2005-09middot19 2006-03-07 109 days

4181 General Components Design Speclflcations 2005-09middot19 2006middot02middot28 104 days

41811 Develop General Components TDS 2005-09middot19 2005-10-26 27 days

41812 Review Gelleral Components T[IS 2005middot1027 2005middot11middot21 18 days

41813 Update Genera Component TDS 2005-11-22 2005-12-12 15 days

41814 Internal review of concept deSign using core build 2005-12-13 2006-02-17 37 days

41815 SAPS Approve updated specification 2006-02middot20 2Q06-02-28 7 days

4182 Documentum Design Specifications 2005-09-19 2006-03-07 09 days

41821 Develop Documentum TDS 2005-09-19 2005-10-17 20 days

41822 Refine Documentum TDS 2005middot10-18 2006middot02middot17 77 days

41823 Internal review of Docurnenlurn TOS 2006middot02-20 2006middot02middot24 5 days

41824 SAPS Approve Documentum TDS 2006-0227 2006-03-07 7 days

4183 Oracle Design Specification 2005-10-24 2006-03-07 85 days

41831 Develop Oracle TDS 2005-10middot24 2005middot11middot2-lt 24 days

41832 Refine Oracle TDS 2006-01-09 2006-02middot7 30 days

41833 Internal review of Oracle TDS 2006-02middot20 2006-02-24 5 days

41834 SAPS Approve Oracle 1 DS 2006-02-27 2006middot03-07 7 days

Competency amp Accreditation Build SpeCification 2005middot09-30 2006-03middot30 116

Specification for Competency Certificates 2005-09-30 2006-02-03 68

Proleot Confidential 40125 V~rsion 40

i -~

Firearms Control System Project Schedule FCSProJeclSchedule-Revslon20060203fda

( A I -tlt4

4194 Deliver Build Specifications 2006-03-13 2006-03-17 5 days

4195 SAPS Approve Competency amp Accreditation Build Specfications 2006-03-20 2006-03-30 7 days

4Z0 2005-10-04 2006-03-06 98 days

4201 ~terface JAD sessIOns 2005-10-04 5 days

4202 Investigate FCSIFRS Interfacing options 2005-10-11 2005-10-24 10 days

4203 Investigate FCS Implementallon concepts 2005-10-25 2005-11-07 10 days

4204 Compile Investigalion report 2005-11-08 2005-11-14 5 days

4205 Authorisation of addendum 2006-02-20 2006-02-20 o days

4206 Review FCSIFRS Interfacng and Implementation 2006-02-20 2006-02-23 4 days

4207 Update and deliver Investigation Report 2006-02-20 2006-C2-23 4 days

4208 SAPS Approve FCSIFRS Inte1~ce investigalon report 2006-02-24 2006-03middot06 7 days

42 2005-10-18 2006-03-14 94 days

4211 2005-10-16 middot2006-02-24 62 days

4212 Receve updated BRR (Ptech) model from SAPS 2006-01-27 2006-01-27 odays

4213 Review updaled BRR model 2006-02-13 2006-02-17 5 days

4214 Update Data Sheets 2006-02-20 2006-03Q3 10 days

4215 Update User Profile Speciflcallon 2006-02-20 2006-03-03 10 days

4216 Inlemal Review of User Profiles 2006Q2-27 i 2006-0303 5 days 4217 SAPS Aeprove updated User Profles 2006-03-06 2006-03-14 7 days

422 2005-10-04 2006Q2-28 94 daysII J4221 Conduct Data Intetface JAD Session 2005-10-04 2006-01-20 67 days

42211 Conduct JAD Session to dscuss interfacing via IJS Interope 2005-10middot04 2005-10-04 1 day

4221i Conduct JAD Session to discuss CRIM amp AFIS Interface 2005-17 2005-17 1 day

42213 Conduct JAD Session to discuss CAS Interface 2005-10-06 2oo5-10Q6 1 day

42214 Conduct JAD Session to discuss Persallnterfac 2005-10-07 2005-10-07 1 day

42215 Conduct JAD Session to discuss PoWn Interface 2006-01-20 2006-01-20 1 day

42216 Conduct JAD Session to discuss FSL Interface 2006Q1-20 2006-01-20 1 day

4221r Conduct JAD Session to discuss Circulations Interface 2005-10-12 2005-10-12 1 day

42216 Conduct JAD Session to discuss Inkwazi Interface 2005-11-30 2005-1 ~-30 1 day

42219 Conduct JAD Session to dISCUSS PAS Interface 2005-10-14 2005-10-14 1 day

422110 Conduct JAD Session to discuss NPIS Intertace 2005-10-17 2005-10-17 1 day

422111 Conduct JAD Session Exhibit Inlerface 2006Q1-20 2006-01-20 1 day

422112 Conduct JAD Session to dISCUSS HANIS Interface 2005-11-08 2005-11-08 1 day

422113 Conduct JAD SessIon to discuss MCS Interface 2006-01-20 2006-01-20 1 day

4222 Comptle Interface Control Document 2005-10-21 2006-02-28 81 days

42221 DeSIgn Interface Solution for External Systems 2005-10-21 2005-12-01 30 days

42222 DeSign interface to lnlernat SAPS Systems 2005-10-21 2005-12-01 middot30 days

4222j Compile Inlerface Control Documenlalion 2005-11-18 2006-02-10 49 days

42224 Inlernal Review of interface conlrol document 2Q06-02-13 2006 -02-i 7 5 days

middot42225 SAPS Approve Interface Control Documenl 2006-Q2middot20 2006-02-28 7 (jays

423 Electronic Fonns DeSign 2006-02-20 2006-03-22 22 days

4231 Develop Electronic Form Design Speclflcation 2006-02-20 2006Q3-1O 15 days

4232 nternal Review of Electronic Form DeSign 2006-03-06 2006Q3-10 5 days

4233 SAPS Approve Electronic Forms Design 2006-03-13 2006-03-22 7 days

424 Fireann Digital Image Viewing Design 2006-01-16 middot2006Q3-15 43 days

Proje ConfIdential V sion 40

~Irearms Control System Proiect Schedule Project Confidential FCSProjeclScheduleKevlslon20060203fda

1 ID 1 WBS ITask Name Start Finish [JJratlon -0602 1_middot0sect03_ __j

OEi9-_I_middotO~_01 I__middot_O9~Ll ~ s J_MJJ~JIT~_Qlt1Lf2LUJM__~ IMJJJJi 236 424 1 Develop Firearm Digital Image Viewing System Design 2006-01-16 2006-03-06 36 days I

~7 i 4242 Internal Review of Firearm Digital Image Viewing System Design 2006-02-07 2006-03-06 20 days I

2381 4243 SAPS Approve Firearm Digital Image Viewing System Design 2006-03-07 2006-03-15 7 days I -~ iI 39 425 Public Web Site Design 2005-10-17 200S-03-29 104 days I I I 240 4251 Study Source Information 2005-10-17 2005-10-28 10 days ~

241 4252 Conduct Public Web Site JAD Session 2005-10-31 2005-11-01 2 days

242 4253 Additional review time 2005-11-02 2005-11-03 2 days

243 4254 Develop- Public Web Site Design 2005-11-i i 2006-02-09 53 days

244 4255 Internal Review of Public Web Site DeSign 2006-02-10 2006-03-16 25 days

245 4256 SAPS Approve Public Web Site Design 2006-03-17 2006-03-29 7 days

246 426 General Enquiry Function Design 2005-10-17 200S-03-22 100 days

247 4261 Develop General Enquiry Design 2005-10-17 2005-11-11 20 days

t-24n 4262 Review General Enquiry Design 2005-11-14 200511-30 13 days

4263 Update General Enquiry Design 2006-01-16 2006-02-10 20 days i 249 I 4264 Internal ReView of General Enquiry Design 2006-01-16 2006-03-10 40 days

4265 SAPS Approve General EnqUirY Design 2006-03-13 2006-03-22 7 days i ~~ I I 252 427 User Support Design 2006-02-20 200S-03-30 27 days

I 25~3_1 4271 Develop User Support Design 2006-02-20 2006-03-17 20 days

254 4272 Internal Review of User Support Design 2006-03-13 2006-03-17 5 days

~ 4273 SAPS Approve User Support Design 2006-03-20 2006-03-30 7 days

426 7ArI _h~ 200S-02-24 200S-05-1S 52 daysI~H 4261 _nalYSe data 200S-02-24 200S-03-09 10 day

-258 4282 Develop data map 2006-03-10 200S-03-24 10 days

4283 2006-03-27 2006-04-03 5 days ~ l----wo 4284 2006-04-04 2006-04-10 5 days

1261 4285 2006-04-11 2006-04 19 5 days - 262-[ 4286 Compile lnlerface Specification 2006-04-20 2006-05-05 10 days l--J I 263 I 4287 Internal Review of Interface Speciflcatior 2006-04-28 2006-05-05 5 days

i264l 4288 SAPS Approve Integration Specification 2006-05-08 2006-05-16 7 days

~ 440 2005-10-14 200S-02-15 725 day

I 266- 441 Configure Core System 2005-10-14 2005-12-02 36 days 267 4411 Configure Documenlum Content Server 2005-10-14 2005-10-20 5 days

4412 Configure Oracle Database 2005-10-18 2005-10-19 2 days

4413 Configure Oracle Application Server 2005-10-20 2005-10-26 5 days ~~- i 270 441 4 Configure Adobe life Cycle Forms 2005-10-21 2005-10-27 5 days

1271 4415 Configure Cold Fusion 2005-10-27 2005-11-02 5days 1- I~ 4416 Configure Emiddotmail amp Fax Server 2005-10-18 2005-10-24 5 day

__373 j 4417 Configure Content Distribution Services 2005-10-25 005-11-22 21 days

274 J 4418 Configure Digital Asset Management 2005-11-01 2005-11-07 5 days

~-I )419 Build the PQdal 2005-10-27 2005-12-02 27 days

2iE3-j 441 10 --tBuild Front Desk Scann~ng 2005-10-18 2005-11-21 25 days 1441 11 Build SpeCialised Printing 2005-10-28 2005-11-24 20 days I ~~ 442 Build Sample Functional Processes 2005-11-01 2006-02-15 Smiddot125 day1_278 Ii 279 4421 bull i2005-11-01 2006-02-03 57 days

i 280 I 44211 2005-11-01 2006-01-25 50 days

Build Process application for a competency certificate 2005-11-17 2006-02-01 25 days

Test Competency Certificate Functionality 2006-02-02 2006-02-03 2 days bull _~______bull I-------I

I I

II III

III

~IJj I bull

1

-------------=- 60f25 1

1

Proje J~ Confidential V sion 40

~ 44212

4421 3

--~

Firearms Control System PrOject Schedule -- shy

10 Name

4422 accreditation for business purp

44222 Build Process application for accreditation as an official insti

44223 Build Process application for accreditation as an 1~~tIriAtinn

44224 Test Accreditation Functionality

439 Integrate and Test Core System 4301 Integrate and Test Core System

4302 Internal Review of Core System

4303 Snr Mgt Core System Demonstration 450 Acceptance Test Planning

4501 Develop FCS tesl plan

4502 Internal review of FCS tesl plan

4503 SAPS Approve FCS test pi

4504 Develop FCSFRS Interface test plan

4505 Inlernal review of FCSFRS Interface test plan

4506 SAPS Approve FCSFRS Interface test plan

470

471 5Jl 4711

4712 Setup amp Ccnfigure Software

4713 Test Core System Operation

471 4 Tram Test Users

472SU T 4721 bull

4722 Setup amp Configure Software

4723 T est Cere System Operation

460 i4601

lt602 Conduct Design Review Workshop

4603 Updae documentation

4604 Sig~-off deg5190 Baseline

4605 Design Baseline Approved 500 Development Phase 510 FCS Development

5101 General components

51011 Manage paper flies and folders

5101 11 Build

5101 2 Transition

510113 Test amp QA

510114 Refine S~ftware

51011 5 Function S ignoft

51012 Resource management

51012- Build

510122 Transition

510123 Test amp QA

510124 Refine Software

Function Signoff

flO

2005-11middot22 2006middot02-06

2006-01-25 2006-02-13

2006-01-25 2006-02-13

2006-02middot13 2006-02-15

2006-02-08 2006-03-24

2006-02-08 2006-03-16

2006-02-16 2006-03middot24

2006-02-10 2006-02-10

2005-11-21 2006-04-07

2005middot11-21 2005-12-09

2005-12-05 2006-02-03

2006-02-06 2006-02-14

2006-03-07 2006-03-28

2006-03-n 2006-03-29

2006-0330 2006-04middot07

2006-03middot24 2006-05middot15

2006-03middot24 2006-04-26

2006-03-24 2006-04-03

2006-04-03 2006-04-1 deg 2006-04-10 2006-04-19

2006-04-19 2006-04-26

2006-04-26 2006-05middot15

2006-04-28 2006-05-03

2006-05-03 2006-05-08

2006-05-08 2006-05middot15

2006-05-15 2006-05-26

2006-05-15 2006-05-18

2006-05-17 2006-05-19

2006-05-19 2006-05-24

2006-05-22 2006-05middot26

2006-05-26 2006-05-26

2006-03-30 2007)1middot31

2006-03-30 2006-09middot27

2006-03-30 2006-06-14

2006-03-30 2006middot05-08

2006middot03-30 2006-04-11

2006-04-13 2006-04-13

2006-04-1 B 2006-04-20

2006-04-21 2006-04-25

2006middot04-26 2006middot05middot08

2006-05-09 2006Q6-14

2006-05-09 ~006-05-22

2006-05-23 2006-05-24

2006middot05-25

2006-06-01

2006-00-06

27 days

13 days

13 days

2 days

31 days

26 days

25 days

1 day

86 days

15 days

33 days

aays

15 days

odays

3 days

3 days

5 days

975 days

3 days

3 days

4 days

5 daygt

odays

l04days

26 days

51 days

24 days

10 days

1 day

3 days

3 days

7 days

27 days

days

2 days

0125

510132 Transition

510133 Test amp QA

510134 Refine Software

510135 Function SI9noff

51014 Implement Security

510141 BUild

510142 TranSition

510143 Test amp QA

510144 Refine Software

510145 Function Signoff

5102 Develop FCSFRS Interface 51021 Develop migration methods and tools

51022 Develop data dictionary

51023 Develop dala schemas

51024 Develop and test FCS data PUIl1P

51025 Oeve~op and test Documelturn dala pump

26 DevelOp OCI wrapper

Develop dynarric interface components

51028 Test data migration from end to end

51029 Develop IOterface management reports

510210 Document interface

5103 Build Firearm Control Processes

51031 Design Firearm Control Processes

510311

5103111

510311 2

5103113 Define design for proce

5103114

5103115

5103116

51031 17

5103118

5103119 Compile bUild specificalion

510312 Develop Retums build specification

5103121

5103122

5103123

5103124

5103125

5 iO~l 1 26

510313

5103131

5103132

1300

2006-04-13 2006-04-13

1 day

2006-04-18 2006-04-24 5 days

2006-04-25 2006-05-03 5 days

2006-05-04 2006-05-12 7 days

2006Q3-30 2006QSmiddot22 34 days

2006-03-30

2006-04-21 15 days 2006-04-24 bull 2006-04-25 20ays

middot

2006-04-26 2006-05-04 5 days

middot 2006-05-05 2005-05-11 5 days 2006-05-12 2006-05-22 7 days middot 2006-05middot17 2006Q9-27 96 days

2006-05-17 2006-06-06 15 days

2006-06-07 2006-06-20 10 days

2006-06-21 2006-07 -04 10 days

2006-07-05 2006-07-18 10 da~s

200G-O-19 2000-08-01 10 deys

2006-08-02 2006-08-08 6 days

2006middot07-27 2006~O8-30 25 days

2006-08-31 2006-09-13 10 days

2006-09-14 2006-09-27 10 days

2006-09-14 2006~09-27 10 days

2006Q3-30 2006Q9-26 125 days

2006Q3-30 2006Qa-29 105 days

2006-03middot30 2006Q4-21 15 days

2006-03-30 2006-04-21 15 days

2006-03-30 2006-04-21 15 days

2006-0330 2006-04-21 15 days

2006-04-21 15 days

2006-03-30 2006-04-21 15 days

2006-03-30 2000middot04-21 15 day

2006-03-30 middot 2006-04-21 15 days

2006-03lt30 2006-04~21 15 days

2006-03middot3( 2006-04-21 15 days

2006Q4-13 2006middot05Q2 10 days

2006-04-13 2000-05-02 10 aays

2006-04-13 2006middot05-02 10 days

2006-05~02 10 days

2006-04-13 middot 2006-0S-02 10 days

2Q06-04-13 2006-05-02 10 days

2006-04-13 2006-05-02 10 days

2006-04-24 2006-05-16 15 days

2006-04-24 2006-05-16 15 days

2006-04-24 I I~~

2006-04-24

Proiet Co)fiden

Firearms Control System Project Schedule Project Confidential FCSProjectSchedule Revislon200602031da

Develop licensing amp inspections build speCification

Define design for process application for licence to po

Define design for process application for licence to can

application for licence to deal

Define design for process application for licence to mar 2006-03-30

Define design for change commerCial agent premises

Define deSign for performAaministrate inspectton of de

Define design for periormAdminntrate inspection of gUJ

Define design for perforrnlAdmlOisrrate inspection of me

Define design for Manag relurns

Define design for Introduce firearm into SA legal firearrr

Define design for Inlroduce ammunition into SA (Import 2006-04-13

Deline design for Process application for acyuisilion by

Define design for Maintain official institution I egister

Compile Define design for specification

Develop ImportlExportiln transiU Transport Oefine desig

Define deSign for process application for permit lt0 Impo

Define deSign for Procesb _~ppllcation tor multiple impof 2006-04middotmiddot24

Deline design for Process applicatioo for multiple impor

Define design for Process application for multiple impor

37

5103138

5103139

51031310

5103U11

51031312

51031313

51031314

51031315

51031316

510314

5103141

51031 42

5103143

510314 4

510314 5

5103_ Ui

3151

51031S2

5103153

510_316

510j161

5103162

5)03163

510317

~103171

5103172

5103 3

5103114

5103175

5103U6

5103177

5103178

5103179

51031710

51031711

51031712

510 31713

51031714

510318

5103181

5103182

5103183

503184

5103185

Define design for Process application for temporary im 2006-04-24 2006-05-16 15 days

Define design for Process application for temporary im 2006-04-24 2006-05-16 15 days

Define design for Process application for permit to carr 2006-04middot24 2006-05-16 15 days middot middot Define design for Process application for permit to carr 2006-04-24 2006-05-16 15 days middot Define deSign for Process application for permit to carr 2006-04-24 2006-05-16 15 days

Define design for Transit firearm through SA 2006-04-24 2006-05-16 15 days

Deline design for Physically export firearms 2006-04-24 2006-05-16 15 days

Define design for Physically export ammunition 2006-04-24 2006-05-16 15 days middot middot DeflOe design for Conlrol firearm item storage at border 2006-04-24 2006-05-16 15 days middotmiddot Compile build specification 2006-04-24 2006-05-16 15 days

Oevelop Temporary Authorisation build speCification 2006-05middot10 middot 2006~5-23 10 days

Define design for Process application for a temporary a 2006-05-10 2006-05-23 10 days

Define deSign for Process application for temporary aut 2006-05-10 2006-05-23 10 days

Define design for Process application for temporary lice 2006-05-10 2006-05-23 10 days

Define deSign for Process application tor a lemporary a 2006-05-10 2006-05-23 10 days

Compile build specIfication 2006-05-10 2006-05-23 10 days

Develop Permits Oefine design for specification 2006~5-17 2006-05-30 10 days

Define design for Process applicallon for permit 10 colle 2006middot05 middot17 200605-30 10 days

Define design for Process application for permit 10 tram 2006-05-17 middot 2006-05-30 10 days

Compile build specificalion 2006-05-17 middot 2006-05-30 10 days

Develop Appeals Define dsgn for specificallon 2006~5-24 2006~6~6 10 days

Define design far Manage Appeal 2006-05middot24 2006-06-06 10 days

Define design for Process Appeal 2006-05-24 2006-06-06 10 days

Compile build speCification 2006-05-24 2006-06-06 10 days

Develop Notification build specification 2006-05-31 2006~6-20 15 days

Define deSign for Declare firearm free zone 2006-05-31 2006-06-20 15 days

Define design for Update Central Firearms Register will 2006-05-31 2006-06-20 15 days

Define design for Update Central Firearms Register witl 2006-05-31 middot 2006-06-20 15 days

Define design for Update Central Firearms Registerwltl 2006-05-31 2006-06-20 15 days

Define design for Updale manufaclurer licence with ne 2006-05-31 2006-0620 15 days

Define design for Process nolification of alteration done 2006-05-31 2006-06-20 15 days

Define design for Process request 10 alief firearm 2006-05-31 2006-06-20 15 days

Define design for Manage information on annual report 2006-05middot31 2006-06-20 15 days

Define design for Up dale central firearm register with nl 2006middot05-31 2006-06-20 15 days

Define design fOi Process notification of lasUstolenldef 2006-05-31 2006-06-20 15 days

Define design for Inform registrar that executoradmlflisl 2006-05middot31 2006-06-20 15 days

Define design for Inform regislrar of progress that has b 2006-05-31 2006-06-20 15 days

Define design for Ensure Ihal all firearms possessed or 200605-31 2006-06-20 15 days

(ompile build speCifIcation 2006-05-31 2006-06-20 i5 days

15 days

Develop Renewals build specification 2006~6-14 2006-07-ltl4 15 days

Define design for Apply for firearm warrant renewal that 2006-0614 2006-07-04 15 d8yS

Define design for Apply for firearm warrant renewal that 2006-06-14 200S()7-04 15 days

Define design for Apply for firearm warrant renewal thatmiddot 2006-06-14 200607-04 15 days

Defina deSign for Apply for firearm warrant renewal that 2006-06-14 2006-07-04 15 days

Define design for Apply for firearm warrant renewal at C 2006-06-14 7006-01-04 15 days

PrO)eel Confidenlai 9 of 25 Vfsion 40

Project Confidential FCSProjectSchedule-Revlsion20060203fda

Task Name

460

46i7 462

463

5103188

5103189

51031810

51031811

51031812

51031813

510 31814

51031815

51031816

51031817

51031618

51031819

51031820

51031821

51031822

51031823

5103_19

510319

5103192

5103193

5103194

5103195

5103196

5103197

5103198

5103199

51031910

510319

5103110

5103 1101

51031102

51031103

51031104

51031 105

51031106

51031107

51031108

5103110 9

510311010

510311011

510311012

510311013

510311014

510311015

Define design for Decide whether llcerice to posses-- I

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whelher licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether commercial agent lie 2006-06-14

Define design for Decide whether permit to possess am 2006-06-14

Define design for Decide whether Import permit may be 2006-06-14

Define design for Decide whether export permit may be 2006-06-14

Define design for Decide whether in-transit permit may I 2006-06-14

Define design for Decide whether firearm transport perr 2006-06-14

Define design for Decide whether temporary authorisati 2006-06-14

Define deSign for Approve firearm warrant renewat appl 2006-06-14

Define design for Refuse firearm warrant renewal appli 2006-06-14

Define design for Assess applicallon for Iransitional ren 2006-06-14

Define design for Issue renewed firearm warrant 2006-06-14

Compile build specification 2006-06-14

Develop Duplication (replacements) build specification 2006-06-28

Define design for Replace commercral agent licence 2006-06-28

Define design for Replace compelency certlficale 2006-06-28

Define deSign for Replace transpor1 permit 2006-06-28

Define design for Replace licence to possess 2006-06-28

Define design for Replace expor1 permit 2006-06-28

Define design for Replace ammunition collection permit 2006-06-28

Define design for Replace temporary authOrisation 2006-06-28

Define design for Replace impor1 permit 2006-06-28

Define design for Replace accreditation certiflcale 2006-06-28

Define design for Replace in-transit permit 2006-06-28

Compile build specificalion 2006-06-28

Develop Cancellation amp Suspension build speclllcalJon 2006-07-05

Define design for Regislrar determines whether person 2006-07-05

Define design for Decide persons fitness to possess a I 2006-07-05

Define design for Finalise registrars deCision that perslt 2006-07-05

Define design for Finalise registrars deCision that perse 2006-07-05

Define design for Inform registrar and Irwestlgaling offie 2006-07-05

Define design for Finalise unfitness status of person wh 2006-07-05

Define design for Process cancelled licence to possess 2006-07-05

Defina design for Process Cancelled import permit 2006-07-05

Define design for Process cancelled commercial agent I 2006-07-05

Define design for Process cancelled temporary authoris 2006-07-05

Define design for Process cancelled in-transit permit 2006-07-05

Define design for Ensure that cancelled export permit is 2006-07-05

Define deSign for Ensure that cancelled transport permi 2006-07middot05

Define design for Inform registrar of ceasing to carry on 2006-07 -05

Define design for ReconCile warrant holders list of paS 2006-07-05

Define desian for Reverse unfit persons unfitness statu 2006-07-05

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07middot25

2006-07-25

15days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

10 days

10 days

10 days

10days

10 days

10 days

10 days

10 days

10 days

10 days

10 days

10 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

I

I

U~___ __j __ __ j

10 of

510132 Transition

510133 Test amp QA

510134 Refine Software

510135 Function SI9noff

51014 Implement Security

510141 BUild

510142 TranSition

510143 Test amp QA

510144 Refine Software

510145 Function Signoff

5102 Develop FCSFRS Interface 51021 Develop migration methods and tools

51022 Develop data dictionary

51023 Develop dala schemas

51024 Develop and test FCS data PUIl1P

51025 Oeve~op and test Documelturn dala pump

26 DevelOp OCI wrapper

Develop dynarric interface components

51028 Test data migration from end to end

51029 Develop IOterface management reports

510210 Document interface

5103 Build Firearm Control Processes

51031 Design Firearm Control Processes

510311

5103111

510311 2

5103113 Define design for proce

5103114

5103115

5103116

51031 17

5103118

5103119 Compile bUild specificalion

510312 Develop Retums build specification

5103121

5103122

5103123

5103124

5103125

5 iO~l 1 26

510313

5103131

5103132

1300

2006-04-13 2006-04-13

1 day

2006-04-18 2006-04-24 5 days

2006-04-25 2006-05-03 5 days

2006-05-04 2006-05-12 7 days

2006Q3-30 2006QSmiddot22 34 days

2006-03-30

2006-04-21 15 days 2006-04-24 bull 2006-04-25 20ays

middot

2006-04-26 2006-05-04 5 days

middot 2006-05-05 2005-05-11 5 days 2006-05-12 2006-05-22 7 days middot 2006-05middot17 2006Q9-27 96 days

2006-05-17 2006-06-06 15 days

2006-06-07 2006-06-20 10 days

2006-06-21 2006-07 -04 10 days

2006-07-05 2006-07-18 10 da~s

200G-O-19 2000-08-01 10 deys

2006-08-02 2006-08-08 6 days

2006middot07-27 2006~O8-30 25 days

2006-08-31 2006-09-13 10 days

2006-09-14 2006-09-27 10 days

2006-09-14 2006~09-27 10 days

2006Q3-30 2006Q9-26 125 days

2006Q3-30 2006Qa-29 105 days

2006-03middot30 2006Q4-21 15 days

2006-03-30 2006-04-21 15 days

2006-03-30 2006-04-21 15 days

2006-0330 2006-04-21 15 days

2006-04-21 15 days

2006-03-30 2006-04-21 15 days

2006-03-30 2000middot04-21 15 day

2006-03-30 middot 2006-04-21 15 days

2006-03lt30 2006-04~21 15 days

2006-03middot3( 2006-04-21 15 days

2006Q4-13 2006middot05Q2 10 days

2006-04-13 2000-05-02 10 aays

2006-04-13 2006middot05-02 10 days

2006-05~02 10 days

2006-04-13 middot 2006-0S-02 10 days

2Q06-04-13 2006-05-02 10 days

2006-04-13 2006-05-02 10 days

2006-04-24 2006-05-16 15 days

2006-04-24 2006-05-16 15 days

2006-04-24 I I~~

2006-04-24

Proiet Co)fiden

Firearms Control System Project Schedule Project Confidential FCSProjectSchedule Revislon200602031da

Develop licensing amp inspections build speCification

Define design for process application for licence to po

Define design for process application for licence to can

application for licence to deal

Define design for process application for licence to mar 2006-03-30

Define design for change commerCial agent premises

Define deSign for performAaministrate inspectton of de

Define design for periormAdminntrate inspection of gUJ

Define design for perforrnlAdmlOisrrate inspection of me

Define design for Manag relurns

Define design for Introduce firearm into SA legal firearrr

Define design for Inlroduce ammunition into SA (Import 2006-04-13

Deline design for Process application for acyuisilion by

Define design for Maintain official institution I egister

Compile Define design for specification

Develop ImportlExportiln transiU Transport Oefine desig

Define deSign for process application for permit lt0 Impo

Define deSign for Procesb _~ppllcation tor multiple impof 2006-04middotmiddot24

Deline design for Process applicatioo for multiple impor

Define design for Process application for multiple impor

37

5103138

5103139

51031310

5103U11

51031312

51031313

51031314

51031315

51031316

510314

5103141

51031 42

5103143

510314 4

510314 5

5103_ Ui

3151

51031S2

5103153

510_316

510j161

5103162

5)03163

510317

~103171

5103172

5103 3

5103114

5103175

5103U6

5103177

5103178

5103179

51031710

51031711

51031712

510 31713

51031714

510318

5103181

5103182

5103183

503184

5103185

Define design for Process application for temporary im 2006-04-24 2006-05-16 15 days

Define design for Process application for temporary im 2006-04-24 2006-05-16 15 days

Define design for Process application for permit to carr 2006-04middot24 2006-05-16 15 days middot middot Define design for Process application for permit to carr 2006-04-24 2006-05-16 15 days middot Define deSign for Process application for permit to carr 2006-04-24 2006-05-16 15 days

Define design for Transit firearm through SA 2006-04-24 2006-05-16 15 days

Deline design for Physically export firearms 2006-04-24 2006-05-16 15 days

Define design for Physically export ammunition 2006-04-24 2006-05-16 15 days middot middot DeflOe design for Conlrol firearm item storage at border 2006-04-24 2006-05-16 15 days middotmiddot Compile build specification 2006-04-24 2006-05-16 15 days

Oevelop Temporary Authorisation build speCification 2006-05middot10 middot 2006~5-23 10 days

Define design for Process application for a temporary a 2006-05-10 2006-05-23 10 days

Define deSign for Process application for temporary aut 2006-05-10 2006-05-23 10 days

Define design for Process application for temporary lice 2006-05-10 2006-05-23 10 days

Define deSign for Process application tor a lemporary a 2006-05-10 2006-05-23 10 days

Compile build specIfication 2006-05-10 2006-05-23 10 days

Develop Permits Oefine design for specification 2006~5-17 2006-05-30 10 days

Define design for Process applicallon for permit 10 colle 2006middot05 middot17 200605-30 10 days

Define design for Process application for permit 10 tram 2006-05-17 middot 2006-05-30 10 days

Compile build specificalion 2006-05-17 middot 2006-05-30 10 days

Develop Appeals Define dsgn for specificallon 2006~5-24 2006~6~6 10 days

Define design far Manage Appeal 2006-05middot24 2006-06-06 10 days

Define design for Process Appeal 2006-05-24 2006-06-06 10 days

Compile build speCification 2006-05-24 2006-06-06 10 days

Develop Notification build specification 2006-05-31 2006~6-20 15 days

Define deSign for Declare firearm free zone 2006-05-31 2006-06-20 15 days

Define design for Update Central Firearms Register will 2006-05-31 2006-06-20 15 days

Define design for Update Central Firearms Register witl 2006-05-31 middot 2006-06-20 15 days

Define design for Update Central Firearms Registerwltl 2006-05-31 2006-06-20 15 days

Define design for Updale manufaclurer licence with ne 2006-05-31 2006-0620 15 days

Define design for Process nolification of alteration done 2006-05-31 2006-06-20 15 days

Define design for Process request 10 alief firearm 2006-05-31 2006-06-20 15 days

Define design for Manage information on annual report 2006-05middot31 2006-06-20 15 days

Define design for Up dale central firearm register with nl 2006middot05-31 2006-06-20 15 days

Define design fOi Process notification of lasUstolenldef 2006-05-31 2006-06-20 15 days

Define design for Inform registrar that executoradmlflisl 2006-05middot31 2006-06-20 15 days

Define design for Inform regislrar of progress that has b 2006-05-31 2006-06-20 15 days

Define design for Ensure Ihal all firearms possessed or 200605-31 2006-06-20 15 days

(ompile build speCifIcation 2006-05-31 2006-06-20 i5 days

15 days

Develop Renewals build specification 2006~6-14 2006-07-ltl4 15 days

Define design for Apply for firearm warrant renewal that 2006-0614 2006-07-04 15 d8yS

Define design for Apply for firearm warrant renewal that 2006-06-14 200S()7-04 15 days

Define design for Apply for firearm warrant renewal thatmiddot 2006-06-14 200607-04 15 days

Defina deSign for Apply for firearm warrant renewal that 2006-06-14 2006-07-04 15 days

Define design for Apply for firearm warrant renewal at C 2006-06-14 7006-01-04 15 days

PrO)eel Confidenlai 9 of 25 Vfsion 40

Project Confidential FCSProjectSchedule-Revlsion20060203fda

Task Name

460

46i7 462

463

5103188

5103189

51031810

51031811

51031812

51031813

510 31814

51031815

51031816

51031817

51031618

51031819

51031820

51031821

51031822

51031823

5103_19

510319

5103192

5103193

5103194

5103195

5103196

5103197

5103198

5103199

51031910

510319

5103110

5103 1101

51031102

51031103

51031104

51031 105

51031106

51031107

51031108

5103110 9

510311010

510311011

510311012

510311013

510311014

510311015

Define design for Decide whether llcerice to posses-- I

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whelher licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether commercial agent lie 2006-06-14

Define design for Decide whether permit to possess am 2006-06-14

Define design for Decide whether Import permit may be 2006-06-14

Define design for Decide whether export permit may be 2006-06-14

Define design for Decide whether in-transit permit may I 2006-06-14

Define design for Decide whether firearm transport perr 2006-06-14

Define design for Decide whether temporary authorisati 2006-06-14

Define deSign for Approve firearm warrant renewat appl 2006-06-14

Define design for Refuse firearm warrant renewal appli 2006-06-14

Define design for Assess applicallon for Iransitional ren 2006-06-14

Define design for Issue renewed firearm warrant 2006-06-14

Compile build specification 2006-06-14

Develop Duplication (replacements) build specification 2006-06-28

Define design for Replace commercral agent licence 2006-06-28

Define design for Replace compelency certlficale 2006-06-28

Define deSign for Replace transpor1 permit 2006-06-28

Define design for Replace licence to possess 2006-06-28

Define design for Replace expor1 permit 2006-06-28

Define design for Replace ammunition collection permit 2006-06-28

Define design for Replace temporary authOrisation 2006-06-28

Define design for Replace impor1 permit 2006-06-28

Define design for Replace accreditation certiflcale 2006-06-28

Define design for Replace in-transit permit 2006-06-28

Compile build specificalion 2006-06-28

Develop Cancellation amp Suspension build speclllcalJon 2006-07-05

Define design for Regislrar determines whether person 2006-07-05

Define design for Decide persons fitness to possess a I 2006-07-05

Define design for Finalise registrars deCision that perslt 2006-07-05

Define design for Finalise registrars deCision that perse 2006-07-05

Define design for Inform registrar and Irwestlgaling offie 2006-07-05

Define design for Finalise unfitness status of person wh 2006-07-05

Define design for Process cancelled licence to possess 2006-07-05

Defina design for Process Cancelled import permit 2006-07-05

Define design for Process cancelled commercial agent I 2006-07-05

Define design for Process cancelled temporary authoris 2006-07-05

Define design for Process cancelled in-transit permit 2006-07-05

Define design for Ensure that cancelled export permit is 2006-07-05

Define deSign for Ensure that cancelled transport permi 2006-07middot05

Define design for Inform registrar of ceasing to carry on 2006-07 -05

Define design for ReconCile warrant holders list of paS 2006-07-05

Define desian for Reverse unfit persons unfitness statu 2006-07-05

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07middot25

2006-07-25

15days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

10 days

10 days

10 days

10days

10 days

10 days

10 days

10 days

10 days

10 days

10 days

10 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

I

I

U~___ __j __ __ j

10 of

37

5103138

5103139

51031310

5103U11

51031312

51031313

51031314

51031315

51031316

510314

5103141

51031 42

5103143

510314 4

510314 5

5103_ Ui

3151

51031S2

5103153

510_316

510j161

5103162

5)03163

510317

~103171

5103172

5103 3

5103114

5103175

5103U6

5103177

5103178

5103179

51031710

51031711

51031712

510 31713

51031714

510318

5103181

5103182

5103183

503184

5103185

Define design for Process application for temporary im 2006-04-24 2006-05-16 15 days

Define design for Process application for temporary im 2006-04-24 2006-05-16 15 days

Define design for Process application for permit to carr 2006-04middot24 2006-05-16 15 days middot middot Define design for Process application for permit to carr 2006-04-24 2006-05-16 15 days middot Define deSign for Process application for permit to carr 2006-04-24 2006-05-16 15 days

Define design for Transit firearm through SA 2006-04-24 2006-05-16 15 days

Deline design for Physically export firearms 2006-04-24 2006-05-16 15 days

Define design for Physically export ammunition 2006-04-24 2006-05-16 15 days middot middot DeflOe design for Conlrol firearm item storage at border 2006-04-24 2006-05-16 15 days middotmiddot Compile build specification 2006-04-24 2006-05-16 15 days

Oevelop Temporary Authorisation build speCification 2006-05middot10 middot 2006~5-23 10 days

Define design for Process application for a temporary a 2006-05-10 2006-05-23 10 days

Define deSign for Process application for temporary aut 2006-05-10 2006-05-23 10 days

Define design for Process application for temporary lice 2006-05-10 2006-05-23 10 days

Define deSign for Process application tor a lemporary a 2006-05-10 2006-05-23 10 days

Compile build specIfication 2006-05-10 2006-05-23 10 days

Develop Permits Oefine design for specification 2006~5-17 2006-05-30 10 days

Define design for Process applicallon for permit 10 colle 2006middot05 middot17 200605-30 10 days

Define design for Process application for permit 10 tram 2006-05-17 middot 2006-05-30 10 days

Compile build specificalion 2006-05-17 middot 2006-05-30 10 days

Develop Appeals Define dsgn for specificallon 2006~5-24 2006~6~6 10 days

Define design far Manage Appeal 2006-05middot24 2006-06-06 10 days

Define design for Process Appeal 2006-05-24 2006-06-06 10 days

Compile build speCification 2006-05-24 2006-06-06 10 days

Develop Notification build specification 2006-05-31 2006~6-20 15 days

Define deSign for Declare firearm free zone 2006-05-31 2006-06-20 15 days

Define design for Update Central Firearms Register will 2006-05-31 2006-06-20 15 days

Define design for Update Central Firearms Register witl 2006-05-31 middot 2006-06-20 15 days

Define design for Update Central Firearms Registerwltl 2006-05-31 2006-06-20 15 days

Define design for Updale manufaclurer licence with ne 2006-05-31 2006-0620 15 days

Define design for Process nolification of alteration done 2006-05-31 2006-06-20 15 days

Define design for Process request 10 alief firearm 2006-05-31 2006-06-20 15 days

Define design for Manage information on annual report 2006-05middot31 2006-06-20 15 days

Define design for Up dale central firearm register with nl 2006middot05-31 2006-06-20 15 days

Define design fOi Process notification of lasUstolenldef 2006-05-31 2006-06-20 15 days

Define design for Inform registrar that executoradmlflisl 2006-05middot31 2006-06-20 15 days

Define design for Inform regislrar of progress that has b 2006-05-31 2006-06-20 15 days

Define design for Ensure Ihal all firearms possessed or 200605-31 2006-06-20 15 days

(ompile build speCifIcation 2006-05-31 2006-06-20 i5 days

15 days

Develop Renewals build specification 2006~6-14 2006-07-ltl4 15 days

Define design for Apply for firearm warrant renewal that 2006-0614 2006-07-04 15 d8yS

Define design for Apply for firearm warrant renewal that 2006-06-14 200S()7-04 15 days

Define design for Apply for firearm warrant renewal thatmiddot 2006-06-14 200607-04 15 days

Defina deSign for Apply for firearm warrant renewal that 2006-06-14 2006-07-04 15 days

Define design for Apply for firearm warrant renewal at C 2006-06-14 7006-01-04 15 days

PrO)eel Confidenlai 9 of 25 Vfsion 40

Project Confidential FCSProjectSchedule-Revlsion20060203fda

Task Name

460

46i7 462

463

5103188

5103189

51031810

51031811

51031812

51031813

510 31814

51031815

51031816

51031817

51031618

51031819

51031820

51031821

51031822

51031823

5103_19

510319

5103192

5103193

5103194

5103195

5103196

5103197

5103198

5103199

51031910

510319

5103110

5103 1101

51031102

51031103

51031104

51031 105

51031106

51031107

51031108

5103110 9

510311010

510311011

510311012

510311013

510311014

510311015

Define design for Decide whether llcerice to posses-- I

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whelher licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether commercial agent lie 2006-06-14

Define design for Decide whether permit to possess am 2006-06-14

Define design for Decide whether Import permit may be 2006-06-14

Define design for Decide whether export permit may be 2006-06-14

Define design for Decide whether in-transit permit may I 2006-06-14

Define design for Decide whether firearm transport perr 2006-06-14

Define design for Decide whether temporary authorisati 2006-06-14

Define deSign for Approve firearm warrant renewat appl 2006-06-14

Define design for Refuse firearm warrant renewal appli 2006-06-14

Define design for Assess applicallon for Iransitional ren 2006-06-14

Define design for Issue renewed firearm warrant 2006-06-14

Compile build specification 2006-06-14

Develop Duplication (replacements) build specification 2006-06-28

Define design for Replace commercral agent licence 2006-06-28

Define design for Replace compelency certlficale 2006-06-28

Define deSign for Replace transpor1 permit 2006-06-28

Define design for Replace licence to possess 2006-06-28

Define design for Replace expor1 permit 2006-06-28

Define design for Replace ammunition collection permit 2006-06-28

Define design for Replace temporary authOrisation 2006-06-28

Define design for Replace impor1 permit 2006-06-28

Define design for Replace accreditation certiflcale 2006-06-28

Define design for Replace in-transit permit 2006-06-28

Compile build specificalion 2006-06-28

Develop Cancellation amp Suspension build speclllcalJon 2006-07-05

Define design for Regislrar determines whether person 2006-07-05

Define design for Decide persons fitness to possess a I 2006-07-05

Define design for Finalise registrars deCision that perslt 2006-07-05

Define design for Finalise registrars deCision that perse 2006-07-05

Define design for Inform registrar and Irwestlgaling offie 2006-07-05

Define design for Finalise unfitness status of person wh 2006-07-05

Define design for Process cancelled licence to possess 2006-07-05

Defina design for Process Cancelled import permit 2006-07-05

Define design for Process cancelled commercial agent I 2006-07-05

Define design for Process cancelled temporary authoris 2006-07-05

Define design for Process cancelled in-transit permit 2006-07-05

Define design for Ensure that cancelled export permit is 2006-07-05

Define deSign for Ensure that cancelled transport permi 2006-07middot05

Define design for Inform registrar of ceasing to carry on 2006-07 -05

Define design for ReconCile warrant holders list of paS 2006-07-05

Define desian for Reverse unfit persons unfitness statu 2006-07-05

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07middot25

2006-07-25

15days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

10 days

10 days

10 days

10days

10 days

10 days

10 days

10 days

10 days

10 days

10 days

10 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

I

I

U~___ __j __ __ j

10 of

Project Confidential FCSProjectSchedule-Revlsion20060203fda

Task Name

460

46i7 462

463

5103188

5103189

51031810

51031811

51031812

51031813

510 31814

51031815

51031816

51031817

51031618

51031819

51031820

51031821

51031822

51031823

5103_19

510319

5103192

5103193

5103194

5103195

5103196

5103197

5103198

5103199

51031910

510319

5103110

5103 1101

51031102

51031103

51031104

51031 105

51031106

51031107

51031108

5103110 9

510311010

510311011

510311012

510311013

510311014

510311015

Define design for Decide whether llcerice to posses-- I

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whelher licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether licence to possess a I 2006-06-14

Define design for Decide whether commercial agent lie 2006-06-14

Define design for Decide whether permit to possess am 2006-06-14

Define design for Decide whether Import permit may be 2006-06-14

Define design for Decide whether export permit may be 2006-06-14

Define design for Decide whether in-transit permit may I 2006-06-14

Define design for Decide whether firearm transport perr 2006-06-14

Define design for Decide whether temporary authorisati 2006-06-14

Define deSign for Approve firearm warrant renewat appl 2006-06-14

Define design for Refuse firearm warrant renewal appli 2006-06-14

Define design for Assess applicallon for Iransitional ren 2006-06-14

Define design for Issue renewed firearm warrant 2006-06-14

Compile build specification 2006-06-14

Develop Duplication (replacements) build specification 2006-06-28

Define design for Replace commercral agent licence 2006-06-28

Define design for Replace compelency certlficale 2006-06-28

Define deSign for Replace transpor1 permit 2006-06-28

Define design for Replace licence to possess 2006-06-28

Define design for Replace expor1 permit 2006-06-28

Define design for Replace ammunition collection permit 2006-06-28

Define design for Replace temporary authOrisation 2006-06-28

Define design for Replace impor1 permit 2006-06-28

Define design for Replace accreditation certiflcale 2006-06-28

Define design for Replace in-transit permit 2006-06-28

Compile build specificalion 2006-06-28

Develop Cancellation amp Suspension build speclllcalJon 2006-07-05

Define design for Regislrar determines whether person 2006-07-05

Define design for Decide persons fitness to possess a I 2006-07-05

Define design for Finalise registrars deCision that perslt 2006-07-05

Define design for Finalise registrars deCision that perse 2006-07-05

Define design for Inform registrar and Irwestlgaling offie 2006-07-05

Define design for Finalise unfitness status of person wh 2006-07-05

Define design for Process cancelled licence to possess 2006-07-05

Defina design for Process Cancelled import permit 2006-07-05

Define design for Process cancelled commercial agent I 2006-07-05

Define design for Process cancelled temporary authoris 2006-07-05

Define design for Process cancelled in-transit permit 2006-07-05

Define design for Ensure that cancelled export permit is 2006-07-05

Define deSign for Ensure that cancelled transport permi 2006-07middot05

Define design for Inform registrar of ceasing to carry on 2006-07 -05

Define design for ReconCile warrant holders list of paS 2006-07-05

Define desian for Reverse unfit persons unfitness statu 2006-07-05

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-04

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-11

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07-25

2006-07middot25

2006-07-25

15days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

10 days

10 days

10 days

10days

10 days

10 days

10 days

10 days

10 days

10 days

10 days

10 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

15 days

I

I

U~___ __j __ __ j

10 of

15 days

510311020 Define design for lift suspension of firearm warrant 2006-07-05 2006-07-25 15 days

510311021 Define design for Re-instae suspended license to pass 2006-07-05 2006-07-25 15 days

510311022 Compile build specification 2006-07-25 15 days

5103111 Develop Surrendering build specification 2006-07middot19 2006-06-01 10 days

51031111 Define design for Surrender commercial agent warrant 2006-07-19 2006-08-01 10 days

51031112 Define design for Surrender non-commercral agent wan 2006-07-19 2006-08-01 10 days I 51031113 Define design for Process surrendering of firearm item 2006-07-19 2006-08-01 10 days

51031114 Definedesign for Seize firearm related anifacls possesmiddot 2006-07-19 middot 2006-08-01 10 days

51031115 Define design for Place flrearmsfirearm pans and amm 2006-07-19 2006-08-01 10 days

51031116 Define design for Manage surrendered commercial age 2006-07-19 2006-08-01 10 days

51031117 Define design for Process surrendering of firearm ilem 2006-07-19 2006-08-01 10 days

51031118 Define design for Ensure that ffrearm tems are dispose 2006-07-19 2006-08-01 10 days

51031119 Define desrgn for Dispose all firearm items possessed t 2006-07 -19 2006-08-01 10 days

Define deSign for Ensure thai all firearms and flrearm w 2006-07-19 2006-08-01 10 days

Detine design for Dispose of all firearm Ilems in Ihe esl 2006-07-19 2006-06-01 10 days

Compile build specification 2006-07-19 2006-08-01 10 days

5103112 Develop Lost and Found build specification 2006-0726 2006-06-08 10 days

51031121 Define design for Manage losl or slolen firearm item pre 2006-07-26 2006-06-06 10 days

51031122 Define design for Manage found firearm item process 2006-07-26 2006-06-06 10 days

51031123 Compile Define design for specification 2006-07-26 2006-08-08 10 days

5103113 Develop Deactivation amp destruction Define design for Bp 2006-08-02 2006-06middot15 10 days

5103131 Define design for Dispose of FIA ilem (Remove from SP 2006-08-02 2006-08-15 10 days

5103132 Define design for Deaclivate Firearms 2006-08-02 2006-08-15 10 days

5103133 Compile Define design for specification 2006-08-02 2006-08-15 10 days

5103114 Develop Compensation Define design for specification 2006-08-09 bull 2006-08middot22 10 days

51031141 Define design for Process applrcation lor campensatron 2006-08-09 middot 2006-08-22 10 days

51031142 Define design for Process change of bank delall notific 2006-08-09 2006-08-22 10 days

5103 1143 Compile Define deSign for specification 2006-OB~09 2006-08-22 10 days

5103115 Develop Fines Define design for specification 2006-08-16 2006-08-29 10 days

51031151 Define deSign for Issue administrative fine 2006-08-16 2006-08-29 10 days

51031152 Define design for Process response to administrative fir 2006-08-16 2006-08-29 10 days

51031 153 Compile Define deSign for specification 2006-08middot16 2006-08-29 10 days

5103116 Develop System Administration Define design for speclf 2006-08-23 2006-08middot29 5 days

51031161 Define design for Maintain firearms control system user 2006-08-23 2006-08-29 5 days

51031162 Define design for Maintain firearms control system user 2006-08-23 2006-08-29 5 days

51031163 Define design for Manage systern and hardware problol 2006-08-23 2006-08-29

51031 164 Define design for Manage user request for syslem sorv 2006-08-23 2006-08-29 51031165 Compile Define design for specification 2006-08-23 2006-0829

Develop Administration Support Define design for specl 2006-0823 2006-08-29

Define deSign for Mainlaln firearms control system user 2006-08-23 2006-08-29

Define design for Maintain firearms control system user 2006-08-23 2006-08-29

Define design for Manage system and hardware proble 2006-08-23 2006-08-29

Define design for Manage user request for system servr 2006-0823 2006-08-29

Compile build specification 2006-08-23 2006-08-29 ----------1 I U-RLiILI LlI LLI ~_~_L__I__~~

11 of 25

------

510321

Processes

5103211 Refine software for Process application for a further cor 2006middot05middot18

5103212 Refine software for Process application for a compelenlt 2006-05middot18

5103213 Refine software for Process application for accreditatior 2006-05-18

5103214 Refine software for Process application for accreditatior 2006-05-18

5103215 Refine software for Process application for accreditatior 2006-05-18

510323 Licensing amp Inspections 2006-05-03 5103231 Build Process application for licence to possess a firear 2006-05-03

5103232 Build Process application for licence to conduct busine 2006middot05-03

5103233 Build Process application for licence to deal In firearms 2006-05-03

5103234 Build process application for licence to manufacture fire 2006-05-03

5103235 Build Change commercial agent premises 2006-05-03

5103236 BUild PerformiAdministrate inspection of dealer 2006-05-03

5103237 BUild PerformAdministrate inspection of gunsmith 2006-05-03

5103238 Build PerformAdministrate inspection of manufacturer 2006-05-03

510323 Returns 2006-05-03

5103231 Build Manage returns 2006-05-03

5103232 Build Introduce firearm into SA legal firearm environmel 2006-05-03

5103233 Build Introduce ammunition into SA (Imports and manuf 2006-05-03

5103234 Build Process application for acquisition by official instit 2006-05-03

5103235 Build Maintain offiCIal institution register 2006-05-03

510324 ImportJExportJln transit) Transport 2006-05-17

5103241 Build Process application for permit to import firearms a 2006-05-17

510 3242 Build Process application for multiple import and export 2006-05-17

5103243 Build Process application for multiple import and export 2006-05-17

510324 4 Build Process application for multiple import and export 2006-05-17

510324 5 Build Process application for permit to export firearms a 2006-05-17

5103246 Build Process application for temporary import and exp 2006-05-17

510324 7 Build Process application for temporary import and exp 2006middot05-17

5103J48 Build Process application for temporary import and exp 2006-05-17

5103249 Build Process application for permil to carry firearms an 2006-05-17

51032410 Build Process application for permit to carry firearms an 2006-05-17

51032411 Build Process application for permit to carry firearms an 2006-05-17

51032412 Build Transit firearm through SA 2006-05-17

510324 13 Build PhYSically export firearms 2006-05-17

51032414 BUild PhySically export ammunition 2006-05-17

510324 15 Build Control firearm item storage at border post 2006-05-17

510325 Temporary Authorisation 2006-06-07

5103251 Build Process application for a lemporary authorisation 2006-06-07

5103252 Build Process application for temporary authorisation to 2006-06-07

5103253 Build Process application for temporary licence to displ 2006-06-07

5103254 Build Process application for a temporary authorisation 2006-06-07

510326 Pennits 2006-05-31 5103261 BUild Process application for permit to collect ammuniti 2006-05-31

5103262 Build Process application for permit to transport firearm 2006-05-31

510327 Appeals 2006-06-07

2006middot06-08

2006middot06-08 2006-06-08

2006-06-08

2006-06-08

15 days

15 days

15 days

15 days

15 days

2006-06-06

2006-06-06

25 days

25 days

2006-06-06 25 days

2006-06middot06

2006-06-06

2006-06-06

25 days

25 days

25 days

2006-06-06

2006-06-06

2006-06-06

2006-06-06

2006-05-30

25 days

25 days

25 days

25 days

20 days

2006-06-06 25 days

2006-06-06

middot 2006-06-06

25 days

25 days

2006middot06-06

2006-06-20

2006-06middot20

2006-06-20

25 days

25 day

25 days

25 days

middot 2006-06-20 25 days

2006middot06-20 25 days

2006-06-20 25 days

2006-06-20 25 days

2006-06-20

2006-06-20

25 days

25 days

middot 2006-06-20 25 days

2006-06-20

2006-06-20

2006middot06-20

25 days

25 days

25 days

2006middot06-20

2006-06-20

2006-06-20

2006-06-27

25 days

25 days

25 days

15 days

2006-06-27 15 days

2006-06-27

2006-06-27 15 days

15 days

2006-06-27

2006-06-13

2006-06-13

2006-06middot13

2006-07-04

15 days

10 days

10 days

10 days

20 days

Project Confidenl1al Version 40

12 of 25

Project Confidential FCSProjectScedule-Revislon200G0203fda

Build Replace import permit

Build Replace accreditation certificate 200607-12 2006-0801 15 days

Build Replace in-transit permit 2006-07-12 200608-01 15 days

Cancellation amp Suspension 2006-07middot26 2006-08middot29 25 days

Build Registrar determines whether person is unfit to pc i 20Q60726 2006-08-29 25 days

51032 112 Build Decide persons fitness to possess a firearm in co 2006-07-26 200608-29 25 days

5103211 3 Build Finalise registrars decision that person is fll to po 2006-07-26 2006middot08middot29 25 days

51032114 Build Finalise registrars decision that person is unfll to 2006-07-26 2006-08-29 25 days

51032115 Build Inform registrar and investigating officer of decislc 2006-07-26 2006-08middot29 25 days

51032116 Build Finalise unfitness status of person who becomes I 200607-26 2006middot08-29 25 days

51032117 Build Process cancelled licence to possess a firearm 2006-07middot26 2006-08-29 25 days

51032118 BUIld Process Cancelled import perml 2006-07-26 2006-08-29 25 days

51032119 Build Process cancelled commercial agenl licence 200607-26 2006middot08-29 25 days i 510321110 Build Process cancelled temporary authOrisation 10 pos 2006-07-26 2006-08-29 25 days

510 321111 Build Process cancelled in-transit permit 2006-07-26 2006-08-29 25 days

510321112 Build Ensure that cancelled export permit is surrenderel 2006-07-26 2006-08middot29 25 days

510 113 Build Ensure that cancelled transport permit is surrendE 2006-07-26 2006-08-29 25 days

510321114 Build Inform reglslrar of ceasing 10 carry on bUSiness 200607middot26 2006middot08-29 25 days I 510321115 Build Reconcile warrant holders hst 01 possed firearms 2006-07-26 200608middotmiddot29 25 days

510321116 Build Reverse unfit personls unfitness status 2006-07middot26 2006-08-29 25 days

510321117 Build Suspend firearm warrant for more than 7 days 2006middot07-26 2006-08-29 25 days

510321118 Build Suspend Firearm Warranl due to suspected offen 2006-07-26 2006-08-29 25 days

510321119 Build Suspend Firearm authorising lost or stolen lirearrr 2006-0726 2006-08-29 ~5 days

510321120 BUild Lift suspension of firearm warrant 2006-07-26 2006-08-29 ~5 days

510321121 Build Remiddotinstate suspended license to possess a firearr 2006-07-26 2006-08-29 25 days

5103212 Surrendering 2006-08-02 2006-08middot29 20 days

sf0_32121 Build Surrender commercia agent warrant 2006-08-02 2006-08-29 20 days

510_32122 Build Surrender non-commercial agenl warrant 2006-0802 2006-08-29 20 days 51032123 Build Process surrendering of firearm item 200608-02 2006-08-29 20 days I

51032124 Build Seize firearm related artifacts possessed by perse 2006-08-02middot 2006-08-29

20 days I 51032125 Build Place flrearmsfirearm parts and ammunition in sa 2006middot0802 2006-08-29 20 days

510 Build Manage surrendered commerCial agent regISters 200608middot02 2006-08middot29 20 days

51032127 Build Process surrendering of firearm item 2006middot08-02 2006-08-29 20 days

51032128 Build Ensure that firearm items are dISposed of within a 2006-08-02 2008-06-29 20 days

51032129 Build Dispose all firearm items possessed by involved 2008-08-02 2006-08-29 20 days

510321210 Build Ensure that all firearms and firearm warrants in tho 2006middot08-02 2006-08-29 20 days

510321211 BUIld Dispose of all firearm Items n the estate of the fin 200606-02 2006-08-29 20 days

51032_13 Lost and Found 2006-08-09 2006-08middot22 10 days

510 32131 Build Manage lost or stolen firearm item process 2006-08-09 200608-22 10 days

51032132 Build Manage found firearm item process 2006-08middot09 2006-08-22 10 days

5103214 Deactivation amp destruction 2006-08-23 2006middot09-05 10 days

51032141 Build Dispose of FA item (Remove from SA environmel 2006-08-23 2006-09-05 1G days

51032142 Build Deactivate Firearms 2006-08middot23 2006-09-05 10 days

51032_15 Compensation 2006-08middot23 2006-09-05 10 days

51032151 Build Process applicallon for compensation 2006-08middot23 2006-09-05 10 days

51032152 Build Process change of bank delail nollficalion 2006-08-23 2006-09-05 0 days

5103216 Fines

I

14 of 25 I

Project Confidential FCSProjectScedule-Revislon200G0203fda

Build Replace import permit

Build Replace accreditation certificate 200607-12 2006-0801 15 days

Build Replace in-transit permit 2006-07-12 200608-01 15 days

Cancellation amp Suspension 2006-07middot26 2006-08middot29 25 days

Build Registrar determines whether person is unfit to pc i 20Q60726 2006-08-29 25 days

51032 112 Build Decide persons fitness to possess a firearm in co 2006-07-26 200608-29 25 days

5103211 3 Build Finalise registrars decision that person is fll to po 2006-07-26 2006middot08middot29 25 days

51032114 Build Finalise registrars decision that person is unfll to 2006-07-26 2006-08-29 25 days

51032115 Build Inform registrar and investigating officer of decislc 2006-07-26 2006-08middot29 25 days

51032116 Build Finalise unfitness status of person who becomes I 200607-26 2006middot08-29 25 days

51032117 Build Process cancelled licence to possess a firearm 2006-07middot26 2006-08-29 25 days

51032118 BUIld Process Cancelled import perml 2006-07-26 2006-08-29 25 days

51032119 Build Process cancelled commercial agenl licence 200607-26 2006middot08-29 25 days i 510321110 Build Process cancelled temporary authOrisation 10 pos 2006-07-26 2006-08-29 25 days

510 321111 Build Process cancelled in-transit permit 2006-07-26 2006-08-29 25 days

510321112 Build Ensure that cancelled export permit is surrenderel 2006-07-26 2006-08middot29 25 days

510 113 Build Ensure that cancelled transport permit is surrendE 2006-07-26 2006-08-29 25 days

510321114 Build Inform reglslrar of ceasing 10 carry on bUSiness 200607middot26 2006middot08-29 25 days I 510321115 Build Reconcile warrant holders hst 01 possed firearms 2006-07-26 200608middotmiddot29 25 days

510321116 Build Reverse unfit personls unfitness status 2006-07middot26 2006-08-29 25 days

510321117 Build Suspend firearm warrant for more than 7 days 2006middot07-26 2006-08-29 25 days

510321118 Build Suspend Firearm Warranl due to suspected offen 2006-07-26 2006-08-29 25 days

510321119 Build Suspend Firearm authorising lost or stolen lirearrr 2006-0726 2006-08-29 ~5 days

510321120 BUild Lift suspension of firearm warrant 2006-07-26 2006-08-29 ~5 days

510321121 Build Remiddotinstate suspended license to possess a firearr 2006-07-26 2006-08-29 25 days

5103212 Surrendering 2006-08-02 2006-08middot29 20 days

sf0_32121 Build Surrender commercia agent warrant 2006-08-02 2006-08-29 20 days

510_32122 Build Surrender non-commercial agenl warrant 2006-0802 2006-08-29 20 days 51032123 Build Process surrendering of firearm item 200608-02 2006-08-29 20 days I

51032124 Build Seize firearm related artifacts possessed by perse 2006-08-02middot 2006-08-29

20 days I 51032125 Build Place flrearmsfirearm parts and ammunition in sa 2006middot0802 2006-08-29 20 days

510 Build Manage surrendered commerCial agent regISters 200608middot02 2006-08middot29 20 days

51032127 Build Process surrendering of firearm item 2006middot08-02 2006-08-29 20 days

51032128 Build Ensure that firearm items are dISposed of within a 2006-08-02 2008-06-29 20 days

51032129 Build Dispose all firearm items possessed by involved 2008-08-02 2006-08-29 20 days

510321210 Build Ensure that all firearms and firearm warrants in tho 2006middot08-02 2006-08-29 20 days

510321211 BUIld Dispose of all firearm Items n the estate of the fin 200606-02 2006-08-29 20 days

51032_13 Lost and Found 2006-08-09 2006-08middot22 10 days

510 32131 Build Manage lost or stolen firearm item process 2006-08-09 200608-22 10 days

51032132 Build Manage found firearm item process 2006-08middot09 2006-08-22 10 days

5103214 Deactivation amp destruction 2006-08-23 2006middot09-05 10 days

51032141 Build Dispose of FA item (Remove from SA environmel 2006-08-23 2006-09-05 1G days

51032142 Build Deactivate Firearms 2006-08middot23 2006-09-05 10 days

51032_15 Compensation 2006-08middot23 2006-09-05 10 days

51032151 Build Process applicallon for compensation 2006-08middot23 2006-09-05 10 days

51032152 Build Process change of bank delail nollficalion 2006-08-23 2006-09-05 0 days

5103216 Fines

I

14 of 25 I

--

2006middot06middot30

200608middot30

200608middot30

20060830

2006Q8middot30

2006middot08middot30

2006middot08--30

200608middot30

2006middot08middot30

2006Q7middot13

2006Q7middot13

20060905 5 days

2006~09~O5 5 days

200609middot05 5 days

2006-09middot05 Sdays

200609-05 S days

2006Q9o5 5 days

200609middot05 5 days

200609middot05 5 days

200609middot26 5375 days

200607middot20 6 days

200607middot20 5 days

1middot

1

1middot

F rearms Controt System Project Schedule PrOject Confidential

10

5103217

51032171

tlldme

51032172

51032173

51032174

5103218

51032181

668 51032182

669 51033

510331

5103311

5103312

5103313

5103314

5103315

510332

5103321

5103322

5103323

5103324

681 5103325

682 5103326

653 5103327

684 5103328 - 685-~~

510333

5103331

5103332

5103333

5103334

510333S

510$34

5103341

5103342

5103343

5103344

5103345

5103346

5103347

5103348

5103349

51033410

51033411

51033412

51033413

51033414

Build Issue administrative fine

Build Process response to administrative fine

System Administration

Build Maintain firearms conlrol system user

Build Maintain firearms control system user profile optic

Build Manage system and hardware problem

Build Manage user request for system sefce

Administration Support

Build Manage scanning of documenlatlon

Build Manage paper documents received al CFR for re

Review Buifd Specifications for Processes

Competency amp accredilatlon

Process application for a further competency certlficale 200607-13

Process application for a competency certificale

Process application for accreditation for business purpc

Process applicallon for accreditation as an official instlt

Process appljcation for accreditation as an association

Licensing amp Inspections

Process application for licence to possess a firearm

Process applicalion for licence to conduct business as

Process application for licence to deal in flfearms and a

Process appllcalion for licence to manufacture firearms

Change commercial agent premises

PerformAdministrate inspeclion of dealer

PerfonniAdministrate inspection of gunsmith

PerformAdministrale inspeclion of manufacturer

Returns

Manage returns

Introduce firearm into SA legal firearm environment (iml

Introduce arnmumtion inlo SA (Imports and manufactur

Process application for acquisition by official institution

Maintain official institution regIster

ImportExportIn transit Transport

Process application for permit to Import firearms and an

Process application for multiple import and export perm

Process application for multiple import and export perm

Process application for mUltiple import and export perm

Process applicalion for permit to export firearms and an 200607middot27

Process application for temporary import and export pel 2006middot07middot27

Process applicalion for temporary import and export pel 2006-07-27

Process applicallon for temporary import and export pel 200607-27

Process applicalion for permilio carry firearms and ami 200607middot27

Process application for permit to carry firearms and amr 200607-27

Process application for permt to carry firearms and am 200607middot27

Transit firearm through SA 2006middot07-27

Physically export firearms 2006middot07-27

Physically export ammUnilion 2006middot07middot27

200607middot13

2006-0713

2006-07-13

2006middot07-13

200607middot13

2006-07-13

2006-07middot13

2006middot07middot13

200607middot13

2006-07-13

2006~O7middot13

2006middot07middot13

2006middot07middot13

200607middot20

2Q06middot07middot20

2006middot07middot20

2006-07-20

2006-07middot20

2006-07-20

200607-27

2006-07-27

2006middot07middot27

200607middot27

2006middot07middot27

2006middot07middot20 5 days 2006middot07 -20 5 days 2006middot07 middot20 5 days 2006-07-20 5 days

200607middot20 5 day$ middot 2006middot07-20 5 days middot middot 2006-07-20 5 days middot 2006middot07middot20 5 days

2006middot07-20 5 days 2006-07middot20 5 days 2006middot07middot14 1 day 2006middot07-14 1 day 2006-07middot14 1 day

middot

200607middot27 5 days 2006middot07middot27 b days middot 2006middot07-27 5 days

2006-07-27 5 days

2006-07-27 5 days

2006middot07-27 E days

20060803 5 days

2006middot08-03 days

2006-08middot03 5 days

200608middot03 5 days

20060803 5 days 200606middot03 5 days 2006-0803 5 days middot 2006-0803 5 days 2006~08middot03 5 days

2006-08middot03 5 days

2006-08middot03 5 days

200608-03 5 days

2006-06middot03 5 days

2006-08middot03

2006-08-03

150f 25

Firearms ControlSyslem Pro)ecl Schedule Project Confidential FCSPfOlectSChedule-Revlslon20060203fda

Task Name

2006-07-13

5103351

5103352

5103353

5103354

510336

5103361

5103362

510337

5103371

5103372

5103_38

5103381

5103382

5103383

5103384

5103385

5103386

5103387

5103388

5103389 _

51033810

729 51033811

730 51033812

51033B13

732 510339

5103391

734 5103392

5103393

5103394

5103395

5103396

5103397

5103398

5103399

51033910

51033911

51033912

51033913

51033914

51033915

748 51033916

Process application fora temporary authorisation to cor 2006-07-13

Process application for temporary authorisation to passmiddot 2006-07-13

Process application for temporary licence to display fire 2006-07-13

Process application for a temporary authorisation to tra 2006-07-13

Permits 2006-07-13

Process application for permit to collect ammunition 2006-07-13

Process application for permit to transport firearms and 2006-07-13

Appeals 2006-07-13

Manage Appeal 2006-07-13

Process Appeal 2006-07-13

Notification 2006-07-26

Declare firearm free zone 2006-07-26

Update Central Firearms Register with change in circun 2006-07-26

Update Central Firearms Register with change In addre 2006-07-26

Update Central Firearms Register with COffect informali 2006middot07-26

Update manufacturer licence with new manufactured fip 2006-07-26

Process notification of alteration done to firearm bull 2006-07 -26

Process request to aller firearm 2006-07-26

Manage Information on annual report by accredited entl 2006-07-26

Update central firearm register with new responsible pe 2006-07-26

Process notification of loststolendefaced firearm warra 2006-oi-pound6 Inform registrar that executoradmimstratortrusteecura 2000-07-26

Inform registrar of progress thai has been made with th 2006-07-26

Ensure that all firearms possessed or registered on the 2006-07-26

Renewals 2006-08-09

Apply for firearm warrant renewal that requires paymenl 2006-08-09

Apply for firearm warrant renewal that does not require 2006-08-09

Apply for firearm warranl renewal that requires paymer 2006-08-09

Apply for firearm warrant renewal that does not require 2006-08-09

Apply for firearm warrant renewal at CFR 2006-08-09

Decide whether licence to possess a firearm for self del 2006-08-09

Decide whether licence to possess a firearm for occasic 2006-08-09

Decide whether licence to possess a firearm for dedlcal 2006-08-09

Decide whether licence to possess a flfearm in a privatt 2006-08-09

Decide whether licence to possess a firearm in a public 2006-08-09

Decide whether licence to possess a firearm for buslne 2006-08-09

Decide whether commercial agent licence may be rene 2006-0B-09

DeCide whether permit 10 possess ammunition in a call 2006-08-09

Decide whether import permit may be renewed 2006-08-09

Decide whether export permit may be renewed 2006-08-09

Decide whether In-transit permit may be renewed 2006-08-09

Decide whether firearm transport permit may be renewe 2006-08-09

Decide whether temporary authorisation to possess a fi 2006-08-09

Approve firearm warrant renewal application 2006-08-09

Refuse firearm warrant renewal applicaton 2006-06-09

2006-07-20

2006-07-20

2006-07-20

2006-07 -20

2006-07-20

2006-07-20

2006-07 -20

2006-07-20

2006-01-20

2006-07-20

2006-07-20

2006-08-01

2006-08-01

2006-08-01

2006-08-01

2006-08-01

2006-0B-01

2006-08-01

2006-08-01

2006-08-01

2006-08-01

2006-08-01

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

2006-08~15

2006-08-15

2006-08-15

2006-08-15

2006-08-15

5 days

5 days I 5 days

5 days

liday

5 days

5 days

5days

5 days

5 days

5 days

5 days

5 days

5days

5 days

5 days

5 days

5 days

5 days

5 days

days

5 days

5 days

5 days

5 days

5 days

5 days

5 days

5 days

5 days

5 days I 5 days

5 days

5 days

5days

5 days

5 days

5 days

I

16 of 25

5103310 Duplication (replacements) 2006-08-02

51033101 Replace commercial agent licence 2006-0e-02 2006-08-08 5 days

51033102 Replace competency certlficale 2006-0S-02 2006-08-0S 5 days

51033103 Replace transport permit 2006-0S-02 2006-08-0e 5 days

51033104 Replace licence to possess 2006-08-02 2006-08-0e 5 days

510 33105 Replace export permit 2006-08-02 2006-08-0e 5 days

51033106 Replace ammunition coilection permit 2006-06-02 2006-08-0e 5 days

51033107 Replace temporary authorisation 2006-06-02 2006-08-0e 5 days

51033108 Replace import permit 2006-08-02 2006-06-06 5 days

51033109 Replace accreditation certificale 2006-08-02 2006-08-08 5 days

510331010 Replace in-transit permit 2006-0e-02 2006-08-08 5 days

5103311 Cancellation amp Suspension 2006-08-30 2006-09-05 5 days

51033111 Registrar determines whether person is unfil to possest 2006-08-30 2006-09-05 5 days

51033112 Decide persons fitness to possess a firearm in court 2006-08-30 2006-09-05 5 days

51033113 Finalise registrars decision Ihal person is fit to possess 2006-08-30 2006-09-05 5 days

51033114 Finalise registrars decision thaI person is unfit to posslt 2006-08-30 2006-09-05 5 days

51033115 Inform registrar and invesligaling officer of decision reg 2006-08-30 2006middot09-05 5 days

51033116 Finalise unfilness slatus of person who becomes unfit te 20OP-08-30 2006-09-05 5 days

51033117 Process cancelled licence 10 possess a firearm 2006-06-30 2006-09-05 5 days

51033118 Process Cancelled import permit 2006-06-30 2006-09middot05 5 days

5103311 9 Process canceJJed commercial agent licence 2006-08-30 2006-09-05 5 days

Process canceiled temporary authorisation to possess I 2006-06-30 2006-09-05 5 days

Process cancelled in-transit permit 2006-08-30 i 2006-09-05 5 days

112 Ensure that cancelled export permil is surrendered 2006-08-30 2006-09-05 5 days

Ensure that cancelled transport permit is surrendered 2006-08-30 2006-09-05 5 days

510331114 Inform registrar of ceasing to carTY on business 2006-08-30 2006-09-05 5 days

510331115 Reconcile warrant holders list of possed firearms with ( 2006-08-30 2006-09-05 5 days

51033lU6 Reverse unfil persons unfitness status 2006-08-30 2006-09-05 5 days

Suspend firearm warranl for more Ihan 7 days 2006-06-30 2006-09-05 5 days

Suspend Firearm Warrant due to sus peeled offence 2006-06-30 2006-09-05 5 days

Suspend Firearm authorising losl or stolen firearm 2006-08-30 2006-09-05 5 days

Lift suspension of firearm warranl 2006-08-30 2006-09-05 5 days

Re-instate suspended license to possess a firearm 2006-08-30 2006-09-05 5 days

5103312 Surrendering 2006-09-06 2006-09middot12 5 days

51033121 Surrender commercial agent warrant 2006-09-06 2006-09-12

51033122 Surrender non-commercial agent warrant 2006-09-06 2006-09-12

51033123 Process surrendering of firearm item 2006-09-06 2006-09-12

51033124 Seize firearm related artifacts possessed by person wh 2006-09-06 2006-09-12

51033125 Place firearmsfirearm parts and ammUnition In safe sto 2006-09-06 200609-12

51033126 Manage surrendered commercial agent registers 2006-09-06 2006-09-12

51033127 Process surrendering of firearm item 2006-09-06 2006-09-12

51033128 Ensure that firearm items are disposed of within an acci 2006-09-06 2006-09-12

51033129 Dispose all firearm items possessed by Involved party 2006-09-06 2006-09-12

Ensure that ail firearms and firearm warranls in Ihe esta 2006-09-06 2008-09-12

Dispose of ail firearm ilems in the eslale of Ihe firearm 2006-09-06 2006-09middot12

Project Confidential Version 40

Firearms Cont~ol System Project Schedule

L St~n ~~~~~~~ 2006-08-23

Manage lost or stolen firearm item process 2006-08-23

Manage found firearm Item process 2006-OB-23

OeactlvatJon amp destruction 2006-09-13

Dispose of FIA ilem (Remove from SA environment De 2006-09-13

51033142 Deactivate Firearms 2006-09-13

5103315 Compensation 2006-09-15

51033151 Process application for compensation 2006-09-1 5

51033152 Process change of bank detail nolification 2006-09-15

5103316 Fine 2006-09middot19 51033161 Issue administrative fine 2006-09-19

51033162 Process response to administrative fine 2006-09-19

5103311 System Administration 2006-09-21

5103317 Maintain firearms control system user 2006-09-21

51033172 Maintain firearms control system user profile options 2006-09-21

51033173 Manage system and hardware problem 2006-09-21

51033174 Manage user request for system service 2006-09-21

5103318 Administration Support 2006-09-25

5103318 Manage scanning of documentation 2006-09-25

51033182 Manage paper documents received at CFR for regislral 2006-09-25

51034 Test Processes 2006-01-13

510341 Competency amp accreditation 2006-01middot13

510341 1 Test Process application for a further competency cartif 2006-07-13

5103412 Test Process applicalion for a competency certificate 2006-07-13

5103413 Tesl Process application for accredilalion for business I 2006-07-13

5103414 Test Process application for accreditation as an official 2006-07-13

5103415 Test Process applicalion for accreditation as an associ 2006-07-13

510342 licensing amp Inspections 2006-01-13

5103421 Test Process application for licence 10 possess a lirearr 200607-13

5103422 Test Process application for licence to conduct busines 2006-07-13

5103423 Tesl Process application for licence to deal in firearms i 2006-07-13

5103424 Test Process application fer licence to manufacture fire 2006-07middot13

5103425 Test Change commercial agent premises 2006-07-13

5103426 Test PerformAdministrate Inspeclion 01 dealer 2006-07-13

5103427 Tesl PerformAdministrate inspection of gunsmith 2006-07-13

5103428 Test PerformAdministrate inspection of manufacturer 2006-07-13

510343 Returns 2006-01-20

5103431 Test Manage returns 2006-07-20

5103432 Tesllntroduce firearm inlo SA legal firearm environmen 2006-07middot20

TeSllnlroduce ammunition inlo SA (Imports and manuf 2006-07-20

5103434 Tesl Process application for acquisition by offiCial inslitl 2006-07middot20

5103435 T esl Maintain official Institution regisler 2006-07middot20

510344 ImportlExportln IranslV Transport 2006-01middot21 5103441 Test Process application lor penTiit to Import firearms ar 2006-07-27

5103442 Test Process application for multiple import and 2006-07-27

845 5103443 Test Process application for multiple import and 2006-07-27

846 5103444 Tesl Process application for multiple import and exporll 2006-07-27

20()6~)2~)3 1300

PrOject Contidential r-~~~--~-~~~~~~~~~~--~~~--~~~~~--~~=

Finish 1Dural10n 1--Ic-TTT-+--~~~+~~~+~~~jh~TT==-+--~ 200amp-08-24 2 cla-y-a+--------1

2006-08-24 2 days

2006-08-24 2 days

2006-09middot14 2 days

2006-09-14 2 days

2006-09-14 days

2006-09-18 2

2006-09-18 2

2006-09-18

2006-09-20 2

2006-09-20 2

2006-09-20 2

2006-09-22 2daya

2006-09-22 2 days

2006~09-22 2 days

2006-09-22 2 days

2006-09-22 2 days

2006-09-28 2days

2006-09-26 2 days

2006-09-26 2 days

2006-09-26 5315 days

2006middot01-20 5 days

2006middot07-20 5 days

2006-07-20 5 days

2006-07-20 Sdays

2006middot07-20 5 days

2006-07-20 5 days

2006-01-20 5 days

2006-07-20 5 days

2006-07middot20 5 days

2006-07-20 5 days

2006-07-20 5 days

2006-07-20 5 days

2006-07 -14 1 day

2006-07-14 1 day

2006middot07-14 1 day

2006middot01-21 5 days

2006-07-27 5 days

2006-07middot27 5 days

2006-07-27 5 days

2006-07-27 5 days

2006-07-27 5 days

I 2006-08-03 5 days

2006-08-03 5 days

2006-08-03 5 days

2006-08-03 5 days

2006-08-03 5 days -------shy----ProJect Confidential

Version 40 18 of 25

Firearms Cont~ol System Project Schedule

L St~n ~~~~~~~ 2006-08-23

Manage lost or stolen firearm item process 2006-08-23

Manage found firearm Item process 2006-OB-23

OeactlvatJon amp destruction 2006-09-13

Dispose of FIA ilem (Remove from SA environment De 2006-09-13

51033142 Deactivate Firearms 2006-09-13

5103315 Compensation 2006-09-15

51033151 Process application for compensation 2006-09-1 5

51033152 Process change of bank detail nolification 2006-09-15

5103316 Fine 2006-09middot19 51033161 Issue administrative fine 2006-09-19

51033162 Process response to administrative fine 2006-09-19

5103311 System Administration 2006-09-21

5103317 Maintain firearms control system user 2006-09-21

51033172 Maintain firearms control system user profile options 2006-09-21

51033173 Manage system and hardware problem 2006-09-21

51033174 Manage user request for system service 2006-09-21

5103318 Administration Support 2006-09-25

5103318 Manage scanning of documentation 2006-09-25

51033182 Manage paper documents received at CFR for regislral 2006-09-25

51034 Test Processes 2006-01-13

510341 Competency amp accreditation 2006-01middot13

510341 1 Test Process application for a further competency cartif 2006-07-13

5103412 Test Process applicalion for a competency certificate 2006-07-13

5103413 Tesl Process application for accredilalion for business I 2006-07-13

5103414 Test Process application for accreditation as an official 2006-07-13

5103415 Test Process applicalion for accreditation as an associ 2006-07-13

510342 licensing amp Inspections 2006-01-13

5103421 Test Process application for licence 10 possess a lirearr 200607-13

5103422 Test Process application for licence to conduct busines 2006-07-13

5103423 Tesl Process application for licence to deal in firearms i 2006-07-13

5103424 Test Process application fer licence to manufacture fire 2006-07middot13

5103425 Test Change commercial agent premises 2006-07-13

5103426 Test PerformAdministrate Inspeclion 01 dealer 2006-07-13

5103427 Tesl PerformAdministrate inspection of gunsmith 2006-07-13

5103428 Test PerformAdministrate inspection of manufacturer 2006-07-13

510343 Returns 2006-01-20

5103431 Test Manage returns 2006-07-20

5103432 Tesllntroduce firearm inlo SA legal firearm environmen 2006-07middot20

TeSllnlroduce ammunition inlo SA (Imports and manuf 2006-07-20

5103434 Tesl Process application for acquisition by offiCial inslitl 2006-07middot20

5103435 T esl Maintain official Institution regisler 2006-07middot20

510344 ImportlExportln IranslV Transport 2006-01middot21 5103441 Test Process application lor penTiit to Import firearms ar 2006-07-27

5103442 Test Process application for multiple import and 2006-07-27

845 5103443 Test Process application for multiple import and 2006-07-27

846 5103444 Tesl Process application for multiple import and exporll 2006-07-27

20()6~)2~)3 1300

PrOject Contidential r-~~~--~-~~~~~~~~~~--~~~--~~~~~--~~=

Finish 1Dural10n 1--Ic-TTT-+--~~~+~~~+~~~jh~TT==-+--~ 200amp-08-24 2 cla-y-a+--------1

2006-08-24 2 days

2006-08-24 2 days

2006-09middot14 2 days

2006-09-14 2 days

2006-09-14 days

2006-09-18 2

2006-09-18 2

2006-09-18

2006-09-20 2

2006-09-20 2

2006-09-20 2

2006-09-22 2daya

2006-09-22 2 days

2006~09-22 2 days

2006-09-22 2 days

2006-09-22 2 days

2006-09-28 2days

2006-09-26 2 days

2006-09-26 2 days

2006-09-26 5315 days

2006middot01-20 5 days

2006middot07-20 5 days

2006-07-20 5 days

2006-07-20 Sdays

2006middot07-20 5 days

2006-07-20 5 days

2006-01-20 5 days

2006-07-20 5 days

2006-07middot20 5 days

2006-07-20 5 days

2006-07-20 5 days

2006-07-20 5 days

2006-07 -14 1 day

2006-07-14 1 day

2006middot07-14 1 day

2006middot01-21 5 days

2006-07-27 5 days

2006-07middot27 5 days

2006-07-27 5 days

2006-07-27 5 days

2006-07-27 5 days

I 2006-08-03 5 days

2006-08-03 5 days

2006-08-03 5 days

2006-08-03 5 days

2006-08-03 5 days -------shy----ProJect Confidential

Version 40 18 of 25

i

2006-07-27 2006-08-03

5103449 Test Process application for permit 10 carry firearms an 2006-07-27 2006-08-03 5 days

510344 10 Tost Process application for permit 10 carry firearms an 2006-07-27 2006-08-03 5 days

51034411 Test Process apptication for permit to carry firearms an 2006-07-27 2006-08-03 5 days

51034412 Test Transit firearm through SA 2006-07-27 2006-08-03 5 days

51034413 Test Physically export firearms 2006-07-27 2006-08-03 5 days

51034414 Test Physically export ammunition 2006-07-27 i 2006-08-03 5 days

51034415 Test Controllirerm item storage at border post 2006-07-27 2006-08-03 5 days

510345 Temporary Authorisation 2006Q7-13 2006Q7-20 5 days

5103451 Test Process application for a temporary authorisation I 2006-07-13 2006middot07middot20 5 days

5103452 Test Process application for temporary aulhorisation to 2006-07-13 2006-07-20 5 days

5103453 Tesl Process application for lemporary licence 10 displa 2006Q7-13 2006-07-20 5 days

5103454 Test Process application for a temporary authorisation t 2006Q7-13 2006-07-20 5 days

510346 Permits 2006Q7-13 2006Q7-20 5 days

5103461 Test Process application for permit to collect ammunilio 2006-07-13 2006-07-20 5 days

5103462 Test Process appllcalion for permit to transport firearm5 2006-07-13 2006-07-20 5 days

510347 Appeals 2006middot07middot13 2006Q7middot20 5 days

5103471 Test Manage Appeal 2006-07-13 2006-07-20 5 days

5103472 Test Process Appeal 2006-07-13 2006-07-20 5 days

510348 Notification 2006Q7-26 2006Q8Q1 5 days

510 3481 Test Declare firearm free zone 2006-07-26 2006-06-01 5 days

5103482 Test Update Cenlrat Firearms Register wilh change in c 2006-07-26 2006-08-01 5 days

5103483 Tesl Update Central Firearms Register wilh change in I 2006-07-26 2006-08-01 5 days

5103484 Test Update Central Firearms Register wilh correct info 2006-07middot26 2006-08-01 5 days

amp103485 Test Update manufacturer ticence with new manufaclur 2006-07-26 2006-08-01 5 days

5103486 Test Process notificalion of alteralion done 10 firearm 2006-07middot26 2006-08-01 5 days

5103487 T esl Process request to alter firearm 2006-07-26 2006-08-01 5 days

5103488 Test Manage information on annual report by accredilelt 2006-07middot26 2006-08-01 5 days

5103489 Test Update central firearm register with new responsib 2006-07-26 2006-08-01 5 days

51034810 Test Process notificatJOn of 10sUstolendefaced firearm 2006-07-26 2006-08-01 5 days

51034811 Test Inform registrar thai execuloradministratortrustee 2006-07middot26 2006-08-01 5 days

51034812 Testlnlorm registrar of progress tnal has been made wi 2006-07-26 2006-08-01 5 days

MO 34813 T esl Ensure that all firearms possessed or regislered 01 2006-07-26 2006-0B-01 5 days

510349 Renewals 2006o8Q9 20Q6-OB-15 5 day

5103491 Test Apply for firearm warrant renewallhal requires pa) 2006-08-09 2006-08-15 5 days

5103492 Tesl Apply for firearm warrant renewal thai does not ree 2006()8-O9 2006-06-15 5 days

5103493 Tesl Apply for firearm warrant renewallhat requires pa 2006-06-09 2006-08-15 5 days

5103494 Tesl Apply for firearm warrant renewal thaI does not ree 2006-06-09 2006-08-15 5 days

5103495 Test Apply for firearm warranl renewal at CFR 2006-08-09 2006-08-15 5 days

5103496 Test Decide whether licence 10 possess a firearm for se 2006-08-09 2006-08-15 5 days

5103491 Test Decide whetMr licence to possess a firearm for oe 2006-08-09 2006-08-15 5 days

5103498 Tesl DeCide whether licence 10 possess a firearm for dE 2006()8-09 2006-08-15 5 days

5103499 Test Decide whether licence to possess a firearm in a p 2006-08-09 2006-08-15 5 days

51034910 Tesl Decide whether licence to possess a firearm in a p 2006()8-09 2006-08-15 5 days

Test Decide whether licence 10

51034912 Test Decide whether commerci

51034913 Tesl Decide whelher permillo possess ammunilion in a 2006-08-09 2006-08-15 51034914 Tesl Decide whether import permll may be renewed 2006-08-09 2006-08-15 5 days

51034915 T esl Decide whether export permit may be renewed 2006-08-09 2006-08-15 I 5 days

51034916 Tesl Decide whelher in-Iransil permit may be renewed 2006-08-09 2006-08-15 5 days

5i034 17 T eurolsi Decide whether firearm Iransport permit may be re 2006-08-09 2006-08-15 5 days

51034916 Test Decide whether temporary authorisation to posses i 2006-08-09 2006-08-15 5 days

51034919 Tesl Approve firearm warrant renewal application 2006-08-09 2006-08-15

51034920 Test Refuse firearm warrant renewal applicallon 2006-08-09 2006-08-15

51034921 Test Assess applicalion for Iransilional renewal of licen 2006-08-09 2006-08-15

51034922 Test Issue renewed firearm warrant 2006-08-09 2006-08-15 5

5103410 Duplication (replacementa) 2006-08-02 2006-08-08 51034101 Test Replace commercial agent licence 2006-08-02 2006-08-08

51034102 Test Keplace competency certificate 2006-08-02 2006-08-08

51034103 Tesl Replace transport permil 2006-08-02 2006-08-08

51034104 Test Replace licence to possess 2006-08-02 2006-08-08 5 days

51G34105 Test Replace export permit 2006-08-02 2006-08-08 5 days

51034106 Test Repiace ammunition collection permit 2006-08-02 2006-08-08 5 days

51034101 T est Replace temporary authorisalion 2006-08-02 2006-08-08 5 days

51034108 Test Replace import permit 2006-08-02 2006middot08-08 5 days

51034 109 Test Replace accreditation certificale 2006-08-02 2006-08-08 5 days

Test Replace in-transit permit 2006-08-02 2006-08-08 5 days

5103411 Cancellation amp Suspension 2006-08-30 2006-09-05 Ii days

51034111 Test Registrar determines whether person is unfit 10 po 2006-08-30 2006-09-05 5 days

51034112 Test Decide personmiddots fitness to possess a firearm in COt 2006-08-30 2006-09-05 5 days

51034113 Test Finalise registrars decision that person IS fit to po 2006-08-30 2006-09-05 5 days

51034114 Test Finatise registrars deciSion Ihat person is unfit to r 2006-08-30 2006-09-05 5 days

51034115 Test Inform registrar and invesligating officer of decisiol 2006-08-30 2006-09-05 5 days

51034116 Test Finalise unfitness slatus of person who becomes u 2006-08-30 2006-09-05 5 days

51034117 Test Process cancelled IJcence to possess a firearm 2006-08-30 2006-09-05 5 days

510341 Ul Test Process Cancelled import permit 2006-08-30 2006-09-05 5 days

51034119 Test Process cancelled commercial agent licence 2006-08-30 2006-09-05 5 days

510341110 Test Process cancelled temporary authorisation to poss 2006-08-30 2006-09-05 5 days

510341111 Test Process cancelled in-transit permil 2006-08-30 2006-09-05 5 days

510341112 Test Ensure that cancelled export permil is surrenderee 2006-08-30 2006-09-05 5 days

510341113 Test Ensure that cancelled transport permIt IS surrendel 2006-08-30 2006-09-05 5 days

510341114 Tesllnform registrar of ceasing to carry on business 2006-08-30 2006-09-05 5 days

510341115 Tesl Reconcile warrant holderS lisl of passed firearms 2006-08-30 2006-09-05 5 days

510341116 Tesl Reverse unfil persons unfitness slatus 2006-08-30 2006-09-05 5 days

510341117 Test Suspend firearm warrant for more Ihan 7 days 2006-08-30 2006-09middot05 5 days

510341118 Test Suspend Firearm Warranl due to suspected offenc 2006-08-30 2006-09-05 5 days

Tesl Suspend Firearm aulhorisinglosl or slolen firearm 2006-08-30 2006-09-05 5 days

Test lift suspension of firearm warrant 2006-08-30 i 2006-09-05 5 days

Tesl Re-inslate suspended license to possess a firearlT 2006-08-30 2006-09-05 5 days

5103412 Surrendering 2006-09-06

Test Surrender commercial aaent warrant 2006-09-06

WI u am in sa 06 I middot12 bullbulldYS

03411 I CIl MaoaJe surrendered commercia agent regislers 2006-09-06 2006-09-12 5 days

51034127 Test Process surrendering of firearm item 2006-09-06 2006-09-12 5 days

51034128 Test Ensure that firearm items are disposed of within ar 2006-09-06 2006-09-12 5 days

51034129 Test Dispose all firearm items possessed by invOlved Pi 2006-09-06 2006-09-12 5 days

510341210 Test Ensure that all firearms and firearm warrants in thE 2006-09-06 2006-09-12 5 days

51034 1211 Test Dispose of all firearm items In the eslate of the fire 2006-09-06 2006-09-12 5 days

5103413 Lost and Found middot 2006-08middot23 2006-08middot24 2 days

51034131 Test Manage 10SI or slolen firearm item process 2006-08-23 2006-08-24 2 days

51034132 TeSI Manage found firearm item process 2006-08-23 2006-06-24 2 days

51034middot14middot Deactivation amp destruction 2006-09-13 2006-09-14 2 days

51034141 Test Dispose of FIA item (Remove from SA environmen 2006-09-13 2006-09-14 2 days

51034142 Test Deactivate FInarms 2006middot09middot13 2006-09-14 2 days

5103415 Compensation 2006-09middot15 2006-09middot18 2 days

51034151 Test Process application for compensation 2006-09-15 2006-09-18 2 days

51034152 Test Process change of bank detail notification 2006-09middot15 2006-09-18 2 days

5103416 Fines middot 2006-09-19 2006-09-20 2 days

51034161 Test Issue administrative fine 2006-09-19 2006middot09-20 2 days

51034162 Test Process response to administrative fine 2006-09-19 2006-09-20 2 days

5103417 System Administration 2006-09-21 2006-09middot22 2 days

51034171 Test MaintaIn firearms control system user 2006-09-21 2006-09-22 2 days

51034172 Test Maintain firearms control system user profile opto 2006-09-21 2006-09-22 2 days

51034173 Test Manage system and hardware probtem 2006-09-21 2006-09-22 2 days

51034 174 Test Manage user request for system service 2006-09-21 2006middot09-22 2 days

5103418 Administration Support 2006-09middot25 2006-09middot26 2 days

51034181 Test Manage scanning of documentatIon 2006-011-25 2006-09-26 2 days

51034182 Test Manage paper documents received at CFR for reg 2006-09-25 2006-09-26 2 days

5104 Supplementary Components Development 2006-05middot29 2006-07-31 46 days

51041middot Electronic Fonms Build 2006-05middot29 2006-07middot14 35 days

510411 Develop Forms Processing Methods 2006-05-29 2006-06-23 20 days

510412 Develop Sampte FCS Forms 2006-05-29 2006-06-23 20 days

510413 Tesl Forms Functionality middot 2006-06-26 2006-06-30 5 days

510414 Integrale Forms into FCS processes 2006-07-03 2006-07-07 b days

510415middot Test integrated solution 2006-07-10 2006-07-14

51141 Electronic receipt of documents 2006-05-29 2006-06-30

511411 Build 2006~05~29 2006-06-09

511412 Transition 2006-06-12 2006-06-16

511413 Tesl amp QA middot 2006-06-19 2006-06-23

S11414 Refine software 2006-06-26 2006-06-30

511415 FUnction Signoff 2006middot06middot30 2006-06-30

51042 Flreann Digital Image Viewing Build 2006-05-29 2006-07-28

510421 Conflgure streaming engine 2006-05-29 2006-06--09

510A 22 Configure amp tnlegrale Documenlum DAM 2006-05-29

51042 3 Develop repository structure 2006-06-12 2006-06-30

10

15

Projecl Confidntial 21 of 25 Version t )

Firearr)1s Control System Project Schedule

2006-07-03

2006-07-24

2006-1)5middot29

bull2006-05-29

2006-06-12

2006-06-12

2006-06-26

2006-06-12

2006-07-10

2006-1)5-29

2006-05-29

2006-06-12

2006-06-26

2006-07-20

2006()5-29

2006-05-29

2006-06-12

2006-06-26

2006-1)5-29

2006()S-29

2006-05-29

2006-06-06

2006-1)6-12

2006-06-12

2006-06-20

2006()6-12

2006-06-12

2006-06-20

2006-1)6middot12

2006-06-12

2006-06-20

2006-1)6middot12

2006-06-12

2006-06-20

2006-1)6-21

2006-06-21

2006-06-29

2006-1)6-21

2006-06-21

2006-06-29

2006-1)6-21

2006-06-21

2006-06-29

2006-1)6-21

006-06-21

2006-07-21

2006-07 -26

2006j)7-14

2006-06-09

2006-06-23

2006-06-16

2006-07-07

2006-06-23

2006-07-14

2006-1)7middot31

2006-06-23

2006-07-07

2006-07-19

2006-07-31

2006-1)6-30

2006-06-09

2006-06-23

2006-06-30

2006-1)7-17

2006-1)6()9

2006-06-07

2006-06-09

2006-1)6middot20

2006-06-19 I

2006-06-20

2006-1)6-20

2006-06-19

2006-06-20

2006-1)6middot20

2006-06-19

2006-06-20

2006-1)6middot20

2006-06-19

2006-06-20

2006-1)6-29

2006-06-28

2006-06-29

2006-1)6-29

2006-06-28

2006-06-29

2006-1)6-29

2006-06-28

2006-06middot29

2006()6middot29

2006-06-28

15 days

15 days

5 days

35 days

10 days

10 days

S days

10 days

10 days

S days

46 days

20 days

20 days

18 days

8 days

25 days

10 days

10 days

days

36 days

10 days

8 days

2 days

7 days

6 days

1 day

7 days

6 days

1 day

7 days

6 days

1 day

7 days

6 days

1 day

7 days

S days

1 day

7 days

6 days

1 day

7 days

6 days

1 day

7 days

6

FCSProjectSchedule-Revislon20060203fda

middot middotmiddot middot

middot middot middot

middot

I

I I Firearm Control System Project Schedule Project Confidential FCSProjectSchedule-Revision20060203fda

10 W8S Task Name ~6Q~ 06Jl4 1_07_W~--1I y91

__ l JIIsect ]JHID J TID ATM ELL 1 1035 510592 Test Interface ~ I 1 [1036 510510 Develop NPIS Interface 2006-06-12 2006-06-20 7 days Ill I I 1037 5105101 Develop Inlerface 2006-06-12 2006-06-19 6 days I I

1038 5105102 Test Interface 2006-06-20 2006-06-20 1 day I t

1039 510511 Develop Exhibit Interface 2006-06-12 2006-06-20 7 days =

1040 5105111 Develop Inlerface 2006-06-12 2006-06-19 6 days

1041 5105112 Test Interface 2006-06-20 2006-06-20 1 day

1042 510512 Develop HANIS Interface 2006-06-30 2006-07-13 10 days

1043 5105121 Develop Inlerface 2006-07-11 I2006-06-30 8 days

1044 5105122 Test Interface 2006-D7-12 2006-07-13 2 days

1045 510513 Develop MCS Interface 2006-06-30 2006-07-13 10 days

1046 5105131 Develop Interface 2006-06-30 2006-07-11 8 days

1047 5105132 Test Interface 2006-07-12 2006-07 -13 2 days

1048 510514 Integrate Interfaces to Functions 2006-06-12 2006-07-17 26 days

1049 5105141 Enabte CRIM amp AFIS Interface 2006-06-21 2006-06-22 2 days

1050 5105142middot Enable CAS Inlerface 2006-06-21 2006-06-22 2 days

1051 510 5 143 Enabte Persal Interface 2006-06-21 2006-06-22 2 days

1052 5105144 Enable Polfin Interface 2006-06-21 2006-06-22 2 days

~ 5105145 Enable FSL Interface 2006-06-30 2006-07-03 2 days

1054 5105146 Enable Circulations Interface 2006-06-30 2006-07 -03 2 days

1055 5105147 Enable Inkwazi Interface 2006-06-30 2006-07-03 2 days

1056 5105148 Enabte PAS Interface 2006-06-30 2006-07-03 2 days

1057 5105149middot Enable NPIS Interface 2006-D6-21 2006-06-22 2 days

1058 51051410 Enable Exhibit Interface 2006-06-21 2006-06-22 2 days

1059 510 51411 Enable HANIS Interface 2006-07-14 2006-07-17 2 days

1060 51051412 Enable MCS Interface 2006-07-14 2006-07-17 2 days

1061 51051413 Enable IJS Interface 2006-D6-12 2006-06-13 2 days

1062 5106 Develop User Support System 2006-05-29 2006-07-18 ~7 days

1063 51061 Develop content presentation method 2006-05-29 2006-06-23 ~O days

1064 51062 Develop contenl mainlenance method 2006-05-29 2006-06-23 20 days

1065 51063 Integrate Support System into the FCS 2006-06-26 2006-07-18 ~ 7 days

1066 520 Develop User Documentation 2006-07-05 2006-11-22 1~1 days

1 1067 5201 Develop User Support Documentation 2006-07-05 2006-09-26 IlQ days I-~

~1068 5202 Internal Review of User Documentation 2006-09-13 2006-09-26 10 days

I 1069 5203 Update User Documentation 2006-09-27 2006-10-10 ~O days11070j 5204 Approve User Documentation 2006-10-11 2006-10-19 7 days 1-shy

1071 5205 Develop Training Material 2006-09-27 2006-11-13 34 days

11072 5206 Internal Review of Training Documentation 2006-10-31 2006-11-13 10 days

1073 5207 Approve Trainin9 Matenal 2006-11-14 2006-11-22 7 days I11074 Acceptance Test Development 2006-07-05 2006-09-27 61 days I530

~ 5301 Develop test cases amp documentation 2006-07-05 2006-08-15 30 days

1076 5302 Develop FCSFRS Interface test cases amp documentation 2006-08-16 2006-09-06 16 days I 1077 5303 Internal review of test cases amp documentation 2006-09-07 2006-09-13 5 days I 1078 5304 SAPS Approve test documentation 2006-09-14 2006-09-27 - 0 days

1079 540 Fes ote amp10 ~- 1 ~I I

1080 5401 System Integration (Alpha) 2006-09-28 2006-10-20 17 days I

I 1081 54011 Verify integraled syslem operation 2006-09-28 2006-10-04 5 days ~ L I 11 - 1 Xtnnted on 2006-02-10 Project Confidential 23 of 25 I

ve~06-)2-)31300 Verion40

~-

WI u am in sa 06 I middot12 bullbulldYS

03411 I CIl MaoaJe surrendered commercia agent regislers 2006-09-06 2006-09-12 5 days

51034127 Test Process surrendering of firearm item 2006-09-06 2006-09-12 5 days

51034128 Test Ensure that firearm items are disposed of within ar 2006-09-06 2006-09-12 5 days

51034129 Test Dispose all firearm items possessed by invOlved Pi 2006-09-06 2006-09-12 5 days

510341210 Test Ensure that all firearms and firearm warrants in thE 2006-09-06 2006-09-12 5 days

51034 1211 Test Dispose of all firearm items In the eslate of the fire 2006-09-06 2006-09-12 5 days

5103413 Lost and Found middot 2006-08middot23 2006-08middot24 2 days

51034131 Test Manage 10SI or slolen firearm item process 2006-08-23 2006-08-24 2 days

51034132 TeSI Manage found firearm item process 2006-08-23 2006-06-24 2 days

51034middot14middot Deactivation amp destruction 2006-09-13 2006-09-14 2 days

51034141 Test Dispose of FIA item (Remove from SA environmen 2006-09-13 2006-09-14 2 days

51034142 Test Deactivate FInarms 2006middot09middot13 2006-09-14 2 days

5103415 Compensation 2006-09middot15 2006-09middot18 2 days

51034151 Test Process application for compensation 2006-09-15 2006-09-18 2 days

51034152 Test Process change of bank detail notification 2006-09middot15 2006-09-18 2 days

5103416 Fines middot 2006-09-19 2006-09-20 2 days

51034161 Test Issue administrative fine 2006-09-19 2006middot09-20 2 days

51034162 Test Process response to administrative fine 2006-09-19 2006-09-20 2 days

5103417 System Administration 2006-09-21 2006-09middot22 2 days

51034171 Test MaintaIn firearms control system user 2006-09-21 2006-09-22 2 days

51034172 Test Maintain firearms control system user profile opto 2006-09-21 2006-09-22 2 days

51034173 Test Manage system and hardware probtem 2006-09-21 2006-09-22 2 days

51034 174 Test Manage user request for system service 2006-09-21 2006middot09-22 2 days

5103418 Administration Support 2006-09middot25 2006-09middot26 2 days

51034181 Test Manage scanning of documentatIon 2006-011-25 2006-09-26 2 days

51034182 Test Manage paper documents received at CFR for reg 2006-09-25 2006-09-26 2 days

5104 Supplementary Components Development 2006-05middot29 2006-07-31 46 days

51041middot Electronic Fonms Build 2006-05middot29 2006-07middot14 35 days

510411 Develop Forms Processing Methods 2006-05-29 2006-06-23 20 days

510412 Develop Sampte FCS Forms 2006-05-29 2006-06-23 20 days

510413 Tesl Forms Functionality middot 2006-06-26 2006-06-30 5 days

510414 Integrale Forms into FCS processes 2006-07-03 2006-07-07 b days

510415middot Test integrated solution 2006-07-10 2006-07-14

51141 Electronic receipt of documents 2006-05-29 2006-06-30

511411 Build 2006~05~29 2006-06-09

511412 Transition 2006-06-12 2006-06-16

511413 Tesl amp QA middot 2006-06-19 2006-06-23

S11414 Refine software 2006-06-26 2006-06-30

511415 FUnction Signoff 2006middot06middot30 2006-06-30

51042 Flreann Digital Image Viewing Build 2006-05-29 2006-07-28

510421 Conflgure streaming engine 2006-05-29 2006-06--09

510A 22 Configure amp tnlegrale Documenlum DAM 2006-05-29

51042 3 Develop repository structure 2006-06-12 2006-06-30

10

15

Projecl Confidntial 21 of 25 Version t )

Firearr)1s Control System Project Schedule

2006-07-03

2006-07-24

2006-1)5middot29

bull2006-05-29

2006-06-12

2006-06-12

2006-06-26

2006-06-12

2006-07-10

2006-1)5-29

2006-05-29

2006-06-12

2006-06-26

2006-07-20

2006()5-29

2006-05-29

2006-06-12

2006-06-26

2006-1)5-29

2006()S-29

2006-05-29

2006-06-06

2006-1)6-12

2006-06-12

2006-06-20

2006()6-12

2006-06-12

2006-06-20

2006-1)6middot12

2006-06-12

2006-06-20

2006-1)6middot12

2006-06-12

2006-06-20

2006-1)6-21

2006-06-21

2006-06-29

2006-1)6-21

2006-06-21

2006-06-29

2006-1)6-21

2006-06-21

2006-06-29

2006-1)6-21

006-06-21

2006-07-21

2006-07 -26

2006j)7-14

2006-06-09

2006-06-23

2006-06-16

2006-07-07

2006-06-23

2006-07-14

2006-1)7middot31

2006-06-23

2006-07-07

2006-07-19

2006-07-31

2006-1)6-30

2006-06-09

2006-06-23

2006-06-30

2006-1)7-17

2006-1)6()9

2006-06-07

2006-06-09

2006-1)6middot20

2006-06-19 I

2006-06-20

2006-1)6-20

2006-06-19

2006-06-20

2006-1)6middot20

2006-06-19

2006-06-20

2006-1)6middot20

2006-06-19

2006-06-20

2006-1)6-29

2006-06-28

2006-06-29

2006-1)6-29

2006-06-28

2006-06-29

2006-1)6-29

2006-06-28

2006-06middot29

2006()6middot29

2006-06-28

15 days

15 days

5 days

35 days

10 days

10 days

S days

10 days

10 days

S days

46 days

20 days

20 days

18 days

8 days

25 days

10 days

10 days

days

36 days

10 days

8 days

2 days

7 days

6 days

1 day

7 days

6 days

1 day

7 days

6 days

1 day

7 days

6 days

1 day

7 days

S days

1 day

7 days

6 days

1 day

7 days

6 days

1 day

7 days

6

FCSProjectSchedule-Revislon20060203fda

middot middotmiddot middot

middot middot middot

middot

I

I I Firearm Control System Project Schedule Project Confidential FCSProjectSchedule-Revision20060203fda

10 W8S Task Name ~6Q~ 06Jl4 1_07_W~--1I y91

__ l JIIsect ]JHID J TID ATM ELL 1 1035 510592 Test Interface ~ I 1 [1036 510510 Develop NPIS Interface 2006-06-12 2006-06-20 7 days Ill I I 1037 5105101 Develop Inlerface 2006-06-12 2006-06-19 6 days I I

1038 5105102 Test Interface 2006-06-20 2006-06-20 1 day I t

1039 510511 Develop Exhibit Interface 2006-06-12 2006-06-20 7 days =

1040 5105111 Develop Inlerface 2006-06-12 2006-06-19 6 days

1041 5105112 Test Interface 2006-06-20 2006-06-20 1 day

1042 510512 Develop HANIS Interface 2006-06-30 2006-07-13 10 days

1043 5105121 Develop Inlerface 2006-07-11 I2006-06-30 8 days

1044 5105122 Test Interface 2006-D7-12 2006-07-13 2 days

1045 510513 Develop MCS Interface 2006-06-30 2006-07-13 10 days

1046 5105131 Develop Interface 2006-06-30 2006-07-11 8 days

1047 5105132 Test Interface 2006-07-12 2006-07 -13 2 days

1048 510514 Integrate Interfaces to Functions 2006-06-12 2006-07-17 26 days

1049 5105141 Enabte CRIM amp AFIS Interface 2006-06-21 2006-06-22 2 days

1050 5105142middot Enable CAS Inlerface 2006-06-21 2006-06-22 2 days

1051 510 5 143 Enabte Persal Interface 2006-06-21 2006-06-22 2 days

1052 5105144 Enable Polfin Interface 2006-06-21 2006-06-22 2 days

~ 5105145 Enable FSL Interface 2006-06-30 2006-07-03 2 days

1054 5105146 Enable Circulations Interface 2006-06-30 2006-07 -03 2 days

1055 5105147 Enable Inkwazi Interface 2006-06-30 2006-07-03 2 days

1056 5105148 Enabte PAS Interface 2006-06-30 2006-07-03 2 days

1057 5105149middot Enable NPIS Interface 2006-D6-21 2006-06-22 2 days

1058 51051410 Enable Exhibit Interface 2006-06-21 2006-06-22 2 days

1059 510 51411 Enable HANIS Interface 2006-07-14 2006-07-17 2 days

1060 51051412 Enable MCS Interface 2006-07-14 2006-07-17 2 days

1061 51051413 Enable IJS Interface 2006-D6-12 2006-06-13 2 days

1062 5106 Develop User Support System 2006-05-29 2006-07-18 ~7 days

1063 51061 Develop content presentation method 2006-05-29 2006-06-23 ~O days

1064 51062 Develop contenl mainlenance method 2006-05-29 2006-06-23 20 days

1065 51063 Integrate Support System into the FCS 2006-06-26 2006-07-18 ~ 7 days

1066 520 Develop User Documentation 2006-07-05 2006-11-22 1~1 days

1 1067 5201 Develop User Support Documentation 2006-07-05 2006-09-26 IlQ days I-~

~1068 5202 Internal Review of User Documentation 2006-09-13 2006-09-26 10 days

I 1069 5203 Update User Documentation 2006-09-27 2006-10-10 ~O days11070j 5204 Approve User Documentation 2006-10-11 2006-10-19 7 days 1-shy

1071 5205 Develop Training Material 2006-09-27 2006-11-13 34 days

11072 5206 Internal Review of Training Documentation 2006-10-31 2006-11-13 10 days

1073 5207 Approve Trainin9 Matenal 2006-11-14 2006-11-22 7 days I11074 Acceptance Test Development 2006-07-05 2006-09-27 61 days I530

~ 5301 Develop test cases amp documentation 2006-07-05 2006-08-15 30 days

1076 5302 Develop FCSFRS Interface test cases amp documentation 2006-08-16 2006-09-06 16 days I 1077 5303 Internal review of test cases amp documentation 2006-09-07 2006-09-13 5 days I 1078 5304 SAPS Approve test documentation 2006-09-14 2006-09-27 - 0 days

1079 540 Fes ote amp10 ~- 1 ~I I

1080 5401 System Integration (Alpha) 2006-09-28 2006-10-20 17 days I

I 1081 54011 Verify integraled syslem operation 2006-09-28 2006-10-04 5 days ~ L I 11 - 1 Xtnnted on 2006-02-10 Project Confidential 23 of 25 I

ve~06-)2-)31300 Verion40

~-

Firearr)1s Control System Project Schedule

2006-07-03

2006-07-24

2006-1)5middot29

bull2006-05-29

2006-06-12

2006-06-12

2006-06-26

2006-06-12

2006-07-10

2006-1)5-29

2006-05-29

2006-06-12

2006-06-26

2006-07-20

2006()5-29

2006-05-29

2006-06-12

2006-06-26

2006-1)5-29

2006()S-29

2006-05-29

2006-06-06

2006-1)6-12

2006-06-12

2006-06-20

2006()6-12

2006-06-12

2006-06-20

2006-1)6middot12

2006-06-12

2006-06-20

2006-1)6middot12

2006-06-12

2006-06-20

2006-1)6-21

2006-06-21

2006-06-29

2006-1)6-21

2006-06-21

2006-06-29

2006-1)6-21

2006-06-21

2006-06-29

2006-1)6-21

006-06-21

2006-07-21

2006-07 -26

2006j)7-14

2006-06-09

2006-06-23

2006-06-16

2006-07-07

2006-06-23

2006-07-14

2006-1)7middot31

2006-06-23

2006-07-07

2006-07-19

2006-07-31

2006-1)6-30

2006-06-09

2006-06-23

2006-06-30

2006-1)7-17

2006-1)6()9

2006-06-07

2006-06-09

2006-1)6middot20

2006-06-19 I

2006-06-20

2006-1)6-20

2006-06-19

2006-06-20

2006-1)6middot20

2006-06-19

2006-06-20

2006-1)6middot20

2006-06-19

2006-06-20

2006-1)6-29

2006-06-28

2006-06-29

2006-1)6-29

2006-06-28

2006-06-29

2006-1)6-29

2006-06-28

2006-06middot29

2006()6middot29

2006-06-28

15 days

15 days

5 days

35 days

10 days

10 days

S days

10 days

10 days

S days

46 days

20 days

20 days

18 days

8 days

25 days

10 days

10 days

days

36 days

10 days

8 days

2 days

7 days

6 days

1 day

7 days

6 days

1 day

7 days

6 days

1 day

7 days

6 days

1 day

7 days

S days

1 day

7 days

6 days

1 day

7 days

6 days

1 day

7 days

6

FCSProjectSchedule-Revislon20060203fda

middot middotmiddot middot

middot middot middot

middot

I

I I Firearm Control System Project Schedule Project Confidential FCSProjectSchedule-Revision20060203fda

10 W8S Task Name ~6Q~ 06Jl4 1_07_W~--1I y91

__ l JIIsect ]JHID J TID ATM ELL 1 1035 510592 Test Interface ~ I 1 [1036 510510 Develop NPIS Interface 2006-06-12 2006-06-20 7 days Ill I I 1037 5105101 Develop Inlerface 2006-06-12 2006-06-19 6 days I I

1038 5105102 Test Interface 2006-06-20 2006-06-20 1 day I t

1039 510511 Develop Exhibit Interface 2006-06-12 2006-06-20 7 days =

1040 5105111 Develop Inlerface 2006-06-12 2006-06-19 6 days

1041 5105112 Test Interface 2006-06-20 2006-06-20 1 day

1042 510512 Develop HANIS Interface 2006-06-30 2006-07-13 10 days

1043 5105121 Develop Inlerface 2006-07-11 I2006-06-30 8 days

1044 5105122 Test Interface 2006-D7-12 2006-07-13 2 days

1045 510513 Develop MCS Interface 2006-06-30 2006-07-13 10 days

1046 5105131 Develop Interface 2006-06-30 2006-07-11 8 days

1047 5105132 Test Interface 2006-07-12 2006-07 -13 2 days

1048 510514 Integrate Interfaces to Functions 2006-06-12 2006-07-17 26 days

1049 5105141 Enabte CRIM amp AFIS Interface 2006-06-21 2006-06-22 2 days

1050 5105142middot Enable CAS Inlerface 2006-06-21 2006-06-22 2 days

1051 510 5 143 Enabte Persal Interface 2006-06-21 2006-06-22 2 days

1052 5105144 Enable Polfin Interface 2006-06-21 2006-06-22 2 days

~ 5105145 Enable FSL Interface 2006-06-30 2006-07-03 2 days

1054 5105146 Enable Circulations Interface 2006-06-30 2006-07 -03 2 days

1055 5105147 Enable Inkwazi Interface 2006-06-30 2006-07-03 2 days

1056 5105148 Enabte PAS Interface 2006-06-30 2006-07-03 2 days

1057 5105149middot Enable NPIS Interface 2006-D6-21 2006-06-22 2 days

1058 51051410 Enable Exhibit Interface 2006-06-21 2006-06-22 2 days

1059 510 51411 Enable HANIS Interface 2006-07-14 2006-07-17 2 days

1060 51051412 Enable MCS Interface 2006-07-14 2006-07-17 2 days

1061 51051413 Enable IJS Interface 2006-D6-12 2006-06-13 2 days

1062 5106 Develop User Support System 2006-05-29 2006-07-18 ~7 days

1063 51061 Develop content presentation method 2006-05-29 2006-06-23 ~O days

1064 51062 Develop contenl mainlenance method 2006-05-29 2006-06-23 20 days

1065 51063 Integrate Support System into the FCS 2006-06-26 2006-07-18 ~ 7 days

1066 520 Develop User Documentation 2006-07-05 2006-11-22 1~1 days

1 1067 5201 Develop User Support Documentation 2006-07-05 2006-09-26 IlQ days I-~

~1068 5202 Internal Review of User Documentation 2006-09-13 2006-09-26 10 days

I 1069 5203 Update User Documentation 2006-09-27 2006-10-10 ~O days11070j 5204 Approve User Documentation 2006-10-11 2006-10-19 7 days 1-shy

1071 5205 Develop Training Material 2006-09-27 2006-11-13 34 days

11072 5206 Internal Review of Training Documentation 2006-10-31 2006-11-13 10 days

1073 5207 Approve Trainin9 Matenal 2006-11-14 2006-11-22 7 days I11074 Acceptance Test Development 2006-07-05 2006-09-27 61 days I530

~ 5301 Develop test cases amp documentation 2006-07-05 2006-08-15 30 days

1076 5302 Develop FCSFRS Interface test cases amp documentation 2006-08-16 2006-09-06 16 days I 1077 5303 Internal review of test cases amp documentation 2006-09-07 2006-09-13 5 days I 1078 5304 SAPS Approve test documentation 2006-09-14 2006-09-27 - 0 days

1079 540 Fes ote amp10 ~- 1 ~I I

1080 5401 System Integration (Alpha) 2006-09-28 2006-10-20 17 days I

I 1081 54011 Verify integraled syslem operation 2006-09-28 2006-10-04 5 days ~ L I 11 - 1 Xtnnted on 2006-02-10 Project Confidential 23 of 25 I

ve~06-)2-)31300 Verion40

~-

I I Firearm Control System Project Schedule Project Confidential FCSProjectSchedule-Revision20060203fda

10 W8S Task Name ~6Q~ 06Jl4 1_07_W~--1I y91

__ l JIIsect ]JHID J TID ATM ELL 1 1035 510592 Test Interface ~ I 1 [1036 510510 Develop NPIS Interface 2006-06-12 2006-06-20 7 days Ill I I 1037 5105101 Develop Inlerface 2006-06-12 2006-06-19 6 days I I

1038 5105102 Test Interface 2006-06-20 2006-06-20 1 day I t

1039 510511 Develop Exhibit Interface 2006-06-12 2006-06-20 7 days =

1040 5105111 Develop Inlerface 2006-06-12 2006-06-19 6 days

1041 5105112 Test Interface 2006-06-20 2006-06-20 1 day

1042 510512 Develop HANIS Interface 2006-06-30 2006-07-13 10 days

1043 5105121 Develop Inlerface 2006-07-11 I2006-06-30 8 days

1044 5105122 Test Interface 2006-D7-12 2006-07-13 2 days

1045 510513 Develop MCS Interface 2006-06-30 2006-07-13 10 days

1046 5105131 Develop Interface 2006-06-30 2006-07-11 8 days

1047 5105132 Test Interface 2006-07-12 2006-07 -13 2 days

1048 510514 Integrate Interfaces to Functions 2006-06-12 2006-07-17 26 days

1049 5105141 Enabte CRIM amp AFIS Interface 2006-06-21 2006-06-22 2 days

1050 5105142middot Enable CAS Inlerface 2006-06-21 2006-06-22 2 days

1051 510 5 143 Enabte Persal Interface 2006-06-21 2006-06-22 2 days

1052 5105144 Enable Polfin Interface 2006-06-21 2006-06-22 2 days

~ 5105145 Enable FSL Interface 2006-06-30 2006-07-03 2 days

1054 5105146 Enable Circulations Interface 2006-06-30 2006-07 -03 2 days

1055 5105147 Enable Inkwazi Interface 2006-06-30 2006-07-03 2 days

1056 5105148 Enabte PAS Interface 2006-06-30 2006-07-03 2 days

1057 5105149middot Enable NPIS Interface 2006-D6-21 2006-06-22 2 days

1058 51051410 Enable Exhibit Interface 2006-06-21 2006-06-22 2 days

1059 510 51411 Enable HANIS Interface 2006-07-14 2006-07-17 2 days

1060 51051412 Enable MCS Interface 2006-07-14 2006-07-17 2 days

1061 51051413 Enable IJS Interface 2006-D6-12 2006-06-13 2 days

1062 5106 Develop User Support System 2006-05-29 2006-07-18 ~7 days

1063 51061 Develop content presentation method 2006-05-29 2006-06-23 ~O days

1064 51062 Develop contenl mainlenance method 2006-05-29 2006-06-23 20 days

1065 51063 Integrate Support System into the FCS 2006-06-26 2006-07-18 ~ 7 days

1066 520 Develop User Documentation 2006-07-05 2006-11-22 1~1 days

1 1067 5201 Develop User Support Documentation 2006-07-05 2006-09-26 IlQ days I-~

~1068 5202 Internal Review of User Documentation 2006-09-13 2006-09-26 10 days

I 1069 5203 Update User Documentation 2006-09-27 2006-10-10 ~O days11070j 5204 Approve User Documentation 2006-10-11 2006-10-19 7 days 1-shy

1071 5205 Develop Training Material 2006-09-27 2006-11-13 34 days

11072 5206 Internal Review of Training Documentation 2006-10-31 2006-11-13 10 days

1073 5207 Approve Trainin9 Matenal 2006-11-14 2006-11-22 7 days I11074 Acceptance Test Development 2006-07-05 2006-09-27 61 days I530

~ 5301 Develop test cases amp documentation 2006-07-05 2006-08-15 30 days

1076 5302 Develop FCSFRS Interface test cases amp documentation 2006-08-16 2006-09-06 16 days I 1077 5303 Internal review of test cases amp documentation 2006-09-07 2006-09-13 5 days I 1078 5304 SAPS Approve test documentation 2006-09-14 2006-09-27 - 0 days

1079 540 Fes ote amp10 ~- 1 ~I I

1080 5401 System Integration (Alpha) 2006-09-28 2006-10-20 17 days I

I 1081 54011 Verify integraled syslem operation 2006-09-28 2006-10-04 5 days ~ L I 11 - 1 Xtnnted on 2006-02-10 Project Confidential 23 of 25 I

ve~06-)2-)31300 Verion40

~-

Firearms Control System PrOject Schedule

1082 1083

1084

1085

1093

1094

1095

1096

1097

1096

1099

1100

1101

1102

54013 Compile software test version

54014 Inlernal System Integration Testing Starts

5402 Final Alpha Test

54021 Functional amp FCS Process Test (Alpha Site)

54022 Review Alpha Test results

54024 Refine Software for Beta Test

54025 FCS Alpha Test Completed 5403 Installation Mechanisms Build

54031 Compile Installation and Setup Manual

54032 Develop Setup routines scnpt

5404 System Integration (Beta Site)

54041 Install FCS Software at Bela Site

54042 (TeSI) Data migration amp data testing

54043 FRS data migralion

540A4 FCSIFRS Data migration ilf testing

54045 Conduct First Integrated System Tests

54046 Optimise System Performance

54047 Refine System Code

600 FCS Beta Testing 610 PremiddotBeta test

6101 Conduct Second Integrated System Tests

6102 Prepare Software fOf Beta Test

620 FCS Bsta test

6201 Beta Test preparation Phase 1 Tesls

6202 Beta Test FCS

6203 Review Bela Test Refine System Code

6204 Additional reVlew time

6205 Controlled User Beta Completed 700 Testing Phase 710 Set-up Field Test Sites

7101 Implement at the Central Data Centre 71011 Setup amp Configure Hardware

71012 Update amp Configure Software

710_2 Implement at CFR 71021 Setup amp Configure Hardware

71022 Setup amp Configure Software

7103 Implement at Pilot FRC 1 71031 Setup amp Configure Hardware

71032 Setup amp Configure Software

7104 Implement at Pilot FRC 2 710A1 Setup amp Configure Hardware

10A2 Setup amp Configure Software

720 Integration Testing 7201 ConducI1storder Funclional TestsFRC level

7202 Conduct Functional Tests C F R level

7203 Conduct 2nd order Functionat T esls FRC level

2006-10-19

2006-09middot28

2006middot10-19

2006-10-19

2006-11-03

2006-11-14

2006-11middot27

2006middot10middot31

2006-10-31

2006-10-31

2006-11middot28

2006middot11middot28

2006middot11middot28

2006-12-05

2006middot11-28

2007-01-04

2007-01-18

2007-01-18

2007-lt12-01

2007-lt12-lt11

2007-02-lt11

2007-02-lt18

2007-lt12-19

2007middot02middot19

2007-02-26

2007-03-12

2007 -03-19

2007-03-22

2007-02-06

2007-lt12-06

2007-lt12-08

2007-02-08

2007middot02-15

2007-02-15

2007middot02middot15

2007-02-22

2007-02-22

2007-02middot22

2007-02-26

2007-03-01

2007-03-01

2007-03-lt15

2007middot03middot23

2007-03middot23

2007-03-30

2007-lt14-06

2006-10-20 2 days

2006middot09middot28 odays

2006-11-27 28 days

2006-11-lt12 11 days

2006-11-13 1 days

2006-11-27 10 days

2006-11-27 a days

2006-11middot27 20 days

2006-11-13 10 days

2006-11-27 20 days

2007middot01-31 35 days

2006-12-lt14 5 days

2006-12-11 10 days

2007-lt11-03 10 days

2007-01-03 t5 days

2007-01-17 10 days

2007middot01-31 10 days

2007-01-31 10 days

2007-lt13middot22 36 days

2007-02middot16 12 days

2007-02middot07 5 days

2007-02-16 7 days

2007-lt13middot22 24 days

2007-02-23 5 days

2007-03-09 10 days

2007-03middot16 5 days

2007-03-22 4 days

2007-03middot22 odays

i 2007-05middot16 72 days

2007-03-07 ZO days

2007 -02-21 10days

2007-02-14 5 days

2007middot02-21 5 days

2007-02middot28 10 days

2007-02-21 5 days

2007-02-28 5 days

2007-lt12-28 5 days

2007-02middot23 2 days

2007-02-28 3 days

2007-03-07 5 days

2007-03-02 2 days 2007-03middot07 3 days

2007middot04middot20 21 days

2007-03-29 5 days

2007-lt14middot05

2007middot04-12

Project Confidential Ve-ion 40

05-18

0518

Project Confidential [UOmiddotVmiddoty_ 1300 Vemiddotslon 40

32131144 Confidential Review of FCS Scheclile

Annexure B Detail Activity Comparison between Contract Baseline Schedule and Revised Schedule

B 1 Please note the following

B11 The Original Contract Baseline (September 2004) schedule WBS numbers dates and durations are used in the table up to the end of the Design Phase (Column A WBS 1 to 235)

B12 In the Original Contract Baseline schedule the task links in MsProjects for the Development Phase tasks were not all correctly linked to the end of the Design Phase This was corrected in the schedule for the March 2005 contract addendum

B13 For this reason the March 2005 Addendums WBS numbers dates and durations are used in the table from the Development Phase to end of the project (Column Al WBS 225 to 919)

B14 Please note that in the March 2005 Addendum sub-task detail activities Study Source Information were removed and combined with the Compile Specification sub-task detail activities resulting in the Addendums Development Phase WBS number starting at 225 versus the original contract baselines 236

LUUO-UL-IO 0631 Project Confidential

Version 50 Page 23 of 23 if 1_n

j(U (

05-18

0518

Project Confidential [UOmiddotVmiddoty_ 1300 Vemiddotslon 40

32131144 Confidential Review of FCS Scheclile

Annexure B Detail Activity Comparison between Contract Baseline Schedule and Revised Schedule

B 1 Please note the following

B11 The Original Contract Baseline (September 2004) schedule WBS numbers dates and durations are used in the table up to the end of the Design Phase (Column A WBS 1 to 235)

B12 In the Original Contract Baseline schedule the task links in MsProjects for the Development Phase tasks were not all correctly linked to the end of the Design Phase This was corrected in the schedule for the March 2005 contract addendum

B13 For this reason the March 2005 Addendums WBS numbers dates and durations are used in the table from the Development Phase to end of the project (Column Al WBS 225 to 919)

B14 Please note that in the March 2005 Addendum sub-task detail activities Study Source Information were removed and combined with the Compile Specification sub-task detail activities resulting in the Addendums Development Phase WBS number starting at 225 versus the original contract baselines 236

LUUO-UL-IO 0631 Project Confidential

Version 50 Page 23 of 23 if 1_n

j(U (

32131144 Confidential Review of FCS Scheclile

Annexure B Detail Activity Comparison between Contract Baseline Schedule and Revised Schedule

B 1 Please note the following

B11 The Original Contract Baseline (September 2004) schedule WBS numbers dates and durations are used in the table up to the end of the Design Phase (Column A WBS 1 to 235)

B12 In the Original Contract Baseline schedule the task links in MsProjects for the Development Phase tasks were not all correctly linked to the end of the Design Phase This was corrected in the schedule for the March 2005 contract addendum

B13 For this reason the March 2005 Addendums WBS numbers dates and durations are used in the table from the Development Phase to end of the project (Column Al WBS 225 to 919)

B14 Please note that in the March 2005 Addendum sub-task detail activities Study Source Information were removed and combined with the Compile Specification sub-task detail activities resulting in the Addendums Development Phase WBS number starting at 225 versus the original contract baselines 236

LUUO-UL-IO 0631 Project Confidential

Version 50 Page 23 of 23 if 1_n

j(U (

8 aJnxauuv

--------------------

--------------------