Review of MJC², Optimization and Scheduling Software Vendor

Last updated: April, 2026

Go back to Market Research

MJC² (supply chain score 3.9/10) is a real but very small optimization boutique focused on real-time scheduling for logistics, manufacturing, and workforce operations rather than on broad supply chain planning. Public evidence supports genuine technical substance in routing, dispatch, synchromodal freight, process scheduling, and field-service allocation, with repeated participation in EU-funded optimization projects and a long specialist history. Public evidence does not support treating MJC² as a probabilistic planning platform, a broad SaaS suite, or a transparent AI vendor in the modern sense. The product family looks strongest as a project-style solver shop for hard combinatorial operations problems, not as a general supply chain decision platform.

MJC² overview

Supply chain score

• Supply chain depth: 3.8/10
• Decision and optimization substance: 4.2/10
• Product and architecture integrity: 3.8/10
• Technical transparency: 3.8/10
• Vendor seriousness: 4.0/10
• Overall score: 3.9/10 (provisional, simple average)

MJC² should be read as a niche optimization-engine supplier rather than as a mainstream planning vendor. Its public strengths are deep contact with real scheduling problems, long-lived specialist positioning, and a product line clearly centered on hard operational constraints. Its limitations are small-company scale, limited platform productization, and weak public evidence for anything like probabilistic forecasting or modern ML depth.

MJC² vs Lokad

MJC² and Lokad both claim optimization value, but they optimize different classes of decisions.

MJC² is primarily a scheduling and routing vendor. Its core problems are dispatch, crew assignment, multimodal path selection, production sequencing, and real-time replanning when events occur. The public record repeatedly points to dispatch rooms, SCADA-linked production environments, GPS-fed routing, and project-specific optimization engines embedded into customer operations.

Lokad is primarily a predictive optimization vendor. Its core problems are inventory, purchasing, allocation, production planning, and related economic decisions under uncertainty. Rather than solving routing and dispatch in real time, Lokad’s public posture is to turn data into probabilistic forecasts and ranked economic decisions.

So the category difference matters. MJC² is not a weaker version of Lokad. It is a different type of specialist. It is stronger when a client has a hard operational scheduling problem with live disruptions and dense constraints. It is much weaker when the client’s central problem is probabilistic supply chain planning across large assortments and locations.

Corporate history, ownership, funding, and M&A trail

MJC² is an old specialist SME rather than a startup. UK company records show incorporation in 1990, with the business still operating as an independent private software-development company in Berkshire. Public business databases consistently show a very small employee base and modest revenue, which means the firm has persisted for decades without scaling into a mainstream enterprise-software vendor. (1, 2, 3, 4, 5)

There is no visible acquisition trail and no venture-funding story of note. Instead, the strongest public commercial signals come from project participation and repeated roles in EU-funded optimization programs. That makes MJC² look more like a stable optimization craft shop than like a product company aggressively trying to dominate a category. (6, 7, 8)

This structure has two implications. Positively, the company has clearly survived for a long time by doing something real and useful. Negatively, the productization, scale, and support model should be assumed to remain highly specialized and heavily dependent on the vendor’s own small expert team.

Product perimeter: what the vendor actually sells

MJC² does not sell a single unified supply chain platform. It sells a family of optimization tools and project-specific engines across logistics, manufacturing, and workforce scheduling. The main named products and surfaces include DISC for logistics and distribution scheduling, PIMSS for production planning and process control, SLIM for strategic transport planning, and additional tools for workforce scheduling, mobile operations, and multimodal or synchromodal freight. (9, 10, 11, 12, 13, 14)

This perimeter is broad in application but narrow in computational style. The product family repeatedly returns to the same underlying challenge: assigning scarce resources to time-sensitive operational tasks under many constraints, with frequent replanning. That creates a coherent center of gravity even though the outward labels vary by industry.

What MJC² does not look like is a modern, cloud-native planning suite with standard multitenant deployment, rich self-service configuration, or a broad forecasting layer. The public product surface is much closer to industrial optimization software delivered as tailored solutions than to mainstream SaaS planning.

Technical transparency

MJC² is moderately transparent in category and weakly transparent in implementation. A technically literate reader can understand from public material that the company is solving routing, scheduling, and replanning problems under complex constraints. The product pages are clear enough about what types of decisions are in scope and which industries the company targets. (9, 10, 11, 13, 14)

The implementation layer is much less visible. Public materials do not disclose the actual programming stack, solver architectures, model formulations, or data infrastructure. “AI-based algorithms” and “lightning-fast scheduling” are mentioned, but without enough technical detail to determine whether the methods are primarily heuristic, metaheuristic, hybrid OR, or something else. (15, 16, 17)

So the company is transparent enough to classify but not transparent enough to inspect rigorously. That is acceptable for a niche engineering shop, but it limits confidence in any stronger claims around AI or technical distinctiveness.

Product and architecture integrity

The product family looks coherent in its own niche. Whether the application surface is transport, manufacturing, or field service, the underlying problem class remains constraint-heavy operational scheduling. That gives MJC² more conceptual integrity than many broader vendors whose modules drift in unrelated directions. (9, 11, 12, 18)

The main weakness is not incoherence but low productization. Public material strongly suggests embedded, project-style deployments tied to SCADA, TMS, GPS, or custom customer systems. This is a respectable engineering model, but it means the architecture probably depends on vendor-led integration and bespoke configuration more than on a sharply packaged SaaS platform. (11, 19, 20)

Security evidence is minimal. There is little public discussion of cloud architecture, trust boundaries, or secure-by-default design. That does not imply negligence, but it does cap the score because the public record is simply too sparse.

Supply chain depth

MJC² is supply-chain-relevant in a narrower sense than most peers in this directory. The company is deeply involved in logistics, transport, ports, bulk flows, rail corridors, and production operations. Those are real supply chain domains, and the constraints described are concrete and meaningful. (9, 10, 14, 15, 21)

The limitation is that MJC² is much stronger on execution scheduling than on classic supply chain planning questions such as probabilistic inventory policy, large-scale replenishment, or economic stock positioning. It is adjacent to those issues, but the public record does not show them as the company’s primary competence.

That leaves MJC² with a solid but capped supply-chain score: clearly not generic software, clearly not a full-spectrum planning vendor either.

Decision and optimization substance

This is MJC²’s best dimension. The public evidence strongly suggests the company is doing real combinatorial optimization rather than superficial analytics. Multi-depot distribution scheduling, workforce rostering, rail freight optimization, synchromodal routing, and SCADA-linked production planning are exactly the kinds of hard problems where real solver work is necessary. (9, 11, 15, 16, 17, 21)

The limitation is not plausibility but visibility and scope. The public record does not show probabilistic planning depth, and the AI language remains vague. So while MJC² looks technically more substantive than many “AI supply chain” startups, it still looks like a classical OR and heuristic optimization shop rather than a transparent next-generation decision platform.

This justifies a relatively strong score within its niche, but not an exceptional one in a broader supply chain comparison.

Vendor seriousness

MJC² looks serious. It has lasted for decades, works on hard problems, and repeatedly shows up in technically relevant project contexts instead of in empty hype cycles. The public language is narrower and more grounded than what many larger vendors use. (1, 6, 7, 8)

The deduction comes from opacity and partial research-theater risk. Because so much of the public record is tied to EU projects, awards, and innovation programs, there is a temptation to over-read that evidence as proof of broad commercial product maturity. It proves technical activity and external selection, not necessarily deep product scale or reproducible commercial success.

So the seriousness score is good but not high. MJC² looks like a real specialist with real technical substance, but one still best understood as a niche optimization boutique rather than a mature platform vendor.

Supply chain score

The score below is provisional and uses a simple average across the five dimensions.

Supply chain depth: 3.8/10

Sub-scores:

• Economic framing: MJC²’s tools are clearly linked to cost, utilization, throughput, service reliability, and network efficiency. That is real economic relevance. The public doctrine is still mostly operational and engineering-driven rather than explicitly economics-first in the supply chain sense, so the score remains moderate. 4/10
• Decision end-state: The company clearly produces concrete operational decisions such as routes, assignments, schedules, and dispatch actions. That deserves real credit. The decision surface is narrow and execution-heavy rather than broad supply chain automation, which keeps the score from going higher. 4/10
• Conceptual sharpness on supply chain: MJC² has a clear thesis around real-time optimization under constraints. That is a genuine point of view. It is a point of view about scheduling more than about supply chain as a full discipline, so the score stays moderate. 4/10
• Freedom from obsolete doctrinal centerpieces: Because MJC² is not built around classic ERP planning dogma, it avoids many stale APS clichés by default. At the same time, it does not replace them with a broader articulated supply chain doctrine, so the score remains moderate. 4/10
• Robustness against KPI theater: The problems MJC² addresses are grounded in live operations and hard constraints, which naturally reduces empty KPI theater. Public evidence is still heavily vendor- and project-curated, so the score remains strong but not exceptional. 3/10

Dimension score: Arithmetic average of the five sub-scores above = 3.8/10.

MJC² is clearly doing real operational work in supply-chain-adjacent domains. The cap comes from its narrow planning scope and logistics-scheduling bias. (9, 11, 14, 21)

Decision and optimization substance: 4.2/10

Sub-scores:

• Probabilistic modeling depth: The public record shows very little evidence of explicit probabilistic modeling or distribution-driven planning. MJC² is much more visible on real-time rescheduling than on uncertainty modeling, so this sub-score remains low. 2/10
• Distinctive optimization or ML substance: There is strong reason to believe MJC² has real, nontrivial optimization capabilities in routing and scheduling. The public evidence still does not clearly expose what makes the methods technically distinctive beyond speed and complexity handling, which keeps the score moderate-positive. 4/10
• Real-world constraint handling: This is one of MJC²’s clearest strengths. Vehicle capacities, skills, shift rules, route constraints, multimodal flows, and process-control realities are all prominent in the public material. 5/10
• Decision production versus decision support: MJC² appears to produce real schedules and dispatch decisions rather than only recommendations or dashboards. That is a genuine positive. Because the systems are still embedded and project-specific rather than broadly automated platforms, the score remains moderate-strong rather than maximal. 5/10
• Resilience under real operational complexity: The company’s visible project record in ports, rail, bulk logistics, and manufacturing strongly suggests resilience under complex operations. The lack of technical detail and broader commercial evidence keeps the score from going higher. 5/10

Dimension score: Arithmetic average of the five sub-scores above = 4.2/10.

This is where MJC² is strongest. It appears to be doing real solver work on hard operational problems, even if the public record remains thin on the underlying methods. (15, 16, 17, 18, 21)

Product and architecture integrity: 3.8/10

Sub-scores:

• Architectural coherence: The product family is unified by one problem class, which is a real strength. Even across different verticals, the company is clearly doing “optimization for operational schedules” rather than drifting into unrelated products. 4/10
• System-boundary clarity: MJC² is fairly clear that its tools sit alongside operational systems such as SCADA, GPS, or TMS rather than replace them as systems of record. That is a healthy boundary. 4/10
• Security seriousness: Public security evidence is sparse. There is no strong public basis for assuming either unusually good or unusually bad security practice, so the score remains conservative. 3/10
• Software parsimony versus workflow sludge: The company’s public product line does not look bloated by generic enterprise CRUD. It looks specialized and solver-centered, which is a positive. The likely bespoke and project-heavy nature of deployments still implies operational complexity, so the score stays moderate-positive. 4/10
• Compatibility with programmatic and agent-assisted operations: The systems clearly integrate with operational data and external applications, which is useful. There is no public evidence of a customer-facing programmable or agent-ready operating model, so the score remains moderate. 4/10

Dimension score: Arithmetic average of the five sub-scores above = 3.8/10.

MJC² looks coherent and focused, but also heavily dependent on specialist integration and configuration work rather than on a highly productized platform. (11, 19, 20)

Technical transparency: 3.8/10

Sub-scores:

• Public technical documentation: MJC²’s public material makes the problem class and product family fairly understandable. That is better than many peers. It remains weak on actual implementation detail, so the score stays moderate. 4/10
• Inspectability without vendor mediation: A technical reader can understand that MJC² is doing scheduling and routing optimization and can infer many of the operational constraints involved. The algorithmic layer itself remains opaque, which caps the score. 4/10
• Portability and lock-in visibility: The public record makes it clear that MJC² tends to integrate into specific operational landscapes rather than replace them wholesale. That helps assess its boundary and likely lock-in shape. The practical migration burden remains hard to judge, so the score is moderate. 4/10
• Implementation-method transparency: The company is fairly open, indirectly, that solutions are project-style and tightly integrated with customer operations. That at least makes the delivery model legible. There is no real public implementation methodology or deployment architecture guide, so the score remains moderate. 3/10
• Evidence density behind technical claims: Public claims about optimization speed and operational fit are backed by many project references and domain-specific pages, which is a positive. The lack of formal method disclosure still limits the score. 4/10

Dimension score: Arithmetic average of the five sub-scores above = 3.8/10.

MJC² is transparent enough to classify confidently as a scheduling specialist. It is not transparent enough to let an outsider inspect the solver stack in a serious way. (9, 10, 11, 15)

Vendor seriousness: 4.0/10

Sub-scores:

• Technical seriousness of public communication: MJC²’s public communication is narrow, operational, and grounded in real scheduling problems. That is a meaningful strength. It avoids much of the empty theater common in broader supply chain software. 5/10
• Resistance to buzzword opportunism: The company does use “AI” language in project contexts, but far less aggressively than many modern peers. The modest use of those terms, combined with its specialist positioning, supports a relatively good score. 4/10
• Conceptual sharpness: MJC² has a clear point of view around solving hard scheduling and routing problems in real time. That is sharper than many broad suite vendors. The point of view is still narrower than a general theory of supply chain optimization, so the score remains moderate-positive. 4/10
• Incentive and failure-mode awareness: The operational domains MJC² addresses naturally involve hard constraints and failure modes, and the public material reflects that reality to some extent. It still says little about limits of the software itself, so the score remains moderate. 3/10
• Defensibility in an agentic-software world: MJC² retains meaningful defensibility because real-time routing and scheduling under complex constraints is not easy to commoditize into generic workflow software. The small size and bespoke-delivery model still constrain how strong that defensibility looks commercially, so the score remains moderate. 4/10

Dimension score: Arithmetic average of the five sub-scores above = 4.0/10.

MJC² looks like a serious niche solver company with real technical craft. The main ceiling is not hype but limited scale and limited public method disclosure. (6, 7, 8, 18)

Overall score: 3.9/10

Using a simple average across the five dimension scores, MJC² lands at 3.9/10. This reflects genuine optimization substance in a narrow operational niche, combined with limited productization and limited public evidence for broader planning sophistication.

Conclusion

MJC² is a real optimization vendor, not a brochure. Its public record strongly suggests competence in hard scheduling and routing problems where live operational constraints matter and generic ERP logic is insufficient.

The caution is category fit. MJC² is not a broad supply chain planning suite and not a transparent probabilistic optimization platform. It is best understood as a specialist solver partner for routing, dispatch, process scheduling, and related operational problems. For buyers with those problems, it could be highly relevant. For buyers seeking inventory, purchasing, or network-level planning under uncertainty, the public record suggests a much weaker fit than vendors such as Lokad.