Rd-011 Future Process Model Sc Orm

OUM

RD.011 FUTURE PROCESS MODEL Sify Technologie Technologiess Limited Limi ted Serice Contr!ct"ORM #$siness C$stomi%!&on

'$thor(

)rishn!*$m!r

Cre!&on D!te(

M!y +1, -01

RD.011 Future Process Model

1

Doc Ref: RD)030*C+RR,-&*PROC,SS*Service Contract*v 1.0.doc

DOCUMENT CONTROL

1.1

Change Record -ﾧ

Date

1."

Na$e

Author

Verson

Change Re!erence

3'$thor4

Dr!5 1!

o Preio$s Doc$ment

Reve#ers

%os&on

RD.011 Future Process Model


Contents

1

Docu$ent Control............................................................................................................. 

1.1 1.-

Ch!nge Record........................................................................................................................... .ii Reie6ers................................................................................................................................... .ii

"

'ntroduc&on...................................................................................................................... 1

3

(uture )usness %rocess (lo# Dagra$ !or ............................... "

*

(uture )usness %rocess Descrp&on + %rocess Na$e......................................................... ,

-

A' %rocess %an %onts.................................................................................................... *

/

Open and Closed 'ssues................................................................................................... 1,

7.1 7.-

O/en 8ss$es............................................................................................................................... 1+ Closed 8ss$es............................................................................................................................. 1+


"

'NTRODUCT'ON This doc$ment /resents the F$t$re Process Model constr$cted for the Sify #$siness '$tom!&on for Serice Cont!ct !nd ORM 9Order Reision Mod$le:. The F$t$re Process Model doc$ments the triggering eents th!t drie the ;$siness !re!s th!t !re to ;e !$tom!ted !nd descri;es the f$t$re ;$siness /rocess th!t the ;$siness e
Serice Contr!ct Mod$le

-.

Order Reision Mod$le 9O'F P!ge:

+.

Conc$rrent Progr!ms 

Sify Serice Contr!cts Order C!/t$re 8ntegr!&on Progr!m



Sify Serice Cont!rct U/d!te T!;le Conc Progr!m



Serice Contr!cts Order C!/t$re 8ntegr!&on 9o;solete:



Serice Contr!cts Order Re/rocessing Progr!m 9o;solete:



Sify O-S DFF 8ntegr!&on



Serice Contr!ct #illing Progr!m


3

(UTURE )U'NE %ROCE (LO0 D'ARAM (OR 2)U'NE AREA NAME3

Service Contract with ORM File Ref: 35!!"#"5.doc $v. '

Docu(ent Control

ii


*

(UTURE )U'NE %ROCE DECR'%T'ON + %ROCE NAME

)usness Re4ure$ent De5n&on 'D


A ' %rocess Descrp&on

olu&on Mappng

(re4uenc6

Docu(ent Control

ii


-

A' %ROCE %A'N %O'NT

)usness Re4ure$ent De5n&on 'D

A ' %rocess Descrp&on


olu&on Mappng

(re4uenc6

Docu(ent Control

ii


Le!/ ye!r c!lc$l!&on in Serice Contr!ct. Ref. Le!/ =e!r C!lc$l!&on

SC"PP"001

+ Reg$l!r

Secific custo(er havin/ two lins $one is 1st 2an 01# to 31st Dec 01 another one is 1st %r 01# 4 31st Mar 01' for %r)Ma)2un invoice a(ount are var for 6oth the lins due to lea eriod $das'. Custo(er did not a/reein/ this variation.

1: C$stomi%e the st!nd!rd !nd m!*e it def!$lt n$m;er of d!ys irres/ec&e of the ye!r !s +7?.

Perfor(ance issue while runnin/ re7uest set of Concurrent Pro/ra(s:

eed to chec* the systemAs gener!l /erform!nce



SC"PP"00-

System c!lc$l!tes le!/ ye!r !s /er the or!cle st!nd!rd. >e c!nnot ch!nge this st!nd!rd /rocess.

  

-: O/&m!l 6!y is ho6 they !re h!ndling c$rrently. Thr$ De;it memo they !re h!ndling the di@erence of !mo$nt. Reg$l!r

Disc$ssed 6ith cl To Chec* in R1-

Service Contract order cature 8orflow 6ac/round rocess Service Contracts Main 9illin/ ro/ra(

L!ter 6ill t!*e c!l

%uto nvoice Master Pro/ra(

For ;on/ &er( Contract Sif wants to cature different Price for each ear.

Since Serice contr!ct is gener!ted from OM, !nd !lso 8R d!te inoled, 6e c!nnot cre!te m$l&line contr!ct in OM.

Reg$l!r

F$nc&on!l 8n/$t CR

SC*PP*003

SC*PP*00!

%fter Service contract scheduled then the sste( is not allowin/ the user to (odif the details. %ll Service contract $&e ) Contract %roval' does not carr Contract
SC*PP*005

Contract rice defined as +SD not /enerated until 3Ao cloc due to currenc conversion

SC*PP*00#

Prorated values for Fi=ed orders in ORM


C$rrently they !re $sing thr$ Price Reision /rocess in ORM for cre!&ng !ddi&on!l ye!rs of contr!ct. &hru >Sif SC %rover? in the worflow notifications user selects all the worflows sa 1000 nos. &hen the have to /ive >%roval? for one 6 one 6 ressin/ >%rove? 6utton. %fter arovin/ this.

Reg$l!r

Possi;ili&es.

Sif SC +ser also receivin/ 1000 notifications then the have to select all and ress >@es? 6utton one 6 one to co(lete the notification rocess. &he need to Su6(it %rove 6 ressin/ one sin/le 6utton. +SD Conversion as to 6e inte/rated with Oracle sste( Sif ORM OPB +ser: ,=istin/ lin with new activit. f the Order &e is Oen then the user can a6le

eed to chec* th

Reg$l!r

SO' Technology

Moder!te

B

Docu(ent Control

ii


to chan/e the SC start date 6ased on the start date the end date will 6e adusted with the sa(e SC a(ount. 9ut if the Order &e is Fi=ed then the user can a6le to chan/e the SC start date 6ased on the start date the end date cannot 6e adusted so the SC a(ount has chan/ed accordin/l 6ased on nu(6er of das. Currentl the calculation is worin/ fine so(e ti(e it?s not calculatin/ correctl.. the don?t have sa(le data also to verif. Multile level of aroval for rice revision need to si so(e aroval.

SC*PP*00

For Price Revision Sales tea( raised %rover re7uest to RM $%rover 1' &hen it flows to followin/ aroval rocess ' Sif ORM %rover 3' Sif ORM OPB user $9illin/ &er(' !' Sif ORM OPB arover 5' Sif ORM OPB R +ser $SC creation'

Reg$l!r

?

Reg$l!r

?

-eed to chec ORM alication.

Moder!te

B

-eed to chec ORM alication.

Moder!te

B

Once RM aroved it /oes to ORM %rover $arover ' $6illin/ tea(' then it (oves to ORMEOPB user $arover 3' in the 3rd %roval the are selectin/ fro( the ;O< 6efore arovin/. -ow the need to re(ove an one level of aroval. +ser didn?t confir( so far.

SC*PP*00"

SC*PP*00 SC*PP*010

SC"PP"011

9ul Price revision for 50E100 lins in sin/le re7uest. -eeds to ena6le the co(lete sin/le otions to co(lete entire lin Price Revision sin/le clic 500E1000 n the ORM re7uest so(eti(es ;in id Reflectin/ twice in ORM n the ORM re7uest so(eti(es active ;in D?s are not reflectin/ in ORM 9illin/ schedule attern should 6e defaulted to Pa(ent ter(s.


-eed to chec sste( erfor(ance while select (ore nu(6er of lins and su6(it

%t Sif ORM Suer +serGSif ORM OPB +ser

+

9illin/ schedule has to 6e cature as er e=istin/ a(ent ter(s.

M!//ing det!ils Re$ired Docu(ent Control

ii


SC*PP*01

SC*PP*013

f Service re7uest is oen the e=istin/ contract is not /ettin/ ter(inated. -eed to chec with heldes to close the ta/ $thru (ail follow u is haenin/'. 9ut the user needs a rovision to ter(inate the Service contract even thou/h the Service re7uest e=ists. n case of renewalEu/radeEshift Edown/rade etc. &he old contract is not chan/ed to ter(inate if an service re7uest is endin/ for that contract. Further if the lin itself is hsicall ter(inated need feature to o u (essa/e if an service re7uest availa6le and user should have rivile/e to override the (essa/e to close the service re7uest and cancel order accordin/l. -ew functionalit re7uired at the ti(e of new re7uest creation in ORM for shift last (ile cases i.e fro( wireless to ;;EFi6er etc.. all the activeE ,=istin/ recurrin/ char/es has to oulate auto(aticall instead of enterin/ (anuall. -eed a rovision in ORM screen to e in the Recurrin/ char/es lie O&C for shift last (ile cases.

n 9 if ou ut ,nd date for the instance it is not ter(inated since SR is associated with this te(. 9ut new SC has created without an ou.

B

-eed ou if an SR is associated with SC. .

-eed one >;ast Mile? 6utton in ORM Sales +ser resonsi6ilit. Provide chec 6o= for Ports $laer  and laer 3' and Details. Once select Port and Details chec 6o= and su6(it it should 6e create Order in OM.

?

's One Time !c&ity cre!tes S!les order from ORM, the s!me they need for L!st MileA

SC*PP*01!

,=istin/ contract e=ir on ")Fe6)01. &he Custo(er Provided the PO for an u/rade on 5th Fe6 01 the ORM re7uest will 6e created and then interface to Fusion for e=ecution. &he deliver tea( e=ecutes the activit and then su6(its the R on th Mar 01 in this case (anuall creatin/ the invoice fro( 01 (ar 01 to 0#th Ma 01.

E
Service contract standard >,=tend? otion to 6e ena6led and chec the feasi6ilit of udate with ORM Service Contract end date or create new field called >,=tension Date? and udate the new SC e=tend date.

Sol$&on they !re !s*ing  F$nc&o Sol$&on

-eed to chec the feasi6ilit of renewin/ e=istin/ contract H old rice till u/radeEshift etc. Order is i(le(ented H custo(er location. Sste( to tae care of ter(inatin/ e=istin/ contract 6ased on lin id. , lse to validate the contract e=ir date with threshold of 30 das while lo/in E su6(ission of ORM re7uest. SC*PP*015

+na6le to do %uto ,=tension of Contracts with an ,=istin/ Rates $Service Contracts (odule'

F$nc&on!l sol$&

-eed to chec the in Service Contract

SC*PP*01# +na6le to do renewal of Contracts which is in 8or in Pro/ress $8P' Service Contract with ORM File Ref: 35!!"#"5.doc $v. '

F$nc&on!l sol$&

f the lin have renewal 6ut the sste( shows >Pendin/ for (le(entation? as the ;ine status. &his is 6ecause PMB tea( needs to 6e udated Docu(ent Control

ii


R infor(ation for that lin once R date udated in ORM then onl the status will 6e chan/e >Read for (le(entation?. &hen the user will do the Renewal. 9etween the status chan/es there will 6e renewal for that lin since the status showin/ >Pendin/ for (le(entation? the user cannot do the renewal. So the user should have fle=i6ilit to do the renewal if the status is in >Pendin/ for (le(entation?


Docu(ent Control

ii


Schedule nvoice date and nterface date (anual Ie in $offset das' in SC. -eed to auto(ate. SC*PP*01

O@set d!ys  for /erson!li%!&on

Chec the feasi6ilit while creatin/ SC fro( OM at the ti(e of SC creation $set of concurrent ro/ra(s' need to ut conditions for these dates $nor(all !5 das' fro( the SC start date. 9ut while creatin/ SC fro( ORM these offset das are oulated auto(aticall thru Jsif*sc*ter(inate*chr? this rocedure. 8e can validate this and acco((odate to our needs.

9ul the rice revision in ORM. SC*PP*01"

simil!r /oint 

Sa(e as SC*PP*00"

f the rice re7uests are (ore than one it?s difficult to enter (anuall each re7uest hence need rovision to create rice revision a re7uest in 6ul. ,=cel uload otion should 6e availa6le durin/ ORM Re7uest creation

SC*PP*01

For the Service Contract te JFi=edK rorate calculation the sste( is not calculatin/ correctl 6 default oulatin/ the start date as R date and end date is oulated default with 1 ear. &he user is (anuall co(utin/ the dates and rovidin/ the dates. Provision to 6ill the eriod with old rice till the R is o6tained uon contract e=ir. Manual invoice ro/ra( need to 6e run on Dail 6ases.

SC"PP"0-0

Sa(e as SC*PP*00#

simil!r /oint 7

One ti(e nvoice /eneration and Recurrin/ nvoice /eneration should 6e scheduled on dail 6asis. f concurrent status co(leted with ,rror the user needs to fire e(ail re/ardin/ the lo/ error.

Conc$rrent Sched$ling >ith em!il o&G  ? D!ys

n ORM Service Contract %roval one 6 one

Sa(e as SC*PP*00!

>or*Ho6 ModiG

SC"PP"0-1

SC"PP"0--

St!nd!rd Fe!t$re to chec* the /os -eed auto udate for Sales credit otion


Once SC created fro( OM then in the Su((ar $&'GParties /o to &oolsGSales credit the sales erson na(e auto(aticall udated fro( OM. 9ut at the line level select the ite( and &oolsGSales credits there the sales erson is not udated. For each line ite( user enterin/ (anuall. -eed to Docu(ent Control

! ii


udate this sales credit infor(ation at the line level.


Docu(ent Control

ii


SC"PP"0-+

For the rice revision ORM re7uest the 9illin/ attern details are entered 6 the user each line (anuall. &he user is e=ected to oulate the 9illin/ Pattern details fro( the e=istin/ service contract.

SC"PP"0-B

8hile doin/ ;in Disconnections we re7uire POP u to 6e shown for >,=istin/ Oen Orders? details also if the lin disconnection is for Pri(ar let sste( also as the tea( to chec on the Secondar ;ins Status or an SD-E;ast (ile ;ines also if this has 6een ta//ed as Sin/le ;in. Currentl the &ea( is doin/ disconnections onl which are lo//ed in SF%. Lowever ero Co((ercials Disconnections are not re/ulariNed 6 Re/ions  OPB.

SC"PP"0-?

Sales tea( creatin/ the disconnection re7uest in (ultile ti(es in the sste(. Dulication re7uest for er(anent disconnect for sa(e lin id is allowed and no validation haens. &his needs to 6e fi=ed.

&hru Sif ORM OPB +ser 7uer the re7uest id for rice revision or other new activit  there is one field called >9illin/ schedule? its nothin/ 6ut a(ent ter( which is availa6le in the lin details a/e. &his a(ent ter( should 6e udated auto(aticall in the >9illin/ Schedule? field

B

Sif 9 user

?

f the user ter(inate the >;in? thru nstall 9ase need ou if an Oen Orders are there a/ainst that ;in.

&hru Sif uotin/ +ser$;in cancellation re7uest the user can find the lin id for cancellation. Once noted the lin id thru 9 the user ut end date a/ainst that lin id and cancel the lin. 9ut a/ain if ou if ou /o chec Sif 7uotin/ user $ lin cancellation re7uest the lin id is availa6le a/ain for cancellation.

?

-eed so(e condition in the ;in cancellation re7uest for(.

SC"PP"0-7

&he sste( is not allow the user to udate the 6ac dated disconnection details in the service re7uested. Sste( validation for 6ac dated lin disconnection in SR $service re7uest' in CRM (odule

SC"PP"0-

f the service re7uest is oen then the sste( is not allowin/ the user to udate the disconnection details in the nstall 6ase.

SC"PP"0-

For lin revival rocess notification to 6e tri//ered to CP, Co((ercials lease of last (ile Lel Des %sset Recover &ea( and Fusion &ea( 6ased on the threshold in revival window

SC"PP"0-I

8hile cancellin/ the lin renewalEu/radeEshift etc. 6efore R accetance sta/e there should 6e rovision to enter the reason for cancellation and it should 6e (andator

SC"PP"0+0

-ew functionalit re7uired at the ti(e of new re7uest


-ot needed.

Currentl ,rror ous 6ut not allow to close the connection. 9ut the user needs to allow for close the connection and should fire the (ail to Leldes to close the SR a/ainst the ;in %t OM level once order 6ooed for ;in Revival the (ail to fire to the (entioned /rous

B

&hru Sif ORM OPB R user 7uer the re7uest id there user can find S C Status 4 %ctiveECancel. f user wants to cancel the lin the need fields to cature the cancellation reason. Sa(e as SC*PP*013

?

Docu(ent Control

?

ii


SC"PP"0+1

SC"PP"0+-

SC"PP"0++

creation in ORM for shift last (ile cases i.e fro( wireless to ;;EFi6er etc.. all the activeE ,=istin/ recurrin/ char/e has to oulate auto(aticall instead of enterin/ (anuall. -eed a rovision in ORM screen to e in the Recurrin/ char/es lie O&C for shift last (ile cases. &he ORM re7uested is created 6efore e=ir the contract eriod. &he OPB tea( validated the ORM re7uest and reected the re7uest the sales tea( will resu6(it the re7uest after (odifin/ the details. 9ut the Service contract has e=ired at the ti(e of resu6(ittin/ the sste( is not validatin/ the contract e=ir date and allow for the sales tea( to su6(it the re7uest. For the Service Contract te JFi=edK rorate calculation the sste( is not calculatin/ correctl 6 default oulatin/ the start date as R date and end date is oulated default with 1 ear. &he user is (anuall co(utin/ the dates and rovidin/ the dates. Provision to 6ill the eriod with old rice till the R is o6tained uon contract e=ir %n chan/eE (odifications in the custo(er na(e chan/e there is no histor availa6le for the chan/es. &he user wants to audit trail for the custo(er (aster. n case if custo(er sells sa 100 lins to their artners in such case we need to transfer onl those 10 lins to new custo(er. -eed feature in alication to swa onl those 10 lins to new custo(er


Contract e=ir date validation is re7uired at the su6(ission lus resu6(ission of ORM re7uest for aroval in addition to validation H ti(e of creatin/ ORM re7uest

S!me !s SC"PP"007

%R related

8n the st!nd!rd f$nc&on!lity the history for n!me

Docu(ent Control

ii


/

O%EN AND CLOED 'UE

/.1

Open 'ssues

'D

'ssue

SC"PP"0-7

&he sste( is not allow the user to udate the 6ac dated disconnection details in the service re7uested. Sste( validation for 6ac dated lin disconnection in SR $service re7uest' in CRM (odule f the service re7uest is oen then the sste( is not allowin/ the user to udate the disconnection details in the nstall 6ase.

SC"PP"0-

/."

'D

Resolu&on

Respons7lt6

Target Date

'$pact Date

Closed 'ssues

'ssue


Resolu&on

Respons7lt6

Target Date

'$pact Date

Docu(ent Control

ii

Rd-011 Future Process Model Sc Orm

Recommend Documents