MS
MACT Sampoorna
What Production Still Needs
MS
Chhattisgarh Roll-out · Readiness

What Production Still Needs

The portal is feature-complete. It covers all 5 modules of the Supreme Court’s 2025 INSC 530 dashboard framework. Below is the honest list of 12 items still needed from outside the build, with the owning office, the usual timeline and the pilot workaround. For the Registry of the High Court of Chhattisgarh.

Total Items
12
Blocking
5
High
4
Medium
3
§01

Nodal current account in the Registrar General's name

Blocking

Production needs one nodal current account at a public-sector bank (usually SBI Bilaspur), with sub-ledgers per Tribunal and corporate internet banking that can send NEFT, RTGS or IMPS of at least ₹5 crore per day.

Owner
Registrar General, High Court of Chhattisgarh with SBI Bilaspur Circle
Typical Timeline
8 to 12 weeks from board approval, including KYC and corporate IB setup
Pilot Workaround
Pilot uses an existing Tribunal account at SBI Bilaspur. The Reader reconciles by hand against the portal ledger.
§02

Payment gateway for inbound deposits

Blocking

Production needs a merchant account with an NPCI-empanelled aggregator (BillDesk, PayU or SBI ePay) on a Government tariff so the depositor pays no charge.

Owner
Registrar General with Finance Department, e-Governance Cell, Government of Chhattisgarh
Typical Timeline
6 weeks for empanelment plus 4 weeks for production testing
Pilot Workaround
Pilot accepts NEFT and RTGS only. The Reader creates the deposit row after the bank advice comes in.
§03

SMS gateway with a Government of Chhattisgarh sender ID

Blocking

Production needs a DLT-registered 6-character sender ID (such as CGHCRT or MACTCG) issued by the State for OTP, deposit, payout and Fixed Deposit maturity SMS.

Owner
Department of Public Relations and Department of Electronics and IT, Government of Chhattisgarh
Typical Timeline
4 to 6 weeks for DLT registration; 1 week for template approval
Pilot Workaround
Pilot shows the OTP on screen and sends SMS through a single Registry-side bulk provider for spot-checks.
§04

Read-only API to the Case Information System (CIS)

High

Production needs an API to fetch the cause title, parties and award document from CIS using the case number or CNR, with no edit rights for the Reader.

Owner
e-Committee, Supreme Court of India through the High Court of Chhattisgarh Computer Cell
Typical Timeline
10 to 14 weeks; needs an MoU and a stable endpoint
Pilot Workaround
Pilot loads case details from a flat extract refreshed nightly by the Computer Cell.
§05

Fixed Deposit API from at least 2 banks

High

Production needs an API to open the FD in the Applicant's name with the Tribunal as lien holder, and to schedule periodic interest credits. This is a non-standard product and needs an SLA.

Owner
SBI and Bank of Baroda (Bilaspur), corporate banking
Typical Timeline
12 to 16 weeks per bank; can run in parallel
Pilot Workaround
Pilot opens the FD by physical instruction at the branch. The Reader records the FDR number, maturity and rate on the portal by hand.
§06

Aadhaar-seeded bank account check for the Applicant

Medium

Production needs NPCI mapper access or a penny-drop service to confirm the account is Aadhaar-seeded and the name matches the Applicant on record.

Owner
Registrar General with NPCI
Typical Timeline
6 to 8 weeks bilateral with NPCI; 4 weeks via SBI ePay
Pilot Workaround
Pilot sends a ₹1 credit and reversal. A successful credit counts as verification.
§07

Registrar General's notification adopting the portal

Blocking

Production needs a notification from the Registrar General that makes the portal the official record, fixes the commencement date and lists the Tribunals it applies to.

Owner
Registrar General with the approval of the Chief Justice
Typical Timeline
2 to 4 weeks after bench-and-bar consultation; needs a board resolution
Pilot Workaround
Pilot runs alongside the existing manual register until the notification is issued.
§08

Training of Readers and Presiding Officers across 8 Tribunals

Medium

Production needs 16 staff trained (1 Reader and 1 Presiding Officer per Tribunal) through a train-the-trainer programme at the State Judicial Academy.

Owner
Chhattisgarh State Judicial Academy and the Registry
Typical Timeline
2 weeks for the first batch; refresher sessions ongoing
Pilot Workaround
Pilot is run by a small task force at MACT Bilaspur. Other Tribunals come on board one at a time.
§09

Hindi layer for applicant-facing screens

High

Production needs Registry-approved Hindi alongside English on every Applicant screen. Halbi and Gondi voice prompts are needed for Bastar division.

Owner
Registry of the High Court of Chhattisgarh with the Translation Cell
Typical Timeline
4 weeks for first-pass Hindi; Halbi and Gondi later
Pilot Workaround
Pilot ships Hindi for the key Applicant instructions. Halbi and Gondi voice prompts are pushed to phase 2.
§10

Data retention and audit policy approved by the High Court

Medium

Production needs a written retention policy aligned with the Information Technology Act, 2000 and the Bharatiya Nagarik Suraksha Sanhita, 2023 rules for records of judicial proceedings.

Owner
Registrar General with the High Court IT Committee
Typical Timeline
6 weeks for drafting and approval
Pilot Workaround
Pilot follows a default 15-year retention with annual snapshots to the NIC data centre.
§11

Cyber-security audit and STQC clearance

Blocking

Production needs a CERT-In empanelled audit and STQC clearance before the portal can go live on a State or High Court sub-domain.

Owner
STQC Directorate, Ministry of Electronics and IT, through a CERT-In empanelled auditor
Typical Timeline
8 to 10 weeks for the audit; 6 weeks for remediation
Pilot Workaround
Pilot runs on a non-judicial sub-domain (for example sampoorna.chhattisgarh.gov.in) until STQC clearance is in for the High Court domain.
§12

Disaster recovery hosting in NIC or a Tier-IV data centre

High

Production needs active-passive replication across 2 geographically separated data centres to meet the High Court's business-continuity standard.

Owner
NIC Chhattisgarh State Centre at Raipur and the central NIC data centre at Hyderabad
Typical Timeline
6 weeks for NIC commissioning; 2 weeks for cutover
Pilot Workaround
Pilot runs in a single NIC region with hourly snapshots replicated to NIC Hyderabad.
Recommended Pilot Setup

Smallest Viable Roll-out · MACT Bilaspur · 90 days

  1. Registrar General issues a notification adopting the portal at MACT Bilaspur as a parallel record.
  2. Run on a Government of Chhattisgarh sub-domain (sampoorna.cg.gov.in) until STQC clearance comes in for the High Court domain.
  3. Use a nodal account at SBI Bilaspur with manual reconciliation.
  4. Accept NEFT and RTGS only. Push the payment gateway to phase 2.
  5. Ship Hindi for the key Applicant instructions.
  6. Train 2 Readers and 1 Presiding Officer. Keep a Computer Cell engineer on-site for the first 30 days.
  7. Send a weekly status report to the Chief Justice through the Registry.
Back to DemoBack to Home