A certification close to expiration, an action set in a meeting, and a technical visit still without an owner compete for the manager’s attention. When each record sits in a different spreadsheet, tracking the team means gathering information before deciding what to do.
Regimen brings that tracking together in a Windows application: people, certifications, processes, pending items, goals, trips, and finance. It was built for managing the teams of a Transmission Operation Center (COT), in the electric power sector, with screens that tie the work to the people responsible, the deadlines, and the operation’s records.
Transparency: Regimen is a product developed by Jeremias Cardoso, the author of this blog. This is a commercial presentation of the features that exist, with an invitation to a demonstration.
The manager’s routine starts with priorities
Day Central organizes the administrator’s attention into a work queue. Certifications, pending items, and other commitments appear with context and with shortcuts to the corresponding modules. The manager can open, postpone, or resolve the items according to the handling available.
The panel brings together the team, priority actions, the calendar, and the budget status. The advantage is seeing what needs attention without starting the review by walking through each registry on its own.
This is Regimen’s field of action: managing the team and the processes that support the operation. Real-time electrical supervision and equipment commands stay in the facility’s own systems.
People and certifications with context
The 360 Record draws together information that usually stays separate. The employee’s registry connects to certifications, responsibilities in the processes, trips, and other records tied to the person, according to access permissions.
Certification Central tracks the validity and status of the records, while alerts flag expirations. That makes it possible to organize renewal follow-up from recorded dates, instead of relying on informal reminders.
People tracking has a space of its own. Feedback Central lets you record conversations and schedule one-on-one meetings. Behavioral profiles and development plans stay restricted to the administrator; the operation’s technical follow-up has a separate module.
That separation matters for management: a note about equipment and a confidential development conversation have different purposes and different audiences.
Processes with owners and recorded work
The Processes module organizes responsibilities and lets you record work that was done, with evidence attached. The RACI matrix identifies who performs the work, who answers for the delivery, who should be consulted, and who needs to be informed.
The benefit is making responsibility something you can look up. An activity can be followed through the process and through the person involved, with a record of what was done.
Meetings connect to execution as well. An action recorded in the minutes can be explicitly converted into a pending item, carrying the owner, the deadline, and the reference to the meeting. The link lets you return to the origin of the request; converting the same action again retrieves the pending item that already exists.
An example of use, illustrative only:
- During the meeting, record the review of a procedure, with an owner and a deadline.
- Convert the action into a pending item so it can be tracked on the work board.
- Check progress and return to the source meeting when the context needs to be recovered.
Deadlines, goals, and commitments in the same routine
The Pending Items board sorts the cards by due date, including overdue, today, this week, completed, and future or with no deadline. Search, filters, and checklists help track both the date and the stages of the delivery.
For repeated activities, there are monthly, quarterly, and annual templates. Completing the current occurrence generates the next one, with a new checklist and with the history preserved. The series can also be paused and reactivated.
The year’s goals appear on a timeline by quarter, with owner, progress, status, and a risk indication. The indicators complement that view with current value, target, and a history of change.
The Operational Agenda gathers commitments by type, such as certifications, trips, and contracts, with indicators of how close the due date is and with access to the source module. The manager can switch between the year view and the deadline that requires action now.
Technical visits with an itinerary and distribution across the team
Trip planning includes substations and stops by city. The registry by municipality can fill in the coordinates, and the itinerary allows different stops on the same trip.
The panel combines a map, trip cards, and a participation tracker. The equity list highlights who has gone the longest without a completed trip and who does not yet have one recorded. That data supports distributing technical-visit opportunities, preserving the manager’s decision about each trip.
The map uses OpenStreetMap services and offers search; the route can be opened in Google Maps through the browser. Online cartography and external search need internet. The registries and the other local controls remain usable without those services, as long as the database is accessible.
Budget and contracts tied to spending
Finance brings together operating expenses (Opex), investments (Capex), contracts, and spending. Forecasts can be tracked by half-year, while entries feed the comparison between planned and actual.
Spending can be linked to the budget and to contracts. The contract balance then follows the amounts recorded, and the finance panel shows resource consumption in one consolidated view.
| Management need | Regimen feature | Use in the routine |
|---|---|---|
| Prepare renewals | Certifications and validity alerts | Identify records that require follow-up |
| Track meeting decisions | Actions linked to pending items | Look up owner, deadline, and origin of the request |
| Repeat periodic activities | Recurring templates with a checklist | Create the next cycle while keeping the previous one |
| Distribute technical visits | History and equity tracking | Identify people not yet included |
| Control the area’s resources | Budget, contracts, and related spending | Compare forecast, actuals, and balance |
There is PDF report export and a consolidated Monthly Management Report. In that report, the criteria separate movement during the period from information that represents the status at the time of issue, so a current position is not presented as if it were a complete history.
Access by role and management records
Regimen distinguishes administrator, manager, and operator. Management screens and personal screens are made available according to the profile; the operator looks up their own records in the individual modules.
In the sensitive modules covered by the audit, the system records who performed the action, the result, and the names of the fields that changed. The audit record avoids copying confidential narratives and sensitive values into that history.
The application also makes an automatic database backup when it opens, limited to one per day, keeping the 30 most recent. That feature depends on access to the configured folder; the rollout should include a check of the copies and of the restore.
Announcements, shift handover, a knowledge base, recognitions, and records of training simulations complete the set of support for the team.
How to see Regimen and evaluate the rollout
Regimen has a Windows package with Java included, without requiring that environment to be installed separately. The database uses a Microsoft Access file, and the application lets you set its path.
For a shared rollout, permissions, backups, and simultaneous access need to be evaluated with the IT team. Concurrency validation between two machines is still pending in the project consulted on 20/09/2026. For that reason, the demonstration and acceptance testing in the interested party’s environment are part of the adoption evaluation.
The commercial conversation can start with the process that currently takes the most effort: certification renewal, action tracking, visit distribution, or budget control. Demonstrating that flow with sample data makes it possible to judge how useful the system is for the team.
Request a Regimen demonstration through the Fluxonar contact. State the type of operation, the size of the team, and the controls you want to organize in order to talk about the solution and the rollout conditions.
Basis of this presentation
The features were checked in the code, the documentation, and Regimen’s delivery records on 20/09/2026. The functional record with implementation excerpts and the limits of the verification gathers the basis of this presentation, with no data on employees, customers, or the operation.
The benefits described follow from the flows that are available. They are not a measurement of time saved or of financial return. Price, support, and contracting terms are handled through the commercial contact.
This article was written with assistance from artificial intelligence. The opening image was generated by AI from the system’s visual organization; it is a conceptual illustration, with no real data, and not a screenshot of Regimen.
