# Industrial Manager: case study > Industrial Manager case study: the web platform and iPhone app where maintenance, production and quality teams at an industrial group log breakdowns and downtime. [Home](https://alphaimpact.pt/en/) › [Cases](https://alphaimpact.pt/en/casos/) › Industrial Manager Page: https://alphaimpact.pt/en/casos/industrial-manager · Updated: 2026-10-27 The platform where the maintenance, production and quality teams of an industrial group log what happens on every shift: on the office computer, on the phone of whoever is on the line and in an iPhone app. - Sector: Industry - Solution: [Custom software and apps](https://alphaimpact.pt/en/solucoes/software-e-apps-a-medida) - Technology: Installable web app, iPhone app, Connected sensors, Reading the MultiDos Excel file, AI assistant, Export to Excel - Client: Continuous-production industrial group with several plants - Who uses it: Maintenance, production, quality, control room and management - We delivered: Installable web app and iPhone app - What we did: Discovery, design, development, hosting and support ## Problem The downtime log and the maintenance plan lived in separate Excel sheets, with causes typed by hand and different units from plant to plant. To know what was stopped, who was handling what and what it cost, someone had to phone around and do the maths separately. - **Breakdowns with no owner.** They were reported by word of mouth or by message, and it was not always clear who took them on and when they were fixed. - **Downtime hard to compare.** Each plant logged things its own way, so availability and lost production could not be compared. - **Preventive work far from the people doing it.** The plan sat in a file few people opened. - **Quality on the side.** Non-conformities and audits were not linked to the equipment or to the work done. ## Solution We designed and built a platform with the modules a plant needs day to day. They all share the same equipment, people and plants: a breakdown stays linked to the downtime it caused, the work that fixed it and the parts it used. ## A day at the plant People on the shop floor use their phones; the people who plan use the computer. The records are the same and stay linked: the breakdown, the downtime it caused, the work that fixed it and the parts it used. 1. **Someone on the line reports the breakdown.** On the phone, right from the home screen. The breakdown shows up for the people who can take it, in the plants assigned to them. 2. **The technician takes it and fixes it.** The work order holds the request, the work done, the owner and the parts used, which come off the stock. To postpone, just pick the new date. 3. **Each plant logs its day.** The working day and the downtime, with causes from the official list. If that day already has a log, the app opens it instead of creating a duplicate. 4. **Management decides with everything in view.** Home opens with what needs a decision: breakdowns with no owner, overdue orders and new non-conformities. Right below sit yesterday's downtime and the chosen metric, compared with the previous period. ## Also on the platform - **Preventive plan.** The maintenance plan generates the week's work, and operators tick off their shift checks on the phone. - **Equipment and stock.** A record for each piece of equipment with criticality, manuals and parts with suppliers. - **Quality and improvement.** Non-conformities closed by Quality, audits and improvement ideas that go through approval. - **Sensors.** Each sensor has warning and alarm limits. An alarm opens a critical task, alerts the phone and, if nobody takes it in time, moves up to the next person in charge. - **External services.** Jobs by outside companies, with the technician, the scanned job sheet and the cost of the service. - **Production report.** The Excel file MultiDos sends by email is read every night and published on the management dashboard. - **Imported history.** The old Excel files were brought into the platform, with causes and units standardised. - **Action log.** Every save is logged with the name of whoever made it, including refused attempts. ## AI assistant The assistant turns dictated text into a job record, prepares the morning summary and answers questions about the plant's data. It never saves on its own. It proposes the record, the person confirms, and saving goes through the same permissions and checks as any other record. The figures always come from the database. ## Access Each person has a profile and the plants assigned to them. The rules are checked on the server, so they apply the same way on the web and on the iPhone. - **Administrator.** Sets up plants, teams, limits and permissions. - **Technician.** Logs and edits the work assigned to them. - **Quality.** Has a technician's access and closes non-conformities. - **Operator.** Reports breakdowns, logs downtime and ticks off shift checks. - **Control room.** A shared account that logs downtime under the name of whoever is on shift. - **Guest.** Views, without changing anything. ## Technology - **Web.** Node.js and MySQL, with a light interface that loads fast on modest phones and updates itself. - **iPhone.** Native SwiftUI app, distributed to the team and connected to the same server. - **Hosting.** A dedicated server with Docker and HTTPS, with backups before every update. - **Integrations.** Sensors and PLCs send readings over a dedicated connection, with one key per device. The MultiDos report comes in by email. ## Result Every breakdown has an owner and a date, downtime can be compared across plants and the preventive plan reaches the phone of whoever carries it out. --- Alpha Impact, Lda, Lisboa, Portugal · NIF 516881590 · info@alphaimpact.pt · +351 916 464 768 · First step: a 30-minute call, free of charge.