ProModel review

How each criterion scored

1. 1

   Modeling capability

   10 / 20 out of 20

   How much of a real process the model can represent: routing, resources and shifts, queueing, batching, statistical distributions and control logic.

   Not assessed. Half weight, carried so this record has the same shape as the others. A discrete event product of long standing, with model building documented from CAD files and process maps. The published material does not describe the distributions, replication handling or control logic that the scored records in this assessment are scored on.

2. 2

   Ease of learning

   10 / 20 out of 20

   How long it takes to reach a first useful model. Onboarding, templates, and how much scripting the product makes unavoidable.

   Not assessed. Half weight. Academic packages exist and are described as limited versions, with no limits, no price and an application form rather than a download. Nothing published establishes what a first model costs a new user in time.

3. 3

   Results, analysis and experimentation

   10 / 20 out of 20

   Depth of reporting, bottleneck analysis, scenario comparison, repeated runs, and structured experiments.

   Not assessed. Half weight. An Output Viewer is documented for comparing results, with export to external business intelligence tools, which is a real reporting story. Its depth cannot be established from what is published.

4. 4

   Pricing transparency and total cost

   8 / 15 out of 15

   Whether a price is published at all, what training, renewal and hosting add to it, and what the free tier really allows.

   Not assessed. Half weight. No figure appears at any tier for any product in the suite, and no third party source carries one specific enough to repeat. On the scored records this would be a low number rather than a middling one, which is exactly why the half weight here is not a finding.

5. 5

   Visualization and stakeholder communication

   5 / 10 out of 10

   How well a finished run persuades somebody who did not build the model. A three dimensional view is one route to that, and not the only one: an animated run, a heatmap showing when a queue builds, or a chart ranking every step by what it costs can each do the same job at a fraction of the effort to produce.

   Not assessed. Half weight. Animation and visual modeling are described in general terms. Whether a three dimensional view is offered is not established, so the capability field reads not stated rather than yes or no.

6. 6

   Platform and deployment

   5 / 10 out of 10

   Which operating systems are supported, whether it runs in a browser, and how teams share and govern work.

   Not assessed. Half weight. Windows is evident from the published material and from a student edition that names Windows 10. The publisher's documentation lists hardware requirements and names Windows 10 only, and nothing found names macOS, Linux or a browser version.

7. 7

   Learning resources and support

   2 / 5 out of 5

   Documentation, training, an active community, and academic access.

   Not assessed. Half weight, rounded down from two and a half. Documentation exists and an academic program is described. Nothing published establishes a certification path, a published textbook or the university reach that the strongest records in this assessment are scored on.