--- title: Announcing the MM-ISAC Solution Library description: Announcement of the MM-ISAC Reference Architecture image: https://mmisac.org/hubfs/mm-isac-ot-reference-architecture-overview.png --- [Skip to the main content.](https://mmisac.org/mm-isac-blog/announcing-the-mm-isac-solution-library#main-content) [![Mining and Metals Logo without wording](https://mmisac.org/hubfs/Mining%20and%20Metals%20Logo%20without%20wording.svg "Mining and Metals Logo without wording")](https://mmisac.org?hsLang=en) [![Mining and Metals Logo](https://mmisac.org/hs-fs/hubfs/Mining%20and%20Metals%20Logo.jpg?width=14572&height=7199&name=Mining%20and%20Metals%20Logo.jpg "Mining and Metals Logo")](https://mmisac.org?hsLang=en) - [Home](https://mmisac.org) - [About MM-ISAC](https://mmisac.org/about) - [Membership](https://mmisac.org/membership) - [Partnership](https://mmisac.org/partnership) - Programs - [Supply Chain Resilience](https://mmisac.org/supply-chain-resilience) - [Working Groups](https://mmisac.org/working-groups) - [Events](https://mmisac.org/events) - [MM-ISAC Annual Conference](https://mmisac.org/conference_2026) - [MM-ISAC Blog](https://mmisac.org/mm-isac-blog) - [Contact Us](https://mmisac.org/contact-us) - [Member Portal](https://mm-isac.cyware.com/webapp/auth/login/) Search Toggle Menu Search Toggle Menu - [Home](https://mmisac.org) - [About MM-ISAC](https://mmisac.org/about) - [Membership](https://mmisac.org/membership) - [Partnership](https://mmisac.org/partnership) - Programs - [Supply Chain Resilience](https://mmisac.org/supply-chain-resilience) - [Working Groups](https://mmisac.org/working-groups) - [Events](https://mmisac.org/events) - [MM-ISAC Annual Conference](https://mmisac.org/conference_2026) - [MM-ISAC Blog](https://mmisac.org/mm-isac-blog) - [Contact Us](https://mmisac.org/contact-us) - [Member Portal](https://mm-isac.cyware.com/webapp/auth/login/) [Facebook](https://mmisac.org/mm-isac-blog/announcing-the-mm-isac-solution-library#0) [Instagram](https://mmisac.org/mm-isac-blog/announcing-the-mm-isac-solution-library#0) [Linkedin](https://www.linkedin.com/company/mmisac/) [X](https://mmisac.org/mm-isac-blog/announcing-the-mm-isac-solution-library#0) [YouTube](https://mmisac.org/mm-isac-blog/announcing-the-mm-isac-solution-library#0) [Medium](https://mmisac.org/mm-isac-blog/announcing-the-mm-isac-solution-library#0) 5 min read # Announcing the MM-ISAC Solution Library [![Picture of Rob Labbé](https://mmisac.org/hubfs/AGC_Speakers/ROBL%20WebSpeaker2.svg) Rob Labbé](https://mmisac.org/mm-isac-blog/author/rob-labbé) : November 4, 2026 [Partnerships](https://mmisac.org/mm-isac-blog/tag/partnerships) [Architecture](https://mmisac.org/mm-isac-blog/tag/architecture) ![Announcing the MM-ISAC Solution Library](https://mmisac.org/hubfs/mm-isac-ot-reference-architecture-overview.png) Publishing an architecture creates a useful obligation: we need to help people implement it. A diagram can establish where a security boundary belongs. Somebody still has to specify the equipment, configure the services, work through the dependencies and demonstrate that the mine can operate when something fails. That is the next piece of work for MM-ISAC. We are developing the Mining OT Solution Library, with publication planned for Q1 2027. It will help mining companies apply the reference architecture developed by our Reference Architecture Working Group, with participation from 12 mining and metals companies. We invite technology providers and implementation partners to contribute practical solution briefs showing how they can help. **Why the solution library matters** The architecture gives the industry a common design to base decisions on. It establishes a consistent security boundary at the site industrial DMZ, commonly called Level 3.5, while allowing the control environment below it to reflect each operation's needs. It requires local operating authority, controlled external connections and the ability to sustain safe operation through a prolonged loss of enterprise services. It also addresses the eventual transfer of a mine to another owner. Those requirements affect purchasing decisions. A product may provide an excellent capability and still introduce a dependency that the site cannot tolerate. An implementation may look sensible until somebody asks how it will be administered without corporate identity, or whether it can restart without contacting a cloud licensing service. The time to resolve those questions is while we still have choices. Commissioning is an expensive place to discover an architectural disagreement. The solution library will clarify those choices. It connects the architecture's requirements to products, services and deployment approaches that companies can evaluate. For an operating company, that should reduce the effort required to find relevant options and repeatedly explain the same requirements. For a supplier, it provides a shared design context for demonstrating value. Both sides can spend more time on the actual operating problem. **How the library will support implementation** The structure starts with traceability. A reader should be able to identify an architectural capability, find the sections governing it and understand the outcome an implementation needs to deliver. The library then groups relevant solutions into capability families. These include segmentation, monitoring, identity and remote access, recovery, operational data and core site infrastructure. Coverage also extends to private wireless, remote operations centres, AI integration and the business systems that support supply and maintenance. Within those families, entries identify the provider and solution, explain its potential architectural role and set out the questions a buyer needs to resolve. Contributed briefs will add the practical detail: component placement, required connections, dependencies, implementation considerations and evidence of operating behaviour. A diagram is useful here when it shows where the solution belongs and what it needs to communicate with. We should be able to follow the connections and understand their purpose. The library also includes common procurement questions and a record for requests for information and proof-of-concept testing. These connect selection to evidence about disconnected operation, recovery, support, safety and ownership transfer. The document will need to evolve as products and the architecture change. Inclusion will identify a potential fit; it will not certify that every configuration suits every mine. Site engineering and acceptance testing remain essential. **Who we are inviting to contribute** I am asking three groups to help make this resource useful. **Security and technology vendors** Security and technology vendors: Please demonstrate how your products help implement specific parts of the reference architecture. Provide a solution brief written for a mining company making a deployment decision. Identify the capabilities you support, where each component sits and which services it depends on. Explain the supported implementation, including any additional components or subscriptions required to deliver it. Take remote access as an example. Show how a supplier reaches a named system through an approved, recorded session. Explain who grants access, where identity is checked and how the site revokes that access. For a monitoring platform, show how evidence is collected safely, retained locally and used when the central service is unavailable. Explain known limitations. A precise statement of a limitation helps a buyer design around it; discovering it later creates rework. There is a commercial incentive to do this well. Mining companies considering the architecture already have a set of problems they need to solve. A brief that answers those problems gives your technical and sales teams a useful starting point with those buyers. It can reduce repeated discovery work and help a customer decide whether a pilot is worthwhile. You can compete on demonstrated fit and make the engineering behind your product easier to recognize. **System integrators and technology consultants** For system integrators and technology consultants, the invitation is to show you can turn the reference architecture into an operating environment. Members need help understanding their current architecture, identifying consequential gaps and developing a realistic implementation plan. They also need people who can deliver that plan alongside operations and engineering, with a clear understanding of who accepts the result. Show how you would approach both a new mine and an existing operation. A greenfield project can establish boundaries, local services, and supplier requirements during design and procurement. A brownfield operation may have decades of equipment, undocumented dependencies and very limited shutdown windows. Its roadmap needs sequencing, coexistence arrangements and rollback plans. Requiring every legacy system to disappear before progress can begin is unlikely to produce much progress. Your brief should explain the assessment method, implementation scope and evidence you would leave with the member. That might include an agreed design, a prioritized backlog, tested configurations, operating procedures and a handover that the site can use. Show relevant mining experience where you can substantiate it. Describe the skills and delivery capacity you bring. For members, this makes it easier to distinguish firms capable of delivering the work; for capable firms, it makes that expertise visible before a project is tendered. **Mining technology software and equipment suppliers** The third invitation is to mining technology, software and equipment suppliers. This includes companies providing automation, fleet systems, processing equipment, maintenance applications and other technology on which production depends. Your solutions need to function within the architecture, and you can help customers establish that fit much earlier in procurement. Show how your system works with segmented networks, local authority and governed support access. Document the communications it requires, how updates are applied and what happens when an external dependency disappears. If remote supervision is involved, explain how operating authority returns to the site. If cloud services are involved, distinguish the functions that remain available locally from those that stop, and describe the supported continuity arrangements. Customers need that information to make an informed operating decision. Business software deserves particular attention. The control system can remain healthy while the mine loses access to the information needed to obtain reagents or maintain equipment. An ERP or maintenance supplier can contribute by explaining data exports, offline workflows, recovery and reconciliation. The architecture's 30-day objective is the operation's ability to keep running. Suppliers should make their contribution to that outcome explicit, including the work the customer must do around the product. For these suppliers, architectural clarity can help speed procurement decisions. A buyer who understands the required connections, support model and failure behaviour has fewer unanswered questions to work through. Security and engineering teams can assess a documented deployment before the purchase becomes urgent. When a solution meets the requirements, that evidence helps the project move forward. Where a gap exists, an early discussion gives both sides time to address it. **How to contribute** Across all three groups, the most useful submission will connect a mining use case to the relevant architecture guidance and show how the proposed solution delivers it. Include a deployment diagram where it helps, supported versions and dependencies, relevant validation evidence and a technical contact. Explain what is available today and identify planned capabilities as planned. Readers need to know what they can procure and implement now. **How members can help** MM-ISAC members have an important role in building the library. Please encourage your suppliers to reach out, including the firms already supporting your sites. Share the architecture with them and ask how their offering fits. Tell us where implementation is difficult and which capabilities are hard to source. Those conversations will help the library reflect the systems mining companies actually use and the work they actually need done. **Get involved before publication** We are aiming to publish the solution library in Q1 2027. If your organization can supply a relevant capability, implement the architecture, or demonstrate that its mining technology works within it, contact the MM-ISAC team or me about contributing a solution brief. The reference architecture has given us a shared starting point. I want the next document to help a project team make a better decision, an integrator deliver a workable design, and a site prove that it can keep operating. - [Tweet](https://twitter.com/share) [![Mining and Metals Logo without wording](https://mmisac.org/hubfs/Mining%20and%20Metals%20Logo%20without%20wording.svg)](https://www.mmisac.org?hsLang=en) - Privacy Policy © 2026 Global Mining and Metals Information Sharing and Analysis Centre Linkedin YouTube Return to top ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Rob Labbé", "url" : "https://mmisac.org/mm-isac-blog/author/rob-labbé" }, "dateModified" : "2026-11-04T03:52:56.931Z", "datePublished" : "2026-11-04T03:52:56.000Z", "headline" : "Announcing the MM-ISAC Solution Library", "image" : [ "https://mmisac.org/hubfs/mm-isac-ot-reference-architecture-overview.png" ], "mainEntityOfPage" : { "@id" : "https://mmisac.org/mm-isac-blog/announcing-the-mm-isac-solution-library", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://mmisac.org/hubfs/Mining%20and%20Metals%20Logo%20-%20200px%20Wide.jpg" }, "name" : "Global Mining and Metals Information Sharing Analysis Centre" } } ```