Skip to Content

RASID SERVICES

A clear path to a working setup

Define preparation, device configuration and practical checks before handover.

HOW TO GET STARTED

A scope you can follow

01

Prepare the site

Agree on mounting points, cable paths, power and access to the site.

02

Configure the equipment

Review network settings and device compatibility within the agreed scope.

03

Test and hand over

Check the agreed use cases and record device and access ownership.

What to have ready

  • An agreed list of equipment and installation tasks
  • Required power and network availability
  • An authorized person for the site and handover
  • Testing points and configuration documentation

GOOD QUESTIONS. BETTER CHOICES.

Details worth checking

What determines the service quotation?

The equipment, site conditions and agreed tasks define the scope. Confirm the inclusions, timing and any additional work in the quotation.

YOUR NEXT STEP

Let’s put the details together

Tell us what you want to achieve, and start with a clear requirement.

Talk to our team

PRACTICAL ANSWERS

Installation and service questions

What is the difference between supplying equipment and installing it?

Supplying equipment and providing installation or configuration are separate scope items unless explicitly combined in the quotation. Confirm the site work, materials, configuration and testing included before accepting the service.

What should I prepare for a technical consultation?

Describe the desired outcome, current setup and observed limitations. Add model numbers, approximate quantities and a site sketch where useful, but do not send passwords or sensitive customer data with an initial enquiry.

How is the installation scope confirmed?

Review device locations, cable routes, power and network prerequisites, working access and the required tests. Ask for any exclusions or additional work to be documented before scheduling, rather than treating a product price as an installation commitment.

Can configuration work affect existing operations?

Discuss the expected changes and any interruption risk with the implementation team. Agree on a maintenance window, current configuration backup and rollback criteria before changes are made to a live system.

What should a maintenance request include?

Provide the affected model, a clear symptom description, when the issue started and any recent changes. Include relevant error text or non-sensitive photos, and avoid repeated resets that could remove useful configuration or diagnostic information.

Are support hours and response times the same for every service?

Do not assume a service level from the website design or a product listing. Confirm the support channel, hours, response targets and exclusions in the applicable quotation or agreement before relying on them for an operational plan.