ARIA and Eclipse V18

Technical Specifications Guide

Varian Application Support Infrastructure

P1060883-002-B
Technical Specifications Guide / ARIA and Eclipse AUGUST 2023
Legal Information
Publication ID
P1060883-002-B

Publication Title
Technical Specifications Guide / ARIA and Eclipse

Abstract
The following specifications cover Varian application support infrastructure for ARIA, Eclipse, and
related products for release v18 inclusive:
• ARIA Oncology Information System (OIS) for Radiation Oncology (RO)
• ARIA Radiation Therapy Management (RTM)
• ARIA Unified Reporting Application (AURA)
• Eclipse Treatment Planning System (TPS)
Including ARIA Connect 5.0 and later, plus Varian Mobile 2.0 and later.

This publication is the English-language original.

Notice
Information in this publication is subject to change without notice and does not represent a
commitment on the part of Varian.

Copyright
© 2023 Varian Medical Systems, Inc. All rights reserved. Published in the United States of America.

No part of this publication may be reproduced, translated, or transmitted without the express written
permission of Varian Medical Systems, Inc.

Trademarks
Varian Medical Systems, Inc. or its affiliates own the names of our products and services
referenced herein. These names are either registered trademarks (®) or trademarks (™) in the
United States and/or other countries. All other trademarks are the property of their respective
owners. Any rights not expressly granted herein are reserved.

Contact Varian Customer Support / Report Incidents

For customer support, go to www.MyVarian.com and select Contact Us. Use MyVarian to report
incidents. If you do not have access to MyVarian, contact your local representative or call +41-41-
749-8844.

Any serious incident that has occurred while using the device should be reported to the
manufacturer and the competent authority of the Member State in which the user or patient is
established.

Electronic labeling
This symbol on the label indicates that the Instructions for Use for the corresponding product are
available at www.MyVarian.com. Access the Instructions for Use in electronic form by logging in
with your assigned MyVarian user credentials.

2 Technical Specifications Guide / ARIA and Eclipse

 In compliance with Anvisa and EU regulations, Varian will send Brazil
and EU customers a free printed copy of the Instructions for Use
within 7 days. Use the “Paper Publication Request” form provided on
the Varian webpage to order your copy.

WHO
ICD-O codes and terms used by permission of WHO, from:
• International Classification of Diseases for Oncology, Third Edition.
ICD-10 codes and terms used by permission of WHO, from:
• International Statistical Classification of Diseases and Related Health Problems, Tenth
Revision (ICD-10).

Medical Device

CAUTION: US Federal law restricts this device to sale by or on the order of a

physician.

FDA 21 CFR 820 Quality System Regulations (cGMPs)

Varian Medical Systems, Oncology Systems products are designed and manufactured in
accordance with the requirements specified within this federal regulation.

International Organization for Standardization ISO 13485

Varian Medical Systems, Oncology Systems products are designed and manufactured in
accordance with the requirements specified within the ISO 13485 quality standard.

IEC 62304
Eclipse™ Treatment Planning System is IEC 62083 compliant.

EU REACH SVHC Disclosure

The link to the current EU REACH SVHC disclosure statement can be found at
http://www.varian.com/us/corporate/legal/reach.html

Legal Information 3
 Legal Manufacturer
Varian Medical Systems, Inc.
3100 Hansen Way
Palo Alto, CA 94304
United States of America

Authorized Representative / Importer in the EU

Varian Medical Systems Nederland B.V.
Kokermolen 2
3994 DH Houten
The Netherlands

4 Technical Specifications Guide / ARIA and Eclipse

Table of Contents
Legal Information ..................................................................................... 2

Introduction .............................................................................................. 7
Introduction .................................................................................................................. 7

Common Hardware Specifications ......................................................... 8

Citrix Thin-client Workstations ..................................................................................... 8
ARIA Thick-client Workstations ................................................................................... 9
Virtual Desktop Infrastructure (VDI) .......................................................................... 10
Tablet, Slate, and Convertible Laptops ..................................................................... 10
Eclipse Treatment Planning Workstations ................................................................ 10
Velocity Workstations and Citrix Virtual Apps Server ............................................... 10
OIS Core Servers - General Requirements .............................................................. 11

OIS Deployment Models ........................................................................ 16

Cloud Hosted Solutions ............................................................................................. 16

Server Sizing Guidelines ....................................................................... 17

Option 1 - Virtual Server Deployments...................................................................... 17
ARIA OIS for Radiation Oncology and Eclipse ............................................... 18
Platform Server for Varian Treatment Delivery with 3rd party information
system............................................................................................................. 19
Option 2 - Physical Server Deployments .................................................................. 19
ARIA OIS for Radiation Oncology and Eclipse ............................................... 19

Physical Server Profiles ........................................................................ 21

Server Models ........................................................................................................... 21

Additional Server Requirements .......................................................... 22

Varian T-Box Server .................................................................................................. 22
Interface Server – ARIA Connect .............................................................................. 23
Citrix Virtual Apps Server Specifications for Radiation Oncology Client Application
Virtualization .............................................................................................................. 24
Varian Mobile Server v2.0 ......................................................................................... 24
Velocity Server .......................................................................................................... 25

Appendix A – Recommended Deployment Models............................. 26

Virtual Server Recommended Deployment Model .................................................... 27
Physical Server Deployment Model (Secondary) with Citrix Thin-clients ................. 27

Appendix B – Services Descriptions.................................................... 29

Legal Information 5
 Acronyms and Abbreviations ............................................................... 35

6 Technical Specifications Guide / ARIA and Eclipse

Introduction

Introduction
This document details the server and workstation specifications in support of the Varian
Medical Systems software products listed below. Carefully review Appendix A for
recommended deployment models.
• ARIA® oncology information system for Radiation Oncology (ARIA OIS for RO)
version v18.
• ARIA® Radiation Therapy Management (ARIA RTM) version v18.
• ARIA® Unified Reporting Application (AURA) version v18.
• Eclipse® Treatment Planning System (TPS) version v18.
• ARIA Connect™ v5.0 and later.
• Varian Mobile v2.0 and later.
Infrastructure requirements for the deployment of software products not listed above are
described in separate documents published on either Varian.com or MyVarian.com.
Contact a Varian representative for more information.

Other than English, statements regarding supported languages refer only to the NLS
(“Native Language Support”) release of the above products when available unless
otherwise explicitly noted.

Note: 1) Ensure that the Microsoft Office versions are compatible with the respective
installed OS version.

Introduction 7
Common Hardware Specifications

Citrix Thin-client Workstations

The following are the specifications for a thin-client workstation for use with ARIA OIS for
RO, Eclipse, Velocity® intended for application virtualization using Citrix®.

Table 1: General Requirements

Description Specification

Citrix Software Citrix Workspace App 1912 LTSR or later

• Consult Citrix Systems, Inc.
Operating System • Varian has validated its software with the supported Citrix
Workspace App on Windows 10.

Processor Consult Citrix Systems, Inc.

Memory Consult Citrix Systems, Inc.

Disk Space Consult Citrix Systems, Inc.

Video Adapter Consult Citrix Systems, Inc.

• 17" monitor capable of 1280x1024 resolution for ARIA OIS
for RO, ARIA RTM, and ARIA OIS for MO, minimum.
• 23" monitor capable of 1600x1200 for ARIA RTM,
Monitor recommended.
• 23" monitor capable of 1920x1080 for Eclipse, minimum.
• 27" monitor capable of 2560x1440 for Eclipse,
recommended.

Network Interface 1 Gbps recommended (100 Mbps minimum)

• Microsoft® Windows compatible 101-key keyboard and 2-
button mouse.
User Interface
• Unless explicitly noted otherwise, Varian software
applications are not optimized for use with Touch Screens.
• Optical drive (CD/DVD) for importing documents or images.
Peripherals • Topaz Signature Pad (T-LBK462-HSB-R – USB connection
only).
• 1 parallel, 1 serial, and 2 USB ports for connecting optional
peripherals.
Ports/adapters • Serial-to-USB and parallel-to-USB adapters may be
available to support legacy third-party peripherals at the
customer’s discretion.

8 Technical Specifications Guide / ARIA and Eclipse

 ARIA Thick-client Workstations
The following specifications are common to all Varian client/desktop applications where
the Varian application software is to be installed natively. The Eclipse Calculation
Workstations, Non-Calculation Workstations and Framework Agent Servers (FAS) are
sold as integrated products along with the Eclipse and/or BrachyVision Treatment
Planning System (TPS) software and must be purchased from Varian as an integrated
product.

Table 2: General Requirements

Description Specification
• Microsoft Windows 10 latest supported versions
Operating system
• 64-bit only.

Browser Chrome, Microsoft Edge

Managed execution
.NET 4.8
environment

Windows Installer Windows Installer 5.0 or greater

Processor • Dual core 64-bit CPU at 1GHz or higher

• 8 GB RAM minimum for textual users.

• 16 GB RAM recommended when running multiple
Memory
application (UserHome) sessions or imaging applications
(OLR).

Disk space 20 GB available free disk space, minimum.

• Video adapter with 512 MB of video memory recommended.
• DirectX® 9 hardware accelerated and Shader Model 3
Video adapter
minimum.
• Minimum of OpenGL 2.1 for imaging applications.

Monitor 17" monitor capable of 1280x1024 resolution, minimum.

Network interface 1 Gbps recommended (100 Mbps minimum)

• Microsoft Windows compatible 101-key keyboard and 2-
button mouse.
User Interface
• Unless explicitly noted otherwise, Varian software
applications are not optimized for use with touch screens.
• Optical drive (CD/DVD) for importing documents or images
Peripherals • Topaz Signature Pad (T-LBK462-HSB-R – USB connection
only)
• 1 parallel, 1 serial, and 2 USB ports for connecting optional
peripherals.
Ports/adapters • Serial-to-USB and parallel-to-USB adapters may be
available to support legacy third-party peripherals at the
customer’s discretion.

Common Hardware Specifications 9

 Description Specification
• Microsoft Word 2016, Word 2019 or Office 365.
• Adobe Reader 11.0 and later.
Productivity Software
• PDF printer
• Office365 support

Virtual Desktop Infrastructure (VDI)

VDI is not supported.

Tablet, Slate, and Convertible Laptops

Provided a tablet, slate, or convertible laptop computer meets or exceeds the
specifications listed previously, these devices are supported.

Note: Varian applications are not designed for use with touch interfaces. These devices
must be supplied with a standard keyboard and mouse.

Eclipse Treatment Planning Workstations

The Eclipse client software is required to run on workstation hardware supplied
exclusively by Varian Medical Systems, except when the Eclipse client application is
deployed via Citrix. Consult the TPS Supported Hardware Reference Guide 1 for current
supported hardware.

Velocity Workstations and Citrix Virtual Apps Server

Consult the Velocity oncology imaging informatics system specifications document:

Velocity 4.1 use document ”Velocity 4.1 Technical Specifications and Sizing.pdf."

Velocity 4.0 use document ”Velocity 4.0 Technical Specifications and Sizing.pdf”

Velocity 3.2 use document ”Velocity 3.2 Technical Specifications and Sizing.pdf”

for further information at MyVarian.com.

1The document will be available on Varian.com after the release of Eclipse TPS, version 18.0.

10 Technical Specifications Guide / ARIA and Eclipse

 OIS Core Servers - General Requirements
The following are the general server specifications for the deployment of Varian OIS
software. Application specific parameters are related to the specific deployment model in
subsequent sections.

Table 3: Common Server Requirements

Description Specification

Operating • Microsoft Windows Server 2019, 64-bit, (Standard or Datacenter).

System • Microsoft Windows Server 2016, 64-bit, (Standard or Datacenter).

SQL Database • Microsoft SQL Server 2019(Latest CU) (SQL is supplied and installed by
Varian Medical Systems under Microsoft’s Independent Software Vendor
(“ISV”) Royalty Licensing agreement, see CTB-SS-966 on
MyVarian.com.)
• Microsoft SQL Server 2019(Latest CU) is limited to the lesser of 4
Sockets or 16 cores. Customer configurations requiring greater than 16
cores require the customer to supply MS SQL Enterprise Edition licensing
to Varian at the time of installation.
• Microsoft SQL clustering is not compatible with Varian OIS v18 software.

Note: Customers are strongly advised to consult the Varian

Medical Systems’ Help Desk, or other authorized technical
representatives, prior to applying service pack updates to
Microsoft SQL.

Browser Microsoft Edge, Chrome

.NET .NET 4.8

Framework

NetBIOS Computer NetBIOS name not to exceed 15 characters

Windows Windows Installer 5.0 or greater

Installer

Processors • The CPU core counts provided in this document are stated with reference
(CPU) to Intel Xeon V2 processors running at 2.1 GHz or higher. Varian qualifies
and supports its software with Intel processors only.

Storage • Direct Attached Storage with SAS drives having 6ms access time, or less,
and interfaces capable of 3 Gbps or more.
• While Varian permits deployments on SAN, or other network storage
technologies, performance may be impacted. The proper configuration of
storage devices is a customer responsibility.
• Varian recommends the use of hardware RAID (RAID1 for system and
application files, RAID 5 or 6 for data storage).
• The use of software RAID is not supported.

Common Hardware Specifications 11

 Description Specification

Storage • C:/ system partition; 200-300 GB nominal (30 GB minimum free space for
Partition upgrades).
Sizing • D:/ storage partition; sizing is profile dependent and includes data growth
(see subsequent detail).
• E:/ dump partition; 75 GB nominal for the Database server and 150 GB
nominal for the Data Warehouse server.
• F:/ applicable to certain combo servers for image storage; partition sizing
is profile dependent (see subsequent detail)
• Server partition sizes are estimates for new system deployments only.
When upgrading from a prior version, add the used drive space to the
new system estimate stated herein. Always consider the data growth rate
in any calculation.
• Adjust partition sizes as necessary to reflect your specific needs.

Data Growth - • Monitor data growth and adjust storage as needed.

Database • Approximately 15 GB, per year, per linac.
Server
Partition (D:/)

Data Growth – • Monitor data growth and adjust storage as needed.

Data • Approximately 22 GB, per year, per linac.
Warehouse • Growth rate is approximately 1-1/2 times the growth rate of the Database
Server server’s D:/ drive.
Partition (D:/)

File Storage • Monitor data growth and adjust storage as needed.

Growth (File • Approximately 50 GB, per year, per linac with imaging (excluding Halcyon
Server or or utilizing daily CBCT imaging)
image • Approximately 15 GB, per year, per linac without imaging.
directory) • Approximately 600 GB, per year linac, for Halcyon or other daily CBCT
imaging protocols.
• Image file size is variable depending upon the type of image (I.e., kV, MV,
CBCT, etc.) and the customer’s chosen image parameters.

User • User authentication via Windows Active Directory. Please see the
Authentication Security Implementation Guide on MyVarian.com for further details.
• The use of spaces or apostrophes within the AD User ID is not permitted.

Network • 1 Gbps or faster recommended (100 Mbps minimum)

Interface and • Maximum of 20 ms latency for Eclipse and image management users for
Latency Citrix server connections
• Maximum of 50 ms latency for ARIA OIS users for Citrix server
connections

12 Technical Specifications Guide / ARIA and Eclipse

 Description Specification

System Setup • Includes Network Firewall and Communication utilizations for environment
setup.
• Please see the ARIA v18.x System Preparation Manual (SPM-SS-18x) on
MyVarian.com for further details.

Network • Varian OIS software supports only TCP/IP network environments with
Integration IPv4. Varian OIS software can exchange data with many different
third-party systems including Hospital Information Systems, PACS,
CT and other medical imaging devices, as well as Varian and third-
party Linear accelerators. As such, network bandwidth requirements
can vary greatly depending upon many factors (including the type
and number of products deployed, number of users, and specific
treatment and/or imaging techniques). Please see the Varian’s
CyberSecurity Administration Reference Guide on MyVarian.com for
further details.

Power Disable Power Management (“PM”).

Management

Note: The appropriate PM setting may not be labeled “disabled” but

rather some combination of “Performance,” “Maximum Performance,”
“High Performance,” or similar verbiage. Customers should consult
their vendor documentation to confirm the proper setup. Setting this
feature appropriately at the BIOS level is generally considered the
most reliable means as BIOS settings should override any hypervisor
or OS settings.

Anti-virus • Varian recommends deploying anti-virus software on the servers

supporting Varian software with virus definitions updated frequently.
• See Varian’s CyberSecurity Administration Reference Guide on
MyVarian.com for further details.

Additional • 15" monitor @ 1024 x 768 resolution

Hardware • Optical Drive (CD/DVD) 8x or higher
Components • 2 USB ports
• Microsoft Windows Compatible 101 Key Keyboard & 2 button mouse

Common Hardware Specifications 13

 Description Specification

Hardware Varian supports its software on systems using hardware virtualization provided
Virtualization the guest virtual machines are configured with sufficient resources as
identified in this document.

Note: Customers are advised that it is incumbent upon them to ensure

proper performance of the system following best practices for their
chosen hypervisor with respect to the entire Varian oncology system
and for third-party software such as MS SQL & Citrix Virtual Apps;
such as, VMWare using VMXNET3 & PVSCSI drivers and ensuring up
to date “guest VM” tools. A complete discussion of all best practices
for all hypervisor vendor software is outside the scope of this
document.

Backup Varian Oncology Information System (“OIS”) software is the repository of

extremely important oncology workflow data, as such a proper enterprise
backup solution is highly recommended.

Note: See the Varian’s CyberSecurity Administration Reference Guide

on MyVarian.com for further details.

Redundancy Varian OIS for Radiation Oncology software provides direct support for the
delivery, planning, and control of therapeutic radiation treatments performed
on medical linear accelerators or other delivery modalities. Therefore, the
availability of the Varian Software is extremely important. As such, Varian
recommends customers supply servers with hardware redundancy in power
supplies, fans and other hardware components that may be subject to regular
failure.

Disaster Varian makes no specific recommendations on DR solutions. Customers

Recovery (DR) should follow industry best practices in consultation with Varian Medical
Systems technical experts to help ensure the DR solution planned by the
customer is viable for Varian OIS Software prior to the deployment of any DR
solution.

Table 4: Server Descriptions

Installed software and services installed by Varian

Server Name or Function
(partial list)

Database Server Microsoft SQL Server 2019(Latest CU)

Data Warehouse (“DW”) Server Microsoft SQL Server 2019(Latest CU)

Varian application S/w, MS IIS, Web Services, Shared

Platform Server
Framework Services, VAIS

File Server CIFS file storage (images & documents)

14 Technical Specifications Guide / ARIA and Eclipse

 Aria Connect Server HL7 interface engine and Aria Connect services.

DICOM Server DICOM Daemon Services (one per Linac)

DCF Server Calculation Distributor (Varian S/w)

T-Box Server (test) Microsoft SQL Server 2019 (Latest CU), Varian application
S/w, MS IIS, Web Services, Share Framework Services,
CIFS file storage (images & documents), DICOM Daemon
Services

Common Hardware Specifications 15

OIS Deployment Models
This document assumes a “relative equivalency” between a virtualized hardware
deployment and a physical one. In the virtualized hardware deployment model, we have
separated the backend services based on “best practices” considering cost effectiveness,
management efficiency, overall serviceability, and so on.

Review Appendix A for more information on recommended deployment models.

Review Appendix B for descriptions of the various system services.

Cloud Hosted Solutions

Varian offers a managed infrastructure solution with its FullScale Infinity Cloud offering.
Varian does not encourage or endorse ARIA and Eclipse on customer provided
environments hosted on public cloud infrastructure.

16 Technical Specifications Guide / ARIA and Eclipse

Server Sizing Guidelines
The following provides options and specifications needed to create a properly sized core
server environment based upon the Varian OIS products purchased, facility size
(numbers of Linacs & users), and the server deployment model desired. The OIS Core
Servers - General Requirements and the server provisioning requirements detailed in the
following sections provide a comprehensive framework for server deployment.

Server sizing presumes quantitative equivalence between customers with similar

numbers of machines, users, purchased applications, and using similar deployment
models. While it is true that some factors are not included in the following analysis (such
as, paperless deployment, patient volume, specialty practices, and others), customers
should consider these recommendations as a starting point for system deployment while
monitoring and adjusting system resources as needed to achieve the desired level of
performance.

Note: 1) The resource requirements supplied here are recommendations intended to

ensure end-users experience an acceptable level of performance for typical sizes of
deployments. Routine monitoring and adjusting of the OIS core server resources is
highly recommended. Customers should not reduce OIS core server resources below
Varian recommendations and, if done, should be prepared to add resources quickly
when it becomes necessary.
2) The minimum resource requirements are the same as depicted for ARIA version 17
in a previous version of this guide.
2) For cases where the customer does not have a separate server for Domain
Controller(DC), it is required to provision a separate DC server. This is as per guidelines
from Microsoft.
Typical recommendation for DC server to start with is as below:
vCPU Cores: 2 vCPU
RAM: 8 GB RAM
System Partition(C:\): 100 GB
Data Partition(D:\): 100 GB + Growth

Option 1 - Virtual Server Deployments

These are the unique server requirements for the deployment of Varian software based
on the Virtual Server model using the terminology and configuration as described in
Appendix A, Figure 1.

Server Sizing Guidelines 17

 ARIA OIS for Radiation Oncology and Eclipse
In addition to the OIS Core Servers - General Requirements, the following server
provisions are recommended for the deployment of ARIA OIS for Radiation Oncology
software in a purely virtual server environment. In addition to this if Citrix clients are used
the Citrix application virtualization is needed as described in section Citrix Virtual Apps
Server Specifications for Radiation Oncology Client Application Virtualization.

Table 5: Virtual Server Model Guidelines

Scenario DB AURA 2 Platfor File DICOM DCF 3 ARIA
(DW) m Connect 4

Small Sites 8 Cores 8 Cores 8 Cores 4 Cores 4 Cores 4 Cores 4 Cores

Up to 2 Linacs

30 ARIA Users, 6 24GB 24GB 24GB 16GB 16GB 16GB 32GB

Eclipse Users

Medium Sites 12 12 12 8 8 8 4
Cores Cores Cores Cores Cores Cores Cores
Up to 4 Linacs

60 ARIA Users, 32GB 32GB 32GB 24GB 24GB 24GB 32GB

12 Eclipse Users

Large Sites 12 12 12 8 8 8 4
Cores Cores Cores Cores Cores Cores Cores
Up to 6 Linacs
32GB 32GB 32GB 32GB 32GB 32GB 32GB
90 ARIA Users,
18 Eclipse Users

Extra-large 16 16 16 12 12 12 4
Sites Cores Cores Cores Cores Cores Cores Cores

Up to 8 Linacs 64GB 64GB 64GB 32GB 32GB 32GB 32GB

120 ARIA Users,
24 Eclipse Users

C:\ Drive 200- 200- 200- 200- 200- 200- 200-

300GB 300GB 300GB 300GB 300GB 300GB 300GB

D:\ Drive 600GB 600GB 300GB 2160GB 300GB 300GB 300GB

5

E:\ Drive 900GB 900GB N/A N/A N/A N/A N/A

2 Optional for Eclpse TPS

3
Needed only if Eclipse TPS is included.
4 Optional for HL7 and FHIR connectivity
5 Expandable

18 Technical Specifications Guide / ARIA and Eclipse

 Platform Server for Varian Treatment Delivery with 3 rd party
information system
The following server provisions are recommended for the deployment of the required
platfrom server and file storage needs for Varian Treatment Delivery systems (e.g.
TrueBeam and Halycyon) when deployed without ARIA OIS.
Table 6: Virtual Server Model Guidelines
Scenario Platform & File Server

Up to 4 Linacs 4 Cores / 12 GB

Up to 8 Linacs 6 Cores / 14 GB

Up to 12 Linacs 8 Cores / 16 GB

Over 12 Linacs 12 Cores / 18 GB

C:\ Drive 200-300GB

D:\ Drive 200 GB

E:\ Drive Expandable 300 GB/Linac

Option 2 - Physical Server Deployments

The physical server deployment models to follow are based on the servers available from
Varian Medical Systems. The server profiles are found in the next section of this
document.

ARIA OIS for Radiation Oncology and Eclipse

In addition to the OIS Core Servers - General Requirements, the following server
provisions are recommended for the deployment of ARIA OIS for Radiation Oncology and
Eclipse TPS software in a purely physical server environment.

Table 7: Secondary Server Model Guidelines

Server Sizing Guidelines 19

 Database Platform & File Server
Description DW Server 6
Server DICOM, DCF 7

Up to 2 Linacs, 30
ARIA users, 6 Data Server Data Server
File Server
Eclipse Users

Up to 4 Linacs, 60
Application
ARIA users, 12 Data Server Data Server File Server
Server
Eclipse users

Up to 6 Linacs, 90
Application
ARIA users, 18 Data Server Data Server File Server
Server
Eclipse users

Up to 8 Linacs, 2x
2x File
120 ARIA users, Data Server Data Server Application
Server
24 Eclipse Users Server
Consult Varian for sizing recommendations when the number of users exceed the
parameters stated in this table.

Storage Partitioning 8

System (C:/) 300 GB 300 GB 300 GB 300 GB

Data (D:/) 600 GB 600 GB 600 GB

900 GB

900GB - 900GB - 2160GB

Data (E:/) 2160GB 2160GB N/A expandable
expandable expandable

6 Not needed for Eclipse TPS

7
For Eclipse TPS additional FAS servers are needed depending on configuration
8 Server partition sizes are estimates for new system deployments only. When upgrading from a

prior version, add your existing used drive space to the estimate stated above. Always consider
the data growth rate in any calculation. Adjust partition sizes as necessary to reflect your specific
needs.

20 Technical Specifications Guide / ARIA and Eclipse

Physical Server Profiles
The following is a list of physical servers available for purchase from Varian Medical
Systems. Varian customers may elect to deploy physical servers acquired from other
vendors; however, it is the customer’s responsibility to ensure functional equivalency
between the servers listed below and the alternative vendor’s device deployed in support
of the Varian OIS software.

In addition to the OIS Core Servers - General Requirements, the following reflects the
requirements for the specified physical servers. These specifications are subject to
change without notice and reflect the current configuration of Varian supplied devices as
of the date of this publication.

Server Models
These are four different rack-mounted servers offering an economical and versatile
solution to Varian software deployment.

Table 8: Server Options

Utility Server Data Server File Server Application

Description
Server

2 x 10- 2x14 2 x 10 – 2x 14 2 x 14 cores

CPU 1x 12 cores
cores cores
Memory 32 GB 32-64 GB 64-96 GB 64 GB

1920-3360 GB 2880- 960 GB

Total Usable
960 GB (expandable) 3360GB
Disk Space
(expandable)

Options:
GPU NA NA NA a) none
b) Citrix: GPU

Domain DB, DW File Server Platform, DICOM,

Suitable for controller, DCF
Server Roles Varian Mobile,
Aria Connect

Physical Server Profiles 21

Additional Server Requirements
Clinical system configurations often require additional servers not included in the
previously described core architecture. System designers should obtain a complete list
of purchased applications before finalizing the design of any Varian OIS server
environment.

The following describes certain additional server requirements. For all purposes the
requirements stated below apply equally to all server models and assume a functional
equivalency between physical and virtual deployment.

Varian T-Box Server

A dedicated T-Box (test) server is required for ARIA OIS deployments. Customers who
desire to virtualize the ARIA T-Box are strongly encouraged to create a T-Box VM with
the following provisions.
Note: ARIA T-Box servers are “all-in-one” deployments where MS SQL and other OIS
core applications are deployed on a single server. Performance is not the key
objective. The domain controller (AD) functionality cannot be included in the same
server.

In addition to the OIS Core Servers - General Requirements, the following server
provisions are recommended for the deployment of the ARIA OIS software in a purely
virtual server environment.
Table 9: Virtual T-Box Server Model Resource Guidelines

Description Specification
• Windows Server 2019 (Standard or Datacenter), 64-bit
Operating System
• Windows Server 2016 (Standard or Datacenter), 64-bit
• Intel Xeon Silver 4114 @ 2.1 GHz, or equivalent
• 20 vCPU cores, minimum
Hardware Guidelines
• 48 GB RAM, minimum
Note: CPU must support AVX instructions
• C:/ ~200-300 GB (30 GB free)
Storage • D:/ ~1000 GB
• E:/ ~100 GB

Recommended HW Server
Application Server
Model

22 Technical Specifications Guide / ARIA and Eclipse

 Interface Server – ARIA Connect
ARIA Connect is installed on an Interface Server platform and manages the exchange of
data between ARIA OIS software and third-party systems using the HL7 (Health Level 7)
protocol.

Varian is in the process of replacing IEM with ARIA Connect for most customers with
ARIA OIS for Radiation Oncology. Customers upgrading from a previous version of ARIA
need to transition to ARIA Connect.

In addition to the OIS Core Servers - General Requirements, the following are the
technical specifications for supporting ARIA Connect v5.0

Table 10: Virtual Interface Server Model Resource Guidelines

Description Specification

Software ARIA Connect v5.0 9

• Windows Server 2019 (Standard or Datacenter), 64-bit.
Operating System • Windows Server 2016 (Standard or Datacenter), 64-bit.
• Windows 10
• 4 CPU cores @ 3.0 GHz
Hardware Guidelines 10
• 32GB GB RAM, minimum

• C:/ = 200-300 GB (30 GB free)

Storage
• D:/ = ~300 GB

Recommended HW
Utility Server
Server Model

9
ARIA Connect v5.0 is compatible with ARIA for Radiation Oncology v15.5 and later.
10The amount of CPU and RAM assigned to the Interface Server can vary widely depending on the
number & type of interfaces, the amount of filtering of the HL7 data feed, and the message volume.
Customers are encouraged to perform load testing prior to putting any new interface into production
and adjust the amount of CPU and RAM as needed.

Additional Server Requirements 23

 Citrix Virtual Apps Server Specifications for
Radiation Oncology Client Application Virtualization
In addition to the OIS Core Servers - General Requirements, the following are the
recommended specifications for deployment of the ARIA OIS for RO, Eclipse TPS, and
ARIA RTM client software on Citrix application servers, excluding ARIA OIS for CCS.
Table 11: Virtual Apps Server System Guidelines
Description Specification
• RECOMMENDED - Citrix Virtual Apps 1912 LTSR or later
Citrix Software • MINIMUM COMPATIBLE - Citrix XenApp 7.15 LTSR CU2
• Citrix licenses are not supplied by Varian Medical Systems
• Windows Server 2019(Standard or Datacenter) with Citrix Virtual
Apps 1912(LTSR)
Operating Systems • Windows Server 2016 (Standard or Datacenter) with Citrix
XenApp 7.15 LTSR20

The following may vary depending upon user load and the Varian
applications deployed.
• ARIA OIS for RO: 4 Cores/16 GB RAM supports approximately
10 users.
• Eclipse TPS: 6 Cores/24 GB RAM supports up to 3 users.
These user counts are for the identified applications when published to
CPU and RAM
run on separate Citrix Virtual Apps servers. The applications can be
published to run on the same Citrix Virtual Apps server provided the
resources assigned are adjusted proportionally.
Customers should regularly monitor resource utilization of Citrix Virtual
Apps servers and adjust available resources or number of servers in a
farm to meet their actual workload.
• System Partition (C:/) ~100 GB
Storage Partitioning
• Application Partition (D:/) ~100 GB
• Varian recommends deploying GPU on Citrix Virtual Apps
servers.
Graphics Processing • Customers using hardware virtualization are guided towards the
Units (GPU) NVIDIA Tesla M10 GPU, or equivalent.
• GPU must meet the proper OpenGL and DirectX compatibility for
the client software.
Recommended HW
Application Server
Server Model

Varian Mobile Server v2.0

A dedicated server is required for Varian Mobile.

Varian Mobile requires Microsoft Azure AD Connect to be installed. Azure AD Connect is

compatible with Windows Server 2016 and above. Microsoft recommends at least two
Azure AD Connect instances to be installed for each deployment.

In addition to the OIS Core Servers - General Requirements, the following are the
technical specifications for a dedicated server supporting Varian Mobile.

24 Technical Specifications Guide / ARIA and Eclipse

 Table 12: Varian Mobile Server System Guidelines
Description Specification
• Windows Server 2022 (Standard or Datacenter), 64-bit.
Operating System • Windows Server 2019 (Standard or Datacenter), 64-bit.
• Windows Server 2016 (Standard or Datacenter), 64-bit.
UP TO 20 USERS

• 2 CPU cores, minimum

Virtualization Guidelines
• 8 GB RAM, minimum
• C:/ ~100 GB (30 GB free)
Storage
• D:/ ~100 GB
UP TO 50 USERS
• 4 CPU cores, minimum
Virtualization Guidelines
• 12 GB RAM, minimum
• C:/ ~100 GB (30 GB free)
Storage
• D:/ ~150 GB
Recommended HW
Utility Server
Server Model

Velocity Server
Consult the Velocity oncology imaging informatics system specifications

Velocity 4.1 use document ”Velocity 4.1 Technical Specifications and Sizing.pdf."
Velocity 4.0 use document ”Velocity 4.0 Technical Specifications and Sizing.pdf”

Velocity 3.2 use document ”Velocity 3.2 Technical Specifications and Sizing.pdf””

for information on supported infrastructure at MyVarian.com.

Additional Server Requirements 25

 Appendix A – Recommended
Deployment Models
The following are provided as recommended deployment models for Varian ARIA for RO,
ARIA RTM, and Eclipse treatment planning software applications. As noted previously,
review the Varian documentation for Velocity and InSightive whenever those additional
products are purchased and deployed.

LEGEND:
o Represents a physical or virtual server. For a more detailed description
of the service names and concepts, see Appendix B.
o Varian ARIA Connect server software used to exchange HL7 data with
third-party hospital information systems.
o Represents 1 or more Citrix Virtual Apps “worker” servers (either physical
or virtual). Varian client software is deployed directly on these servers.
o Represents the Citrix Virtual Apps support services such as the Citrix
WebInterface/Storefront, Delivery Controller, Citrix License server and so
on. These are services supplied by Citrix to support any typical Citrix
Virtual Apps environment.
o Represents 1 or more physical Framework Agent Servers (FAS) used to
perform complex treatment plan calculations for Eclipse.
o Represents a collection of “servers” (physical or virtual), the primary
purpose being to help identify the collection of servers included in the
deployment models described below.
o Varian client software (UserHome, ARIA for OIS, ARIA for RTM, or
Eclipse), which can be installed directly on a PC/client device, or in a
Citrix Virtual Apps environment. The PC requirements are identified
above.
o Varian treatment console software, which is client software that manages
delivery of treatments at a linear accelerator. This software is identified
slightly differently than the standard Varian client software, as the
treatment console software cannot be deployed in Citrix Virtual Apps
environment and comes packaged only with client hardware supplied by
Varian.
o Represents the Citrix Workspace App software deployed on PC/client
devices when a customer is using Citrix Virtual Apps.
o Represents one or more third-party imaging (CT/MRI/PET/PACs) or
hospital information systems exchanging patient data with Varian
software via DICOM (for imaging systems) or HL7 for HIS.
o Represents the exchange of data between Varian server software and
Varian client software (or third-party systems).
o Represents the exchange of data (generally screen pixels) between the
Citrix Workspace App & backend Citrix Virtual Apps servers.

26 Technical Specifications Guide / ARIA and Eclipse

 Virtual Server Recommended Deployment Model

Figure 1: Virtual Server Recommended Deployment

Figure 1 represents Varian recommended deployment model for hardware virtualization.

Varian OIS applications and services are distributed onto smaller, dedicated virtual
servers. This provides for “fine-grained” computer resource allocation and management
of services and minimizes potential resource conflicts.

Separate servers are required for Data Warehouse, ARIA Connect, and the Calculation
Array (FAS Servers), which may or may not be deployed depending upon the products
purchased by the customer.

Physical Server Deployment Model (Secondary) with

Citrix Thin-clients

Figure 2: Physical Secondary Server Deployment Model

Figure 2 represents Varian recommended physical server deployment model. Varian

OIS applications and services are deployed on a Platform & File server while the Varian
System Database server is dedicated to managing SQL tasks.

Appendix A – Recommended Deployment Models 27

 Separate servers are required for Data Warehouse, ARIA Connect, and the Calculation
Array (FAS Servers), which may or may not be deployed depending upon the products
purchased by the customer. Other optional components like Varian Mobile will require
additional servers.

28 Technical Specifications Guide / ARIA and Eclipse

Appendix B – Services Descriptions
Figure 4 is a conceptual view of the deployment of Varian software. As a conceptual view
this figure is not meant to depict any particular “deployment model” of the services but
rather the exchange of information between client software (or third-party systems) and
the Varian server software and is provided to help facilitate further description of the
Varian and third-party server software below.

Figure 4: Varian Software Conceptual View

Appendix B – Services Descriptions 29

 The following is a description of the various services depicted in Figure 44.
The exact services used within any particular deployment will depend upon the
purchased Varian software applications and support modules.
Table 13: Varian software applications and support modules
Product/Feature
Name Function Services
Purchased

Production Database MS SQL ARIA RO, ARIA RTM,

Eclipse

Considerations:
Varian
System The Varian System Database is the workhorse for daily work done by
Database clinic staff including treatment software. This type of workload is termed
a “transactional” workload as end-users are performing a specific
function or task. This database needs fast response time to requests for
information to minimize end-user wait time.

Reporting & Analytics MS SQL ARIA RO

Database

Considerations:
This database supports the workload for reporting (AURA) and,
optionally, InSightive Analytics (see the table below). In general,
Data
reporting and analytics are not considered a “real-time” activity as reports
Warehouse
can be complex and may aggregate data from multiple tables and/or
over long periods of time and, as such, the workload can be sporadic.
By offloading the reporting workload from the Varian System Database
server to this Data Warehouse database instance (synchronized
regularly) the potential impact of large reports or analyses can be
diminished significantly while still allowing “real time reports”, such as,
“daily activity for today”, to run against the Varian System Database.

Web based IIS, Varian ARIA RO, ARIA RTM,

Application Pools for WebServices and Eclipse,
application support & Shared Framework
third-party tools for (Flexnet, WinSyslog)
support functions. services

Platform Considerations:
Services
These services provide IIS application pools to act as a middle-ware
layer between Varian client software and the database and/or file server
as well as support for system functions such as license management,
logging, inventory management, and so on. The application pools are
designed to support daily transactional workload. They support caching
of data to speed up access to the data used by multiple end-users.

30 Technical Specifications Guide / ARIA and Eclipse

 Product/Feature
Name Function Services
Purchased

NTFS/CIFS File OS File Services ARIA RO, ARIA RTM,

Access Eclipse

Considerations:
Traditionally Varian has referred to this as the “Image Server” but other
unstructured file data (documents, templates, Beam Data files for
Eclipse, and so on) are stored on the file system external to the
database. The services related to this purpose is more properly simply
termed a “File Server.” As a networked application Varian software reads
and writes files using the OS provided CIFS (file sharing) functions. File
File Services access utilizes Windows security and is configured according to the
Security Implementation Guide.

Whether the files are actually stored on the same server acting as a file
server (for instance, customers using a SAN may make this storage
visible to the file server using other means) is a deployment design
decision for some customers. However, in pure physical deployments, it
is generally the case that the physical storage is directly attached to the
server acting as a “file server” and this document “assumes” this is the
case. Configuration of SAN storage and making it visible to the server
acting as a file server for Varian applications is outside the scope of this
document.

Appendix B – Services Descriptions 31

 Product/Feature
Name Function Services
Purchased

DICOM Transfers with File, DB and IT ARIA RO and Eclipse

accelerators and Daemons
third-party information
systems

Considerations:

DICOM services in version 15.x collectively replace the File, DB, and IT
Daemons which were used in previous releases. The File and DB
Services are exact equivalents to the File and DB Daemons. The IT
Service replaces the Treat Daemon and Image Daemon previously
deployed on the Treatment Console workstations. For configuring secure
DICOM, certificates from connecting DICOM nodes need to be
DICOM configured in the DICOM Services configuration.
Services The DICOM File Service requires no connection to the Varian System
Database and is used simply to receive DICOM objects and store them
to files that can be later imported to the Varian software manually.

The DICOM DB Service interfaces with the Varian System Database. It

supports bi-directional DICOM query-retrieve services and DICOM
import/export services.

The DICOM IT Service consists of a single DICOM service for each

Linear Accelerator in the customer’s environment and is designed to act
as the middle-ware layer between the Varian System Database, File
Server, and Varian treatment and imaging software. For this release it is
now mandatory that this service be placed on a backend server and not
on a workstation at the Linear Accelerator.

Client Applications ARIA RO, ARIA RTM,

UserHome
Eclipse, Velocity
(ARIA RO,
ARIA RTM, Considerations:
Eclipse),
These client applications are depicted for purposes related to
Velocity
completeness of the deployment models only.

Calculation job Distributor Eclipse

control.

Considerations:
DCF Core
This service is used as a “command & control” service for calculation
jobs submitted to the calculation system, it is similar to a “printer queue”
since jobs submitted to it are sent to one or more calculation computers
and are queued up if those computers are otherwise currently busy.

32 Technical Specifications Guide / ARIA and Eclipse

 Product/Feature
Name Function Services
Purchased

Eclipse calculation DCF Agent, Eclipse

support
DCF Core
(Optionally)

Considerations:

The deployment of Framework Agent Servers (FAS) used for calculation

Calculation support is depicted in Figures 1-3 purely for purposes related to
Array (FAS completeness of the deployment models only. Eclipse Framework Agent
Servers) Servers (FAS) are sold as integrated products along with the Eclipse
and/or BrachyVision Treatment Planning System (TPS) software and
must be purchased from Varian as an integrated product. FAS are
always deployed as “pure physical servers”. One or more FAS are
required when customers deploy Varian Eclipse client software using
Virtual Apps application virtualization and do not have Eclipse
Calculation Workstations for treatment plan calculation support.

HL7 Cloverleaf ARIA Connect

Considerations:

ARIA Connect These services are optional, purchasable interface modules used to
(AC) transfer data between the Varian System Database and third-party
systems in HL7 format. The server’s workload will vary depending upon
the number and type of interfaces deployed (ADT, Billing, Lab, and so
on).

Appendix B – Services Descriptions 33

 Product/Feature
Name Function Services
Purchased
Velocity data storage PostgreSQL, file Velocity
and analytics storage, DICOM
Services.

VelocityGRID Considerations:

The VelocityGRID server manages image data with a pseudo database

and file system. For information on VelocityGRID server requirements,
see Velocity Server.

Domain Controller Servers arer servers used for authenticating and

validating user access on the network. They responds to security
DC Server
authentication requests and verify users within a computer network
domain.

34 Technical Specifications Guide / ARIA and Eclipse

Acronyms and Abbreviations

4DITC 4-Dimension Integrated Treatment Console

AC ARIA Connect

AD Microsoft Active Directory

AURA ARIA Unified Reporting Application

CCS Comprehensive Cancer Solution

CIFS Common Internet File System

DB Database

DCF Distributed Calculation Framework

DICOM Digital Imaging and Communications in Medicine

DS Microsoft Domain Services

DW Data Warehouse

FAS Framework Agent Server

HL7 Healthcare Level 7

IEM Information Exchange Manager

IIS Microsoft Internet Information Server

Linac Linear Accelerator

MO Medical Oncology

NAS Network Attached Storage

OBI On-board Imaging

OIS Oncology Information System

RO Radiation Oncology

RTM Radiation Treatment Management

S/w Software

SAN Storage Area Network

SAS Serial Attached SCSI

SCSI Small Computer System Interface

SSRS SQL Server Reporting System

VM Virtual Machine

DC Domain Controller

Acronyms and Abbreviations 35