Pilot / Early Access Asset, AssetLight and Standard by MetraSlate: Metrology Edition.
Start with the work you need to run. Plan a pilot that tests the product, the records and the operating responsibilities together, with clear decisions before adoption.
The evaluation follows five steps. The pilot proposal sets their scope and responsibilities; there is no fixed rollout timeline published here.
01
Demonstrate the Fit
Bring an equipment list, a representative workflow and the decisions your team needs to make. MetraSlate demonstrates the relevant product and identifies the configuration and limitations to evaluate.
02
Set the Pilot Scope
MetraSlate and your decision owner define the product, people, sites, workflows, commercial terms and acceptance criteria. Name the people responsible for configuration, data preparation and review.
03
Validate a Migration Sample
Your data owner supplies an authorized representative export. Review mappings, imported records, relationships and linked attachments together, and record exceptions before authorizing a wider transfer.
04
Accept Roles and Workflows
Your operators and acceptance owner exercise the specified tasks, permissions and failure cases in the pilot configuration. Keep unresolved requirements visible in the adoption decision.
05
Complete the Operating Handover
Before adoption, plan training, support contacts, update procedures and backup and restore responsibilities. Confirm who accepts the deployment, what remains open and how you can export or leave.
Commercial Terms
Know What the Proposal Covers.
MetraSlate prepares the proposal around your defined scope. Prices and standard package limits are not published here; the written proposal must identify the charges, inclusions and responsibilities before you proceed.
Price Basis and Inclusions
Confirm the product and edition, enabled capabilities, subscription or other licensing basis, and how users, sites or scope affect the quoted price. These are items to resolve in the proposal, not a published per-user or per-site tariff.
Implementation and Import Assistance
Identify who prepares and cleans the source data, maps fields, configures the workspace and checks the results. State which assistance is included and which work requires a separate charge or agreement.
Training and Support
Define who trains operators and administrators, what training is included, the support contact and escalation route, and any specified support hours or response commitments.
Acceptance and Next Steps
Name your acceptance owner and the MetraSlate contact. Record the pilot scenarios, evidence to review, outstanding limitations and the commercial decision required before wider adoption.
Migration and Record Acceptance
An Equipment Import Is a Starting Point.
The current CSV and XLSX import creates new equipment records. It does not establish complete migration of historical service records, business relationships or attachments from another system.
Prepare the Sample
Your data owner selects representative records, including incomplete or conflicting examples. Define the identifiers, field meanings and source documents before mapping them.
Inspect the Result
Check record counts and identifiers, then open sampled records and their linked attachments. Verify that relationships and document associations retain their intended meaning. Record anything that needs manual work or remains outside the import scope.
Plan the Wider Transfer
Resolve the sample findings before scheduling a larger migration. Confirm source retention, access during the transition, reconciliation and who authorizes the final changeover.
These are arrangements to assess for the selected product and deployment. Availability, technical requirements and service commitments must be confirmed in the proposal.
MetraSlate-Hosted Arrangement
Confirm the Hosted Scope.
Ask MetraSlate to identify the environment, data location and application services it would operate. Define your administrators’ responsibilities for accounts, access and day-to-day use.
Confirm Before Adoption
Application and infrastructure ownership, monitoring, update coordination, support, backup policy and restore responsibility.
Customer Infrastructure
Assess the Environment First.
Bring your infrastructure requirements and technical owner for a feasibility review. A discussion of this arrangement is not confirmation that self-hosted delivery is available for every product or configuration.
Confirm Before Adoption
Supported infrastructure, installation and maintenance ownership, access for support, update compatibility and recovery procedures.
Backups and Restore
Name the backup operator and restore owner. Set coverage, frequency, retention, recovery objectives and how restoration will be checked for your deployment. This page does not establish a restore guarantee or service level.
Export and Exit
Specify which records, relationships and files can be exported, their formats, any assistance or charges, and the limits of the export. Decide how you will validate the result and retain required records before ending access.
Technical Review
Review the Relevant Evidence.
Read the security and provider information alongside the pilot scope. Confirm which controls, connections and operating arrangements apply to your configuration.
