Product Deployment · DDMS

From Printed Circulars
to a Live Display Network

A residential cooperative housing society in Navi Mumbai replaced their printed notice board process with DDMS — a real-time digital display system built and deployed by Jyotvira. The committee now manages every screen in the property from a browser.

Client Type Residential Cooperative Housing Society
Location Navi Mumbai, Maharashtra
Property Scale 300+ units · 3 towers
System DDMS — Digital Display Management
Status Deployed & Running
The Problem

A broken notice process no one had formally decided to fix

The society's communication model had evolved by accident, not design. Critical information — water cut schedules, AGM dates, maintenance windows, security advisories — was distributed through a combination of printed circulars, WhatsApp broadcast groups, and a physical notice board in the lobby that was routinely out of date.

Emergency announcements were the worst case. If a water supply issue developed at 11pm, the only option was a WhatsApp message to residents who happened to be in the right group — or physical door-knocking the next morning.

Printed circulars distributed floor-by-floor — dependent on watchman availability and committee member time
Physical notice board showing notices from weeks ago — no removal schedule, no accountability
WhatsApp groups as a communication fallback — not all residents present, no audit trail
No emergency broadcast capability — critical notices had no fast, reliable path to all residents
Before DDMS

The process for issuing a routine society notice

Committee secretary types the notice in a Word document or WhatsApp
Document printed — 150 to 200 copies for a 300-unit society
Printing cost, paper waste, time at printing shop or society office printer
Copies handed to watchman staff for floor-by-floor distribution, or delivered by committee member personally
Dependent on watchman availability and willingness; partial distribution common
Same notice forwarded separately to 2–3 WhatsApp resident groups
Different groups have different membership — no single channel reaches all residents
Notice pinned to lobby board — remains until manually removed, often weeks later
Jyotvira's Approach

Replace the process, not just the medium

The requirement wasn't "install a TV in the lobby." The requirement was: any authorized committee member must be able to push a notice to every common area in the property, from their phone or laptop, without calling anyone.

DDMS was scoped, built, and deployed to satisfy exactly that.

01
Discovery: mapped the actual flow, not the stated requirement
The committee initially asked for "a digital notice board." Two sessions in, the real need was an emergency broadcast system with scheduling — the notice board was incidental.
02
Architecture: web admin panel + Android screen client
A Laravel 12 web application serves as the control panel. Each physical display runs an Android client that polls the API. No special hardware — any Android TV or tablet works as a screen endpoint.
03
Content model: schedule, loop, or push immediately
Content can be queued with a start/end date, set to loop indefinitely, or pushed immediately with the emergency override — which clears the current queue and displays the emergency notice on all screens within seconds.
04
Access control: committee members only, no IT admin required
Role-based login. The committee chairman has full access; other authorized members can upload content but cannot change screen configuration. No IT staff required to operate the system day-to-day.
System Delivered

What was built and deployed

Web admin panel — browser-based, works on mobile and desktop
Android screen client — API-connected, auto-refreshes content queue
Content scheduler — date-range publishing, loop, and expiry
Emergency push — overrides all screens instantly with one action
Screen health dashboard — online/offline status visible to admin
Role-based access — chairman, committee member, view-only tiers
Content audit log — timestamp record of every published notice
Multi-screen deployment — lobby, gym area, lift lobby zones
System Interfaces

Admin panel and screen output

Admin Panel — Content Queue & Screen Status
Screenshot pending client sign-off
Live Display Output — Lobby Screen
Photograph pending site visit confirmation
What Changed

Measurable and observable outcomes

These are system-level outcomes — behaviors the system was designed to produce and that are verifiable by using it.

Emergency notices reach all property screens in under 2 minutes
The emergency push button clears the content queue and broadcasts to all online screens immediately via the Android client API — no phone calls, no coordination required.
Zero dependency on watchman or committee member presence for routine notices
The committee secretary publishes from their phone or laptop. The watchman does not need to be involved in notice distribution. Committee members no longer need to be physically present in the building.
Every published notice has a timestamp audit trail
The admin panel logs who published what, when, and to which screens. AGM notices, emergency alerts, and routine announcements all have a verifiable record — useful for committee accountability and society records.
Lobby screens always display current, relevant information
Content scheduling with automatic expiry means notices are removed from display when they're no longer relevant. The lobby board no longer shows 3-week-old maintenance notices.
What This Proves About Jyotvira

The brief was "a digital notice board." We delivered a process replacement.

Engineering decisions that mattered
  • We mapped the actual communication flow before writing any code — the emergency broadcast capability emerged from discovery, not from the original brief
  • We chose Android-client architecture so the society doesn't need proprietary hardware — any commodity Android device becomes a screen endpoint
  • Role-based access was scoped from day one — the system had to work without an IT administrator present
  • Content scheduling with auto-expiry was a deliberate design decision, not a feature request — we understood that stale notices were as much a problem as missing ones
  • The system runs in production without Jyotvira's ongoing involvement — handover was planned into the architecture, not bolted on at the end
Work With Jyotvira

Have a process in your property, business, or operation that still runs on paper and WhatsApp?

We'll map what's actually broken, then build the system that fixes it — not a template, not a workaround.

Start a Conversation See DDMS Details