Technical glitch framework requires immediate reporting and detailed RCA, plus capacity, testing, monitoring and DR obligations. Prescribes a regulatory framework requiring immediate notification to exchanges, a next-day preliminary incident report, and a detailed Root Cause Analysis within fourteen days for any defined technical glitch. Mandates capacity planning, robust software testing and change management, API-based logging and monitoring by exchanges, and business continuity/disaster recovery arrangements including geographically separated DR sites and periodic full-day DR drills. Exchanges will publish incidents and RCAs, issue implementation guidelines, and impose financial disincentives for glitches and non-compliance.
Cases where this provision is explicitly mentioned in the judgment/order text; may not be exhaustive. To view the complete list of cases mentioning this section, Click here.
Provisions expressly mentioned in the judgment/order text.
Technical glitch framework requires immediate reporting and detailed RCA, plus capacity, testing, monitoring and DR obligations.
Prescribes a regulatory framework requiring immediate notification to exchanges, a next-day preliminary incident report, and a detailed Root Cause Analysis within fourteen days for any defined technical glitch. Mandates capacity planning, robust software testing and change management, API-based logging and monitoring by exchanges, and business continuity/disaster recovery arrangements including geographically separated DR sites and periodic full-day DR drills. Exchanges will publish incidents and RCAs, issue implementation guidelines, and impose financial disincentives for glitches and non-compliance.
Full Summary is available for active users!
Note: It is a system-generated summary and is for quick reference only.
TaxTMI 
of 
Join Channel
TaxTMI 
