SCADA-Style Production Downtime Dashboard

SCADA-like Web Application (No PLC Integration)


Project Title

Development of a SCADA-like Web Application (Manual Data Entry, No PLC Integration)



Project Overview

I am looking to develop a web-based application similar in concept to Ignition / SCADA systems, but without any direct integration to PLCs or machines. There is no automatic data capture. All operational data will be entered manually by supervisors through a web interface (tablet, mobile phone, or PC).



The purpose of the application is to provide real-time visibility of machine status, efficiency, and production performance, and to display this information live on a TV/monitor in the plant.



The system must update in near real time whenever a supervisor enters or updates data.



Project Objectives

• Capture operational data by machine and shift through supervisors

• Track current machine status (running, stopped, setup, maintenance, etc.)

• Calculate efficiency / OEE (or at minimum Availability and Performance)

• Display a real-time dashboard suitable for a large TV screen

• Store historical data for analysis and export



Scope of Work



1. Data Entry – Supervisor Interface

• User authentication with roles (Supervisor, Admin, Viewer)

• Selection of Plant / Area / Machine / Shift

• Manual entry of:

– Machine status (Running, Down, Setup, Maintenance, Idle)

– Downtime reason (configurable list)

– Start / End time or duration of events

– Production quantity (kg or pieces)

– Scrap quantity (kg or pieces)

– Comments (optional)

• Simple and fast UI suitable for shopfloor use

• Input validation to avoid incorrect data



2. Database and KPIs

• Central database with full historical record by machine and shift

• Configurable master data:

– Machines

– Shifts

– Downtime reasons

– Target rates per machine (kg/h or pcs/h)

• KPI calculations:

– Availability

– Performance / Speed

– Quality (if scrap is used)

– OEE (if standards are configured)



3. Real-Time Dashboard (TV / Control Room)

• Live dashboard showing all machines

• Machine cards with:

– Current status (color-coded)

– Time in current state

– Shift production

– Scrap

– Availability / Performance / OEE

• Pareto chart of downtime reasons (shift/day)

• Full-screen TV mode (1080p)

• Automatic refresh or real-time updates (WebSockets / Realtime DB)



4. Administration

• User management and role control

• CRUD for machines, downtime reasons, shifts, and targets

• Data export to CSV / Excel

• Basic audit trail (who changed what and when)



Platform Expectations

The developer is expected to propose the most suitable platform. Preferred options include:



Option A – Web App with Realtime Database (Recommended)

• Frontend: React / Next.js or similar

• Backend / DB: Firebase (Firestore) or Supabase Realtime

• Authentication: Firebase Auth or equivalent

• Hosting: Cloud-based (Firebase, Vercel, etc.)

• Advantage: Native real-time updates, fast deployment, cost-effective



Option B – Web App with Custom Backend

• Frontend: React / Vue

• Backend: Node.js / Python (FastAPI) / .NET

• Database: PostgreSQL

• Real-time: WebSockets / SignalR

• Hosting: AWS / Azure / DigitalOcean

• Advantage: Higher scalability and future PLC integration



Important Note: There is NO PLC integration in this phase.



Deliverables

• System architecture and data model documentation

• UI/UX prototype or wireframes

• Fully functional web application (MVP + v1)

• Real-time dashboard for TV display

• Admin configuration module

• Source code (Git repository)

• Basic user and deployment documentation



Acceptance Criteria

• Dashboard updates within 3 seconds after data entry

• Real-time visibility of machine status

• Editable master data (machines, downtime reasons, targets)

• Historical data access and export

• Secure login and role-based access

• Working cloud deployment with admin access



Milestones (Suggested)

• M1 – Architecture and UI design

• M2 – Data entry module + real-time dashboard (MVP)

• M3 – KPIs, OEE calculations, admin configuration

• M4 – Reporting, export, documentation, final deployment



Developer Requirements

• Experience with real-time web applications

• Experience with manufacturing dashboards or OEE systems

• Strong UX design for shopfloor environments

• Clean, well-documented code



Proposal Requirements

Please include in your proposal:

• Recommended technology stack and justification

• Real-time implementation approach

• Estimated timeline per milestone

• Examples of similar projects