C-SFMS - Mptreasury.org

C-SFMS
MIGRATION PROCESS
Department of Finance
Government of Madhya Pradesh
Directorate of Treasuries & Accounts,
Department of Finance,
Govt. of M.P.,
5th floor, Block -'A', Pariyavas Bhawan, Arera Hills, Bhopal
(M.P.)- 462016,
Web - www.mptreasury.org,
Page 1 of 41

Contents
1. izLrkouk
2. C-SFMS Structure ,oa Working
3. izfØ;k %&
A. lapkyuky;] dks"k ,oa ys[kk }kjk dh tkus okyh izfØ;k
B. dks"kky; }kjk dh tkus okyh izfØ;k
C. uksMy vf/dkjh }kjk dh tkus okyh izfØ;k
4. C-SFMS esa dh tkus okyh dk;Zokgh
Annexures:
ifjf'k"V&1 Check List for treasuries.
ifjf'k"V&2 Project Monitoring Committee (PMC)
ifjf'k"V&3 Activities to be performed under SWAN Connectivity
ifjf'k"V&4 Nodal Officers
ifjf'k"V&5 Network Status
ifjf'k"V&6 C- SFMS: Data Migration Methodology
ifjf'k"V&6a Check-list and certificate for data migration (At Treasury)
ifjf'k"V&6b Check-list and certificate for data migration (At DTA)
ifjf'k"V&6c Issue reporting list: Migration
ifjf'k"V&7 C-SFMS Migration Completion
ifjf'k"V&8 dks"kky; ds loZj dks lhycan djus laca/h izek.k i=k
ifjf'k"V&9 midks"kky; ,oa WDDF/FDDF/DPO mi;ksxdrkZ }kjk Transaction Completion
ifjf'k"V&10 SFMS Transaction Completion
ifjf'k"V&11 C-SFMS Application Software Rollout at Treasury
ifjf'k"V&12 C-SFMS: User Authentication and Accessibility
Page 2 of 41

C-SFMS
MIGRATION PROCESS
-------
1. izLrkouk
1) ,dhd`r dks"kky;hu dEI;wVjkbZts'ku ifj;kstuk vUrxZr lapkfyr jkT; foRrh;
izca/u iz.kkyh (SFMS) dks Distributed Architecture ls
Centralized Architecture esa ifjofrZr djus dk fu.kZ; e0iz0'kklu] foRr
foHkkx }kjk fy;k x;k gSA
2) SFMS dk C-SFMS esa ifjorZu pj.kc¼ rjhds ls fd;k tkuk gSA
3) C-SFMS ds lapkyu gsrq ,Iyhds'ku lkiQ~Vos;j vUrxZr data migration,
merging, maintenance bR;kfn dk dk;Z lh0,e0lh0 fyfeVsM dks lkSaik
x;k gSA
4) C-SFMS data centre ds gkMZos;j‚lkiQ~Vos;j dk iznk;] laLFkkiu ,oa vuqj{k.k
dk dk;Z IFMIS vUrxZr gq;s djkj vuqlkj Vh0lh0,l0 dks lkSaik x;k gSA
5) C-SFMS ds fy;s Network laca/h dk;Z] MPSEDC ds ek?;e ls laLFkkfir
gks jgs MPSWAN connectivity dks primary network ds :i esa Setup dj
leLr dks"kky;‚midks"kky; esa fd;k tk jgk gSA
2. C-SFMS Structure ,oa Working :-
1) C-SFMS vUrxZr lapkyuky; ij data centre dk fuekZ.k fd;k x;k gSA
2) C-SFMS data centre (DC) esa LFkkfir izR;sd equipment tSls UPS,
Servers, Firewall, Routers, Switch dks high availability vFkkZr~
dual‚nksgjs :i esa laLFkkfir fd;k x;k gSaA
3) C-SFMS D.C. esa LFkkfir Database Server(Oracle DB 10g) Hkh nks
LFkkfir fd;s x;s gSa ftlesa ls ,d Stand by ds :i esa dk;Z djsxkA
4) C-SFMS D.C. esa rhu Application Server(Oracle 11g) LFkkfir fd;s x;s
gSa ,oa rhuksa dks load balancer device ls Integrated :i ls vPNk
Performance nsus gsrq laLFkkfir fd;k x;k gSA
5) mijksDr fcUnqvksa esa of.kZr Database ,oa Application Server ij lh0,e0lh0
}kjk Application Software migrate/configure fd;k x;k gSA blh DB
Server ij izns'k ds leLr dks"kky; ds Database dks merge o migrate
fd;k tkosxkA
Page 3 of 41

6) tks Hkh dks"kky; uhps of.kZr izfdz;k vuqlkj C-SFMS vUrxZr merge gksrs
tk;saxs] muds dks"kky; vUrxZr application software ds leLr mi;ksxdrkZ
lapkyuky; esa laLFkkfir Application server ds ekè;e ls dks"kky;hu
lcflLVe (WDDF/FDDF/SLIM/DPO lfgr) access dj dk;Z laikfnr
djsaxsA
7) C-SFMS ds iw.kZr% laLFkkfir (SFMS ds pkjksa lcflLVe Treasury/JD/
FMIS/DTA) gks tkus ds i'pkr~ jkT; ds izR;sd dks"kky;hu laO;ogkj
(Transaction) Real-Time gks ldsaxs vFkkZr~ budget distribution, reappropriation,
re-allocation, surrender, employee data transfer, global
masters updation and MIS real-time basis ij dsUnzh; :i esa laHko gks
ldsxkA
8) C-SFMS ds vUrxZr Networking dks Hkh fofHkUu izdkj ls C-SFMS D.C.
ls high availability esa j[kk x;k gSA dks"kky; ,oa midks"kky; dh izkFkfed
connectivity MPSWAN ls jgsxhA
9) dks"kky; ij MPSWAN connectivity down gksus ij Application
software dk access dks"kky; esa LFkkfir VPNoBB ,oa VSAT ds ekè;e
ls gks ldsxkA
10) midks"kky; esa MPSWAN down gksus ij VSAT ds ek?;e ls
connectivity gks ldsxh
11) vU; mi;ksxdrkZ (FDDF/WDDF/DPO/SLIM) VPNoBB ds ekè;e ls
centralized Application Access dj ldsaxsA
12) C-SFMS vUrxZr Application software access djus gsrq fuEu URL
address vius Windows Computer ds Internet Explorer ij fy[ksa %&
3. izfdz;k %&
http://10.5.11.X< ________ >
C-SFMS ds izkFkfed lapkyu gsrq ftyk dks"kky;] Hkksiky(midks"kky; lfgr)
,oa ftyk dks"kky; jk;lsu(midks"kky; lfgr) dks C-SFMS esa ik;ysV VsfLVax gsrq
pquk x;k gSA mijksDr nksuksa dks"kky; es C-SFMS ds lqpk: lapkyu gks tkus i'pkr~
izns'k ds leLr dks"kky;‚midks"kky; dks C-SFMS vUrxZr merge fd;k tkuk
izLrkfor gSA izLrkfor migration schedule i`Fkd ls lwfpr fd;k tk;sxkA Data
merging o migration dh izfØ;k fuEukuqlkj jgsxh %&
Page 4 of 41

(A) lapkyuky;] dks"k ,oa ys[kk }kjk dh tkus okyh izfØ;k %&
1) lapkyuky; dh Project Monitoring Committee (PMC) (ifjf'k"V&2) ;g
lqfuf'pr djsxh dh C-SFMS data centre ds leLr laLFkkiu laca/h dk;Z iw.kZ
gks x;s gSaA
2) Data Centre esa laLFkkfir lHkh equipment dh acceptance
testing/commissioning gks xbZ gS (IFMIS Cell ;g lqfuf'pr djsxk) ,oa
lHkh device lqpk: :i ls dk;Z dj jgs gSA
3) lh0,e0lh0 ;g lqfuf'pr djsxh fd ,Iyhds'ku lkiQ~Vos;j ls lacaf/r lHkh
configuration dj fy;s x;s gS ,oa C-SFMS Project Monitoring Committee
(PMC) dks Mseks iznku dj fn;k x;k gSA
4) C-SFMS ds lapkyu ,oa data migration dh izfØ;k dsk le>us gsrq ,d
fnol dk izf'k{k.k lapkyuky; esa lgk;d izksxzkej }kjk lacaf/r uksMy vf/dkjh
dh mifLFkfr esa fn;k tk;sxkA bl izf'k{k.k esa dks"kky; vf/dkjh] lgk;d
izksxzkej ,oa ,d deZpkjh tks SFMS vUrxZr routine technical dk;Z esa fuiq.k
gks] mifLFkr gksdj izf'k{k.k izkIr djsaxsA mDr izf'k{k.k esa mijksDr rhuksa
vf/dkfj;ksa dh mifLFkfr vfuok;Z gSA
5) Data migration dh izfdz;k 'kq: djus ls iwoZ C-SFMS Project Monitoring
Committee (PMC) lacaf/r dks"kky; ls ;g lqfuf'pr djsxk dh muds
dks"kky;‚midks"kky; esa primary (SWAN/VPNoBB) /secondary(VSAT)
dh connectivity laLFkkfir gks xbZ gS ,oa lqpk: :i ls dk;Z dj jgh gSA
mijksDr gsrq funsZ'k ,oa izfØ;k lapkyuky; }kjk tkjh fd;s x;s gSa iqu% izfØ;k
ifjf'k"V&3 ij layXu gSA
6) Data migration/merging ds dk;Z esa liksVZ gsrq lapkyuky; }kjk uksMy
vkWfiQlj fu;qDr fd;s x;s gSa tks dh ifjf'k"V&4 ij layXu gSA
(B) dks"kky; }kjk dh tkus okyh izfØ;k %&
lapkyuky; ls funsZ'k izkIr gksus ij dks"kky; (midks"kky; lfgr) dks data
migration laca/h dk;Zokgh iw.kZ djuh gksxh tks fd fuEukuqlkj gS %&
1) Lakiw.kZ izfdz;k esa fdlh izdkj dh ykijokgh ;k xyrh ik;s tkus ij dks"kky;
vf/dkjh Lo;a ftEesnkj gksaxsA vr% dks"kky; vf/dkjh gj dk;Z Lo;a viuh
mifLFkfr esa laikfnr djuk ‚ djkuk lqfuf'pr djsaA
Page 5 of 41

2) C-SFMS ds lapkyu ,oa data migration dh izfØ;k dsk le>us gsrq ,d
fnol dk izf'k{k.k lapkyuky; esa lgk;d izksxzkej }kjk lacaf/r uksMy vf/dkjh
dh mifLFkfr esa fn;k tk;sxkA bl izf'k{k.k esa dks"kky; vf/dkjh] lgk;d
izksxzkej ,oa ,d deZpkjh tks SFMS vUrxZr routine technical dk;Z esa fuiq.k
gks] mifLFkr gksdj izf'k{k.k izkIr djsaxsA mDr izf'k{k.k esa mijksDr rhuksa
vf/dkfj;ksa dh mifLFkfr vfuok;Z gSA
3) loZizFke vius dks"kky; esa usVodZ dh miyC/rk lqfuf'pr djsa ftlesa primary
network (SWAN/VPNoBB) ,oa secondary network (VSAT) dk lqpk:
lapkyu gks jgk gS rRlaca/h iqf"V vius dks"kky; es inLFk vFkok lEc¼ lgk;d
izksxzkej ls djk ysaA rRlaca/h fjiksVZ lapkyuky; ds uksMy vkfiQlj dks
ifjf'k"V&5 vuqlkj miyC/ djk;saA
4) lh0,e0lh0 }kjk dsUnzh; :i ls lHkh dks"kky; loZj ij migration patch run
dj fn;k tk;sxkA dks"kky; vf/dkjh ;g lqfuf'pr djsa fd lh0,e0lh0 }kjk
migration patch iznk; dj fn;k x;k gS bldh iqf"V CMC help desk ls dj
ysaA
5) ftl fnol migration dh frfFk fu/kZfjr dh xbZ gS ml fnu vius dks"kky; ls
lacaf/r leLr midks"kky; WDDF, DPO, FDDF ds mi;ksxdrkZvksa dks
dks"kky; esa mifLFkr djok ysaA
6) Treasury server ds leLr mi;ksxdrkZvksa dks ;g lqfuf'pr djuk gksxk fd
mUgksaus vkt fnukad (migration patch pykus ds iwoZ) rd ds leLr ysu&nsu
(transaction) iw.kZ dj fy;s gS vkSj dksbZ Hkh dk;Z yafcr ugha gSA
7) dks"kky; vf/dkjh ,oa mi;ksxdrkZ (WDDF/FDDF/DPO/Sub Treasury)
ifjf'k"V&6 ij nh xbZ migration method vuqlkj dk;Zokgh lqfuf'pr djsaxs
,oa izek.k i=k ds lkFk ifjf'k"V& 6a vuqlkj SFMS checklist Hkh iw.kZ dj
layXu djsaxsA
8) dks"kky; vf/dkjh Lo;a vius dks"kky; ds izek.k i=k(ifjf'k"V&7vuqlkj)ds
lkFk&lkFk vU; lHkh mi;ksxdrkZvksa ls izek.k i=k izkIr djsaxs(ifjf'k"V&8
vuqlkj)A Migration izfØ;k iw.kZ gksus ij ;fn dksbZ folaxfr ikbZ tkrh gS rks
gLrk{kjdrkZ Lo;a ftEesnkj gksaxsA
9) dks"kky; ds MkVkcsl dks dsUnzh; MkVkcsl esa ;Fkkor~ migrate fd;k tk;sxkA vr%
bl ckr dh iqf"V vko';d gS fd tks data/information/transaction
treasury database esa gS og ;Fkkor~ dsUnzh; MkVkcsl esa laLFkkfir gksA
10) Migration verification gks tkus ds i'pkr~ fy;s x;s MkVk cSdvi
(export backup) ,oa full backup dh nks izfr;ksa(lkiQ~Vdkih) ds lkFk
dks"kky; vf/dkjh ,oa lgk;d izksxzkej Lo;a lapkyuky; esa okafNr lHkh izek.k
Page 6 of 41

i=k‚izfrosnuksa ds lkFk mifLFkr gksaxs ,oa lacaf/r uksMy vf/dkjh dks viuh
mifLFkfr nsaxsA
11) dks"kky; vf/dkjh MkVk cSdvi dh nks izfr (lkiQ~Vdkih) dks"kky; ds LVªkWx :e
esa seal dj j[kuk lqfuf'pr djsaxs ,oa C-SFMS varxZr dh xbZ dk;Zokgh ls
vius ftys ds dysDVj dks lwfpr dj lapkyuky; esa mifLFkr gksus dk vkns'k
izkIr djsaxsA
12) dks"kky; vf/dkjh ,oa lgk;d izksxzkej dk ;g nkf;Ro gksxk fd data
migration dk data backup yssus ds i'pkr~ Database server o
Application server dks power down djds seal djsaxs ,oa lapkyuky; ds
vkxkeh vkns'k rd lhycan gh j[kk tkuk lqfuf'pr djsaxsA seal dk eryc ;g
gS fd fdlh Hkh izdkj ls loZj dk mi;ksx ugha fd;k tk;sA vr% loZj dk door
lock dj mls seal djsaA ;fn fdlh dkj.ko'k loZj dk door [kjkc gS rks loZj
ds front panel esa yxs pkjksa screws ,oa rear panel dh power supply
socket dks seal djsaA
13) Server dks power down o lhycan dj fn;k x;k gS bl vk'k; dk
izek.k i=k Hkh ifjf'k"V&9 vuqlkj layXu dj lapkyuky; esa tek djsaxsA
mijksDr dk;Zokgh dk vk'k; ;g gS fd ,d ckj data, migration gsrq capture
dj fy;k x;k gS rks iqu% fcuk vuqefr dks"kky; server ls application
access u gksA
14) lapkyuky; esa MkVk cSdvi dh nksuksa izfr izek.k i=k ,oa izfrosnu uksMy
vf/dkjh dks nsus ds i'pkr~ dks"kky; vf/dkjh ,oa lgk;d izksxzkej data
migration dh izfdz;k iw.kZ gksus rd lapkyuky; esa gh mifLFkr jgsaxsA uksMy
vf/dkjh dks"kky; vf/dkjh dks successful migration certificate
ifjf'k"V&10 vuqlkj iznku djsaxsA dks"kky; vf/dkjh ,oa lgk;d izksxzkej
mijksDr izek.k i=k izkIr gksus ds ckn gh lapkyuky; ls izLFkku djsaxsA
15) uksMy vf/dkjh ,oa DBA / lgk;d izksxzkej Lo;a dh mifLFkfr esa dks"kky;
vf/dkjh ,oa lgk;d izksxzkej ds le{k] C-SFMS checklist ifjf'k"V&6b
vuqlkj dk;Zokgh djsaxs ,oa dks"kky; ls ykbZ xbZ SFMS checklist ifjf'k"V&6a
ls feyku djuk lqfuf'pr djsaxsA fdlh Hkh izdkj dh folaxfr ikbZ tkus ij
uksMy vf/dkjh ,oa dks"kky; vf/dkjh lh0,e0lh0 fyfeVsM dks fyf[kr esa
ifjf'k"V&6c vuqlkj lwfpr djrs gq;s folaxfr dk funku djsaxsA
16) Data Migration ds nkSjku vlkekU; folaxfr gksus ij vk;qDr dh
vuqefr izkIr dh tkuh gksxh ,oa vuqefr izkIr gksus ij gh iqu% dks"kky; loZj
dh lhy [kksyus ,oa iqu% dks"kky; Lrj ls dk;Z izkjEHk fd;k tk ldsxkA folaxfr
dk funku gks tkus ds i'pkr~ iqu% Data Migration dh izfØ;k nksgjkuh gksxhA
Page 7 of 41

17) C-SFMS esa Data Migration djus dh izfØ;k esa lh0,e0lh0 }kjk ,Iyhds'ku
lkiQ~Vos;j ds access, functionality, activity, process bR;kfn esa dksbZ ewyHkwr
ifjorZu ugha fd;k x;k gSA vr% end user dks distributed ls Centralized
environment esa transition dk dksbZ izHkko ekywe ugha iM+sxkA
18) C-SFMS esa Application dks Access djus gsrq ek=k
Browser(Internet Explorer) ij URL Change djuk gksxk ftls leLr
Computer/Clients ij save djuk gksxkA mDr dk;Zokgh dks"kky; ds vFkok
lEc¼ dks"kky; ds lgk;d izksxzkej }kjk laikfnr dh tkosxhA
C. uksMy vf/dkjh }kjk dh tkus okyh izfØ;k %&
1) uksMy vf/dkfj;ksa }kjk loZizFke laapkyuky; ds lgk;d izksxzkej ls izf'k{k.k izkIr
fd;k tk;sxk rkfd os lacaf/r dks"kky;ksa dks vko';drk vuqlkj izf'k{k.k nsdj
vko';d monitoring dj ldsA
2) Migration gsrq dks"kky; dk p;u gksus ds i'pkr~ dks"kky; ij dh tk jgh
izfØz;k dh monitoring ,oa laiw.kZ izfØ;k ds iw.kZ gksus rd dh leLr dk;Zokgh
djuh gksxhA
3) dks"kky; dh Vhe ds lapkyuky; esa mifLFkr gksus ds i'pkr~ izek.k i=k ,oa
izfrosnu dh tkap djuk ,oa MkVk cSdvi dks lh0,e0lh0 ds izfrfuf/ dks
lkSaiuk gksxkA
4) Data migration gks tkus ds i'pkr~ iqu% C-SFMS check list ls feyku dj
dks"kky; ny dks larq"V djrs gq;s ifjf'k"V&10 vuqlkj izek.k i=k lkSaiuk gksxkA
5) vxys fnol tc dks"kky; vf/dkjh vius dks"kky; ij igqapdj C-SFMS dks
access djsaxss rks uksMy vf/dkjh ,oa DBA / lgk;d izksxzkej ifjf'k"V&11 vuqlkj
izfrosnu izkIr djsaxs fd dks"kky; dk dk;Z iwoZ dh rjg izkjEHk gks x;k gSA
4. C-SFMS esa dh tkus okyh dk;Zokgh %&
1) (lapkyuky; ,oa dks"kky;‚midks"kky;ksa ds fy;s)C-SFMS esa ,Iyhds'ku
lkiQ~Vos;j vUrxZr look and feel, functionality, logic bR;kfn esa dksbZ Hkh
ewyHkwr ifjorZu (SFMS esa) ugha fd;k x;k gSA
2) C-SFMS esa data migration gks tkus ij lapkyuky; esa uksMy vkf/dkjh
vFkok ekLVj 'kk[kk }kjk dks"kky; vf/dkjh dk ykWfxu cuk;k tk;sxk ,oa
rRi'pkr~ dks"kky; vf/dkjh }kjk iwoZor~ vU; ykWfxu password create fd;s
tkdj role vuqlkj dk;Z vkoafVr fd;s tk;saxsA
Page 8 of 41

3) C-SFMS ij Hkh user access ,oa password policy SFMS dh gh rjg
ykxw gksxhA
4) dks"kky; vf/dkjh ds vodk'k ij tkus vFkok dk;ZHkkj lkSaius dh n'kk esa
lapkyuky; ds uksMy vf/dkjh vFkok ekLVj 'kk[kk dks lwfpr djuk gksxkA
5) dsUnzh; MkVkcsl ykxw gksus ij login/password dks secured j[kuk ;wtj dh
Lo;a dh ftEesnkjh gSA bl ckr dh lwpuk dks"kky; vf/dkjh lHkh user dks
fyf[kr :Ik ls nsa vkSj ikloMZ ikWfylh dk ikyu lqfuf'pr djk;sa A
6) User access and roles laca/h fooj.k ifjf'k"V&12 ij layXu gSA d`I;k budk
vè;;u djsaA user dh mapping employee code ls j[kh xbZ gS vr% ;fn
employee dk LFkkukarj.k ,d dks"kky; ls vU; dks"kky; esa gksxk rks
employee transfer ds lkFk mlds ;wtj ykWfxu Lo;a fuf"Ø; gks tk;saxsA
7) Employee ;w0vkbZ0Mh0 tujs'ku izfØ;k izkjEHk gks xbZ gSA vr% biometric
data miyC/ gksus ij login access o approval screen laca/h access dks
biometrics ls authenticate fd;k tkuk izLrkfor gSA
8) C-SFMS ds ykxw gksus ds i'pkr~ fn;s x;s lHkh funsZ'kksa dk ikyu dM+kbZ ls
djuk ‚ djkuk lqfuf'pr djsa‚djk;saA
9) C-SFMS esa software access central database ls gksuk gSA vr% ;g vfr
vko';d gS fd ,Iyhds'ku dk mi;ksx vko';drk vuqlkj gh gks vU;Fkk
application ds performance ij foijhr izHkko iM+ ldrk gSA
10) C-SFMS ls lacaf/r fdlh Hkh izdkj dh queries‚iz'u gsrq uksMy vf/dkjh ls
laidZ djsaA
Page 9 of 41

Check list for Treasuries to submit at DTA:
ifjf'k"V&1
ifjf'k"V&5 Network Status
ifjf'k"V&6a Check-list and certificate for data migration (At Treasury)
ifjf'k"V&6b Check-list and certificate for data migration (At DTA)
ifjf'k"V&6c Issue reporting list: Migration
ifjf'k"V&7 C-SFMS Migration Completion
ifjf'k"V&8 dks"kky; ds loZj dks lhycan djus laca/h izek.k i=k
ifjf'k"V&9 midks"kky; ,oa WDDF/FDDF/DPO mi;ksxdrkZ }kjk Transaction Completion
ifjf'k"V&10 SFMS Transaction Completion
ifjf'k"V&11 C-SFMS Application Software Rollout at Treasury
Page 10 of 41

ifjf'k"V&2
lapkyuky;]dks"k ,oa ys[kk] eè; izns'kA
‚‚vkns'k‚‚
dzekad‚MhVh,‚ SFMS/‚2011‚291 Hkksiky]fnukad 26&2&11
jkT; 'kklu }kjk orZeku jkT; foRrh; izca/u iz.kkyh SFMS dks orZeku fMLVªhC;wVsM vkdhZVsDpj
ds LFkku ij dsUnzh;d`r vkdhZVsDpj iz.kkyh ij fdz;kfUor djus ds mn~ns'; ls C-SFMS
(Centralised State Financial Management System) gsrq esllZ lh0,e0lh0 fyfeVsM dks fnukad
25&1&2011 dks vuqcaf/r fd;k x;kA
2& dsUnzh;d`r vkdhZVsDpj iz.kkyh esa izLrko O;oLFkk vUrxZr fdz;kUo;u] izkstsDV Iyku] vfrfjDr
iQaD'kafufyVh gsrq ,l0vkj0,l0 (Software Requirement Specification) ,l0Mh0Mh0 (Software
Design Document)] MkVkcsl loZj ,oa ,Iyhds'ku loZj dk la;kstu] Mseks] ik;ysV VsfLVax (ftyk
dks"kky;] Hkksiky ,oa ftyk dks"kky; jk;lsu) ,oa xks ykbZo vkfn xfrfof/;ksa ds ijh{k.k‚ lq>ko gsrq
rRdky izHkko ls fuEukuqlkj lfefr;ka cuk;h tkrh gS %&
ldz fo"k; lfefr esa lfEefyr vf/dkjh dk uke‚inuke
1 ifj;kstuk fdz;kUo;u ,oa izkstsDV
Iyku
2 ,l0vkj0,l0 (Software
Requirement Specification)
,l0Mh0Mh0 (Software
Design Document)
ik;ysV VsfLVax
(ft0dks0Hkksiky ,oa ftyk
dks"kky; jk;lsu)
3 MkVkcsl loZj‚ ,Iyhds'ku loZj
dk la;kstu
1& Jh o:.k oekZ] vij lapkyd] lapkyuky; vè;{k
2& Jh ts0ds0'kekZ] la;qDr lapkyd] lapkyuky;
3& Jh gsear ukiQMs] lgk;d lapkyd] lapkyuky;
4& Jh Vh0,l0feJk] rF;kad iz'kkld] lapkyuky;
5& Jh uhjt f=kosnh] lgk;d izksxzkej] lapkyuky;
1& Jh egs'k xqIrk] ftyk dks"kky; vf/dkjh] Hkksiky
2& Jh jkts'k flag foU?;kpy dks"kky; vf/dkjh]Hkksiky
3& Jh vkj0lh0tSu] dks"kky; vf/dkjh] jk;lsu
4& Jh gsear ukiQMs] lgk;d lapkyd] lapkyuky;
5& Jh iznhi vksadkj] vfr0dks0v0]foU?;kpy Hkksiky
6& Jh jkds'k lDlsuk] vfr0dks0v0]ftyk0dks0Hkksiky
7& Jh yfyr fctykuh] l0dks0v0]ft0dks0Hkksiky
8& Jh yksds'k frokjh] lgk;d izksxzkej] lapkyuky;
9& dq0 ek/qjh y[ksjk] lgk;d izksxzkej] dks"kky;]jk;lsu
10& dq0 dqyoarh [ky[kks] l0izks0]ftyk dks"kky;]Hkksiky
1& Jh gsear ukiQMs] lgk;d lapkyd] lapkyuky;
2& Jh Vh0,l0feJk] rF;kad iz'kkld] lapkyuky;
3& Jh uhjt f=kosnh] lgk;d izksxzkej] lapkyuky;
4& dq0 dqyoarh [ky[kks] l0izks0]ftyk dks"kky;]Hkksiky
leLr lnL; le;&le; ij gksus okyh cSBdksa esa mifLFkr gksdj C-SFMS dh xfrfof/;ksa dk
ijh{k.k dj lq>ko ‚ lgefr ls voxr djkus dk d"V djsaA
(vk;qDr }kjk vuqeksfnr)
vij lapkyd
i`0dzekad‚MhVh,‚ SFMS/‚2011‚292 Hkksiky]fnukad 26&2&11
izfrfyfi%&lacaf/r vf/dkjh‚deZpkjh Jh &&&&&&&&&&&&&&&&&&&&&&&&&&&&& dh vksj
lwpukFkZ ,oa vko';d dk;Zokgh gsrq vxzsf"krA
vij lapkyd
Page 11 of 41

Activities to be performed under SWAN Connectivity:
Activity at Treasury:
ifjf'k"V&3
1. MPSEDC under SWAN will provide a router, receive it and ask the concerned
person (Tulip engineer) to install this router in network RACK.
2. If connectivity is to be provided via leased line BSNL will provide a separate
copper pair till the network RACK and will supply a modem/NTU which will be
installed in network RACK.
3. Once the line is connected by BSNL, ask the SWAN (Tulip) engineer to terminate
the connection from NTU to the existing ROUTER on the serial port 0/0. (If
SWAN(Tulip) engineer wishes to test the line on their router allow him to do so
for confirmation that router is working and configured)
4. If connectivity is provided by SWAN POP centre over LAN then the line will be
terminated on the Ethernet port of the router, MPSEDC(under SWAN) will
provide additional Ethernet port for their router as well as for existing router and
will configure the routers for the required connectivity.
5. Note down the IP address of the serial port/Ethernet port issued by SWAN office
and inform DTA by email so that further necessary configurations are made.
6. After adding the configuration from DTA, your primary connectivity will be from
SWAN with a better response time and then VSAT network will act as backup
connectivity.
7. Switch off the ROUTER which has been provided by SWAN office this will be
used as stand by if existing router fails.
8. Do not connect SWAN router to SWITCH.
9. To test the performance of the SWAN network do the following
a. Ping 10.5.11.101
b. Ping 172.18.12.106
c. Test email is working
d. Test the employee application by connecting DTA Application server
e. Send the status to DTA by email.
Activity at Joint Director Office:
1. MPSEDC (SWAN) will provide a router, receive it and ask the concerned person
(Tulip engineer) to install this router in network RACK.
Page 12 of 41

2. BSNL will provide a separate copper pair till the network RACK and will supply a
modem/NTU which is to be installed in network RACK.
3. Once the line is connected, ask the SWAN (Tulip) engineer to terminate the
connection from NTU to the ROUTER supplied by SWAN office on the serial port
0/0.
4. If connectivity is provided by SWAN POP centre over LAN then the line will be
terminated on the Ethernet port of the router, MPSEDC (SWAN) will provide
additional Ethernet port for their router.
5. Connect SWAN router to SWITCH on eth 0/0 and VSAT on eth 0/1
6. Contact Essel Shyam (Bhopal help desk centre) to change the configuration of
the VSAT (IDU) (details of IP scheme has already been provided to SWAN and
ESCL.)
7. Gateway of your computers would be here X is the district code. Do
not change the IP Gateway of your application server.
8. Note down the IP address of the serial port issued by SWAN office and inform
DTA by email so that further necessary configurations are made.
9. After adding the configuration from DTA, your primary connectivity will be from
SWAN with a better response time and VSAT network will act as a backup
connectivity.
10. To test the performance of the SWAN network do the following
a. Ping 10.5.11.101
b. Ping 172.18.12.106
c. Test email is working
d. Send the status to DTA by email.
Activity at Sub Treasury Office:
1. MPSEDC (SWAN) will provide a router, receive it and ask the concerned person
(Tulip engineer) to install this router in network RACK.
2. BSNL will provide a separate copper pair till the network RACK and will supply a
modem/NTU which is to be installed in network RACK.
3. Once the line is connected, ask the SWAN engineer to terminate the connection
from NTU to the ROUTER supplied by SWAN office on the serial port 0/0.
4. If connectivity is provided by SWAN POP centre over LAN then the line will be
terminated on the Ethernet port of the router, MPSEDC (SWAN) will provide
additional Ethernet port for their router.
5. Connect SWAN router to SWITCH on eth 0/0 and VSAT on eth 0/1.
Page 13 of 41

6. Contact Essel Shyam (help desk centre Bhopal) to change the configuration of
the VSAT (IDU) (details of IP scheme has already been provided to SWAN and
ESCL.)
7. IP Gateway of the client would be 10.X.Y.1 (X is the district code and Y is the sub
treasury code sequence)
8. Note down the IP address of the serial port issued by SWAN office and inform
DTA by email so that further necessary configurations are made.
9. After adding the configuration from DTA, your primary connectivity will be from
SWAN with a better response time and VSAT will act as a backup connectivity.
10. To test the performance of the SWAN network do the following
a. Ping 10.5.11.101
b. Ping 10.X.1.101 (X is the treasury id)
Page 14 of 41

ifjf'k"V&4
lapkyuky;]dks"k ,oa ys[kk]
eè; izns'k
‚‚vkns'k‚‚
Øekad‚MhVh,‚ C-SFMS‚2011‚ Hkksiky]fnukad
,dhd`r dks"kky;hu dEI;wVjkbZts'ku ifj;kstuk vUrxZr lapkfyr jkT; foRrh;
izca/u iz.kkyh (SFMS) dks distributed architecture ls centralized architecture
esa ifjofrZr fd;k tk jgk gSA Migration izfØ;k dk foLrkj iwoZd ys[k migration
process document esa fd;k x;k gS (ifjf'k"V&2)A mijksDrkuqlkj izfdz;k lEiknu gsrq
laHkkxokj fuEukuqlkj uksMy vf/dkjh ukekafdr fd;s tkrs gSa %&
l- uksMy vf/dkjh dk ukekafdr laHkkx fyad vf/dkjh nwjHkk"k uEcj
Ø- uke ,oa inuke
1 Jh fnus'k f}osnh] jhok ('kgMksy dks Jh fou; izdk'k 94250-06252
mi lapkyd 'kkfey djrs gq;s) prqosZnh
2 Jh fou; izdk'k
prqosZnh] mi lapkyd
lkxj Jh fnus'k f}osnh 94250-78226
3 Jh lat; dqekj] Hkksiky(gks'kaxkckn dks Jh gsear ukiQM+s 98934-38250
lgk;d lapkyd 'kkfey djrs gq;s)
4 Jh gsear ukiQM+s]
lgk;d lapkyd
bankSj Jh lat; dqekj 94256-80042
5 Jh larks"k pks[kkUnzs] tcyiqj Jh iznhi 99263-84017
lgk;d lapkyd
ejdke
6 Jh iznhi ejdke] Xokfy;j(pacy dks Jh larks"k 94253-77099
lgk;d lapkyd 'kkfey djrs gq;s) pks[kUnzs
7 Jh ujsUnz /qosZ] mTtSu Jh iznhi 98937-74654
lgk;d lapkyd
ejdke
uksMy vf/dkjh }kjk migration process vuqlkj dk;Zokgh dh tk;sxh rduhdh
lykg lapkyuky; esa inLFk Mh0ch0,0‚lgk;d izksxzkej }kjk nh tkosxhA Migration
process dk laiw.kZ nkf;Ro uksMy vf/dkjh dk jgsxkA
vk;qDr]
dks"k ,oa ys[kk
Page 15 of 41

i`0dzekad‚MhVh,‚ C-SFMS‚2011‚ Hkksiky]fnukad
izfrfyfi%&
1& leLr dysDVj]e0iz0A
2& leLr laHkkxh; la;qDr lapkyd]dks"k ys[kk ,oa isa'ku]e0iz0A
3& leLr dks"kky; vf/dkjh]e0iz0A
4& leLr uksMy vf/dkfj;ksa dh vksj ikyukFkZA d`Ik;k migration process document
dk lko/kuh iwoZd vè;;u dj ysaA
5& leLr Mh0ch0,0‚ lgk;d izksxzkej] e0iz0A
6& izkstsDV eSustj] esllZ lh0,e0lh0 fyfeVsM]HkksikyA
dh vksj lwpukFkZ ,oa vko';d dk;Zokgh gsrq vxzsf"krA
vij lapkyd
Page 16 of 41

ifjf'k"V& 5
izek.k i=k
Network Status
izekf.kr fd;k tkrk gS fd ftyk‚uxj dks"kky; &&&&&&&&&& esa LAN
(Local Area Network) lgh dk;Z dj jgk gSA dks"kky; esa SWAN Connectivity
fnukad &&&&&&& dks laLFkkfir gks xbZ gS ,oa primary network SWAN
connectivity ij py jgk gSA SWAN ds laLFkkiu ds lkFk ;g Hkh VsLV dj fy;k
x;k gS fd SWAN Connectivity fail gksus ij WAN Connectivity VSAT ij
switch over gks tkrh gSA
dks"kky; ds leLr midks"kky;ksa esa Hkh mijksDr of.kZr izfØ;k dj yh xbZ gS gSA
lgk;d izksxzkej dks"kky; vf/dkjh
uke % uke%
eqnzk % eqnzk %&
fnukad
Page 17 of 41

C- SFMS: Data Migration Methodology
Migration Steps and approach:
Annexure – 6
1. A ‘Centralization Application Migration Patch’ would be released for
migration to CSFMS, this will be applied centrally which would consist of
the following activities:
a. Checking the application for readiness for migration (i.e. completion
of the required transactional cycles).
b. Set the application for migration (once this activity is performed no
functional operation would be allowed).
c. Pre migration reports and control reports (available on migration
mode interface).
d. Shell script for migration data dump creation (export backup its
compression/fullbackup and its compression) and process of
applying of checksum /encryption.
A readme would be provided along with the patch set for “Instructions
to do”.
2. For migration, the authorized login (treasury officer) would check the
readiness for migration. For checking purpose a screen / report would be
provided to check the status of pending transaction, for migration the
recommended pendency is zero. System would check that :
i. The bill cycle need to be completed with cheque
generations/ objection.
ii. No E-payment bills should be pending with advice
generation. (All the E-payments files which are generated
and pending should be uploaded on CINB-SBI).
iii. The data transferred from DTA has been loaded in the
system. (ETL status)
iv. The Data to be transferred from treasury has been
transmitted.(ETL status)
v. No transaction is un-committed. (incomplete)
The screen for checking migration is as follows:
Page 18 of 41

Checking for Migration
Page 19 of 41

3. The status of the pending transactions should be zero/Nil, take the printout
of the report. If status is showing pending transactions clear all the
transactions to ensure that pending transactions are set cleared and the
report is set to nil else you will not be able to set the application in
Migration mode.
4. Now the authorized login (treasury officer) would go to the menu and
choose the option for “Set in Migration Mode”. Once he clicks on the
button, system would check for readiness once again, if system is not
ready a message would be reported. If application is ready, the system
would mark the application for migration, and would automatically exit
from the application.
Prior to the final set system would again prompt for login authentication.
Page 20 of 41

Page 21 of 41

Once the system is “Set for Migration” no transactions would be allowed
in the system and system would be available in migration mode only.
5. Treasury officer and sub-treasury officers would be allowed to login into
the system in migration mode, but would not able to make any
transactions. They would be able to view their specific reports only.
Treasury Officer should go to “Report menu” section where he would find
the reports. Treasury officer would have additional reports on transactional
sequence and summarized control figures.
• Transactional sequences: This report would provide the last
transactional sequences like receipt number, advice number,
voucher number, e-payment transaction ID, next available cheque
numbers.
• Payment and Receipt summary (12 months).
• Migration Transactional summary report consisting some key
values for:
o Total balance of Treasury budget.(during the current
financial year)
o Total receipt.(during the current financial year)
o Total count of bill (during the current financial year)
o Total count of challan.(during the current financial year)
o Total count of bills payment treasury (in the system )
o Total count of challan.(in the system )
o Total count of bill pension treasury (in the system )
o Total balance of WDDF /FDDF budget Treasury. (during the
current financial year)
o Total count of WDDF /FDDF bill. (in the system )
o Total no. of Pending bills at treasury.
• Report on DDO wise and account head wise allotment and
expenditures.(Take print out (hardcopy) and along with the
migration CD bring some sample reports(Minimum 5) for few ddo’s
to cross verify as post migration activity at DTA).
• Report on summary of allotment, expenditure and balance. (Take
print out (hardcopy) and along with the migration CD bring some
sample reports (Minimum 5) for few ddo’s to cross verify as post
migration activity)
• Consolidated Treasury receipt (head wise summary).(Print out
reports for last month and previous financial year and bring these
reports to cross verify as post migration activity at DTA)
• DDO wise employee details.(Take print out (hardcopy) and along
with the migration CD bring some sample reports(Minimum 5) for
few ddo’s to cross verify as post migration activity at DTA)
Page 22 of 41

• Employee wise bank details.(Take print out of (hardcopy) and along
with the migration CD bring some sample reports (Minimum 5) for
few ddo’s to cross verify as post migration activity at DTA)
• Issued PD/ED, works/forest cheque report.(Print out reports for last
month and previous financial year and bring these reports to cross
verify as post migration at DTA)
• Report on strong room stock register. (Print report for last issue
date and previous month and bring with the data CD)
• Report on PPO register. (Take print out (hardcopy) and along with
the migration CD bring some sample reports(Minimum 5) for few
Banks to cross verify as post migration activity at DTA)
• Consolidated schedule of deposits. (Print out reports for last month
and previous financial year and bring these reports to cross verify
post migration activity at DTA)
• User Status report (Active and Inactive users existing in the system
will be shown) Print this report and preserve this report it will help in
creating users as per work distribution and as per roles defined in
the system.
• WDDF/FDDF reports
o Allotment and Expenditure Report
o Allotment and Expenditure Summary Report
o DDOwise Works deposit balance
(Take print out of (hardcopy) and along with the migration CD bring
some sample reports (Minimum 5) for few Banks to cross verify as
post migration activity at DTA)
Hard copy (print out) of these reports would be taken by the treasury officer/sub
treasury officer. Also keep soft copies of the reports as well and bring with the
migration data backup.
Page 23 of 41

Migration verification reports
6. Now the Assistant programmer would go to the command prompt of the
database and would run commands as per readme provided by the CMC.
7. Key activities are the fullbackup and creation of data dump at specified
location.
8. The data dump has to be copied as per instructions and should be written
on a CD/DVD.
Page 24 of 41

9. Treasury officer would check /tick the check list for the above activities on
the data migration certificate at the location. (Format of check List
certificate is enclosed at Annexure- 6 a).
10. The treasury officer and Assistant programmer would take the CD, Check
List and Printed Reports (As Specified above see step 5 to 8 ) from the
location to DTA (central location) in two copies and will keep two copies of
data backup in the strong room of the treasury.
11. At DTA the data dump would be decrypted by the authorized engineer
(CMC).
12. The data dump would be imported into the staging server and from the
staging server it would be transferred to the production server.
13. When the data dump is imported in the production server, all login and
passwords of the concerned location would be disabled.
14. The Nodal Officer/Master section at DTA would create a login for treasury
officer login.
15. Initially the application would be available for the treasury officer in
“Migration Mode” for checking, authentication and transactions.
16. Treasury officer would generate the same reports as generated prior to
the migration:
• Transactional sequences: This report would provide the last
transactional sequences like receipt number, advice number,
voucher number, e-payment transaction ID, next available cheque
numbers.
• Last one year’s Payment and Receipt summary.
• Transactional summary/control report consisting some key values
for:
o Total balance of Treasury budget .(during the current
financial year)
o Total receipt.(during the current financial year)
o Total count of bill .(during the current financial year)
o Total Count of challan.(during the current financial year)
o Total count of bills payment treasury .(in the system )
o Total Count of challan.(in the system )
o Total count of bill pension treasury. (in the system )
o Total balance of WDDF /FDDF budget Treasury .(during the
current financial year)
o Total count of WDDF /FDDF bill. (in the system )
o Total no. of bill Pending bills at treasury
• Report on DDO wise and account head wise allotment and
expenditures.
• Report on summary of allotment, expenditure and balance.
• Consolidated Treasury receipt (head wise summary).
Page 25 of 41

• DDO wise employee details
• Employee wise bank details
• Issued PD/ED, works/forest cheque report.
• Report on strong room stock register.
• Report on PPO register.
• Consolidated schedule of deposits.
• WDDF/FDDF reports
o Allotment and Expenditure Report
o Allotment and Expenditure Summary Report
o DDOwise Works deposit balance
A hard copy of all the reports would be generated as brought
from treasuries and would have to be checked/reconciled from
the reports generated prior to the migration.
17. Treasury officer would sign for the acceptance of migration. In case any
issue is reported, the same would be resolved/reconciled by CMC Ltd.
(Issue report format enclosed at annexure – 6 c).
18. Once the acceptance of the migration is done, treasury officer, assistant
programmer (of treasury), authorized representative of CMC and the
concerning nodal officer would jointly certify the system as “Set for
Centralization”.
Page 26 of 41

Centralization authentication
19. Treasury officer would create login for all other users as per roles.
20. The application would be available for regular use for that particular
location.
21. In case any issue occurs during the migration or the migration could not
take place then the application at the location would be revoked (as a
system activity) from migration mode and regular operations then would
start from the closed position with the permission of Commissioner,
Treasuries and Accounts and for further migration the above steps would
be carried out once again.
Page 27 of 41

Annexure- 6 a Check-list and certificate for data migration
(At treasury)
Treasury name: _________ Date: ________
Sr. Description Checked/
printed
Yes/No
Remarks
1 Transactional cycles have been completed.
2 Application is “set for migration”.
3 Migration reports generated and hard copy
prepared of the following
A − Transactional sequences
B − Payment Receipt Summary (12
months)
C − Migration Transaction summary
D − Report on DDO wise and allotment
and expenditures (head wise)
E − Report on DDO wise summary of
allotment, expenditure and balance
F − Consolidated Treasury receipt report
(head wise summary)
G − DDO wise employee details
H − Employee wise bank details
I − Issued PD/ED, Works/Forest
cheque book report.
J − Report on strong room stock
register(Last issue date and
previous month)
K − Report on PPO register(bankwise/
cheque/ cash)
L − Report on consolidated schedule of
deposit
M − User Status report.
N − WDDF/FDDF reports.
− Allotment and Expenditure Reports
− Summary of allotment and
expenditure report
− DDOwise Work deposit balance
4 Migration dump has been created.
6 Migration dump has been written on the
CD
The Data Migration process has been completed at_____________________Treasury.
Treasury Officer: On date:
Page 28 of 41

Annexure - 6 b Check-list and certificate for data migration(At DTA)
Treasury name: _________ Date: ________
Sr. Description Checked/
printed
Yes/No
Remarks
1 The data dump is decrypted/ checked with
checksum at DTA.
2 The application has started in “Migration
mode” at DTA and transactional data and
generic reports have been checked
3 The reports have been generated at the
central application and reconciled with the
local reports.
A − Transactional sequences
B − Payment Receipt Summary (12
months)
C − Migration Transaction summary
D − Report on DDO wise and allotment
and expenditures (head wise)
E − Report on DDO wise summary of
allotment, expenditure and balance
F − Consolidated Treasury receipt report
(head wise summary)
G − DDO wise employee details
H − Employee wise bank details
I − Issued PD/ED, Works/Forest cheque
book report.
J − Report on strong room stock
register(Last issue date and previous
month)
K − Report on PPO register(bankwise/
cheque/ cash)
L − Report on consolidated schedule of
deposit
4 Application accepted for centralization and
“Set for Centralization”
The Data Migration has been completed and location ____________ is accepted for
centralized migration.
Nodal Officer: Treasury Officer:
Page 29 of 41

Annexure - 6 c
Issue Report Sheet: Migration
Location name: ______________ Date: ___________
Sr. Issue reported Module /report name Resolved Yes/No
1
2
3
4
Nodal Officer: On date:
Treasury Officer:
Page 30 of 41

izek.k i=k
SFMS Transaction Completion
ifjf'k"V& 7
izekf.kr fd;k tkrk gS fd migration method (ifjf'k"V&6)dk ikyu djrs
gq;s SFMS dk migration verification ,oa set for migration dh dk;Zokgh iw.kZ
dj yh xbZ gSA migration izfØ;k vUrxZr okfNr ifjf'k"V&6a bl izek.k i=k ds lkFk
layXu gSA ftyk dks"kky; &&&&&&&&&&&&&& }kjk leLr midks"kky;ksa (dks"kky;ksa
ds v/hu) ,oa WDDF/FDDF/DPO mi;ksxdrkZvksa ls Hkh bl vk'k; dk izek.k i=k
izkIr dj fy;k x;k gS ,oa ftyk dks"kky; (leLr midks"kky;ksa lfgr) C-SFMS esa
migration gsrq rS;kj gSA
lgk;d izksxzkej dks"kky; vf/dkjh
uke % uke%
eqnzk % eqnzk %&
fnukad
Page 31 of 41

izek.k i=k
ifjf'k"V&8
midks"kky; ,oa WDDF/FDDF/DPO mi;ksxdrkZ }kjk
Transaction Completion
izekf.kr fd;k tkrk gS fd migration izfØ;k vUrxZr set for migration
dk;Zokgh iw.kZ dj yh xbZ gS ,oa --------------------------------------------------------------------------- (mi;ksxdrkZ ds
dk;kZy; dk uke) C-SFMS esa migration gsrq rS;kj gSA
fnukad
mi;ksxdrkZ
uke %&
inuke %&
eqnzk %&
Page 32 of 41

dks"kky; ds loZj dks lhycan djus laca/h izek.k i=k
ifjf'k"V&9
;g izekf.kr fd;k tkrk gS fd migration method ifjf'k"V&6 vuqlkj
dk;Zokgh dj yh xbZ gSA dks"kky; dk MkVkcsl o ,Iyhds'ku loZj dk MkVk cSdvi
Øe'k% pkj&pkj izfr esa ys fy;k x;k gSA MkVk cSdvi dh nks izfr dks"kky; ds n`

izek.k i=k
C-SFMS Migration Completion
ifjf'k"V&10
izekf.kr fd;k tkrk gS fd ftyk dks"kky; &&&&& }kjk migration izfØ;k
vuqlkj ifjf'k"V& 6 b ls feyku dj fy;k x;k gSA feyku esa dksbZ =kqfV ugha gSA vr%
dks"kky; ---------------------------------------------------------------- (leLr midks"kky;ksa lfgr) dk database set to
centralization fd;k tk;sA
uksMy vf/dkjh dks"kky; vf/dkjh
uke % uke%
eqnzk % eqnzk %&
DBA / lgk;d izksxzkej(lapkyuky;) lgk;d izksxzkej(dks"kky;ksa)
uke % uke %
eqnzk % eqnzk %
lh0,e0lh0 fyfeVsM ds izfrfuf/
uke %
eqnzk %
fnukad
Page 34 of 41

izek.k i=k
ifjf'k"V&11
C-SFMS Application Software Rollout at Treasury
izekf.kr fd;k tkrk gS fd ftyk dks"kky; &&&&&&&&&&&&& es migration
izfØ;k vuqlkj leLr dk;Zokgh laiUu gks x;h gSSA feyku esa dksbZ =kqfV ugha gSA dks"kky;]
midks"kky; ,oa WDDF/FDDF/DPO mi;ksxdrkZ lfgr C-SFMS Application Software
dk dk;Z lqpk: :Ik ls izkjaHk gks x;k gSA
fnukad
dks"kky; vf/dkjh
uke%
eqnzk %&
Page 35 of 41

C-SFMS: User Authentication and Accessibility:
Login Interface:
ifjf'k"V&12
1. A common Login interface (URL) would be provided for CSFMS
accessibility.
2. Users need to enter their login and password.
3. Based on the role assigned to the user, user would be able to access the
menu navigation screen of the sub-system / module.
4. The common login would provide for accessibility of relevant modules for:
a. Sub-systems:
i. Treasury sub-system.
ii. DTA sub-system.
iii. Division sub-system.
iv. FMIS sub-system.
b. Interfaces:
i. WDDF
ii. FDDF
iii. SLIM (salary and employee) for DDO
iv. BCO budget distribution interface.
v. DPO (District Pension Office)
5. Login would be unique across the state.
6. The current password policy and password security policies would remain
as it is.
Login for CSFMS
Page 36 of 41

User creation and roles:
1. Once the system is migrated to the central system all the existing login
and passwords for the location would be disabled / deactivated and
need to be created again.
2. The super user at DTA (master section/Nodal Officer) will have
authorization to create user for treasury officer, joint director (for JD
offices) and special role (for FMIS).
3. The treasury officer will have the authentication to create users under
purview of his treasury including works, forest, SLIM and DPO users.
4. Assigning multiple roles
a. There would be facility in C-SFMS to create / assign multiple
roles for a user/officer.
b. One primary role is mandatory for each user to be created in the
system; there could be only one primary role for a login/user.
c. User can be assigned with multiple additional roles under the
location purview. At the time of login, system would prompt to
choose the role from which user wants to connect to the
application.
d. Few specific roles can only be primary roles.
e. Further, there are two type of roles in the system one as DDO
specific role (like WDDF/FDDF/SLIM) and other is non DDO
specific roles (Treasury/DTA/JD/FMIS/DTA sub system). Each
category would have separate primary and additional roles.
Same user/login cannot be created for single sign in for both the
categories.
Page 37 of 41

Assigning additional role
Assigning additional role
Login from Multiple Roles
Page 38 of 41

Login from Multiple Roles
5. Transfer of employee: Users those are being transferred need to
follow with the below procedure:
a. Self de-activation: Employee needs to deactivate himself/herself
when he/she is transferred or not authorized to use the system.
b. Higher deactivation: The super user (Master section- Nodal
Officer at DTA) and authorized user (treasury officer) needs to
deactivate the user once the user gets transferred or is not
authorized to use the application.
c. Enter the employee code at the time of creation of user/login.
d. With the transfer of employee concerned user would be
automatically de-activated.
e. Only authorized users (treasury officer) can activate the
employee once a user is deactivated (either by self or by the
higher authority).
Page 39 of 41

Creation and deactivation of user
Page 40 of 41

End of Document
Page 41 of 41