Professional Documents
Culture Documents
Operational Efficiency Improvement Layout - June2022 - v1
Operational Efficiency Improvement Layout - June2022 - v1
OEIL
MYCOM OSI
• Background
– OEIL inception kicked off post New Delivery Framework definition
– The problem statement : Based on the recent deliveries on both our Saas and on prem tenancy, there
was a necessity to improve formality, efficiency and results/customer success orientation
• Objective
Weekly
– Improve efficiency in nearly all the aspects of our business achieving an agreed outcome or Definition Governance
meeting
of Done in each category
• Scope
– Initially intended to be within Delivery, it extended to 4 big areas, Delivery, Support, Digital and R&D
• Constraints
– We wish to achieve optimum impact rapidly so will seek to drive closure when an acceptable degree Pseudo Four slots of
of improvement has been achieved – decision through governance model stand-ups 15mins
• Assumptions
– The leads and contributors are confirmed and will assign time required to achieve the improvement
• Risks
– Clash with BAU; the aim is to reduce the time spent fixing problems and become more productive
easing the impact on BAU going forward
Francois P.
1 Continuous Component Update PMO Bruno D. WIP Refresh and make sure we have continuity and plan to achieve Upgrades to major release across customers Continuous
Dave C.
2 Deployment Automation Digital Dirk Philippe B. WIP Day 1, Day 2 automation - re discuss the scope – cross departmental actions TBD
Bruno D. Control and Savings of AWS costs - Best practices - Elastic search/Opensearch, Oracle/Oracle_Less, Support of EKS (visibility
4 AWS Cost Control Delivery Paul Wilson WIP TBD
Jonathan C. program)
Francois P. Mamta B.
6 Adaptor Factory Improvement SWE WIP Enhance and improve - Carry on with the details TBD
Gyanu Pragati A.
Bruno D.
7 Zero Outages All WIP Actions on outages and RCA - Refresh with Owners and restart TBD
Francois P.
8 Creation of new vertical Delivery Bruno D. Jacques L.A WIP Adaptors/Acceptance/Automation TBD
9 Bi weekly component update process Delivery/Support Bruno D. Jonathan C. David T WIP TBD
10 Creation of a knowledge base (sharing) Delivery Bruno D./Jonathan PMO WIP TBD
Actions Status Target Customers Next Action Link (right click to open link)
Maintain the plans of upgrade and WIP Nov-21 All SaaS and On prem Execute the upgrades
refresh link
Lessons learnt as we go along Dynamically within the team to be
WIP TBD All SaaS and On prem
(Governance) published
Define process, agreed with customers –
Notion of First site implementation - Once
Plan for future – After above is executed TBD TBD All SaaS and On prem Quarterly releases need pushed month after release
DevOPs dimension for SaaS tenancies
Actions Status Owner Target Customers Next Action Link (right click to open link)
SWE: COE define service memory Modus operandi reviewed; scope reduced
consumption to parametrize On hold Francois 10/11 All Currently on hold due to priority releases on
formulae BDP/Helm across last FY quarter
Prometheus 24x7 alerting is in place today – This is providing good protection (with new alerts and
severity adjustments ongoing)
For reporting we agreed the Airtel standard is the way forward, so we have reviewed the SCAD
report (the automated version) and have all EAA customers updated to this reporting
http://dev-xlgeosim.mycom-internal.com:8080/
There are still some key areas to add to SCAD, especially IDRH and adapter information, so we need
continued focus on by the monitoring PLM team. There is still manual reporting done at Airtel and
other customer so we have not yet achieved outcome of having complete and full automated
reporting. We need to review the priority of this against other work, such as Outage RCAs and
Service Reviews.
© MYCOM OSI Confidential
Break page – post meeting actions – Next Steps
• On upgrade component action Bruno to refresh the program -> engagement with Jonathan/Rob
• On automation digital – Bruno to action a meeting with Mounir sponsor and visibility of Dirk roadmap
• On monitoring
– Action Rob - understand what sub group the customer belong to implement the correct monitoring – making sure that monitoring is deployed
everywhere… in the suitable manner
– Action Bruno – work on bringing what is necessary, internally to cover our proactive actions – work with Rob on the monitoring of the HEC in various
customers
• On AWS costs
– Action Bruno to gather the roadmap on features to come which would help in cost control
– Action Rob to provide the service limits related to application (SingTel as a pilot)
• On Infosec
– Action Francois on SWE to update the presence of VA/PT in product
– Action Claude on AWS inspector
– Action Bruno to work on resourcing input for VA/PT fixing
• Adaptor Delivery improvement
– Action Pragati/Darren to refresh the list and update the dates, bulk up the actions
– Touch point with Mamta to improve the scope
• Zero outages
– Action Rob/Lee/Jonathan to table the issues/RCA and next action with Owners
• On the bi Weekly
– Action Bruno to intiate first meeting and process definition
Break page
• Action on component upgrade to refresh
• Deployment automation – D1, D2 : re discuss the scope – cross departmental actions
• Pro Active monitoring : ph 1 – Known to all, common existing ground – ph 2 – enhancement and
gaps/pain points
• Early HO to support – Definition, Process, Control, Stability, etc…
• AWS – Cloud Economics -> Paul W/Dirk, Elastic search/Opensearch, Oracle/Oracle_Less, Support of
EKS (visibility program)
• Security (Claude and Dave Crozier)
• Adaptor factory improvement
• Zero Outages – Refresh and revive… clarity
• Creation of new verticals, Team Tejas, UAT documentation and automation, Delivery automation
(day2 delivery, shard integration, SIT, zero touch understanding (Jacques, prog manage)
• Bi Weekly images delivery => bi weekly component upgrades (sense of urgency, process)
• Creation of a know how sharing area and process – articles writing, google search, reference to PR,
env knowledge,
Dashboard – OEIL at one glance – Feb 2022
Item Status Trend Achieved Target and comments
Still to be executed by
Delivery Cloud Upskilling 70%
consultancy/Support
Security 80% Need refresh and relaunch
Day 2 platform tuning Done Oct All customers ACS 3.4 Rosa first deployment Completed at TF GE and near real time data flowing
Governance – Customer dependency Complete NA TF GE + all future RAID in place and agreed NA Reports
Governance – Hybrid model including Organise first stand ups when appropriate in the project
Complete NA TF GE + when appropriate In place and agreed Reports
Agile life cycle
Governance – Controlled Making sure escalation are precisely
Complete Aug end TF GE + all future Communicate internally this practice to the team
escalation/substance documented/motivated
Product Availability/Features Done Continuous TF GE + All Identifying FY22 plan deliverable Prepare Requirement and interaction FY22 features
DONM Done Mounir/Bruno Team Sept 21 Revise this and program a meeting
Cross check – accelerate clean up Done Bruno Project/ISM team NA Post migration/Garbage data
Review the above for further improvement Done Bruno Dirk Oct 21
Dirk/
Weekly meeting Monday Done
Francois
NA NA Review post meeting relevance of attending
Input is with 2 Excel – What is necessary is to re-design our DimTool completely to include the
Consolidate input Dim Tool Done Bruno Arnaud NA
models, extension and accuracy
Build a summary dashboard on cost sheet Done America Matt NA Monthly AWS spend report, splitting internal and external spend – to be presented to Mounir
Deepak, Ankur, Central repository with Process, RACI and all the following aspects, owners
Improve process and repository To be done Matt Nov 21
PreSales BARP/Contract/Budget/Procure/Activate/Actual
Engagement with Pen tester + SWE on Engagement has been made with a Pen testing Delivery team approval to start planning
team and a deal agreed to perform testing on 7 the implementation of test in 2022.
how to handle the generic PEN – WIP Nov21 platforms at a reduced cost. Now awaiting
determine the frequency/scope
• Veracode reconfiguration is 92% completed. • SWE have identified gaps in the Veracode
It’s just a few minor bits that we need to configuration where not all code being
work on as below: produced is being passed to Veracode for
scanning. SWE are actively working on
• Veracode reconfiguration of application closing those gaps.
profiles using microservices has been
completed. • All Jenkins jobs need to be checked /
updated to ensure they process returned
• The Dev teams have started running scans Veracode failure messages. This prevents
using the new configuration. code that does not meet the required
• There’s also some work that the security standard from being deployed to
team is doing in the background to enable customers.
Veracode implementation WIP notifications and monthly reports. SWE are reviewing the dashboards that
•
• Dashboard in place to identify the have been produced and will notify the
vulnerabilities found, working on a process InfoSec team of any changes required.
how to mitigate the vulnerabilities in order • InfoSec and SWE are working on a strategy
to ensure the development process for scanning older versions of code, and
continued. Access to be provided to the the reporting of identified vulnerabilities.
dashboard.
• SWE are working towards the first target of
having zero very-high or high-level
vulnerabilities. An estimated resolution
date will be provided once the
vulnerabilities have been analysed.
Actions Status Owner Target Customers Next Action Link (right click to open link)
OCP/EKS AWS setups On Going François 31/03 All Review and Implementation of QA setup
to encompass both OCP and K8S
deployment and QAT testing and
minimizing/preventing additional AWS
cost
CHO (Continuous hours of On Hold Francois 06/22 All Still down. Additional resources required
operations) setup in during EKS validation. Review of Dev
AWS resources done and budget met in
December, on track for Jan.
https://osiinc.jira.com/plugins/servlet/ac/hakki
PM dashboard was available in Jan. Hakkiri report created for PM adaptors to show monthly production and ri-jira-addon-key/hakkiri-main?project.key=PR
PM Adaptors Dashboard and Hakkiri report Completed Feb-2022 Internal backlog. OAS&project.id=13638
PM adaptors dashboard was enhanced and refined further.
https://osiinc.jira.com/jira/dashboards/21810
The adaptor delivery link will be available in corresponding PSAP JIRA ticket when it is delivered. SE can
PM Spec pack project in JIRA Completed Feb-2022 Internal
directly get adaptors details from JIRA.
Improve the process of design, building and delivering connectors, Ali P is pencilled as
Overall Connector building enhancement Starting Q1-2022 Internal
champion from delivery
1- Time it takes to deploy/SIT adaptors
2 – TAT on OTS
Overall turn around time adaptor delivery Starting Q1 - 2022 Internal
3 – improvement on SIT execution
4 – TaT from speck pack to delivery
Completed At present, property files are submitted in GIT. Version control for different vendor/customer property files
Planning centralize restful property file version control 20-Jan-2022
will be centralized.
Governance – Customer
Complete NA TF GE + all future RAID in place and agreed NA Reports
dependency
Governance – Formality - RAID Complete NA TF GE + future In place and agreed NA RAID
Governance – Hybrid model TF GE + when Organise first stand ups when appropriate in the
Complete NA In place and agreed Reports
including Agile appropriate project life cycle
Communicate internally this practice to the
Governance – Controlled Making sure escalation are precisely
Complete Aug end TF GE + all future team - Make it an item on the PMO weekly
escalation/substance documented/motivated
meeting
Governance – Matrix resourcing v
On Hold Nov End TF GE + all future Identify resources v actions/WBS NA Matrix
area
Product Availability/Features Done Continuous TF GE + All Identifying FY22 plan deliverable Prepare Requirement and interaction FY22 features
Identify area where slowness can be reported,
Plan benchmarking with legacy TF GE + when
WIP Nov-21 Gathering information analyse and run validation prior to customer
issues (slowness) appropriate migration
visibility – need to be ready after MVP
Early User Adoption – Identification Building outcome of MVP concept – Need platform deployed, Adaptors and KPIs…
WIP TBD TF GE + All Solutions_MVP
of outcome identifying dependencies Workshop to be organised
DONM Done Mounir/Bruno Team Sept 21 Revise this and program a meeting
Cross check – accelerate clean up Done Bruno Project/ISM team NA Post migration/Garbage data
Review the above for further improvement Done Bruno Dirk Oct 21
Dirk/
Weekly meeting Monday Done NA NA Review post meeting relevance of attending
Francois
Deepak, Ankur, Central repository with Process, RACI and all the following aspects, owners
Improve process and repository To be done Matt Nov 21
PreSales BARP/Contract/Budget/Procure/Activate/Actual
Completed At present, property files are submitted in GIT. Version control for different vendor/customer property files
Planning centralize restful property file version control 20-Jan-2022
will be centralized.