Project Charter

Project Name: Business Permit and Licensing System

Date: November 29, 2013 ersion: 1!0 "ut#or: BPLS $eam

Document Control
Change Record
Date Author Version Change Reference

Reviewers
Sign Off Date Reviewer Position Sign Off

Distribution
Copy umber ame

ProjectCharter

ii

!able of Contents
DOCUMENTCONTROL ....................................................................................................................II
Change Record......................................................................................................ii Reviewers..............................................................................................................ii Distribution............................................................................................................ii

TABLEOF CONTENTS ....................................................................................................................III 1 PROJECTBACKGROUND .............................................................................................................. 4

1.1 Problem/Opportunity Description....................................................................4 1.2 ene!its............................................................................................................4

1." #oals...............................................................................................................4 1.4 $ta%eholders and Clients.................................................................................4

2 PROJECTSCOPE .......................................................................................................................... 5
2.1 Ob&ectives........................................................................................................' 2.2 Deliverables.....................................................................................................' 2." Out o! $cope....................................................................................................(

3 PROJECTPLAN ............................................................................................................................7
".1 )pproach and *ethodology.............................................................................+ ".2 Pro&ect ,imeline...............................................................................................+ "." $uccess Criteria...............................................................................................+ ".4 -ssues and Policy -mplications.......................................................................... ".' Ris% *anagement Plan..................................................................................... ".( $ervice ,ransition............................................................................................/ ".+ Options )nalysis............................................................................................../

4 TECHNICALFEATURES ............................................................................................................... 10 5 PROJECTORGANIZATIONANDSTAFFING .....................................................................................11 6 PROJECTBUDGET ......................................................................................................................13 7 APPENDIXA- ADDITIONALINFORMATION ..................................................................................... 14

ProjectCharter

iii

"

Project #ac$ground
"%" Problem&Opportunity Description
Business Permit and Licensing %&&ice is a de'artment in (ue)on *ity +a,, t#at 'rocess business 'ermits every -or. day! $#e BPL% De'artment is current,y &o,,o-ing a sc#eme t#at t#ey ca,,ed B%SS or t#e Business %ne Sto' S#o'! $#e B%SS #as &ound out to be e&&ective but not t#e &u,, e/tent! $#e de'artment can a,so 'rocess in e&&ect o& about 20 'ermits a day -#ic# can be adjusted to a more 'ro&itab,e number i& t#ey do #ave an on,ine system t#at cou,d avoid c,erica, res'onsibi,ities on t#eir end!

"%' #enefits
$#e bene&it o& #aving an on,ine system is t#at it more c,erica, res'onsibi,ities on em',oyees! 0it# t#e 'ro'osed Business Permit and Licensing System not on,y t#e -or. -i,, be ,essen but a,so it can ma/imi)e t#e issuance o& 'ermits in a sing,e day! $#e current system -#ic# is ca,,ed Business %ne Sto' S#o' can 'rocess about 10 'ermits at most, our 'ro'osed system envisions ma.ing it 200 'ermits a day! "nd c,ients can a,so #ave t#eir transaction sc#edu,e &or a s'eci&ic day! $#e Business Permit and Licensing System -i,, a,so be integrated a,ong -it# ot#er L23 systems!

"%(

)oals

$#e main objectives o& t#e Business Permit and Licensing System is to ma/imi)e t#e issuance o& 'ermits and to ma.e ,i&e easier not on,y &or c,ients but &or em',oyees as -e,,!

"%* Sta$eholders and Clients

$#e sta.e#o,ders &or t#e Business Permit and Licensing System are t#e em',oyees in t#e BPL% de'artment, t#e business 'erson -#o -is#es to #ave business 'ermits and system administrators!

ProjectCharter

'

Project Scope
'%" Objectives
$#e 'ro'osed 'roject #as sti,, t#e same 'rocesses -it# t#e o,d system! But t#ere -as an additiona, 'rocess &or t#e 'ro'osed system t#e sc#edu,ing! $#is is very im'ortant on bot# c,iente,e and em',oyee because t#is can so muc# time! 0#i,e t#e average t-enty a'',ications 'er norma, day is good it -i,, be a ,ot better i& t#e ne- system can im'rove t#e current average a'',ications t#ey can ac#ieve! $#e &o,,o-ing are t#e sco'e o& t#e 'roject! %n,ine "'',ication, t#e on,ine a'',ication -i,, re',ace t#e '#ysica, 'a'er t#at Business %ne Sto' S#o' introduces! 4rom t#e 'revious ro,e o& t#e '#ysica, 'a'er being encoded it -i,, no- be straig#t into t#e records &or id,e 'rocessing! Sc#edu,e eri&ication, t#e sc#edu,e veri&ication -i,, serve as t#e c,aim stub &or a'',icants! %nce t#e system #as #ad t#eir in&ormation success&u,,y recorded, #e -i,, t#en receive a noti&ication and a c,aim stub a,ong -it# #is sc#edu,e via emai,! $#e researc#ers are ,oo.ing &or-ard to t#e 'ossibi,ity t#at ten c,iente,es can be 'rocessed 'er #our -#ic# means t#ey can average &or more t#an t#e 'revious,y 'rojected! 5ns'ection, it is e/'ected t#at t#e ins'ectors o& t#e BPL% De'artment are very good -it# t#eir s'eci&ic job! 0#at t#e researc#ers &oresee is to #ave a service -#ere ins'ector cou,d easi,y ,ocate &or t#e '#ysica, ,ocation o& t#e business via 2oog,e 6a's! 0it# t#is .ind o& &eature, t#e ,ocation cou,d be easi,y trac.ed do-n and t#e ins'ector cou,d easi,y do #is job! "ssessment, a ne- business is associated a,ong -it# assessment &orm &i,,ed out by a BPL% o&&icer! 5n t#e 'ro'osed system by t#e researc#ers, businesses can easi,y be assessed -it# t#e assurance o& saving it immediate,y as -e,,! 7e,easing o& Business Permit, & a,, t#e re8uirements #ave been success&u,,y met, t#e business #as a,ready been assessed ,ega,,y t#e &ina, 'rocess -i,, be t#e re,easing o& business 'ermit!

'%' Deliverables
Objective " 9 %n,ine "'',ication
Project Deliverable
%n,ine "'',ication

+or$ Products&Description
4i,,ing out t#e in&ormation a,idates sc#edu,e :mai, eri&ication

ProjectCharter

'

Objective ' 9 Sc#edu,e

Project Deliverable
Sc#edu,e

+or$ Products&Description
*on&irms sc#edu,e 7eceives veri&ication via emai,

Objective ( 9 5ns'ection
Project Deliverable
5ns'ection

+or$ Products&Description
Sends mission order Per&orms ins'ection and ',ace &indings!

Objective * 9 "ssessment
Project Deliverable
"ssessment

+or$ Products&Description
:m',oyee assess t#e business 2ives t#e re8uired 'ayments

Objective , 9 7e,ease
Project Deliverable
7e,ease

+or$ Products&Description
:m',oyee re,eases t#e 'ermit Permit issued -it# date o& e/'iration

'%( Out of Scope

0#i,e an on,ine system is a good im'rovement, it -ou,d be nicer i& t#e system can #ave S6S noti&ication and "ndroid a'',ication! +o-ever due to t#e time o& deve,o'ment t#e 'ro'onents decided to e/c,ude t#at &eature in order to &ocus more on t#e re8uirements o& t#e main system and its integration to ot#er L23 systems

ProjectCharter

Project Plan
(%" Approach and -ethodology
5n order to &inis# t#is system on time, t#e 'ro'onents divide t#e tas.s at #and and 'rioriti)e on com',eting t#e de,iverab,es de'ending on t#e dead,ine set! $#e 6S Project is a,so used to monitor t#e accom',is#ment statuses o& t#e de,iverab,es! $#ere is no need to 'urc#ase additiona, #ard-are since a,, t#e team members #ave t#eir o-n mac#ine to be used! "ny additiona, in&ormation needed may come &rom ot#er teams but on,y regarding t#e integration among t#e systems!

(%' Project !imeline

3sing t#e tem',ate 'rovided be,o- or 'roject ',anning so&t-are, indicates t#e tas.s necessary to com',ete t#e 'roject! $#e recommended 'roject ',anning so&t-are is 6icroso&t Project &or 0indo-s!
.D
1 2 3 1 ; > = < 9 10 11 12

!as$

ame

Start
Dec! 2 Dec! 11 4eb! 11 4eb! 1; 4eb! 1< 20 20 20 21 2; 2> 2>

/inish
11 10 11 1= 19 22 22 22 21 2; 2> 2<

Duration
12 ;< 3 2 1 2 2 2 ? ? ? 2

System Design Systems Deve,o'ment Per&orm 5ntegration $esting Deve,o' 6anua, P,an "cce'tance $est *onduct "cce'tance $est Deve,o' $est 7evieDeve,o' 5nsta,,ation P,an Site Pre'aration P,ot 5nsta,,ation Provide 3ser Su''ort Provide $raining

(%( Success Criteria

System va,idation -i,, test t#e system &or its usabi,ity to t#e users, and t#ere&ore needed &or t#e 'artici'ation o& t#em in &e- stages o& tests@va,idations! ",, resu,ts -i,, be enumerated a&ter testing and bugs -i,, be addressed according,y -#at is needed!

ProjectCharter

$esting o& every &unctions o& t#e system -i,, be done: 1! 4i,,ing out o& a'',ication &orm 2! a,idates &or t#e sc#edu,e i& it #as not reac#ed t#e ma/imum number o& a'',icants 'er day! 3! 7eceives con&irmation via emai,! 1! :m',oyee va,idates &or t#e c,ient! ;! a,idating t#e submitted re8uirements! >! "ssessing and 'aying o& t#e re8uired &ees! =! 7e,easing and issuance o& 'ermits!

(%* .ssues and Policy .mplications

Li.e a,, ot#er L23 systems t#e Business Permit and Licensing System -i,, be integrated and be treated as one!
Ris$ /actor
0rong data entry Bdata ty'eC 0rong username@'ass-ord

Probability 012-234
6 6

.mpact 012-234
6 +

Ris$ -anagement Action

Dis',ay understandab,e error message a,idation

$#e deve,o'ers o& t#e 'ro'osed system -i,, ma.e a +e,' Des. &eature as -e,, but -i,, try to vie- i& it #as a contrasting e&&ect -it# a se'arate system named +e,' Des. System!

(%, Ris$ -anagement Plan

5denti&y any &actors t#at can a&&ect t#e outcome o& t#e 'roject inc,uding major de'endencies on ot#er events or actions! $#ese &actors can a&&ect de,iverab,es, success, and com',etion o& t#e 'roject! 7ecord anyt#ing t#at can go -rong!
Ris$ /actor
Members Availability

Probability 012-234
+

.mpact 012-234
6

Ris$ -anagement Action

:nsure t#at s'eci&ication@ overvie- documents contain su&&icient in&ormation to a,,o- every member to understand t#e system! Pro'er,y designate tas.s according to memberAs e/'ertise! Brea. 'roject into sma,,er segments to ensure

Members Skills Sc#edu,e

L 6

+ +

ProjectCharter

sc#edu,e being maintained! *ost *#ange *ontro, 6 6 + 6 7evie- costing to ensure t#at a,, activities -i,, be re&,ected! :nsure t#at a c#ange contro, 'rocess is estab,is#ed t#at ,imits c#anges to essentia,s!

De&ine #o- ris.s -i,, be identi&ied and t#e 'rocess &or esca,ation! 5denti&y t#e e/'ected ris.s to -#ic# t#e 'roject -i,, be e/'osed! "ssess t#e ,i.e,i#ood o& eac# ris. occurring B'robabi,ityC and its im'act on t#e 'roject! %ut,ine a ',an &or managing t#e ris.sD inc,ude ris.Eminimi)ation measures and contingency ',ans &or recovery and damage ,imitation! 7ate eac# ris. 'robabi,ity and im'act as +Big#C, 6BediumC or BLCo-!

(%5 Service !ransition

During testing, veri&ication o& t#e system &unctiona,ities is considered! 0#i,e any c#anges suggested by t#e c,ient -i,, be care&u,,y studied and decided u'on by t#e team members de'ending on t#eir assessment! +o-ever any 8uestions and c,ari&ications regarding t#e &unctiona,ities o& t#e system can be addressed to t#e deve,o'ers during testing!

(%6 Options Analysis

5 Collaborations across the other warehousing system and 78tending or enhancing e8isting tools or services9 660S ,everaging to im'rove t#e systems &unctiona,ities, &eatures and to meet t#e c,ientAs e/'ectation!

ProjectCharter

* !echnical /eatures
$#is section 'rovides a detai,ed descri'tion o& tec#nica, re8uirements stated in terms suitab,e to &orm t#e basis &or t#e actua, design deve,o'ment and 'roduction 'rocesses o& t#e 'roject #aving t#e 8ua,ities s'eci&ied in t#e o'erationa, c#aracteristics!

1ardware Re:uirements9 1ARD+AR7 7"6 Processor +ard Dis. Software Re:uirements9 SO/!+AR7 %'erating System B%SC Language B4ront :ndC Database BBac. :ndC Fava 6yS(L R7CO--7 D7D 0indo-s = 2;> 6B 6inimum 20 2B R7CO--7 D7D Pentium 1 or more

ProjectCharter

10

, Project Organi;ation and Staffing

3sing t#e tem',ate 'rovided, an organi)ation c#art, or bot#, ,ist t#e ro,es, names, and res'onsibi,ities o& individua,s t#at -i,, be invo,ved in t#e 'roject! 5& a''ro'riate, inc,ude 'ercentage o& time and start@end dates! 5nc,ude as a''ro'riate, t#e 'roject governance! $o -#om does t#e 'roject manager re'ortG 0#at grou' or individua,s ma.e recommendationG 0#o ma.es t#e &ina, decisions &or t#e 'rojectG De&ine a decision esca,ation 'rocess!
RO37
:/ecutive S'onsor

A-7S < CO !AC! . /OR-A!.O

R7SPO S.#.3.!.7S
Serve as u,timate aut#ority @ res'onsibi,ity &or t#e 'roject Provide strategic direction and guidance "''rove c#anges to sco'e 5denti&y and secure &unding

!.-7

Project S'onsor

6a.e business @ a''roac# decisions &or t#e 'roject Partici'ate in .ey activities 6a.e resources avai,ab,e "''rove -or. 'roducts, address issues, and a''rove c#ange re8uests

Project 6anager

Price "nt#ony Pagurayan

7e'ort to and receive direction &rom s'onsors 6anage, revie-, and 'rioriti)e 'roject -or. ',ans Provide status re'orts 6anage 'roject team 7ecommend c#anges, esca,ate issues, and mitigate ris.s

Project $eam and 6embers

*#ar,ie PereHa Fo#n Bryan Li'a,am

Partici'ate in 'roject activities, inc,uding ',anning, im',ementation o& de,iverab,es, and 8ua,ity contro,

"dvisors and 7esources

ProjectCharter

11

ProjectCharter

12

5 Project #udget
3sing t#e se'arate 6S :/ce, Project Budget tem',ate, estimate t#e 'roject costs! 5nc,ude one time and 'ermanent costs &or 'ersonne,, consu,ting, #ard-are, so&t-are, and ot#er costs Btraining, consu,tants etc!C as a'',icab,e!
#udget .tem
One2!ime Costs Personne, *osts Summary o& t#e tota, 'ersonne, costs !otal One2!ime Costs Ongoing Costs Summary o& t#e NonE'ersonne, costs +ard-are So&t-are 2=,100!00 1<,2;0!00 1,=00!00 !otal Ongoing Costs *6=(,>%>> 1<,>01!32 1<,>01!32

Description

#udgeted Cost

ProjectCharter

1"

6 Appendi8 A2 Additional .nformation

"dditiona, re,evant in&ormation may a,so be inc,uded in t#is re8uest! $#is in&ormation -i,, be used to decide i& 1C t#e 'roject re8uest is a''roved to move &or-ard to t#e 'roject c#arter '#ase and 2C t#e 'roject c#arter receives a''rova, as an a''roved 5$ 'roject!

ProjectCharter

14