Phase 1<\/strong><\/p>\n\n\n\n \u2022 Kick off meeting – to discuss about the product and its design structure Phase 2<\/strong><\/p>\n\n\n\n \u2022 EA meeting \u2013 Need to present v1 design for approval, EA consists of banks architects team so be ready to answer a lot of queries mostly on security. Phase 3<\/strong><\/p>\n\n\n\n \u2022 CAB meeting – Need to present v2 design for approval, CAB consists of banks business teams & queries focus on use cases & business process which will be improved. Deploy Phase<\/strong><\/p>\n\n\n\n Prerequisites for deployment<\/strong> Deployment and Sign off (UAT environment)<\/strong> Deployment<\/strong> and Sign off<\/strong> (Production<\/strong> environment)<\/strong> Design\/Implement Use cases<\/strong><\/p>\n\n\n\n \u2022 Design use cases as per the functional specifications Operations Phase<\/strong><\/p>\n\n\n\n \u2022 After the project is moved into operations phase the use cases needs to be executed as per the work orders raised by different teams. It is important to have a work order for any use case execution. Audit Phase<\/strong><\/p>\n\n\n\n Successful audit is an important aspect of completing any project in a bank Timeline factors<\/strong><\/p>\n\n\n\n It is important to consider below pointers while defining\/revising project timelines<\/strong> Hoping this data will give you some idea and benefit in your planning for a project and a timely Signoff !!<\/p>\n\n\n\n Cheers \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":" Hello everyone .. We all work with different customers and each one has their specific process and culture to be followed. Banks and for that matter PSU banks have very stringent processes. We (from project delivery side) must understand those processes for efficient project management. I\u2019m noting down a few pointers I have picked up […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_mi_skip_tracking":false,"footnotes":""},"categories":[7],"tags":[],"class_list":["post-136","post","type-post","status-publish","format-standard","hentry","category-process"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/posts\/136","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/comments?post=136"}],"version-history":[{"count":1,"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/posts\/136\/revisions"}],"predecessor-version":[{"id":140,"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/posts\/136\/revisions\/140"}],"wp:attachment":[{"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/media?parent=136"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/categories?post=136"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/oneboxinthecloud.com\/index.php\/wp-json\/wp\/v2\/tags?post=136"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/oneboxinthecloud.com\/wp-content\/uploads\/2026\/10\/Design1.png\")
<\/figure>\n\n\n\n
\u2022 Requirements gathering \u2013 gather info about platform (Sites \u2013 DC\/DR, environment – UAT\/Production, Zones \u2013 DC\/DMZ, Firewall, Ports
\u2022 Prepare High level design document \u2013 clearly mention the design decisions & justifications, constraints, assumptions, network diagram etc
\u2022 Prepare Low level design document \u2013 detailed explanation of all the design points
<\/p>\n\n\n\n![\"\"](\"https:\/\/oneboxinthecloud.com\/wp-content\/uploads\/2026\/10\/Design2.png\")
<\/figure>\n\n\n\n
Note \u2013 EA meeting happens twice a month so if you need approval you need to prepare the necessary documents before the meet.<\/p>\n\n\n\n![\"\"](\"https:\/\/oneboxinthecloud.com\/wp-content\/uploads\/2026\/10\/Design3.png\")
<\/figure>\n\n\n\n
Note \u2013 CAB meeting happens twice a month so if you need approval you need to prepare the necessary documents before the meet.<\/p>\n\n\n\n
\u2022 CR needs to be raised for any component which needs to be created or modified or deleted (consider approval hierarchy & timelines) e.g. VM creation
\u2022 CR needs to be raised for any firewall, port requirements (consider approval hierarchy & timelines which are more as multiple departments are involved) e.g. firewalls needs to be opened up between different components which are placed in different zones
Note:
\u2022 Firewall is pushed at night on a particular day of the week. So you have to be mindful of this timeframe.
\u2022 If any modification in the CR, then approval process has to be repeated so it is very important to give data right first time.
\u2022 Define a process to copy necessary files to the environment. e.g. deployment packages from OEM. Most banks have dark sites and hence this activity may take some time.<\/p>\n\n\n\n
\u2022 Once CR are approved from test vms check if firewalls are working as needed
\u2022 If firewall is ok then proceed with necessary vm deployment
\u2022 It is important to integrate VM with PAM, SIEM, DAM, AV etc as per banks process
\u2022 Install & Configure the necessary software as per OEM documentation
\u2022 It is important to perform planned DC to DR drill for the deployed components and verify if the environment run well from DR site
\u2022 Collect the evidence of the successful deployment and proceed to take Deployment signoff at platform level.<\/p>\n\n\n\n
\u2022 Once CR are approved from test vms check if firewalls are working as needed
\u2022 If firewall is ok then proceed with necessary vm deployment
\u2022 It is important to integrate VM with PAM, SIEM, DAM, AV etc as per banks process
\u2022 Install & Configure the necessary software as per OEM documentation
\u2022 It is important to perform planned DC to DR drill for the deployed components and verify if the environment run well from DR site
\u2022 Collect the evidence of the successful deployment and proceed to take Deployment signoff at platform level<\/p>\n\n\n\n
\u2022 Requirements for use cases needs to be collected from different teams.
\u00a0 e.g. CISO team, Cloud team, SIEM team, Different applications team
\u2022 The use cases needs to be thought based on their reach e.g. some which can be applied at a scale and some which will be specific to any particular team with limited reach.
\u2022 Design and test use cases first in UAT environment.
Note: It is important to get approval from the respective teams on the successful execution of the use case.
\u2022 Submit the evidence of the successful use case implementation & proceed to take use case signoff at UAT level.
\u2022 Once the use case is validated repeatedly on the UAT environment then it can be released on the production environment to be implemented on production VMs.
Note: It is important to get approval from the respective teams on the successful execution of the use case.
\u2022 Submit evidence of the successful use case implementation & proceed to take use case signoff at Production level<\/p>\n\n\n\n
\u2022 Platform level upgrades should also be performed as per the updated received from the OEM after raising a change request.<\/p>\n\n\n\n
Below are few of the points needed for audit:
\u2022 Evidence of servers integration with PAM, SIEM, DAM
\u2022 User access review
\u2022 Password policy & procedures
\u2022 SOP documents (Platform, Use cases)
\u2022 Last 2 quarters of VAPT reports and closure status
\u2022 Last 2 quarters of SCD reports and closure status
etc<\/p>\n\n\n\n
\u2022 Coordination between multiple teams
\u2022 Acquiring successful execution evidence from teams
\u2022 Coordination with OEM for platform updates, feature updates, GSS cases with support timelines
\u2022 Approval timelines for CR, WO
\u2022 Information movement between different hierarchies
\u2022 Processes that needs to be followed
\u2022 Freeze duration \u2013 during audit time, during financial year end
\u2022 Daily, Weekly, Monthly reports
\u2022 Latest 2 quarters of DR Drill reports for the current financial year
etc<\/p>\n\n\n\n