You are on page 1of 150

Federal Electricity and Water Authority

REQUEST FOR PROPOSAL


Tender No.
15EW/2009
BIDDING DOCUMENTS
FOR A CONTRACT
TO DESIGN, SUPP!, INSTA, IMPEMENT, TRAIN
AND PRO"IDE SUPPORT SER"ICES
FOR AN ERP AND CRM /BIING SOUTION
ON A TURN#E! BASIS
ANNE$URE B%
APPENDI$ &B
COMPIANCE S'EET
Annex B: Appendix 3B- Compliance Sheet
Page ii of 89
Con(en()
1 Proposed ERP and CRM/Billing Solution1
11 !"erall S#stem Architecture1
1$ Proposed Application Modules and E-Ser"ices %nter&ace$1
13 'ocument Management S#stem3(
1) *unctional/+echnical Re,uirements3)
$ S#stem %nstallation1$$
$1 %nstallation Ser"ices1$$
$$ C-s o& proposed team mem.ers &or S#stem %nstallation1$$
3 S#stem %mplementation1$)
31 %mplementation Approach1$)
3$ 'ata Migration1$/
33 %nter&aces1$0
3) 'ocumentation1$0
31 Bidder Sta&&ing Plan1$2
3/ C-s o& team mem.ers131
30 *E3A team in"ol"ement133
34 *E3A %n&rastructure Re,uirements134
) +raining132
1 Support 5uestionnaire1)1
/ B%''ER !rgani6ation 'etails1)3
/1 Compan# Pro&ile1)3
/$ Re&erence Site 'etails1))
/3 Experience o& implementing in the 7CC/ 8AE and in 8tilities in the 7ul&
region1)1
0 !ther *ormats1)0
01 *orm &or Clari&ication 5uestions1)0
0$ *orm &or 'e"iations &rom R*P1)4
Annex B: Appendix 3B- Compliance Sheet
Page 1 of 89
1 Pro*o)ed ERP +nd CRM/B,--,n. So-/(,on
%t is mandator# &or all .idders and all their related su.contractors and/or partners 9i& an#: to &ill all listed items ;ithin this
document in a detailed &ashion *ailure to pro"ide all the needed in&ormation can result &or immediate dis,uali&ication
1.1 O0er+-- S1)(e2 Ar34,(e3(/re
1.1.1 Gener+- Prod/3( In5or2+(,on
<indl# &urnish in&ormation &or each product / application separatel# in case more than one product / application is o&&ered
S#stem name ERP /( 9Base Product:= SAP *or 8tilities
'ate o& launch 9 7lo.all# and in 8AE : >une 9ERP /(:= SAP &or 8tilities= multiple releases since late 2(?s
'ate ;hen &irst client site ;ent li"e 9 in 8AE : ;ith client name *irst ERP /( clients in $((/ SAP &or 8tilities currentl# under implementation at 'E3A @i"e in
Saudi Ara.ia since $(()
Current "ersion and release date 97A:
+his is the latest "ersion o& our product and ;as released in $((/ Ao;e"er= SAP is e"ol"ing the
SAP ERP maBor release schedule to a &i"e-#ear rh#thm to .etter align ;ith the customer adoption
c#cle +o ensure that customers taCe ad"antage o& inno"ations ;hile minimi6ing the impact to core
operational s#stems= SAP plans to accelerate deli"er# o& ne; &unctionalit# through enhancement
pacCages that customers can optionall# implement on top o& SAP ERP Enhancement pacCages are
intended to contain &unctional enhancements and enterprise ser"ices in areas such as shared ser"ices=
end-to-end .usiness processes such as order to cash or Dhire to retire=D supplier colla.oration= and
industr# speci&ic &unctionalit# +he intent is to deli"er more inno"ation= more ,uicCl#= in a more
accessi.le ;a# SAP is thus ensuring the greatest possi.le protection o& #our in"estments .#
continuing to deli"er high-,ualit# ERP &unctions
Eum.er o&
Clients using the proposed so&t;are in production en"ironment 9 in
8AE:
MaBor clients in 7CC using the proposed so&t;are ;ith details o& #ear o&
implementation
%nstallations in the last &inancial #ear that has .een implemented .#
.idder and contact details
+oda#= more than 4$=((( customers in o"er 1$( countries run SAP applications and the demand &or
the SAP ERP /( application
is especiall# high= and to date more than 1(=((( customers are using it in li"e operation A large
num.er 9$((F: o& customers are using SAP ERP "ersions in the 7CC 3 7CC utilities are li"e ;ith
SAP and 1 is under implementation
@argest customer &or the proposed product
Eame o& the customer
Eum.er o& customer installed accounts 9 acti"e accounts :
+ransaction "olume
Eum.er o& remote site
'R a"aila.ilit# 9 is it hot-stand.# or cold-stand.# :
Please re"ie; the attached excel sheets ;hich list our customer re&erences &or ERP /( and %S-
8tilities
C: \ Users\ C5037555\
Document s\Client s\ FEWA\ References_ERP_6. xls
C: \ Users\ C5037555\
Document s\ Client s\ FEWA\ References_ !_Ut ilit ies. xls
Ao; can the proposed so&t;are .e ac,uiredG 9purchase/lease/other: Purchased
%n case o& licensing= explain so&t;are licensing s#stems schema and cost
structure
@icensing is a mixture o& named user and metrics .ased: SAP ERP is .ased on named users and
priced according to roles SAP CRM +nd B,--,n. 5or U(,-,(,e) is .ased on the num.er o& acti"e
Annex B: Appendix 3B- Compliance Sheet
Page 2 of 89
%s it restricted as to the location o& installation or glo.alG 9 explain the license
mo.ilit# i& its supported :
contracts
+he installation is not restricted +he regions that the so&t;are ma# .e utili6ed in a documented in
the contract
%s the license agreement per site= per CP8= per concurrent user= per named
user= per ser"er licence= per data.ase = per enterprise .asis or com.ined o& a
mix o& the mentioned methodolog# G 9 Please explain in details :
ERP is per named user .ased on role 8tilities tools are licensed .ased on metrics as per the ans;er
to the pre"ious section Some solutions= such as SAP explorer= are also a"aila.le per CP8
%s the source code a"aila.leG Hes
%* the ans;er on the pre"ious ,uestion is #es then please indicate the Escro;
a"aila.ilit# o& the source code
8nder the terms o& the SAP So&t;are End-8ser @icense Agreement= SAP pro"ides application
source code Basis source code is placed in escro; +he escro;ed code can .e made a"aila.le to
SAP customers in the e"ent o& SAP &iling .anCruptc# or going out o& .usiness
%& the proposed product has an# additional &eatures 9 not listed in the R*P :
that ;ill .e use&ul in e"aluating o& the product9s: / solution= then state them
SAP ERP is pro"en= ;orld-class= integrated ERP so&t;are that addresses the core .usiness
so&t;are re,uirements o& the most demanding organi6ations around the ;orld I in all
industries and sectors
3ith )0 countr# "ersions= SAP ERP is a trul# glo.al application used .# organi6ations across
multiple industries= currencies= and accounting standards to support international ;orC&orces
+he SAP strateg# o& gro;th through inno"ation and scope contrasts ;ith the strategies o& some
competitors that tr# to achie"e gro;th through merger and ac,uisition= ;hich can cause
disruption &or customers SAP ERP has a clear product road map that gi"es organi6ations a
choice as to ho; the# ;ant to consume ne; &eatures and &unctionalit# SAP ERP /( is the go-
to release= and ;ith SAP enhancement pacCages= ;e continue to deli"er inno"ation ;ithout
disruption to SAP ERP customers
SAP ERP is .uilt on SAP Eet3ea"er= the SAP technolog# plat&orm that reduces %+
complexit# ;hile supporting scala.ilit# and gro;th
SAP ERP is tightl# integrated to optimi6e cross-&unctional .usiness processes and to ena.le
comprehensi"e colla.oration ;ithin and .e#ond an organi6ation
SAP ERP deli"ers industr#-speci&ic &unctionalit# that supports the .est .usiness practices in
more than $1 industries .ased on SAP?s experience ;ith thousands o& success&ul customers
3ith SAP ERP= companies can implement industr#-speci&ic &unctionalit# easil#
3ith 31 #ears o& pro"en per&ormance and results= SAP has earned the position o& trusted
ad"iser to organi6ations @iCe;ise= SAP ERP has earned its place as the trusted so&t;are
&oundation &or thousands o& glo.al organi6ations
3hat are maBor enhancements are planned in the next $) months
'escri.e an# limitations o& the proposed product 9 i& an# : in term o&
capacit# = num.er o& users= num.er o& transaction= "olume o& 'ata.ase =
languages support 'R support and/or an# other essential &eature
+here are no so&t;are limitations !nl# limitations are A3 and net;orC capacit# SAP solutions are
used .# some o& the largest 8tilities in the ;orld and are "er# scala.le
Annex B: Appendix 3B- Compliance Sheet
Page 3 of 89
3hat is the road map o& the proposed product &or the next 3 to 1 #earsG Please
explain it in details 8se additional sheets i& re,uired
As the ;orld?s leading pro"ider o& .usiness s#stems= SAP has a pro"en tracC record in de"eloping
so&t;are and pro"iding regular upgrades to assist our customers per&orm .usiness more e&&ecti"el#
and e&&icientl# 3e recognise that our customers need to ha"e tools and technologies that pro"ide
&lexi.le .usiness processes and adapti"e .usiness models to ena.le #ou to respond rapidl# to
change= opportunities= and threats
SAP has a clearl# de&ined upgrade path &or all its solutions !"er the past &e; #ears SAP has
adapted its product release strateg# and roadmap o& SAP ERP to deli"er on t;o Ce# componentsJ
simpli&ication and inno"ation ;ithout disruption
%n recent #ears= maBor "ersion releases ha"e included:
)/c A"aila.le since Ma# $(((
)0 A"aila.le since >ul# $(($
ERP $(() A"aila.le since >une $(()
ERP $((1 A"aila.le since !cto.er $((1
ERP / A"aila.le since >une $((/
3e continue to .uild on the success&ul release strateg# o& SAP ERP= in ;hich the core remains
sta.le= ;hile customers recei"e enhancement pacCages that o&&er regular inno"ation on top o& the
.usiness process plat&orm
3hat Are Enhancement PacCagesG
Enhancement pacCages are:
!ptionall# installed and acti"ated so&t;are inno"ations &or SAP ERP /(
So&t;are inno"ations include
8% simpli&ications
*unctional enhancements
%ndustr# speci&ic capa.ilities
Enterprise ser"ices
Cumulati"e in nature: current enhancement pacCages contain entire content o& earlier pacCages
Enhancement pacCages are not support pacCages
SAP enhancement pacCages ;ill .e deli"ered &or all Suite Applications
Enhancement pacCages are released regularl# ena.ling a customer to .ene&it &rom ne;
&unctional enhancements ;ithout ha"ing to per&orm entire s#stem upgrades e"er# couple o&
#ears= ;hich has .een costl# and time consuming in the past
SAP enhancement pacCages ;ill .e deli"ered &or all Suite Applications
Enhancement pacCages are released regularl# ena.ling a customer to .ene&it &rom ne;
&unctional
Ao; man# releases o& #our product ha"e .een produced during the last &i"e
#earsG
n recent #e$rs% m$&or 'ersion rele$ses ($'e inclu)e):
*.6c A'$il$+le since ,$# -000
*.7 A'$il$+le since .ul# -00-
ERP -00* A'$il$+le since .une -00*
ERP -005 A'$il$+le since /cto+er -005
ERP 6 A'$il$+le since .une -006
Annex B: Appendix 3B- Compliance Sheet
Page 4 of 89
3hat is the next scheduled maBor release o& the proposed so&t;areG
Please see product roadmap a.o"e
Ao; o&ten are ne; "ersions releasedG
Please see the attached material on SAP?s upgrade strateg# ;hich is .ased on
'oes the product ha"e a support centre in 8AE /in 7CCG %& #es= since ;hen
and ;here is located and ;hat ser"ices does pro"ide G
SAP o&&ers support on a glo.al .asis in a &ollo; the sun model Customers are o&&ered online and
phone access to the support organi6ation A toll &ree num.er is o&&ered in the 8AE More details on
Sap Acti"e 7lo.al support are in the attached document
%ndicate contractual agreements= and terms o& use Please attach the dra&t cop#
o& the agreement &or the .elo;
So&t;are purchase 9 :
So&t;are licence 9 :
So&t;are maintenance /AMC K 9 :
K %ndicate clearl# i& upgrade process &or minor and/or maBor releases is
including in the proposed AMCG
'id the proposed product pass through maBor re;rite statue G = i& #es then
indicate ;hich release and ;hen it has .een released
All additions ha"e .een incremental o"er time= no maBor re-;rites
%ndicate all users screens 9i& an#: ;hich ;ill not .e in dual languages Ara.ic
and English 9 i& #ou didn?t indicate an# = then *E3A assume all screens ;ill
.e .i-lingual 9Ara.ic/English :
ERP and SAP CRM and Billing &or 8tilities support Ara.ic
1.1.2 S1)(e2 Ar34,(e3(/re
9<indl# &urnish in&ormation &or each solution separatel# in case more than one application/option is o&&ered:
Annex B: Appendix 3B- Compliance Sheet
Page 5 of 89
1 Pro0,de + de(+,-ed +r34,(e3(/re o5 (4e *ro*o)ed )o-/(,on on + )e*+r+(e )4ee(. T4,) )4o/-d ,n3-/de 6/( no( -,2,(ed (o %
A**-,3+(,on +r34,(e3(/re )4o7,n. (4e ,n(er+3(,on o5 (4e d,55eren( 2od/-e) 6e,n. *ro*o)ed
S1)(e2 De*-o12en( Ar34,(e3(/re
Re3o22ended Ne(7or8 ,n5r+)(r/3(/re re9/,re2en()
+he SAP solution &or utilities is .ased on the Eet;ea"er 3e. Ser"ices Plat&orm +his ena.les the s#stem to .e deplo#ed as a ;e. ser"ices solution as ;ell a E
tier
architecture ;here &ront end= application and data.ase ser"ices ma# .e separated Please see supporting materials on the Eet;ea"er plat&orm
SAP Architecture Overview
SAPs n-Tier Architecture
SAP components are each .uilt on an n-tier client/ser"er architecture=
;hich includes presentation= application and data.ase ser"ice components
that communicate using industr#-standard protocols= such as +CP/%P= and
are .ased on a single repositor# SAP Eet3ea"er includes the em.edded
SAP 3e. Application Ser"er 9SAP 3e. AS:= ;hich em.races nati"e
3e. technologies through a standards-.ased approach SAP is &ull#
accessi.le "ia remote= mo.ile= and 3e.-.ased means Based on the highl#
scala.le SAP Application Ser"er in&rastructure= technologies ha"e .een
implemented &or directl# processing A++P re,uests 9or other protocols:
coming &rom the %nternet 9that is= &rom a .ro;ser:= and &or sending A++P
re,uests as A++P client re,uests to the %nternet
Annex B: Appendix 3B- Compliance Sheet
Page 6 of 89
2 P-e+)e *ro0,de +r34,(e3(/re )34e2+(,3 5or (4e 2+:or 3o2*onen() re9/,red (o ,2*-e2en( 1o/r )o-/(,on ;)<. Co2*-e2en( (4e )34e2+(,3 7,(4 (1*,3+-
4+rd7+re *-+(5or2), OS, 2e2or1 re9/,re2en(), +nd +-- *rere9/,),(e) 5or e+34 3o2*onen(
S#stem architecture and proper si6ing o& a customer?s m#SAPL Business Suite application is o& the highest concern to SAP +o ensure proper si6ing &or the
m#SAP Business Suite landscape= SAP in"ol"es the hard;are partners at m#SAP hard;are competenc# centers SAP ;ill ;orC ;ith *E3A and the certi&ied
hard;are "endor o& choice to ensure proper si6ing o& #our landscape and ;ill pro"ide *E3A;ith con&iguration recommendations .ased on "arious "aria.les
9num.er o& named users= concurrent users= &unctional areas and components used= net;orC .and;idths= high a"aila.ilit#= and so on:
All re,uired SAPM components can operate on a single ser"er 9multi-CP8 SMP machine: or a cluster o& smaller machines 9.lade ser"ers: e,uall# ;ell ;ith a
storage-attached disC 9SAE: 3ithout &urther in&ormation &rom *E3A on the desired operating s#stem= data.ase= and hard;are "endor= it is not possi.le to
pro"ide a more detailed hard;are con&iguration
An example landscape including the SAP Eet3ea"er Portal= SAP applications= and SAP data ;arehouse 9'3: is pro"ided in the &ollo;ing diagram Please note
that there is signi&icant &lexi.ilit# in deplo#ment o& the &inal desired architecture &or *E3A .ased on .usiness re,uirements and plat&orm choices Eot all
components are mandator# in this scenario %n this scenario= the SAP applications 9SAP AR: and the SAP '3 ha"e separate data.ases= .ut this is not re,uired
Both applications and anal#tics can run on a single data.ase
SAP recommends the ph#sical isolation o& con&iguration data through a multiple s#stem landscape ;hen supporting a production landscape SAP?s em.edded
change management s#stem supports phased implementations and team-.ased de"elopment and deplo#ment +hrough the use o& separate ph#sical data.ases in
de"elopment= ,ualit# assurance= and production s#stems= SAP pro"ides &or structured testing and auditing in $1 C*R Part 11 scenarios SAP?s em.edded ;orC&lo;
management s#stem can .e used &or migrating changes &rom one en"ironment to another= along ;ith en&orcing automated and electronic testing procedures
through the em.edded SAP test ;orC.ench tool
Annex B: Appendix 3B- Compliance Sheet
Page 7 of 89
& Fro2 (4e o55ered +**-,3+(,on), P-e+)e *ro0,de (4e 5o--o7,n. de(+,-) o5 (4e )1)(e2) (4+( (4e *ro*o)ed )o5(7+re 4+) 6een ,n(er5+3ed 7,(4%
N+2e o5 )o5(7+re
T1*e o5 )o5(7+re
T1*e o5 ,n(er5+3e
De(+,-) o5 ),(e) 7ere (4e ,n(er5+3e) +re 3/rren(-1 o*er+(,on+-
In 3+)e (4e o55er ,n3-/de) 2/-(,*-e )o5(7+re=), *-e+)e *ro0,de de(+,-) o5 ,n(e.r+(,on 6e(7een (4e o55ered +**-,3+(,on).
All SAP products are &ull# integrated +here are no inter&aces re,uired SAP products are integrated ;ith man# hundreds o& 3rd part# products %n man# cases=
certi&ied inter&aces are a"aila.le &rom SAP and 3rd parties %n addition= Sap Eet;ea"er o&&ers the a.ilit# to inter&ace using industr# standards An inter&ace
de"elopment Cit is also pro"ided to support the de"elopment o& customi6ed inter&aces
> ,)( +n1 +dd,(,on+- /(,-,(1 *+38+.e re9/,red 5or (4e *ro*o)ed +**-,3+(,on )o5(7+re (o 3o2*-1 7,(4 (4e re9/e)(ed re9/,re2en(.
None
5 W4+( *rod/3(,0,(1 (oo-) +re +0+,-+6-e 7,(4 (4e *ro*o)ed )1)(e2? C4e38 (4e 5e+(/re) (4+( +**-1, +nd Ind,3+(e 1o/r *rod/3( n+2e 74,34 )/**or() (4e
2en(,oned 5e+(/re) ; (4e 2en(,oned e@+2*-e 5or ./,de-,ne +nd doe)n=( ,nd,3+(e +n1 *re5erred *rod/3( +nd/or )o-/(,on <
Feature Product name
D+(+ d,3(,on+r1/2ode- SAP includes an integrated 'ata 'ictionar# that per&orms the &unctions o& a metadata repositor# +he 'ata
'ictionar# centrall# descri.es and manages all the data de&initions 9.oth technical and .usiness: used in the
s#stem +he 'ata 'ictionar# supports the de&inition o& user-de&ined t#pes 9data elements= structures= and ta.le
t#pes: Hou can also de&ine the structure o& data.ase o.Bects 9ta.les= indexes= and "ie;s: in the 'ata 'ictionar#
+hese o.Bects can then .e automaticall# created in the data.ase ;ith this de&inition +he 'ata 'ictionar# also
pro"ides tools &or editing screen &ields= &or example &or assigning a &ield an input help +he most important
o.Bect t#pes in the 'ata 'ictionar# are ta.les= "ie;s= t#pes 9data elements= structures= and ta.le t#pes:= domains=
search helps= and locC o.Bects +he 'ata 'ictionar# also pro"ides standard &unctions &or editing &ields on the
screenJ &or example= &or assigning a screen &ield an input help +he 'ata 'ictionar# permits a central
description o& all the data used in the s#stem ;ithout redundancies Ee; or modi&ied in&ormation is
automaticall# pro"ided &or all the s#stem components +his ensures data integrit#= data consistenc# and data
securit#
A/er1 -+n./+.e ;e... SA<
SAP Eet3ea"er Composition En"ironment I Pro"ides a ro.ust en"ironment &or design= deplo#ment and running o&
composite applications that compl# ;ith enterprise ser"ice-oriented architecture
SAP Eet3ea"er 'e"eloper Studio I !&&ers a con"enient user inter&ace and rich &unctionalit# &or de"eloping >$EE
applications
SAP Eet3ea"er -isual Composer I Simpli&ies the creation o& portal content and anal#tics applications= ena.ling
.usiness anal#sts to .uild or customi6e applications using a "isual user inter&ace rather than manual coding
Re*or( .ener+(or ;e... re*or( 7r,(er< See pre"ious section
Annex B: Appendix 3B- Compliance Sheet
Page 8 of 89
Pre)en(+(,on (oo-)
See pre"ious section
De0e-o*2en( -+n./+.e
Customers get the source code o& SAP applications= as ;ell as the de"elopment tools used to create the
applications +he de"elopment tools support .oth ABAP 9Ad"anced Business Applications Programming: and
>a"a
*or ABAP de"elopment= the ABAP 'e"elopment 3orC.ench is pro"ided +he ABAP 3orC.ench is a set o&
tools and li.raries &or designing= implementing= testing= and maintaining transactions and reports ;ritten in
ABAP !.Bects
*or >a"a de"elopment= SAP pro"ides Eet3ea"er 'e"eloper?s Studio= an Eclipse-.ased >a"a de"elopment
en"ironment
SAP also pro"ides -isual Composer= a model-dri"en de"elopment tool that produces 3e. .ased screens
8ser-de"eloped customi6ations= such as con&iguration changes and code inserted at pre-de&ined points= are
maintained separatel# &rom the core applications= and i& properl# applied can easil# .e preser"ed through an
upgrade !nl# changes to the core applications 9ie= modi&ications to the source code: are not automaticall#
upgraded Ao;e"er= e"en in this case= an audit is per&ormed .e&ore upgrading the core applications= and an#
changes are highlighted to allo; the changes to .e extracted and
Annex B: Appendix 3B- Compliance Sheet
Page 9 of 89
In(er5+3e de0e-o*er
SAP?s products are extenda.le .# a "ariet# o& processes including con&iguration= the use o& user exits= and
&inall# modi&ication o& the code 9A more detailed description o& each is pro"ided .elo;: Con&iguration is the
simplest o& the options and entails using the pro"ided SAP tools to con&igure the s#stem to meet a ;ide "ariet#
o& .usiness needs 3hen this does not meet the customer?s needs= ;e ha"e user exits pro"ided in the standard
code= ;hich allo; &or minor customi6ation *inall#= the ABAP tool pro"ided ;ith the so&t;are pro"ides the
a.ilit# to maCe customi6ations as needed
'uring the reali6ation phase o& the proBect= the proBect team can create their uni,ue SAP installation "ia the
&ollo;ing:
Con5,./r+(,on - ProBect team mem.ers identi&# the .usiness re,uirements and maCe modi&ications as
needed to ena.le the solution "ia the %mplementation 7uide 9%M7: Application code is designed to
operate .ased on con&iguration ta.les--as such= no programming is re,uired to Dcustomi6eD the s#stem
;ithin these design parameters +he %M7 is speci&icall# designed &or use .# the &unctional mem.ers o& the
ProBect +eam= and is .ased on application appropriate user inter&aces &or creating .usiness rules and
con&iguration ta.les
En4+n3e2en( - ProBect team mem.ers identi&# the Duser exitD location and then ;rite a de&inition o& the
extension needed ;hich is then coded .# a tools consultant 9using the ABAP 3orC.ench: A Duser exitD is
a pre-de&ined point in a transaction at ;hich customers t#picall# ;ant to per&orm some site-speci&ic
processing Customer-de"eloped applications are also an example o& an enhancement= and can de"eloped
using ABAP or >$EE
C/)(o2,B+(,on - %& the proBect team cannot &ind solutions using either o& the &irst t;o processes then it ;ill
need to re,uest that a modi&ication o& the product .e made +hese are de&ined and presented to the steering
committee and proBect management &or appro"al *re,uentl# the .usiness process change team engages in
this area to see i& there are .usiness solutions that can a"oid this A customi6ation modi&ies an SAP
pro"ided .usiness o.BectJ the ABAP 3orC.ench includes tools to manage modi&ied o.Bects
+hrough SAP Eet3ea"er= .usinesses can achie"e end-to-end process integration ;ith pre-integrated SAP
solutions Eet3ea"er also ena.les disparate applications and s#stems ;orC to ;orC together to per&orm
.usiness processes &rom a com.ination o& SAP and non-SAP s#stems
SAP adheres to an ES!A 9Enterprise Ser"ices !riented Architecture: as supported .# SAP Eet3ea"er +his
adapta.le model pro"ides enterprises the &lexi.ilit# to easil# extend s#stem &unctionalit# .# le"eraging existing
%+ in"estments that include SAP and non-SAP applications Based on a 3e. ser"ices paradigm= this model
ele"ates %+ to e&&icientl# meet the needs o& the enterprise and deli"er a +C! that maps to an enterprises
o.Becti"es
SAP Eet3ea"er o&&ers an %ntegration BroCer 9SAP P%: and a Business Process Management 9BPM: solution &or
process integration .esides the message-oriented middle;are
%nter&aces are at the heart o& e"er# cross-component process +he# are almost constantl# re&erenced during
design and con&iguration %t is there&ore "ital that an inter&ace description can .e accessed at a central point +he
&ollo;ing are inter&ace description t#pes that #ou can sa"e in the SAP Process %ntegration 9SAP P%= &ormerl#
Cno;n as SAP Eet3ea"er Exchange %n&rastructure= or SAP Eet3ea"er N%: %ntegration Repositor#:
Plat&orm-independent message inter&aces
%mported inter&aces &or ;hich an NM@ representation o& a BAP%= R*C= or %'oc is generated in the
%ntegration Repositor#
External 3S'@= NS'= or '+' de&initions containing message schemas that #ou can access in the
%ntegration Builder
+he standard SAP inter&aces are ;e. ser"ices and are pu.lished centrall# in the NM@-.ased %nter&ace
Repositor# +he# are stored as NM@ schema= ;hich means that the# are immediatel# a"aila.le &or use in
integration scenarios ;here multiple components communicate ;ith each other using the %nternet
Additionall#= Business AP%s 9BAP%s: are traditional AP%s that allo; communication using technologies such as
Annex B: Appendix 3B- Compliance Sheet
Page 10 of 89
A**-,3+(,on Ser0er
SAP Eet3ea"er Application Ser"er I Supports plat&orm-independent 3e. ser"ices= .usiness applications= and
standards-.ased de"elopment= ena.ling #ou to le"erage existing technolog# assets &or 3e.-ser"ices-oriented
solutions
D+(+6+)e M+n+.e2en( Too-
+he SAP s#stem supports the use o& relational data.ase management s#stems 9R'BMS: to include: !racle=
Microso&t S5@ Ser"er= 'B$= and m#S5@ Max'B All supported R'BMS are AES% S5@ compliant SAP does
not recommend one R'BMS o"er another All s#stem &unctionalit# is data.ase independent
Standard tasCs such as per&ormance tuning and .acCup are re,uired A trained 'BA can easil# support the SAP
application &rom a data.ase perspecti"e
SAP so&t;are comes ;ith its o;n .acCup and restore utilit#= a &ull s#stem and data.ase administrati"e tool
called Computing Center Management S#stem 9CCMS: Both &ull and partial .acCups are supported BacCup
and reco"er# is al;a#s per&ormed at the data.ase le"el +he SAP .acCup utilit# supports t;o modes o& .acCup:
o&&line and online %n o&&line mode= the application is not a"aila.le &or the duration o& the .acCup %n online
mode= users ha"e &ull access to the application ;hile .acCup is running
B/),ne)) In(e--,.en3e ;BI< 6/,-der
SAP Eet3ea"er Business %ntelligence I Ena.les #ou to integrate data &rom across the enterprise and trans&orm
it into practical= timel# .usiness in&ormation to dri"e sound decision-maCing
De0e-o*2en( Too-
8ser producti"it# ena.lement -- Aelp users and groups impro"e their producti"it# through enhanced
colla.oration= optimi6ed Cno;ledge management= and personali6ed access to critical applications and data
'ata uni&ication -- Consolidate= rationali6e= s#nchroni6e= and manage all master data &or impro"ed
.usiness processes
Business in&ormation management -- %ncrease the "isi.ilit#= reach= and use&ulness o& structured and
unstructured enterprise data
Business e"ent management -- Ensure that .usiness e"ents &rom multiple s#stems are distri.uted to the
appropriate decision maCers in the context o& the rele"ant .usiness processes
End-to-end process integration -- MaCe disparate applications and s#stems ;orC together consistentl# to
per&orm .usiness processes
Custom de"elopment -- Rapidl# create ne; enterprise-scale applications that dri"e #our compan#Os
di&&erential ad"antage
8ni&ied li&e-c#cle management -- Automate application management processes and optimi6e all &acets o&
an applicationOs li&e c#cle
Application go"ernance and securit# management -- Maintain an appropriate le"el o& securit# and ,ualit#
in #our intellectual propert# and in&ormation assets
Consolidation -- 'eplo# a consolidated technolog# plat&orm ;ith the a.ilit# to allocate computing po;er
according to changing .usiness needs
Enterprise ser"ice-oriented architecture design and deplo#ment -- Consolidate and standardi6e #our .asic
processes and le"erage existing in"estments to compose ne;= distincti"e .usiness processes
C+)e (oo- ;e... De),.ner 2000 e(3.< %ncluded in de"elopment en"ironment o& SAP See pre"ious sections
RDBMS ;e... Or+3-e, DB2 e(3.< !racle= 'B$ are supported +he SAP s#stem supports the use o& relational data.ase management s#stems
9R'BMS: to include: !racle= Microso&t S5@ Ser"er= 'B$= and m#S5@ Max'B All supported R'BMS are
AES% S5@ compliant SAP does not recommend one R'BMS o"er another All s#stem &unctionalit# is
data.ase independent
Annex B: Appendix 3B- Compliance Sheet
Page 11 of 89
C De)3r,6e 1o/r -o.,3+- +nd/or *41),3+- d+(+ 2ode-. ;P-e+)e *ro0,de (4e 2ode-) 5or re0,e7.< P-e+)e de)3r,6e (4e e+)e +nd *ro3e)) o5 +dd,n. 3/)(o2 5,e-d) (o
1o/r *rod/3(=) d+(+ +r34,(e3(/re.
As the Sap solution is .uilt on top o& an integrated Enterprise Ser"ices en"ironment= clients ha"e a num.er o& methods o& adding &ields= modi&#ing processes and
adding ne; &unctionalit# Please see supporting materials descri.ing Eet;ea"er
D P-e+)e *ro0,de de(+,-) on )3+-+6,-,(1, 4,.4E+0+,-+6,-,(1, re-,+6,-,(1, +nd 5-e@,6,-,(1 5e+(/re) 6+)ed on (4e *rod/3(;)< +r34,(e3(/re. In +dd,(,on, *-e+)e
,--/)(r+(e -o+dE6+-+n3,n. 5e+(/re) *ro0,ded ,n 1o/r *ro*o)ed )o-/(,on ;,5 +n1 <.
+he SAP Eet3ea"erM Application Ser"er component relies on its >$EE-.ased clustering architecture to pro"ide high-a"aila.ilit# *ail-o"er capa.ilities include:
Replication and partition o& components inside a cluster architecture
Cluster ;ide resource locCing AP%= ;ith high a"aila.ilit# &eatures such as locC replication
'ata.ase and persistenc# la#er ;ith reconnect &unctionalit#
State&ul session &ailo"er is supported at "arious le"els:
Session sticCiness "ia cooCies or 8R@ re;riting
Session &ailo"er at E>B le"el "ia redirect to alternati"e ser"er nodes
7ranularit# o& &ailo"er can .e adBusted in a &lexi.le manner to co"er each user re,uest or each http session *lexi.le session persistenc# is achie"ed "ia &ile s#stem=
R'BMS= shared memor# or shared closures 9part o& the -M container architecture .# SAP: Planned do;ntime is &ull# supported .# the high a"aila.ilit# concept
o& SAP Eet3ea"er Application Ser"er Ser"ers and indi"idual components can .e shut do;n on a schedule de&ined .# the s#stem administrator +he cluster
architecture automaticall# redirects processes to other a"aila.le instances o& the ser"er
8sing the three- or multi-tier approach= all re,uests must access the application ser"er +he application se"er does the necessar# processing and data.ase access
and returns the results to the presentation client +he application ser"er is highl# scala.le and per&orms log on load .alancing +his mechanism ensures
transparenc# to the users &rom the logon process to the s#stem
F P-e+)e de)3r,6e +n1 -,2,(+(,on) (4+( e@,)( +nd/or 2+1 +r,)e ,n (4e *ro*o)ed )o5(7+re/o*er+(,n. )1)(e2/5,-e 2+n+.er e(3 6+)ed on (4e 0o-/2e o5 D+(+ (4+(
3+n 6e 4+nd-ed +nd *ro3e))ed. ;N/26er o5 (+6-e en(r,e), 2+)(er d+(+ 5,e-d), 8e1 0+-/e), e(3.<
+here are no so&t;are imposed limits Ser"er capacit# and Eet;orC throughput are the onl# limitations +he SAP en"ironment can .e con&igured to meet
re,uirements and is in&initel# scala.le to meet expected gro;th
Annex B: Appendix 3B- Compliance Sheet
Page 12 of 89
9 P-e+)e de)3r,6e (4e (1*e o5 Re)(ore/Re3o0er1 *ro3ed/re) )/**or(ed 7,(4,n (4e *ro*o)ed *+38+.e, ,n (4e e0en( o5 (r+n)+3(,on or *ro3e)) 5+,-/re +nd (4e
e)(,2+(ed (,2e (o 3o2*-e(e (4e *ro3e)), +-)o ,nd,3+(e ,5 )/34 Re3o0er1/Re)(ore *ro3ed/re 7,-- 3+/)e do7n(,2e?
An SAPM so&t;are implementation comes ;ith all the necessar# components to ensure high a"aila.ilit# and e&&ecti"e reco"era.ilit# ;hen &aults occur SAP
so&t;are comes ;ith its o;n .acCup and restore utilit# Both &ull and partial .acCups are supported +he SAP .acCup utilit# supports t;o modes o& .acCup: o&&line
and online %n o&&line mode= the application is not a"aila.le &or the duration o& the .acCup %n online mode= users ha"e &ull access to the application ;hile .acCup is
running *rom an SAP perspecti"e= one method is as good as another All data.ase s#stems ha"e their tools to .acC up and restore their data.ases +he SAP
en"ironment inter&aces to nati"e data.ase tools to support the .acCup and restore &unctions 3ith all dataase s#stems supported .# SAP= data.ase .acCups can .e
scheduled and triggered &rom the computer center management s#stem 9CCMS: &unctionalit#J alternati"el#= external .acCup tools can also .e used SAP .acCup
support o& tape stacCers com.ined ;ith SAP scheduling allo;s #ou to run .acCups unattended SAP .acCup also pro"ides tape "olume management Reco"er# in
cases ;here data is lost is managed ;ith a com.ination o& the SAP restore utilit# and data.ase logging SAP restore is normall# used to .ring a data &ile .acC to a
Cno;n state .# appl#ing the most recent &ull .acCup 9and an# incremental .acCups since that time: !nce this is done= data.ase logs are applied to .ring the s#stem
.acC to the last committed transaction An# Pin-&lightQ transactions are captured in an update log ;here .roCen transactions can .e re"ie;ed .# the s#stem
administrator and the user to determine the most appropriate course o& action 8sers are also noti&ied o& an# &ailed transactions "ia an e-mail message SAP
data.ase management tools come ;ith a checC and restore &unction ChecC and repair &unctionalit# is used to unco"er an# inconsistencies in the data.ase %& an
inconsistenc# is &ound= SAP restore uses in&ormation &rom .acCup logs and tape "olume management to &ind the appropriate &iles to restore= and pro"ide automated
reco"er#
10 De)3r,6e (4e 3on(ro- 5e+(/re) ,n3-/ded 7,(4,n (4e )1)(e2 (o en)/re ,n(e.r,(1 o5 d+(+ ;,.e. ,n*/( +nd /*d+(e, (o(+-) 2+,n(+,ned, 3ro))34e38) 3+rr,ed o/(,
+/d,( (r+,-), error re*or(), e(3.<
+he SAPM s#stem handles all "alidations in the application la#er As a result= the SAP s#stem pro"ides &ar .etter data integrit# during s#stem inter&aces !ther
solutions pro"ide inter&aces 9including .atch inter&aces: to the s#stem at the data.ase or middle;are le"el +he pro.lem ;ith such an approach is that .asic
"alidation rules 9in the client: are .#passed and must .e reproduced in the inter&acing program !& course= as soon a rule has to .e maintained in more than one
place= there is a "irtual guarantee that those rules e"entuall# dri&t apart= resulting in in"alid data
B# pro"iding an inter&ace la#er at the application ser"er= the SAP s#stem ensures that all data &ed to the s#stem 9;hether .atch or real-time: is processed .# a
single set o& "alidation and securit# rules %t is technicall# impossi.le to pass the SAP s#stem in"alid data through an inter&ace +he s#stem can record user actions
and create an audit trail &or data integrit# All data changes are logged .# user %'= date and time stamp= and .e&ore and a&ter "alues +he data log is stored
inde&initel# until it is archi"ed out o& the s#stem +he transaction log Ceeps an audit o& all transactions executed in the s#stem .# user %'= data and time stamp=
terminal %'= and detailed per&ormance statistics +his data is stored in a c#clical &ile +he SAP s#stem comes deli"ered ;ith the securit# user in&ormation s#stem
9S8%M: and audit in&ormation s#stem 9A%S:= ;hich pro"ide diagnostic= reporting= and auditing &unctionalit#= as ;ell as extensi"e checClists to assist in ensuring
s#stems are secure All data is checCed .# the application I as a result= the data is al;a#s in s#nc
11 De)3r,6e (4e 2od/-e) 7,(4,n 1o/r *ro*o)ed )o-/(,on , +nd 4,.4-,.4( ,n 3-e+r M+nner (4e de*enden31/,n(erde*enden31 o5 e+34 2od/-e +nd (4e n+(/re o5
)/34 de*enden31 +nd (4e *o)),6-e 3on)(r+,n() o5 )/34 re-+(,on on (4+( 2,.4( ,2*o)e on (4e ,2*-e2en(+(,on +nd/or on (4e o*er+(,on
All Sap modules proposed are &ull# integrated in real time Customer care and .illing are &ull# integrated ;ith the .acC end ERP s#stem that pro"ides accounting=
recei"a.les and pa#a.les solutions As a result there are no constraints imposed on clients +here is no need to &actor integration into an# implementation or costing
plans
Annex B: Appendix 3B- Compliance Sheet
Page 13 of 89
12 P-e+)e de)3r,6e (4e ,n(ero*er+6,-,(1 o5 (4e *ro*o)ed *rod/3(. And 74+( )(+nd+rd ,n(er5+3e) ,) )/**or(ed , +nd 4o7 FEWA 3+n /(,-,Be (4e *ro*o)ed
*rod/3( (o ,n(er5+3e/,n(e.r+(e 7,(4 o(4er +**-,3+(,on ; ,5 ,() re9/,re < e... ; Con(+3( Cen(er , AMS .. e(3 <
'etailed in&ormation a.out a"aila.le adapters= including adapters &rom partners= can .e &ound at the SAPM Ser"ice MarCetplace under http://ser"icesapcom/xi
See SAP Eet3ea"erG Exchange %n&rastructure in 'etail and Connecti"it#
Ad+*(er) de-,0ered 61 SAP
+he SAP Eet3ea"er Exchange %n&rastructure 9SAP Eet3ea"er N%: component supports all integration scenarios .ased on %'!Cs= BAP%Gs or R*Cs %'!C
structures and BAP%/R*C signatures can .e imported directl# into the Repositor# o& SAP Eet3ea"er N% as preparation &or the implementation phase
7RAPA%C 9Adapter !"er"ie;:
Ad+*(er) (o Conne3( (o E@,)(,n. SAP
S1)(e2)
IDo3 Ad+*(er
RFC Ad+*(er
Ad+*(er) (o Conne3( (o T4,rd P+r(1 +nd Me))+.,n. S1)(e2)
F,-e/FTP Ad+*(er
D+(+6+)e ;HDBC< Ad+*(er
H+0+ Me))+.,n. Ser0,3e ;HMS< Ad+*(er
Speciali6ed Messaging Adapters
DPlain A++PD Adapter
S!AP Adapter
Adapters to Connect to MarCetplaces
MarCetplace Adapter
Connecti"it# to Main&rames
Connecting C%CS and SAP Eet3ea"er N%
.# 8sing S!AP
+he %'!C- and the R*C-Adapter can .e used to communicate ;ith SAP s#stem release "ersions 31x or higher in .oth directions 9in.ound and out.ound: *or
applications executed on the SAP Eet3ea"er Application Ser"er 9SAP Eet3ea"er AS: component "ersion /$( or higher= custom ABAPL or >a"a Proxies can .e
generated into the application 9as >a"a or ABAP !.Bects classes: %n these cases= the prox# runtime o& SAP Eet3ea"er AS executes the A++P-communication to
the SAP Eet3ea"er N% integration ser"er= ;hile the customer-speci&ic proxies are either called .# the application 9in.ound prox#: or the prox# runtime 9out.ound
prox#: to exchange data ;ith the application "ia local inter&aces More and more m#SAPL solutions 9m#SAP SCM= m#SAP CRM= and so on: are deli"ered ;ith
.uilt-in standard proxies +here&ore= SAP Eet3ea"er N% proxies ;ill more and more .ecome a standard inter&ace to SAP s#stems= Bust liCe R*Cs= %'ocs= and 3e.
Ser"ices
1& P-e+)e 3on5,r2 ,5 (4e *ro*o)ed *rod/3( 3+n 6e r/n on e@(ern+- 5ron( *or(+- ;e... C,(r,@, SS 0,r(/+- 7or8)*+3e ..e(3 <. I5, 1e) *-e+)e *ro0,de 3+)e)
;re5eren3e 3-,en()< 74ere )/34 ,2*-e2en(+(,on 4+) 6een done. E@*-+,n ,5 )/34 ,2*-e2en(+(,on 4+) +n1 -,2,(+(,on on (4e 5/-- 5/n3(,on+-,(1 o5 (4e *ro*o)ed
)o-/(,on ; H+0+ +**-e( -,2,(+(,on , A3(,0eE$ , 4((*) I. E(3 <
SAP solutions ma# .e used ;ith the Citrix &ront portal solution Sap is also certi&ied &or 3+S Sap has man# customers using Citrix SAP uses Citrix &or glo.al
traing on SAP s#stems and Citrix itsel& uses SAP
1> P-e+)e de)3r,6e (4e (e34n,9/e)/2e(4odo-o.1 (o 5+3,-,(+(e &
rd
*+r(1 *rod/3( (o ,n(e.r+(e 7,(4 (4e *ro*o)ed )o-/(,on, *-e+)e e@*-+,n ,n de(+,-) +-- (e34n,3+-,
-,3en)e) +nd -e.+- +)*e3().
Please see the ans;er gi"en to 5uestion 1$ in this section
Annex B: Appendix 3B- Compliance Sheet
Page 14 of 89
15 P-e+)e e@*-+,n +nd -,)( +-- +0+,-+6-e (e)(,n. , +/d,(,n. , +nd 6+38/*/re)(ore/re3o0er 5e+(/re) (4+( ,) ,n3-/ded ,n (4e *ro*o)ed )o-/(,on 7,(4o/( +n1
+dd,(,on+- -,3en)e) +nd/or +dd,(,on+- 3o)(.
*unctional R +echnical +esting +ools: 3ipro shall use Solution Manager eCA++ tool &or per&orming +esting the *unctionalit# customi6ed during the Reali6ation
Phase +he +est Scenarios= +est Cases and +est 'ata ;ill .e prepared .# *E3A and 3ipro Bointl#
3ipro shall use SAP?s BR +ools &or BacCup= Restore R Reco"er *eatures 9Re,uest Anand to add content i& he has &actored AP 'ataprotector or an# 'ata BacC
up tools &or managing +ape @i.rar# &or BacCup R Restore *unctions:
@oad / Stress / -olume +esting +ools: 3ipro shall use AP @oadRunner &or per&orming these +ests during the Reali6ation to see the Per&ormance under Sustained
periods +he @icenses &or using these tools shall .e procured .# 3ipro on @imited Period Basis 9!ne Month: %& *E3A desires to ha"e these tools &or @onger
Periods= the same shall .e pro"ided a&ter initiating Change Control Procedure
1C P-e+)e ,nd,3+(e +-- 4+rd7+re re9/,re2en( 5or 1o/r *ro*o)ed )o-/(,on ,n3-/d,n. ;Me2or1, CPU, OS, S(or+.e S*+3e 5or +**-,3+(,on Jd,)8 )*+3eK +nd +-)o
,nd,3+(e (4e D+(+6+)e/re*or() )(or+.e )*+3e re9/,re2en( *er 2on(4 J6+)ed on 1o/r *ro*o)ed )o-/(,on +nd on 1o/r /nder)(+nd,n. o5 FEWA 6/),ne))
n+(/re +nd -o+dK.
%MP@EMEE+ER +! AES3ER I Anand to Respond ;ith B!M and Si6ing Summar#
1D
W4+( (1*e o5 ,2*or( +nd e@*or( 3+*+6,-,(,e) +re +0+,-+6-e 5or 3re+(,n. 3/)(o2,Bed d+(+ 5eed)?
B1 /),n. SAP 'ata +rans&er 3orC.ench #ou can trans&er data ;hich supports the automatic trans&er o& data into the s#stem
+he 3orC.ench is particularl# use&ul &or "arious .usiness o.Bects ;ith large amounts o& data %t guarantees that data is trans&erred e&&icientl# and ensures that data
in the s#stem is consistent +he 'ata +rans&er 3orC.ench ;as designed &or the initial trans&er o& data %& #ou ;ant to trans&er data repeatedl# at regular inter"als=
;e recommend that #ou use tools such as A@E 9through the %'oc inter&ace: or the Process integrator 9P%:
+he 'ata +rans&er 3orC.ench pro"ides the &ollo;ing &unctions:
Administration and organi6ation o& data trans&er proBects
+ools &or anal#6ing the re,uired SAP structures
%ntegration o& standard data trans&er programs
Registration and integration o& #our o;n data trans&er programs and help programs
-arious techni,ues &or loading data
+he data is read &rom a trans&er &ile in SAP &ormat and loaded into #our s#stem using one o& the techni,ues .elo;:
1. BAP% inter&ace
2. Batch input
3. 'irect input 9'%EP:
'ata con"ersion using the @egac# S#stem Migration 3orC.ench 9@SM3:
Annex B: Appendix 3B- Compliance Sheet
Page 15 of 89
1F Men(,on (4e d+(+6+)e 2+n+.e2en( (oo-) (4+( ,) ,n3-/ded 7,(4,n 1o/r *ro*o)ed o55er ;I5 +n1 e.. S34e2+ 2+n+.e2en(, +r34,0,n. )(or+.e (oo-), d+(+
6+38/* re3o0er1 (oo-), d+(+6+)e 2on,(or,n., *er5or2+n3e (/n,n. +nd o*(,2,B+(,on, :o6 3re+(,on L )34ed/-,n., )e3/r,(1, 5,-e 2+n+.e2en(, e(3<
+he SAP Solution Manager application management solution= is pro"ided &ree o& charge and &acilitates technical support &or distri.uted s#stems ;ith &unctionalit#
that co"ers all Ce# aspects o& solution deplo#ment= operation= and continuous impro"ement %t is a centrali6ed= ro.ust application management and administration
solution that com.ines tools= content= and direct access to SAP to increase the relia.ilit# o& solutions and lo;er total cost o& o;nership SAP Solution Manager is
no; mandatoril# used in all SAP Consulting implementations o& core SAP processes SAP Solution Manager Enterprise Edition pro"ides additional &unctionalit#
re,uired &or SAP Enterprise Support ser"ices *eatures and &unctions that ;e can le"erage are:
S Ser0,3e -e0e- 2+n+.e2en( I SAP Solution Manager allo;s #ou to de&ine and report ser"ice le"els= pro"iding an automated reporting across
se"eral s#stems re,uires less manual e&&ort Ser"ice Reporting co"ers all s#stems in the solution landscape and pro"ides a consolidated report
containing the in&ormation #ou need to maCe strategic %+ decisions
S Ser0,3e *ro3e)),n. I SAP Solution Manager maCes appropriate ser"ice recommendations and acts as a "ehicle &or deli"ering SAP support
ser"ices +hese include ser"ices &rom the SAP Sa&eguarding port&olio= ;hich helps #ou manage technical risCJ ser"ices &rom the SAP Solution
Management !ptimi6ation port&olio= ;hich helps to exploit the &ull potential o& #our SAP solutionsJ and ser"ices &rom the SAP Empo;ering
port&olio= ;hich helps ac,uire core competencies to manage #our solutions
Speci&icall#= Solution Manager &acilitates the running o& #our End to End operational support through managing:
S Roo( C+/)e An+-1),) I SAP standards &or %ncident Management
S C4+n.e Con(ro- I SAP standards &or Change Control and Application Management SAP standards &or *unctional= Regression and -olume +esting
S B/),ne)) Pro3e)) In(e.r+(,on +nd A/(o2+(,on - SAP standards &or >o. Scheduling= %nter&ace and Business Process Monitoring
S En(er*r,)e SOA re+d,ne)) - SAP standards &or Ser"ice Ena.lement= 8pgrades and Migrations
S EndE/)er (r+,n,n. M SAP Solution Manager helps create and deli"er interacti"e learning units to educate all users a.out ne; or changed
&unctionalit#= thus reducing the cost o& end-user training
S U*.r+de +nd 34+n.e 2+n+.e2en( M Hou can manage and accelerate #our upgrade and change management proBects ;ith SAP Solution
Manager to increase R!%
S SAP ,2*-e2en(+(,on M SAP Solution Manager pro"ides content that accelerates implementation Con&iguration in&ormation and a process-dri"en
approach to implementation speed the .lueprint= con&iguration= and &inal preparation phases SAP Solution Manager ena.les e&&icient proBect
administration and centrali6ed control o& cross-component implementations
. S1n34ron,B+(,on o5 3/)(o2 )e((,n.) I 3ith SAP Solution Manager= #ou can maintain consistenc# as #ou customi6e #our heterogeneous %+
en"ironment %t ena.les sa&er administration o& customi6ation= less error-prone replication o& custom settings= and simpler consistenc# checCs
SAP Solution Manager reduces manual s#nchroni6ation e&&orts .# automaticall# distri.uting custom settings to "arious s#stems simultaneousl#=
and .# centrall# managing all re,uests to s#nchroni6e settings
S Te)(,n. I SAP Solution Manager speeds test preparation and execution %t pro"ides a single point o& access to the complete s#stem landscape and
ena.les centrali6ed storage o& testing material and test results to support cross-component tests
S IT +nd +**-,3+(,on )/**or( I +he support desC included in SAP Solution Manager helps #ou manage incidents more e&&icientl# and eases the
settlement o& support costs Centrali6ed handling o& support messages maCes the support organi6ation more e&&icient
S So-/(,on 2on,(or,n. M SAP Solution Manager per&orms centrali6ed= real-time monitoring o& s#stems= .usiness processes= and inter&aces= ;hich
reduces administration e&&ort %t can e"en monitor inters#stem dependencies Proacti"e monitoring helps #ou a"oid critical situations= ;hile
automatic noti&ications ena.le &ast response to issues
S Ser0,3eE-e0e- 2+n+.e2en( +nd re*or(,n. I SAP Solution Manager allo;s eas# de&inition o& ser"ice le"els and pro"ides automated reporting
Ser"ice reporting co"ers all s#stems in the solution landscape and pro"ide a consolidated report containing the in&ormation #ou need to maCe
strategic %+ decisions
S Ser0,3e *ro3e)),n. M SAP Solution Manager maCes appropriate ser"ice recommendations and deli"ers SAP support ser"ices +hese include SAP
Sa&eguarding= ;hich helps #ou manage technical risCJ SAP Solution Management !ptimi6ation= ;hich helps #ou get the most &rom #our SAP
solutionsJ and SAP Empo;ering= ;hich helps #ou manage #our solutions
Annex B: Appendix 3B- Compliance Sheet
Page 16 of 89

19 P-e+)e de)3r,6e (4e n+(/re +nd -e0e-) o5 )e3/r,(1 2e+)/re (4+( ,) )/**or(ed 61 (4e *ro*o)ed )1)(e2 ; (4,) )4o/-d ,n3-/de A/d,( 3+*+6,-,(,e), -o..,n.
de(+,-), D+(+6+)e 5,-e -o38, en3r1*(,on , A33e)) -e0e- , *+))7ord )(ren.(4 +nd en5or3e2en( .. e(3 < . In +dd,(,on, +-)o o/(-,ne (4e de(+,-) +nd +r34,(e3(/re o5
+n1 e@(ern+- )e3/r,(1 3o2*onen() (4+( 7,-- 6e re9/,re
Access to SAPM so&t;are is onl# "ia a "alid user name and pass;ord +he user is then assigned roles= ;hich relate to authori6ation o.Bects -arious rules exist &or
pass;ord changes= including length= special characters rules= and pass;ord expir# times
Se"eral mechanisms are a"aila.le &or authenticating users on the SAP Eet3ea"erM plat&orm 3hen man# s#stems are in"ol"ed in #our s#stem landscape= SAP
also supports the &ollo;ing option &or single sign-on:
8ser %' and Pass;ord I de&ault mechanism that can .e used &or user authentication &or .oth SAP and %nternet protocols= regardless o& the &ront-end
client
Secure Eet;orC Communications 9SEC: I can .e used &or user authentication and single sign-on ;hen using SAP protocols 9dialog= R*C: and the SAP
78% &or 3indo;s or SAP 78% &or >a"a as the &ront-end clients +ransport la#er securit# is also pro"ided ;hen using SEC
SAP logon ticCets I can .e used &or single sign-on ;hen using %nternet protocols and a 3e. .ro;ser as the &ront-end client
SS@ and N1(2 client certi&icates I can .e used &or .oth user authentication and single sign-on ;hen using %nternet protocols and a 3e. .ro;ser as the
&ront-end client
Plugga.le Authentication Ser"ices 9PAS: I a"aila.le as a ser"ice ;ith the SAP 78% &or A+M@ 3e. 78% +he user is issued a logon ticCet a&ter .eing
authenticated .# an external authentication mechanism
SAP also pro"ides the SAP Eet3ea"erM %dentit# Management solution An o"er"ie; o& the architecture o& the SAP Eet3ea"erM %dentit# Management
component is a"aila.le in the &igure .elo; +he pro"isioning option o& SAP Eet3ea"er %dentit# Management stores all identit#= con&iguration and polic#= and
audit and logging data in a data.ase 8ser management and appro"al processes are managed through a 3e.-.ased graphical user inter&ace 978%: Con&iguration is
managed through a 3indo;s thicC client 9Microso&t Management Console I MMC: Connecti"it# ;ith authoritati"e and target applications is done through the
dispatchers 8ser pro"isioning and identit# data s#nchroni6ation Bo.s are set up in the data.ase to .e picCed up .# a"aila.le dispatchers +hree-tier architecture
allo;s high le"els o& a"aila.ilit# and scala.ilit#
Annex B: Appendix 3B- Compliance Sheet
Page 17 of 89
20 Doe) (4e *rod/3( 4+nd-e 3on3/rren( /)e) o5 (4e )+2e ID? I5 1e) (4en e@*-+,n (4e 4+nd-,n. *ro3e)) +nd 5-o7 , 74+( ,) (4e ,2*+3( on (4e )e3/r,(1 ),de ?, ,5
no( *-e+)e e@*-+,n (4e -o.Eo55 en5or3e2en( 5or ,d-e /)er) , +nd +-)o e@*-+,n (4e +-+r2,n. +nd -o. +3(,0,(1 5or )/34 )3en+r,o
SAP uses the named user concept and does not support multiple users o& the same %' as it creates a securit# risC SAP does allo; users to ha"e multiple sessions
open against a single %'
21 W4+( 8,nd o5 e@(ern+- de0,3e)/)o5(7+re +re re3o22ended 5or )1)(e2/D+(+6+)e 6+38/*), *-e+)e ,n3-/de re3o22ended 6+38/* *ro3e)) +nd 2e(4odo-o.1.
W4+( 8,nd o5 e@(ern+- de0,3e)/)o5(7+re +re re3o22ended 5or )1)(e2/D+(+6+)e re)(ore/re3o0er1, *-e+)e ,n3-/de re3o22ended re)(ore/re3o0er1 *ro3e))
+nd 2e(4odo-o.1.
%mplementer to respond I Anand to respond i& ;e are proposing +ape @i.rar#
22 N+(/re o5 *o)),6-e o*er+(,on) +( (4e re2o(e -o3+(,on) 74en 3en(r+- )er0er +nd/or WAN -,n8 ,) do7n.
Su.Bect to technical design .ased on the re,uirements o& each process step
2& In 3+)e o5 +n1 5+,-/re o5 (4e 3en(r+- )er0er 74+( ,) (4e *ro0,),on (o re(r,e0e (4e 6/),ne)) 3on(,n/,(1 ; 'o(/3o-dE)(+nd61 )er0er, DR )/**or( < +nd 74+( ,)
(4e e@*e3(ed do7n(,2e 5or e+34 )3en+r,o , +-)o -,)( (4e re9/,re2en( 5or DR )e(/* .
'isaster reco"er# strategies rel# on partner products= such as cluster solutions= replication so&t;are= and storage SAPM so&t;are comes ;ith all the necessar#
components to ensure high-a"aila.ilit# and e&&ecti"e a.ilit# &or reco"er#= should &aults occur SAP so&t;are comes ;ith its o;n .acCup and restore utilit# and
supports .oth &ull and partial .acCups +he SAP so&t;are .acCup utilit# supports t;o modes o& .acCup: o&&line and online %n o&&line mode= applications are not
a"aila.le &or the duration o& the .acCup %n online mode= users ha"e &ull access to the application ;hile the .acCup is running *rom our perspecti"e= one method is
as good as another
SAP so&t;are pro"ides transaction roll.acC 9not sa"ing incomplete transactions: and data.ase reco"er# in the e"ent o& so&t;are interruptions *rom the point o&
"ie; o& data.ase programming= a data.ase logical unit o& ;orC 9@83: is an insepara.le se,uence o& data.ase operations that ends ;ith a data.ase commit +he
data.ase @83 is either &ull# executed .# the data.ase s#stem or not at all !nce a data.ase @83 has .een executed success&ull#= the data.ase is in a consistent
state %& an error occurs ;ithin a data.ase @83= all o& the data.ase changes since the .eginning o& the data.ase @83 are re"ersed +his lea"es the data.ase in the
state it ;as in .e&ore the transaction started
+he data.ase changes that occur ;ithin a data.ase @83 are not actuall# ;ritten to the data.ase until a&ter the data.ase commit 8ntil this happens= #ou can use a
data.ase roll.acC to re"erse the changes %n SAP so&t;are= #ou can use either implicit or explicit commands to trigger data.ase commits and roll.acCs SAP has
de"eloped a uni,ue techni,ue that completel# insulates the user &rom lo;-le"el locCing that taCes place at the data.ase le"el !ur use o& an @83 maCes this
possi.le Because o& the @83 techni,ue= SAP so&t;are is then &ree to esta.lish actual data.ase locCing in line ;ith ;hate"er particular data.ase "endors consider
optimal &or their data.ase
+he @83 o& SAP so&t;are is a logical unit consisting o& dialog steps= ;hose changes are ;ritten to the data.ase in a single data.ase @83 8nliCe a data.ase
@83= an @83 in SAP so&t;are can span se"eral dialog steps= and can .e executed using a series o& di&&erent ;orC processes %n an application program= #ou end
an @83 o& SAP so&t;are either ;ith the PC!MM%+ 3!R<Q or PR!@@BAC< 3!R<Q statement An SAP so&t;are transaction is an application program that
#ou start ;hen using a transaction code %t can contain one or more @83s o& SAP so&t;are 3hene"er the so&t;are reaches a PC!MM%+ 3!R<Q or
PR!@@BAC< 3!R<Q statement - not at the end o& the last dialog step o& the SAP so&t;are transaction - it opens a ne; @83 o& SAP so&t;are %& a particular
application re,uires that #ou ;rite a complex transaction= it can o&ten .e use&ul to arrange logical processes ;ithin the SAP so&t;are transaction into a se,uence o&
indi"idual @83s o& SAP so&t;are
2> P-e+)e )/..e)( 74+( o*er+(,on) 3+n 6e )/**or(ed +( )(+ndE+-one 6r+n34e), 74,34 do no( 4+0e ne(7or8 3onne3(,0,(1. E-+6or+(e (4e *o)),6-e +r34,(e3(/re
+nd 5/n3(,on+- 3o0er+.e.
%mplementer to respond
Annex B: Appendix 3B- Compliance Sheet
Page 18 of 89
25 A0+,-+6,-,(1 o5 ;,<Te)( )1)(e2 , ;II< Prod/3(,on )1)(e2 , ;III< S(+nd61 S1)(e2,
+hese are &ull# supported +he integrated transport management s#stem controls all mo"ement .et;een en"ironments in a secure and controlled manner
2C In 3+)e o5 +n1 5+,-/re o5 (4e 2+,n )er0er) +nd +) re)/-( )1)(e2 )7,(34 (o o55-,ne 2ode 4o7 D+(+ )1n34ron,)+(,on 7,-- 6e +34,e0ed?, 74+( +6o/( (4e )1)(e2
5e+(/re (o +))/re D+(+ ,n(e.r,(1? *-e+)e e@*-+,n
SAP so&t;are pro"ides transaction roll.acC 9not sa"ing incomplete transactions: and data.ase reco"er# in the e"ent o& so&t;are interruptions *rom the point o&
"ie; o& data.ase programming= a data.ase logical unit o& ;orC 9@83: is an insepara.le se,uence o& data.ase operations that ends ;ith a data.ase commit +he
data.ase @83 is either &ull# executed .# the data.ase s#stem or not at all !nce a data.ase @83 has .een executed success&ull#= the data.ase is in a consistent
state %& an error occurs ;ithin a data.ase @83= all o& the data.ase changes since the .eginning o& the data.ase @83 are re"ersed +his lea"es the data.ase in the
state it ;as in .e&ore the transaction started
+he data.ase changes that occur ;ithin a data.ase @83 are not actuall# ;ritten to the data.ase until a&ter the data.ase commit 8ntil this happens= #ou can use a
data.ase roll.acC to re"erse the changes %n SAP so&t;are= #ou can use either implicit or explicit commands to trigger data.ase commits and roll.acCs SAP has
de"eloped a uni,ue techni,ue that completel# insulates the user &rom lo;-le"el locCing that taCes place at the data.ase le"el !ur use o& an @83 maCes this
possi.le Because o& the @83 techni,ue= SAP so&t;are is then &ree to esta.lish actual data.ase locCing in line ;ith ;hate"er particular data.ase "endors consider
optimal &or their data.ase
+he @83 o& SAP so&t;are is a logical unit consisting o& dialog steps= ;hose changes are ;ritten to the data.ase in a single data.ase @83 8nliCe a data.ase
@83= an @83 in SAP so&t;are can span se"eral dialog steps= and can .e executed using a series o& di&&erent ;orC processes %n an application program= #ou end
an @83 o& SAP so&t;are either ;ith the PC!MM%+ 3!R<Q or PR!@@BAC< 3!R<Q statement An SAP so&t;are transaction is an application program that
#ou start ;hen using a transaction code %t can contain one or more @83s o& SAP so&t;are 3hene"er the so&t;are reaches a PC!MM%+ 3!R<Q or
PR!@@BAC< 3!R<Q statement - not at the end o& the last dialog step o& the SAP so&t;are transaction - it opens a ne; @83 o& SAP so&t;are %& a particular
application re,uires that #ou ;rite a complex transaction= it can o&ten .e use&ul to arrange logical processes ;ithin the SAP so&t;are transaction into a se,uence o&
indi"idual @83s o& SAP so&t;are
2D Pro0,de (4e 2,n,2/2 WAN 6+nd7,d(4 re9/,re2en( 5or re2o(e -o3+(,on *er /)er 8ee*,n. ,n 2,nd FEWA 7,-- 4+0e MPS ne(7or8 +( (4e
,2*-e2en(+(,on (,2e, +n1 ne(7or8 *ro(o3o-/In(er5+3e ,) re9/,red ;*-e+)e )(+(e +-- ne(7or8 de*enden3,e) <. A-)o *-e+)e ,n3-/de 1o/r re3o22end+(,on 5or
WAN +33e-er+(or
%mplementer to respond I S% +eam to respond
2F W4+( ,) (4e ./+r+n(eed re)*on)e (,2e o5 (4e *ro*o)ed )o-/(,on ; +))/2,n. 4,.4 )*eed ne(7or8 ,) +0+,-+6-e <
%mplementer to respond I S% R EP' +eam to respond
29 Doe) (4e )1)(e2 )/**or( +33e)) o5 (4e +**-,3+(,on 5ro2 + re2o(e -o3+(,on (4ro/.4 "PN/SSE"PN? Pro0,de de(+,-).
-PE/SS@--PE is &ull# supported .# Sap applications See supporting material on Eet;ea"er &or &ull details
&0 In 3+)e o5 re*-,3+(,on o5 d+(+, *-e+)e de(+,- (4e (1*e o5 d+(+ (4+( ,) re*-,3+(ed +3ro)) -o3+(,on). De)3r,6e 1o/r re*-,3+(,on 2e34+n,)2.
SAP supports data replication ;here appropriate to support processing= &or example ;hen using mo.ile de"ices %nstalled locall# on each mo.ile de"ice= the SAP
Eet3ea"erM Mo.ile component client includes its o;n s#nchroni6ation la#er= persistence la#er= user inter&ace 98%: runtime 9local 3e. ser"er or a.stract
;indo;ing toolCit:= and other con"enience application programming inter&aces o&&ered to mo.ile applications +his is all part o& a light-installation runtime
en"ironment that extends enterprise capa.ilities to users= ;hether or not the# are connected to the net;orC Mo.ile applications use the &unctionalit# o&&ered .# the
SAP Eet3ea"er Mo.ile client to run their local .usiness logic= data persistence= data "alidation= and 8%
%n the disconnected mode= users access data stored on the client?s local data persistence 3hen the client is in online mode= users can s#nchroni6e clients to upload
the changed data and get the latest data &rom the data orchestration engine 9'!E:
*or data changed or edited in the &ield= SAP Eet3ea"er Mo.ile pro"ides a s#nchroni6ation and replication la#er that resol"es enterprise-le"el data redundanc# .#
s#nchroni6ing the mo.ile de"ice ;ith .acC-end s#stems through the '!E to smartl# resol"e all redundancies in the application ser"er proacti"el#= to ensure data
consistenc# SAP Eet3ea"er Mo.ile also includes a centrali6ed= role-.ased deplo#ment console that simpli&ies deplo#ment tasCs in a glo.al= multiple-de"ice %+
en"ironment
Annex B: Appendix 3B- Compliance Sheet
Page 19 of 89
&1 In 3+)e o5 2od/-e) 6e,n. (,.4(-1 ,n(e.r+(ed, e55e3( o5 +n1 34+n.e 2+de (o +n +**-,3+(,on on (4e o(4er +**-,3+(,on)?
SAP upgrade process ensures &ull s#nchroni6ation across applications All applications are Cept in s#nch using the enhancement pacCage concept Clients add Bust
the .usiness &unctionalit# re,uired= enhancement pacCs ensure all a&&ected application components are s#nchroni6ed


&2 S/**or( 2,rror,n. o5 d+(+ ,n(o + )e3ond+r1 )er0er ;e... B+(34, Re+-E(,2e, On-,ne ;(,2e -+.< .. e(3 < *-e+)e *ro0,de de(+,-)
An+nd (o Re)*ond
&& In 3+)e (4e )1)(e2 re9/,re) )*e3,5,3 dr,0er) 5or ; Pr,n(er), )3+nner) ..e(3 < , 2en(,on (4e2 +-on. 7,(4 (4e n+2e o5 (4e 0endor).
An+nd (o Re)*ond NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
&> W,-- (4e ),Be o5 d+(+6+)e +55e3( (4e )*eed o5 re(r,e0+-? , *-e+)e e@*-+,n
Retrie"al speed is al;a#s a &unction o& ecos#stem design B# ensuring the correct com.ination o& A3= net;orC and management strategies= response times can .e
Cept to suita.le le"els
2007 2008 2009 2010-2015 2006
SAP NetWeaver
SAP ERP 6.0
Enhancement Packages
Next
ERP
Release
Annex B: Appendix 3B- Compliance Sheet
Page 20 of 89
&5 P-e+)e *ro0,de (4e (e34n,9/e +nd ,n(e.r+(,on 5or D+(+ W+re4o/),n. 5or +-- 4,)(or,3+- d+(+
+he SAPM solution includes the SAP Eet3ea"er Business %ntelligence 9SAP Eet3ea"er B% : component= ;hich is a &ull# &unctional= end-to-end data ;arehouse
that is tightl# integrated to SAP?s transactional s#stems= .ut open to other data sources %t is .uilt on data ;arehousing P.est practicesQ= using star-schema to
pro"ide multi-dimensional anal#sis %t comes pre-con&igured ;ith data models .ased on SAP?s industr# experience 9.oth cross-industries and speci&icall# &or retail:
co"ering all aspects - such as procurement= suppl# chain= &inancials= sales= in"entor#= assets= and so on +he models= ho;e"er= are open to additional con&iguration
to meet the speci&ic needs o& the .usiness= .ut the approach means a much ,uicCer time or lo;er cost to implement .ased on a rigorous 9and ;idel# accepted:
metadata schema
SAP Eet3ea"er B% has a range o& E+@ tools 9extraction= trans&ormation= and load: *rom the SAP transactional s#stems there is a "er# tight le"el o& integration
;ith approximatel# 0(( integration points= ;hich include the a.ilit# to drill .acC &rom the reports to actual transaction screens @oad supports a delta mechanism
9loading onl# changes since the last load: and real-time data &eeds +he data ;arehouse is e,uall# suited to loading non-SAP data "ia a range o& in-.uilt E+@
capa.ilities &rom simple &lat &ile loads to the uni"ersal data integrator 98'%: that connect "ia !'B! and >'BC dri"ers to o"er $(( potential sources
Reporting is a"aila.le in a thin client 9needs onl# a 3e. .ro;ser such as %nternet Explorer / *ire&ox: and an MS Excel client Both inter&aces gi"e the end users an
interacti"e reporting en"ironment ;here the# can slice and dice the data= &ilter on &ields and drill do;n to the detail
+he solution has a series o& open inter&aces &or loading data= exchanging metadata 9designed to meets the C3M% I common ;arehouse metadata interchange
standards: and !'B!= BAP%M programming inter&ace and xmla inter&aces &or alternati"e &ront-end reporting tools +here are man# certi&ied third part# reporting
tools that can access "ia these inter&aces including tools such as Cognos= Business !.Bects= SAS= A#perion= and so on
1.1.& Re3o22ended '+rd7+re
Please pro"ide the details o& proposed hard;are that compl# ;ith the ERP principle recommendations that ;ill .e the &oundation o& the entire solution 9 please
indicate #our hard;are solution is it .ased on ne; hard;are or using the existing one: %n all solution scenarios= the o&&er should cater &or the &ollo;ing
1: *E3A ;ould pre&er to ha"e the &ollo;ing en"ironments o& the application:
a Sand-.ox
. 'e"elopment
c +est
Annex B: Appendix 3B- Compliance Sheet
Page 21 of 89
d Production
$: +he recommended hard;are deplo#ment architecture should consider a 'isaster Reco"er# pro"isioning site
3: Current .usiness "olumes and expected s#stem per&ormance are pro"ided in Annex B - Appendix 3A o& the .id documents +he s#stem should .e
si6ed to support at least $(T gro;th in .usiness "olumes &or a 1 #ear period= ;ithout an# per&ormance degradation or the need o& hard;are upgrade
): Aard;are redundanc# ;ithout an# single point o& &ailure
1: %n addition to the ser"ers and storage9SAE:= Bidders are also re,uested to pro"ide speci&ications &or other de"ices such as:
a Aigh Speed= 5ualit#= and Aea"# 'ut# printers to &acilitate printing o& customer .ills
. Storage de"ices
c BacCup de"ices
d An# other de"ices= that ma# .e re,uired &or smooth operations o& the proposed solution
/: Please pro"ide an o"erall schematic la#out &or the hard;are en"ironment that clearl# highlight the connecti"it# .et;een them and the net;orC
inter&ace ;ith ser"er/storage assignment per module 9i& an#: %n addition= &or each element please list the &ollo;ing &acts:
S#stem name
Model
Processor 9Please pro"ide details:
Proposed RAM/ Maximum RAM
Proposed disC dri"e capacit#/ Maximum disC dri"e capacit#
Operating System
Eame and "ersion
Eet;orCing protocol supported 9@a#er $ and @a#er 3 :
!ther details
1.2 Pro*o)ed A**-,3+(,on Mod/-e) +nd EESer0,3e) In(er5+3e
1.2.1 Pro*o)ed A**-,3+(,on Mod/-e)
Please pro"ide the &ollo;ing details &or each o& the proposed &unctional areas Customer Relationship ManagementR Billing= *inance R Accounting= Suppl# Chain
Management= Auman Capital Management= Asset @i&ec#cle Management= Per&ormance Management 9Business %ntelligence:
A**-,3+(,on Are+% Customer Relationship ManagementR Billing= *inance R Accounting= Suppl# Chain Management= Supplier relationship
management= Auman Capital Management= Enterprise Asset @i&ec#cle Management= Mo.ile in&rastructure= Per&ormance Management/Business
%ntelligence 9.usiness !.Bects: and Eet3ea"er
1 Please pro"ide a list o& the application modules proposed to address the re,uirements o& this &unctional area:
Annex B: Appendix 3B- Compliance Sheet
Page 22 of 89
A**-,3+(,on Mod/-e
1 Core ERP 9 *inancials R Controlling= Suppl# Chain Management= Asset @i&ec#cle
Management= Maintenance= 'ocument Management S#stem= Auman Resources= Sel&
Ser"ice Auman ResourcesU:
$ ERP .usiness Suite 9 $2( users= de"eloper= .usiness expert= pro&essional R limited
pro&essional F 1((( emplo#ee sel& ser"ice:
3 Pa#roll 9 3$(( emplo#ee master records:
) %%- %S-8 CRM R Billing &or 8tilities Customer *inancial Management &or 8tilities
1 Business !.Bects Reporting 9 Cr#stal Reports= 3e. %ntelligence=Polestar= Ncelcius
Enterprise=Enterprise Premium= 'ash.oard Builder= @i"e !&&ice= Mo.ile= -o#ager:
/ Business %n&ormation R Anal#sis PacCage 9 $2( users:
0 Energ# 'ata Management &or 8tilities
4 AM% I optional
2 En"ironment= Aealth R Sa&et# I optional
1( 3CM I 3orC clearance management I optional
11 BCM - Business Communication Manager - optional
$ Please pro"ide detailed illustration &or the Ce# &eatures o& the proposed application modules %n case pre-printed literature is a"aila.le descri.ing the
&eatures= please attach them as appendixes and mention the re&erence in this section
Please see &le attached
01
!AP_2usiness_!uite__Ac(ie'e_Process_Excellence%_3o4er_Costs%_!ei5e_/66ortunities_7A*8.6)f

-1
CustomerC$re_9_2illin:_7A*8.6)f

31
En$+lin:_A,_nte:r$tion_for_Utilities_7A*8.6)f

*1
!AP_2usiness_Communic$tions_,$n$:ement_for_Utilities_7A*8.6)f

5_!AP_E;!_,$n$:e
ment_!olution_2rief.6)f

61
!tre$m!er'e_Utilities_1_!olution_2rief_7A*8.6)f

71
!tre$m!er'e_Utilites_2ill.6)f

<1
Enter6rise_Asset_,$n$:ement_!olution_2rief_7A*8.6)f

=1
,$ximi5in:_Re'enue_$n)_Retention_.6)f

001
R$te_3ife1C#cle_,$n$:ement_for_Utilities_7A*8.6)f

001
nter$cti'e_D$s(+o$r)s_for_Decision_,$>ers_.6)f

0-1
,$n$:e%_!($re%_$n)_Deli'er_Critic$l_2usiness_Re6orts_.6)f

031
!AP_2usiness/+& ects_nte:r$tion_.6)f

0*1
!AP_2usiness/+& ects_3i'e_/ffice_.6)f

051
!AP_2usiness/+& ects_?celsius_Enter6rise_7A*8.6)f
3 Please pro"ide &lo; charts &or the Ce# .usiness processes supported .# the proposed application modules 8se separate sheets= as needed
Please see Attached &iles

Utilities 2usiness
Processes.6)f

Annex B: Appendix 3B- Compliance Sheet
Page 23 of 89
) Please pro"ide details o& ho; the proposed solution modules integrate/inter&ace ;ith the rele"ant modules o& other application to complement the
solution +his should include the &ollo;ing details:
a An o"erall schematic o& the integration across modules identi&#ing the exchange o& Ce# data elements
+he &ollo;ing graphic is a simple o"er"ie; sho;ing ho; SAP Eet3ea"er process integration 9P%: positioned +he important components and
concepts are listed on the right-hand side
SAP Eet3ea"er P% is part o& the usage t#pe Process %ntegration
. Ao; the integration is achie"ed= ie 9!nline/Batch:G
Realtime 9onlne:= #ou can also use e"ent dri"en
1 Are there an# pre-re,uisites &or installation/implementation o& proposed modulesG %n case there are an#= please list .elo; all the modules re,uired to
implement the proposed module 9Eg %n order to deplo# Pa#roll module= implementation o& AR module ;ill .e a pre-re,uisite:
+he Roadmap &or *E3A has .een designed Ceeping in "ie; these Pre-re,uisites +here is a @ogical progression to implement Modules
*%C! R @ogistics is the Basic Component ;hich should .e implemented .e&ore %S-8= CRM= B! and Portals are implemented
/ Please pro"ide the &ollo;ing implementation considerations &or implementing the proposed application modules +his should .e pro"ided in terms
o&: 9Please use separate sheets= as necessar#:
Annex B: Appendix 3B- Compliance Sheet
Page 24 of 89
a An %mplementation ChecClist= listing the Ce# steps adopted ;hile implementing this module
. A"aila.le con&iguration options highlighting the Ce# parameters that can .e con&igured in the s#stem= *E3A ;ill decide the .est approach &or
the operation 9example: *or implementing 7eneral @edger= the con&iguration options ma# include de&inition o& *inancial Hear= Chart o&
Accounts= Currencies= etc:
c <e# in&ormation re,uirements &rom *E3A 9example: *or implementing %tem Master= *E3A ma# need to pro"ide %tem Categories= %tem
'etails= Replenishment Planning Parameters= etc:
0 'oes the proposed application module pro"ide AP%s &or inter&acing ;ith an# 3
rd
part# applicationG %& so= please pro"ide a list o& a"aila.le AP%s &or
the proposed application module and the &inancial implication i& an#
SAP integrates ;ith +hird Part# Applications either As#nchronousl# using *lat *ile 8pload R 'o;nload using B'C?s
SAP Can also %ntegrate S#nchronousl# using BAP%?s= BA'%?s= E'% %'oc?s= Process %ntegrators in Eon NM@ or NM@ *ormats SAP?s +ransactions
are exposed to 3e. &or an# Ser"ice to .e Consumed .# the +hird Part# S#stem +here is no Additional *inancial %mplication on the same
4 3hat are the &unctional enhancements/ne; &eatures planned in the next release o& the proposed application module and the proposed release= please
include the expecting releasing date
Proposed Release 'ate: %n&ormation is pro"ided in Page 12 o& this document
*unctional Enhancements Planned: %n&ormation is pro"ided in Page 12 o& this 'ocument
Annex B: Appendix 3B- Compliance Sheet
Page 25 of 89
1.2.2 We6),(e +nd EE)er0,3e)
1 Please pro"ide a note descri.ing the e-ser"ices inter&ace capa.ilit# o& each o& the .elo; modules
Customer Relationship Management and Billing
*inance and Accounting
Suppl# Chain Management
Auman Capital Management
Asset @i&ec#cle Management
Per&ormance Management 9Business %ntelligence:
'ocument management s#stem
Supplier Relationship Management
+he# are o"er $4((F e ser"ices a"aila.le &rom SAP= See list .elo;:
Annex B: Appendix 3B- Compliance Sheet
Page 26 of 89
Example o& the e ser"ices &or CRM:

$
'oes the proposed solution support inter&ace capa.ilities ;ith an external e-ser"ices portal %& #our ans;er is #es = please indicate i&
inter&ace &eature has an# limitation = i& so please list all o& the limitation %n addition please indicate the needed pro&essional ser"ices =
so&t;are licenses= Application etc that might needed to implement the inter&ace
Eo @imitations


%n #our proposed solution= please pro"ide a detailed description o& the E-ser"ices Portal capa.ilities
See diagrams .elo;

Annex B: Appendix 3B- Compliance Sheet
Page 27 of 89
Annex B: Appendix 3B- Compliance Sheet
Page 28 of 89
1.2 Re9/,re2en()
Co2*-,+n3e
Re2+r8)
E)er0,3e) Por(+-
SUP MOD
&RD CST FUT NS
1$1
Acti"ation o& Suppl#
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$
Billing complains
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$3
Change o& .ill address
Hes
8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$) Bill en,uir#
Hes
8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$1
Change o& landlord in&o
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$/ Clearance certi&icate re,uest Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$0 Planned !utage :A map ser"ice can .e pu.lished
&or customers ;hose geographical location can
.e highlighted as part o& the planned outage to
re&lect the a&&ected AREAS
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er and
utili6ing the !utage
management and 7%S
s#stems
1$4 Clearance pa#ment re,uest Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$2 Manage statement code Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$1( +ari&& calculator Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$11 Statement code re,uest Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$1$ Contractor Registration= rene;al and pa#ment Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
Annex B: Appendix 3B- Compliance Sheet
Page 29 of 89
1.2 Re9/,re2en()
Co2*-,+n3e
Re2+r8)
1$13 Application &or Permanent
/+emporar#/Additional @oad/Shi&ting
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$1) Building E!C Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$11 'emolition E!C Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$1/ 'istri.ution Su.station %nspection Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$10 Electronic Building -iolation Ser"ice Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$14 @ocal Purchase Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$12 @- 'esign Pro"isional Appro"al Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$( @- %nspection R Release o& Suppl# Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$1 +enders Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$$ Su.station @a#out 'ra;ing Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$3 Su.station @ocation R Si6e Appro"al Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$) ProBect-7eneration 'ocument Su.mission Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$1 @- Shop 'ra;ing Appro"al Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$/ Pro"ide Secure E-ser"ices &or online pa#ment Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$0 *E3A Careers and sel& ser"ices Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$$4 Registered Customer &or *E3A e-ser"ices Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
%n #our proposed solution= please pro"ide a detailed description o& the 3e.site Portal
1.2 Re9/,re2en() Co2*-,+n3e Re2+r8)
E)er0,3e) Por(+- SUP MOD &RD CST FUT NS
1$$2
'#namic Menus
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$3(
Administration modules ;hich ;ill gi"e *E3A
the capa.ilit# to upload ne; &acilities= pages= etc
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
Annex B: Appendix 3B- Compliance Sheet
Page 30 of 89
1.2 Re9/,re2en() Co2*-,+n3e Re2+r8)
1$31
3ell presenta.le ;e.site ;hich is representati"e
o& *E3A?s marCet stature
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$3$
Eas# integration ;ith third part# applications
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$33
*ull training to .e pro"ided &or ;e.site
de"elopment and support
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$3)
3e.site Portal should support Ara.ic R English
978%:
Hes 8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1$31
Bidder should pro"ed minimum three protot#pes
&or the 3e.site design to .e appro"ed .#
*E3A
Hes
8sing e-ser"ices
ena.led .# SAP
Eet3ea"er
1.& Do3/2en( M+n+.e2en( S1)(e2
!ne o& the re,uirements ;ithin this R*P is integration .et;een the ERP and the 'ocument Management S#stem 9'MS:
*E3A currentl# has an existing 'MS PSAPER%!EQ ;hich is inter&aced ;ith the legac# ERP solution +he Bidder has the choice
to o&&er *E3A one o& the &ollo;ing options
8pgrade and re-inter&ace/integrate the existing s#stem ;ith the proposed ERP solution
O55er ne7 Do3/2en( M+n+.e2en( S1)(e2 +nd 2,.r+(e +-- (4e e@,)(,n. do3/2en() ,n(o (4e ne7 *-+(5or2 7,(4 5/--
,n(e.r+(,on 7,(4 (4e ERP
We +re *r*o),n. (4e re*-+3e2en( o5 (4e e@,)(,n. DMS )1)(e2 61 SAP DMS. We )4+-- /)e (4e E@,)(,n. DMS Con(en( Ser0er
+))/2,n. (4+( (4e )+2e ,) 3o2*+(,6-e 7,(4 SAP S1)(e2. In 3+)e (4ere ,) + Co2*+(,6,-,(1 I))/e, (4e )+2e )4+-- 6e re*-,3+(ed ,n
+no(4er S1)(e2.
%& the .idder decides to go ;ith option $ as the methodolog# o& implementing the 'ocument Management S#stem= then the
&ollo;ing re,uirements should .e &ull# maintained and complied +!:
E&&icienc# - Eo time lost &iling R retrie"ing documents
Colla.oration - Share documents ;ith others among the net;orC an# time an# ;here an# media
Access - Access documents o"er the %ntranet= %nternet and/or extranet
Securit# - Pro"ide controlled access to speci&ic document .ased on +A7 = and ;ith access log
Sa"ings - Reclaim space used to stored documents
Compliance - Compl# ;ith go"ernment regulations &or %ntegrit#= A"aila.ilit#= Securit# and Con&identialit#
'isaster Reco"er# I A.ilit# to ensure .usiness continuit# .# protecting documents &rom natural and other
disasters 9 @ocall# and/or o&&site :
Simpli&ication E Single mechanism to manage .oth electronic and paper documents
Please pro"ide a note descri.ing the 'ocument Management s#stem= Clearl# clari&# compliance o& the do;n .elo; :
1.& Do3/2en( M+n+.e2en( S1)(e2 Co2*-,+n3e Re2+r8)
SUP MOD &RD CST FUT NS
131
*E3A can create a single centrali6ed repositor# o& all their electronic R
paper documents And a.ilit# to pro"ide their sta&& ;ith controlled access to
this repositor# ;ith Aierarchical Storage Management
Hes 8sing
SAP core
'MS
S#stem
13$
+he document management so&t;are pro"ides &ast= relia.le and securit#-
controlled access to these documents throughout the compan# net;orC
Hes 8sing
SAP core
'MS
S#stem
133
%ntegrated 3orC&lo; ;hich allo;s routing documents 9.ased on preset
Hes 8sing
Annex B: Appendix 3B- Compliance Sheet
Page 31 of 89
1.& Do3/2en( M+n+.e2en( S1)(e2 Co2*-,+n3e Re2+r8)
SUP MOD &RD CST FUT NS
rules:= and support automatic escalation &lo;
SAP core
'MS
S#stem
and 3orC
*lo;
engine
13)
Eas#-to-use inter&ace
Hes 8sing
SAP core
'MS
S#stem
B#
utili6ing
the
internet
.ro;ser or
SAP 78%
or MS
Explorer
131
7reatl# impro"ed the e&&ecti"eness and e&&icienc# o& the .usiness operations
Hes 8sing
SAP core
'MS
S#stem
13/ 3ith a high securit# measure= the proposed solution should allo; document
marC-ups 9ie notes and highlights: ;ithout altering the original document
and also allo;s to print or email an# document on the s#stem
Hes 8sing
SAP core
'MS
S#stem
including
redlining
and
electronic
stamp
130
Allo;s to locate document ,uicCl# and easil# 9 please explain :
Hes 8sing
SAP core
'MS
S#stem
8sing
SAP
search
engine
and use
the
'ocument
*inder to
&ind and
displa#
documents
134
+he 'MS ma# extract metadata &rom the document automaticall# or prompt
the user to add metadata
Hes 8sing
SAP core
'MS
S#stem
132
+he proposed solution should support !ptical Character Recognition 9!CR:
on scanned images
Hes +he
'ri"ers
used in the
Scanner
shall
per&orm
the !CR
&unctions
and
communic
ate the
same to
Annex B: Appendix 3B- Compliance Sheet
Page 32 of 89
1.& Do3/2en( M+n+.e2en( S1)(e2 Co2*-,+n3e Re2+r8)
SUP MOD &RD CST FUT NS
SAP in a
*lat *ile
132
Archi"ed data migration &rom the current s#stem
Hes 8sing
SAP core
'MS
S#stem
utili6ing
SAP
migration
tool
131(
%nter&aces= Reports and 'ata that are supported in English/Ara.ic
Hes 8sing
SAP core
'MS
S#stem
1311
'MS should support and integrate ;ith the ERP and CRM/Billing to
achie"e all the transactions that need archi"ing through !CR and !CN
Hes
131$
A.ilit# to archi"e So&t-documents as ;ell as Aard-'ocuments
Hes 8sing
SAP core
'MS
S#stem
1313
'MS should support 'ocuments ;orC&lo;
Hes 8sing
SAP core
'MS
S#stem
131)
Supporting the encr#ption o& the 8R@ in the .ro;ser &or securit# ;ise
Hes 8sing
SAP core
'MS
S#stem
1311
Source Code
Hes 8sing
SAP core
'MS
S#stem
131/
'e"elop a solution &or %n.ound/!ut.ound @etters and internal
announcements U etc
Hes 8sing
SAP core
'MS
S#stem
1.1&.1D Se3/r,(1
13101
Pro"ides role-.ased securit# &or indi"idual authors
Hes SAP
BAS%S
Roles R
Authori6at
ion
1310$
Pro"ides role-.ased securit# &or group o& authors
Hes SAP
BAS%S
Roles R
Authori6at
ion
13103
Pro"ides role-.ased securit# &or organi6ational unit o& groups
Hes SAP
BAS%S
Roles R
Authori6at
ion
1310)
Pro"ides role-.ased securit# &or indi"idual domains/sites
Hes SAP
BAS%S
Roles R
Authori6at
ion
13101
Pre"ents Dun-authori6ed "ie;ing/accessD a&ter permanent deletion
Hes SAP
BAS%S
Roles R
Annex B: Appendix 3B- Compliance Sheet
Page 33 of 89
1.& Do3/2en( M+n+.e2en( S1)(e2 Co2*-,+n3e Re2+r8)
SUP MOD &RD CST FUT NS
Authori6at
ion
1310/
Pre"ents "ie;ing o& expired content
Hes SAP
BAS%S
Roles R
Authori6at
ion
13100
Allo;s access to checCed-out content &rom a secure location
Hes SAP
BAS%S
Roles R
Authori6at
ion
13104
Creates "ie;-onl# &ormat &or content
Hes SAP
BAS%S
Roles R
Authori6at
ion
13102
%mmediatel# re"oCes all access and "ie; pri"ileges
Hes SAP
BAS%S
Roles R
Authori6at
ion
13101(
Restricts access .ased on pro&ile
Hes SAP
BAS%S
Roles R
Authori6at
ion
131011
Restricts access .ased on document
Hes SAP
BAS%S
Roles R
Authori6at
ion
13101$
Applies a securit# categor# to a &ile &older
Hes SAP
BAS%S
Roles R
Authori6at
ion
131013
Applies a securit# categor# to a document
Hes SAP
BAS%S
Roles R
Authori6at
ion
13101)
Applies a securit# categor# to a user
Hes SAP
BAS%S
Roles R
Authori6at
ion
131011
Applies a securit# categor# to a group
Hes SAP
BAS%S
Roles R
Authori6at
ion
13101/
Pro"ides lo;er or e,ual securit# le"el in &ile structure
Hes SAP
BAS%S
Roles R
Authori6at
ion
Annex B: Appendix 3B- Compliance Sheet
Page 34 of 89
1.> F/n3(,on+-/Te34n,3+- Re9/,re2en()
+he appendix pro"ides the Ce# re,uirements &rom the proposed ERP and CRM/Billing application +he re,uirements are
presented in the &orm o& a matrix Each Bidder is re,uired to respond as &ollo;s:
Respond VHes? i& the re,uirement is &ull# met= or i& the ,uestion asCed is &ull# ans;ered Please pro"ide in&ormation in the Comments
column to descri.e ho; #our compan#/s#stem meets the re,uirement
Respond VEo? i& the re,uirement cannot .e met Comments should .e included i& there is an alternate solution %& the re,uirement ;ill .e
met through a planned or &uture release= pro"ide details in the Comments column
Respond VPartial? i& the re,uirement is partiall# met AE' include details as to ;h# in the Comments column %& a re,uirement contains
multiple points and not all can .e supplied then Bust a single OPartialO indication is the appropriate response 'o not address each point=
.ut use the Comments to pro"ide details o& ;hich o& the re,uirements cannot .e met and ;h#
Each last le"el re,uirement should .e responded to as per the &ollo;ing &ashion
E@+2*-e:
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+-
Re2+r8
!e) P+r(. No
221 Bidder ;ill implement &ull ERP S#stem Page $/= Sec 3 *inancial Management ;ill not .e pro"ided
1.>.1 C/)(o2er Re-+(,on)4,* M+n+.e2en( +nd B,--,n.
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
1.0 C/)(o2er Re-+(,on)4,* M+n+.e2en(
11 S#stem should ena.le setup o& a single customer/person record in a single
location= so this record is preser"ed ;hen that person mo"es or ;ishes to
purchase ne; ser"ices
Hes CRM and
.illing
1$ S#stem should support the tracCing o& complex customer o;nerships
associated ;ith that person or customer
Hes CRM and
.illing
13 S#stem should ena.le the de&inition o& user-de&ined &ields to the person R
account records= and these user-de&ined &ields are maintained during
upgrades
Hes CRM and
.illing
1) S#stem should allo; multiple names 9aliases: to .e speci&ied &or the same
person +hese names should all .e a"aila.le &or searching
Hes CRM and
.illing
11 S#stem should ena.le multiple &orms o& identi&ication to .e linCed to the
person Eg 'ri"ers license +hese identi&iers should .e a"aila.le &or
searching
Hes CRM and
.illing
1/ S#stem should ena.le the de&inition o& an account that is linCed to a
speci&ic customer
Hes CRM and
.illing
10 Account in&ormation should contain all critical data related to that account=
including contact persons= pa#ment terms and methods
Hes CRM and
.illing
14 Account should remain linCed to the speci&ic customer inde&initel#=
eliminating the need to setup a ne; account ;hen the person mo"es or
purchases ne; ser"ices
Hes CRM and
.illing
12 S#stem should has the capa.ilities to add a priorit# tag &or certain accounts
and route an# related issues to speci&ic *E3A sta&& &or special handling
Hes CRM and
.illing
11( S#stem should support the association o& a single account ;ith multiple
ser"ices
Hes CRM and
.illing
111 S#stem should support hierarchical linCing o& ser"ices Hes CRM and
.illing
Annex B: Appendix 3B- Compliance Sheet
Page 35 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
11$ +he s#stem should support ser"ices consolidation &or ser"ices that span
o"er multiple locations 9eg= add usage &rom se"eral meters:
Hes CRM and
.illing
113 S#stem should pro"ide ro.ust= eas#-to-use capa.ilities &or starting and
stopping customer ser"ice
Hes CRM and
.illing
2.0 C/)(o2er ,5e313-e M+n+.e2en(
$1 S#stem should ena.le searches .# name= address= account num.er= phone
num.er= person identi&ier= or an# other con&igura.le criteria
Hes CRM and
.illing
$$ 3hen a customer is identi&ied= all appropriate &ields on the s#stem screen
should .e populated and contextual in&ormation .e displa#ed ;here
necessar# 9eg= pa#ment in&ormation should displa# on the pa#ment
screen:
Hes CRM and
.illing
$3 S#stem should pro"ide a contextual= user-centric portal that displa#s onl#
the account in&ormation that is most applica.le to the needs o& the user
Hes CRM and
.illing
$) +he s#stem should ha"e an optional dash.oard ;hich allo;s the user to
maintain &ocus o& the customer R account in context= contact notes= and
&inancial in&ormation %t should also .e a.le to sho; ;orC items
Hes CRM and
.illing
$1 +he portal should .e &ull# con&igura.le= allo;ing *E3A to con&igure
speci&ic portals around alerts= .illing graphs= &inancial .alances= other
account details= etc
Hes CRM and
.illing
$/ *E3A should .e a.le to em.ed con&igured speci&ic .usiness processes to
.e launched &rom an# o& the data displa#ed in the portals
Hes CRM and
.illing
$0 S#stem should maintain contact notes and other contact data as customer
contact records
Hes CRM and
.illing
$4 S#stem should pro"ide ro.ust integration capa.ilities ;ith Contact Center
"ia C+% and to support %-R portal integration
Hes CRM and
.illing
$2 S#stem should pro"ide a Pone-stepQ enrollment process &or ne; customers
in a ,uicC R e&&icient &ashion and .e a.le to "alidate the data
Hes CRM and
.illing
$1( S#stem should pro"ide &or the creation o& PpacCagedQ ser"ices that ma#
trigger a discount
Hes CRM and
.illing
&.0 C/)(o2er B,--,n. E B,-- R+(,n.
31 S#stem should pro"ide a ro.ust rating engine that de&ines the pricing &or
products and ser"ices o&&ered to the marCet
Hes CRM and
.illing
3$ +he rating engine should .e con&igura.le ;ithout the need &or
customi6ation
Hes CRM and
.illing
33 +he rating engine should allo; the de&inition o& products that accept
charges calculated ;ithin external applications= optionall# adding other
calculations 9eg= -A+= taxes etc: to &acilitate .ill consolidation
Hes CRM and
.illing
3) S#stem should support complex regulated R unregulated rate calculations
;ithout the need to modi&# the .ase s#stem
Hes CRM and
.illing
31 S#stem should permit rates to ha"e multiple components that produce the
actual charges on .ills
Hes CRM and
.illing
3/ S#stem should support plug-ins or other non-customi6ed &unctionalit# that
support more complex rate calculations
Hes CRM and
.illing
30 S#stem should support short and long .illing rates= as ;ell as rate changes
during a period 9;ithout an# &urther de"elopment:
Hes CRM and
.illing
Annex B: Appendix 3B- Compliance Sheet
Page 36 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
34 S#stem can de&ine multiple rules use to modi&# consumption "alues
.e&ore appl#ing the rate
Hes CRM and
.illing
32 S#stem should also support consumption estimates ;here ad"anced
metering is not used Please explain the methodolog# that the s#stem does
support
Hes CRM and
.illing
31( +he s#stem should ena.le the &ollo;ing speci&ication o& prices: CRM and
.illing
31(1 'irectl# on the rate Hes CRM and
.illing
31($ -ia a .ill &actor that can .e re&erenced on multiple rates Hes CRM and
.illing
31(3 As the result o& another rate component Hes CRM and
.illing
31() As the result o& a set o& con&igura.le rules Hes CRM and
.illing
31(1 As entered into the s#stem "ia an inter&ace to an external s#stem Hes CRM and
.illing
311 +he s#stem should allo; the de&inition o& P.ill &actorsQ that contain
&re,uentl# used amounts= and can .e setup to de&ine &lat &ees= per-unit &ees=
and percentage rates
Hes CRM and
.illing
31$ +he "alues o& .ill &actors must .e date e&&ecti"e to ena.le simple changes
o"er time
Hes CRM and
.illing
313 Proration should .e supported ;hen the .ill &actor "alue changes during
the .illing period
Hes CRM and
.illing
31) +he s#stem should ena.le P;hat i&Q anal#sis to test the results o& appl#ing
a particular rate in "arious scenarios
Hes CRM and
.illing
311 +he s#stem should handle sophisticated cross-product discounting
scenarios
Hes CRM and
.illing
>.0 C/)(o2er B,--,n. 9 should support all the &ollo;ing :
)1 %nternall# rated charges 9rated .# the s#stem?s rating engine: Hes CRM and
.illing
)$ Externall# rated charges 9passed through &rom another s#stem: Hes CRM and
.illing
)3 Complex .illing charges 9eg hal&-hourl# electricit# charges: Hes CRM and
.illing
)) Ad"ance .illing ;ith ser"ice pro"isioning Hes CRM and
.illing
)1 Billing o& metered ser"ices Hes CRM and
.illing
)/ Billing o& non-metered ser"ices Hes CRM and
.illing
)0 *ees= such as &lat rate 9&or example= a connection charge: S#stem should
also allo; &or the calculation o& &ees as a percentage o& another charge 9&or
instance= a late &ee on an o"erdue .alance:
Hes CRM and
.illing
)4 S#stem should pro"ide the &ollo;ing standard .illing capa.ilities: Hes CRM and
.illing
)41 Automatic handling o& meter exchanges Hes CRM and
.illing
)4$ Proration o& long or short .ill periods Hes CRM and
.illing
)43 *irst and last .ills Hes CRM and
.illing
)4) !ptional estimation o& meter reads ;hen actual data is not a"aila.le Hes CRM and
.illing
Annex B: Appendix 3B- Compliance Sheet
Page 37 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
)41 Automatic normali6ation o& consumption in&ormation &or rate
calculation &or .ills ;hen .illing period is longer/shorter than user-
speci&ied range
Hes CRM and
.illing
)4/ Calculation and addition o& taxes Hes CRM and
.illing
)40 'iscounts Hes CRM and
.illing
)44 Margins Hes CRM and
.illing
)42 Customi6ation o& .ill due dates Hes CRM and
.illing
)41( 'e&inition o& exact due dates Hes CRM and
.illing
)411 !"errides on due dates Hes CRM and
.illing
)2 S#stem should generate a summar# .ill that can .e associated ;ith man#
additional ser"ices
Hes CRM and
.illing
)1( S#stem should pro"ide .ill printing R rendering o& online .ill image
&unctionalit#
Hes CRM and
.illing
)11 S#stem should support cancel/re-.ill &unctionalit#= to permit recalculation
o& charges once source data is corrected
Hes CRM and
.illing
)1$ S#stem should support online= real-time corrections o& indi"idual .ills Hes CRM and
.illing
)13 S#stem should support automatic re-.illing ;hen earlier meter-read
estimates &all a.o"e or .elo; pre-de&ined thresholds
Hes CRM and
.illing
)1) S#stem should support the speci&ication o& a date range during ;hich .ills
ma# .e produced= ;hich ena.les *E3A to immediatel# .egin .ill
production as meter reads come in
Hes CRM and
.illing
)11 S#stem can automaticall# create statements that consolidate in&ormation
across multiple accounts and/or multiple .illing periods
Hes CRM and
.illing
)1/ S#stem should pro"ide .illa.le charge templates and other tools to support
one-o&& and 3
rd
part# charges that &all outside normal .usiness operations
Hes CRM and
.illing
)10 S#stem can .ill customers a standard .udget amount each period= .ased on
pre"ious usage trends= customer histor#= or other &actors
Hes CRM and
.illing
)14 S#stem should support con"ergent .illing= ie= the consolidation o& .illing
in&ormation created .# other s#stems in a single .ill to the customer
Hes CRM and
.illing
)12 S#stem can add permanent or one-time messages to .ills= including meter
reading remarCs and ad hoc CSR comments
Hes CRM and
.illing
5.0 C/)(o2er B,--,n. E M/-(, P+r(1 B,--,n.
11 S#stem should maintain contract agreement in&ormation &or ser"ices
pro"iders= including the &ollo;ing ser"ice pro"ider t#pes:
CRM and
.illing
111 Energ# 9energ# suppl# companies= energ# ser"ice pro"iders= retailers= and
suppliers:
Hes CRM and
.illing
11$ Meter ser"ice 9meter ser"ice pro"iders and meter agents: Hes CRM and
.illing
113 Meter reading 9meter data management agencies R meter reading ser"ice
pro"iders:
Hes CRM and
.illing
11) Billing 9.illing agents: Hes CRM and
.illing
1$ S#stem should maintain the &ollo;ing relationship t#pes: Hes CRM and
Annex B: Appendix 3B- Compliance Sheet
Page 38 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
.illing
1$1 Billing relationships Hes CRM and
.illing
1$$ Consumption relationships Hes CRM and
.illing
1$3 Recei"a.le 9pa#ment: relationships Hes CRM and
.illing
13 S#stem should support "arious t#pes o& .illing calculations and
presentation= including the &ollo;ing:
Hes CRM and
.illing
131 Rate-read#= ;hen another ser"ice pro"ider?s rates are loaded into the
s#stem
Hes CRM and
.illing
13$ Bill-read#= ;hen another ser"ice pro"ider?s calculated charges are loaded
into the s#stem
Hes CRM and
.illing
133 Billing on .ehal& o& a ser"ice pro"ider Hes CRM and
.illing
13) Consolidated ser"ice pro"ider .illing o& charges %n this instance= charges
are inter&aced to another ser"ice pro"ider= ;hich the s#stem "ie;s as the
customer
Hes CRM and
.illing
131 Split .illing= ;here multiple pro"iders ;ere each o& them has their o;n
.illing charges
Hes CRM and
.illing
1) Proposed solution should compl# ;ith local marCet transaction standards
in a deregulated marCet 9eg= s#stem s;itches ser"ice pro"iders as
customers direct:
Hes CRM and
.illing
11 Bidder should support updates to the marCet transaction &unctionalit# as
ne; marCet standards and rules are pu.lished .# the go"erning .odies
Hes CRM and
.illing
1/ +he s#stem should support in &light messages ;hen standards change Hes CRM and
.illing
10 +he s#stem should .e a.le to displa# marCet transactions ;hich are
directl# linCed to the rele"ant customer records and .e a.le to see the
automated processing and pro"ide support &or manual inter"ention ;hen
necessar#
Hes CRM and
.illing
14 +he s#stem should .e a.le to either integrate ;ith a transaction hu. or
parse large incoming message &iles into indi"idual transactions
Hes CRM and
.illing
12 @ist deregulated energ# marCets ;here the so&t;are has .een
implemented
Hes CRM and
.illing
C.0 Re3e,0+6-e) M+n+.e2en( E P+12en( Pro3e)),n.
/1 S#stem can manage pa#ments &rom man# sources= including mailed-in or
;alC-in pa#ments= remittance processors= locC .oxes= etc
Hes CRM and
.illing
/$ S#stem should support .atch processing o& pa#ments 9ie through staging
ta.les: to permit the creation o& pa#ments in the s#stem &rom di&&erent
source
Hes CRM and
.illing
/3 *or pa#ment distri.ution= s#stem should support either P.alance &or;ardQ
9in ;hich pa#ments are applied to the oldest de.t &irst: or Popen itemQ
distri.ution 9in ;hich pa#ments are applied to speci&ic .ills= charges=
ser"ice agreements= or a com.ination o& these:
Hes CRM and
.illing
/) S#stem should support automatic pa#ments= including Electronic *unds
+rans&ers 9E*+:= direct de.its= and credit card pa#ments
Hes CRM and
.illing
/1 S#stem should support pa#ment alternati"es 9pa# plans= etc: under
automatic pa#ment pro"isions
Hes CRM and
.illing
// S#stem should support prepa#ment in ad"ance o& ser"ice R.e a.le to
calculate amount o& allo;a.le consumption
Hes CRM and
.illing
Annex B: Appendix 3B- Compliance Sheet
Page 39 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
/0 S#stem should support integration ;ith prepaid metering de"ices Hes CRM and
.illing
/4 S#stem should support &ollo;ing cashiering &unctions: CRM and
.illing
/41 Adding and "ie;ing pa#ments online Hes CRM and
.illing
/4$ Scanning .ill stu.s Hes CRM and
.illing
/43 Endorsing checCs Hes CRM and
.illing
/4) Printing receipts Hes CRM and
.illing
/41 Managing and .alancing indi"idual cash dra;ers in a pa#ment center Hes CRM and
.illing
/4/ Single/multiple checC9s: &or multiple accounts Hes CRM and
.illing
/40 Popup messages alerting operators to excess cash in a dra;er Hes CRM and
.illing
/44 !nline= real-time trans&er or pa#ments .et;een accounts 9to &acilitate error
correction:
Hes CRM and
.illing
/2 S#stem can halt ongoing collection acti"it# i& pa#ment is recei"ed &or a
delin,uent account
Hes CRM and
.illing
/1( S#stem should support online cancellation o& pa#ments and le"#ing o&
automatic &ees &or .ounced checCs
Hes CRM and
.illing
/11 S#stem should pro"ide po;er&ul search capa.ilities to help users locate a
particular pa#ment= including:
CRM and
.illing
/111 Account 9.# name or Account %': Hes CRM and
.illing
/11$ Amount 9;ith a V.et;een? range allo;ed: Hes CRM and
.illing
/113 Pa#er Account 9.# name or Account %': Hes CRM and
.illing
/11) Pa#ment tender amount 9;ith V.et;een? range allo;ed: Hes CRM and
.illing
/111 +ender Source Hes CRM and
.illing
/11/ Pa#ment 'ate range Hes CRM and
.illing
/1$ S#stem should pro"ide &or the creation o& non-.illed .udget plans to
standardi6e a customer?s pa#ments o"er time= particularl# ;here .ills are
created in&re,uentl#
Hes CRM and
.illing
D.0 Re3e,0+6-e) M+n+.e2en( E Cred,( L Co--e3(,on)
01 S#stem can monitor ho; much customers o;e to ensure the# ha"e not
"iolated de.t prede&ined le"els
Hes CRM and
.illing
0$ +he de.t should .e monitored .# .alance due or .# indi"idual items such
as .ills= adBustments= or charges
Hes CRM and
.illing
03 3hen a "iolation is detected= the s#stem should support the &ollo;ing: CRM and
.illing
031 Encourage the customer to pa# Hes CRM and
.illing
03$ +erminate ser"ice Hes CRM and
.illing
033 3rite o&& de.t Hes CRM and
.illing
0) S#stem encourages customers to pa# .# pro"iding the &ollo;ing &unctions: CRM and
.illing
0)1 7enerate letters Hes CRM and
.illing
Annex B: Appendix 3B- Compliance Sheet
Page 40 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
0)$ Credit-rating noti&ications Hes CRM and
.illing
0)3 Cancel existing .udget plans Hes CRM and
.illing
0)) An out.ound call to the customer Hes CRM and
.illing
0)1 Esta.lish pa#ment plans 9installments= le"elised .ill pa#ments= etc: Hes CRM and
.illing
01 S#stem should initiate se"erance processing i& the a.o"e steps do not
result in a satis&actor# pa#ment arrangement
Hes CRM and
.illing
0/ S#stem should .e a.le to create a ;rite-o&& e"ent to trigger a collection
agenc# re&erral
Hes CRM and
.illing
00 S#stem should support automatic and manual cancellation o& ;rite-o&&s Hes CRM and
.illing
04 %n the case o& a ;rite-o&&= s#stem should generate accounting noti&ication
processes re,uired to complete the necessar# transactions
Hes CRM and
.illing
02 Credit R collection acti"ities can .e processed automaticall# or manuall#=
or mixture thereo&= .ased on *E3A?s speci&ic practices R regulator#
re,uirements
Hes CRM and
.illing
01( Automaticall#-triggered collection-.ased acti"ities can .e o"erridden
manuall#
Hes CRM and
.illing
011 S#stem can calculate R maintain an internal credit rating on each account
.ased on account li&ec#cle e"ents
Hes CRM and
.illing
Credit
rating ;ill
calculated
externall#
.# a credit
ser"ices
Assuming
the
in&rastruct
ure o&
such
ser"ices
a"aila.le
in 8AE
01$ Collection rules can .e con&igured to taCe the credit rating into account
;hen deciding on the appropriate collection path &or the customer
Hes
013 S#stem should support cash and non-cash deposits= such as letters o& credit
and suret# .onds
Hes @/c R
Suret#
Bonds
Module
;ill .e
de"eloped
01) S#stem can automaticall# recommend a customer?s suggested deposit
amount
Hes CRM and
.illing
011 S#stem can calculate interest on deposits= periodicall# 9"ia a .atch
process: and ;hen a re&und is anticipated %& deposits are recei"ed o"er
time= s#stem calculates interest on each pa#ment separatel#
Hes CRM and
.illing
01/ S#stem can re&und deposits automaticall# ;hen a customer meets user-
de&ined criteria 9;hich ma# .e .ased on credit rating= length o& ser"ice
etc:
Hes CRM and
.illing
010 S#stem should support DchallengerD con&igurations o& collection e"ents
that can .e initiated randoml# to test alternati"es ;hich impro"ed de.t
collection
Hes CRM and
.illing
Annex B: Appendix 3B- Compliance Sheet
Page 41 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
014 Control reports and reconciliation reports +#pical reports liCe cash
collection summar#= receipt cancellation ;ith reason code= reconciliation
.et;een cash collected and deposited to .anC at each area o&&ice etc
Hes
ECC /(
012 *unctionalit# to generate .anC pa#-in-slips &rom the s#stem to a"oid
manual steps
Hes
ECC /(
F.0 F,e-d O*er+(,on) E Geo.r+*4,3 D+(+ M+n+.e2en(
41 S#stem can record .asic geographic in&ormation a.out each location or
address
Hes CRM and
.illing
+he exact
location
and
coordinate
s ;ill
extracted
"ia the
integration
;ith 7%S
4$ Multiple geographic identi&iers ma# .e linCed to the premise/ser"ice
location 9eg= map coordinates= 7PS:
Hes CRM and
.illing
+he exact
location
and
coordinate
s ;ill
extracted
"ia the
integration
;ith 7%S
7PS ;ill
.e utili6ed
to identi&#
the
location
&or routing
and
directions
43 S#stem should support searching .# geographic identi&iers Hes CRM and
.illing
+he exact
location
and
coordinate
s ;ill
extracted
"ia the
integration
;ith 7%S
4) S#stem should support an unlimited num.er o& distinct Ser"ice Points &or
each premise 9A Ser"ice Point is a location ;here a gi"en ser"ice is
actuall# pro"ided:
Hes CRM and
.illing
+he exact
location
and
coordinate
s ;ill
extracted
"ia the
Annex B: Appendix 3B- Compliance Sheet
Page 42 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
integration
;ith 7%S
41 @andlord agreements ma# .e attached to a premise Hes CRM and
.illing
8sing
.usiness
document
linC
4/ @andlord agreements should control the automatic ser"ice re"ersion rules
9to the landlord: ;hen a tenant mo"es out o& a premise
Hes CRM and
.illing
40 S#stem should ena.le the linCage o& multiple Ser"ice Points to a single
ser"ice agreement
Hes CRM and
.illing
44 S#stem should also ena.le the linCage o& a single Ser"ice Point to multiple
ser"ices
Hes CRM and
.illing
42 S#stem should pro"ide &or hierarchical structuring o& parent R child
premises &or .uildings= Mall= apartment complexes= etc
Hes CRM and
.illing
9.0 F,e-d O*er+(,on) E Pre2,)e M+n+.e2en(
21 S#stem should pro"ide po;er&ul ,uer# R other tools that can ,uicCl#
per&orm mass updates on premises or checC the account status o&= 9ie all
apartments in a .uilding:
Hes CRM and
.illing
2$ Mass updates actions should= at a minimum= include: Hes
2$1 Assign or remo"e parent premise Hes CRM and
.illing
2$$ Assign or remo"e landlord Hes CRM and
.illing
2$3 Start or stop ser"ice Hes CRM and
.illing
10.0 F,e-d O*er+(,on) E Me(er +nd De0,3e M+n+.e2en(
1(1 S#stem can record the relationship .et;een a de"ice and the Ser"ice Point
it ser"es
Hes CRM and
.illing
8sing
'e"ice
manageme
nt
1($ S#stem can tracC meters R e,uipment installations through their li&e c#cle
3hen meters are used at di&&erent locations= records are Cept o& initial and
terminal readings at each site
Hes CRM and
.illing
8sing
'e"ice
manageme
nt
1(3 8sers should .e a.le to access the histor# o& a meter or ser"ice point=
including all meters installed o"er time
Hes CRM and
.illing
8sing
'e"ice
manageme
nt
1() S#stem should allo; &or speci&ication o& a stocC location 9;hich includes
on hand in a trucC: ;hene"er a meter or item is remo"ed &rom a ser"ice
point
Hes CRM and
.illing
8sing
'e"ice
manageme
nt and
material
manageme
nt
1(1 +racCing .# stocC location can .e acti"ated &or indi"idual meter t#pes and
item t#pes
Hes CRM and
.illing
8sing
Annex B: Appendix 3B- Compliance Sheet
Page 43 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
'e"ice
manageme
nt
1(/ S#stem can maintain records on non-metered e,uipment such as
trans&ormers= .acC&lo; de"ices= lamps= and other items installed in the
&ield
Hes CRM and
.illing
8sing
'e"ice
manageme
nt
1(0 S#stem should also .e a.le to handle sets o& un-.adge item t#pes that use a
single Ser"ice Point .ut are not indi"iduall# identi&ied 9ie all lamps in a
parCing lot:
Hes CRM and
.illing
8sing
'e"ice
manageme
nt
1(4 +o reduce data entr#= s#stem should ena.le data replication &rom template
entries &or meters and items= and supports the automatic incrementing o&
.adge num.ers and serial num.ers
Hes CRM and
.illing
8sing
'e"ice
manageme
nt
1(2 S#stem should include &eatures &or selecting de"ices to .e tested and
recording test results
Hes CRM and
.illing
8sing
'e"ice
manageme
nt
including
5A
11.0 F,e-d O*er+(,on) E Me(er Re+d,n.
111 S#stem should support meter read c#cles and routes= to ;hich Ser"ice
Points can .e assigned 9A route is a group o& properties ;hose meters can
.e read .# a meter reader on a gi"en &ull or partial da#:
Hes CRM and
.illing
11$ S#stem pro"ides staging ta.les to load in the meter read data= ;hich is
then processed and used to create meter reads in the s#stem
Hes CRM and
.illing
113 S#stem should support the loading o& reads &rom traditional manual
reading processes= or &rom automatic meter reading s#stems
Hes CRM and
.illing
11) S#stem should permit uploading remarC codes ;ith meter read data Hes CRM and
.illing
111 +he remarC code should .e a.le to trigger one or more user-de&ined
e"ents= eg= ;hene"er a meter read ;ith a P.roCen sealQ remarC is
recorded in the data.ase= the s#stem might trigger the creation o& a &ield
acti"it# to in"estigate the meter
Hes CRM and
.illing
11/ S#stem should support the tracCing= re"ie;ing= and correction o& meter
read errors
Hes CRM and
.illing
110 S#stem should ena.le the a.ilit# to add non-c#clical meter reads= such as
;hen a customer starts or stops ser"ice
Hes CRM and
.illing
114 S#stem should support meter read estimation ;hen an actual meter read is
not a"aila.le
Hes CRM and
.illing
112 S#stem should support .oth trend-.ased and historical estimation Hes CRM and
.illing
111( S#stem should support the de&inition o& and comparison against high/lo;
limits that are .ased on estimated usage &or the account
Hes CRM and
.illing
1111 S#stem should store a complete online histor# o& all meter reads= including
those uploaded &rom handheld de"ices= no reads= R manuall# entered
reads
Hes CRM and
.illing
12.0 F,e-d O*er+(,on) E F,e-d Wor8
Annex B: Appendix 3B- Compliance Sheet
Page 44 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
1$1 S#stem should pro"ide handling &or all customer &ield re,uests= including
meter installs R remo"als= turning ser"ice on or o&&= and ser"ice
in"estigations
Hes CRM and
.illing
1$$ 3hen a customer calls to start ser"ice at a premise= the s#stem should
re"ie; the current status o& ser"ice= R ma# create one or more &ield
acti"ities as applica.le to start ser"ice
Hes CRM and
.illing
1$3 S#stem should allo; a single &ield acti"it# to .e linCed to se"eral pending
ser"ice agreements
Hes CRM and
.illing
1$) S#stem should pro"ide a dispatch ,uer# that presents pending *ield
Acti"ities that need to .e dispatched= ;hich can .e grouped and gi"en to
;orC teams
Hes CRM and
.illing
1$1 S#stem should &eature an automated &ield order dispatch process that
selects pending &ield acti"ities that:
Hes CRM and
.illing
1$11 are not #et connected to a *ield !rder Hes CRM and
.illing
1$1$ ha"e .een assigned a dispatch group Hes CRM and
.illing
1$13 are linCed to an *ield Acti"it# t#pe that permits automated dispatching Hes CRM and
.illing
1$1) ha"e a schedule date earlier than toda#?s date plus the speci&ied 'ispatch
Ahead 'a#s
Hes CRM and
.illing
1$/ *ield ;orC completion acti"ities should trigger an# o& the &ollo;ing
s#stem updates:
Hes CRM and
.illing
1$/1 Meter %nstallation= ne; meter R the start reading are recorded Hes CRM and
.illing
1$/$ Meter Remo"al - the remo"al and the related end reading are recorded Hes CRM and
.illing
1$/3 Record Meter Reads Hes CRM and
.illing
1$/) Ser"ice Point Connection Status update Hes CRM and
.illing
1$/1 'e"ice At Ser"ice Point Status - indicates i& the meter is on or o&& 9or= &or
lamps= i& the e#e is in or out:
Hes CRM and
.illing
1$0 S#stem should support appointment &unctionalit# 9eg dispatch groups
;ould recei"e e&&ecti"e-dated ;orC schedules= ;hich de&ine their ;orCda#
;ith time slots R the num.er o& resources a"aila.le &or each time slot:
+he s#stem should .e a.le to o"erride a dispatch group?s normal ;orC
schedule &or e"ents liCe holida#s
Hes CRM and
.illing
1$4 %ntegration ;ith a 3orC&orce Management s#stem should ena.le additional
appointment &unctionalit# in the core s#stem 9eg= ;hether appointments are
re,uired at dispatch time 9!ptional not allo;ed &or &ield acti"ities o& that
t#pe:
Hes CRM and
.illing
1&.0 F,e-d O*er+(,on) E Wor8 For3e M+n+.e2en(
131 S#stem should pro"ide standard integration ;ith a AR management
s#stem
Hes CRM and
.illing
and AR
13$ Should permit the user to "ie; the a"aila.le time slots= choose &rom them=
and= in a real-time transaction= .oth reser"e the time slot and update the
&ield acti"it#
Hes CRM and
.illing
and AR
133 All acti"ities should taCe place ;ithout the need to Bump .et;een the t;o
s#stems
Hes CRM and
.illing
and AR
13) Should send status "alues to the Customer Relationship Management
s#stem so that users can in&orm customers a.out &ield "isit status= eg=
Pthe ;orCer is on the ;a#Q
Hes CRM and
.illing
and AR
Annex B: Appendix 3B- Compliance Sheet
Page 45 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
131 S#stem should support a &ield acti"it# histor# log to capture the changes to
the &ield acti"it# that are triggered .# messages coming &rom the &ield
operations stamped ;ith the date/time and action that ;as per&ormed
Hes CRM and
.illing
and AR
1>.0 Ener.1 D+(+ M+n+.e2en(
1)1 S#stem should calculate and manage all t#pes o& time-series data=
including ra; consumption= aggregated load= standard load pro&iles=
prices= and other &actors
Hes CRM and
.illing
and E'M
1)$ S#stem should include man# &eatures to process this data= including
"alidation= editing R estimation 9-EE:= deri"ation= aggregation= time-o&-
use mapping= and complex .illing
Hes CRM and
.illing
and E'M
15.0 Ener.1 D+(+ M+n+.e2en( E Me(er D+(+ M+n+.e2en(
111 S#stem should support man# &orms o& inter"al data= in an# inter"al si6e=
including:
Hes
1111 Ra; and aggregated data Hes CRM and
.illing
and E'M
111$ Consumption "alues Hes CRM and
.illing
and E'M
1113 Standard load pro&iles Hes CRM and
.illing
and E'M
111) +ime-o&-use maps Hes CRM and
.illing
and E'M
1111 Prices Hes CRM and
.illing
and E'M
111/ Contractual terms Hes CRM and
.illing
and E'M
11$ S#stem should allo; loading o& ne; or corrected data ;ithout corrupting
existing data= including a histor# o& ;hat has .een loaded in support o&
retroacti"e adBustments and calculations
Hes CRM and
.illing
and E'M
113 S#stem should permit calculations and manipulations o& this inter"al data
in order to per&orm man# di&&erent &unctions
Hes CRM and
.illing
and E'M
11) S#stem should permit inter"al data processes to .e per&ormed as data
.ecomes a"aila.le
Hes CRM and
.illing
and E'M
111 S#stem should support multiple time 6ones and da#light-sa"ing shi&ts Hes CRM and
.illing
and E'M
1C.0 Ener.1 D+(+ M+n+.e2en( E Co2*-e@ B,--,n.
1/1 S#stem should include a module &or complex .illing that taCes o"er ;hen
ra; inter"al data has .een processed
Hes CRM and
.illing
and E'M
1/$ S#stem should support aggregation o& inter"al data 9the accumulation o&
data &or multiple sources into a single stream= such as ;hen a single
Ser"ice Agreement exists &or multiple ser"ice points or meters:
Hes CRM and
.illing
and E'M
1/3 S#stem should support time-o&-use mapping .# pro"iding tools that help
users upload data= de&ine standard reusa.le templates= classi&# and price
usage periods= etc
Hes CRM and
.illing
and E'M
1/) S#stem should store and process .oth inter"al-.ased and time-o&-use-
.ased prices
Hes CRM and
.illing
and E'M
Annex B: Appendix 3B- Compliance Sheet
Page 46 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
1/1 S#stem should include &ormulae in the .ase s#stem that supports= at a
minimum= the &ollo;ing:
Hes CRM and
.illing
and E'M
1/11 Pro&ile data con"ersion &or aggregation o& peaC demand 9sum o& cur"es or
the maximum peaC in each period:
Hes CRM and
.illing
and E'M
1/1$ Pro&ile data con"ersions &or unit o& measure and time inter"alsW&or
instance= &rom <3h/11-minute inter"al "alues to <3h/3(-minute inter"al
"alues
Hes CRM and
.illing
and E'M
1/13 A rate component calculation capa.ilit# to picC out a PpeaC cur"e "alueQ Hes CRM and
.illing
and E'M
1// Complex .illing s#stems should= at a minimum= .e a.le to support the
&ollo;ing:
Hes CRM and
.illing
and E'M
1//1 Straight time-o&-use pricing= ;here time-o&-use data is deri"ed &rom time-
series usage
Hes CRM and
.illing
and E'M
1//$ Pure real-time= inter"al pricing= ;here spot marCet prices are applied
inter"al .# inter"al to the customer?s time-series usage
Hes CRM and
.illing
and E'M
1//3 Com.ination products= ;here &ixed prices are o&&ered &or pre-de&ined
loads 9or &or usage ;ithin a .and o& loads:= and the excess or under-used
energ# is sold or .ought on a spot marCet contract
Hes CRM and
.illing
and E'M
1//) All o& these t#pes o& products should support integration ;ith special
contract options= such as price- or demand-response load-management
triggers
Hes CRM and
.illing
and E'M
1/0 S#stem should calculate and manage all t#pes o& time-series data=
including ra; consumption= aggregated load= standard load pro&iles=
prices= and other &actors
Hes CRM and
.illing
and E'M
1/4 S#stem should support sophisticated contract options &or the management
o& curtailment and interruption periods
Hes CRM and
.illing
and E'M
1.>.2 F,n+n3e +nd A33o/n(,n.
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
1.0 Or.+n,B+(,on S(r/3(/re
11 Allo;s multi-compan# en"ironment in a single instance
Hes SAP ERP
*inancials
1$
Allo;s de&inition o& legal entit#= its di"isions= .ranches= plants=
distri.ution centers etc Allo;s de&inition o& pro&it centers ;ithin
organi6ation
Hes SAP ERP
*inancials
2.0 Gener+- ;+3ro)) +-- 2od/-e) ,n 5,n+n3,+-)<
$1 'e&inition o& countr# = regions= su.-regions to meet legal re,uirements
Hes SAP ERP
*inancials
$$ *lexi.ilit# to de&ine &iscal #ear including start month and end month
Hes SAP ERP
*inancials
$3 A.ilit# to de&ine 1$ periods PmonthsQ ;ithin a &iscal #ear
Hes SAP ERP
*inancials
$) A.ilit# to re"ise no o& periods in a &iscal #ear during #ear
Hes SAP ERP
*inancials
$1
Pro"ision &or separate logical periods &or the purpose o& annual closing
acti"ities
Hes SAP ERP
*inancials
Annex B: Appendix 3B- Compliance Sheet
Page 47 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
$/
Multiple &iscal #ear closings are allo;ed Multiple sets o& same .ooCs o&
accounts is permitted
Hes SAP ERP
*inancials
$0 Allo;s closing o& &iscal periods to restrict transactions posting
Hes SAP ERP
*inancials
$4
Allo;s to Ceep multiple periods open across &inancial #ears or ;ithin
&inancial #ear
Hes SAP ERP
*inancials
$2 A.ilit# to re-open closed period= su.Bect to "alid authori6ation
Hes SAP ERP
*inancials
$1(
A.ilit# to de&ine exchange rates ;ith multiple currencies "is-X-"is .ase
currenc#
Hes SAP ERP
*inancials
$11
A.ilit# to process transactions entered in &oreign currenc# .ased on exchange
rates de&inition in a online mode
Hes SAP ERP
*inancials
$1$
+racCing o& all &oreign currenc# transactions in .oth transaction currenc#
as ;ell as .ase currenc#
Hes SAP ERP
*inancials
$13
A.ilit# to calculate exchange &luctuation gain or loss automaticall# on
closing o& open transaction as ;ell as simultaneous posting o& such gain /
loss .ased on pre-determined criteria ;ithout an# &urther user inter"ention
Hes SAP ERP
*inancials
$1)
A.ilit# to calculate "alue o& open items in &oreign currenc# as o& end o& a
&iscal #ear and end o& period ;ithin &iscal #ear
Hes SAP ERP
*inancials
$11
*lexi.ilit# to choose rules &or posting o& such re"alued items at the end o&
&iscal #ear and end o& period &or each t#pe o& account such as recei"a.le=
pa#a.le= assets
Hes SAP ERP
*inancials
$1/
*lexi.ilit# options &or posting o& these di&&erences meet criteria de&ined .#
%*RS
Hes SAP ERP
*inancials
$10
A.ilit# to dra; complete set o& .ooCs o& accounts such as pro&it R loss
account= .alance sheet &or the legal entit#= each o& the .usiness unit .ranch=
plant etc
Hes SAP ERP
*inancials
$14 A"aila.ilit# o& "arious document t#pes &or di&&erent &inancial transactions
Hes SAP ERP
*inancials
$12 A"aila.ilit# o& s#stem generated num.ering &or the documents
Hes SAP ERP
*inancials
$$( A"aila.ilit# o& an option o& manual num.ering &or certain documents
Hes SAP ERP
*inancials
$$1 Eum.ering se,uence &or all documents is reset per &iscal #ear
Hes SAP ERP
*inancials
$$$
!ption o& setting num.ering se,uence .ased on location= .ranch etc &or the
same document t#pe
Hes SAP ERP
*inancials
$$3 Supports legal re,uirements &or 8AE
Hes SAP ERP
*inancials
$$4 Supports capturing o& "arious tax codes
Hes SAP ERP
*inancials
$31
*lexi.ilit# to control posting to speci&ic ledger accounts ;ith speci&ic
documents
Hes SAP ERP
*inancials
$3$ *lexi.ilit# to de&ine date &ormats= num.er &ormats per user
Hes SAP ERP
*inancials
&.0 A/d,( (r+,-
31
*or re-opening o& &iscal #ear periods
Hes SAP ERP
*inancials
3$
+racCing o& user= date and time &or each transaction
Hes SAP ERP
*inancials
33
+racCing o& changes made to an# document
Hes SAP ERP
*inancials
3)
+racCing o& creation and changes to an# master data in the s#stem
Hes SAP ERP
*inancials
Annex B: Appendix 3B- Compliance Sheet
Page 48 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
31
+racCing o& creation and changes to an# set up data in the s#stem= eg
codes= etc
Hes SAP ERP
*inancials
3/
+racCing o& changes to authori6ation pro&ile / appro"al pro&ile
Hes SAP ERP
*inancials
>.0 Gener+- ed.er
)1
A.ilit# to de&ine chart o& account &or the compan#
Hes SAP ERP
*inancials
)$
Eo restriction o& the arrangement or the num.er o& accounts Hes SAP ERP
*inancials
)3
Allo;s grouping o& general ledger account &or the purpose o& account
management
Hes SAP ERP
*inancials
))
Allo;s creating general ledger accounts in online mode Hes SAP ERP
*inancials
)1
Allo;s creating general ledger accounts in .atch mode using external
inter&ace
Hes SAP ERP
*inancials
)/
%& re,uired= allo;s creating master records during transaction entr# Hes SAP ERP
*inancials
)0
Can .locC / delete general ledger accounts i& postings are to .e .locCed Hes SAP ERP
*inancials
)4
Possi.le to map general ledger account codes to speci&ic .usiness
transactions in other modules
Hes SAP ERP
*inancials
)2
A.ilit# to post transactions &rom other modules in online mode .ased on
such pre-de&ined criteria
Hes SAP ERP
*inancials
)1(
Allo;s creation R posting o& Bournal entries online or in .atches Hes SAP ERP
*inancials
)11
Allo;s de&inition o& recurring transactions and periodicit# o& recurrence Hes SAP ERP
*inancials
)1$
Creates these automatic transactions .ased on prede&ined criteria Hes SAP ERP
*inancials
)13
Allo;s to create re"ersi.le Bournal "ouchers ;ith date de&inition &or
re"ersal
Hes SAP ERP
*inancials
)1)
Automatic re"ersal o& "ouchers .ased on pre-de&ined criteria Hes SAP ERP
*inancials
)11
Allo;s de&inition o& certain 7@ accounts in a ;a# that indi"idual
transactions can .e tracCed .ased on its OopenO status eg Securit#
deposits= clearing accounts etc
Hes SAP ERP
*inancials
)1/
Allo;s manual clearing o& such accounts .# matching transactions Hes SAP ERP
*inancials
)10
!ption to capture due dates &or such securit# deposits and ,uer# / report to
highlight deposits / ad"ances ;hich are due &or repa#ment
Hes SAP ERP
*inancials
)14
*lexi.ilit# to de&ine rules &or automatic clearing o& such accounts and
clearing o& open items .ased on such criteria
Hes SAP ERP
*inancials
)12
Allo;s cash accounting ;ith multiple cash points &or a single or multiple
cash 7@ accounts
Hes SAP ERP
*inancials
)$(
A.ilit# to de&ine .anCs= .anC accounts ;ithin s#stem Hes SAP ERP
*inancials
)$1
Allo;s upload o& .anC statements into the s#stem Hes SAP ERP
*inancials
)$$
Allo;s manual entr# o& .anC statements into the s#stem Hes SAP ERP
*inancials
)$3
Allo;s to de&ine criteria &or .anC reconciliation R carries out .anC
reconciliation .ased on pre-determined criteria
Hes SAP ERP
*inancials
)$)
Allo;s entr# o& incoming Che,ues &or current as ;ell as &uture period and
segregation .ased on dates possi.le
Hes SAP ERP
*inancials
)$1 Allo;s to "ie; R print Che,ue deposit statement &or a da# Hes SAP ERP
Annex B: Appendix 3B- Compliance Sheet
Page 49 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
*inancials
)$/
Allo;s to de&ine OCash Management S#stemsO ;hich are o&&ered .# "arious
.anCs in the countr#
Hes SAP ERP
*inancials
)$0
Captures "alue date &or Che,ue deposits and pa#ments Hes SAP ERP
*inancials
)$4
Ena.les calculation o& interest .ased on "alue dates captured in the s#stem Hes SAP ERP
*inancials
)$2
*lexi.ilit# to ;rite certain "alidation rules to support .usiness rules ;hich
are not supported directl# .# standard product &eatures
Hes SAP ERP
*inancials
)3(
Built in maCer - checCer concept &or appro"al o& documents .# super"isor#
authorit#
Hes SAP ERP
*inancials
)31
Supports process o& trans&er o& all re"enue statement account .alances to
retained earnings on closure o& &iscal #ear
Hes SAP ERP
*inancials
)3$
A.ilit# to trans&er .alances o& pro&it R loss account to retained earnings
account multiple times during a &iscal #ear closing process
Hes SAP ERP
*inancials
5.0
G E A/er1 / Re*or(,n. re9/,re2en()
11
Allo;s listing o& all transaction &or a particular document t#pe in .ooCs o&
accounts
Hes SAP ERP
*inancials
1$
A.ilit# to ,uer# all accounts and transactions on-line &or current R pre"ious
periods including pre"ious &iscal #ears
Hes SAP ERP
*inancials
13
*lexi.ilit# in de&inition o& transaction &ields that are displa#ed in such
,uer# / report .ased on re,uirements ;ithout an# programming e&&orts
Hes SAP ERP
*inancials
1)
A.ilit# to drill do;n &rom .alance to indi"idual transactions &or an#
account
Hes SAP ERP
*inancials
11
Allo;s classi&ication o& expenses on the .asis o& pre-de&ined parameters
eg +elephone num.er= -ehicle num.er etc
Hes SAP ERP
*inancials
1/
7enerates error report in case o& reBections or an# errors at the time o& data
trans&er using .atch mode
Hes SAP ERP
*inancials
10
Allo;s to de&ine multiple &ormats o& annual accounts 9ie Balance sheet
and pro&it R loss account: at the same time
Hes SAP ERP
*inancials
14
A.ilit# to taCe these annual accounts at legal entit# le"el= di"ision etc Hes SAP ERP
*inancials
12
Allo;s to taCe comparati"e .alance sheet= pro&it R loss account= trial
.alance ;here a corresponding period ;hich can .e selected .# user
Hes SAP ERP
*inancials
11(
Allo;s to de&ine schedules to support annual accounts Hes SAP ERP
*inancials
111
Report on all &oreign currenc# transactions entered during a period Hes SAP ERP
*inancials
11$
Allo;s to extract trial .alance &or entire compan#= di"ision= .ranch=
location etc
Hes SAP ERP
*inancials
113
Allo;s to extract actual cash &lo; o& the compan# Hes SAP ERP
*inancials
11)
A.ilit# to generate &inancial reports on .oth cash and accrual .asis .ased
on speci&ic reporting re,uirements
Hes SAP ERP
*inancials
C.0 Co)(,n.
/1
Adherence to costing record rules &or the purpose o& cost audit
re,uirements
Hes SAP ERP
*inancials
/$
*lexi.ilit# to per&orm costing &or a legal entit# or across legal entities
Hes SAP ERP
*inancials
/3
*lexi.ilit# to de&ine &iscal #ear including start month and end month
Hes SAP ERP
*inancials
/) *lexi.ilit# to de&ine periods ;ithin a &iscal #ear Hes SAP ERP
Annex B: Appendix 3B- Compliance Sheet
Page 50 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
*inancials
/1
Allo;s closing o& &iscal periods to restrict transactions posting
Hes SAP ERP
*inancials
//
A.ilit# to de&ine cost centers .ased on internal reporting re,uirements Hes SAP ERP
*inancials
/0
Allo;s grouping o& cost centre in a tree structure at least upto 1 le"els Hes SAP ERP
*inancials
/4
Allo;s trans&er o& cost &rom one cost centre to another cost centre Hes SAP ERP
*inancials
/41
!n ad-hoc .asis - manual transactions online
Hes SAP ERP
*inancials
/4$
!n prede&ined criteria including a speci&ic amount= percentage or &ormula
Hes SAP ERP
*inancials
/43
%n case o& &ormula= &lexi.ilit# to change &ormula ;ith an e&&ecti"e date
Hes SAP ERP
*inancials
/2
*lexi.ilit# to trans&er costs pertaining to speci&ic expense head onl#
Hes SAP ERP
*inancials
/1(
*lexi.ilit# to retain origin in&ormation o& cost e"en a&ter trans&er o& costs
Hes SAP ERP
*inancials
/11
A"aila.ilit# o& sender and recei"er cost centre in&ormation at all the time
Hes SAP ERP
*inancials
/1$
*lexi.ilit# to de&ine departments= di"isions= .ranches o& the compan# as
pro&it centers
Hes SAP ERP
*inancials
/13
Allo;s grouping o& pro&it centers in a tree structure at least up to 1 le"els Hes SAP ERP
*inancials
/1)
Allo;s transactions to &lo; &rom cost centers= general ledger accounts to
pro&it centers
Hes SAP ERP
*inancials
/11
Allo;s assets and lia.ilities to .e allocated to indi"idual pro&it centers
Hes SAP ERP
*inancials
/1/
A.ilit# to extract pro&it R loss account and .alance sheet &or each pro&it
centre
Hes SAP ERP
*inancials
/10
Allo;s trans&er price mechanism across pro&it centers &or stocC trans&er
across pro&it centers
Hes SAP ERP
*inancials
/14
A.ilit# to deri"e unreali6ed pro&it in stocCs at the end o& period o& &iscal
#ear
Hes SAP ERP
*inancials
/12
A.ilit# to arri"e at standard product cost .ased on materials= la.or and
o"erheads consumption
Hes SAP ERP
*inancials
/$(
A.ilit# to calculate standard cost o& products .ased on the a.o"e
Hes SAP ERP
*inancials
/$1
A.ilit# to calculate actual cost o& products .ased on allocation o& expenses
during a period
Hes SAP ERP
*inancials
/$$
A.ilit# to calculate actual cost o& product .ased on production data
Hes SAP ERP
*inancials
/$3
-ariance anal#sis .et;een standard / .udgeted cost and actual cost
Hes SAP ERP
*inancials
/$)
A.ilit# to produce cost reports at production sites and operational unit
le"els
Hes SAP ERP
*inancials
/$1
A.ilit# to report transmission / distri.ution losses
Hes SAP %S-8
E'M
D.0 B/d.e(,n.
01
*lexi.ilit# to de&ine and change .udgets &or accounts and cost centre le"el Hes SAP ERP
*inancials
/BPC
0$
Allo;s to create "arious "ersions during .udgeting process ;ith one
"ersion identi&ied as &irm .udget
Hes SAP ERP
*inancials
/BPC
Annex B: Appendix 3B- Compliance Sheet
Page 51 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
03
*lexi.ilit# in allocation o& annual .udget o"er accounting periods in a
&iscal #ear
Hes SAP ERP
*inancials
/BPC
031
Either in e,ual installments Hes SAP ERP
*inancials
/BPC
03$
An# other &ormula / criteria Hes SAP ERP
*inancials
/BPC
0)
*lexi.ilit# o& creating .udgets Hes SAP ERP
*inancials
/BPC
0)1
3ithout an# re&erence to pre"ious #earOs .udgets / actual Hes SAP ERP
*inancials
/BPC
0)$
As a percentage "ariation &rom pre"ious #earOs / current #earOs .udgets or
actual data
Hes SAP ERP
*inancials
/BPC
01
Allo;s tracCing o& .udget on a real time .asis "is-X-"is actual transactions
and commitments and highlight
Hes SAP ERP
*inancials
/BPC
011
!n actual &igures exceeding .udget &igures Hes SAP ERP
*inancials
/BPC
01$
!n actual &igures reaching a predetermined percentage o& .udget &igures Hes SAP ERP
*inancials
/BPC
0/
*lexi.ilit# to de&ine this tracCing &or each indi"idual period or &or entire
&iscal #ear or com.ination o& .oth
Hes SAP ERP
*inancials
/BPC
00
A.ilit# to consolidate .udgets o& "arious departments= regions= .ranches
into one corporate .udget &or the compan#
Hes SAP ERP
*inancials
/BPC
04
Pro"ides .udget "is-X-"is actual comparison on a on-line .asis as ;ell as
periodic inter"als
Hes SAP ERP
*inancials
/BPC
02
*lexi.ilit# to change .udget &igures during a &iscal #ear / period Hes SAP ERP
*inancials
/BPC
F.0 A33o/n( P+1+6-e E Gener+-
41
Allo;s creation o& "endors in the s#stem and "endor codes can .e
Eumeric and/or Alphanumeric
Hes SAP ERP
*inancials
4$ -endor num.ers can .e generated .# the s#stem
Hes SAP ERP
*inancials
43 %& re,uired "endor codes can .e manuall# assigned
Hes SAP ERP
*inancials
4) Captures critical "endor in&ormation such as
Hes SAP ERP
*inancials
4)1
Eame and address= Ce# person at "endor compan# Hes SAP ERP
*inancials
4)$
Captures state ;here "endor is located Hes SAP ERP
*inancials
4)3
Captures email %' o& "endor Hes SAP ERP
*inancials
4))
BanC account details Hes SAP ERP
*inancials
4)1
Pa#ment terms= discount terms= pa#ment methods Hes SAP ERP
*inancials
4)/
@egal status o& the "endor such as corporate= non-corporate etc Hes SAP ERP
*inancials
41 A.ilit# to hint that "endor code ma# .e existing in the s#stem Hes SAP ERP
Annex B: Appendix 3B- Compliance Sheet
Page 52 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
*inancials
4/
Allo;s creation o& "endor codes in an online mode as ;ell as in a .atch
mode
Hes SAP ERP
*inancials
40 %& re,uired "endor codes can .e created during transaction entr#
Hes SAP ERP
*inancials
44 Allo;s to de&ine pa#ment terms in &ollo;ing scenarios:
SAP ERP
*inancials
441
Standard pa#ment term o& pa#ment due a&ter speci&ic no o& da#s Hes SAP ERP
*inancials
44$
Pa#ment term ;ith discount sla.s &or pa#ment .e&ore speci&ic no o& da#s
Should allo; up to 1 sla.s in such cases
Hes SAP ERP
*inancials
443
Pa#ment term ;here discount is o&&ered as interest component &or earl#
pa#ments
Hes SAP ERP
*inancials
44)
Pa#ment term ;hich allo;s retention mone# Hes SAP ERP
*inancials
42
Allo;s .locCing o& speci&ic "endors so that transactions ;ith such "endors
cannot .e entered
Hes SAP ERP
*inancials
41(
Allo;s linCing o& man# "endors to capture group exposure / transaction
"olume
Hes SAP ERP
*inancials
411
Allo;s linCing o& "endors ;ith customers in case a compan# is .oth
"endor as ;ell as customer
Hes SAP ERP
*inancials
41$
Allo;s creation o& "endorsO &inancial data independent o& purchase and
materials related data
Hes SAP ERP
*inancials
413
A uni,ue "endor code can .e used &or all the di"isions= .ranches= multiple
legal entities .ased on the re,uirement
Hes SAP ERP
*inancials
41)
Allo;s to de&ine "arious +'S rates= ;orCs contract tax rates in the s#stem R
attach rele"ant rates to "endors .ased on applica.ilit#
Hes SAP ERP
*inancials
411
Allo;s clearing o& "endor transactions .# matching t;o or more open
de.it and credit items
Hes SAP ERP
*inancials
41/ Allo; to segregate and tracC "endor transactions into:
41/1
Eormal in"oices and pa#ments Hes SAP ERP
*inancials
41/$
Ad"ance pa#ments to "endors Hes SAP ERP
*inancials
41/3
7uarantees Hes SAP ERP
*inancials
41/)
Securit# deposits ;ith "endors Hes SAP ERP
*inancials
41/1
BanC guarantee= letter o& credit to "endors Hes SAP ERP
*inancials
9.0 AP E A33o/n(,n. +nd "endor 3red,( *ro3e))e)
21 Allo;s in"oice processing
211
3ith respect to a 7oods Receipt Eote 97RE: in the s#stem Hes SAP ERP
*inancials
/Procurem
ent
21$
3ith respect to capital Bo. note in case o& capital asset receipt Hes SAP ERP
*inancials
/Procurem
ent
213
3ith respect to ser"ice entr# note in case o& a ser"ice "endor Hes SAP ERP
*inancials
/Procurem
ent
21)
Expense "oucher ;here "endor is credited ;ithout P!/7RE in the s#stem Hes SAP ERP
*inancials
/Procurem
ent
Annex B: Appendix 3B- Compliance Sheet
Page 53 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
2$
Supports t#pical 3 ;a# match 9P!= 7RE= -endor in"oice: .ill passing
process
Hes SAP ERP
*inancials
/Procurem
ent
23
Considers ,uantitati"e details &rom 7RE and price details &rom P! during
the 3;a# match
Hes SAP ERP
*inancials
/Procurem
ent
2)
Bills are processed .ased on P!= 7RE e"en i& in"oice does not match ;ith
"alue arri"ed at using these t;o documents
Hes SAP ERP
*inancials
/Procurem
ent
21
-endor .ills should .e .ooCed at gross and an# reBection= disallo;ance
should .e captured during .ill processing as a separate entr# ReBection=
deductions should .e printa.le during printing o& pa#ment ad"ice
Hes SAP ERP
*inancials
/Procurem
ent
2/
A.ilit# to prompt / automaticall# deduct all deducti.le charges at the time
o& "endor .ill processing
Hes SAP ERP
*inancials
/Procurem
ent
20
A.ilit# to automaticall# account &or all these deductions .ased on pre-
determined criteria
Hes SAP ERP
*inancials
/Procurem
ent
24 'e&aults master data in&ormation o& "endor during in"oice processing
Hes SAP ERP
*inancials
/Procurem
ent
22
Allo;s to de&ine parameters to determine ;hether de&ault master data
in&ormation can .e changed during processing and changes are allo;ed
onl# .ased on this +he same can .e done onl# .ased on authori6ation
Hes SAP ERP
*inancials
/Procurem
ent
21( Allo;s entr# o& transaction in "endor account %n online and/or .atch mode
Hes SAP ERP
*inancials
/Procurem
ent
211
Allo;s to e"aluate amount o& pending 7RE &or in"oice processing to
arri"e at pro"ision &igures
Hes SAP ERP
*inancials
/Procurem
ent
21$
+riggers commitment and updates .udget on issue o& purchase orders &or
goods / ser"ices
Hes SAP ERP
*inancials
/Procurem
ent
213
A.ilit# to tracC duplicate in"oice .ased on "endor code and in"oice
num.er
Hes SAP ERP
*inancials
/Procurem
ent
21) %n case o& la.or .ills a.ilit# to checC indi"idual time sheets
Hes SAP ERP
*inancials
/Procurem
ent
211
A.ilit# to post de.it notes and credit notes as ;ell as print these &or
sending across to "endors
Hes SAP ERP
*inancials
/Procurem
ent
21/
A.ilit# to calculate o"erdue interest &or "endors .ased on indi"idual
transaction due dates in &ollo;ing scenario:
Hes SAP ERP
*inancials
/Procurem
ent
Annex B: Appendix 3B- Compliance Sheet
Page 54 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
21/1
%nterest is accrued at each period end &or all outstanding line items .e#ond
due date
Hes SAP ERP
*inancials
/Procurem
ent
21/$
%nterest is accrued onl# at the time o& pa#ment o& principal +ill then
although interest is calculated = ho;e"er not accounted &or
Hes SAP ERP
*inancials
/Procurem
ent
10.0 AP E P+12en( *ro3e)),n.
1(1 A.ilit# to process "endor pa#ment in
SAP ERP
*inancials
1(11
Manual pa#ment mode Hes SAP ERP
*inancials
1(1$
Automatic pa#ment processing .ased on prede&ined parameters Hes SAP ERP
*inancials
1($ Allo;s pa#ment &or &ollo;ing scenarios:
Hes SAP ERP
*inancials
1($1
Ad"ance pa#ment I ad-hoc Hes SAP ERP
*inancials
1($$
Ad"ance pa#ment onl# against purchase orders Hes SAP ERP
*inancials
1($3
Pa#ment against one or multiple in"oices - matching amount Hes SAP ERP
*inancials
1($)
Pa#ment against one or multiple in"oices - partial amount Hes SAP ERP
*inancials
1($1
Pa#ment against one or multiple in"oices I ad-hoc amount Hes SAP ERP
*inancials
1(3 A.ilit# to capture and report capital and re"enue ad"ances separatel#
Hes SAP ERP
*inancials
1()
A.ilit# to .locC certain "endor in"oices so that the# cannot .e paid unless
cleared .# appropriate authorit#
Hes SAP ERP
*inancials
1(1
A.ilit# to .locC certain "endors &or pa#ment so that no pa#ments can .e
made to such "endors unless appropriatel# appro"ed
Hes SAP ERP
*inancials
1(/
A.ilit# to pro"ide &unds re,uirement .ased on due date &or a user
determined period
Hes SAP ERP
*inancials
1(0
+he &unds re,uirement in&ormation also identi&ies currenc#= .ranches=
di"isions &or all the indi"idual transactions ;hich are captured .ased on
due dates
Hes SAP ERP
*inancials
1(4
Allo;s to processes one or more "endor in"oices= de.it notes= credit notes
and allo;s to maCe net pa#ment
Hes SAP ERP
*inancials
1(2 *or the purpose o& automatic pa#ment processing s#stem ena.les:
SAP ERP
*inancials
1(21
Allo;s to run pa#ment program &or &uture date Hes SAP ERP
*inancials
1(2$
Allo;s to process multiple pa#ment programs runs &or di&&erent dates= same
date - di&&erent criteria
Hes SAP ERP
*inancials
1(23
%denti&ication in"oices due .# a particular date Hes SAP ERP
*inancials
1(2)
Allo;s to select / deselect certain in"oices &or pa#ment processing Hes SAP ERP
*inancials
1(21
*or the purpose o& pa#ment processing= allo;s to pa# on one single da# Hes SAP ERP
*inancials
1(2/
*lexi.ilit# to process pa#ment o& all in"oices at one go= ho;e"er= strictl# on
due date .asis
Hes SAP ERP
*inancials
1(20
%denti&ies .anCs .ased on predetermined criteria and &unds a"aila.ilit# Hes SAP ERP
*inancials
Annex B: Appendix 3B- Compliance Sheet
Page 55 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
1(24
Based on the process= posts accounting entries in .anC accounts as ;ell as
"endor accounts
Hes SAP ERP
*inancials
1(22
Clears "endor items ;here"er clearing is possi.le Hes SAP ERP
*inancials
1(1(
'uring pa#ment 9automatic or manual: s#stem automaticall# calculates
discount i& an# and proposes net amount &or pa#ment processing
Hes SAP ERP
*inancials
1(11
A.ilit# to generate accounting entr# a&ter considering discount &igures R
posting o& entr# .ased on pre-determined account mapping
Hes SAP ERP
*inancials
1(1$
Allo;s maintenance o& Che,ue stationar# and tracCing o& Che,ue .ased
on a"aila.le stationar# and usage
Hes SAP ERP
*inancials
1(13 Allo;s printing o& Che,ues &or "arious .anCs
Hes SAP ERP
*inancials
1(1)
!ption o& sending pa#ment details to .anCs in a so&t cop# &ormat so that
pa#ment processing can .e carried out .# .anC
Hes SAP ERP
*inancials
1(11
!ption o& Che,ue printing .# .anCs on trans&er o& pa#ment instruction and
updating o& Che,ue nos .acC in the s#stem
Hes SAP ERP
*inancials
1(1/
Allo;s printing o& pa#ment ad"ice along ;ith Che,ue ;hich ma# .e sent
across to "endors along ;ith their pa#ment
Hes SAP ERP
*inancials
1(10
Ensures updating o& Che,ue register on printing o& Che,ue as ;ell as updates
the pa#ment "oucher ;ith details o& Che,ue no
Hes SAP ERP
*inancials
1(14
*lexi.ilit# to update Che,ue register in case Che,ue are issued manuall#=
Che,ue is destro#ed= damaged etc
Hes SAP ERP
*inancials
11.0 AP E Re*or()
111
Statement o& account &or the purpose o& sending it across to "endors &or
.alance and transaction con&irmation= ;ith an option to de&ine &ormat o&
con&irmation letter
Hes SAP ERP
*inancials
11$ 'ue date ;ise anal#sis o& "endor accounts
Hes SAP ERP
*inancials
113 Ageing anal#sis o& "endor line items
Hes SAP ERP
*inancials
11) -endor account trial .alance
Hes SAP ERP
*inancials
111 -endor account line item details
Hes SAP ERP
*inancials
11/ -endor account details segregated into:
Hes SAP ERP
*inancials
11/1 %n"oices and pa#ments
Hes SAP ERP
*inancials
11/$ Ad"ances paid to "endors
Hes SAP ERP
*inancials
11/3 @Cs and .anC guarantees
Hes SAP ERP
*inancials
110 -endor account .alances R transactions per "endor control account
Hes SAP ERP
*inancials
114 Allo;s regrouping o& "endor .alances .ased on de.it / credit .alances
Hes SAP ERP
*inancials
112
A.ilit# to "ie; / print all the a.o"e "endor account and line item reports
per .ranch= di"ision= location etc
Hes SAP ERP
*inancials
111(
Allo;s to capture separate ageing anal#sis &or di&&erent categories o&
"endors
Hes SAP ERP
*inancials
1111
A"aila.ilit# o& details o& pa#ments made .e&ore due data and
corresponding cash discount earned
Hes SAP ERP
*inancials
111$
Allo;s to extract details o& purchase orders= 7REs= in"oices= accounting
documents o& indi"idual "endors
Hes SAP ERP
*inancials
Annex B: Appendix 3B- Compliance Sheet
Page 56 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
1113
Allo;s to segregate imported and local purchases and expenditure in
&oreign currenc#
Hes SAP ERP
*inancials
111) Allo;s to extract details o& capital commitment made .# the compan#
Hes SAP ERP
*inancials
1111
A.ilit# to pro"ide details o& pa#ments segregated into on time pa#ment=
earl# pa#ment and dela#ed pa#ment
Hes SAP ERP
*inancials
111/
A.ilit# to report on total "olume o& .usiness generated= discounts earned
&rom "endors
Hes SAP ERP
*inancials
12.0 A33o/n() Re3e,0+6-e E Gener+-
1$1
Allo;s creation o& customers in the s#stem and customer codes can .e
Eumeric and/or Alphanumeric
Hes SAP ERP
*inancials
1$$ Customer num.ers can .e generated .# the s#stem
Hes SAP ERP
*inancials
1$3 %& re,uired customer codes can .e manuall# assigned
Hes SAP ERP
*inancials
1$) Captures critical customer in&ormation such as
Hes SAP ERP
*inancials
1$)1 Eame and address= Ce# person
Hes SAP ERP
*inancials
1$)$ BanC account details
Hes SAP ERP
*inancials
1$)3 Pa#ment terms= discount terms= pa#ment methods
Hes SAP ERP
*inancials
1$)) @egal status o& "endor such as corporate= non-corporate etc
Hes SAP ERP
*inancials
1$1
Allo;s de&ining multiple groups in ;hich indi"idual customers ma# .e
clu..ed such that di&&erent groups ma# exist &or di&&erent class o&
customers eg %ndustrial= domestic etc
Hes SAP ERP
*inancials
1$/ A.ilit# to hint that customer code ma# .e existing in the s#stem
Hes SAP ERP
*inancials
1$0
Allo;s creation o& customer codes in an online mode as ;ell as in a .atch
mode
Hes SAP ERP
*inancials
1$4 %& re,uired allo;s creation o& master data during transaction entr#
Hes SAP ERP
*inancials
1$2 Allo;s to de&ine speci&ic credit limits &or indi"idual customers
Hes SAP ERP
*inancials
1$1( Allo;s speci&ic credit limit &or each customer ;ithin a customer categor#
Hes SAP ERP
*inancials
1$11 Allo;s tracCing o& an# change to the credit limit set
Hes SAP ERP
*inancials
1$1$
A.ilit# to pro"ide speci&ic o"erriding authori6ation &or allo;ing
transactions o"er and a.o"e credit limit
Hes SAP ERP
*inancials
1$13
A.ilit# to pro"ide separate credit limits depending upon product to the
same customer
Hes SAP ERP
*inancials
1$1) A.ilit# to de&ine d#namic credit limits .ased on:
Hes SAP ERP
*inancials
1$1)1 Sale o& past OxO months ;here "alue o& OxO is &reel# de&ina.le
Hes SAP ERP
*inancials
1$1)$
*ormula to alter credit limits o& all customers as a T o& existing credit limit
eg F / - 1(T &or all customers in a categor#
Hes SAP ERP
*inancials
1$1)3
Percentage o& a total o& securit# deposit and ad"ances as reduced .#
outstanding .ills .e#ond due date
Hes SAP ERP
*inancials
1$11 Allo;s to de&ine pa#ment terms in &ollo;ing scenarios:
Hes SAP ERP
*inancials
1$111 A &ixed date as pa#ment date such as e"er# Monda#= e"er# 0
th
o& month
Hes SAP ERP
*inancials
1$11$ Standard pa#ment term o& pa#ment due a&ter speci&ic no o& da#s
Hes SAP ERP
*inancials
Annex B: Appendix 3B- Compliance Sheet
Page 57 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
1$113
Pa#ment term ;ith discount sla.s &or pa#ment .e&ore speci&ic no o& da#s
Should allo; upto 1 sla.s in such cases
Hes SAP ERP
*inancials
1$11)
Pa#ment term ;here discount is o&&ered as interest component &or earl#
pa#ments
Hes SAP ERP
*inancials
1$111 Pa#ment term ;hich allo;s retention mone#
Hes SAP ERP
*inancials
1$1/
Allo;s .locCing o& speci&ic "endors so that transactions ;ith such "endors
cannot .e entered
Hes SAP ERP
*inancials
1$10
Allo;s linCing o& man# customers to capture group exposure / transaction
"olume
Hes SAP ERP
*inancials
1$14
Allo;s linCing o& "endors ;ith customers in case a compan# is .oth
"endor as ;ell as customer
Hes SAP ERP
*inancials
1$12
A uni,ue customer code can .e used &or all the di"isions= .ranches=
multiple legal entities .ased on the re,uirement
Hes SAP ERP
*inancials
1$$(
Allo;s clearing o& customer transactions .# matching t;o or more open
de.it and credit items
Hes SAP ERP
*inancials
1$$(1 Allo; to segregate and tracC transactions into:
SAP ERP
*inancials
1$$($ Eormal in"oices and pa#ments
Hes SAP ERP
*inancials
1$$(3 Ad"ance pa#ments
Hes SAP ERP
*inancials
1$$() 7uarantees
Hes SAP ERP
*inancials
1$$(1 Securit# deposits &rom customers
Hes SAP ERP
*inancials
1$$(/ BanC guarantee= letter o& credit to customers
Hes SAP ERP
*inancials
1$$1 A.ilit# to calculate un.illed re"enue .ased on re"enue recognition polic#
Hes A report
;ill .e
de"eloped
&or the
same
1&.0 A33o/n() Re3e,0+6-e E In0o,3,n. +nd 3o--e3(,on)
131 Allo;s to create manual / s#stem in"oices &or customer charges
Hes SAP ERP
*inancials
13$
Allo;s to create in"oices in .atch mode so that in"oices can .e uploaded
into s#stem &rom external &ile / data.ase in case .illing is generated in a
di&&erent solution
Hes SAP ERP
*inancials
133 Automatic in"oice no generation .# the s#stem
Hes SAP ERP
*inancials
13) 7eneration o& in"oice no can .e an# o& the &ollo;ing:
SAP ERP
*inancials
13)1 8ni,ue across compan#
Hes SAP ERP
*inancials
13)$ 8ni,ue per .ranch= di"ision= location
Hes SAP ERP
*inancials
131
Allo;s posting o& de.it notes / credit notes in the s#stem .oth manuall#= or
in a .atch mode thru an external &ile / data.ase
Hes SAP ERP
*inancials
13/ Allo;s entr# o& pa#ments in an# o& the &ollo;ing ;a#s:
SAP ERP
*inancials
13/1 Manual cash / Che,ue receipt
Hes SAP ERP
*inancials
13/$ Batch upload &rom an external &ile / data.ase
Hes SAP ERP
*inancials
13/3 Electronic upload o& the 'ata through s#stem checCs liCe .ill Eo
Hes SAP ERP
*inancials
Annex B: Appendix 3B- Compliance Sheet
Page 58 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
130
Allo;s clearing o& open in"oices= other items on entr# o& pa#ment against
those items
Hes SAP ERP
*inancials
134 A.ilit# to clear multiple de.it= credit line items in a single transaction
Hes SAP ERP
*inancials
132
A.ilit# to segregate customer transactions and automatic accounting
parameters .ased on:
Hes SAP ERP
*inancials
1321 Pa#ment against in"oice - Partial pa#ment or complete pa#ment
Hes SAP ERP
*inancials
132$ Pa#ment &or other charges such as maintenance= repair
Hes SAP ERP
*inancials
1323 Eon-re"enue pa#ments such as securit# deposit &rom customers
Hes SAP ERP
*inancials
132) Capital receipt &rom customers such as connection charges
Hes SAP ERP
*inancials
1321 Excess pa#ments compared to outstanding in"oices
Hes SAP ERP
*inancials
131(
Possi.le to parC amounts in suspense accounts in case o& unaccounted
credit / de.it
Hes SAP ERP
*inancials
1311
Automaticall# Calculates and account &or Ocash discountsO .ased on pre-
determined parameters in case o& pa#ment .e&ore speci&ic time inter"al
Hes SAP ERP
*inancials
131$
Automaticall# calculates and account &or Odela#ed pa#ment chargesO in case
o& pa#ment is not made .# due date +he charges can .e computed in an#
o& the &ollo;ing manner:
Hes SAP ERP
*inancials
131$1
Charges are accrued at each period end &or all outstanding line items
.e#ond due date
Hes SAP ERP
*inancials
131$$
Charges are accrued onl# at the time o& pa#ment o& principal +ill then
although calculation is made= the same is not accounted &or
Hes SAP ERP
*inancials
1313
Allo;s re"ersal o& pa#ment transaction in case o& OreturnedO che,ues in an#
o& the a.o"e scenarios
Hes SAP ERP
*inancials
131)
%n case o& cleared transactions= the clearing is reset on re"ersal o& pa#ment
transaction
Hes SAP ERP
*inancials
1311
Ageing o& such in"oices is restated to original date &or the purpose o&
calculation o&:
Hes SAP ERP
*inancials
13111 Eo o& da#s o& outstanding .ill
Hes SAP ERP
*inancials
1311$ Calculation o& o"erdue interest / penalt#
Hes SAP ERP
*inancials
131/
A.ilit# to con&igure dunning / automated reminders to customers ;here
pa#ments are not made against in"oices
Hes SAP ERP
*inancials
131/1 At least 3 le"els o& dunning can .e con&igured
Hes SAP ERP
*inancials
131/$ Summar# as ;ell as details o& transactions outstanding can .e pro"ided
Hes SAP ERP
*inancials
131/3 'etails o& interest charges / penalties can .e pro"ided
Hes SAP ERP
*inancials
1310
A.ilit# to trans&er in&ormation related to collections to an external &ile /
data.ase ;here collections are identi&ied as:
Hes SAP ERP
*inancials
13101 Collections against in"oices
Hes SAP ERP
*inancials
1310$ Ad-hoc pa#ment .# customer
Hes SAP ERP
*inancials
13103 Ad"ance pa#ments .# customers
Hes SAP ERP
*inancials
1310) An# other pa#ments .# customers
Hes SAP ERP
*inancials
Annex B: Appendix 3B- Compliance Sheet
Page 59 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
1314
Possi.le to allo; processing o& .illing ;hile closing o& accounts and
&inancial #ear closing acti"ities
Hes SAP ERP
*inancials
1>.0 AR M Re*or()
1)1
Statement o& account &or the purpose o& o.taining con&irmations &rom
customers on .alance and transactions
Hes SAP ERP
*inancials
1)$ 'ue date ;ise anal#sis o& customer accounts
Hes SAP ERP
*inancials
1)3 Ageing anal#sis o& customer line items
Hes SAP ERP
*inancials
1)) BucCets &or ageing can .e &reel# de&ined .# user .ased on re,uirements
Hes SAP ERP
*inancials
1)1 Ageing can .e taCen on the .asis o& .oth= in"oice date R due date
Hes SAP ERP
*inancials
1)/ Customer account trial .alance
Hes SAP ERP
*inancials
1)0 Customer account line item details
Hes SAP ERP
*inancials
1)4 Customer account details segregated into:
SAP ERP
*inancials
%n"oices and pa#ments
Hes SAP ERP
*inancials
Ad"ances paid
Hes SAP ERP
*inancials
@Cs and .anC guarantees
Hes SAP ERP
*inancials
1)2 Customer account .alances and transactions per "endor control account
Hes SAP ERP
*inancials
1)1(
A.ilit# to "ie; / print all the a.o"e customer account and line item reports
per .ranch= di"ision= location etc
Hes SAP ERP
*inancials
1)11
A"aila.ilit# o& details o& pa#ments made .e&ore due data and
corresponding cash discount allo;ed to customers
Hes SAP ERP
*inancials
1)1$
A.ilit# to pro"ide details o& pa#ments segregated into ontime pa#ment=
earl# pa#ment and dela#ed pa#ment
Hes SAP ERP
*inancials
1)13
A.ilit# to report on total "olume o& .usiness generated= discounts allo;ed
to Customer
Hes SAP ERP
*inancials
15.0 A))e() E CWIP
111 Allo;s capitali6ation o& assets through C3%P route
Hes *inancials
and assets
accountin
g
11$ Allo;s de.iting direct purchases to C3%P
Hes *inancials
and assets
accountin
g
113 Allo;s de.iting o& materials issues to C3%P
Hes *inancials
and assets
accountin
g
11)
Allo;s capital receipts to .e credited to C3%P .e&ore capitali6ation o&
assets
Hes *inancials
and assets
accountin
g
111 Allo;s apportionment o& total cost o& C3%P o"er multiple assets .ased on:
Pre-determined criteria
Hes *inancials
and assets
accountin
g
Annex B: Appendix 3B- Compliance Sheet
Page 60 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
*ormula entr# at the time o& capitali6ation
Hes *inancials
and assets
accountin
g
'irect entr# o& amounts &rom C3%P to Asset
Hes *inancials
and assets
accountin
g
11/ Allo;s allocation o& indirect expenses to C3%P
Hes *inancials
and assets
accountin
g
110
Allo;s de&inition o& multiple parts o& one single asset Allo;s
classi&ication o& C3%P expenses o"er asset parts as ;ell
Hes *inancials
and assets
accountin
g
114
Cen-A+9Central -alue Added +ax: net o&& record is maintained and
re"ersed i& asset is disposed o&& in speci&ic time &rame
Hes *inancials
and assets
accountin
g
112 Allo;s adBustment in capitali6ation due to exchange &luctuation
Hes *inancials
and assets
accountin
g
111( Supports capital expenses .udgeting such as:
111(1 Asset le"el .udgeting is possi.le
Hes *inancials
and assets
accountin
g
111($ ProBect le"el .udgeting is possi.le
Hes *inancials
and assets
accountin
g
1111
Allo;s classi&ication o& assets into groups to &acilitate grouping o& similar
assets
Hes *inancials
and assets
accountin
g
111$ Allo;s creating assets ;ith all re,uisite in&ormation such as:
111$1 'escription o& asset
Hes *inancials
and assets
accountin
g
111$$ 'ate o& capitali6ation
Hes *inancials
and assets
accountin
g
111$3 -endor details
Hes *inancials
and assets
accountin
g
111$) 5uantit# o& assets
Hes *inancials
and assets
accountin
g
111$1 @ocation o& asset= cost centre
Hes *inancials
and assets
accountin
g
111$/ 'epreciation related details such as method= rate Hes *inancials
and assets
accountin
Annex B: Appendix 3B- Compliance Sheet
Page 61 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
g
111$0 Asset insurance details
Hes *inancials
and assets
accountin
g
1113
An# change in an# o& these details should .e carried out as per maCer-
checCer concept
Hes *inancials
and assets
accountin
g
111)
*lexi.ilit# to create e,uipment details out o& asset records to tracC and
control maintenance Bo.s on the assets
Hes *inancials
and assets
accountin
g
1111
Allo;s recapitali6ation o& assets &or &urther capital receipts such as
registration charges= connection charges etc
Hes *inancials
and assets
accountin
g
111/ A.ilit# to create proBects and de"elop proBect .udgets
Hes ProBect
S#stems
1110
A.ilit# to capture costs &or each proBect 9either capex or other;ise: and
linC to contracts= AR costs= o"erheads and material issues
Hes
ProBect
S#stems
1114 ProBect "ariance reports
Hes ProBect
%n&ormatio
n S#stems
1112
A.ilit# to manage proBect accounting liCe milestone de&inition= pa#ment
certi&icate and accounting against rele"ant contract
Hes ProBect
S#stems
;ith
Certi&icate
to .e
de"eloped
as per
*E3A?s
re,uireme
nt
11$(
A.ilit# to maintain separate account management &or retention ;ith
"endor ;ise details
Hes SAP ECC
/(
*inancial
Managem
ent
1C.0 A))e() E De*re3,+(,on
1/1 Allo;s de&ining di&&erent t#pes o& depreciation methods such as:
Hes *inancials
and assets
accountin
g
1/11 Straight line method 9S@M:
Hes *inancials
and assets
accountin
g
1/1$ 3ritten do;n "alue method 93'-:
Hes *inancials
and assets
accountin
g
1/$ Allo;s multi-shi&t depreciation
Hes *inancials
and assets
accountin
g
1/3
Allo;s ;orCing o& di&&erent depreciation &or same assets ;hich ma# .e
used &or di&&erent purposes
Hes *inancials
and assets
accountin
g
Annex B: Appendix 3B- Compliance Sheet
Page 62 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
1/31 *or the purpose o& .ooCs o& accounts
Hes *inancials
and assets
accountin
g
1/3$ *or the purpose o& costing / M%S purposes
Hes *inancials
and assets
accountin
g
1/) Allo;s to calculate depreciation on a pro-rata .asis
Hes *inancials
and assets
accountin
g
1/1
Allo;s de&ining a threshold "alue .elo; ;hich assets need not .e de&ined=
and a threshold limit .elo; ;hich assets should not .e depreciated
Hes *inancials
and assets
accountin
g
1// Allo;s automatic calculation o& depreciation .ased on pre-de&ined criteria
Hes *inancials
and assets
accountin
g
1/0
Allo;s calculation and posting o& depreciation at monthl# inter"als= ;ith
an option o& posting= posting ;ith re"ersal entr#
Hes *inancials
and assets
accountin
g
1/4 Allo;s .oth up;ard and do;n;ard re"aluation o& assets
Hes *inancials
and assets
accountin
g
1/2 Supports accounting o& re"aluation o& assets
*inancials
and assets
accountin
g
1/1(
Allo;s depreciation calculation on re"alued portion and charge o&
re"aluation depreciation on:
Hes *inancials
and assets
accountin
g
1/1(1 Re"aluation reser"e
Hes *inancials
and assets
accountin
g
1/1($ Capital reser"e
Hes *inancials
and assets
accountin
g
1/11
!ption o& calculation o& depreciation ;ith retrospecti"e e&&ect in case o&
change o& method or rate o& depreciation
Hes *inancials
and assets
accountin
g
1/1$
*or retrospecti"e change= calculation o& prior period items posted during
current &iscal #ear
Hes *inancials
and assets
accountin
g
1/13
Allo;s trans&er o& an asset to other locations= departments= di"isions or
.ranches
*inancials
and assets
accountin
g
1D.0 A))e() E S+-e
Hes
101 Supports sale o& asset and carries out pro&it R loss calculation
Hes *inancials
and assets
accountin
g
Annex B: Appendix 3B- Compliance Sheet
Page 63 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
10$
Posting o& capitali6ation= depreciation= sale o& asset is automatic .ased on
pre-determined characters
Hes *inancials
and assets
accountin
g
103
Supports automatic calculation o& pro&it or loss on sale o& assets .ased on
.ooC depreciation
*inancials
and assets
accountin
g
1F.0 A))e() E Re*or()
141
Assets register to pro"ide all the details a.out e"er# asset in the .ooCs o&
accounts Some o& the critical details include:
Hes *inancials
and assets
accountin
g
1411 Asset no ;ith part no and asset description
Hes *inancials
and assets
accountin
g
141$ 'ate o& capitali6ation= original cost= accumulated depreciation and 3'-
Hes *inancials
and assets
accountin
g
1413 Additions and deletions &rom assets o"er a period
Hes *inancials
and assets
accountin
g
141) Cost centre= location o& asset
Hes *inancials
and assets
accountin
g
1411 8nit o& measurement o& asset such as meters= &eet= Cgs etc
*inancials
and assets
accountin
g
14$ Reports on transactions during the #ear such as:
Hes *inancials
and assets
accountin
g
14$1 Purchase o& ne; assets
Hes *inancials
and assets
accountin
g
14$$ Sale o& assets
Hes *inancials
and assets
accountin
g
14$3 'etails o& sale= trans&er and ;ritten o&&
Hes *inancials
and assets
accountin
g
14$) @ocation details o& assets to .e used &or ph#sical "eri&ication
Hes *inancials
and assets
accountin
g
14$1 %ncome tax depreciation details
Hes *inancials
and assets
accountin
g
14$/ BooC depreciation
*inancials
and assets
accountin
g
Annex B: Appendix 3B- Compliance Sheet
Page 64 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
19.0 P+1ro-- A33o/n(,n. Hes
121 %ntegrated ;ith the AR module &or Emplo#eeOs details liCe : Eame=
Address= Emplo#ee code= designation= grade= position= cost centre= etc
Hes
SAP
ACM
12$ Allo;s to maintain and update emplo#eeOs salar# / ;age structure
Hes
SAP
ACM
123 Allo;s to tracC changes made to the structure
Hes
SAP
ACM
12) Pro"ision &or commission ta.les &or complex calculations
Hes
SAP
ACM
121 Captures emplo#eeOs .anC account num.er and .anC details
Hes
SAP
ACM
12/ Allo;s to de&ine di&&erent salar# or ;age classes and scales
Hes
SAP
ACM
120 Allo;s to de&ine unlimited no o& ne; heads o& pa# or ne; heads o&
deduction at a later date to accommodate an# changes in the salar#
structure / ;age structure due to internal changes or statutor# changes
Hes
SAP
ACM
124 Allo;s to capture cost centre o& each emplo#ee and salar# or ;age data
can .e allocated to "arious cost centers
Hes
SAP
ACM
122 8nlimited num.er o& salar# / ;age t#pes and .ases
Hes
SAP
ACM
121( Allo;s to de&ine standard and .ranch / di"ision or location speci&ic salar# /
;age t#pes
Hes
SAP
ACM
1211 Allo;s de&ining designation / grade speci&ic salar# or ;age t#pe
Hes
SAP
ACM
121$ Allo;s trans&erring o& attendance records to pa#roll s#stem in .atch mode
or manuall#
Hes
SAP
ACM
1213 Allo;s calculation o& o"ertime and other shi&t dependent allo;ances .ased
on the attendance records trans&erred to pa#roll s#stem
Hes
SAP
ACM
121) S#stem should .e a.le to categori6e the deductions 9deduction on ad"ance
taCen= loans &rom compan# or external organi6ations= pa#ments &or an# other
purposes to external org= etc:
Hes
SAP
ACM
1211 Pro"ision o& supporting loan details / ad"ances taCen "ia: amount taCen=
tenure= amount o& each installment
Hes
SAP
ACM
121/ Pro"ision to set loan and ad"ances re-pa#ment schedule ;ith an option to
modi&# the same
Hes
SAP
ACM
1210 Pro"ision to print salar# / ;age slips as per user de&ined &ormat pro"iding
details o& emoluments and deductions
Hes
SAP
ACM
1214 !ption o& exporting salar# / ;age slip in desired &ormat
Hes
SAP
ACM
1212 Pro"ision to carr# &or;ard negati"e salar# / ;age o& an emplo#ee to the next
pa#roll c#cle su.Bect to speci&ic authorisation
Hes
SAP
ACM
12$( Pro"ision to consolidate salar# .ill across groups= sla.s= seniorit# etc
Hes
SAP
ACM
12$1 7lo.al editing o& ;age records 9eg: i& con"e#ance allo;ance has increased
uni&orml# across grade le"els then a single update in the Salar# Master ;ill
drill do;n to the indi"iduals in that categor#: Hes
SAP
ACM
12$$ !n-line and .atch pa#roll statements
Hes
SAP
ACM
12$3 Selection o& salar# .# departments= locations= grade or .anC through
;hich pa#ment ;ill .e processed
Hes
SAP
ACM
12$) Should allo; &or Pro Rata calculations
Hes
SAP
ACM
12$1 3age pa#ments .# electronic s#stem such as BanC trans&ers / Che,ue /
Cash Hes
SAP
ACM
Annex B: Appendix 3B- Compliance Sheet
Page 65 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Re5eren3e ,n Pro*o)+- Re2+r8
SUP MOD &RD CST FUT NS
12$/ 8nlimited num.er o& salar# statements per month
Hes
SAP
ACM
12$0 Should .e a.le to generate emplo#ee-;ise records o& unpaid salar#
Hes
SAP
ACM
12$4 Should .e a.le to calculate the arrear pa#ment automaticall# once the
details o& arrear pa#ments are entered
Hes
SAP
ACM
12$2 Should allo; &or emplo#ees to claim allo;ances as per the appro"ed salar#
structure
Hes
SAP
ACM
123( Should allo; &or each claim to .e appro"ed= on a ;orC&lo; .asis
Hes
SAP
ACM
1231 Should allo; &or automaticall# con"erting the claims to pa#ment "ouchers=
.ased on the nature o& claim and amount
Hes
SAP
ACM
123$ Print and export to a &ile pa#roll Bournal .# month / period / cumulati"e /
pre"ious #ears
Hes
SAP
ACM
1233 %n the case o& *ull and *inal Settlements= the &inal salar# / is to .e
generated upon receipt o& clearances as per the AR module Calculations
&or End o& Ser"ice .ene&its to .e done as per user de&initions and added to
the settlement pacCage Hes
SAP
ACM
123) %n case o& &inal settlement= the s#stem should stop processing salar# &or
that emplo#ee
Hes
SAP
ACM
1231 +he s#stem should ha"e pro"ision to stop pa#ment &or emplo#ees ;ho are
marCed as a.sconding
SAP
ACM
1.>.& S/**-1 C4+,n M+n+.e2en(
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
1 Gener+-
11 Possi.le to de&ine material master Hes
SAP ERP
MM
111 %tem code
Hes
SAP ERP
MM
11$ %tem description
Hes
SAP ERP
MM
113 8nit o& measure 9in alphanumeric characters:
Hes
SAP ERP
MM
11) Speci&ications 9should ha"e pro"ision &or attaching documents / dra;ings:
Hes
SAP ERP
MM
111 Shel&-li&e
Hes
SAP ERP
MM
11/ Reorder point 9maximum / minimum stocC le"els:
Hes
SAP ERP
MM
110 Economic order ,uantit#
Hes
SAP ERP
MM
114 Si6e/"olume
Hes
SAP ERP
MM
112 Categories as capital= consuma.le= operations R maintenance
Hes
SAP ERP
MM
111( Cross-re&erence ,uali&ied "endor in&ormation to each purchased part o&
su.assem.l# .#:
Hes
SAP ERP
MM
1111 -endor num.er
Hes
SAP ERP
MM
111$ -endor name
Hes
SAP ERP
MM
1113 -endor part num.er
Hes
SAP ERP
MM
Annex B: Appendix 3B- Compliance Sheet
Page 66 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
111) %tem code
Hes
SAP ERP
MM
1111 Manu&acturersO part num.er
Hes
SAP ERP
MM
1$ Possi.le to de&ine material as the &ollo;ing
Hes
SAP ERP
MM
1$1 Capital &or proBects 9Steel= etc:
Hes
SAP ERP
MM
1$$ Consuma.le
Hes
SAP ERP
MM
1$3 Spares
Hes
SAP ERP
MM
1$) !perations R maintenance 9eg maintenance tools:
Hes
SAP ERP
MM
1$1 'amaged material
Hes
SAP ERP
MM
13 Possi.le to de&ine groups o& materials liCe main group= su. group etc
Hes
SAP ERP
MM
1) Should .e possi.le to marC items as indigenous or imported
Hes
SAP ERP
MM
11 S#stem should generate material code 9alpha-numeric: .ased on user
de&ined logic
Hes
SAP ERP
MM
1/ Possi.le to map material code o& a processed material ;ith material codes
o& components that are used to prepare the processed material
Hes
SAP ERP
MM
10 Possi.le to a"oid generation o& material code &or the same material
speci&ication
Hes
SAP ERP
MM
14 %n case o& generation o& a ne; material code= a.ilit# to map all old codes
;ith the ne; codes
Hes
SAP ERP
MM
12 Possi.le to de&ine a master list o& "endors ;ith &ollo;ing details Hes
SAP ERP
MM
121 Compan# details 9address= contact person= etc: Hes
SAP ERP
MM
12$ Material supplied .# the "endor Hes
SAP ERP
MM
123 @ead times &or material supplied .# "endor Hes
SAP ERP
MM
12) Prices o& items supplied .# "endor Hes
SAP
ERP
MM
11( Possi.le to de&ine stores in the s#stem ;ith &ollo;ing details Hes
SAP ERP
MM
11(1 @ocation o& store Hes
SAP ERP
MM
11($
Code &or the store 9multiple stores de&inition possi.le: Hes
SAP ERP
MM
11(3
3hether *E3A store or contractor store Hes
SAP ERP
MM
11()
Eame o& the contractor ;hose store it is Hes
SAP ERP
MM
11(1
'epartment using the store Hes
SAP ERP
MM
11(/
%tems stored in the store 9Capital / Spares / Consuma.les etc: Hes
SAP ERP
MM
111
Pro"ision to pass recti&ication entries &or an# errors during document
creation/appro"al Hes
SAP ERP
MM
11$ Possi.le to capture details a.out @etter o& credit Hes
SAP ERP
MM
Annex B: Appendix 3B- Compliance Sheet
Page 67 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
11$1 Pro"ision to capture letter o& credit/Bu#ersO credit in&ormation Hes
SAP ERP
MM
11$$
Pro"ide reports on @/Cs pending retirement= expir# dates Hes
SAP ERP
MM
11$3
Pro"ision to tracC @/c limits Hes
SAP ERP
MM
11$)
Pro"ision to load @/C charges on goods recei"ed Hes
SAP ERP
MM
11$1
Pro"ision to tracC pa#ments through @/Cs= remittances Hes
SAP ERP
MM
113 Possi.le to enter recti&ication "ouchers &or an# ;rong entries made earlier Hes
SAP ERP
MM
11)
Possi.le to de&ine audit in&ormation liCe creator= appro"er and de&ine
access control &or in&ormation Hes
SAP
BAS%S
2 Con(r+3()
SAP ERP
MM
$1
Possi.le to de&ine a contract ;ith the contractor 9selected .ased on
tendering process: ;ith &ollo;ing details Hes
SAP ERP
MM
$11 Contract t#pe Hes
SAP ERP
MM
$1$ Contract num.er Hes
SAP ERP
MM
$13 +erms and conditions Hes
SAP ERP
MM
$1)
Scope o& ;orC under the contract 9attach documents / dra;ings as a part o&
speci&ications: Hes
SAP ERP
MM
$11 Schedule o& rates 9ie rates &or each acti"it# under the contract: Hes
SAP ERP
MM
$1/ Start date / End date Hes
SAP ERP
MM
$10 Contractor details Hes
SAP ERP
MM
$14 Su.-Contractors Hes
SAP ERP
MM
$12 Pa#ment terms and amount Hes
Can .e
customi6e
d as per
the actual
re,uireme
nt
$11( Eormal 9allo;a.le: loss o& material Hes
SAP ERP
MM
$$ Possi.le to de&ine contract t#pes Hes
SAP ERP
MM
$$1 Annual rate contract 9ARC: Hes
SAP ERP
MM
$$$ Single purchase contract
SAP ERP
MM
$3
Possi.le to capture &ollo;ing details speci&ic to contracts ;ith
Energ#/3ater suppliers Hes
8sing the
material
master
data
parameter
s
$31
speci&ications o& the Energ# to .e supplied ;ith possi.le range o&
parameters 9eg range ;ithin ;hich the suppl# "oltage should &all: Hes
SAP ERP
MM
$3$
upper and lo;er limit o& ,uantit# o& "olume to .e supplied ;ith possi.le
range o& parameters Hes
SAP ERP
MM
Annex B: Appendix 3B- Compliance Sheet
Page 68 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
$33 Charges &or consumption on time-o&-da# Hes
SAP ERP
MM
$3) Charges &or consumption limits 9upper and lo;er limit: Hes
SAP ERP
MM
$31
Pricing &ormulae 9in"ol"ing addition= su.traction= etc: using a.o"e
speci&ications o& contract Hes
SAP ERP
MM
$3/
!ther terms and conditions 9taCe or pa#= Billing= credit period= etc: 9re&er to
re,uirements de&ined in DBillingD &or &urther details: Hes
SAP ERP
MM
$)
Possi.le to de&ine a.o"e contract details .ased on the data alread# captured
during tendering process Hes
SAP ERP
MM
$1
Possi.le to linC ProBect9s: ;ith the Contract 9ie linC ProBect num.er9s:
;ith a Contract num.er: Hes
SAP ERP
MM
$/ Possi.le to amend the contract .# de&ined authorit# Hes
SAP ERP
MM
$0 Monitor contract per&ormance and input Ce# contract e"ents Hes
Can .e
customi6e
d as per
the actual
re,uireme
nt
$4 Possi.le to capture 7uarantee 9i& an#: related to the contract
& M+(er,+- re9/,),(,on +nd ,nden(
31
Possi.le to de&ine list and ,uantit# o& material 9Bill o& Material:
re,uirement &or pro"ision o& each domestic connection Hes
SAP ERP
MM
3$
Possi.le to compute aggregate material re,uirement .ased on the
con"ersion targets &or the #ear Hes
SAP ERP
MM
33
Possi.le to arri"e at monthl# indent plan &or the material re,uirements &or
an #ear arri"ed as a.o"e Hes
SAP ERP
MM
3) Possi.le to prompt &or raising an indent ;hen material reaches reorder le"el Hes
SAP ERP
MM
31
Possi.le to release a 'eli"er# order &or an ARC contract ;hen material
reaches reorder le"el 9considering on "aria.le demand: Hes
SAP ERP
MM
3/
Possi.le to checC material deli"er# pending against existing Purchase
orders
SAP ERP
MM
30 Possi.le to generate an indent &or material ;ith &ollo;ing details Hes
SAP ERP
MM
301 Material code= description and ,uantit# Hes
SAP ERP
MM
30$ Expected deli"er# date Hes
SAP ERP
MM
303 ProBect num.er o& proBect &or ;hich the material is re,uired Hes
SAP ERP
MM
30) @ocation ;here material is re,uired Hes
SAP ERP
MM
301 Material inspection plan / approach Hes
SAP ERP
MM
30/ Material deli"er# location 9possi.le to indicate more than one locations: Hes
SAP ERP
MM
300 PacCing details Hes
SAP ERP
MM
304 *ields &or OPurpose o& indentO= ORemarCsO= Attaching separate &ile &or BEC Hes SAP SRM
302 Bid e"aluation criteria 9+echnical: Hes
SAP ERP
MM
34
Possi.le to "ie; item-;ise estimated price / last purchase price &or each
material Hes
SAP ERP
MM
32 Possi.le to indicate the total "alue o& the indent Hes
SAP ERP
MM
Annex B: Appendix 3B- Compliance Sheet
Page 69 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
31(
Possi.le to checC a"aila.le stocC 9at all stores including the contractorsO
stores: .e&ore raising indent Hes
SAP ERP
MM
311 Possi.le to consolidate multiple indents into one Hes
Sap ERP
MM
31$ Possi.le to checC &ollo;ing .e&ore raising indent Hes
SAP ERP
MM
31$1 Pending orders Hes
SAP ERP
MM
31$$ Material in transit Hes
SAP ERP
MM
313
Possi.le to de&ine authorit# and limits o& raising indent .ased on
designation Hes
SAP ERP
MM
31) Possi.le to checC .udgeted purchase limits .e&ore accepting an indent Hes
SAP ERP
MM
311
Possi.le to grant &inancial concurrence .# &inance dept= in case o& non-
.udgeted items Hes
SAP ERP
MM
31/ Possi.le to de&ine ;orC&lo; .ased appro"al process &or indents Hes
SAP ERP
MM
310 Ena.les the creator o& indent to de&ine the appro"er
314 Pro"ision to prede&ine appro"er &or indent depending on Hes
SAP ERP
MM
3141 reporting hierarch# Hes
SAP ERP
MM
314$ amount o& indent Hes
SAP ERP
MM
3143 +#pe o& indent 9nomination= limited tender= proprietar#= etc:
312 Ena.le changing the indent 9,uantit#= material code= etc: once it is created Hes
SAP ERP
MM
3121 .# creator Hes
SAP ERP
MM
312$ .# re"ie;er Hes
SAP ERP
MM
3$(
Pro"ision &or appro"er to put comments on the indent recei"ed &or appro"al
.# re"ie;er Hes
SAP ERP
MM
3$1
Possi.le to tracC the histor# o& an indent in terms o& creation= modi&ication
and appro"al Hes
SAP ERP
MM
3$$
Possi.le to maintain and "ie; %ndent register .ased on ProBect num.er=
location and date Hes
SAP ERP
PS
> Tender,n. *ro3e))
)1
Possi.le to de&ine ;orC&lo; and steps &or di&&erent tendering process liCe
!pen= t;o .id s#stem= etc Hes
SAP ERP
MM
)$
Possi.le to assign the indent to personnel in Purchase department &or
initiating tendering process Hes
SAP ERP
MM
)3 Possi.le to de&ine a ne; tender .# aggregating multiple indents Hes
SAP ERP
MM
))
Support creation o& Re,uest &or 5uotation .# including items re,uired=
,uantit#= shipment location= "alidit# period= technical speci&ication= taxes=
etc Hes
SAP ERP
MM
)1 Possi.le to "ie; list o& "endors a"aila.le &or a particular item Hes
SAP ERP
MM
)/
Support creation o& Re,uest &or 5uotation &or ser"ice and construction
contracts .# including ;orC orders Hes SAP SRM
)0 Possi.le to enter responses &rom "endors in the s#stem Hes
Binding
Period is
supported
)4 Possi.le to capture the de"iations and "alidit# o& responses &rom "endors Hes
SAP ERP
MM
Annex B: Appendix 3B- Compliance Sheet
Page 70 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
)2
Possi.le to enter re"ised .ids &rom the "endors in the s#stem ;ith a
re&erence to the re"ision num.er ;hich it has undergone Hes
SAP ERP
MM
)1( Possi.le to maintain a histor# o& all re"ised .ids recei"ed &rom "endors Hes
SAP ERP
MM
)11 Possi.le to capture details o& Bid Securit# recei"ed &rom "endors Hes
SAP ERP
MM
)1$
Possi.le to de&ine ;orC&lo; &or e"aluation o& "endor responses in"ol"ing
t;o stages 9+echnical and Commercial e"aluation: Hes
SAP ERP
MM
)13
Ena.les e"aluation o& responses .ased on a pre-de&ined e"aluation criteria
and reBection criteria Hes
SAP ERP
MM
)1)
Possi.le to capture issue o& letter to "endors i& Bid ,uotation criteria is not
met Hes
SAP ERP
MM
)11 Possi.le to arri"e at ranCing o& .idders a&ter consolidation or responses Hes SAP SRM
)1/
Possi.le to maintain an audit trail o& .idding process in &ollo;ing steps
- Appro"al o& Bid ,uotation / e"aluation / ,uali&ication criteria
- Release o& R*5
- Receipt o& .ids &rom "endors
- +echnical / Commercial ,uali&ications
- Bid e"aluation and negotiations
- Selection o& "endor Hes
SAP ERP
MM
)10
Possi.le to maintain a tender opening register ;ith details o& price .ids &or
each "endor Hes
SAP ERP
MM
)14
Possi.le to customi6e the tendering process .# adding / remo"ing steps
9eg open tending process ;ill ha"e additional step o& placing ne;spaper
ad"ertisement: Hes
SAP ERP
MM
)12
S#stem maintains a historical record o& .idding process and updates "endor
pro&ile .# registering e"er# ;in .# "endor
5 P/r34+)e order Hes
SAP ERP
MM
11 Possi.le to generate a purchase order using data &rom one / multiple indents Hes
SAP ERP
MM
1$
Possi.le to capture details o& purchase proposal identi&#ing the material
re,uirements and terms o& purchase liCe deli"er# date Hes
SAP ERP
MM
13
Possi.le to generate a P! ;ithout going through some or all acti"ities liCe
indenting= tendering process R selection o& "endor Hes
SAP ERP
MM
1)
Possi.le to generate a purchase order / deli"er# order 9&or ARC: ;ith
&ollo;ing data Hes
SAP ERP
MM
1)1 Material code and description Hes
SAP ERP
MM
1)$ Material speci&ication Hes
SAP ERP
MM
1)3 5uantit# Hes
SAP ERP
MM
1)) Price Hes
SAP ERP
MM
1)1 'eli"er# date Hes
SAP ERP
MM
1)/ 'eli"er# location 9single / multiple: Hes
SAP ERP
MM
1)0 Supplier details Hes
SAP ERP
MM
1)4 Pa#ment terms Hes
SAP ERP
MM
1)2 Eames o& third part# inspection agenc# Hes
SAP ERP
MM
Annex B: Appendix 3B- Compliance Sheet
Page 71 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
1)1( %nspection plan 9inspection stages= inspecting agenc#: Hes
SAP ERP
MM
1)11 PacCaging details 9&ree text input: Hes
SAP ERP
MM
11 Possi.le to de&ine the purchase order t#pe .ased on suppl# source Hes
SAP ERP
MM
111 @ocal Hes
SAP ERP
MM
11$ %mported
1/ Possi.le to linC a P! ;ith &ollo;ing Hes
SAP ERP
MM
1/1 8ser department 9eg !RM= AR: Hes
SAP ERP
MM
1/$ ProBect code9s: &or a proBect Hes
SAP ERP
MM
10 Possi.le to identi&# a P! &or spares related to particular capital item
14
Should allo; modi&ication o& P! ;ith appro"al &rom authorit#
Modi&ication should .e possi.le related Hes
SAP ERP
MM
141 5uantit# Hes
SAP ERP
MM
14$ %tems Hes
SAP ERP
MM
143 Spares Hes
SAP ERP
MM
14) 'eli"er# date Hes
SAP ERP
MM
12 Should allo; maintaining a histor# o& modi&ications made to P! Hes
SAP ERP
MM
11(
Should .e possi.le to reopen a P! a&ter it is closed 9ie material / ser"ices
pro"ided and pa#ments made: +he reopened P! should allo; entering o&
additional material / ser"ices Hes
SAP ERP
MM
111 Should allo; capture o& BanC 7uarantee details Hes
Can .e
customi6e
d as per
the actual
re,uireme
nts
1111 B7 Eo Hes
Can .e
customi6e
d as per
the actual
re,uireme
nts
111$ BanC name Hes
Can .e
customi6e
d as per
the actual
re,uireme
nts
1113 'ate Hes
Can .e
customi6e
d as per
the actual
re,uireme
nts
111) Amount Hes Can .e
customi6e
d as per
the actual
re,uireme
Annex B: Appendix 3B- Compliance Sheet
Page 72 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
nts
1111 -alidit# Hes
Can .e
customi6e
d as per
the actual
re,uireme
nts
111/ -endor / Contractor name Hes
Can .e
customi6e
d as per
the actual
re,uireme
nts
11$
S#stem should prompt in ad"ance 9user de&ined num.er o& da#s: .e&ore
expir# o& B7 Hes
SAP ERP
MM
113 Should allo; anal#sis o& P!Os .ased on &ollo;ing Hes
1131 Contract num.er Hes
SAP ERP
MM
113$ -endor Hes
SAP ERP
MM
1133 'eli"er# date Hes
SAP ERP
MM
1113) 5uantit# Hes
SAP ERP
MM
11131 Rate Hes
SAP ERP
MM
1113) Pa#ment terms Hes
SAP ERP
MM
11) Possi.le to linC one or more indents ;ith P! Hes
SAP ERP
MM
111 Possi.le to linC one or more P!s ;ith one or more indents Hes
SAP ERP
MM
11/
Possi.le to open and close P! depending on the status o& deli"er# and
pa#ment
C M+(er,+- re3e,*( Hes
SAP ERP
MM
/1 Possi.le to de&ine an agenc# &or inspection o& material
/$ Possi.le to input material inspection details in the s#stem Hes
/$1 %nspection agenc# Hes
SAP ERP
MM
/$$ Eame o& the inspector Hes
SAP ERP
MM
/$3 %nspection date Hes
SAP ERP
MM
/$) %nspection &indings
/3 Possi.le to tracC status o& material &rom the suppliersO premise Hes
SAP ERP
MM
/31 'ispatched Hes
SAP ERP
MM
/3$ 'amaged in transit Hes
SAP ERP
MM
/33 Recei"ed at recipientOs end
/) Possi.le to capture material receipt details Hes
SAP ERP
MM
/)1 Challan 9Receipt &or pa#ment or deli"er#: details Hes
SAP ERP
MM
/)$ P! &or ;hich material is recei"ed Hes
SAP ERP
MM
/)3 Contract num.er &or ;hich material is recei"ed Hes SAP ERP
Annex B: Appendix 3B- Compliance Sheet
Page 73 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
MM
/)) '! 9'eli"er# order &or ARCs: &or ;hich material is recei"ed Hes
SAP ERP
MM
/)1 'ate o& receipt Hes
SAP ERP
MM
/)/ Store ;here material is recei"ed Hes
SAP ERP
MM
/)0 Material code o& material recei"ed Hes
SAP ERP
MM
/)4 5uantit# o& material recei"ed Hes
SAP ERP
MM
/)2 'ate and time o& receipt Hes
SAP ERP
MM
/1
Possi.le to de&ine location other than the store 9eg user department at the
*E3A !&&ice: ;here the material is recei"ed directl# Hes
SAP ERP
MM
//
S#stem should alert i& the material receipt ,uantit# is greater / less than the
,uantit# mentioned in the P!
/0 Possi.le to generate a note to .e sent to the supplier identi&#ing &ollo;ing Hes
SAP ERP
MM
/01 !"er receipt o& material Hes
SAP ERP
MM
/0$ 8nder receipt o& material Hes
SAP ERP
MM
/03 'amaged material recei"ed Hes
SAP ERP
MM
/0) ReBection o& material a&ter inspection
/4
Possi.le to modi&# material receipt details 9&or reasons liCe ;rong entr#
initiall#: Hes
SAP ERP
MM
/41 Material code o& material recei"ed Hes
SAP ERP
MM
/4$ 5uantit# o& material recei"ed Hes
SAP ERP
MM
/43 -alue o& material recei"ed Hes
SAP ERP
MM
/2 S#stem should support capture o& multiple P!Os &or single receipt Hes
SAP ERP
MM
/1(
Possi.le to de&ine details o& material accepted / reBected a&ter inspection on
receipt o& material Hes
SAP ERP
MM
/11 S#stem should automaticall# update stocC in stores on receipt o& material Hes
SAP ERP
MM
/1$
S#stem should deduce the ,uantit# o& amount D#et to .e deli"eredD &rom a
P! on receipt o& material Hes
SAP ERP
MM
/13
Possi.le to identi&# de&ecti"e material returned .# contractor as
manu&acturing de&ect or damage due to mishandling Hes
SAP ERP
MM
/1)
Possi.le to map the receipt o& processed material &rom contractors against the
issue o& material to contractor &or preparation o& processed material
D M+(er,+- ,))/e
01 Possi.le to capture material re,uisition details Hes
SAP ERP
MM
011 Material code Hes
SAP ERP
MM
01$ Material ,uantit# Hes
SAP ERP
MM
013 Eame o& the person re,uesting material Hes
SAP ERP
MM
01) Eame o& the entit# 9*E3A / Contractor: re,uesting material Hes
SAP ERP
MM
011 P! / Contract num.er Hes SAP ERP
Annex B: Appendix 3B- Compliance Sheet
Page 74 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
MM
01/ 'ate o& re,uisition Hes
SAP ERP
MM
0$ Possi.le to generate a uni,ue issue re,uisition num.er Hes
SAP
ERP
MM
03 Should ena.le posting details o& material issue Hes
SAP ERP
MM
031 Re&erence material issue re,uisition num.er Hes
SAP ERP
MM
03$
*E3A department to ;hich issue is made Hes
SAP ERP
MM
033
Eame o& Contractor to ;hom issue is made Hes
SAP ERP
MM
03)
Eame o& personnel re,uesting material issue Hes
SAP ERP
MM
031
ProBect code &or ;hich material is issued Hes
SAP ERP
MM
03/
Contract num.er against ;hich the material is issued Hes
SAP ERP
MM
030
Material codes o& material issued Hes
SAP ERP
MM
034
5uantit# o& material issued Hes
SAP ERP
MM
032
Cost centre &or ;hich material is issued Hes
SAP ERP
MM
031(
Store &rom ;hich material is issued
0) Should deduct the stocC a"aila.le to the extent o& material issued Hes
SAP ERP
MM
0)1 %n stores Hes
SAP ERP
MM
0)$ A"aila.le &or a proBect as compared to ;hat ;as .udgeted Hes
SAP ERP
MM
0)3 A"aila.le &or a department as compared to ;hat ;as .udgeted
01 Possi.le to capture lending o& material on returna.le .asis Hes
SAP ERP
MM
011 Possi.le to tracC material issued &or processing Bo. R returna.le .asis Hes
SAP ERP
MM
01$ Possi.le to de&ine input/output material con"ersion unit o& measure Hes
SAP ERP
MM
013 Reconciliation o& material issued &rom processing R recei"ed .acC Hes
SAP ERP
MM
0/
Possi.le to marC against each 7oods Receipt -oucher= an# charges on
suppliers
00
Possi.le to capture details o& material sale &rom the stores ;ith &ollo;ing
details Hes
SAP ERP
MM
001 Part# ;hom the sale is made Hes
SAP ERP
MM
00$ Rate o& sale Hes
SAP ERP
MM
003 5uantit# o& material sold Hes
SAP ERP
MM
00) Material code o& material sold Hes
SAP ERP
MM
001 'ate o& sale Hes
SAP ERP
MM
00/ 'ate o& material dispatch &rom the stores Hes
SAP ERP
MM
Annex B: Appendix 3B- Compliance Sheet
Page 75 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
04
Possi.le to trigger an entr# &or accounts recei"a.les in *RA module
e,ui"alent to the "alue o& sale in a.o"e case Hes
SAP ERP
*inancials
F M+(er,+- )(o38 2+n+.e2en(
41 At an# point o& time indicate material Hes
SAP ERP
MM
411 Budgeted &or each proBect / department Hes
SAP ERP
MM
41$
!rdered &or each proBect / department Hes
SAP ERP
MM
413
A"aila.le at *E3A stores &or each proBect / department Hes
SAP ERP
MM
41)
A"aila.le at ContractorOs store &or each proBect Hes
SAP ERP
MM
411 Consumed .# each proBect / department during the &inancial #ear
4$ +racC material trans&er &rom Hes
SAP ERP
MM
4$1 !ne store to another Hes
SAP ERP
MM
4$$ !ne proBect to another Hes
SAP ERP
MM
4$3 !ne contractor to another Hes
SAP ERP
MM
4$) *E3A store to contractorOs store Hes
SAP ERP
MM
43 Possi.le to add &reight ;hen material is trans&erred Hes
SAP ERP
MM
4) Possi.le to tracC material issue under &ollo;ing heads Hes
SAP ERP
MM
4)1 8sage &or steel &or proBects 9;ith proBect num.er: Hes
SAP ERP
MM
4)$ 8sage &or CPE ;orC at the consumers Hes
SAP ERP
MM
4)3 CRE 9consumer num.er: ;here it is used Hes
SAP ERP
MM
4)) ProBect num.er &or PE installation Hes
Sap ERP
PS
41 Possi.le to tracC material through &ollo;ing mechanism Hes
SAP ERP
MM
411 Capture o& material issue in&ormation ;hen material is issued Hes
SAP ERP
MM
41$ Capture o& in&ormation ;hen ph#sical "eri&ication is done at proBect site Hes
SAP ERP
MM
4/ Possi.le to tracC 7R- details &or capital material recei"ed in past Hes
SAP ERP
MM
40
Should ena.le computation o& Reorder le"els .ased on the lead times and
consumption pattern Hes
SAP ERP
MM
44 Should support ABC anal#sis o& material Hes
SAP ERP
MM
42 Should support anal#sis o& material loss in transit Hes
SAP ERP
MM
41( Should support anal#sis o& normal loss as pro"ided in the contract Hes
SAP ERP
MM
411
Possi.le to maCe reco"er# &rom contractor &or loss o& material .# raising
auto-in"oice Hes
SAP ERP
MM
41$
Should support anal#sis o& material .udgeted "s actual &or .oth 9Rate and
5uantit# : Hes
SAP ERP
MM
413 Possi.le to capture &indings o& ph#sical "eri&ication o& stocC Hes
SAP ERP
MM
Annex B: Appendix 3B- Compliance Sheet
Page 76 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
41)
Possi.le to update the a"aila.le stocCs o& material .ased on the &indings o&
"eri&ication o& stocC Hes
SAP ERP
MM
411
Pro"ision to enter material consumption details 9.ased on laid dra;ings:
&or a proBect Hes
SAP ERP
MM
41/
Possi.le to get an appro"al &rom the *E3A engineer &or the details on
consumption entered in the s#stem Hes
SAP ERP
MM
410
Pro"ision to get material "aluation &or material entered as consumed &or a
proBect .ased on purchase price Hes
SAP ERP
MM
414
Pro"ision to undertaCe material reconciliation &or material consumed "s
material issued &or each proBect Hes
SAP ERP
PS
9 "endor / Con(r+3(or 2+n+.e2en( Hes
SAP ERP
MM
21 Possi.le to de&ine &re,uenc# and time period &or e"aluation o& "endors Hes
SAP
ERP
MM
2$
Possi.le to de&ine &rame;orC and e"aluate "endors .ased on these
parameters Hes
SAP ERP
MM
2$1 @ead times &or suppl# Hes
SAP ERP
MM
2$$ 5ualit# o& material supplied Hes
SAP ERP
MM
2$3 Prices o& material Hes
SAP ERP
MM
2$) *lexi.ilit# sho;n .# the "endor in terms o& lead times R prices Hes
SAP ERP
MM
23 Possi.le to de&ine "endors in terms o& ranCing Hes
SAP ERP
MM
231 Best per&orming 9long term .usiness partners: Hes
SAP ERP
MM
23$ A"erage per&ormance Hes
SAP ERP
MM
233 BlacClisted "endors 9to a"oid undertaCing .usiness in &uture: Hes
SAP ERP
MM
2) Possi.le to summaries &ollo;ing &or each "endor &or a user de&ined period Hes
SAP ERP
MM
2)1 %nstances o& material reBected on ,ualit# parameters Hes
SAP ERP
MM
2)$ -aria.ilit# o& deli"er# schedules as compared to agreed schedules Hes
SAP ERP
MM
2)3 -aria.ilit# o& prices o"er a period o& time Hes
SAP ERP
MM
2)) Ee; "endors during the last user de&ined period Hes
SAP ERP
MM
21 Pro"ide reports on each "endor Hes
SAP ERP
MM
211 !rders placed ;ith the "endor during user de&ined period Hes
SAP ERP
MM
21$ !rders currentl# li"e ;ith deli"er# o& material pending Hes
SAP ERP
MM
2/
Possi.le to &ind list o& all ne; items ;hich are de"eloped / procured in
user de&ined period Hes
SAP ERP
MM
10 M+(er,+- 0+-/+(,on
1(1 Possi.le to capture &ollo;ing prices related to material Hes
SAP ERP
MM
1(11 Current marCet price Hes
SAP ERP
MM
1(1$ Actual purchase price Hes
SAP ERP
MM
Annex B: Appendix 3B- Compliance Sheet
Page 77 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
S8P M!' 3R' CS+ *8+ ES
1($
Possi.le to capture actual purchase price o& material directl# &rom the
purchase order o& the material along ;ith o"erheads 9loading &actor: as per
P! Hes
SAP ERP
MM
1(3
Possi.le to linC pa#ments o& custom dut#= transportation= CR* charges= etc
along ;ith 7R- Hes
SAP ERP
MM
1()
%n case o& trans&er / issue o& material= a.ilit# to trace the purchase price o&
material at an# stage 9in trans&er: &or the purpose o& "aluation Hes
SAP ERP
MM
1(1
Possi.le to arri"e at indi"idual material price .ased on o"erall price in case
o& .ulC purchase Hes
SAP ERP
MM
1(/
Possi.le to de&ine material stocC "aluation methodologies .ased on 9*%*!=
@%*! and/or 3eighted a"erage : Hes
SAP ERP
MM
1(0 Possi.le to arri"e at material stocC "aluation &or &ollo;ing groups Hes
SAP ERP
MM
1(01 -aluation o& material in a proBect Hes
SAP ERP
MM
1(0$ -aluation o& material in a department Hes
SAP ERP
MM
1(03 -aluation o& material in a stores Hes
SAP ERP
MM
1(4 Possi.le to maintain a histor# o& material "aluation &or user-de&ined periods
Hes SAP ERP
MM
11 B/),ne)) A**-,3+(,on) C+(+-o./e
111 Colla.oration process support &or material management
11$ Price 'e"iations
113
Engineering change order "ariance and noti&ications
11) !rder tracCing and status alerting
111 5ualit# and #ield management
11/
%n"entor# shortages= including noti&ication to replenishment s#stems
110 5ualit# control ;ith control charts
114
Machine .reaCdo;n alerts and causal anal#sis
112
'emand "olatilit#= including de"iations due to ne; orders= cancellations=
and ;rong mix
111(
Real-time detection o& shrinCage
1111 Polic# rules anal#sis and de"iation anal#sis
111$
@ogistics trace and tracC noti&ications o& such issues as late deli"eries and
de"iation &rom routes
1.>.> '/2+n C+*,(+- M+n+.e2en(
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
1 E2*-o1ee D+(+6+)e +nd Or.+n,B+(,on S(r/3(/re
11 Maintain emplo#ee in&ormation including:
111 Emplo#ee num.er Hes
SAP ERP
ACM
Annex B: Appendix 3B- Compliance Sheet
Page 78 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
11$
Emplo#ee name Hes
SAP ERP
ACM
113
Address 9Present and permanent: Hes
SAP ERP
ACM
11)
Phone num.er= mo.ile num.er= e-mail %'= extension num.er Hes
SAP ERP
ACM
111
'ate o& Birth and 7ender Hes
SAP ERP
ACM
11/
Marital status Hes
SAP ERP
ACM
110
'etails o& children Hes
SAP ERP
ACM
114
Academic 5uali&ications and Pro&essional ,uali&ications Hes
SAP ERP
ACM
112
'esignation Hes
SAP ERP
ACM
111( Pre"ious experience capturing
Eames o& companies= Sector o& industr# ;ere ;orCed
+enure 9&rom - to: and Role Hes
SAP ERP
ACM
1111
+rainings or courses undergone .e&ore Boining M7@ Hes
SAP ERP
ACM
111$
'ate o& Boining Hes
SAP ERP
ACM
1113
Cost to Compan# 9this &ield should .e pass;ord protected: Hes
SAP ERP
ACM
111)
Status 9Permanent= Pro.ation= Management +rainees= 7raduate Engineer
+rainees: Hes
SAP ERP
ACM
1111
Eationalit# Hes
SAP ERP
ACM
111/
%' Eum.er Hes
SAP ERP
ACM
1110
Passport Eum.er and resident %' 9 &or non @ocal : Hes
SAP ERP
ACM
1114
Blood group Hes
SAP ERP
ACM
1112
!ther details liCe insurance Hes
SAP ERP
ACM
1$
Should .e possi.le to trans&er all 9a"aila.le: &ields mentioned a.o"e &rom
the applicant data.ase 9generated during the recruitment process: to
emplo#ee data.ase Hes
SAP ERP
ACM
13
Should support de&ining reporting hierarch# &or emplo#ees to include
multile"el reporting or multi disciplinar# reporting Hes
SAP ERP
ACM
1)
Should .e possi.le to capture details o& trans&er o& an emplo#ee &rom one
department to another ;ithout changes other attri.utes liCe emplo#ee
num.er Hes
SAP ERP
ACM
11
Should tracC all emplo#ee histor# in M7@ in terms o& past roles as ;ell as
past per&ormance and positions Hes
SAP ERP
ACM
1/
Should allo; &or maintaining a checClist o& details to .e mentioned in each
emplo#eeOs personnel &ile Hes
SAP ERP
ACM
10
S#stem should capture &re,uenc# o& replacement &or items issued to
emplo#ees Hes
SAP ERP
ACM
14 S#stem should support 11( &ree &ields per emplo#ee to support capture o&
additional emplo#ee in&ormation
Hes +here is
space
a"aila.le
to store
documents
= maCe
Annex B: Appendix 3B- Compliance Sheet
Page 79 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
notes= and
create
documents
and to
store them
per
emplo#ee
in the
'MS
12
Should support creation o& organisation structure to include @ocation=
'epartment and assigning emplo#ees to it Hes
SAP ERP
ACM
11( Possi.le to allocate emplo#ees to cost centers Hes
SAP ERP
ACM
111
Should support maintaining an emplo#ee histor# to include change in
assignments= promotions= trans&ers= pending issues etc Hes
SAP ERP
ACM
2 M+n*o7er B/d.e(,n.
$1
Should support planning &or manpo;er across all departments and cost
centers Hes
SAP ERP
ACM
$$
Should support automatic planning o& manpo;er .ased on #earl# re"enue
.udgets on .asis o& user de&ined rules +his planning should .e &or
- Eo and +#pe o& personnel
- Emplo#ees or Contract personnel
- SCills o& personnel Hes
SAP ERP
ACM
$3 +he s#stem should support ;orC&lo; .ased appro"al o& manpo;er .udgets Hes
SAP ERP
ACM
$)
Manpo;er planning should .e integrated ;ith Cost Centre and other le"els
o& Budgeting Hes
SAP ERP
ACM and
*% C!
$1 Should ha"e &acilit# to consolidate the manpo;er re,uirements Hes
SAP ERP
ACM
$11 'epartment ;ise Hes
SAP ERP
ACM
$1$ *unction ;ise Hes
SAP ERP
ACM
$13 7rade ;ise Hes
SAP ERP
ACM
$1) Pro&ile ;ise Hes
SAP ERP
ACM
$/
Should support ;hat-i& anal#sis tool &or increase or decrease in ;ages or
num.er emplo#ees to anal#6e the &inancial impact o& the same Hes
SAP ERP
ACM
& Re3r/,(2en(
31
Maintain personnel data.anC &or details o& candidates applied along ;ith
inter"ie; details Hes
SAP ERP
ACM and
e-
Recruitme
nt
3$ Should support recruitment through agencies Hes
SAP ERP
ACM and
e-
Recruitme
nt
3$1 +racC resume through agencies Hes
SAP ERP
ACM and
e-
Recruitme
nt
Annex B: Appendix 3B- Compliance Sheet
Page 80 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
3$$
%& recruited then create a lia.ilit# to pa# the agenc# .ased on an agreed
contract Hes
SAP ERP
ACM and
e-
Recruitme
nt
33 Should pro"ide &or maintaining a data.ase o& recruitment agencies Hes
SAP ERP
ACM and
e-
Recruitme
nt
3) Should .e possi.le to initiate recruitment process in"ol"ing &ollo;ing Hes
SAP ERP
ACM and
e-
Recruitme
nt
3)1 Recruitment portal 9possi.le to inter&ace ;ith the portal &or data exchange: Hes
SAP ERP
ACM and
e-
Recruitme
nt
3)$ Educational institutions Hes
SAP ERP
ACM and
e-
Recruitme
nt
3)3 %nternal recommendations / re&errals Hes
SAP ERP
ACM and
e-
Recruitme
nt
31 Should support preparation o& a recruitment plan outlining &ollo;ing Hes
SAP ERP
ACM and
e-
Recruitme
nt
311 'etails o& posts to .e &illed Hes
SAP ERP
ACM and
e-
Recruitme
nt
31$ Start date o& recruitment process Hes
SAP ERP
ACM and
e-
Recruitme
nt
313 Source9s: o& recruitment Hes
SAP ERP
ACM and
e-
Recruitme
nt
31) %n"ol"ement o& M7@ personnel in recruitment process Hes
SAP ERP
ACM and
e-
Recruitme
nt
3/
S#stem should support checCing o& ,uali&ications= experience= etc o&
internal sta&& .e&ore preparing an eternal recruitment plan Hes
SAP ERP
ACM and
e-
Recruitme
nt
Annex B: Appendix 3B- Compliance Sheet
Page 81 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
30
+he s#stem should support deduction in re,uirement o& manpo;er once the
manpo;er is recruited against a posted re,uirement Hes
SAP ERP
ACM and
e-
Recruitme
nt
34
Should support comparison o& manpo;er .udgeted "s manpo;er recruited
&or a particular period Hes
SAP ERP
ACM and
e-
Recruitme
nt
32
Should support ;orC&lo; .ased appro"al o& manpo;er re,uirements .ased
on .udgets Hes
SAP ERP
ACM and
e-
Recruitme
nt
31(
Should pro"ide &or de&ining multiple t#pes o& correspondence ;ith
applicant Hes
SAP ERP
ACM and
e-
Recruitme
nt
31(1 %nter"ie; schedule letters Hes
SAP ERP
ACM and
e-
Recruitme
nt
31($ Appointment letters Hes
SAP ERP
ACM and
e-
Recruitme
nt
31(3 Regret letters Hes
SAP ERP
ACM and
e-
Recruitme
nt
311 Should ha"e &acilit# to Ceep a tracC on the status o& recruitment acti"ities Hes
SAP ERP
ACM and
e-
Recruitme
nt
3111 Screening Hes
SAP ERP
ACM and
e-
Recruitme
nt
311$ %nter"ie;s Hes
SAP ERP
ACM and
e-
Recruitme
nt
3113 Selection Hes
SAP ERP
ACM and
e-
Recruitme
nt
311) Pa# pacCage negotiation Hes
SAP ERP
ACM and
e-
Recruitme
nt
Annex B: Appendix 3B- Compliance Sheet
Page 82 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
3111 Acceptance o& o&&er Hes
SAP ERP
ACM and
e-
Recruitme
nt
311/ >oining &acilities Hes
SAP ERP
ACM and
e-
Recruitme
nt
3110 Appointment Hes
SAP ERP
ACM and
e-
Recruitme
nt
3114 Eomination &orm Hes
SAP ERP
ACM and
e-
Recruitme
nt
3112 Medical test Hes
SAP ERP
ACM and
e-
Recruitme
nt
3111(
Should support ;orC&lo; .ased recruitment process in"ol"ing appro"als at
"arious -stages o& recruitment process Hes
SAP ERP
ACM and
e-
Recruitme
nt
31$ Should ha"e &eature to anal#se the histor# o& recruitment e"ents Hes
SAP ERP
ACM and
e-
Recruitme
nt
31$1 College/%nstitute/Agenc# Hes
SAP ERP
ACM and
e-
Recruitme
nt
31$$ Eo o& applications Hes
SAP ERP
ACM and
e-
Recruitme
nt
31$3 Eo o& candidates appeared Hes
SAP ERP
ACM and
e-
Recruitme
nt
31$) Eo o& candidates selected Hes
SAP ERP
ACM and
e-
Recruitme
nt
31$1 Eo o& candidates Boined Hes
SAP ERP
ACM and
e-
Recruitme
nt
Annex B: Appendix 3B- Compliance Sheet
Page 83 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
313
Should ha"e &acilit# to de&ine contract terms and generate Emplo#ment
Contract Hes
SAP ERP
ACM and
e-
Recruitme
nt
> Tr+,n,n.
)1 Should .e possi.le to prepare .udgets &or training Hes
SAP ERP
ACM
)$ Should support ;orC&lo; .ased appro"al o& training .udgets Hes
SAP ERP
ACM
)3 Should .e possi.le to de&ine minimum training hours &or emplo#ees Hes
SAP ERP
ACM
))
Should support de&inition o& standard / compulsor# trainings re,uired 9eg=
induction= .asic course: &or emplo#ees depending on the designation=
compan# and department Hes
SAP ERP
ACM
)1 Should .e possi.le to de&ine t#pes o& trainings Hes
SAP ERP
ACM
)11 +echnical training Hes
SAP ERP
ACM
)1$ Managerial training Hes
SAP ERP
ACM
)13 EngineersO training Hes
SAP ERP
ACM
)1) Sa&et# related training Hes
SAP ERP
ACM
)/
Should .e possi.le to de&ine codes &or training programs .ased on t#pe o&
training= area o& training= internal / external training Hes
SAP ERP
ACM
)0
Should .e possi.le to de&ine the master list o& training programs co"ering
&ollo;ing Hes
SAP ERP
ACM
)01 +raining code Hes
SAP ERP
ACM
)0$ +raining duration Hes
SAP ERP
ACM
)03 +arget audience / department Hes
SAP ERP
ACM
)0) @ist o& trainers 9internal / external: Hes
SAP ERP
ACM
)4 Should ha"e &acilit# to design training calendar Hes
SAP ERP
ACM
)41 +rainer Hes
SAP ERP
ACM
)4$ +rainee Hes
SAP ERP
ACM
)43 Courses Hes
SAP ERP
ACM
)4) +raining date Hes
SAP ERP
ACM
)41 +raining e"aluation criteria Hes
SAP ERP
ACM
)4/ +raining su.Bect Hes
SAP ERP
ACM
)40 Expenses Hes
SAP ERP
ACM
)44 Batches Hes
SAP ERP
ACM
)42 Emplo#ee per&ormance parameter Hes
SAP ERP
ACM
Annex B: Appendix 3B- Compliance Sheet
Page 84 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
)2
Should support allocating personnel &or training courses de&ined in the
training calendar Hes
SAP ERP
ACM
)1(
Should support selection o& personnel &or training .ased on present sCills=
impro"ement areas and pre"ious trainings taCen 97ap anal#sis: Hes
SAP ERP
ACM
)11
Should support identi&ication o& training needs &or each emplo#ee on a
#earl# .asis Hes
SAP ERP
ACM
)1$ Support capturing details o& training courses conducted as : Hes
SAP ERP
ACM
)1$1 Eames o& participants Hes
SAP ERP
ACM
)1$$ +raining su.Bect and description Hes
SAP ERP
ACM
)1$3 'uration o& training Hes
SAP ERP
ACM
)1$) *acult# in"ol"ed in imparting training Hes
SAP ERP
ACM
)1$1 Cost incurred in pro"ision o& training Hes
SAP ERP
ACM
)13 Monitor training taCen .# an emplo#ee &or a user de&ined period Hes
SAP ERP
ACM
)1) Monitor month-;ise .udgeted "s actual expenditure in training Hes
SAP ERP
ACM
)11
Should ha"e &acilit# to collect &eed.acC and anal#se e&&ecti"eness o& the
training Hes
SAP ERP
ACM
)1/
+he s#stem should support triggering o& training due date &or emplo#ees &or
recurring trainings 9re&resh trainings: Hes
SAP ERP
ACM
)10 Monitor training expenses .# emplo#ee= department or cost centre Hes
SAP ERP
ACM
)14
'e&ining a &rame;orC &or assessing .ene&its to emplo#ee a&ter training is
imparted Hes
SAP ERP
ACM
5 Per5or2+n3e +**r+,)+-
11
Should ha"e pro"ision to remind &or con&irmations a month .e&ore the
pro.ation period / training period ends Hes
SAP ERP
ACM
1$
Should .e possi.le to de&ine goals &or the organisation and departments to
arri"e at appraisal &rame;orC / parameters Hes
SAP ERP
ACM
13
S#stem should support de&inition o& appraisal parameters and &rame;orC
depending on
'epartment= 'esignation= Role and !thers Hes
SAP ERP
ACM
1)
Possi.le to de&ine <P%Os &or each emplo#ee and monitor the same during
the #ear Hes
SAP ERP
ACM
11
Should support de&inition o& appraisal &rame;orC in"ol"ing rating on
di&&erent parameters and doing mathematical computation to arri"e at a
&inal scores / ranCing &or emplo#ee Hes
SAP ERP
ACM
1/
Should support process o& sel& appraisal ;here emplo#ees ma# assess their
o;n per&ormance &or the per&ormance period Hes
SAP ERP
ACM
10
Should .e possi.le to de&ine the &re,uenc# 9#earl#= hal&-#earl#= ,uarterl#=
etc: o& per&ormance appraisal Hes
SAP ERP
ACM
14
Should ha"e &acilit# to tracC status o& per&ormance appraisal process 9%ssuing o&
appraisal &orms= Re"ie; o& per&ormance= Re"ision o& .ene&its= Appro"al o& the
appraisal= %ssuing increment letter= RanCing categor#= 8pdating re"ision in
pa#roll: Hes
SAP ERP
ACM
12 S#stem should support checCing &ollo;ing details as a part o& appraisal Hes
SAP ERP
ACM
121 Per&ormance grading Hes
SAP ERP
ACM
12$ Hears o& experience in the same grade Hes SAP ERP
Annex B: Appendix 3B- Compliance Sheet
Page 85 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
ACM
123 +raining undergone Hes
SAP ERP
ACM
11(
Possi.le to de&ine minimum #ears o& experience re,uired &or each grade
.e&ore promoting to next grade Hes
SAP ERP
ACM
111
+he s#stem should support ;orC&lo; .ased appraisal in"ol"ing multiple
rounds o& interactions / discussions / &inalisation Hes
SAP ERP
ACM
11$
S#stem should support de&inition o& all personnel ;ho ;ould e"aluate an
emplo#ee and the se,uence 9eg immediate superior &ollo;ed .# the Aead
o& 'epartment: o& appraisal Hes
SAP ERP
ACM
113
+he s#stem should capture the process o& &eed.acC and counseling .et;een
emplo#ees and respecti"e appraisers Hes
SAP ERP
ACM
11)
Should support entering a de"elopment plan &or emplo#ee at the end o&
appraisal process Hes
SAP ERP
ACM
111 Possi.le to monitor progress on the de"elopment plan &or each emplo#ee Hes
SAP ERP
ACM
11/
+he s#stem should support anal#sis o& department-;ise increase in cash
out&lo; in case o& increments Hes
SAP ERP
ACM
C Tr+0e- M+n+.e2en(
/1
Should allo; &or recording tra"el re,uisitions as per tra"el polic# ;ith the
&ollo;ing details Hes
SAP ERP
+ra"el
Managem
ent
/11 Emplo#ee Hes
SAP ERP
+ra"el
Managem
ent
/1$ *rom/+o= +ra"el 'ates and Mode o& +ra"el Hes
SAP ERP
+ra"el
Managem
ent
/13 ProBect Code Hes
SAP ERP
+ra"el
Managem
ent
/$
Should .e possi.le to de&ine the purpose o& tra"el 9eg +raining= Supplier
'e"elopment= Aolida#= etc: Hes
SAP ERP
+ra"el
Managem
ent
/3 Should support re,uisitions &or: Hes
SAP ERP
+ra"el
Managem
ent
/31 +ra"el +icCets Hes
SAP ERP
+ra"el
Managem
ent
/3$ -ehicles Hes
SAP ERP
+ra"el
Managem
ent
/33 Accommodation Hes
SAP ERP
+ra"el
Managem
ent
/) Should support a ;orC&lo; .ased authori6ation &or tra"el re,uisitions +he
authori6ing person should .e determined .ased on:
Hes SAP ERP
+ra"el
Annex B: Appendix 3B- Compliance Sheet
Page 86 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
Managem
ent
/)1 ProBect Code Hes
SAP ERP
+ra"el
Managem
ent
/)$ Emplo#ee= super"isor Hes
SAP ERP
+ra"el
Managem
ent
/1
Should allo; &or recording tra"el arrangements .ooCed against each tra"el
re,uisition Hes
SAP ERP
+ra"el
Managem
ent
//
Should allo; &or recording ad"ances &or tra"el against a re,uisition= a&ter
appro"al Hes
SAP ERP
+ra"el
Managem
ent
/0
Should allo; &or recording tra"el expense report once the tra"el is
completed Hes
SAP ERP
+ra"el
Managem
ent
/4 Should automaticall# account &or the tra"el expense report a&ter appro"al Hes
SAP ERP
+ra"el
Managem
ent
/2
Should .e integrated ;ith accounts pa#a.le &or creating lia.ilities against
each tra"el expense recorded in the tra"el expense report Hes
SAP ERP
+ra"el
Managem
ent
/1(
Should .e integrated ;ith ProBect Management &or recording tra"el related
expenses against the proBect Hes
SAP ERP
+ra"el
Managem
ent
/11 Should allo; &or &inal settlement o& a tra"el Hes
SAP ERP
+ra"el
Managem
ent
D T,2e +nd +((end+n3e
01
S#stem should capture lea"e entitlements &or di&&erent t#pes lea"es= &or
each emplo#ee depending on the emplo#ee pro&ile 9legal entit#=
designation= #ears o& ser"ice in compan# = etc: Hes
SAP ERP
ACM
0$
Should support to de&ine rules &or lea"e management &or short lea"es=
o"ertime= compensator# lea"es compan# ;ise or department ;ise Hes
SAP ERP
ACM
03
Should .e possi.le to de&ine hierarch# &or appro"al o& lea"e &or e"er#
emplo#ee Hes
SAP ERP
ACM
0) Should .e possi.le to appl# and tracC appro"al o& lea"e Hes
SAP ERP
ACM
01
Should ha"e integration ;ith external attendance registration s#stems &or
capturing time-in and time-out o& e"er# emplo#ee Hes
SAP ERP
ACM
0/ Should .e possi.le to de&ine the o&&ice timings per o&&ice location Hes
SAP ERP
ACM
00
Should .e possi.le to capture emplo#ee-;ise da#s o& attendance and lea"e
taCen details Hes
SAP ERP
ACM
04
Possi.le to generate report ;ith details o& o&&ice time &or each emplo#ee
9department-;ise: Hes
SAP ERP
ACM
041 @ate coming to o&&ice Hes
SAP ERP
ACM
Annex B: Appendix 3B- Compliance Sheet
Page 87 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
04$ @ate sitting Hes
SAP ERP
ACM
043 !"er time Hes
SAP ERP
ACM
02
Should .e possi.le to capture location ;here the emplo#ee ;as on dut# &or
e"er# da# o& presence marCed Hes
%n&ormatio
n &rom the
external
attendance
registratio
n s#stems
9integrated
into SAP
ERP
ACM: can
.e used to
locate an
emplo#ee?
s
;herea.o
uts &or the
da#
01(
Should .e possi.le to de&ine t#pes o& lea"es 9eg Annual lea"e= Medical
lea"e= etc: Hes
SAP ERP
ACM
011 Should ha"e &acilit# to tracC lea"e status o& emplo#ee Hes
SAP ERP
ACM
01$
Should ha"e integration ;ith pa#roll processing s#stem to trans&er data liCe
no o& da#s present in a month= o"ertime taCen= lea"es taCen= a.sent ;ithout
notice= etc &or the purpose o& computation o& salar# Hes
SAP ERP
ACM
F Se*+r+(,on
41 Should ha"e &acilit# to tracC status o& separation process Hes
SAP ERP
ACM
411 Su.mitting resignation letter Hes
SAP ERP
ACM
41$ Acceptance letter Hes
SAP ERP
ACM
413 Eotice period "alidation Hes
SAP ERP
ACM
41) Accounts settlement Hes
SAP ERP
ACM
411 %ssue o& experience certi&icate Hes
SAP ERP
ACM
4$
Capturing o& exit inter"ie; details +he details include
- 'ate o& exit inter"ie;
- Conducted .#
- <e# &indings in the Exit %nter"ie; Hes
SAP ERP
ACM
43
Should support checC o& return status o& material issued to emplo#ees &or
&inal clearance Hes
SAP ERP
ACM
4) Should support calculation o& amount due as End o& Ser"ice .ene&its Hes
SAP ERP
ACM
41 Pro"ide classi&ication o& separation due to Hes
SAP ERP
ACM
411 Resignation Hes
SAP ERP
ACM
41$ +erminal notice Hes
SAP ERP
ACM
413 'eath Hes
SAP ERP
ACM
Annex B: Appendix 3B- Compliance Sheet
Page 88 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
41) 'isciplinar# action Hes
SAP ERP
ACM
41/ Contractual terms Hes
SAP ERP
ACM
410 Retirement Hes
SAP ERP
ACM
9 'e+-(4 +nd S+5e(1
3ipro
shall
de"elop
the same
21
Report and in"estigate incidents o& inBur# and illness &or emplo#ees and
contractors Hes
2$
%nitiation o& correcti"e actions related to an incident Hes
23
@ogging o& &irst aid records and reports Hes
2)
Manage occupational inBur# and illness claims Hes
21
Report incidents in"ol"ing "ehicles and e,uipment Hes
2/
'etect and monitor ha6ardous conditions 9areas: and materials R exporting
them "ia an inter&ace &or &urther processing
Hes
20
Maintenance o& agent composition and in&ormation in a central data.ase Hes
24
%ntegration ;ith suppl# chain and AR modules Hes
22
Per&orm accident in"estigations= identi&ications= and recording Hes
21(
Support !SAA P!ccupational Sa&et# and Aealth ActQ = and sa&et#
regulator# reports
Hes
211
Maintain data.ase o& all MS'S9material sa&et# data sheet: sheets &or all
materials used
Hes
10
E2*-o1ee Se-5ESer0,3e
1(1
Re"ie; and maintain name= address= telephone num.er= etc= associated
;ith li&e e"ents
Hes SAP
ACM ESS
1($
Re"ie; or enroll in .ene&its &or open enrollment period Hes SAP
ACM ESS
1(3
Change .ene&its related to a li&e e"ent Hes SAP
ACM ESS
1()
-ie; pa# stu. in&o: gross pa#= other deductions= net pa#= pa# period= and
#ear-to-date totals
Hes SAP
ACM ESS
1(1
Maintain dependents and .ene&iciaries Hes SAP
ACM ESS
1(/
Maintain emergenc# contacts Hes SAP
ACM ESS
1(0
Re"ie; "acation and sicC da# .alances and su.mit lea"e re,uests Hes SAP
ACM ESS
1(4
Re"ie; and maintain .anC in&o &or direct deposit and reim.ursements Hes SAP
ACM ESS
1(2
Re"ie; and enter or su.mit expenses Hes SAP
ACM ESS
1(1(
Account &or time .ased on t#pe o& a.sence or attendance Hes SAP
ACM ESS
1(11
Choose and maintain personal pass;ords Hes SAP
ACM ESS
1(1$
Posting and updating resumes Hes SAP
ACM ESS
1(13
-ie; personal training histor# Hes SAP
ACM ESS
1(1)
Search &or a"aila.le courses .ased on topic= text= language= and location Hes SAP
ACM ESS
1(11
-ie; course calendars and details Hes SAP
ACM ESS
1(1/ Enroll in or cancel participation in courses Hes SAP
Annex B: Appendix 3B- Compliance Sheet
Page 89 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
ACM ESS
1(10
Re"ie; and maintain deduction in&ormation &or automatic .ill pa#ment
ser"ice
Hes SAP
ACM ESS
1(14
Re"ie; and maintain a Cno;ledge sharing diar# Hes SAP
ACM ESS
1.>.5 A))e( ,5e313-e M+n+.e2en(
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
1 Gener+-
11 Possi.le to de&ine 6ones / areas &or operations and maintenance Hes
SAP ERP
Plant
Maintenan
ce Master
'ata
1$ Associate &ollo;ing ;ith the de&ined 6ones / areas
1$1 !RM team responsi.le &or the 6one / area Hes
SAP ERP
Plant
Maintenan
ce Master
'ata
1$$ Control room num.er &or the 6one / area Hes
SAP ERP
Plant
Maintenan
ce Master
'ata
13 Possi.le to capture e,uipment details Hes
SAP ERP
Plant
Maintenan
ce Master
'ata
1)
Possi.le to marC sending o& communication to entities ;ith details o& the
e,uipment Hes
SAP ERP
Plant
Maintenan
ce 3orC
*lo;s
11 'e&ine categor# o& maintenance
111 'istri.ution net;orC Hes
SAP ERP
Plant
Maintenan
ce !rder
Parameter
s
11$ Consumer end 9PE= etc: Hes
SAP ERP
Plant
Maintenan
ce !rder
Parameter
s
113 Eet;orC station Hes
SAP ERP
Plant
Maintenan
ce !rder
Parameter
s
Annex B: Appendix 3B- Compliance Sheet
Page 90 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
11) !thers 9 please speci&# : Hes
SAP ERP
Plant
Maintenan
ce !rder
Parameter
s
1/ 'e&ine t#pe o& maintenance
1/1 Pre"enti"e maintenance Hes
SAP ERP
Plant
Maintenan
ce -
Pre"enti"e
Maintenan
ce
Managem
ent
1/$ BreaCdo;n maintenance Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent
1/3 Emergenc# maintenance Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent
10
A.ilit# to de&ine routine maintenance acti"ities &or each e,uipment ;ith
&ollo;ing characteristics
101 *re,uenc# Hes
SAP ERP
Plant
Maintenan
ce -
Strategies
o&
Maintenan
ce
10$ Calendar .ased schedule Hes
SAP ERP
Plant
Maintenan
ce -
Strategies
o&
Maintenan
ce
103 'etails o& maintenance to .e done Hes
SAP ERP
Plant
Maintenan
ce -
Pre"enti"e
Maintenan
ce
Planning
10) E,uipment / spares re,uired to undertaCe maintenance Hes SAP ERP
Plant
Maintenan
ce -
Pre"enti"e
Annex B: Appendix 3B- Compliance Sheet
Page 91 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
Maintenan
ce
Planning
101 Expected time re,uired &or maintenance acti"it# Hes
SAP ERP
Plant
Maintenan
ce -
Pre"enti"e
Maintenan
ce
Planning
14
A.ilit# to capture maintenance acti"ities recommended .# the
manu&acturer o& e,uipment Hes
SAP ERP
Plant
Maintenan
ce -
Maintenan
ce
Planning
R
Schedulin
g
12
*or all the maintenance acti"ities de&ined in the s#stem= de&ining clearances
re,uired &rom internal 9sa&et# department: / external agencies Hes
SAP ERP
3orC
Clearance
Managem
ent
11(
A.ilit# to de&ine teams ;ith maintenance responsi.ilit# associated ;ith
&ollo;ing
11(1 Categor# o& maintenance to .e carried out Hes
SAP ERP
Plant
Maintenan
ce -
Master
'ata o&
3orC
Centers
1($ Yone / area o& maintenance Hes
SAP ERP
Plant
Maintenan
ce -
Master
'ata
111 A.ilit# to de&ine operations sta&& &or each 6one / area Hes
SAP ERP
Plant
Maintenan
ce -
Master
'ata
11$
'e&inition o& contractors &or maintenance acti"ities ;ith &ollo;ing
attri.utes
11$1 Yone / area o& maintenance Hes
SAP ERP
Plant
Maintenan
ce -
Master
'ata
11$$ Categor# o& maintenance to .e carried out Hes SAP ERP
Plant
Maintenan
ce -
Master
Annex B: Appendix 3B- Compliance Sheet
Page 92 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
'ata o&
3orC
Centers
11$3 E,uipment 9maCe= e,uipment %': &or ;hich maintenance to .e done Hes
SAP ERP
Plant
Maintenan
ce !.Bect
@ists on
!rders
113
Should ha"e integration ;ith Contracts modules to capture data 9including
the rates &or ser"ices= etc: related to contractors &or maintenance ;orC Hes
SAP ERP
Plant
Maintenan
ce /
Materials
Managem
ent
Ser"ices
R
procureme
nt
2 A))e( 2+n+.e2en(
$1 Possi.le to de&ine uni,ue alpha-numeric asset code .ased on &ollo;ing
$11 Speci&ication o& e,uipment Hes
SAP ERP
Plant
Maintenan
ce -
Master
'ata
$1$ Model num.er= Capacit#= maCe Hes
SAP ERP
Plant
Maintenan
ce -
Master
'ata
$13 location o& installation Hes
SAP ERP
Plant
Maintenan
ce Master
'ata
$1) name R code o& manu&acturer 9"endor: Hes
SAP ERP
Plant
Maintenan
ce -
Master
'ata
$$ Possi.le to de&ine e,uipment asset master ;ith &ollo;ing details
$$1 Asset code Hes
SAP ERP
Plant
Maintenan
ce -
Master
'ata
$$$ Asset speci&ications Hes
SAP ERP
Plant
Maintenan
ce -
Master
'ata
Annex B: Appendix 3B- Compliance Sheet
Page 93 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
$$3 Material codes &or all mo"a.le/replacea.le parts ;ithin the e,uipment Hes
SAP ERP
Materials
Managem
ent -
Materials
Master
$$) Eo o& replacea.le / mo"a.le parts ;ithin the e,uipment Hes
SAP ERP
Plant
Maintenan
ce - Bill o&
Materials
$$1 Eame and code o& manu&acturer 9"endor: Hes
SAP ERP
Materials
Managem
ent -
Materials
Master
$$/ Spares re,uired &or the asset Hes
SAP ERP
Plant
Maintenan
ce - Bill o&
Materials
$3
Possi.le to inter&ace ;ith the material management module to map the
material code ;ith asset codes Hes
SAP ERP
is a &ull#
integrated
real time
solution
$)
Possi.le to integrate ;ith the in"entor# module to &ind spares a"aila.le &or
each asset Hes
SAP ERP
is a &ull#
integrated
real time
solution
$1
Possi.le to capture spares a"aila.le &ree o& cost &rom the manu&acturer
;ith the original e,uipment Hes
SAP ERP
Materials
Managem
ent / Plant
Maintenan
ce Bill !&
Materials
$/
Possi.le to integrate ;ith the Planning and engineering so&t;are &or
exchange o& data on e,uipment assets Hes
SAP
%ntegratio
n <its
A"aila.le
;ith
Planning
R
Engineeri
ng
So&t;ares
$0 Possi.le to integrate ;ith SCA'A &or exchange o& data on e,uipment
assets
Hes SAP ERP
PM - PCS
%nter&ace
linCs SAP
R
SCA'A
&or
trans&er o&
readings
and
in&ormatio
n across
Annex B: Appendix 3B- Compliance Sheet
Page 94 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
the s#stem
$01 Asset code and details Hes
SAP PM-
PCS
%nter&ace
$0$ speci&ication o& e,uipment Hes
SAP PM-
PCS
%nter&ace
$03 location o& installation Hes
SAP PM-
PCS
%nter&ace
$4 +racC mo"ement o& asset &rom one location to another Hes
SAP ERP
Plant
Maintenan
ce - 8sage
@ists
$2 Possi.le to trans&er the meter reading along ;ith the asset Hes
SAP ERP
Plant
Maintenan
ce -
Measuring
Points R
reading
trans&er
$1(
Possi.le to retain the asset health histor# ;hen it is mo"ed &rom one
location to another Hes
SAP ERP
Plant
Maintenan
ce -
!.Bect
%n&ormatio
n @ists R
usage lists
$11
Possi.le to integrate ;ith in"entor# and *inance modules to linC the asset
codes 9de&inition: and "alue o& the asset Hes
SAP ERP
is a &ull#
integrated
real time
solution
& O*er+(,on) 2+n+.e2en(
O*er+(,on) 6/d.e(
31 Possi.le to de&ine .udget &or operating costs &or each department Hes
SAP
operation
and
maintenan
ce cost
.udgeting
3$
Possi.le to de&ine the operations .udget under user de&ined categories liCe
maintenance= material= etc Hes
SAP
operation
and
maintenan
ce cost
.udgeting
33 Possi.le to de&ine operations .udget across dimensions liCe locations=
6ones / areas
Hes SAP
operation
and
maintenan
ce cost
.udgeting
Also can
.e done
.# asset
and
Annex B: Appendix 3B- Compliance Sheet
Page 95 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
&unction
location
3) Possi.le to ha"e ;orC&lo; .ased appro"al process &or .udget Hes
SAP
operation
and
maintenan
ce cost
.udgeting
and ;orC
&lo;
31 Monitor actual expenditure "s the .udget &or operating costs Hes
SAP
operation
and
maintenan
ce cost
.udgeting
Support
.# reports
and
dash.oard
s
E2er.en31 4+nd-,n.
3/ Register a call related to an emergenc# ;ith &ollo;ing details
3/1 Control room num.er Hes
CRM=
customer
ser"ice
and ;orC
orders
3/$ Caller details Hes
CRM=
customer
ser"ice
and ;orC
orders
3/3 'etails o& person recei"ing the call Hes
CRM=
customer
ser"ice
and ;orC
orders
3/) 'etails o& incident 9place= time= date: Hes
CRM=
customer
ser"ice
and ;orC
orders
30 Possi.le to generate a uni,ue call num.er &or e"er# call Hes
CRM=
customer
ser"ice
and ;orC
orders
34 Possi.le to &or;ard the call details to rele"ant personnel Hes
CRM=
customer
ser"ice
and ;orC
orders
32 Possi.le to capture time taCen to attend and resol"e the incident Hes
CRM=
customer
ser"ice
and ;orC
orders
31( Possi.le to capture &ollo;ing related to attending the incident Hes CRM=
customer
ser"ice
Annex B: Appendix 3B- Compliance Sheet
Page 96 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
and ;orC
orders
31(1 +ime taCen to resol"e Hes
CRM=
customer
ser"ice
and ;orC
orders
31($ Acti"ities done Hes
CRM=
customer
ser"ice
and ;orC
orders
31(3 Personnel ;ho attended Hes
CRM=
customer
ser"ice
and ;orC
orders
31() Material used Hes
CRM=
customer
ser"ice
and ;orC
orders
311
Possi.le to re,uest &or a .reaCdo;n maintenance in case o& large
.reaCdo;n Hes
CRM=
customer
ser"ice
and ;orC
orders
31$ Possi.le to monitor all the calls ;hich remain
31$1 8nattended Hes
CRM=
customer
ser"ice
and ;orC
orders
31$$ 8nresol"ed Hes
CRM=
customer
ser"ice
and ;orC
orders
313 Possi.le to anal#se the emergenc# calls
3131 *re,uentl# occurring emergencies Hes
CRM=
customer
ser"ice
and ;orC
orders
313$ Yone / area ;here emergencies are occurring &re,uentl# Hes
CRM=
customer
ser"ice
and ;orC
orders
3133
time / da# / period during the #ear ;hen emergenc# is occurring
&re,uentl# Hes
CRM=
customer
ser"ice
and ;orC
orders
Me(er re+d,n. / re3ord,n.
31) Possi.le to capture meter reading at consumer end ;ith &ollo;ing details
31)1 Meter reading "alue Hes CRM=
customer
ser"ice
Annex B: Appendix 3B- Compliance Sheet
Page 97 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
and ;orC
orders
31)$ Consumer num.er 9CRE num.er: Hes
CRM=
customer
ser"ice
and ;orC
orders
31)3 'ate and time o& meter reading Hes
CRM=
customer
ser"ice
and ;orC
orders
311
Possi.le to reset the meter reading 9the opening reading is di&&erent &rom
the pre"ious closing reading: ;ith authorit# Hes
CRM=
customer
ser"ice
and ;orC
orders
31/
Possi.le to highlight cases o& exception ;here meter reading is possi.l#
incorrect 9.ased on meter reading trends: Hes
CRM=
customer
ser"ice
and ;orC
orders
310
%ntegration ;ith the .illing module to trans&er meter reading data &or .illing
purpose at the &re,uenc# de&ined in the .illing module Hes
CRM=
customer
ser"ice
and ;orC
orders
314 Possi.le to capture meter readings ;ith &ollo;ing details
3141 Meter reading "alue Hes
CRM=
customer
ser"ice
and ;orC
orders
314$ 'ate and time o& meter reading Hes
CRM=
customer
ser"ice
and ;orC
orders
E9/,*2en( 2on,(or,n.
312
'e&inition o& &ollo;ing &or purpose o& monitoring 9.# taCing readings: o&
e,uipment operations Hes
SAP ERP
Plant
Maintenan
ce -
Condition
Monitorin
g
3121 E,uipment %' Hes
SAP ERP
Plant
Maintenan
ce -
Condition
Monitorin
g
312$
Parameters 9eg temperature= pressure= "i.ration= dispenser internal /
external: to .e monitored Hes
SAP ERP
Plant
Maintenan
ce -
Measuring
Points /
Parameter
s
Annex B: Appendix 3B- Compliance Sheet
Page 98 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
3123 *re,uenc# o& monitoring Hes
SAP ERP
Plant
Maintenan
ce -
Schedule
o&
Condition
Monitorin
g Plans
3$(
Possi.le to record the e,uipment monitoring parameters 9operations readings:
&or the de&ined &re,uenc# &or the e,uipment Hes
SAP ERP
Plant
Maintenan
ce -
Measurem
ent
Reading
@ists
3$1
Possi.le to inter&ace ;ith SCA'A s#stem 9;hich captures real time data
o& e,uipment: to get the operations readings Hes
SAP ERP
PM - PCS
%nter&ace
linCs SAP
R
SCA'A
&or
trans&er o&
readings
and
in&ormatio
n across
the s#stem
3$$ A.ilit# to undertaCe trend anal#sis &or o.ser"ing an# a.normalit# Hes
SAP ERP
Plant
Maintenan
ce
Measurem
ent Point
+rend
graphs
3$3
A.ilit# to use the monitoring data 9readings and trend: to pro"ide inputs to
&ollo;ing
3$31 E,uipment health histor# Hes
SAP ERP
Plant
Maintenan
ce
3$3$ Maintenance re,uirements &or the e,uipment Hes
SAP ERP
Plant
Maintenan
ce
D,)3onne3(,on
3$)
Possi.le to integrate ;ith the CRM / Billing module to consolidate
re,uests related to disconnection Hes
CRM and
Billing
3$1
Possi.le to prepare a schedule &or disconnection and appro"e the same
through a ;orC&lo; Hes
CRM and
Billing
8sing
;orC&lo;
3$/ Possi.le to input &ollo;ing ;here disconnection is achie"ed Hes
CRM and
Billing
3$/1 CRE num.er o& disconnection Hes
CRM and
Billing
3$/$ 'ate o& disconnection Hes CRM and
Annex B: Appendix 3B- Compliance Sheet
Page 99 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
Billing
3$/3 Agenc# / Personnel in"ol"ed in disconnection Hes
CRM and
Billing
3$/) Closing reading Hes
CRM and
Billing
3$/1 Reason &or disconnection Hes
CRM and
Billing
3$// 'isconnection charges Hes
CRM and
Billing
3$0
Possi.le to capture t#pe o& disconnection done 9permanent= temporar#=
non-pa#ment: Hes
CRM and
Billing
3$4
Possi.le to update the Billing module ;ith cases ;here disconnection is
achie"ed 9to stop .illing &or such consumers: Hes
CRM and
Billing
Re3onne3(,on
3$2
Possi.le to integrate ;ith the CRM /Billing module to consolidate re,uests
related to Reconnection Hes
CRM and
Billing
33(
Possi.le to prepare a schedule &or Reconnection and appro"e the same
through a ;orC&lo; Hes
CRM and
Billing
331 Possi.le to input &ollo;ing ;here Reconnection is achie"ed
3311 CRE num.er o& Reconnection Hes
CRM and
Billing
331$ 'ate o& Reconnection Hes
CRM and
Billing
3313 Personnel in"ol"ed in Reconnection Hes
CRM and
Billing
331) !pening reading Hes
CRM and
Billing
3311 Reason &or Reconnection and re,uest recei"ed &rom ;hich source
33$
Possi.le to capture t#pe Reconnection done 9permanent= temporar#= Eon-
pa#ment: Hes
CRM and
Billing
333
Possi.le to update the Billing module ;ith cases ;here Reconnection is
achie"ed 9to start .illing &or such consumers: Hes
CRM and
Billing
33) Possi.le to capture the charges &or Reconnection Hes
CRM and
Billing
Me(er D+2+.e / F+/-(1
331 Capturing meter &ault# Hes
CRM and
Billing
33/
Capturing meter damaged .# consumer and reco"er charges &rom
consumers Hes
CRM and
Billing
330 Replacement o& ne; Meter and reasons thereo& Hes
CRM and
Billing
P+(ro--,n.
334
Possi.le to plan a route &or patrolling at points liCe consumer site= 'RS=
etc Hes
CRM and
Billing
%ncluding
7%S
332 Possi.le to allocate sta&& &or executing the patrolling tasC Hes
CRM and
Billing
3)( Recording &indings o& each sta&& on completion o& patrolling Hes
CRM and
Billing
3)1
Possi.le to intimate rele"ant personnel to resol"e issues identi&ied during
patrolling Hes
CRM and
Billing
3)$ Possi.le to tracC actions taCen &or the issues Hes
CRM and
Billing
3)3 Possi.le to list issues ;hich are unresol"ed Hes
CRM and
Billing
A/d,(
Annex B: Appendix 3B- Compliance Sheet
Page 100 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
3)) Possi.le to de&ine the audit scope and plan
3))1 'ate o& audit Hes
CRM and
Audit
tracCing
3))$ Personnel in"ol"ed Hes
CRM and
Audit
tracCing
3))3 !utlet to .e audited Hes
CRM and
Audit
tracCing
3)1 Report on audit undertaCen Hes
CRM and
Audit
tracCing
3)11 Personnel in"ol"ed Hes
CRM and
Audit
tracCing
3)1$ *indings Hes
CRM and
Audit
tracCing
3)13 Actions to .e taCen &or resolution Hes
CRM and
Audit
tracCing
3)1) Responsi.le personnel &or actions Hes
CRM and
Audit
tracCing
3)/
Alert the rele"ant personnel a.out the tasCs to .e undertaCen &or resolution
o& issue identi&ied through audit Hes
CRM and
Audit
tracCing
3)0 +racing the action taCen on &indings .# Audit team Hes
CRM and
Audit
tracCing
> M+,n(en+n3e *-+nn,n.
)1
Possi.le to de&ine .udgets &or maintenance ;ith .reaC up in terms o&
&ollo;ing
)11 Material cost / consuma.les Hes
SAP ERP
Maintenan
ce Cost
Budgeting
/ SAP
*inancials
)1$ ContractorsO cost Hes
SAP ERP
Maintenan
ce Cost
Budgeting
/ SAP
*inancials
)13 Spares re,uired &or maintenance Hes
SAP ERP
Maintenan
ce Cost
Budgeting
/ SAP
*inancials
)1) !ther costs Hes
SAP ERP
Maintenan
ce Cost
Budgeting
/ SAP
*inancials
)$ Possi.le to de&ine separate maintenance .udget &or categories o&
maintenance and arri"e at an aggregate .udget
Hes SAP ERP
Maintenan
Annex B: Appendix 3B- Compliance Sheet
Page 101 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
ce Cost
Budgeting
/ SAP
*inancials
)3 Preparation o& maintenance schedule .ased on &ollo;ing
)31 Maintenance schedule recommended .# the manu&acturer Hes
SAP ERP
Plant
Maintenan
ce -
Maintenan
ce
Planning
R
Schedulin
g
)3$ Aistor# o& e,uipment health Hes
SAP ERP
Plant
Maintenan
ce -
!.Bect
%n&ormatio
n @ist R
%n&ormatio
n S#stems
)33 Maintenance acti"ities ;hich are pending / not completed Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder @ist
*unctions
)3) Hears since commissioning ;as done 9&or domestic consumers: Hes
SAP ERP
Plant
Maintenan
ce
%n&ormatio
n S#stems
))
Possi.le to prepare maintenance plan annuall# ;ith details a"aila.le &or
monthl# and ;eeCl# plan +he maintenance plan should co"er &ollo;ing
))1 'etails o& maintenance acti"it# to .e carried out Hes
SAP ERP
Plant
Maintenan
ce -
Maintenan
ce
Planning
R
Schedulin
g
))$ %n"ol"ed personnel / 'epartment / Contractor Hes
SAP ERP
Plant
Maintenan
ce -
Maintenan
ce
Planning
R
Schedulin
g
))3 'ate o& maintenance Hes SAP ERP
Plant
Annex B: Appendix 3B- Compliance Sheet
Page 102 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
Maintenan
ce -
Maintenan
ce
Planning
R
Schedulin
g
))) Estimated time re,uired &or maintenance acti"it# Hes
SAP ERP
Plant
Maintenan
ce -
Maintenan
ce
Planning
R
Schedulin
g
)1 Possi.le to prepare a ;orC order &or maintenance identi&#ing &ollo;ing
)11 Personnel to undertaCe maintenance Bo. Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent
)1$ E,uipment / areas to .e co"ered &or maintenance Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent
)13 Spares re,uired &or maintenance Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent
)1) 'ate and time o& maintenance Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent
)1/ All appro"als re,uired &or carr#ing out maintenance Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent R
3orC
*lo;s
5 M+,n(en+n3e e@e3/(,on
11 Possi.le to electronicall# intimate di&&erent departments &or taCing
clearances .e&ore undertaCing maintenance Bo.
Hes SAP ERP
Plant
Maintenan
Annex B: Appendix 3B- Compliance Sheet
Page 103 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
ce R
3orC
*lo;s
1$
%ntimating *E3A personnel and other agencies .e&ore undertaCing
maintenance Bo. Hes
SAP ERP
Plant
Maintenan
ce R
3orC
*lo;s
13 Possi.le to +ag an e,uipment ;hen taCen &or maintenance Hes
SAP
3orC
Clearance
Managem
ent
1) Possi.le to input a report on maintenance Hes
SAP ERP
Plant
Maintenan
ce
Eoti&icatio
ns
1)1 E,uipment / Consumer premise o& ;hich / location Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent
1)$ Material used Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent
1)3 Acti"it# summar# Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent
1)) +ime taCen Hes
SAP ERP
Plant
Maintenan
ce
Con&irmat
ions o&
3orC
!rders
1)1 Personnel / Contractor in"ol"ed in maintenance acti"ities Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent
Capacities
11 *or .reaCdo;n maintenance= &ollo;ing should .e supported
111 Cause o& .reaCdo;n Hes SAP ERP
Plant
Maintenan
Annex B: Appendix 3B- Compliance Sheet
Page 104 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
ce
Eoti&icatio
ns
11$ 'amage caused .# .reaCdo;n Hes
SAP ERP
Plant
Maintenan
ce
Eoti&icatio
ns
1/
%n case o& cali.ration as a maintenance acti"it#= updating the cali.ration
details &or the instrument Hes
SAP ERP
Plant
Maintenan
ce -
Planned
Maintenan
ce /
Measuring
Points
10
%n case o& change o& meter as a part o& maintenance acti"it#= the Billing
department should .e alerted a.out the same Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent R
3orC
&lo;s
14 8pdate the e,uipment histor# ;ith maintenance acti"ities Hes
SAP ERP
Plant
Maintenan
ce
%n&ormatio
n
S#stems =
!.Bect
%n&ormatio
n @ists R
8sage
@ists
12
Capture extent o& ser"ices pro"ided .# each contractor / "endor during a
user de&ined period
121 Man-hours Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent R
Ser"ice
Entr#
Sheets
12$ Eum.er o& acti"ities carried out Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent R
Ser"ice
Entr#
Sheets
Annex B: Appendix 3B- Compliance Sheet
Page 105 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
123 E,uipment 9%'= speci&ications R location: on ;hich maintenance ;as done Hes
SAP ERP
Plant
Maintenan
ce - 3orC
!rder
Managem
ent
11(
Possi.le to update the annual / monthl# / ;eeCl# maintenance plan ;ith
details o& maintenance completed Hes
SAP ERP
Plant
Maintenan
ce -
Maintenan
ce
planning
R
execution
111
Possi.le to integrate ;ith the Contracts module to de&ine mechanism &or
pa#ment to contractors
1111 Based on man-hour rate Hes
SAP ERP
Plant
Maintenan
ce /
Materials
Managem
ent
Ser"ice
Contracts
111$ *ixed charges monthl# / annual Hes
SAP ERP
Plant
Maintenan
ce /
Materials
Managem
ent
Ser"ice
Contracts
1113 *ree ser"ices as a part o& AMC &or &irst #ear Hes
SAP ERP
Plant
Maintenan
ce /
Materials
Managem
ent
Ser"ice
Contracts
11$
Calculate costs incurred &or maintenance ;ith .reaC up in terms o&
&ollo;ing
11$1 material cost Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent R
%n&ormatio
n S#stem
Reports
11$$ contractorsO cost Hes SAP ERP
Plant
Maintenan
ce 3orC
Annex B: Appendix 3B- Compliance Sheet
Page 106 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
!rder
Managem
ent R
%n&ormatio
n S#stem
Reports
11$3 other costs Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent R
%n&ormatio
n S#stem
Reports
11$) Spares re,uired &or maintenance Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent R
%n&ormatio
n S#stem
Reports
11$1 cost incurred at ;hich cost centre Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent R
%n&ormatio
n S#stem
Reports
11$/ cost incurred at ;hich location Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent R
%n&ormatio
n S#stem
Reports
113
Possi.le to monitor .udgeted "s actual cost incurred in maintenance &or a
user de&ined period Hes
SAP ERP
Plant
Maintenan
ce 3orC
!rder
Managem
ent R
%n&ormatio
n S#stem
Reports
11) Possi.le to generate a report on &re,uentl# occurring .reaCdo;n &or each
asset
Hes SAP ERP
Plant
Maintenan
ce
%n&ormatio
Annex B: Appendix 3B- Compliance Sheet
Page 107 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
n S#stem
R @ist
Reports
C E9/,*2en( 4e+-(4 2+n+.e2en(
/1
Possi.le to de&ine parameters 9eg "i.rations= temperature= running hours=
&ailures= etc ;hich are monitored: &or each asset / e,uipment that de&ine
its health Hes
SAP ERP
Plant
Maintenan
ce -
Measuring
Points R
Condition
ed Based
Maintenan
ce
Planning
/$ Possi.le to anal#6e the health data to identi&# &ollo;ing
/$1 Mean time .e&ore &ailure Hes
SAP ERP
Plant
Maintenan
ce
%n&ormatio
n S#stem
/$$ A"erage running hours per period 9da#= month: Hes
SAP ERP
Plant
Maintenan
ce
%n&ormatio
n S#stem
/$3 A"erage hours o& operations .e&ore maintenance re,uired Hes
SAP ERP
Plant
Maintenan
ce
%n&ormatio
n S#stem
/3
Possi.le to maintain historical health data &or e,uipment &or user de&ined
time period Hes
SAP ERP
Plant
Maintenan
ce
%n&ormatio
n S#stem
R 8sage
@ists
/) Possi.le to summaries the health data .#
/)1 Manu&acturer Hes
SAP ERP
Plant
Maintenan
ce /
Business
%ntelligenc
e Reports
/)$ @ocation Hes
SAP ERP
Plant
Maintenan
ce /
Business
%ntelligenc
e Reports
Annex B: Appendix 3B- Compliance Sheet
Page 108 of 89
1.>.C Per5or2+n3e M+n+.e2en( ;B/),ne)) In(e--,.en3e<
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
1 Re*or() +nd A/er,e)
11 Real-time reports accessing multiple data stores Hes
SAP-
Business
3arehous
e
1$ 3e.-,ueries Hes
SAP-
Business
3arehous
e
13 Ad-hoc ,ueries Hes
SAP-
Business
3arehous
e
1) %nteracti"e data exploration ;ith anal#tics Hes
SAP-
Business
3arehous
e
11 %ntegration o& ,ueries/reports ;ith 'esCtop tools such as Excel Hes
SAP-
Business
3arehous
e
1/ Support tree-st#le structure to logicall# organi6e data Hes
SAP-
Business
3arehous
e
10 Com.ine multiple reports into a single report/dash.oard Hes
SAP-
Business
3arehous
e
14 Supports graphical inter&ace to a"oid complex languages Hes
SAP-
Business
3arehous
e
12 Re*or( A33e)),6,-,(1 In3-/d,n.
121 Re$l time re6orts $ccess o6er$tion$l )$t$ stores
12$ @ener$tes re6orts $utom$tic$ll#
123 We+ Auer#
12) A)1(oc Aueries
121 Column1+$se) in)exin: for f$ster )$t$ retrie'in:
12/ B$'i:$tes $ll connecte) rel$tion$l )$t$+$ses
120 nter$cti'e )$t$ ex6lor$tion 4it( $n$l#tics
124 Des>to6 interf$ce to $)'$nce) $n$l#tics
122 ,ulti6le )$t$ sources $n) 6l$tforms
121( Accesses )elimite) A!C files $n) Fixe) A!C
1211 !c(e)ules inform$tion $lerts +$se) on s6ecifie) con)itions
121$ Re$l time $ccess to o6er$tion$l )$t$
1213 Re6ort )rill t(rou:( from /3AP cu+es
121) Em+e))e) 6ro)uction re6ort 4riters
1211 2$tc( 6ro)uction $n) )istri+ution of re6orts
121/ Com+ines multi6le re6orts into $ sin:le Cre6ort )$s(+o$r)C
1210 Ex6orts re6orts to ot(er form$ts 7 6le$se )efine ex6ort form$t 8
1214 nte:r$tes 4it( 3
r)
P$rt# ;D,3 )e'elo6ment tools
1212 @r$6(ic$l interf$ce $'oi)s com6lex l$n:u$:es% suc( $s C or .$'$
Annex B: Appendix 3B- Compliance Sheet
Page 109 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
2 An+-1(,3)
$1 Supports predicti"e modeling techni,ues such as: Hes
SAP-
Business
3arehous
e
$11 Regression algorithm Hes
SAP-
Business
3arehous
e
$1$ Scoring Hes
SAP-
Business
3arehous
e
$13 Classi&ication Hes
SAP-
Business
3arehous
e
$1) 7roupings Hes
SAP-
Business
3arehous
e
$11 Clustering Hes
SAP-
Business
3arehous
e
$1/ -aria.le contri.ution Hes
SAP-
Business
3arehous
e
$10 +ime series anal#ses predicts patterns and trends in data o"er time
$14
Association rules identi&ies patterns in transaction data &or descri.ing
;hich e"ents &re,uentl# occur together
$12
Consistent coder automaticall# &ills in missing "alues R detects out o&
range data
$11( Se,uence coder aggregates e"ents into a series o& transitions
$111 E"ent log aggregates e"ents into periods o& time
$11$ Segmentation
$$ Supports time-series anal#sis patterns and plots trends o"er time
Hes SAP-
Business
3arehous
e
$3 Supports *orecasting
Hes SAP-
Business
3arehous
e
& Wor85-o7
31 Represents complex processes that are comprised o& su.-processes
Racti"ities
Ees
SAP-
Eet;ea"er
3$ Processes can .e de&ined or mapped into the s#stem
Ees
SAP-
Eet;ea"er
33 7raphicall# portra#s .usiness processes and acti"ities
Ees
SAP-
Eet;ea"er
3) Shares acti"ities and su.-processes .et;een processes
Ees
SAP-
Eet;ea"er
31 Reuses an acti"it# alread# de&ined in the process ;ithout ha"ing to de&ine
it againJ
Ees
SAP-
Eet;ea"er
3/ 'e&ines a.solute or relati"e dates ;hen acti"ities or ;orC-items must .e
completed
Ees
SAP-
Eet;ea"er
Annex B: Appendix 3B- Compliance Sheet
Page 110 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
30 'e&ines a.solute or relati"e dates ;hen acti"ities or ;orC-items must .e
completed
34 Schedules tasCs to start automaticall# at a speci&ied time
Ees
SAP-
Eet;ea"er
32 +erminates a ;orC&lo; in a process= .ased on user pri"ileges securit#
Ees
SAP-
Eet;ea"er
31( Suspends or resumes a ;orC&lo; in process R speci&ies inacti"e periods
Ees
SAP-
Eet;ea"er
311 Processes to ha"e multiple points and end at an# end point
Ees
SAP-
Eet;ea"er
31$ 'ispla#s decision logic using text= the .ranch concept= or a decision icon
on the process map
Ees
SAP-
Eet;ea"er
313 Speci&ies note 9acti"it#: properties at design time
Ees
SAP-
Eet;ea"er
31) 'ispla#s the path tra"eled .et;een acti"ities 9color change:
Ees
SAP-
Eet;ea"er
311 Supplies acti"it# and tasC names
Ees
SAP-
Eet;ea"er
31/ -ie;s o"erall status and displa# acti"e node 9acti"it#:
Ees
SAP-
Eet;ea"er
310 Support de&inition o& Resources R Roles
Ees
SAP-
Eet;ea"er
314 Support de&inition o& Rules and Routing
Ees
SAP-
Eet;ea"er
312 Support de&inition o& 5ueues R 3orC @ists
Ees
SAP-
Eet;ea"er
3$( Support de&inition o& +riggers
Ees
SAP-
Eet;ea"er
3$1 Supports scheduling
Ees
SAP-
Eet;ea"er
> D+(+ In(e.r+(,on
)1 Aas de&ined tools &or E+@ &rom transaction data .ases Hes SAP-
Business
3arehous
e
)$ Aas .uilt-in tools to &acilitate data cleansing and trans&ormation Hes SAP-
Business
3arehous
e
)3 Supports 'ata Matching and Consolidation Hes SAP-
Business
3arehous
e
)) Supports de&inition o& metadata Hes SAP-
Business
3arehous
e
)1 Concurrent processing o& multiple source data streams= ;ithout ;riting
procedures
)/ E"ent-.ased change data capture
)0 BulC data mo"ement
)4 Explores ra; data in disparate s#stems to unco"er relationships and
discrepancies .et;een and ;ithin data sets
)2 Components that can .e used to ;orC around the &ile si6e or plat&orm
limitations
)1( 8pdates data capture and loads onl# changed records into the data source
Annex B: Appendix 3B- Compliance Sheet
Page 111 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
)11 Automaticall# generates data extract programs
)1$ Automatic updates &or slo;l# changing dimensions
1.>.D Te34n,3+- Re9/,re2en()
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
1 So-/(,on +r34,(e3(/re +nd ,n(e.r+(,on
11 Should support application deplo#ment in"ol"ing
111 Centrali6ed architecture Hes
11$ 'ecentrali6ed architecture Hes
113 'istri.ution architecture Hes
1$
Should support deplo#ing application components at local locations to
continue operations in case o& 3AE linC &ailure Hes
Can .e
deplo#ed
this ;a#
.ut
su.Bect to
design and
cost
constraints

13
Should .e possi.le to access application &rom remote location 9Remote
o&&ice = Remote users = please explain : Hes
Bro;ser=
Mo.ile
1)
Should support storing / replicating data related to critical &unctions at the
local locations to support &unctioning at .ranches in case o& 3AE linC
&ailure Hes
Can .e
deplo#ed
this ;a#
.ut
su.Bect to
design and
cost
constraints
11
Should .e a.le to integrate ;ith B3= 'SS and E%S s/; ;ithout con"ersion
o& 'ata Hes
Sap is
&ull#
integrated
1/ Should support ;orC&lo; .ased routing o& transactions according to user-
de&ined rules Pro"ide details a.out &unctionalit# pro"ided in.uilt or through
external pacCage / inter&ace
Hes
*ull#
integrated
10 Support &or data exchange .et;een modules using
101 Messaging Hes
10$ S#stem calls Hes
103 Application &unction calls Hes
10) An# other speci&# Hes
Standard
;e
ser"ices
&unctionali
t# .ased
on NM@=
pre.uilt
connectors

14 Support selecti"e export / import o& data in the &ollo;ing &ormats:


141 ASC%% Hes
14$ +ext Hes
Annex B: Appendix 3B- Compliance Sheet
Page 112 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
143 *ormatted Hes
14) &rom Microso&t Excel and 'A+ &iles Hes
141 8n&ormatted Hes But
con"ersio
n to
internal
&ormats
needed
12 A"aila.ilit# o& an# o& the &ollo;ing &or inter&aces &or external data
exchange
121 AP%s Hes
12$ M!Ms Hes
123 RPC Hes
12) An# other please speci&#
11( %n case o& an# o& the message .ased mechanisms= does the s#stem integrate
;ith:
11(1 M5 Series Hes 8sing ;e.
Ser"ices
Standards
Some
con&igurat
ion ;ill .e
needed
11($ MS M5 Hes 8sing ;e.
Ser"ices
Standards
Some
con&igurat
ion ;ill .e
needed
11(3 +i.co Acti"e Enterprise Hes 8sing ;e.
Ser"ices
Standards
Some
con&igurat
ion ;ill .e
needed
11() !thers 9Please Speci&#:
111 Should pro"ide DnD le"els in ;orC&lo; .ased routing o& transactions &or
di&&erent &unctions
Hes
Eet3ea"e
r BPM=
Eet3ea"e
r P%
11$
Should .e a.le to integration / inter&ace ;ith other pacCages ;ithout
duplication o& 'ata Hes
Eet3ea"e
r P%
113
Should support messaging solutions ;ith integration ;ith
MS Exchange Ser"er and Contact Centre 9SMS= &ax= etc: Hes
Eet3ea"e
r P%
11) A"aila.ilit# o& source code ;ith the application Hes
111 Possi.le to integrate ;ith &ollo;ing other so&t;are?s
1111 SCA'A Hes
@i&eC#cle
'ata
Managem
ent
111$ 7%S Hes
Eet3ea"e
r P%
1113 P!S s#stem Hes
Eet3ea"e
r P%
111) External data.ases 9eg oil prices= compan#-;ise car sales: Hes
1111 Scanned image storage and retrie"al applications Eet3ea"e
Annex B: Appendix 3B- Compliance Sheet
Page 113 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
r <M
111/ AutoCA' Hes
@i&eC#cle
'ata
Managem
ent
1110 Mapin&o Hes
8sing ;e.
Ser"ices
Standards
Some
con&igurat
ion ;ill .e
needed
1114 MS proBect / Prima"era Hes
@i&eC#cle
'ata
Managem
ent
1112a Contact Center Hes
Eet3ea"e
r P%
1112. 'MS Hes
@i&eC#cle
'ata
Managem
ent= <M
1112c MS !&&ice Hes
@i&eC#cle
'ata
Managem
ent= <M=
'8E+
11/
Possi.le to integrate ;ith *E3A ;e.site to disseminate in&ormation to
customers as : Hes
11/1 Bill paid / pending Hes
Enterprise
Portal
11/$ Consumption o& gas Hes
Enterprise
Portal
2 Te34no-o.1 *-+(5or2 +nd OS 3+*+6,-,(,e)E We6 B+)ed So-/(,on
$1
Should utili6e Multi processor / Parallel Processing / Multi-+hreading o&
the !S Hes
SAP
Eet3ea"e
r Plat&orm
$$ Should pro"ide &or Automated BacCup to o&&-peaC hours / !nline BacCups Hes
!&&line
and
!nline
.acCups
strategies
can .e
applied
$3 Pro"ide menu-dri"en 78% &ront-end &or !S Hes SAP 78%
$) Support load .alancing .et;een
$)1 Application ser"er Hes
AS.jpg
Part o&
architectur
e
$)$ 'ata.ase ser"er Hes
Part o&
architectur
e
$1
Should ena.le automatic scheduling o& Bo. to reduce load during peaC load
hours Hes
$/ Should support Automated tasCs as part o& Bo. scheduler Hes
$0 Pro"ide all .acCup and restore/reco"er# Capa.ilities 9&or losses= Hes
Annex B: Appendix 3B- Compliance Sheet
Page 114 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
corruption/damage U etc: as ;ell as the a.ilit# to &lash.acC to pre"ious
timestamp or .e&ore drop
$4 Please pro"ide details o& !S supported .# the applications Hes
& Se3/r,(1
31 Should pro"ide authentication at the &ollo;ing le"els:
311 8ser le"el Hes
31$ Application le"el Hes
313 Menu le"el Hes
31) *ile le"el Hes
311 Record le"el Hes
31/ *ield le"el Hes
310 !peration le"el 9add= change= delete: Hes
314 +erminal Hes
312 S#stem Module Hes
311( Master *ile Hes
3111 +ime o& da# and da# Hes
+ime o&
da# is
stamped
on
transactio
n
311$ Screen or &ield Hes
3113 *unction per&ormed
Hes
311) Authorit# le"els .ased on amounts
Hes Hes as
part o&
standard
;orC&lo;s

3$ Support &acilit# to allo; the de&ining o& the pass;ord construct


Hes
3$1 Eum.er o& characters and the complex pass;ord 9 explain:
Hes
Rules can
.e de&ined
and
en&orced
.# the
s#stem
33 Support de&ining user acti"it# 9on transactions: access to .e .ased on the
&ollo;ing and not limited to:
331 %nput
Hes
33$ Aold Hes
333 Modi&# Hes
33) 'elete Hes
331 Authori6e Hes
33/ Re"erse Hes Re"erse is
onl# .#
adding a
cancelling
transactio
n
330 -ie;/'ispla#
Hes
Annex B: Appendix 3B- Compliance Sheet
Page 115 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
334 Print
Hes
3) Support de&inition o& group pass;ords 9eg groups I s#stem administrator=
ProBects= Contractor= etc: ;ith ;hich certain &unctions / Bo. descriptions
are associated
Hes
31 Support storage o& pass;ord= in the data.ase= in encr#pted &orm Hes
3/
Possi.le to de&ine external users 9&rom outside compan#: ;ith access
rights and authentication as descri.ed a.o"e Hes
30
S#stem should support authentication &rom local ser"er in case o& 3AE
&ailure and local application access +he access rights de&ined centrall#
should also .e "alid in case o& local operations
34
Pro"ide a.ilit# to locC entr# screen a&ter a user-speci&ied num.er o&
incorrect pass;ord attempts Hes
32 Should log all update transactions in a secure audit trail &ile Hes
31(
Should pro"ide &or re,uired changes to user pass;ords .ased on a user-
speci&ied period o& time
Hes
311 Report attempts o& unauthori6ed s#stem access or use
Hes
31$
Pro"ide the a.ilit# to de&ine an access categor# relating to groups o& users
9eg= mem.ers o& a department or management class:
Hes
313 Pro"ide &or data encr#ption ;hen transmitted o"er net;orC
Hes
31)
Should pro"ide a &acilit# to automaticall# logout the user i& the s#stem is
inacti"e &or more than a speci&ied period o& time
Hes
311
+he s#stem should support automatic logout in case o& disconnection o&
user &rom the application ser"er
Hes
31/
+he s#stem should support de&inition o& access rights &or online a"aila.le
reports
Hes
> Tr+n)+3(,on o..,n. +nd Re3o0er1
)1
Pro"ide clear audit trails o& all transactions &rom source data entr# through
summari6ation at higher le"els or integration ;ith other application
s#stems Audit trail in&ormation should include .e&ore and a&ter images=
and the date= time and identi&ication o& the person maCing the entr# Hes
All state
changes in
data a
&ull#
logged
;ith all
data
re,uired
here
)$
Audit trail should highlight the entries made .# accessing the s#stem
through dial-in or through %nternet Hes
+rigger is
data
change
regardless
o& access
path used
)3
Pro"ide option to ena.le/disa.le audit trail o& an# speci&ied transaction
;ith all the a.o"e details 9.e&ore and a&ter images= date= time= person -
etc: Hes
)) Pro"ide on-line in,uir# to .oth status in&ormation and detail transactions Hes
)1
S#stem should support s;itching to alternate/stand.# ser"er to pro"ide
uninterrupted a"aila.ilit# Hes
)/
Branch accessing applications / data &rom central ser"er should pro"ide
and indication o& 3AE linC a"aila.ilit# status
Eet;orC
design
status
)0
+he s#stem should maintain transaction integrit# in case o& 3AE &ailure
;hile the transaction is under execution at the accessing .ranch Hes
)4 Pro"ide transaction logs to assist in reco"er# o& data or &iles Hes Sap
supports
Annex B: Appendix 3B- Compliance Sheet
Page 116 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
&ull
roll.acC
capa.ilit#
%ncomplet
e
transactio
ns are
automatic
all# rolled
.acC to
the
pre"ious
state
)2
Pro"ide on-line access to audit trail in&ormation including terminal operator %'=
time= date= re"ised amount= and .e&ore R a&ter update and transaction t#pes
results 9insert= updates= delete etc: Hes
)1(
Allo; "alidation rules to .e changed easil# .# the user ;ithout program
changes Hes
Business
"alidation
rules are
not
usuall#
put in
control o&
users
Such
changes
re,uire a
&ormal
appro"al
process=
testing
and
promotion
as part o&
the s#stem
control
)11
+he S#stem should accept/reBect transactions on the .asis o& master &ile
"alues 9eg Account Code= ProBect code etc: Hes
SAP does
this in real
time to
a"oid later
issues
!nl# &ull#
"alidated
transactio
ns are
entered
into the
s#stem
)1$ Easil# correct data entr# errors ;ithin a .atch Hes
Sap uses
"er# little
.atch
processing
3here it
is done= an
error list is
generated
&or repair
)13 +he s#stem should support reco"er# o& application so&t;are in case o&
damage
Hes *ull
reco"er#
.acC to
last
Annex B: Appendix 3B- Compliance Sheet
Page 117 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
complete
transactio
n is
supported
5 D+(+ )(or+.e
11
Pro"ide details o& data.ases supported .# the s#stem including )et$ile)
)$t$+$se clusterin:Fmirrorin:Fre6lic$tion= please speci&# Hes
SAP
supports
all
common
data.ases
including
MS S5@
ser"er=
Max'B=
!racle
SAP
supports
mirroring=
clustering
and
replication
.ut these
are a
&actor o&
ser"er and
net;orC
design
1$
!perating s#stem supported .# 'ata.ase ser"er
8nix= 3indo;s= @inux = please speci&# Hes
All
supported
13
Monitor on-line &ile capacit# control &or master and transaction &iles +he 'BA
to .e noti&ied ;hen a &ile is approaching capacit# Hes
Sap
includes
9at no
cost: the
Solution
manager
tool ;hich
allo;s
online
monitorin
g o& all
aspects o&
s#stem
operation
&rom .oth
an
applicatio
n and
data.ase
perspecti"
e
1) Should .e supported on !'BC compliant 'ata.ases Hes
11
Should .e possi.le to support pooling o& multiple data.ase connections
;hen the load is high Hes
Sap
supports
load
.alancing
to ensure
response
times
1/ Automatic expansion o& &ile ;hen approaching limits o& usage Hes
Annex B: Appendix 3B- Compliance Sheet
Page 118 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
10
Pro"ide multi-user operations do;n to the program le"el so that man#
people ma# access the same &iles and programs at the same time Hes
SAP
supports
&ile
locCing %&
a user has
a &ile
locCed &or
editing
other
users are
read onl#
till it is
checCed
in +his is
done to
include
integrit#
14
Allo; seamless data exchange and automatic update o& data ;ithin the
su.s#stems o& the same pacCage Hes
SAp onl#
deli"ers
&ull#
integrated
processes
12 Should pro"ide a comprehensi"e data dictionar# Hes
11(
Should pro"ide &or online data access &or a period o& 3 &inancial #ears and
up to 1( #ears o& historical data in some summari6ed &ormat Pro"ide
details Hes
Retention
and
o&&line
.acCup
strateg# is
user
de&ined
C Ed,() +nd Con(ro-)
/1 All su.-modules o& the pacCage should use the same master &iles online Hes
/$ Maintain all master &iles= ta.les and descripti"e transaction &ields on-line
Hes
All
transactio
ns are
done in
real-time
/3 Pro"ide report accurac# such that all reports pro"ide summar# totals
regardless o& rounding &actors
Hes
/) Should pro"ide &or a consistent screen &ormat across all modules
Hes
/1 Should pro"ide &or changing &ield la.els to suit *E3AOs terminolog#
Hes
// Should pro"ide &or templates &or rapid data entr# and "alidations
Hes
/0 Should pro"ide &or replication o& transactions &or reduced data entr#
G
Meaning
is unclear
More
details
needed
*ast data
entr# is
pro"ided
;here
appropriat
e as is the
a.ilit# to
.atch
load
D Re*or(,n. +nd A/er1
01 Route output to printer= &ile or ;orCstations
Hes
Annex B: Appendix 3B- Compliance Sheet
Page 119 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
0$ +ransmit reports to multiple locations
Hes
Also
includes
.roadcast
control
tools
03 Automate the report distri.ution process including:
031 -ar#ing the num.er o& copies o& each report
Hes
03$ Produce the report in report distri.ution se,uence= rather than report
num.er se,uence
Hes
033 @a.eling o& reports to speci&ic recipients
Hes
0) A.ilit# to de&ine and store report &ormats separatel# &or each department
Hes
01 Possi.le to de&ine priorities &or handling ,ueries depending on the user /
department / designation= etc
G
Meaning
unclear
0/ Should .e possi.le to de&ine the &re,uenc# at ;hich reports need to .e
prepared and distri.uted to di&&erent pre-de&ined users
Hes
00 Support report distri.ution "ia *ax= e-mail and Popup screen
Hes
04 Print selected reports at user-speci&ied printer locations
Hes
02 Allo; selecti"e report in&ormation to .e sent to a screen instead o& .eing
directed to a printer
Hes
01( Per&orm screen prints on re,uest
Hes
011 A.ilit# to generate Static and '#namic and all B% reports
Hes
01$ A.ilit# to generate the reports in di&&erent *ile &ormat 9P'*= MS 3ord=
MS Excel= +ext= A+M@ U etc: Hes
F Prod/3(,0,(1 Too-)
41 Pro"ide eas# to use on-line screen generator capa.ilit# to allo; user to
design or modi&# screen displa# &ormats
Hes
All
screens
4$ Pro"ide user--de&ined on-line AE@P screen &or &ield description= policies
or procedures related to speci&ic screens
Hes
Customers
can create
customi6e
d help
screens
.ased on
SAP
pro"ided
data
43 Pro"ision o& sel&-learning +utorials &or each &unctional areas &or users to
teach themsel"es operation o& ERP
Hes
SAP
pro"ides a
third part#
product
9R3' :
that
allo;s the
customi6at
ion o&
online
tutorials
linCed to
the SAP
help
s#stem
9 U)er In(er5+3e
21 Should pro"ide intuiti"e and eas# to use inter&ace 978%: Hes SAP 78%=
Portal=
Ado.e
%nteracti"e
*orms=
Mo.ile=
Annex B: Appendix 3B- Compliance Sheet
Page 120 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
'8E+
2$ 3orCstation !S &or installing the &ront-end s#stems 9clients:
Hes
2$1 3indo;s 24= $(((=NP and -ista
Hes
3indo;s
24 is onl#
supported
&or SAP
*rontends
until
(1/11/$((
)
Microso&t
limited the
product
support
&or
3indo;s
24 to this
date
2$$ @inux
Hes
23 Allo; the user to mo"e &rom screen to screen ;ithout mo"ing through
menu hierarchies and/or ;ithout signing o&& one application to sign on to
another Hes
2) %nterrupt current screen to per&orm &unction on another applicationOs screen
and to return to interrupted screen ;ith all original screen data intact
Hes
21 A.ilit# to pro"ide single sign-on Hes
21 Should support access to all modules= &unctions under single log-in %n case
there are more than one log-ins re,uired= pro"ide details
Hes
2/ S#stem should allo; de&ining &ields as
2/1 Mandator# Hes
2/$ Eon-mandator# Hes
2/3 Aighlighting o& mandator# &ields Hes
2/) 'e&ault &ields Hes
20
Application should support de&ining additional &ields .ased on and not
limited to
201 +ext Hes
20$ Eum.er Hes
203 'ate Hes
20) Character Hes
24
Possi.le to populate de&ault "alues &or &ields on screen 9eg toda#Os date:
to reduce le"el o& data entr# Hes
22
+he s#stem should support generating search on &ields pro"iding results
relating to e"er# area 9sales= marCeting: ;ithin the ERP application Hes
1 0 Re*or( Wr,(er
1(1 Create custom= ad hoc reports ;ithout s#stems or application programming
in"ol"ement &unctions
Hes SAP B3
1(11 A.ilit# to create d#namic reports 9drill do;ns= dash.oards ;ith <P%s etc: Hes SAP B3
1($ Speci&# contents and la#out o& user-speci&ied reports Hes SAP B3
1(3 Prompt the user &or data and report speci&ications at the terminal
interacti"el#
Hes SAP B3
1() Pro"ide access to master= summar# and detail records through interacti"e
in,uir#
Hes SAP B3
1(1 'o;nload in&ormation &rom an# transaction and summar# &ile to standard PC
so&t;are &ormats such as MS-!**%CE suite o& products
Hes SAP B3
Annex B: Appendix 3B- Compliance Sheet
Page 121 of 89
Sr. No. Re9/,re2en( De)3r,*(,on
Co2*-,+n3e Re2+r8
SUP MOD &RD CST FUT NS
1(/ Access external &iles 9o& other third part# applications not included in this
procurement: &or data to .e included in reports
Hes SAP B3
1(0 +he application should ha"e in-.uilt report ;riter Mention i& external
report ;riter tools is pro"ided
Hes SAP B3
1(4 Process complex selection criteria utili6ing: Hes SAP B3
1(41 !perators 9Z= [=\=]= &rom-to= and not &rom-to= AE'= !R : Hes SAP B3
1(4$ Multiple data &iles across s#stem .oundaries Hes SAP B3
1(2 Store report la#outs in user li.raries &or displa# at an# time Hes SAP B3
1(1( %nclude Dreport ;riterD reports in standard report printing menus and in-
.atch Bo.s
Hes SAP B3
1(11 Cop# standard reports o"er to user li.raries and maCe speci&ied changes to
them ;ithout altering the original report
Hes SAP B3
1(1$ 'esign a report .ased on the &ollo;ing user-de&ined criteria:
1(1$1 Selected data elements Hes SAP B3
1(1$$ Sort se,uence Hes SAP B3
1(1$3 Mathematical &unctions 9calculations: Hes SAP B3
1(1$) +ime inter"al Hes SAP B3
1(1$1 Print &ormats= Column headings Hes SAP B3
1(1$/ Su.totals/totals Hes SAP B3
1(1$0 7rouping &unctions Hes SAP B3
1(1$4 Retention o& prior column "alues Hes SAP B3
1(1$2 Multiple &iles accessed Hes SAP B3
1(13 Access an# data elements and &iles 9permanent or temporar#: ;ithin the
s#stem
Hes SAP B3
1(1) %t should .e possi.le to attach &ollo;ing to a report
1(1)1 Charts Hes SAP B3
1(1)$ Custom de&ined logos Hes SAP B3
1(1)3 7raphic pictures Hes SAP B3
1(11 Pro"ide access control/securit# that limits a speci&ic 8ser %' &rom
accessing:
1(111 Report ;riter s#stem Hes SAP B3
1(11$ Speci&ic data.ases Hes SAP B3
1(113 Speci&ic data &iles/records Hes SAP B3
1(11) Speci&ic data &ields Hes SAP B3
1(111 'ata.ase update capa.ilit# Hes SAP B3
1(1/ Create report ;riter programs using DEnglishD descriptions &or data elements
rather than speci&#ing the exact &ile data element name
Hes SAP B3
1(10 Calculate and total columns and ro;s o& data &or ;hich user can speci&#
su.totals or a su.total on multiple le"els or speci&ic le"el
Hes SAP B3
1(14 Allo; partial &ields 9eg= the &irst t;o digits o& &ield: to .e used as
selection criteria
Hes SAP B3
1(12 Per&orm rounding o& amount &ields .ased on user de&ined rules Hes SAP B3
Annex B: Appendix 3B- Compliance Sheet
Page 122 of 89
2 S1)(e2 In)(+--+(,on
2.1 In)(+--+(,on Ser0,3e)
Please pro"ide details o& the s#stem installation ser"ices o&&ered in this section:
1
De*-o12en( Ar34,(e3(/re - Please detail .elo; the o"erall s#stem 9applications and technolog#: deplo#ment
architecture &or installing the proposed applications &or *E3A= considering that *E3A intends to ha"e &our
en"ironments "i6: Sand-Box= 'e"elopment= +est and Production along ;ith a 'isaster Reco"er# Site
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
$
In)(+--+(,on P-+n - Please pro"ide .elo; a detailed plan 9module ;ise and the plan must sho; se,uence o& e"ents o&
the integration process .et;een de&erent modules and including timelines= resources= pre-re,uisites= etc: &or installation
o& the proposed applications +he Plan should clearl# indicate the roles o& the Product -endor= .idder= and *E3A %+
sta&&
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3
In)(+--+(,on Te)(,n. - Please pro"ide .elo; detailed testing plan on ho; the installed s#stem ;ill .e tested to ensure a
success&ul installation
Anand to add Please
)
Po)(E,n)(+-- 2+n+.e2en( - Please pro"ide details o& ho; the tested installation ;ill .e managed &or su.se,uent
implementation acti"ities
Anand to add please
2.2 C") o5 *ro*o)ed (e+2 2e26er) 5or S1)(e2 In)(+--+(,on
*or each proposed resource= please pro"ide a detailed C- in the &ollo;ing &ormat:
FORMAT OF CURRICUUM "ITAE ;C"< FOR PROPOSED #E! STAFF
Proposed Position:
Eame o& *irm:
Eame o& Sta&&:
Pro&ession:
'ate o& Birth:
Hears ;ith *irm/Entit#:
Mem.ers Bidder in Pro&essional Societies:
'etailed +asCs Assigned:
#e1 A/+-,5,3+(,on)%
Annex B: Appendix 3B- Compliance Sheet
Page 123 of 89
[Give an outline of staff memer!s e"perien#e an$ training most pertinent to tas%s on assignment& 'es#rie $egree
of responsiility (el$ y staff memer on relevant previous assignments an$ give $ates an$ lo#ations& )se aout
(alf a page&*
Ed/3+(,on%
[Summari+e #ollege,university an$ ot(er spe#iali+e$ e$u#ation of staff memer- give names of s#(ools- $ates
atten$e$- an$ $egrees otaine$& )se aout one .uarter of a page&*
E2*-o12en( Re3ord%
[Starting /it( present position- list in reverse or$er every employment (el$& 0ist all positions (el$ y staff memer
sin#e gra$uation- giving $ates- names of employment organi+ations- titles of positions (el$- an$ lo#ations of
assignments& 1or e"perien#e in last ten years- also give types of a#tivities performe$ an$ #lient referen#es- /(ere
appropriate& )se aout t/o pages&*
+n./+.e)%
[1or ea#( language in$i#ate profi#ien#y2 e"#ellent- goo$- fair or poor in spea%ing- rea$ing an$ /riting&*

Cer(,5,3+(,on%
%= the undersigned= certi&# that to the .est o& m# Cno;ledge and .elie&= these data correctl# descri.e me= m#
,uali&ications= and m# experience % also certi&# that % ha"e onl# gi"en permission &or m# C- to .e included in the
Bid su.mitted .#
[1ill in name of 3i$$er (ere&*
'ate:
[Signature of staff memer an$ aut(ori+e$ representative of t(e firm* 'ay,4ont(,5ear
*ull name o& sta&& mem.er:
*ull name o& authori6ed representati"e:
Annex B: Appendix 3B- Compliance Sheet
Page 124 of 89
& S1)(e2 I2*-e2en(+(,on
&.1 I2*-e2en(+(,on A**ro+34
1 Pro"ide the Pro:e3( *-+n ;ith details o& phases 9eg +o-Be Process mapping= design= solution setup=
customisation= con&iguration= training= user testing etc: o& proBect Pro"ide the location plan &or all the
proBect acti"ities 9ie ;hich acti"ities ;ill .e carried out ;here I ProBect o&&ice location= *E3A site=
-EE'!R training centre= -endors 'e"elopment centre= etc:
R 3ipro shall implement the Solution in a Phased Manner +here ;ill .e *our 3a"es in the implementation
Each ;a"e has the &ollo;ing Milestones:
Business Blueprint
Reali6ation
*inal Preparation R 7o @i"e
+he details are pro"ided in the P+echnical ProposalQ 'ocument ;hich is gi"en as an appendix to this
document
1a Please pro"ide details o& the Application Con&iguration Plan
R
Since 3ipro is proposing a Phased approach there ;ill .e Re,uirements 7athering stage 9Business
Blueprint: in each 3a"e Post the Business Blueprint is Signedo&&= the Con&iguration and 'e"elopment shall
start +he 'etailed plan &or the same ;ill .e pro"ided during the ProBect Preparation Phase
$ Pro"ide details o& the ,n5r+)(r/3(/re Se(E/* 9eg ser"ers= net;orC= so&t;are= etc: proposed &or
con&iguration= customi6ation and testing o& the ERP application during implementation Pro"ide details o&
speci&ic tools that ;ill .e used and made a"aila.le .# B%''ER &or the purpose o& implementation o& ERP
solution Pro"ide o"er"ie; .elo; and attach additional sheets to the proposal= i& re,uired
R
+he %n&rastructure such as %'ES S#stems ;ill .e installed at the .eginning o& the proBect and maCe them
a"aila.le &or +raining
+he 'e"elopment Ser"ers= 5ualit# Ser"ers and Product Ser"er %nstallation Pplan ;ill .e discussed in detail
during the ProBect Preparation Phase
3 Pro"ide details o& application 3/)(o2,B+(,on *-+n 9&or customi6ation o& each module= indicate timelines and
resource deplo#ment= location o& customi6ation= in"ol"ement o& *E3A personnel: Pro"ide o"er"ie; .elo;
and attach additional sheets to the proposal= i& re,uired
R
A Aigh @e"el MPP plan is pro"ided &or the proBect ;hich ;ill .e re&ined .# the PM! 93ipro R *E3A
ProBect Managers: during the ProBect Preparation Phase
) Pro"ide details o& ho; the re*or(,n. re9/,re2en() identi&ied in the re,uirement matrix ;ill .e con&igured
in the ERP applicationG 'escri.e tools to .e used &or same and in"ol"ement o& *E3A team= i& an#
R
3ipro shall pro"ide Most o& the !perational Reports through the SAP S#stem %ntelligence Reports co"ering
Multiple *unctional Areas ;ith Aigh 'etail o& %n&ormation shall .e pro"ided using the %n&ocu.es &rom SAP
B% and SAP B! <P%?s= 'ash.oards also ;ill .e pro"ided as part o& the deli"era.les
3e ha"e co"ered the re,uirements as per the cap mentioned in the R*P
Annex B: Appendix 3B- Compliance Sheet
Page 125 of 89
1 Pro"ide details o& S,.nEo55 *ro3ed/re) Pro"ide o"er"ie; .elo; and attach additional sheets to the proposal=
i& re,uired
R
E"er# Milestone in each 3a"e has a Sign-o&& procedure to ensure the 5uailit# o& Ser"ice to the Satis&action
o& the *E3A?s +eam
/ Pro"ide details o& U)er A33e*(+n3e Te)( ;UAT< *-+n= script templates to .e used= approach to .e taCen=
*E3A in"ol"ement 9department= user pro&ile= etc: and signo&& procedures to .e &ollo;ed
R +he 8ser Acceptance Plan &or each o& the 3a"e in Application 98A+: Shall use SAP S!@MAE 0( eCA++
+ool &or 8A+
0 Con&irm that Po)(E,2*-e2en(+(,on )/**or( &or a period o& one #ear &rom the date o& 7o-@i"e is included in
this proposal +he cost o& additional support should also .e speci&ied in the commercial section
R 3ipro Con&irms that Post-implementation support &or a period o& one #ear &rom the date o& 7o-@i"e
+he Support is !n-Site R !&&-Shore
4 Pro"ide details o& C4+n.e 2+n+.e2en( *-+n and procedures during the proBect
R A 'edicated Change Manager ;ill .e positioned on Site &or / Months to pro"ide Strateg#= 'irection o&
Change Management Ae ;ill pro"ide Aand Aolding Ser"ices to *E3A?s Change Manager ;ho is also a
*ull +ime Mem.er on the proBect till completion
For 5/r(4er de(+,-) *-e+)e re5er (o (4e Te34n,3+- Pro*o)+- 74,34 ,) *ro0,ded +) +n A**end,@ (o (4,)
do3/2en(.
2 Pro"ide details o& the Pro:e3( R,)8 2+n+.e2en( plan Pro"ide o"er"ie; .elo; and attach additional sheets
to the proposal= i& re,uired
R 3ipro?s 7o"ernance Strucutre ;ill handle the RisC Management and pro"ide Mitigation Plans &or the senior
Management
For 5/r(4er de(+,-) *-e+)e re5er (o (4e Te34n,3+- Pro*o)+- 74,34 ,) *ro0,ded +) +n A**end,@ (o (4,)
do3/2en(.
1( Pro"ide details o& the Pro:e3( 3on(ro-) proposed Pro"ide o"er"ie; .elo; and attach additional sheets to the
proposal= i& re,uired
R +he 7o"ernance Strucutre ;ill handle the ProBect Controls liCe Communication Plan= Escalation Matrix and
Responsi.ilit#
For 5/r(4er de(+,-) *-e+)e re5er (o (4e Te34n,3+- Pro*o)+- 74,34 ,) *ro0,ded +) +n A**end,@ (o (4,)
do3/2en(.
11 Pro"ide the Pro:e3( A/+-,(1 2+n+.e2en( *-+n ;ith clarit# on procedures= roles and responsi.ilities
Pro"ide o"er"ie; .elo; and attach additional sheets to the proposal= i& re,uired
R 3ipro shall engage a person &rom 3ipro 5ualit# !rgani6ation ;hich acts as an %ndependent Re"ie;er and
appraises the Steering Committee on the 5ualit# Acti"ities
For 5/r(4er de(+,-) *-e+)e re5er (o (4e Te34n,3+- Pro*o)+- 74,34 ,) *ro0,ded +) +n A**end,@ (o (4,)
do3/2en(.
Annex B: Appendix 3B- Compliance Sheet
Page 126 of 89
1$ Pro"ide details o& E)3+-+(,on *ro3ed/re) +nd ,))/e re)o-/(,on *-+n &or the proBect Pro"ide o"er"ie; .elo;
and attach additional sheets to the proposal= i& re,uired
R +he 'etails are pro"ided in the +echnical Proposal ;hich is pro"ided as an Appendix to this 'ocument
13 Please pro"ide details o& In(ern+- A/+-,(1 )(+nd+rd) that B%''ER &ollo;s &or proBects in"ol"ing
implementation o& ERP Please con&irm i& the B%''ER has achie"ed standard certi&ications &or the internal
5ualit# processes
R +he 'etails are pro"ided in the +echnical Proposal ;hich is pro"ided as an Appendix to this 'ocument
1) Pro"ide the proposed Pro:e3( or.+n,B+(,on 34+r( outlining ProBect roles 9eg Steering Committee mem.er=
ProBect manager= Module leader= etc:= !rgani6ation 9eg *E3A= @ead B%''ER= supporting B%''ER= etc:
and roles and responsi.ilities o& each role 9eg ProBect manager Z ProBect planning= monitoring= resource
management= etc=: Please use additional sheets i& re,uired
R +he ProBect !rgani6ation Chart &or 3ipro and *E3A is pro"ided in the Te34n,3+- Pro*o)+- 74,34 ,)
*ro0,ded +) +n A**end,@ (o (4,) do3/2en(.
&.2 D+(+ M,.r+(,on
1
Please pro"ide a .rie& o"er"ie; o& the D+(+ M,.r+(,on S(r+(e.1 t#picall# adopted .# the B%''ER in such
implementation proBects
R W,*ro )4+-- 5o--o7 S(+nd+rd SAP S/..e)(ed C/(o0er Me(4odo-o.1 ,n M,.r+(,n. D+(+ 5ro2 e.+31
S1)(e2) (o SAP S1)(e2.
W,*ro )4+-- 5o--o7 SAP DW' S(r+(e.1 5or 2,.r+(,n. ',)(or,3+- D+(+ 5ro2 e.+31 S1)(e2) (o SAP
S1)(e2.
T4e S+2e 4+) 6een *ro0,ded ,n (4e A**end,@ JTe34n,3+- Pro*o)+-K
$ Ao; do #ou esta.lish the +33e*(+6,-,(1 o5 (4e d+(+ +0+,-+6-e 5ro2 -e.+31 +**-,3+(,on)G
R +he 'ata has to .e appro"ed .# the *E3A?s Business !;ners on the Correctness o& 'ata
3 3hat are the considerations &or deciding ;hether manual or automated 3orre3(,on/0+-,d+(,on should .e
adopted to &acilitate the data migrationG
R %& the Records are more than 1(( and co"ering Multiple Screens along ;ith its &re,uenc# o& use during @i"e
En"ironment= 3ipro and *E3A shall Bointl# decide on the approach %& the Master 'ata Population is small
3ipro suggests to create the 'ata Manuall# to sa"e time and e&&ort in de"eloping and +esting o& 8pload
Programs
) 'oes the B%''ER intend to use an# speci&ic (oo-) (o 5+3,-,(+(e d+(+ 2,.r+(,onG %& so= please pro"ide
details
R 3ipro Shall use SAP S!@MAE 0( @egac# 'ata Migration 3orC.ench coupled ;ith Batch 'ata
Con"ertion Programs to upload data &rom *lat *iles to SAP S#stem or SAP '3A S#stem as the case ma#
.e
1 Ao; is the +33/r+31 o5 (4e D+(+ M,.r+(,on *ro3e)) esta.lishedG Please pro"ide details o& the control
mechanism that the B%''ER deplo#s to ensure integrit# o& the data migration process
Annex B: Appendix 3B- Compliance Sheet
Page 127 of 89
R +he 'ata Migration is MarCed Success&ul onl# a&ter dra;ing a report on Eum.er o& Records @oaded and
+rial Balance 7enerated out o& SAP S#stem *E3A?s BP! R 'ata Migration +eam shall pro"ide 'ata in a
C' in the re,uired &ormat
/ Please clearl# identi&# the ,n0o-0e2en( o5 FEWA in the data migration process and also indicate the
re,uirements &rom *E3A sta&&
R 3ipro +eam and *E3A?s Core +eam shall identi&# the !.Bects &or ;hich 'ata Migration has to .e
per&ormed
PM! ;ill de"elop a 'ata Migration Plan &or Each 3a"e and create a 'edicated +eam comprising o& *E3A
%+ personnel and 'ata Collectors representing each location +his team is responsi.le &or Extraction=
Enrichment= Con"ersion in the &ormats pro"ided .# 3ipro Consultants 3ipro consultants shall pro"ide
+raining in Enrichment and Con"ersion to this team
3e ;ill re,uire a +eam o& 11 persons representing each Area o& Business &or 'ata Collection
&.& In(er5+3e)
1
Please pro"ide a .rie& o"er"ie; o& ho; B%''ER ;ill handle the In(er5+3e) proposed .# *E3A and the
proposed Billing/ ERP Applications +he proposed inter&aces are ;ith Contact center= e-ser"ices= 'ocument
Management S#stem= Cash Settlement Machines= BanC Statements= Emirates Post Receipts= Credit
Card Readers= 7%S/ SCA'A= etc
R 3ipro team shall pro"ide AP%?s to integrate ;ith Contact Center= Pa#ment 7ate;a#s= BanCs= 7%S/SCA'A=
SMS 7ate;a#s
+he +echnical Proposal ;hich is pro"ided as an appendix gi"es &urther details on ho; 3ipro plans to
pro"ide integration
$ Ao; ;ould the B%''ER approach de),.n,n., de0e-o*,n. +nd (e)(,n. (4e ,n(er5+3e)G
R 3ipro shall &ollo; the *RS I +RS I 'E-E@!PMEE+ I +ES+%E7 I M!-EMEE+ methodolog# in
'esigning= 'e"eloping the %nter&aces
3 Ao; ;ould the B%''ER handle the )/6)e9/en( 34+n.e) to the inter&ace re,uirementsG
R +he *E3A %+ +eam ;ill .e pro"ided +raining on maCing changes and also the procedure that has to .e
&ollo;ed in releasing the de"elopments &rom one en"rionement to another
An# Su.se,uent changes in the %nter&ace re,uirements ;hich cannot .e handled .# the *E3A %+ team ;ill
.e pro"ided Ao;e"er an# modi&ication ;hich can taCe more than 3 Man 'a#s o& e&&ort ;ill .e pro"ided
a&ter initating a Change Control Procedure
&.> Do3/2en(+(,on
<indl# &urnish in&ormation &or each solution separatel# in case more than one solution is in"ol"ed
Annex B: Appendix 3B- Compliance Sheet
Page 128 of 89
Please list ;hich o& the &ollo;ing documentation are pro"ided ;ith #our product9s:
8ser manuals
%mplementation manual
S#stem Administration manual / !perations manual
S#stem manuals I Architectures= Entit#-Relationship diagrams= Source code etc
!n-line 8ser Manual
!nline context sensiti"e help
1
Ao; man# copies o& related so&t;are user documentation are pro"ided ;ith the so&t;are purchaseG Please
mention the &orm o& documents 9hard cop#= so&t cop#= etc:
R
SAP 'ocumentation is a"aila.le !n @ine %t is SAP?s and 3ipro?s Polic# to maCe the Planet a 7reener
Place to @i"e Aence Aardcopies o& the same are pro"ided onl# against additional charge
$
Ao; man# copies o& related so&t;are technical documentation are pro"ided ;ith the so&t;are purchaseG
R
Eo Aardcopies Please
3
Can additional copies .e made .# *E3A in-house or must additional manuals .e purchasedG
R
ProBect +eams= *E3A +eam and %+ +eam o& *E3A can taCe printout o& the documents an# num.er o&
times= there is no restriction and cost implications on the same
)
a %s documentation pro"ided in loose-lea& &ormat in case o& updationG
R
'ocumentation o& 8pdates is !n @ine and is not gi"en as an addendum
. Are documentation updates a"aila.le in an electronic &ormG %& #es= please pro"ide details
R
All the 'ocumentation on SAP Aelp= SAP Eotes is a"aila.le in Electronic *ormat and can .e
'o;nloaded &rom http://ser"icesapcom or http://helpsapcom
1
'oes the Bidder pro"ide documentation updates to correspond ;ith each so&t;are releaseG
R
+he 'ocumentation is directl# a"aila.le to *E3A and 3ipro does not pose an# restriction on the use o&
the same .# *E3A +eam
/
!n ;hat &ee .asis are additional documentation updates pro"idedG Pro"ide these details in the commercial
section
R
*or Electronic *ormat= Eeither 3ipro= nor SAP shall charge the customer
%& the 'ocumentation is re,uired in Aardcop# the same shall .e pro"ided at a price that can .e mutuall#
decided
0
'oes the Bidder pro"ide &or do;nloading documents or ;hite papers &rom its ;e. site
R
+he in&ormation on the @inCs to the 'ocumentation shall .e pro"ided .oth .# SAP and 3ipro and none
;ill place an# Restriction on using the same
Note: All costs should .e speci&ied in the commercial section onl#
Annex B: Appendix 3B- Compliance Sheet
Page 129 of 89
&.5 B,dder S(+55,n. P-+n
Since the %mplementation is a Phased approach ha"ing multiple 3a"es= it is not possi.le to gi"e a split as
per the Schedule gi"en .elo;
Pro:e3( Ro-e
P4+)e I M Pro:e3(
*re*+r+(,on, Tr+,n,n.
+nd De),.n
P4+)e II M So5(7+re
Con5,./r+(,on /
C/)(o2,B+(,on / UAT
S,.no55
P4+)e III M Pre*+r+(,on
o5 GoE-,0e, End /)er
(r+,n,n., GoE,0e
P4+)e I" M Po)( GoE
,0e
No. o5
*er)onne-
In0o-0e2en(
Per)on/D+1)
No. o5
*er)onne-
In0o-0e2en(
Per)on/D+1)
No. o5
*er)onne-
In0o-0e2en(
Per)on/D+1)
No. o5
*er)onne-
In0o-0e2en(
Per)on/D+1)
Pro:e3(
M+n+.e2en(
Steering
Committee
mem.er
1
ProBect
Manager
1
F/n3(,on+- /
Mod/-e re-+(ed
Module
Eame
\Module
@eader]
\Module
team
mem.er]
Te34n,3+- +re+)
+echnical
@eader
+echnical
team mem.er
1
+echnical
team mem.er
$
S/**or( +re+)
Support team
mem.er
Annex B: Appendix 3B- Compliance Sheet
Page 130 of 89
Pro:e3( Ro-e
P4+)e I M Pro:e3(
*re*+r+(,on, Tr+,n,n.
+nd De),.n
P4+)e II M So5(7+re
Con5,./r+(,on /
C/)(o2,B+(,on / UAT
S,.no55
P4+)e III M Pre*+r+(,on
o5 GoE-,0e, End /)er
(r+,n,n., GoE,0e
P4+)e I" M Po)( GoE
,0e
No. o5
*er)onne-
In0o-0e2en(
Per)on/D+1)
No. o5
*er)onne-
In0o-0e2en(
Per)on/D+1)
No. o5
*er)onne-
In0o-0e2en(
Per)on/D+1)
No. o5
*er)onne-
In0o-0e2en(
Per)on/D+1)
Support team
mem.er
Annex B: Appendix 3B- Compliance Sheet
Page 131 of 89
&.C C") o5 (e+2 2e26er)
Please &ill up &ollo;ing ta.les &or e+34 o5 (4e *ro*o)ed (e+2 2e26er) o5 BIDDER &or
*E3A proBect %n case o& multiple Bidders please pro"ide details o& team mem.ers o& all the
in"ol"ed Bidders
FORMAT OF CURRICUUM "ITAE ;C"< FOR PROPOSED #E! STAFF
Proposed Position:
Eame o& *irm:
Eame o& Sta&&:
Pro&ession:
'ate o& Birth:
Hears ;ith *irm/Entit#: Eationalit#:
Mem.ers Bidder in Pro&essional Societies:

'etailed +asCs Assigned:

#e1 A/+-,5,3+(,on)%
[Give an outline of staff memer!s e"perien#e an$ training most pertinent to tas%s on
assignment& 'es#rie $egree of responsiility (el$ y staff memer on relevant previous
assignments an$ give $ates an$ lo#ations& )se aout (alf a page&*
Annex B: Appendix 3B- Compliance Sheet
Page 132 of 89

Ed/3+(,on%
[Summari+e #ollege,university an$ ot(er spe#iali+e$ e$u#ation of staff memer- give names of
s#(ools- $ates atten$e$- an$ $egrees otaine$& )se aout one .uarter of a page&*

E2*-o12en( Re3ord%
[Starting /it( present position- list in reverse or$er every employment (el$& 0ist all positions
(el$ y staff memer sin#e gra$uation- giving $ates- names of employment organi+ations- titles
of positions (el$- an$ lo#ations of assignments& 1or e"perien#e in last ten years- also give types
of a#tivities performe$ an$ #lient referen#es- /(ere appropriate& )se aout t/o pages&*

+n./+.e)%
[1or ea#( language in$i#ate profi#ien#y2 e"#ellent- goo$- fair or poor in spea%ing- rea$ing an$
/riting&*

Cer(,5,3+(,on%
%= the undersigned= certi&# that to the .est o& m# Cno;ledge and .elie&= these data correctl#
descri.e me= m# ,uali&ications= and m# experience % also certi&# that % ha"e onl# gi"en
permission &or m# C- to .e included in the Bid su.mitted .#
[1ill in name of 3i$$er (ere&*
'ate:
[Signature of staff memer an$ aut(ori+e$ representative of t(e firm* 'ay,4ont(,5ear
*ull name o& sta&& mem.er:
*ull name o& authori6ed representati"e:
&.D FEWA (e+2 ,n0o-0e2en(
FEWA TEAM INVOVEMENT
Pro:e3( Ro-e P4+)e I M Pro:e3( *re*+r+(,on, Tr+,n,n.
+nd De),.n
P4+)e II M So5(7+re Con5,./r+(,on /
C/)(o2,B+(,on / UAT S,.no55
P4+)e III M Pre*+r+(,on o5 GoE-,0e, End
/)er (r+,n,n., GoE,0e
P4+)e I" M Po)( GoE,0e ;& 2on(4
)/**or( *er,od<
No. o5
*er)on
ne-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--)
Pro:e3(
M+n+.e2en(

S(eer,n.
Co22,((ee
ProBect Sponsor= Business Process !;ners 9Re,uired on Part +ime Basis:
+hese resources ha"e to attend the Steering Committee Meetings ;hich are organi6ed !nce e"er# Month





Pro:e3(
M+n+.er
1 ProBect
Management
Person ;orCing
;ith *E3A and
responsi.le &or %+
ProBects
1 ProBect
Management
Person ;orCing
;ith *E3A and
responsi.le &or %+
ProBects
1 ProBect
Management
Person ;orCing
;ith *E3A and
responsi.le &or %+
ProBects
1 ProBect
Management
Person ;orCing
;ith *E3A and
responsi.le &or %+
ProBects
F/n3(,on+- /
Mod/-e
re-+(ed
Speci&ied as Belo;
Annex B: Appendix 3B- Compliance Sheet
Page 133 o& 42
FEWA TEAM INVOVEMENT
Pro:e3( Ro-e P4+)e I M Pro:e3( *re*+r+(,on, Tr+,n,n.
+nd De),.n
P4+)e II M So5(7+re Con5,./r+(,on /
C/)(o2,B+(,on / UAT S,.no55
P4+)e III M Pre*+r+(,on o5 GoE-,0e, End
/)er (r+,n,n., GoE,0e
P4+)e I" M Po)( GoE,0e ;& 2on(4
)/**or( *er,od<
No. o5
*er)on
ne-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--)
'/2+n
C+*,(+-
M+n+.e2en(
3 ACM +eam
&rom Corporate
Ser"ices ;ill .e
the Core +eam
Mem.ers in the
ProBect
Experience in
Aandling AR
Re,uirements in
*E3A and
3orCing in the
areas o&
Recruitment=
Per&ormance
Appraisal=
Pa#roll= Personnel
'e"elopment
3 ACM +eam
&rom Corporate
Ser"ices ;ill .e
the Core +eam
Mem.ers in the
ProBect
Experience in
Aandling AR
Re,uirements in
*E3A and
3orCing in the
areas o&
Recruitment=
Per&ormance
Appraisal=
Pa#roll= Personnel
'e"elopment
3 ACM +eam
&rom Corporate
Ser"ices ;ill .e
the Core +eam
Mem.ers in the
ProBect
Experience in
Aandling AR
Re,uirements in
*E3A and
3orCing in the
areas o&
Recruitment=
Per&ormance
Appraisal=
Pa#roll= Personnel
'e"elopment
3 ACM +eam
&rom Corporate
Ser"ices ;ill .e
the Core +eam
Mem.ers in the
ProBect
Experience in
Aandling AR
Re,uirements in
*E3A and
3orCing in the
areas o&
Recruitment=
Per&ormance
Appraisal=
Pa#roll=
Personnel
'e"elopment
Per5or2+n3e
M+n+.e2en(
;B/),ne))
In(e--,.en3e<
$ %+ persons &rom
%+ 'epartment
;ho ;ill .e the
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho are
in"lo"ed in
de"eloping the
Senior
Management
Reports and
in"lo"ed in %+
'e"elopment at
*E3A
$ %+ persons &rom
%+ 'epartment
;ho ;ill .e the
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho are
in"lo"ed in
de"eloping the
Senior
Management
Reports and
in"lo"ed in %+
'e"elopment at
*E3A
$ %+ persons &rom
%+ 'epartment
;ho ;ill .e the
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho are
in"lo"ed in
de"eloping the
Senior
Management
Reports and
in"lo"ed in %+
'e"elopment at
*E3A
$ %+ persons &rom
%+ 'epartment
;ho ;ill .e the
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho are
in"lo"ed in
de"eloping the
Senior
Management
Reports and
in"lo"ed in %+
'e"elopment at
*E3A
Per5or2+n3e
M+n+.e2en(
$ %+ persons &rom
%+ 'epartment
;ho ;ill .e the
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho are
in"lo"ed in
de"eloping the
Senior
Management
Reports and
in"lo"ed in %+
'e"elopment at
*E3A
$ %+ persons &rom
%+ 'epartment
;ho ;ill .e the
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho are
in"lo"ed in
de"eloping the
Senior
Management
Reports and
in"lo"ed in %+
'e"elopment at
*E3A
$ %+ persons &rom
%+ 'epartment
;ho ;ill .e the
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho are
in"lo"ed in
de"eloping the
Senior
Management
Reports and
in"lo"ed in %+
'e"elopment at
*E3A
$ %+ persons &rom
%+ 'epartment
;ho ;ill .e the
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho are
in"lo"ed in
de"eloping the
Senior
Management
Reports and
in"lo"ed in %+
'e"elopment at
*E3A
Annex B: Appendix 3B- Compliance Sheet
Page 134 o& 42
FEWA TEAM INVOVEMENT
Pro:e3( Ro-e P4+)e I M Pro:e3( *re*+r+(,on, Tr+,n,n.
+nd De),.n
P4+)e II M So5(7+re Con5,./r+(,on /
C/)(o2,B+(,on / UAT S,.no55
P4+)e III M Pre*+r+(,on o5 GoE-,0e, End
/)er (r+,n,n., GoE,0e
P4+)e I" M Po)( GoE,0e ;& 2on(4
)/**or( *er,od<
No. o5
*er)on
ne-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--)
S/**-1 C4+,n
M+n+.e2en(
$ Suppl#
'irectorate
+eam
Persons in"lo"ed
in the Suppl#
'irectorate o&
*E3A and has
exposure to the
Business
Processes at
*E3A
$ Suppl#
'irectorate
+eam
Persons in"lo"ed
in the Suppl#
'irectorate o&
*E3A and has
exposure to the
Business
Processes at
*E3A
$ Suppl#
'irectorate
+eam
Persons in"lo"ed
in the Suppl#
'irectorate o&
*E3A and has
exposure to the
Business
Processes at
*E3A
$ Suppl#
'irectorate
+eam
Persons in"lo"ed
in the Suppl#
'irectorate o&
*E3A and has
exposure to the
Business
Processes at
*E3A
F,n+n3,+-
M+n+.e2en(
1 Mem.ers &rom
Corporate +eam
o& *E3A ;ill
.e *unctional
Core +eam
Mem.ers in the
ProBect
Persons in"ol"ed
in the Corporate
*unctions o&
*E3A and ;ho
has exposure to
all the Business
Processes o&
Costing=
Budgeting= 7/l=
AR= AP etc
1 Mem.ers &rom
Corporate +eam
o& *E3A ;ill
.e *unctional
Core +eam
Mem.ers in the
ProBect
Persons in"ol"ed
in the Corporate
*unctions o&
*E3A and ;ho
has exposure to
all the Business
Processes o&
Costing=
Budgeting= 7/l=
AR= AP etc
1 Mem.ers &rom
Corporate +eam
o& *E3A ;ill
.e *unctional
Core +eam
Mem.ers in the
ProBect
Persons in"ol"ed
in the Corporate
*unctions o&
*E3A and ;ho
has exposure to
all the Business
Processes o&
Costing=
Budgeting= 7/l=
AR= AP etc
1 Mem.ers &rom
Corporate +eam
o& *E3A ;ill
.e *unctional
Core +eam
Mem.ers in the
ProBect
Persons in"ol"ed
in the Corporate
*unctions o&
*E3A and ;ho
has exposure to
all the Business
Processes o&
Costing=
Budgeting= 7/l=
AR= AP etc
A))e(
,5e313-e
M+n+.e2en(
3 Mem.ers &rom
Shared Ser"ices
'irectorate o&
*E3A ;ill .e
*unctional +eam
Mem.ers in the
ProBect
Persons in"lo"ed
in the Shared
Ser"ices
'irectorate and
;ho has exposure
to all the Business
Processes o&
Asset
Management
3 Mem.ers &rom
Shared Ser"ices
'irectorate o&
*E3A ;ill .e
*unctional +eam
Mem.ers in the
ProBect
Persons in"lo"ed
in the Shared
Ser"ices
'irectorate and
;ho has exposure
to all the Business
Processes o&
Asset
Management
3 Mem.ers &rom
Shared Ser"ices
'irectorate o&
*E3A ;ill .e
*unctional +eam
Mem.ers in the
ProBect
Persons in"lo"ed
in the Shared
Ser"ices
'irectorate and
;ho has exposure
to all the Business
Processes o&
Asset
Management
3 Mem.ers &rom
Shared Ser"ices
'irectorate o&
*E3A ;ill .e
*unctional +eam
Mem.ers in the
ProBect
Persons in"lo"ed
in the Shared
Ser"ices
'irectorate and
;ho has exposure
to all the
Business
Processes o&
Asset
Management
Annex B: Appendix 3B- Compliance Sheet
Page 135 o& 42
FEWA TEAM INVOVEMENT
Pro:e3( Ro-e P4+)e I M Pro:e3( *re*+r+(,on, Tr+,n,n.
+nd De),.n
P4+)e II M So5(7+re Con5,./r+(,on /
C/)(o2,B+(,on / UAT S,.no55
P4+)e III M Pre*+r+(,on o5 GoE-,0e, End
/)er (r+,n,n., GoE,0e
P4+)e I" M Po)( GoE,0e ;& 2on(4
)/**or( *er,od<
No. o5
*er)on
ne-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--)
C/)(o2er
C+re L
B,--,n.
3 Mem.ers &rom
Customer
Ser"ice
'irectorate o&
*E3A ;ill .e
*unctional +eam
Mem.ers in the
ProBect
Persons in"ol"ed
in the Customer
Ser"ices
'irectorate and
;ho ha"e
exposure to all
Business
Processes o&
Customer @i&e
C#cle
3 Mem.ers &rom
Customer
Ser"ice
'irectorate o&
*E3A ;ill .e
*unctional +eam
Mem.ers in the
ProBect
Persons in"ol"ed
in the Customer
Ser"ices
'irectorate and
;ho ha"e
exposure to all
Business
Processes o&
Customer @i&e
C#cle
3 Mem.ers &rom
Customer
Ser"ice
'irectorate o&
*E3A ;ill .e
*unctional +eam
Mem.ers in the
ProBect
Persons in"ol"ed
in the Customer
Ser"ices
'irectorate and
;ho ha"e
exposure to all
Business
Processes o&
Customer @i&e
C#cle
3 Mem.ers &rom
Customer
Ser"ice
'irectorate o&
*E3A ;ill .e
*unctional +eam
Mem.ers in the
ProBect
Persons in"ol"ed
in the Customer
Ser"ices
'irectorate and
;ho ha"e
exposure to all
Business
Processes o&
Customer @i&e
C#cle
Te34n,3+-
+re+)
1( Mem.ers &rom
%+ +eam shall .e
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho ha"e
Programming
Experience in an#
@anguage and has
@earning
Capa.ilit# to
im.i.e ne;
+echnologies
1( Mem.ers &rom
%+ +eam shall .e
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho ha"e
Programming
Experience in an#
@anguage and has
@earning
Capa.ilit# to
im.i.e ne;
+echnologies
1( Mem.ers &rom
%+ +eam shall .e
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho ha"e
Programming
Experience in an#
@anguage and has
@earning
Capa.ilit# to
im.i.e ne;
+echnologies
1( Mem.ers &rom
%+ +eam shall .e
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho ha"e
Programming
Experience in an#
@anguage and has
@earning
Capa.ilit# to
im.i.e ne;
+echnologies
S1)(e2
+d2,n,)(r+(,o
n
$ Mem.ers &rom
%+ +eam shall .e
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho ha"e
Programming
Experience in an#
@anguage and has
@earning
Capa.ilit# to
im.i.e ne;
+echnologies
$ Mem.ers &rom
%+ +eam shall .e
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho ha"e
Programming
Experience in an#
@anguage and has
@earning
Capa.ilit# to
im.i.e ne;
+echnologies
$ Mem.ers &rom
%+ +eam shall .e
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho ha"e
Programming
Experience in an#
@anguage and has
@earning
Capa.ilit# to
im.i.e ne;
+echnologies
$ Mem.ers &rom
%+ +eam shall .e
+echnical Core
+eam Mem.ers
in the ProBect
Persons ;ho ha"e
Programming
Experience in an#
@anguage and has
@earning
Capa.ilit# to
im.i.e ne;
+echnologies
In(er5+3e
de0e-o*2en(
%ncluded in +echnical Areas 9Persons ;ho got trained in the +echnical Areas ;ill also .e gi"en Assignments in 'e"elopment:
S1)(e2
*ro.r+22,n.
%ncluded in +echnical Areas 9Persons ;ho got trained in the +echnical Areas ;ill also .e gi"en Assignments in 'e"elopment:
Annex B: Appendix 3B- Compliance Sheet
Page 136 o& 42
FEWA TEAM INVOVEMENT
Pro:e3( Ro-e P4+)e I M Pro:e3( *re*+r+(,on, Tr+,n,n.
+nd De),.n
P4+)e II M So5(7+re Con5,./r+(,on /
C/)(o2,B+(,on / UAT S,.no55
P4+)e III M Pre*+r+(,on o5 GoE-,0e, End
/)er (r+,n,n., GoE,0e
P4+)e I" M Po)( GoE,0e ;& 2on(4
)/**or( *er,od<
No. o5
*er)on
ne-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--) No.
o5
*er)
onne
-
Ro-e ,n (4e
*ro:e3(
E@*e3(ed )8,--)
D+(+
2,.r+(,on
1( Mem.ers o& this
+eam are
responsi.le &or
Collecting=
Collating and
Correcting the
'ata &rom
@egac# S#stems
+he Mem.ers
should .e a.le to
;orC on Excel
Sheets and
+rans&orm the
'ata &rom @egac#
S#stem to the
&ormat compati.le
&or SAP 8pload
1( Mem.ers o& this
+eam are
responsi.le &or
Collecting=
Collating and
Correcting the
'ata &rom
@egac# S#stems
+he Mem.ers
should .e a.le to
;orC on Excel
Sheets and
+rans&orm the
'ata &rom @egac#
S#stem to the
&ormat compati.le
&or SAP 8pload

C4+n.e
M+n+.er
1 Change @eader A person ;ho can
ena.le change in
the !rgani6ation
1 Change @eader A person ;ho can
ena.le change in
the !rgani6ation
1 Change @eader A person ;ho can
ena.le change in
the !rgani6ation
1 Change @eader A person ;ho can
ena.le change in
the !rgani6ation
A +eam o& )1 Mem.ers 9*unctional R +echnical Core +eam Mem.ers= 'ata Migration +eam Mem.ers: are re,uired to ;orC on this
proBect *ull +ime
ProBect Manager= Change Manager are also re,uired &rom ProBect Management o&&ice to ;orC *ull +ime
Senior @eadership +eam liCe Sponsors etc are re,uired on a Part +ime Basis onl#
Annex B: Appendix 3B- Compliance Sheet
Page 137 o& 42
&.F FEWA In5r+)(r/3(/re Re9/,re2en()
Expected resource re,uirements &rom *E3A 9hard;are= so&t;are= o&&ice space= etc: &or the implementation o& proposed solution Pro"ide o"er"ie; .elo; and
attach additional sheets to the proposal= i& re,uired
R
3ipro shall re,uire a ProBect !&&ice to accommodate 1(( persons 9Both *E3A +eam and 3ipro +eam: ;ith Meeting Aalls= 'iscussion Rooms
Separate Ca.ins each &or 3ipro ProBect Manager and *E3A?s ProBect Manager
Media E,uipment liCe ProBectors= 3riting Boards
Seating Space and 'ocument Storing Sapce to each Mem.er
'esCtops / @aptops &or the +eam Mem.ers
+;o Po;er SocCets 9!ne Standard= !ne 8PS:= @AE Ca.le to each 'esC
Printers= Stationer#= Communication E,uipment
A minimum o& 1 MBPS %nternet Connection
'atacenter ;ith Access Controls and Precision A/c to house the Ser"ers
Eet;orC ;ith *ire;alls ;ith Eo Restriction to SAP MarCetplace and other Authori6ed Sites
Common Amenities and Support Sta&&
3ipro?s ProBect Manager shall pro"ide small suggestions during the ProBect Preparation Phase i& an# additional is re,uired
Annex B: Appendix 3B- Compliance Sheet
Page 138 o& 42
> Tr+,n,n.
1
3hat +2o/n( o5 (r+,n,n. is included in terms o& num.er o& people t#pe o& course/agenda 9technical=
administration= .usiness users= etc: and num.er o& man-da#sG Clearl# mention i& B%''ER proposes that
*E3A should source an# o& the components o& training &rom ERP "endor
CONSUTANT E"E TRAINING%
+raining ;ill .e gi"en during the Phase % o& the proBect
+raining ;ill .e pro"ided &or a +eam o& 12 Mem.ers
+raining ;ill .e 7i"en .# Certi&ied Mem.ers &rom SAP
Module ;ise +rainees split is as &ollo;s:
Tr+,n,n. Co/r)e Per)on) D+1)
SAP *%E= AC(1(= AC(1( 9*inancial Accounting:
9Basic Course:
$ 1$
AC()( 9Management Accounting: 1K 1
Auman Capital Management I SAP AR - 9Basic
Course:
$ $
AR(1(= AR3(1 1K 1
AR)(( R AR11( 1K $
SAP SCM - 9Basic Course: $ 3
SCM1((= SCM11( 1K 1(
SCM 111= SCM1$( 1K 4
PM - 9Basic Course: $ 1(
%8+ 9%S-8tilities: I %8+11( - Basic Course 3 1
%8+$1(= $$(= $$1 1K 4
%8+$$1= $3(= $31 1K 4
%8+$)(= $1( 1K 4
Administration 1 13
ABAP 1 11
B% 1 1
Enterprise Portal 1 $
K %ncluded in the Persons identi&ied in the Basic Course
+raining ;ill .e gi"en out o& *E3A?s ProBect !&&ice
Certi&icate o& Attendance ;ill .e pro"ided to the Participants ;ho ha"e attended &or more than 21T o&
Attendance
Annex B: Appendix 3B- Compliance Sheet
Page 139 o& 42
$
'escri.e all pertinent (r+,n,n. 3o/r)e) &or all the phases o& proBect and all the t#pes o& training 9eg End-user=
core team= S#stem administration training= etc: *or each course= include the &ollo;ing in&ormation:
Course +itle +he 'etails are pro"ided in the +echnical
Proposal Attached
@ocation ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^
Phase o& the proBect ;hen training ;ill .e
imparted
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^
Mode o& training 9eg classroom= online: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^
+arget participants 9eg Core team
&unctional team mem.ers= end-users:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^
Eum.er o& participants per .atch ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^
'uration o& training ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^
*re,uenc# o& o&&ering ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^
Prere,uisites ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^
7eneral description
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3
@ist the courses #ou ;ill not .e a.le to train the d/+- -+n./+.e Ar+6,3/ En.-,)4
Consultant @e"el +raining= @e"el %%% +raining and Customi6ation +raining R P+rain the +rainerQ ;ill .e done
onl# in English
End 8ser +raining ;ill .e done in .oth English R Ara.ic
Annex B: Appendix 3B- Compliance Sheet
Page 140 o& 42
5 S/**or( A/e)(,onn+,re
Please pro"ide details o& support to .e pro"ided .# B%''ER
1
Please indicate the )(r/3(/re o& pro"iding support ;ith details o& escalation procedures Clearl# identi&# the
role that B%''ER ;ill pla# and ;hat ;ill .e the role o& ERP "endor in terms o& pro"iding support
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
$
Please descri.e the *ro6-e2 re*or(,n. +nd re)o-/(,on 2e34+n,)2 that ;ould .e used i& *E3A identi&ies a
pro.lem ;ith the pacCage 'oes the Bidder ha"e dial-up capa.ilit# into the *E3A s#stem to correct
application program .ugsG Pro"ide details o& securit# arrangements in case #our personnel log into *E3A?s
ser"ers
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3
'o #ou ha"e a user 'o(-,neG 9 H / E : %& #es:
A"aila.ilit#: hours/da# 9speci&# time in 'u.ai: - 'oes this include ;eeCendsG *E3A
;ould pre&er local support 0 am to / pm support 9'u.ai:= six da#s a ;eeC
Speci&# ser"ice outside the normal o&&ice hours and at ;eeCends Also speci&# i& the num.er to .e
dialed is ;ithin 'u.ai
Amit / M%+ team to add please
)
3hat is the 2+@,2/2 re)*on)e (,2e &or all the ,ueries / issues registered .# *E3A personnelG
R
+he Response +ime and Resolution +ime shall .e discussed and Mutuall# agreed .e&ore the 3arrant# Support
Starts
1
Please pro"ide details o& the )o5(7+re 9eg helpdesC so&t;are:= 4+rd7+re +nd WAN ,n5r+)(r/3(/re used to
o&&er support to clients
R
Amit / M%+ team to add please
/
C4+r.e) - %s the Aotline support inclusi"e in the annual maintenance charge= or are users charged per callG %&
charged on a per-call .asis= please pro"ide cost in the rele"ant section in Commercial .id
R
Amit / M%+ +eam to add please
0
Pro"ide details o& -o3+(,on) in 8AE &rom ;here Bidder ;ill pro"ide support %ndicate details o& t#pe o&
support 9direct or through a partner compan#:
R
Amit / M%+ +eam to add please
4
Ao; man# re-e+)e) o& #our product are currentl# supportedG Please identi&#
R
Annex B: Appendix 3B- Compliance Sheet
Page 141 o& 42
2
3ill B%''ER pro"ide )/**or( 5or )1)(e2 3/)(o2,B+(,on as a part o& annual support contractG Pro"ide
details
R
%n Sustenance Support= 3ipro onl# pro"ides support &or the *unctionalit# %mplemented and !.Bects
'e"eloped during the %mplementation Phase An# Ee; Modules %mplementation= Ee; *unctionalit#
%mplementation= Change in !rgani6ation Structure= de"elopment o& Ee; Reports= %n&ocu.es= Pages ;ill .e
pro"ided a&ter initiating a Change Control Procedure
1(
Please discuss #our polic# regarding re-e+),n. 5/(/re +**-,3+(,on )o5(7+re 0er),on) (o /)er) ;ho ha"e
modi&ied so&t;are 9modi&ied either &or implementation at *E3A .# implementer or a 3rd part#: Please
indicate #our polic# regarding supporting these modi&ications / customi6ations in su.se,uent
"ersions/enhancements
R
SAP has a Roadmap o& Releasing *unctional Enhancements +;ice E"er# Hear %& the *unctionalit# released
.# SAP is &ound to .e use&ul &or *E3A= the same shall .e %mplemented Ao;e"er ;e ha"e &actored &or a
Minimal E&&ort o& $ da#s &or this acti"it# %& this calls &or more e&&ort .e#ond $ da#s including all the
+echnical R *unctional Resources re,uired &or implementing *unctional Set Enhancement= the same shall .e
routed through Change Control Procedure
11
%n case o& ne; )o5(7+re /*.r+de)= are the upgrades a"aila.le to *E3A &ree o& costG %& not= ;hat is the
polic#G Pro"ide details
R
ONeed C-+r,(1 5ro2 SAP on (4,) *-e+)eP
1$
%s 7e6E6+)ed )/**or( a"aila.leG 3hat &eatures are supportedG
R
!SS Connection ;ith SAP is pro"ided through the SAP Solution Manager ;hich ;ill pro"ide direct Support
Ser"ices &rom SAP SAP has de&ined the S@A?s &or the Support %ssues +he Support is pro"ided on $) N 0
model
Annex B: Appendix 3B- Compliance Sheet
Page 142 o& 42
C BIDDER Or.+n,B+(,on De(+,-)
C.1 Co2*+n1 Pro5,-e
9<indl# &urnish in&ormation &or each Bidder separatel# in case more than one Bidder is in"ol"ed:
eneral
Compan# Eame
'ate o& %ncorporation
Aolding Compan# or Parent Compan# 9i& an#:
Compan# local 9in 8AE: address
Contact details: Eame= phone= &ax and e-mail
Please pro"ide details o& o;nership: pri"ate/pu.licJ ultimate parentJ maBor
shareholders An# signi&icant changes in o;nership in the last t;o #earsG
3ho are the primar# shareholdersG 9Also indicate maBor shareholders ;ith
percentage holding in case o& limited companies:
Eum.er o& #ears in .usiness
Account Representati"e
Address and Phone
Financial !ac"#round $la%t &u'li%hed re&ort(
Annual Re"enue
Annual Eet %ncome
Please indicate ;hat percentage o& total re"enues o& the compan# is contri.uted
.# the ERP and related ser"ices 9%ndicate this &or 8AE as ;ell as international
operations o& the compan#:
Please pro"ide a histor# o& sales &igures during the past &i"e #ears
Please attach most recentl# a"aila.le annual report= and audited .alance sheets
and income statements &or pre"ious three #ears
An# pending or past litigation 9;ithin 3 #ears:G %& #es= please explain
Please also mention an# claims/complaints recei"ed in the last three #ears
)erti*ication%
Please pro"ide details o& an# ,ualit# process certi&ications 9eg SE% CMM etc:
An# other certi&ications= please speci&#
Sta**
+otal num.er o& emplo#ees
8AE
3orld-;ide
%n 8AE Please pro"ide a .reaC-up o& the num.er o& emplo#ees .# &unction= eg
Sales/marCeting
Administrati"e sta&&
Research R 'e"elopment
%mplementation sta&&
+echnical Support sta&&
!thers
Pro"ide details o& total num.er o& sCilled manpo;er in the organi6ation rele"ant
&or *E3A?s ERP implementation
Annex B: Appendix 3B- Compliance Sheet
Page 143 o& 42
*unctional ERP consultants 9&or the ERP &or ;hich implementation is
proposed:
+echnical experts
+eam leaders / ProBect managers
Mention location ;here the a.o"e manpo;er is located in 8AE /
;orld;ide
Eum.er o& implementations carried out in 8AE &or the ERP solution
Please pro"ide num.er o& implementations &or all the applications / modules
Sta** with Ara'ic S"ill%
@ist the o& total num.er o& sCilled manpo;er in the organi6ation rele"ant &or
*E3A?s ERP implementation ;hich is a.le to communicate 9oral and ;ritten:
in Ara.ic
*unctional ERP consultants 9&or the ERP &or ;hich implementation is
proposed:
+echnical experts
+eam leaders / ProBect managers
Mention location ;here the a.o"e manpo;er is located in 8AE /
;orld;ide
+n*ra%tructure
Pro"ide details o& Support Center &or the ERP ;hich is to .e implemented at
*E3A
%n&rastructure a"aila.le
@ocation o& ser"ice center
Manpo;er a"aila.le &or pro"ision o& support
Eum.er and re&erence names o& clients ;hich are supported &rom the
support center
Pro"ide details o& Research and 'e"elopment 9RR': center &or the ERP &or
;hich implementation is proposed
*acilities a"aila.le
+eam a"aila.le
@ocation o& the center
Alliance 'etween Other !idder% $*ill only i* multi&le !idder% involved(
Hears since alliance .et;een Bidders
Eature o& alliance 9marCeting= &inancial= etc: .et;een Bidders
Countries ;here the alliance is applica.le
Eum.er o& prior instances ;hen marCeting / .idding carried out together .# the
Bidders
Eum.er o& prior instances ;hen implementations carried out together .# the
Bidders Please pro"ide client names and countries
C.2 Re5eren3e S,(e De(+,-)
+he re&erence site details should .e gi"en in the &ollo;ing &ormat separatel# &or implementation
carried out A separate cop# should .e used &or each re&erence site
Compan# Eame
Compan# Address
+elephone Eum.er
Annex B: Appendix 3B- Compliance Sheet
Page 144 o& 42
*ax Eum.er
Contact Eame
+itle
3hat is or ;as the contact?s role in the implementation/
proBectG
State the duration o& the implementation
7o @i"e date &or the pilot location
3hich modules and "ersion o& the so&t;are are .eing
currentl# usedG
Pro"ide details o& extent o& customisation e&&ort re,uired on
the .ase so&t;are to meet the re&erred client?s re,uirements
9man-da#s= etc:
State ;hich o& the applications / modules 9;hich are
proposed to *E3A: ;ere implemented at the re&erence site
State i& the re&erence site includes integration .et;een
applications ;hich are proposed to *E3A 9in case the
applications proposed to *E3A ;ere implemented at
re&erence site:
3hat "ersion o& operating s#stem= data.ase etc is in useG
Are there an# other s#stem used in conBunction ;ith the
application so&t;are liCe &ront end s#stems etcG Please
pro"ide details i& an#
State num.er o& locations ;here this so&t;are is used
State the num.er o& emplo#ees= stores= etc ;hich ;ere
mapped in the s#stem
State= i& an#= inter&aces to external s#stems are implemented
at this site
State the role pla#ed .# the Bidder and its scope in the
proBect 9eg process mapping= data migration= training= etc:
%ndicate the role pla#ed .# the re&erence client during
implementation o& the product9s:
C.& E@*er,en3e o5 ,2*-e2en(,n. ,n (4e GCC/ UAE +nd ,n U(,-,(,e) ,n
(4e G/-5 re.,on
Pro"ide .elo; the num.er o& implementations in 7CC/ 8AE and speci&icall# in the utilit# industr#
%mplementations in 7CC .# industr# :
*inance
7o"t
8tilities
Pri"ate Companies
!thers
+otal
%mplementations in 8AE .# industr#:
*inance
7o"t
8tilities
Pri"ate Companies
!thers
+otal
Annex B: Appendix 3B- Compliance Sheet
Page 145 o& 42
Annex B: Appendix 3B- Compliance Sheet
Page 146 o& 42
D O(4er For2+()
D.1 For2 5or C-+r,5,3+(,on A/e)(,on)
For2 5or C-+r,5,3+(,on A/e)(,on)
Bidder?s Eame:
Bidder?s Address: 'ate Su.mitted:
I(e2 No. Se3(,on Re5eren3e P+.e No. Se3(,on
or
Ar(,3-e
No.
A/e)(,on/A/er1/C-+r,5,3+(,on/Co22en(
1
$
3
)
1
/
Annex B: Appendix 3B- Compliance Sheet
Page 147 o& 42
D.2 For2 5or De0,+(,on) 5ro2 RFP
Please outline all the de"iations in #our proposal &rom the scope= re,uirements and terms R conditions
de&ined in the R*P
'e"iations pro"ided in the +echnical Proposal ;hich is gi"en as an Appendix to this document
Sr.
No.
RFP Re5eren3e
;C4+*(er, Se3(,on<
De(+,-) o5 de0,+(,on)
Annex B: Appendix 3B- Compliance Sheet
Page 148 o& 42