Use cases
Use cases
- Quantize an eligible model to evaluate a target memory profile.
- Explore domain, language, or training adaptations when supported for the source release.
- Package an artifact for customer delivery or an available hosting path.
Solutions
Assess model transformation options against release evidence, target hardware, runtime compatibility, language needs, and delivery mode. Work from a specific source model and acceptance criteria rather than assuming every transformation is available.
Business challenges
A transformation is useful only when its technical feasibility, rights, runtime, and target environment are considered together.
Relevant products
The Model Transformation area exposes eligible capabilities and a builder; the catalogue determines what is currently published and orderable.
Logical architecture
The process preserves a traceable path from a source release through selected operations to a delivered artifact.
Use cases
Deployment considerations
Define the source and target releases, operations, hardware, runtime, evaluation set, artifact handling, and whether delivery is downloadable, hosted, or both. Availability is verified for each combination.
Integrations
Commercial engagement
Use the builder for listed eligible options and displayed active prices. For unsupported combinations or custom evaluation requirements, request a technical review before treating the configuration as orderable.
Documentation
Check release-specific technical support and builder behavior directly in the existing engineering product area.
Trust and responsibilities
Record source identifiers, licenses, transformation steps, dependencies, and evaluation conditions. A transformation estimate or package description is not a benchmark guarantee; results and acceptance criteria must be agreed and reported for the work.
Architecture resourcesPricing and procurement
The builder uses currently active commercial records for eligible configurations. Hosting is optional and may be priced separately. Options without validated capability or active orderability should not be treated as purchasable.
Frequently asked questions
No. Technical capability, model rights, release evidence, runtime compatibility, and commercial availability are assessed for each release and requested operation.
No general performance outcome is promised. Agree on the evaluation method and target criteria, then review measured results for the specific artifact and environment.
Bring model identifiers, runtime requirements, and evaluation criteria to an engineering discussion.