rAI-Q / GOVERN

Modeling & Model Lifecycle

Supports a lifecycle-governance structure connecting model artifacts calculated in SIMCA or another analytical engine with candidate intake, independent review, approved versions, and deployment evidence.

rAI-Q SIMCA Model Governance PoC approved version tree screen

Candidate Intake & Evidence

The PoC presents intake of an rAI Pipeline, SIMCA .usp, or external model file as a candidate with file-verification information, performance metrics, and acceptance-target snapshots.

Candidate file and metadata intake
SHA-256 verification information
Project-defined metrics such as R², RMSECV, and MAPE

Independent Review & Signature

Separates Modeler and Reviewer perspectives while recording change intent, changed areas, approval or rejection comments, and re-authenticated signature information.

Modeler / Reviewer role separation
Approve / Reject with comment
Signature meaning, user, role, and timestamp

Approved Version & Package

Illustrates registration of an approved model as a new version with prior-version status, cross-version performance, reports, and export-package evidence.

Approved Version Tree and prior-version status
History / Model / Release Report
Package records for artifact, hash, metadata, and signatures

SIMCA MODEL GOVERNANCE POC

Connect review, approval, and version evidence after model calculation.

The supplied PoC screens illustrate a governance concept in which a SIMCA .usp or other model artifact is registered as a candidate, independently reviewed and signed, registered as an approved version, and connected to reports and a Version Tree Package.

01Candidate Model
02Review Request
03Authenticated Decision
04Approved Version
05Controlled Package

rAI-Q SIMCA PoC candidate model intake and review submission screen — 01 / CANDIDATE
**Candidate intake and review submission**Example intake of an rAI Pipeline, SIMCA .usp, or external model file with performance and acceptance snapshots

rAI-Q SIMCA PoC request status and build history screen — 02 / HISTORY
**Request status and build history**Example Modeler view of In Review, Rejected, and Approved states with file-verification and candidate-registration history

rAI-Q SIMCA PoC reviewer approval and rejection screen — 03 / REVIEW
**Reviewer assessment and decision**Example review of intent, changed areas, performance metrics, acceptance targets, and decision comments

rAI-Q SIMCA PoC reviewer re-authentication and electronic signature screen — 04 / SIGN
**Re-authenticated signature**Example signature prompt recording approval or rejection meaning together with user ID, role, and timestamp

rAI-Q SIMCA PoC approved model version tree screen — 05 / VERSION
**Approved version tree**Example review of approved versions, prior-version status, model performance, and cross-version changes

rAI-Q SIMCA PoC Model Development and Performance Report screen — 06 / REPORT
**Model, history, and release reports**Example report connecting approval, data, preprocessing, modeling, and acceptance-criteria evidence

rAI-Q SIMCA PoC signed Version Tree Package screen — 07 / PACKAGE
**Signed Version Tree Package**Example export combining model artifact, SHA-256, tree history, metadata, report snapshot, and signature records

POC / SCOPE BOUNDARYBased on PoC and supplied screens. Current commercial functions, supported file formats, analytical-engine integration, electronic signatures, reports, and export scope are confirmed by product edition, license, validation status, and project agreement. Final regulatory suitability and approval remain within the customer QMS.

CONTROLLED BOUNDARIES

Defined scope and clear responsibility boundaries.

SCOPE

Contracted scope

Actual functions, analytical engine, interfaces, and layout are confirmed by product version, edition, license, and approved SOW.

RESPONSIBILITY

Customer approval

The customer owns intended use, infrastructure, accounts and access, SOPs, data and model approvals, and manufacturing and quality decisions.

EXCLUSIONS

No regulatory outcome guarantee

Software and support services do not guarantee regulatory approval, final validation acceptance, or process performance.

MAINTENANCE

Operating support

Basic maintenance is included for the first year; annual maintenance is contracted separately from year two.

BUSINESS INQUIRY

Discuss Project Scope

We define the implementation scope around your instrument environment, intended use, model operating approach, validation needs, and timeline.

Business Inquiry Paid PoC and implementation scope are confirmed through separate consultation.