How QT33 works

Overview: what QT33 does every day

QT33 is a digital record system for 33 KV substation operators. It replaces scattered notebooks and inconsistent Excel sheets with validated screens for the Daily Log Register (DLR), feeder interruptions, battery checks, faults, maintenance, charge handover, and monthly reports. Whether you use the connected web workspace, the Connected Android app with cloud sync, or the Offline Android app that stores everything on the device, the daily workflow is the same: set up your substation once, enter operational data each shift, review saved records, and produce month-end outputs for the office.

This guide walks through the full lifecycle from first login to PDF export and backup. Read it once when you adopt QT33, then share the Operator Guide with shift staff for day-to-day habits.

1. Login, roles, and offline use

In connected mode, an administrator creates your user account and assigns one or more substations. You sign in at qt33.in/login with email or username and password through Firebase Authentication. Your role (main admin, substation admin, or operator) controls which menus appear and whether you can manage users, masters, or only operational entry.

The QT33 Offline Android app does not require login for daily work: a single operator profile stores all data locally on the phone or tablet. Use offline mode when internet is unreliable or when your office policy allows only on-device storage. Connected and offline products share the same field names so operators can move between them with minimal retraining.

• Connected web: best for desk review, user management, and multi-operator sync.
• Connected Android: same data as web, suited for field rounds with sync when online.
• Offline Android: no cloud account required; backup files are your responsibility.

2. Substation and feeder setup (masters)

Before the first DLR entry, complete masters for your assigned substation. This includes organizational hierarchy (division, sub-division, section), substation identity, feeders, power transformers, employees, and the report footer text that prints on monthly sheets. Masters drive every dropdown in the app: you cannot pick a feeder that does not belong to the substation, which prevents many cross-substation mistakes.

Substation admins usually maintain masters; operators should verify feeder names and transformer tags match the yard nameplates. If a new feeder is commissioned mid-month, add it in masters before entering readings for that feeder.

3. Daily Log Register (DLR) entry

Each operational date, open the Daily Log module and confirm the date and substation at the top of the screen. Enter hourly readings in the chart: demand, energy where applicable, and feeder-wise kWh or ampere values according to your office format. QT33 stores a substation snapshot with each save so auditors can see which feeder list was active on that date.

Complete the full shift span your office expects (typically 24 hourly slots or the intervals defined locally). Partial charts are visible in saved-record review but monthly reports may flag incomplete hours—finish corrections on the same operational date before running month-end reports.

4. Interruption entry (LS, BD, EF, OC)

Record feeder interruptions with from-time, to-time, type, and remarks. QT33 calculates duration and rolls interruption minutes into monthly interruption summaries. Use the correct type codes your circle uses (load shedding, breakdown, emergency fault, over-current trip, etc.) so classification reports match official registers.

If an interruption spans midnight, follow your local SOP: either split across two operational dates or record as one event per office rule, but stay consistent all month.

5. Battery, fault, and maintenance registers

Battery register: log bank voltage, charger status, specific gravity or cell checks as per your checklist, and remarks when a bank is under maintenance. Fault register: capture feeder, fault type, cause, restoration time, and duration for the printable fault sheet. Maintenance register: tie work to equipment or bays, describe work done, staff involved, and status (open/closed).

These registers run in parallel with DLR—they do not replace interruption minutes on the DLR sheet unless your procedure says so. Operators should enter faults and maintenance on the same day the event occurred.

6. Charge handover between shifts

At shift change, document outgoing and incoming operator names, pending work, open faults, and acknowledgements. Handover notes reduce disputes about who saw an alarm first and what was left for the next shift. Review the previous shift handover at the start of your own shift before entering new DLR readings.

7. Monthly reports, PDF, and print

Report Center builds monthly outputs: consumption summaries, min/max demand, interruption totals, energy balance, feeder load trend, abnormal consumption flags, and data completeness indicators. Select month and substation, preview the layout, then print or export PDF/CSV when numbers match your manual checks.

Print layouts strip navigation and advertisements so office submission copies are clean. The month-end pack assembles multiple sheets in one workflow for submission to subdivision or circle offices.

8. Backup, export, and import

Connected mode relies on cloud sync; admins should still export periodic backups from masters or data tools where available. Offline Android stores data in local database—use Export Backup from settings on a fixed schedule (weekly or before phone replacement) and store the file in a safe folder or email per office IT policy.

Import restores from a previously exported backup file. Always import on a test device first if you are unsure. Never delete local data until import succeeds and you verify record counts.

9. Connected vs offline workflow summary

Connected workflow: login → sync pulls latest masters and records → enter daily data → sync uploads → admins audit → monthly reports from centralized data. Offline workflow: open app → enter daily data locally → export backup file → optional manual transfer to desk for reporting. Choose connected when multiple operators and admins must see the same substation in real time; choose offline when policy or connectivity demands local-only storage.

• Same modules in both products: DLR, interruptions, battery, faults, maintenance, handover, reports.
• Connected requires internet for sign-in and sync; offline works without internet after install.
• Account deletion applies to connected accounts; offline data is removed when you clear app storage or uninstall.