Minitab Real-Time SPC

The published feature list identifies I-MR, XBar-R, XBar-S and I-MR-R/S charts, plus P, NP, C, U and Laney attribute charts with applicable Nelson tests. Buyers should still validate chart selection, rational subgrouping and rule configuration with their own process data.

The feature page lists capability analysis for normal and non-normal data. Distribution choice, process stability, measurement-system adequacy and the basis of specification limits remain buyer-governed validation decisions.

Sampling plans define required measures, use a standard form or configurable check sheet, and can be scheduled, on demand or required at startup. Instructions and collection order can be configured for the operator workflow.

Official documentation distinguishes manual entry, gage collection, automatic collection from one Minitab Connect table and API streaming. Calculated measures are available with form or gage collection, not automatic or streaming collection; confirm device middleware, Connect entitlement and supported measure type per sampling plan.

The API uses a key, base URL and endpoint. The station streaming endpoint is documented for continuous process and output measures, with up to 50 subgroups and 1,000 observations per request and separate success and failure counts. The buyer integration must preserve timestamps and descriptors, reconcile partial success and make retries idempotent.

Administrator, Engineer, Supervisor and Operator roles and configurable permissions are documented. Access assignments can expose related product and process information through group and station relationships, so least-privilege behavior must be tested with representative accounts.

The support library lists station, operator, supervisor and engineering views, including current-performance and process-quality summaries. Availability depends on the user's role and assigned access; dashboard output does not replace validation of the underlying chart configuration.

Users can subscribe by product, process, station or tag and choose email, text or both, with individual or daily delivery for documented event types. Confirm carrier and regional delivery, escalation, acknowledgement and ownership because a notification is not a closed-loop CAPA record.

The station dashboard distinguishes out-of-control from out-of-specification conditions. Data-entry documentation separately describes specification warnings and absolute limits that can reject a manual value or convert an imported value to missing. Buyers should configure and route these conditions separately.

Authorized edits rerun plotted points, statistical tests and summary metrics. Previously assigned causes and corrective actions can remain when an edit removes the original flag, so regulated buyers should require an immutable before-and-after history, approvals and reconciliation evidence rather than infer them from recalculation alone.

Station and editing guidance describes recording assignable causes, corrective actions and comments around flagged data. This operational context should not be represented as a complete quality-event, approval or CAPA system unless the proposed workflow demonstrates those controls.

The station dashboard supports export of the selected period to CSV and Minitab worksheet format. Validate identifiers, timestamps, units, descriptors, limits, exception context and maximum export range against records and downstream analysis requirements.