Case studies · Steel · 2010
A collaboration system for contingencies and crises at a steel company
A multi-plant steel company gained a collaboration system for contingencies and crises, developed by AVILA® using the MoProSoft methodology.
- documented development process
- MoProSoft
- development methodology
- MoProSoft
The challenge
In heavy industry, a contingency comes without warning: a production line failure, a supply interruption, a safety incident, or a problem with a major customer. What determines the impact is how quickly the right people come together with the right information, and how well the decisions are recorded.
When operations span several plants, coordination gets harder:
Information is scattered across calls, emails, and messages, and no one has the full picture of what happened.
Response procedures exist, but they aren't at hand when they're needed.
Each country or plant responds its own way, without a shared record to learn from each event.
Once the crisis is over, there's little trail left to review what worked and what didn't.
In 2010, a multi-plant steel company needed a system that gave its teams a shared space to collaborate on contingencies and crises. Given the scope of the project, it also needed a vendor with a formal, documented development process.
The solution
AVILA® developed a collaboration, contingency, and crisis system for the steel company's operations: a shared space where teams from different plants can coordinate during an event and keep a record of it.
The project was carried out with the MoProSoft methodology, the Mexican process model for the software industry, under which AVILA® earned MoProSoft Level 1 certification in 2009. MoProSoft organizes development around practices like these:
Agreed, documented requirements before building, so the system reflects how teams actually work during a crisis.
Reviewed analysis and design, with traceability between each requirement and what gets built.
Planned testing, not improvised at the end.
Change and version control, so every adjustment is recorded and approved.
Delivery documentation to operate and maintain the system.
A system meant for critical moments has to be reliable on the day it's used. That's why the development process mattered as much as the tool itself.
If your organization needs its own system to coordinate its teams, see how we approach custom software.