IoT Platform User Guide
Model Optimization
Register models, define parameters, create experiments, and manage production sets.
The Model Optimization module is used to define model-level parameter sets, evaluate tuning behavior in experiments, and promote stable configurations into production. In the current Lexmark UI, this module opens from Apps > Model Optimization and uses a card-style model list instead of the legacy tile flow. Each model then has tabbed work areas for Parameters, Experiments, Productions, and Settings.
This area is designed for iterative optimization: register a model, define error-type parameters, create experiments, and then maintain production-ready sets. The UI also supports direct metadata maintenance and delete flows from the settings tab. Availability of create/edit/delete actions depends on your role permissions.
Open Model Optimization
To open Model Optimization, do the following:
- In the left sidebar, go to
Appsand clickModel Optimization. - Confirm the page header shows
Model Optimization. - Confirm top-right actions include
CreateandAsk Optra(based on permissions).
Understand the Model List
The home page shows model cards with badges and relative update times so teams can quickly identify candidate models for tuning or maintenance. When no models exist, the page displays an onboarding empty state with guidance to create the first model.
- Review model cards for name, badges, and
Last updatedmetadata. - Click a model card to open its tabbed detail workspace.
- If no models are listed, verify the
No models foundempty state and continue with model creation.
Register a New Model
To register a new model, do the following:
- On the Model Optimization page, click
Create. - In
Register a new model, complete:NameProduct FamilyRule TypeDescription
- Click
Save. - The system opens the new model in the
Parameterstab.
Use the Parameters Tab
The Parameters tab manages model error types and tuning bounds used by downstream experiment and production sets. The table supports search and row-level edit actions, and the top actions support both new parameter creation and parameter-copy workflows from another model.
- Open a model and stay on the
Parameterstab. - Use search to filter parameter rows.
- Review parameter columns such as:
Error TypeThreshold(min, max, default)Suppression Period (Days)(min, max, default)Repetition Count Window(for repetition rule types)Updated
- Click a row to open
Edit Error Type. - Use the trash action to open
Remove Parameterand confirm deletion when needed.
Add a New Parameter (Add Error Type)
To add a new parameter, do the following:
- In
Parameters, clickNew Parameter. - In
Add Error Type, clickSelect typeand choose an error type. - Enter
Description. - For supported model types, configure threshold/suppression/repetition min-max-default values.
- Click
Save.
Copy Parameters from Another Model
To copy parameters from another model, do the following:
- In
Parameters, clickCopy Parameters. - In
Copy Error types, choose a source model fromParameter set. - Review rows and confirm which types are importable (existing types are marked as already present).
- Click
Import.
Use the Experiments Tab
The Experiments tab is for non-production model tuning sets. It supports list search, quick drill-in, and creation of named experiment sets. This allows teams to iterate safely before promoting settings into production contexts.
- Open the
Experimentstab. - Use search to find experiment sets by name.
- Review table columns (
Name,Parameters,Updated). - Click
New Experimentto open the creation modal. - Enter
Experiment NameandDescription, then clickCreate. - Click an experiment row to open experiment details/settings.
Configure and Run an Experiment
After creating an experiment set, add the error types to evaluate, define the historical analysis window, and run threshold optimization. Experiment runs are non-production: they do not change deployed sets or generate alerts.
- Open an experiment set from the
Experimentstab. - Click
Add Parameter, thenSelect typeand choose an error type. - Enter
Suppression Period (Days)andRepetition Count Window. Threshold is not set here — it is evaluated across candidate values. - Set
Input Date(inclusive end date of the window) andPast Period Data(months of history; defaults to 24 when blank). - Click
Save, then repeat for each error type. - Click
Runto start the optimization.Runis disabled while a run is in progress. - When the run completes, open the
Performancetab to review results.
Review Experiment Performance Results
The Performance tab shows how candidate thresholds would have performed on historical data. Use it to compare thresholds and select a setting before promoting to production.
- Open a completed experiment and click the
Performancetab. - Review the four metric plots:
Precision(Valid Alert Rate)Recall(Service Case Detection Coverage)F-score(Balanced Alert Score)Average Monthly Alert Volume
- Review the
Recommended Parameter Settingstable for the recommended threshold per error type. - Select a threshold that fits the business priority (precision, recall, F-score, or alert volume).
Use the Productions Tab
The Productions tab tracks deployed sets that are active for operational use. This view mirrors experiments but focuses on production lifecycle and deployment context.
- Open the
Productionstab. - Use search to find production sets.
- Review table columns (
Name,Parameters,Updated) and deployment badges. - Click
New Production. - In
New Production, complete:Production NameDescription- Parameter strategy (
Copy parametersfrom experiment or create/select a new set, based on model type)
- Click
Create. - Click a production row to open production details/settings.
Configure and Deploy a Production Set
After creating a production set, add its error-type parameters and deploy it. The Error-Based Rule uses the deployed set on its next scheduled run. Creating or saving a set does not deploy it.
- Open a production set from the
Productionstab. - Click
Add Parameter, thenSelect typeand choose an error type. - Enter
Threshold,Suppression Period (Days), andRepetition Count Windowwithin the displayed ranges. - Click
Save, then repeat for each error type. - Review the set, then click
Deploy. - Confirm the set shows a
Deployedbadge in the Productions list.
Deployment activates the configuration; alerts are generated only when a later scheduled run finds data that meets the criteria.
Promote an Experiment to Production
Promotion creates a production set from an experiment, carrying over its error types and windows. Promotion does not deploy the set — apply the selected thresholds and deploy separately.
- Open a completed experiment from the
Experimentstab. - Click
Promote to Production. - In the modal, review the
Production Name(prefilled from the experiment), adjust if needed, then confirm withYes, promote. - In the new production set, open each error type and enter the
Thresholdselected during the results review. - Click
Save, then repeat for each error type. - Click
Deploy, then confirm theCurrently deployedbadge.
Use Settings (Edit and Delete)
The Settings tab provides model metadata maintenance and irreversible delete actions. Use this area for title/description corrections and controlled retirement of models that are no longer needed.
- Open the
Settingstab. - Review model metadata and copyable
Model ID. - Click
Editto openEdit model. - Update
Titleand/orDescription, then clickSave. - To remove the model, click
Delete model. - In the confirmation modal, review the warning (
This action can not be undone.) and clickDeleteonly when intentional.
View Error-Based Rule Alerts
Alerts generated by a deployed Error-Based Rule appear in the Alert Queue under Alerts. Use this area to identify Error-Based Rule alerts, review details, and update status.
- In the navigation sidebar, go to
Operationsand clickAlerts. - Identify Error-Based Rule alerts by name.
- Review list columns:
Severity,Alert,Status,Last Alert,Device, andAccount. - Click an alert to review its message, metadata, and timeline.
- Set the status —
Mark as open,Mark as case created,Resolve, orDismiss— then save. - To view a device's full alert history, open the device under
Devicesand click on theAlertstab.