You are on page 1of 16

OUM

RD.011 FUTURE PROCESS MODEL


Sify Technologies Limited
Service Contract_ORM Business Customization

Author: Krishnakumar
Creation Date: May 31, 2017
Last Updated: May 31, 2017
Document Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc
Version: DRAFT 1A

Approvals:

<Approver 1>

<Approver 2>
RD.011 Future Process Model Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

1 DOCUMENT CONTROL

1.1 Change Record

Date Author Version Change Reference

<Author> Draft 1a No Previous Document

1.2 Reviewers

Name Position

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. DRAFT 1A )
RD.011 Future Process Model Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

Contents

1 Document Control............................................................................................................. ii
1.1 Change Record............................................................................................................................ii
1.2 Reviewers....................................................................................................................................ii

2 Introduction...................................................................................................................... 1

3 Future Business Process Flow Diagram for <Business Area Name>...............................2

4 Future Business Process Description Process Name.........................................................3

5 ASIS Process Pain Points.................................................................................................... 4

6 Open and Closed Issues................................................................................................... 13


6.1 Open Issues...............................................................................................................................13
6.2 Closed Issues.............................................................................................................................13

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. DRAFT 1A )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

2 INTRODUCTION

This document presents the Future Process Model constructed for the Sify Business Automation for Service Contact and
ORM (Order Revision Module). The Future Process Model documents the triggering events that drive the business areas
that are to be automated and describes the future business process that the business executes in response to each of
those events as a set of one or more activities.

This is covering Sify Service Contract scenario with ORM. Following modules and programs involved in this.

1. Service Contract Module

2. Order Revision Module (OAF Page)

3. Concurrent Programs

Sify Service Contracts Order Capture Integration Program

Sify Service Contarct Update Table Conc Program

Service Contracts Order Capture Integration (obsolete)

Service Contracts Order Reprocessing Program (obsolete)

Sify O2S DFF Integration

Service Contract Billing Program

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

3 FUTURE BUSINESS PROCESS FLOW DIAGRAM FOR <BUSINESS AREA NAME>

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

4 FUTURE BUSINESS PROCESS DESCRIPTION PROCESS NAME

Business Requirement AS IS Process Description Solution Mapping Frequency


Definition ID

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

5 ASIS PROCESS PAIN POINTS

Business AS IS Process Description Solution Mapping Frequency


Requirement
Definition ID

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

Leap year calculation in Service Contract. System calculates leap year as per the oracle 3
standard. We cannot change this standard
Ref. Leap Year Calculation Regular
process.
Specific customer having two links, (one is 1st Jan 2016 to
1) Customize the standard and make it default
31st Dec 2017, another one is 1st Apr 2016 31st Mar
SC_PP_001 2017) for Apr-May-Jun invoice amount are vary for both the number of days irrespective of the year as
links due to leap period (days). Customer did not agreeing 365.
this variation.
2) Optimal way is how they are handling
currently. Thru Debit memo they are handling
the difference of amount.
Performance issue while running request set of Concurrent Need to check the systems general performance Regular Discussed with cl
Programs:
To Check in R12
Service Contract order capture
SC_PP_002 Workflow background process Later will take cal
Service Contracts Main Billing program
Auto Invoice Master Program
For Long Term Contract, Sify wants to capture different Price Since Service contract is generated from OM, and Regular Functional Inputs
for each year. also IR date involved, we cannot create multiline
contract in OM. CR
SC_PP_003
Currently they are using thru Price Revision
process in ORM for creating additional years of
contract.
After Service contract scheduled, then the system is not Thru Sify SC Approver, in the workflow Regular Need to check th
allowing the user to modify the details. All Service contract notifications, user selects all the workflows say
(Type - Contract Approval) does not carry Contract Value, 1000 nos. Then they have to give Approval for Possibilities.
Currency and Contract Period which needs to be included in one by one by pressing Approve button. After
SC_PP_004 notification. Further we need option for mass approval of approving this.
such notification as these are maker-checker case and on an
average we receive around 1000 such notification approx. in Sify SC User also receiving 1000 notifications,
a day. then they have to select all, and press Yes button
one by one to complete the notification process.
They need to Submit Approve by pressing one
single button.
Contract price defined as USD not generated until 3'o clock USD Conversion apps to be integrated with Oracle Regular SOA Technology
SC_PP_005 due to currency conversion system

SC_PP_006 Prorated values for Fixed orders in ORM Sify ORM OPG User: Moderate 4
Existing link with new activity.
If the Order Type is Open, then the user can able
Service Contract with ORM Document Control ii
File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

to change the SC start date, based on the start


date, the end date will be adjusted with the same
SC amount.

But if the Order Type is Fixed, then the user can


able to change the SC start date, based on the
start date, the end date cannot be adjusted, so the
SC amount has changed accordingly based on
number of days.

Currently the calculation is working fine some


time its not calculating correctly.. they dont have
sample data also to verify.

Multiple level of approval for price revision, need to skip For Price Revision, Sales team raised Approver Regular 5
some approval. request to RM (Approver 1)
Then it flows to following approval process
2) Sify ORM Approver
3) Sify ORM OPG user (Billing Term)
4) Sify ORM OPG approver
5) Sify ORM OPG IR User (SC creation)
SC_PP_007
Once RM approved, it goes to ORM Approver
(approver 2) (billing team), then it moves to
ORM/OPG user (approver 3), in the 3rd Approval,
they are selecting from the LOV before approving.

Now, they need to remove any one level of


approval. User didnt confirm so far.

SC_PP_008
Regular 5
Need to check system performance while select
Bulk Price revision for 50/100 links in single request. Needs more number of links and submit
to enable the complete single options to complete entire link
Price Revision single click 500/1000
In the ORM request, sometimes Link id Reflecting twice in Need to check ORM application. Moderate 4
SC_PP_009
ORM

SC_PP_010 In the ORM request, sometimes active Link IDs are not Need to check ORM application. Moderate 4
reflecting in ORM
Billing schedule pattern should be defaulted to Payment At Sify ORM Super User>Sify ORM OPG User 3
terms.
SC_PP_011 Billing schedule has to be capture as per existing Mapping details
payment terms.
Required
Service Contract with ORM Document Control ii
File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

If Service request is open, the existing contract is not getting In IB, if you put End date for the instance, it is not 4
terminated. Need to check with helpdesk to close the tag terminated since SR is associated with this Item.
(thru mail follow up is happening). But the user needs a But new SC has created without any popup.
provision to terminate the Service contract even though the
SC_PP_012 Service request exists. Need popup if any SR is associated with SC.
In case of renewal/upgrade/shift /downgrade etc. The old
contract is not changed to terminate if any service request is .
pending for that contract. Further, if the link itself is physically
terminated need feature to pop up message if any service
request available and user should have privilege to override
the message to close the service request and cancel order
accordingly.
New functionality required at the time of new request Need one Last Mile button in ORM Sales User 5
creation in ORM for shift last mile cases i.e from wireless to responsibility.
LL/Fiber etc.., all the active/ Existing recurring charges has Provide check box for Ports (layer 2 and layer 3)
to populate automatically instead of entering manually. Need and Details.
SC_PP_013 a provision in ORM screen to key in the Recurring charges Once select Port and Details check box and
like OTC for shift last mile cases. submit it should be create Order in OM.

As One Time activity creates Sales order from


ORM, the same they need for Last Mile

Extn- Billing-
Service contract standard Extend option to be
Existing contract expiry on 28-Feb-2017. The Customer Solution they are
enabled and check the feasibility of update with
Provided the PO for an upgrade on 25th Feb 2017 the ORM
ORM Service Contract end date or create new
request will be created and then interface to Fusion for
field called Extension Date and update the new asking Function
execution. The delivery team executes the activity and then
SC extend date. Solution
SC_PP_014 submits the IR on 7th Mar 2017, in this case manually
creating the invoice from 01 mar 2017 to 06th May 2017.
Need to check the feasibility of renewing existing contract @
old price till upgrade/shift etc. Order is implemented @
customer location. System to take care of terminating
existing contract based on link id. Else to validate the
contract expiry date with threshold of 30 days while login /
submission of ORM request.
SC_PP_015 Unable to do Auto Extension of Contracts with an Existing Functional solutio
Rates (Service Contracts module) Need to check the in Service Contract

SC_PP_016 Functional solutio


If the link have renewal, but the system shows
Unable to do renewal of Contracts which is in Work in
Pending for Implementation as the Line status.
Progress (WIP)
This is because PMG team needs to be updated
Service Contract with ORM Document Control ii
File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

IR information for that link, once IR date updated


in ORM, then only the status will be change
Ready for Implementation. Then the user will do
the Renewal.

Between the status changes, there will be renewal


for that link, since the status showing Pending for
Implementation, the user cannot do the renewal.

So, the user should have flexibility to do the


renewal, if the status is in Pending for
Implementation

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

Offset days - form


Check the feasibility, while creating SC from OM,
Schedule Invoice date and Interface date manual Key in
at the time of SC creation (set of concurrent
personalization
(offset days) in SC. Need to automate.
programs) need to put conditions for these dates
(normally 45 days) from the SC start date.
SC_PP_017
But, while creating SC from ORM, these offset
days are populated automatically thru
sify_sc_terminate_chr this procedure. We can
validate this and accommodate to our needs.

similar point 8
Bulk the price revision in ORM. Same as SC_PP_008

SC_PP_018 If the price requests are more than one, its difficult to enter
manually each request, hence need provision to create price
revision a request in bulk.
Excel upload option should be available during ORM
Request creation
For the Service Contract type Fixed, prorate calculation, Same as SC_PP_006 similar point 6
the system is not calculating correctly by default populating
SC_PP_019
the start date as IR date and end date is populated default
with 1 year. The user is manually computing the dates and
providing the dates. Provision to bill the period with old price
till the IR is obtained upon contract expiry.
Manual invoice program need to be run on Daily bases. One time Invoice generation and Recurring Concurrent
Invoice generation should be scheduled on daily
basis. If concurrent status completed with Error, Scheduling
SC_PP_020 the user needs to fire email regarding the log
error. With email Notifi
- 5 Days
In ORM, Service Contract Approval one by one Same as SC_PP_004 Workflow Modific
SC_PP_021
Standard Feature
to check the poss
SC_PP_022 Need auto update for Sales credit option Once SC created from OM, then in the Summary
(T)>Parties, go to Tools>Sales credit, the sales
person name automatically updated from OM. But
at the line level, select the item and Tools>Sales
credits, there the sales person is not updated. For 4
each line item, user entering manually. Need to
Service Contract with ORM Document Control ii
File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

update this sales credit information at the line


level.

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

Thru Sify ORM OPG User, query the request id 4


for price revision or other new activity , there is
For the price revision ORM request, the Billing pattern details one field called Billing schedule, its nothing but
SC_PP_023 are entered by the user each line manually. The user is payment term, which is available in the link details
expected to populate the Billing Pattern details from the page. This payment term should be updated
existing service contract. automatically in the Billing Schedule field

While doing Link Disconnections, we require POP up to be Sify IB user 5


shown for Existing Open Orders details also if the link
disconnection is for Primary let system also ask the team to If the user terminate the Link thru Install Base,
SC_PP_024 check on the Secondary Links Status or any ISDN/Last mile need popup if any Open Orders are there against
Lines also if this has been tagged as Single Link. Currently that Link.
the Team is doing disconnections only which are logged in
SFA. However Zero Commercials Disconnections are not
regularized by Regions & OPG.
Thru Sify Quoting User(Link cancellation request, 5
the user can find the link id for cancellation. Once
noted the link id, thru IB the user put end date
Sales team creating the disconnection request in multiple against that link id and cancel the link. But again if
SC_PP_025 times in the system. Duplication request for permanent you if you go check Sify quoting user ( link
disconnect for same link id is allowed and no validation cancellation request, the link id is available again
happens. This needs to be fixed. for cancellation.

Need some condition in the Link cancellation


request form.
The system is not allow the user to update the back dated
SC_PP_026 disconnection details in the service requested. System Not needed.
validation for back dated link disconnection in SR (service
request) in CRM module
Currently Error popups, but not allow to close the 4
If the service request is open, then the system is not allowing connection.
SC_PP_027 the user to update the disconnection details in the Install But the user needs to allow for close the
base. connection and should fire the mail to Helpdesk to
close the SR against the Link
For link revival process, notification to be triggered to CPE, At OM level, once order booked for Link Revival, 5
SC_PP_028 Commercials lease of last mile, Help Desk, Asset Recovery the mail to fire to the mentioned groups
Team and Fusion Team based on the threshold in revival
window
Thru Sify ORM OPG IR user, query the request id, 5
While cancelling the link renewal/upgrade/shift etc., before
SC_PP_029 there user can find SC Status Active/Cancel. If
IR acceptance stage there should be provision to enter the
user wants to cancel the link, they need fields to
reason for cancellation and it should be mandatory
capture the cancellation reason.
SC_PP_030 New functionality required at the time of new request Same as SC_PP_013

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

creation in ORM for shift last mile cases i.e from wireless to
LL/Fiber etc.., all the active/ Existing recurring charge has to
populate automatically instead of entering manually. Need a
provision in ORM screen to key in the Recurring charges like
OTC for shift last mile cases.
The ORM requested is created before expiry the contract Contract expiry date validation is required at the
period. The OPG team validated the ORM request and submission plus resubmission of ORM request for
rejected the request, the sales team will resubmit the request approval in addition to validation @ time of
SC_PP_031 after modifying the details. But the Service contract has creating ORM request
expired at the time of resubmitting, the system is not
validating the contract expiry date and allow for the sales
team to submit the request.
For the Service Contract type Fixed, prorate calculation, Same as SC_PP_006
the system is not calculating correctly by default populating
SC_PP_032 the start date as IR date and end date is populated default
with 1 year. The user is manually computing the dates and
providing the dates. Provision to bill the period with old price
till the IR is obtained upon contract expiry
Any change/ modifications in the customer name change, AR related In the standard
there is no history available for the changes. The user wants
to audit trail for the customer master. In case if customer
functionality ther
SC_PP_033 history for name
sells say 100 links to their partners in such case we need to
transfer only those 10 links to new customer. Need feature in
application to swap only those 10 links to new customer

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. )
Doc Ref: RD-030_CURRENT_PROCESS_Service Contract_v 1.0.doc

6 OPEN AND CLOSED ISSUES

6.1 Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

SC_PP_026 The system is not allow the user to update


the back dated disconnection details in
the service requested. System validation
for back dated link disconnection in SR
(service request) in CRM module
SC_PP_027 If the service request is open, then the
system is not allowing the user to update
the disconnection details in the Install
base.

6.2 Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

Service Contract with ORM Document Control ii


File Ref: 357448685.doc (v. )

You might also like