Skip to content
The start date is the day your device arrives, not the day your engagement begins. How the start date works

Device requests

A device request is how you get a device for an engagement. You say what you need and when you need it, and a configured device shows up ready to test. You can ask for physical hardware shipped to a site, or a virtual appliance you download and run yourself. Get the dates or contact details wrong and you can lose days to shipping problems.

You can request three things:

  • Physical hardware devices are custom Linux computers with cellular failover and built-in VPN connectivity. You use these when you need a box on the client’s network.
  • Virtual appliances are downloadable VM images (OVA, QCOW2, and other formats) for whatever hypervisor the client runs. Reach for these when shipping hardware is not an option.
  • Wireless testing equipment means optional ALFA wireless cards bundled with a physical device for wireless work.

Every request is subject to U.S. export control regulations and VTEM Labs’ export policies. Some countries require extra review or cannot receive ARROW products at all, and choosing a virtual appliance does not change that, because releasing an image is an export in the same way a shipment is. The Export and Deployment Policy sets out the rules and Annex A of it lists every destination. The ARROW Platform also flags the destination for you in two places, on the client location as soon as you enter a non-US country, and again on the request itself when you pick a delivery location outside the US. The US territories are not foreign destinations, so Puerto Rico, the US Virgin Islands, Guam, American Samoa, and the Northern Mariana Islands are treated as domestic and are not flagged. Contact support before you commit to a delivery location you are unsure about, since requests to restricted countries can incur legal review fees and add significant time to processing.

You cannot create a request until the client exists in the ARROW Platform. The Clients section holds every client in your organization along with their locations, assigned devices, and primary contacts. Only Admins and Managers can manage clients.

ARROW Console Clients page ARROW Console Clients page

The Clients page listing each client with its locations, devices, and primary contact

ARROW Console Clients page ARROW Console Clients page

The page works like Devices, with a collapsible filter rail on the left that holds the search box and lets you narrow the list by Devices or Locations, and View above the table chooses which columns show.

To add one, open Clients in the sidebar and click Add client. In the dialog, give the client a Company name (required) and an optional Website, then add at least one Location and one Point of Contact. Leave Website blank and ARROW uses the domain of a contact’s work email. Your organization can hold each client only once, so one client’s requests do not end up split across two records: if the name matches a client you already have, ignoring capitals, punctuation, and endings such as Inc. or LLC, the dialog says so under Company name, and you open that client and add to it instead of creating a second one. Click Create client when you are done.

Add new client dialog Add new client dialog

The Add new client dialog with Basic information, Locations, and Points of contact sections

Add new client dialog Add new client dialog

A client can have several delivery locations, which matters when devices go to different offices or project sites. Add them from the Locations section of the Add new client or Edit client dialog. Click Add location and enter a recognizable name (for example, “NYC Headquarters” or “Chicago Branch”), the full shipping address, and contact details for that site. Pick the Country from the list, which you can search by name or code; a location saved earlier with a country the list does not recognize shows it in red, and the client cannot be saved until you choose one. The location you pick later on the request is where the hardware ships, so name them clearly.

The Point of Contact is the person the carrier calls when a delivery needs a signature or hits a snag.

Points of contact section of the Add new client dialog Points of contact section of the Add new client dialog

Adding a Point of Contact to a client

Points of contact section of the Add new client dialog Points of contact section of the Add new client dialog

Open Device requests in the sidebar. You will see your existing requests in a table with a New request button in the top right, next to View for choosing which columns show, Refresh, and Share setup video (see Sharing the setup video). When the table is wider than the space it has, it drops its least important columns instead of making you scroll sideways, and brings them back once there is room again, for example when you collapse the filter rail. The device, its Progress, and the row’s actions menu are never dropped, and a column dropped this way stays ticked under View, marked Hidden to fit. The table also shows as many requests as fit the height of the window and pages the rest. Rows per page under the table starts on Fit to screen, which shows how many rows that currently is, and you can pick 10, 25, 50, or 100 instead. Filtering lives in the rail down the left side, with a search box, then Status, Type, Clients, Opportunities, and Consultants sections, each listing how many requests match. The search box looks through all of your requests, not only the page you are on, and finds a request by its device’s hostname or serial number, a virtual machine’s included, as well as by client, opportunity number, consultant, or tracking number. Completed requests are hidden by default, so tick Show complete at the bottom of the rail if you are looking for an old one, and use Clear all filters to get back to the full list. The button beside the search box collapses the rail when you want the table at full width. On a phone, or in a narrow browser window, the rail starts closed, and Show filters, the arrow tab at the top left of the page, opens it. Your search, filters, and sort order are kept in the page’s address, so a refresh or the Back button brings back the same list, and you can copy the link to share it.

ARROW Platform Device Requests page ARROW Platform Device Requests page
The Device Requests page showing the request queue
  1. 1 Start a new device request here.
  2. 2 Filter the queue from the rail on the left. Completed requests are hidden until you tick Show complete.
  3. 3 Each request shows the device, VM name, client, opportunity number, consultants, progress, engagement dates, where it ships to, and the next step. Click a row to open its details. The actions menu holds View details, Cancel request, Send setup instructions, Share setup video, and Contact support.

Click New request to open the form. It walks you through four numbered steps, Device, Schedule & delivery, Software, and Consultants, with a Request summary panel down the right side that ticks each step off as you finish it. If you cannot submit yet, the line above the Submit Request button names what is still missing. The first step is the device type, and the rest of the form changes depending on whether you pick Physical device or Virtual machine.

A physical request covers one device per submission. Fill in these fields:

FieldWhat it does
Device typeSet this to “Physical device”.
Device specificationThe device you need: ARROW or OBSIDIAN. Each is marked “Available” or “Not available”, and one that is not available cannot be chosen. Once you pick one, the Device specifications panel shows its CPU, RAM, VM storage, built-in eMMC, ethernet, WiFi, and cellular, as a range where the hardware models behind it differ. The device you receive is one of the hardware models that meet that specification, chosen when your request is approved.
Wireless cardsHow many ALFA wireless cards ship with the device (None, 1 Card, or 2 Cards). Choose based on your wireless scope.
ClientThe client this engagement is for.
Delivery locationWhich of the client’s locations to ship to.
Request PeriodThe start date is the day your device arrives (see How the start date works); the end date drives the return. These are commitments, not labels.
Images to installThe VM images to load into the device’s App Library so they are ready to deploy on arrival. Up to 200GB in total; the form keeps a running total and will not let you add an image that would push you over.
ConsultantsThe team members assigned to the engagement.
Hostname (optional)The name the device goes by on your client’s network and in the ARROW Console. Leave it blank and ARROW generates one (pve- followed by four characters). Set one when the device has to look like the rest of the client’s equipment, such as a laptop-style asset name. Use letters, digits, and hyphens only, up to 63 characters, with no hyphen at the start or end. The device shows the name and sends it to the client’s network exactly as you typed it, capitals included; anywhere a name is looked up, such as its VPN address, capitals and lowercase count as the same name. A hostname must not match one that any device or VM in your organization has now or had before, and a request with a taken hostname is refused when you submit it. You can change the name later from ARROW Manager on the device.

Long-term deployment sits under the dates. Turn it on when the device stays on site indefinitely, such as for recurring quarterly testing. The end date becomes optional, the device drops out of return reminders, and standard billing still applies.

The two models suit different jobs:

Which device should I choose?

  • ARROW is the compact, lower-cost model, with an Intel N5105 (4 cores), 8GB RAM, 512GB encrypted NVMe, and one Gigabit ethernet port. It fits most engagements, including standard testing, travel, and anywhere a smaller, simpler device works.
  • OBSIDIAN is larger and costs more, with an Intel i5-1340P (12 cores), 32GB RAM, 1TB encrypted NVMe, dual 2.5GbE, and Thunderbolt 4 expansion. Choose it when the work outgrows the ARROW, such as hosting VMs on the device, processing large datasets, or running multiple high-speed network links.

See the full specifications and comparison if you are on the fence.

The OBSIDIAN is a premium device and is priced above the standard ARROW. How the premium applies depends on your plan, and the request form shows the exact terms for your plan when you select it. See OBSIDIAN pricing or contact support for a precise quote.

Three optional fields sit behind Additional details at the bottom of the form, collapsed so they stay out of your way: an Opportunity number for your internal project tracking, Notes for any special instructions about the request, and Tags for labelling the request so you can sort and filter on it later. A tag takes a label, an optional category, and a color; on a request for several VMs, the tags apply to all of them.

Timing is where people get burned, and it hangs on one field, so it has its own section below.

New Device Request dialog for a physical device New Device Request dialog for a physical device

The New Device Request dialog with Device type set to Physical device

New Device Request dialog for a physical device New Device Request dialog for a physical device

Submitting a physical request opens Confirm the delivery address before anything is filed. It shows the exact address the shipping label will be built from, the receiver the carrier contacts on delivery, the date the device has to arrive by, and the hostname if you set one. Read it, because a wrong location does not surface anywhere else until a parcel lands at the wrong building, and your organization is billed for that shipment plus the replacement. Click Confirm and submit to file the request, or Cancel to go back and pick a different location. If you asked for rush shipping on a date that standard two-day delivery would reach anyway, the dialog warns you here.

Once you submit, the request goes into the queue for approval. After it is approved, your device is configured, packaged, and given a shipping label. You get an email with tracking information when it ships, and the same tracking shows up on the Device Requests page.

The start date is the day your device arrives, whatever day we start working on the request and wherever your project timeline sits. We ship to land on that exact date, and never after it.

So set it to the day you want the device in your hands. If your engagement starts on a Monday and you want the device on site the Friday before, put Friday, not Monday.

A few things the portal handles for you:

  • Weekends. Transit is counted in business days, so a two-day shipment sent on a Friday arrives Monday. You do not need to pad the date to route around a weekend. A start date that lands on a Saturday or Sunday is delivered the Friday before, because the carriers do not deliver on those days.
  • Same-day cutoff. Requests are processed until 6 PM Eastern. Anything after that starts the next business day, and the form tells you when that pushes your earliest possible date out.
  • Dates we cannot reach. The form will not let you pick a start date that no service can make. If your date is reachable by overnight but not by standard shipping, it offers Need it faster? Add rush shipping and asks for a reason before you can submit.

Rush shipping is next-day air, offered when your start date is too soon for standard two-day delivery. It is best effort, not a guarantee. On a weekday, next-day air means the following business day. Over a weekend it usually means Monday, so a rush shipment sent Friday arrives Monday rather than Saturday.

None of our delivery dates are guaranteed. Carrier estimates are estimates, weather happens, and we tell you what we expect rather than what we can promise.

Early delivery costs something, and how much depends on your plan:

  • UAP Plus. Your allocation is a pool of concurrent device time. A device occupies a slot from the moment it is delivered, whether or not your engagement has started, so shipping a device out early spends part of your allotment on a device sitting in a box. This is the main reason to keep the buffer short.
  • Pay-as-you-go. Billing does not start early. If the device arrives before your start date, the clock starts on the start date itself. If it arrives on the start date, billing starts at the hour it lands. If it arrives after your start date, billing starts at the hour it lands then too, so a late delivery is never billed as if it had been on time.

Once the device is delivered, open the request: the Delivered step on its Timeline, and Arrival under Engagement, show whether the delivery landed on the start date, a number of days early, or a number of days late. If something looks wrong there, that is worth a support ticket.

See Billing for how device hours turn into charges.

Use a virtual appliance when you cannot ship hardware. You can request up to 10 VMs in a single submission. Fill in these fields:

FieldWhat it does
Device typeSet this to “Virtual machine”.
VM quantityOne VM unless you say otherwise. Turn on Request multiple VMs for this engagement to pick a Number of VMs, from 1 to 10.
VM configurationShown once you ask for more than one: a unique name for each VM (for example, “US East” or “NYC HQ”) so you can tell them apart later, plus its own type and network settings.
Hostname (optional)The VM’s own system hostname. Leave it blank and ARROW generates one. The image name is never part of the hostname. A hostname you set must not match one that any VM or device in your organization already has, including one from a finished request, and each VM on a request needs its own, because two VMs on one name can send ARROW Control for one to the other. Names are compared the way the VM will carry them, in lowercase with spaces and underscores as hyphens, so “Lab_01” and “lab-01” are the same hostname. The form marks a hostname typed for more than one VM, and a request with a hostname already in use is refused when you submit it.
VM typeThe output format for the client’s hypervisor: VMware (OVA), VirtualBox (OVA), QEMU/KVM (QCOW2), Azure (VHD), AWS (AMI), GCP (raw.tar.gz), Hyper-V (.vhdx), or Nutanix AHV (QCOW2). Match this to what the client actually runs.
Static IP (optional)A fixed address, gateway, and DNS for each VM, for sites with no DHCP. Leave it blank to use DHCP (the default). Once you enter an address, Gateway is required and has to sit in the same subnet as the address, because a VM without one cannot reach anything outside its own subnet. The form marks the field and says what is wrong, and you cannot submit until it is fixed. ARROW bakes the address into the image. See Static IP Addressing.
VMware compatibility (optional)Shown only for VMware VMs. Sets the maximum hardware version of the delivered OVA. Leave it at Default unless the target ESXi or vSphere host is older and rejects newer versions (for example, ESXi 6.7 supports up to vmx-15). A lower version imports on older hosts.
ClientThe client this engagement is for.
Request PeriodThe start and end dates of your engagement.
Images to installThe VM images to include in the App Library, up to 200GB in total.
ConsultantsThe team members assigned to the engagement.

There is no delivery location to choose for a VM. Delivery method confirms the appliance is delivered online, and the download link appears in the ARROW Platform once the build is done.

New Device Request dialog for a virtual machine New Device Request dialog for a virtual machine

The New Device Request dialog with Device type set to Virtual machine, showing VM type and delivery options

New Device Request dialog for a virtual machine New Device Request dialog for a virtual machine

After you submit, the request goes into the queue. Once approved, VM imaging starts automatically, the status moves to “fulfilled” when the images are ready, and download links appear in the portal. You also get an email for each VM once it is ready, with the client it is for and a link to download it.

Every request lives in the Device requests table, and each row shows where it stands and what happens next. Device names the device, with an icon for physical versus virtual: the hostname and serial number once a device is assigned, and until then the hostname you asked for, or the device specification if you did not set one, marked Not assigned yet, and for a VM request its hostname (or the number of VMs) with the hypervisor beside it. VM name shows the names you gave the VMs on the request, with the image beside them, or just the image if you did not name them. Then come the Client, the Opportunity #, the assigned Consultants as initials (hover them for the full names), Progress, the Engagement dates as one range, and Ships to, the city and state the device is going to (hover it for the full address; a VM reads Download link). Next step holds the one thing to do next, and the actions menu at the end of the row holds the per-request options. View adds the columns that are hidden by default: Requested by, Requested on, Type, Shipping status, Imaging status, and Notes.

Progress shows how far the request has come as a short run of steps: Requested, Approved, Shipped, On site, and Returned for a physical device, or Requested, Approved, Built, and Complete for a VM. Hover the steps to see their names. Beside them is where the request stands, with a detail where one helps: the expected delivery date and carrier while a device is in transit, the day of the engagement once it is on site (such as day 9 of 20), long-term for a long-term deployment, or how far a VM build has got. A warning sign appears when a request needs someone to act, and hovering it says why. Return overdue means the engagement has ended and the device has not been sent back, Past end date means a VM is still active after its end date, and Build failed means the VM build did not finish.

Next step gives you a button when there is something to do:

Next stepWhat it does
Download VMShown once a VM is ready. Opens its download page (see Getting to Tracking and Downloads).
Mark completeShown when a VM is past its end date. Opens the same confirmation as Mark complete on the request (see Managing Active Requests).
Track shipment or Track returnShown while a device is on its way out or back. Opens the shipment’s tracking page in a new tab.
Print return labelShown when a return is overdue and the return label exists. Opens the label to print.
Arrange returnShown when a return is overdue and there is no return label. Opens the request.
Contact supportShown when a VM build has failed. Opens a support ticket for the request.

Otherwise the column carries a short note, such as Awaiting approval or Return by Nov 6.

Click a row to open the request in a details drawer on the right. The drawer keeps up to five requests open as tabs across the top, so you can work through several without losing your place, and you can drag its left edge to make it wider. The top of the drawer names the client and the device, with the request’s actions in the […] menu beside it: Edit request, View device (or View VM device), Contact support, and Cancel request, each shown when it applies. Below that, the Next box shows the same progress steps as the table, says what happens next, and holds the button for it, such as Track shipment, Print return label, or Mark complete. Timeline lists each stage of the request with the dates it carries, so you can see what has happened and what is still ahead. Details keeps everything else folded into rows you click to expand: Engagement for the dates, and for a physical device Ships to for the delivery address, Shipping for tracking and labels, Setup email for the site’s setup instructions and setup video, and Device for the hardware specification. A VM has Build instead, with its platform, images, and build status. Consultants follows, then Notes and Tags when the request has them.

The actions menu open on a device request row The actions menu open on a device request row

The per-request Actions menu, with View details and Contact support

The actions menu open on a device request row The actions menu open on a device request row

Contact support, in a row’s actions menu or in the drawer, opens Submit a Support Ticket with the subject and the request’s details already filled in under Device Information, so you only have to say what is wrong. Attach screenshots or files if they help, and click Submit Ticket. The dialog gives you the ticket number and a View ticket button. ARROW support replies in the ARROW Platform and by email, and you can follow the ticket, along with every other one you have raised, under Support in the sidebar.

Status tells you what stage a request is in:

StatusWhat it means
PendingSubmitted and waiting for approval.
ApprovedApproved; your device is being prepared.
FulfilledThe physical device has been imaged, or the VM is ready to download.
ShippingLabel created, device ready for pickup.
In TransitThe device is with the carrier.
DeliveredThe carrier has dropped the package off.
On-SiteThe physical device has been delivered and is operational.
CompleteThe engagement is closed out.

For physical devices, tracking is in two places. Open the request from the Device requests page and expand Shipping under Details. Once the carrier has scanned the package, it leads with where the package is right now, giving you a map of the latest scan, the city and state it happened in, the status of that leg, how long ago the scan was, and an Est. delivery date when the carrier has given one. If the scan location cannot be mapped, you still get it as text. Below that are the carrier and the outbound and return legs, each with its status and tracking number, Track to open its tracking page, and Copy. If the return label has expired or the carrier refuses it, Request new label under the return tracking number replaces it; see Lost the label? Print another one. Once the device starts its return leg, the map follows it back. You will also get an email with the tracking details the moment it ships. A device taken to the site by hand has no outbound tracking and no shipping email. Its Shipping row and its Timeline read Hand delivered, and the return label shows on the Return line once we add one (see Returning devices).

For virtual machines, once a request is fulfilled you can download from either the request details or the Devices page. In the request drawer, the Next box lists each VM with a Download button and, where it is offered, a button that copies its download link. Download there, or Download VM in the request’s Next step column, opens a download page in a new tab that checks your access, prepares a link, and starts the download. The page also shows the file name, its size, when the link expires, and a SHA-256 checksum you can use to confirm a multi-gigabyte file arrived intact. Links are generated fresh on each download and expire seven days after they are created, so reopen the page for a new one rather than reusing an old link. To hand the download to whoever is deploying the VM, click Copy download link on the page. Anyone holding that link can download the file without signing in until it expires, so send it only to the person deploying it. If nothing opens, allow pop-ups for the ARROW Platform. While a VM is still being built, the Next box says so and shows how far the build has got. If its build failed or produced no file, the box tells you that instead and offers Contact support, and we will rebuild it. On the Devices page, each VM card shows a VM Image row with Download and Copy URL buttons as soon as the image is ready.

Devices page showing a virtual machine with Download and Copy URL options Devices page showing a virtual machine with Download and Copy URL options

A virtual machine device card with the Download and Copy URL actions for the VM image

Devices page showing a virtual machine with Download and Copy URL options Devices page showing a virtual machine with Download and Copy URL options

A physical device only comes online if the site’s firewall lets it out, and the people who make that change are usually the client’s IT team, who have no ARROW account. Send them the setup instructions before the device arrives, so the firewall ticket is filed in time rather than after the box is sitting on a desk.

Open the request, expand Setup email under Details, and click Send setup instructions in Setup instructions for the site, or choose Send setup instructions from the row’s actions menu on the Device requests page. The option is there for physical requests that are still open; a virtual machine has no box to receive, and a canceled, denied, or complete request has no device on its way. Sending works once the request is approved and a device has been assigned to it, because the link in the email is made for that device. Until then, or once the device is on its way back, the card tells you why it cannot be sent. Before a device is assigned, the card offers Share setup video instead, whose link works without one (see Sharing the setup video). You can send for a request you raised yourself, or for any request if you manage your organization’s device requests.

In the dialog:

  1. Add the recipients in To. The client’s primary point of contact is filled in for you, and the client’s other contacts are offered as buttons underneath. Type any other address and press Enter or a comma to add it. You can send to up to 10 people at once.
  2. Leave Send me a copy ticked if you want the message in your own inbox too.
  3. Add a Personal note (optional) if the site needs to know something specific, such as which switch port to use or when to expect the delivery. It is plain text, up to 1000 characters.
  4. Check The email includes and click Send.

The email carries the one firewall rule the device needs, with your VPN address filled in, the carrier and tracking number once a shipping label exists, and a link to your organization’s setup guide, the same page the QR code on the card in the box opens. The emailed link carries the device’s serial number, so it opens the guide straight away, while anyone who scans the QR code is asked for the device’s serial number first, and can pick which device they have to see where to find it. See Receiving an ARROW Device for what the site sees there. It arrives from your organization via ARROW, everyone you listed receives the same message, and replies come to you.

Once it has gone, the card shows when it was last sent, by whom, and to how many recipients at which domains, and the button becomes Send again. If the device has shipped and nothing has been sent yet, the card says so, because that is the last moment to get the firewall change in place. Each request can be sent a limited number of times a day; if you reach the limit, the dialog tells you and you can try again tomorrow. If the card tells you your organization’s setup page is switched off, contact VTEM Labs support.

The setup instructions have to wait for a device, but the site can see what is coming well before that. The setup video shows how to unpack the device, connect it, and check that it is online, in about four minutes. Its link plays without a device serial, so you can send it while you are still arranging the engagement, before you have even raised the request.

On a request, Share setup video sits on the Setup email card, beside Send setup instructions or on its own while no device is assigned, and in the row’s actions menu on the Device requests page for physical requests that are still open. With no request yet, use Share setup video at the top of the Device requests page. Sharing from a request takes the same permission as sending its setup instructions, and the button at the top of the page is there if you can create device requests.

In Share the setup video, pick the Device and how long the Link works for: 7, 30, or 90 days. If the request already has a device assigned, it is picked for you. Leave Device on Not sure yet and the page offers all three devices, so the site picks the one that arrives. Where your organization has no video of its own for a device, the link plays the ARROW video for it.

Then choose how it goes out:

  • Copy a link is for your own email, so the message goes from your mailbox with your signature and branding. Click Create and copy link and paste it in. Create another link makes a new link each time.
  • Email from ARROW sends it for you. Fill in To, Send me a copy, and Personal note (optional) as you would for the setup instructions, and click Send. The sender shows as your organization’s name followed by “via ARROW”, the email uses ARROW’s layout, and replies come to you. Sent from a request, it also names the client and the start date. These emails share one daily limit with the setup instructions you send; once you reach it, the dialog says so, and you can still copy a link.

Links still working, at the bottom of the dialog, lists each live link with its device, the date it stops working, how many times it has been viewed, and who sent it. You see the links you made, or every link in your organization if you manage its device requests. Copy copies a link again. Withdraw stops it playing at once for everyone who has it; an email already sent still carries the link, but it opens on a page saying the link no longer works.

The site needs no ARROW account. The link opens a page in your organization’s branding with the video, a choice of device, the date the link stops working, and a note that the QR code on the card in the box opens the full setup page once the device arrives. Nothing else from the setup page is on it, so the firewall rule still reaches the site through the setup instructions; send those as well once a device is assigned. A link that has expired or been withdrawn tells the site to ask you for a new one. If the dialog tells you your organization’s setup page is switched off, contact VTEM Labs support.

To change dates, go to the Devices page, open the […] menu on your device, and choose Edit request details. From there you can adjust the start or end dates and save. The same dialog lets you update the assigned consultants, opportunity number, and notes. Changing the assigned consultants takes permission to manage devices or device requests; without it you can still save the dates, opportunity number, and notes.

The Edit Device Request Details dialog The Edit Device Request Details dialog

The Edit Device Request Details dialog, where you adjust the engagement dates, consultants, opportunity number, and notes

The Edit Device Request Details dialog The Edit Device Request Details dialog

The Long-term deployment toggle in this dialog works the same way. Turn it on when a device stays on site indefinitely, such as for recurring quarterly testing. The end date becomes optional, the device drops out of return reminders, and standard billing still applies.

You can also edit from the Device requests page itself. Open the request and choose Edit request from the drawer’s […] menu, or expand Engagement under Details and click Edit dates when the dates are all you need to change. While a request is still pending you can change its dates, opportunity number, and notes. Once it is approved, only the testing dates are editable.

Notes are the one field you cannot empty. You can replace them with different text, but saving with the Notes box cleared leaves the existing notes in place, so the context you wrote when you raised the request is not lost to a later edit.

You can change the delivery address on the request itself. Open the request, expand Ships to under Details, and click Update address. Update delivery address opens with the street address, city, state or province, postal code, and country the label will carry, plus the Delivery contact the carrier calls when a delivery needs a signature. Correct what is wrong and click Save address. Country is picked from a list you can search by name or code; if the address holds a country the list does not recognize, it shows in red with a note under it, and Save address waits until you pick the right one. When the address matches one of the client’s saved locations, a tickbox at the bottom offers to correct that location on the client record as well, so the next request starts from the right address; it is on by default, and you clear it for a one-time delivery somewhere else. Correcting a location under Clients works the other way too: requests that ship to it and have no shipping label yet pick up the parts of the address and the delivery contact you changed, unless you had already set something different for them on that request. Update address is only offered while the destination can still change. Once a shipping label has been purchased the address is fixed: the button stops appearing, or the dialog tells you the label already exists instead of showing the form. Contact VTEM Labs support at that point if the device has to go somewhere else.

To cancel a request while it is still pending, open it and choose Cancel request from the drawer’s […] menu, or choose Cancel request from the row’s actions menu. Nothing has been reserved or built yet at that stage, so it cancels on the click with no confirmation step. You can always cancel a request you raised yourself; cancelling someone else’s request takes permission to manage device requests. After a request has been approved, cancelling takes permission to manage device requests, even on a request you raised yourself, and asks you to confirm first; without that permission the cancel is refused and tells you so. Once a shipping label has been bought for a physical device, the request can no longer be cancelled here, and the option disappears once cancelling is no longer possible, which for a physical device means as soon as it ships. At that point, contact VTEM Labs support.

When a VM engagement is finished, open the request and click Mark complete on the Complete step of its Timeline. The button appears once the request is fulfilled. Once the end date has passed, it moves up into the Next box, and the row itself reads Past end date and offers Mark complete under Next step, which opens the same confirmation. You can complete a request you raised yourself; completing someone else’s takes permission to manage device requests. You have to confirm that the work is genuinely done, because completing closes the engagement and the request cannot be reopened. It does not delete the VMs from your client’s hypervisor, but it removes them from the ARROW VPN straight away, so they can no longer reach, or be reached through, ARROW. If a VM is still online when you complete it, ARROW tells you so. Do not use it just to tidy up the list. Mark it complete when the project ends, not when you download the VM.

Several devices for one engagement. Physical devices are one per request, so submit a separate request for each. Virtual appliances are different, and you can request up to 10 VMs in one submission.

The delivery location changes. Open the request, expand Ships to, and use Update address. That works until a shipping label has been purchased; after that, contact VTEM Labs support to redirect it.

Your dates move. Edit the request. Moving the start date moves the day we ship, so change it as soon as you know rather than the week of. Bringing a start date forward can push the request into the rush window; the edit dialog tells you when it has.

You need it fast. Put the date you actually need the device in and let the form work it out. If the date is only reachable by overnight, it offers you rush shipping and asks for a reason. If the date is not reachable at all, it tells you the earliest date that is, and you should contact VTEM Labs support if that does not work for you. Either way, turnaround still depends on current device inventory.

Hardware specifications:

  • ARROW Device - Full specifications, setup, and connectivity guide
  • OBSIDIAN Device - Full specifications, setup, and connectivity guide

Portal and management: