Technical Specifications - v15.x

Transcription

1 ARIA oncology information system (OIS) for Radiation Oncology (RO) v15.1 ARIA oncology information system (OIS) for Medical Oncology (MO) v15.1 ARIA Radiation Therapy Management (RTM) v15.1 ARIA Unified Reporting Application (AURA) v15.1 Eclipse treatment planning system (in Citrix XenApp ) v15.1 and v15.5 Information Exchange Manager (IEM) v15.1 Page 1

2 Table of Contents Introduction... 3 V15.x Release Considerations... 5 Technical Specifications... 7 Desktop/PC Technical Specifications... 7 Common... 7 ARIA OIS for RO... 8 ARIA OIS for MO... 8 Eclipse Treatment Planning System... 9 Velocity Imaging Informatics System... 9 Tablet, Slate, Convertible laptops:... 9 Citrix XenApp (thin-client) Specifications:... 9 Server Technical Considerations General Considerations Server OS and Software Requirements Deployment Considerations Deployment Models Virtual Server Recommended Deployment Model Physical Server Recommended Deployment Model Secondary Multi-Server Deployment Model (pure physical deployment) Deployment Models - Server Sizing Guidelines Virtual Server Recommended Deployment model ARIA for Radiation Oncology ARIA OIS for Medical Oncology Eclipse Only ARIA for Radiation Oncology and Eclipse ARIA Comprehensive Cancer Solution (CCS) Physical Server Recommended Deployment ARIA for Radiation Oncology Page 1

3 ARIA OIS for Medical Oncology Eclipse Only ARIA for Radiation Oncology & Eclipse ARIA Comprehensive Cancer Solution (CCS) Secondary Physical Server Recommended Deployment ARIA for Radiation Oncology ARIA OIS for Medical Oncology Eclipse Only ARIA for Radiation Oncology and Eclipse ARIA Comprehensive Cancer Solution (CCS) Additional Server Requirements IEM Interface Server Citrix XenApp Server HARRP Servers Appendix A Pure Physical Deployment For Existing Customers Eclipse Only Combo Server (without DCF Core) ARIA for Radiation Oncology & Eclipse Combo Server (without DCF Core) ARIA Comprehensive Cancer Solution (CCS) Combo Server (without DCF Core) Appendix B: Service Application Page 2

4 INTRODUCTION This document describes deployment model guidelines and technical specifications with respect to the following Varian software products: ARIA oncology information system for Radiation Oncology (ARIA OIS for RO) v15.1 ARIA oncology information system for Medical Oncology (ARIA OIS for MO) v15.1, ARIA Radiation Therapy Management (ARIA RTM) v15.1, ARIA Unified Reporting Application (AURA) v15.1, Eclipse (in Citrix XenApp) v15.x (Currently v15.1 & v15.5) Since Eclipse thick client and FAS servers must be purchased directly from Varian the currently supported platform specs are published separately in the TPS Supported Hardware Reference Guide available on Varian.com IEM v15.1 Note specifications for Velocity, InSightive and ARIA Connect are provided separately in the following documents either published on Varian.com or at MyVarian Velocity See "Velocity 3.2 Technical Specification.pdf" (RAD10408 or latest currently available) InSightive 1.5 CTB-PM-990 (latest version available) ARIA Connect v2.5 ARIAConnect_TechnicalSpecifications_v25.pdf Other than English, statements regarding supported languages refer only to the NLS release of the above products when or if they become available unless otherwise explicitly noted. Page 3

5 Document ID Document Title Abstract Manufacturers European Authorized Representative Notice FDA 21 CFR 820 Quality System Regulation (cgmps) ISO CE EU REACH SVHC Disclosure HIPAA P Reference Guide This document provides reference information for the software and computer hardware requirements for using Varian's software products. This document is the English-language original. Varian Medical Systems, Inc Hansen Way Palo Alto, CA United States of America Varian Medical Systems UK Ltd. Oncology House Gatwick Road, Crawley West Sussex RH10 9RG United Kingdom Information in this reference guide is subject to change without notice and does not represent a commitment on the part of Varian. Varian is not liable for errors contained in this reference guide or for incidental or consequential damages in connection with furnishing or use of this material. This document contains proprietary information protected by copyright. No part of this document may be reproduced, translated, or transmitted without the express written permission of Varian Medical Systems, Inc. Varian Medical Systems, Oncology Systems products are designed and manufactured in accordance with the requirements specified within this federal regulation. Varian Medical Systems, Oncology Systems products are designed and manufactured in accordance with the requirements specified within the ISO quality standard. Varian Medical Systems, Oncology Systems products meet the requirements of Council Directive MDD 93/42/EEC. The link to the current EU REACH SVHC disclosure statement is: Varian s products and services are specifically designed to include features that help our customers comply with the Health Insurance Portability and Accountability Act of 1996 (HIPAA). The software application uses a secure login process, requiring a user name and password that supports role-based access. Users are assigned to groups, each with certain access rights, which may include the ability to edit and add data or may limit access to data. When a user adds or modifies data within the database, a record is made that includes which data were changed, the user ID, and the date and time the changes were made. This establishes an audit trail that can be examined by authorized system administrators. Trademarks ARIA oncology information system, ARIA Radiation Therapy Management, ARIA Unified Reporting Application, InSightive,, OncQT and Eclipse are trademarks or registered trademarks of Varian Medical Systems, Inc. Microsoft, Windows, Windows Server, Internet Explorer, DirectX and SQL Server are registered trademarks of Microsoft Corporation. Citrix and Citrix XenApp are registered trademarks of Citrix. Intel, Intel Core 2 Duo and Xeon are registered trademarks or trademarks of Intel Corporation. Adobe and Reader are registered trademarks of Adobe Systems Incorporated. Apple and OS X are registered trademarks of Apple Inc. All other trademarks or registered trademarks are the property of their respective owners. Copyright 2017 Varian Medical Systems, Inc. All rights reserved. Produced in the United States of America Page 4

6 V15.X RELEASE CONSIDERATIONS The following table summarizes significant considerations for customers upgrading to v15.x of ARIA and/or Eclipse. This information is supplied to help in planning for an upgrade of these products and was considered accurate when written, however for the most up to date information please see the official documentation for the products mentioned and/or consult with the Varian service team (local service or Project Management). Table 1: v15.x Upgrade Considerations Consideration Supported Server Operating Systems Supported Client Operating Systems Windows Active Directory Comment All backend servers except those used with Citrix XenApp are supported on Windows Server 2012 R2 or Windows Server Windows Server 2008 R2 SP1 is supported only with Citrix XenApp servers running XenApp 6.5 Windows 10 Support has been added. Windows 7 is still supported. Customers are strongly advised to supply a separate server running Windows Active Directory Domain Services (AD DS). With v15.x Varian software User Authentication is now performed by Windows AD DS therefore running Varian server software on the same server as Windows AD DS is strongly discouraged. ARIA OIS for MO Customers of previous releases with Varian server software and Windows AD DS on the same server should consult with their Varian representatives to provision and deploy one (or more) servers running Windows AD DS prior to an upgrade. ARIA OIS for MO no longer supports Windows 7, Windows Server 2008 R2 SP1 and Citrix XenApp 6.5. Customers attempting to run ARIA OIS for MO with other Varian software that may otherwise support the above 3 rd party products, Page 5

7 InSightive Analytics HL7 Interface Support Velocity Treat & Image Daemon Support Varian Linear Accelerator Consoles Acuity Varian Treatment (VTx) Varian Exchange (VEx) especially in a CCS environment, will need to plan accordingly, primarily in regards to implications to XenApp farms. Customers with InSightive Analytics must upgrade to v1.5. It is highly recommended that customers with IEM transition to ARIA Connect. While IEM is still supported in this release support for it may be discontinued in a future release. Customers with Velocity must upgrade to Velocity 3.2. The DICOM Daemons (Treat & Image Daemons) used to transfer plan & image data to/from Linear Accelerator console software and the Varian server software has been replaced by a single Windows Service (IT Service) which now must be installed on backend servers. This functionality is no longer supported on workstations at the Linear Accelerator. This modification enhances both security and performance. C-Series Linear Accelerators: An upgrade of the Console to WES7 is required. Support of Consoles at v13 will only be supported on Windows XP with prior written consent of the VP of Field Service. TrueBeam Accelerators Console version TBM 2.5MR2 required. Customers with an Acuity will need a 'standalone Windows Domain Controller' (hardware & configuration supplied by Varian). Please consult with your Varian Service team for details. Supports Elekta Linacs and Siemens Linacs without Imaging V13.0 MR1.1 or higher is required Supports Siemens Linacs with Imaging TBD a new version is being developed for compatibility with ARIA v15.1. Page 6

8 Please contact your local service or sales representative for details. Long-Term Archive LTA is not supported with v15.x; customers wishing to archive data external to the Varian System software are directed to use DICOM Import/Export functionality. Varian Link Link Stored Procedures are not supported with v15.x; customers are directed to transition to use ARIA Access (web services API provided with ARIA). PAVS & BCCV (Verification Products) VVS 1.1 required DCF Core Service For customers with Eclipse the deployment of the DCF Core service to support calculation has been on a backend server or a FAS, with this release the recommendation is to deploy this service only on a backend server though the traditional/previous deployment model is still supported. TECHNICAL SPECIFICATIONS DESKTOP/PC TECHNICAL SPECIFICATIONS Common The following technical specifications are common to all Varian client/desktop applications, excluding Eclipse and treatment related software sold with hardware that must be purchased from Varian. Specifically, these specifications apply to the ARIA oncology information system for Radiation Oncology (ARIA OIS for RO), ARIA Radiation Therapy Management (ARIA RTM) and ARIA oncology information system for Medical Oncology (ARIA OIS for MO). Further tables below may modify these specifications based on the specific application requirements. System Requirements Specification Operating system Microsoft Windows 7 SP1 Professional, Ultimate or Enterprise (ARIA OIS for RO and ARIA RTM) 1 OR Microsoft Windows 10 Professional or Enterprise 64-bit only 1 NOTE: ARIA OIS for MO v15.1 or higher does not support any edition of Windows 7/Windows 7 SP1. Page 7

9 Browser Internet Explorer 11 or higher 2 Managed execution environment.net or higher Installer Windows Installer 4.5 Processor Memory Disk space Minimum of a single Core GHz or better (Dual core or better CPU recommended when running multiple UserHome sessions and imaging applications.) 1 GB RAM minimum free memory (2 GB RAM recommended when running multiple UserHome sessions and imaging applications.) 20 GB available free disk space Video adapter Video adapter with 512 MB of video memory recommended. DirectX Monitor 9 hardware accelerated and Shader Model 3 minimum. Minimum of OpenGL 2.1 for imaging applications. Minimum of 17" monitor capable of 1280x1024 Network interface Other Minimum of 100 Mbps NIC, 1 Gbps recommended Microsoft Windows compatible 101-key keyboard and 2-button mouse. Unless explicitly noted otherwise Varian's applications are not optimized for use with Touch Screens. Optional Hardware Guidelines Peripherals Ports/adapters ARIA OIS for RO System Requirements Software ARIA OIS for MO System Requirements Monitor Specification Optical drive (CD/DVD) for importing documents or images Topaz Signature Pad (T-LBK462-HSB-R USB connection only) 1 parallel, 1 serial and 2 USB ports for connecting optional peripherals. Serial-to-USB and parallel-to-usb adapters may be available to support legacy third-party peripherals. Specification Microsoft Word 2013 or Word 2016 higher for use with Dynamic Documents. Adobe Reader 11.0 Specification 17" or greater capable of 1280x1024 minimum resolution 2 Subject to the support of the Operating System Page 8

10 Eclipse Treatment Planning System The Eclipse client software is required to run on hardware supplied by Varian please see the TPS Supported Hardware Reference Guide for current supported hardware. Velocity Imaging Informatics System Please see the Velocity Imaging Informatics System Specifications reference guide for further information. Tablet, Slate, Convertible laptops: Provided a tablet, slate or convertible laptop computer meets or exceeds the specifications listed above these devices are supported. Note that Varian's applications are not designed for use with touch interfaces and as such these devices must be supplied with a standard keyboard and mouse for optimal user experience. Customers may also want to consider providing docking stations (if available) for use with these devices. Citrix XenApp (thin-client) Specifications: ARIA OIS for RO, ARIA OIS for MO, Eclipse, Velocity and InSightive, are supported in a Citrix XenApp environment. The following are the specifications for a thin-client device for use with these applications. Citrix XenApp thin-client System Requirements Specification Software Operating System Citrix Receiver 4.4 LTSR (Long Term Service Release) See Citrix Operating System compatibility requirements for Citrix Receiver. Processor Memory Disk Space Video Adapter Monitor Page 9 Varian has validated our software with the supported Citrix Receiver version on Windows 7 SP1 and Windows 10. See Citrix requirements for Citrix Receiver See Citrix requirements for Citrix Receiver See Citrix requirements for Citrix Receiver See Citrix requirements for Citrix Receiver Minimum of 17" Monitor capable of 1280x1024 for ARIA OIS for RO, ARIA RTM, and ARIA OIS for MO Minimum 23" Monitor capable of 1920x1080 for Eclipse 27" Monitor capable of 2560x1440 recommended. 23" Monitor capable of 1600x1200 for ARIA RTM recommended.

11 Network Interface Other Minimum of 100 Mbps NIC, 1 Gbps recommended Microsoft Windows compatible 101-key keyboard and 2-button mouse. Unless explicitly noted otherwise Varian's applications are not optimized for use with Touch Screens. Optional Hardware Guidelines Specification Peripherals Ports/adapters Optical drive (CD/DVD) for importing documents or images Topaz Signature Pad (T-LBK462-HSB-R USB connection only) 1 parallel, 1 serial and 2 USB ports for connecting optional peripherals. Serial-to-USB and parallel-to-usb adapters may be available to support legacy third-party peripherals. SERVER TECHNICAL CONSIDERATIONS The following sections provide some general considerations for deployment of Varian's server software as well as the Operating System and related software requirements. General Considerations The following are general considerations when deploying Varian's oncology server software. Specification Processors (CPU) Anti-virus Varian validates our software only on Intel CPU's not 'Intel Compatible' CPUs. The core counts provided as recommendations in this document are in reference to Xeon V2 processors running at 2.1 GHz or higher. Varian recommends deploying anti-virus software on the servers supporting Varian's oncology software with virus signatures updated frequently. Storage See Varian's anti-virus guidelines (CTB-GE-309) for further details available through MyVarian. Varian recommends deploying the Varian System Database as well as the file system storage on the equivalent of Direct Attached Storage with SAS drives and interfaces capable of 3 Gbps or higher. While Varian supports deployments on SAN or other network storage technologies, performance may be impacted. Backup Varian recommends the use of hardware RAID (RAID1 for system and application files, RAID5 or 6 for data storage), the use of software RAID is not supported. Varian's Oncology System Software is the repository of extremely important oncology workflow data, as such a proper enterprise backup solution is highly recommended. Page 10

12 Redundancy Power Management User Authentication Network Integration Additional Hardware Components Hardware Virtualization Please see Varian's Backup Configuration Guidelines (CTB-GE-936) for further information regarding backing up the Varian System. Varian's Radiation Oncology System software provides front line support for delivery of Radiation Oncology treatments on Varian or 3rd party linear accelerators; availability of the Varian System 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. Modern CPUs and systems provide sophisticated options for Power Management (PM) by throttling CPU and other system resource performance. Unfortunately these features can greatly impact performance of the Varian and related 3 rd party software (MS SQL, and XenApp most specifically but may impact other Varian software.), Customers are advised to consult their 3 rd party vendor documentation for proper settings to ensure maximum/high performance (PM 'disabled') of their systems running Varian software. Note that the appropriate PM setting may not be labeled 'disabled' but rather some combination of 'Performance'., 'Maximum Performance', 'High Performance' etc., customers should consult their vendor documentation to confirm that PM can be disabled and the proper setting to use. Setting this feature appropriately at the BIOS level is generally considered the most reliable (it should override any hypervisor or OS settings) in ensuring that PM is set appropriately. User Authentication for ARIA RO, ARIA MO, and Eclipse is now performed through Windows Active Directory. Please see the Security Implementation Guide (SIG-SS-150) available from the MyVarian website for further information. Varian's software supports only TCP/IP network environments with IPv4. Varian's software can exchange data with many different 3rd party systems including Hospital Information Systems, PACS, CT and other medical imaging devices, as well as Varian and 3rd party Linear accelerators as such network bandwidth requirements can vary greatly depending on many factors including the type and number of products deployed. Please see Varian's Network Configuration Guidelines (CTB-GE-945) available via MyVarian for more detailed information. For service, installation and system management the following hardware is recommended to be available on any server supporting Varian server software: 15" 1024 x 768 resolution Optical Drive (CD/DVD) 8x or higher 2 USB ports Microsoft Windows Compatible 101 Key Keyboard & 2 button mouse Varian supports our software on systems using hardware virtualization provided the guest virtual machines are configured with sufficient resources as identified in this document. Customers are advised however that it is their responsibility to ensure proper performance of the system which means following best practices for their chosen hypervisor with respect to the system as a whole and for 3 rd party software such as MS SQL & Citrix XenApp; for example with VMWare using VMXNET3 & PVSCSI drivers and Page 11

13 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. As well in reference to CPU core recommendations it may be considered best practices with some hyper-visors & hardware platforms to assign only even core counts to a VM, customers should therefore consider rounding core counts up to the next highest value though again vendor hyper-visor documentation on this subject should be consulted. Server OS and Software Requirements The following are the standard software requirements for Varian's server software components unless otherwise explicitly noted in the sections below: Specification Operating System Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. Browser Internet Explorer 11 or higher Managed Execution Environment.NET or higher Installer Windows Installer 4.5 DEPLOYMENT CONSIDERATIONS With the common use of application virtualization (Citrix XenApp) and hardware virtualization (VMWare ESXi, MS Hyper-V etc.) customers have many different options for deploying Varian's client and server software. As well high count multi-core servers (dual socket 10-core or more) with a large amount of RAM (128 GB or more) are extremely cost effective, providing even more options for customers when making purchasing and deployment decisions. Historically Varian has published separate documents directed at customers using hardware virtualization (a 'Server Virtualization Guide') versus a pure physical server installation ('Technical Specifications'). Since the resource requirements as provided are with respect to physical resources eg. physical cores (not 'logical' or 'hyper threaded cores') this separation is considered unnecessary and as such this document simply treats the difference between a hardware virtualized deployment versus a pure physical deployment as different 'deployment models' where separation of the different backend services used to support Varian's software is provided based on 'best practices' (considering cost, ability to manage the resources assigned, serviceability considerations etc.). Page 12

14 DEPLOYMENT MODELS The following models are provided as recommended deployment models for ARIA OIS for RO, ARIA OIS for MO, ARIA RTM, Eclipse Treatment Planning System and sizing recommendations are provided for each. As noted previously please see the relevant documentation for Velocity and InSightive when these additional products are purchased. In the figures included in this section and Appendix A the following legend is provided for reference purposes: o Represents a physical or virtual server where 1 or more Varian, 3 rd party (MS SQL etc.) or Operating System services (service applications) is running to support data import/export between Varian client applications or 3 rd party software systems. The actual services deployed and number of recommended servers needed depends on the actual Varian applications purchased and deployment model selected. For a more detailed description of the service names and concepts please see Appendix B. o Varian's IEM or ARIA Connect server software used to exchange data via HL7 with 3 rd party hospital information systems. This is optionally purchasable software though it is extremely common to be found with ARIA for RO and ARIA for MO deployments and as such has been included in the diagrams for completeness. o Represents 1 or more Citrix XenApp 'worker' servers (either physical or virtual). Varian's client software is deployed directly on these servers. The size and number of XenApp servers deployed depends on the number of users a customer needs to support and their chosen deployment model (physical or virtual). o Represents the Citrix XenApp support services such as the Citrix WebInterface/Storefront, Delivery Controller, Citrix License server etc. These are services supplied by Citrix to support any typical Citrix XenApp environment; the resource requirements for these services are defined by Citrix and are outside the scope of this document. Customers should consult the appropriate Citrix documentation for recommendations regarding the proper deployment of these services for the version of Citrix XenApp they intend to use. o Represents 1 or more physical Framework Agent Servers (FAS) used to perform complex physics calculations for Eclipse. These are physical servers which must be purchased from Varian and are required when deploying Eclipse in a Citrix XenApp environment; they are included in the diagrams for completeness. o Simply 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's client software (Userhome, ARIA for OIS, ARIA for RTM, ARIA for MO or Eclipse) which can be installed directly on a PC/client device or in a Citrix XenApp environment. The PC requirements are identified above. o Varian's 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 above as this software cannot be deployed Page 13

15 in Citrix XenApp environment and comes packaged only with client hardware supplied by Varian. o Simply represents the Citrix Receiver software deployed on PC/client devices when a customer is using Citrix XenApp. o Represents one or more 3 rd party imaging (CT/MRI/PET/PACs) or hospital information systems exchanging patient data with Varian's 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 3 rd party systems). o Represents the exchange of data (generally screen pixels) between the Citrix Receiver & backend Citrix XenApp servers. Virtual Server Recommended Deployment Model Figure 1: Virtual Server Recommended Deployment Figure 1 is Varian's recommended deployment model when using hardware virtualization where the Varian software services are separated into dedicated virtual servers. The goal of this deployment model is to allow customers to segregate Varian software services for more fine grained computer resource allocation and management for the services as well as for minimizing potential conflicts and the troubleshooting of issues. Physical Server Recommended Deployment Model Page 14

16 Figure 2: Physical Server Recommended Deployment Model Figure 2 is a depiction of Varian's traditional physical server deployment model. In this model the primary software services used by Varian's ARIA and Eclipse software (and management of treatment information) are deployed on a single server deployment or 'combo server' along with a separate server for use with analytics & reporting (Data Warehouse Server). 3 Note furthermore, that in this release Varian is recommending placing the Distributed Calculation Framework (DCF) Core Service only on the same physical server as all other 'backend services' though the previous deployment model on a FAS is still supported. Secondary Multi-Server Deployment Model (pure physical deployment) Figure 3: Secondary Multi-Server Deployment Model 3 Note that customers considering the purchase of InSightive should be aware that InSightive can be installed on the same server as the Data Warehouse server provided the server is sized appropriately to support both, which may be a cost effective choice for some customers. See CTB-PM-990-B referenced earlier for more information. Whether or not customers choose to do so or provide a separate InSightive Server is dependent on current and future purchasing decisions and as such Varian does not supply a specific recommendation to support one deployment model over another. Page 15

17 Figure 3 is a secondary deployment model that would primarily be recommended for larger customers (>6 Linear Accelerators or >90 users) considering a pure physical deployment. In this model the Varian System Database will be performing a significant amount of work, as such dedicating a single server's computer resources to the Varian System Database is considered best practices, and the other services (Platform, DICOM, File and DCF Core Services) can reside on a second physical server. Otherwise for the Data Warehouse and IEM/Aria Connect services this deployment model remains unchanged from the previous 'pure physical' deployment model above. 4 DEPLOYMENT MODELS - SERVER SIZING GUIDELINES The previous sections described general requirements for the Varian software stack and introduced some recommended deployment models; the following sections provide more specific detail in order for customers to properly size their technical environment based on the products purchased, their specific size and workload and selected server deployment model. NOTE: The resource requirements as supplied here are recommendations intended to ensure Varian's software achieves acceptable end-user experience for typical sizes of customers. The actual computer resources needed by any single customer will depend on their specific workload and as such monitoring of the server resources and adjusting them as needed is highly recommended. Customers should use careful consideration in reducing the allocated computer resources below the following recommendations, and be prepared to add resources quickly, as impaired user experience may result. NOTE: The term 'ARIA for Radiation Oncology' is used throughout the server specifications and encompasses the server requirements for the Varian products named ARIA OIS for Radiation Oncology (ARIA OIS for RO) and ARIA Radiation Therapy Management (ARIA RTM). VIRTUAL SERVER RECOMMENDED DEPLOYMENT MODEL As the most general deployment model this section lists the system requirements of the Varian software using the terminology and configuration as depicted in Figure 1. For ease of consumption 4 See previous footnote for comments on deploying InSightive with the Data Warehouse Server. Page 16

18 later sections will provide a summation of resource requirements of the pure physical deployment models depicted above. Page 17

19 ARIA for Radiation Oncology The following section provides the technical specifications for customers deploying only ARIA for Radiation Oncology. Server Sizing Guidelines Installed Software & OS Services Operating System CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) - Up to 4 Linacs (60 ARIA RO Users) - Up to 6 Linacs (90 ARIA RO Users) - Up to 8 Linacs (120 ARIA RO Users) Varian System Database Server Data Storage Growth ~15 GB/year/linear accelerator 2 Storage Partitioning 4 -System Partition (C:) - Data Partition (D:) 100 GB DB + Log - Dump Partition (E:) ~75 GB Temp + Dump Files Storage Speed Data Warehouse Server MS SQL 2014 MS SQL 2014, SSRS (SQL Server Reporting Services) Platform Server File Server DICOM Server IIS (Varian WebServices), and Shared Framework Services. File Storage (CIFS) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. File, DB & IT Service (1 instance per Accelerator) 4 cores / 8 GB 8 cores / 16 GB 3 cores / 8 GB 2 cores / 4 GB 2 cores / 4 GB 6 cores / 14 GB 8 cores / 32 GB 5 cores / 14 GB 2 cores / 4 GB 3 cores / 6 GB 8 cores / 20 GB 12 cores / 32 GB 7 cores / 20 GB 3 cores / 8 GB 4 cores / 8 GB 10 cores / 26 GB 16 cores / 64 GB 1 9 cores / 26 GB 4 cores / 8 GB 5 cores / 10 GB ~13 GB/year/linear accelerator 150 GB DB + Log Files 150 GB Temp + Dump File N/A ~ 50 GB/year/linear Accelerator 3 ~100 GB for System & Installation Files 75 GB - Configuration + Logs N/A 250 GB ~100 GB for logs & temp dicom files N/A N/A N/A Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps Network Interface 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 Database & File server partitions are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs. Other server partition sizes recommended for log files and other temporary storage such as DICOM files prior to importing for use with ARIA and/or Eclipse and can be adjusted as needed. Page 18

20 ARIA OIS for Medical Oncology The following section provides the technical specifications for customers deploying only ARIA OIS for Medical Oncology. Server Sizing Guidelines Varian System Database Server Platform & File Server Installed Software & OS Services Operating System MS SQL 2014 File Storage (CIFS) & IIS (Varian WebServices) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. CPU/RAM (cores/gb) - Up to 30 Users 4 cores / 8 GB 2 cores / 4 GB - Up to 60 Users 6 cores / 16 GB 2 cores / 4 GB - Up to 90 Users 12 cores / 24 GB 3 cores / 8 GB - Up to 120 Users 16 cores / 32 GB 4 cores / 8 GB Data Storage Growth ~15 GB/year/Oncologist 1 ~10 GB/year/Oncologist 2 Storage Partitioning 3 -System Partition (C:) ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log 75 GB file storage & system configuration - Dump Partition (E:) ~75 GB Temp + Dump Files N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 2 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated and the type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 3 The data partition sizes are estimates for a single Oncologist department for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs. Page 19

21 Eclipse Only The following section provides the technical specifications for customers deploying Eclipse only. Server Sizing Guidelines Varian System Database Server Platform Server File Server DCF Server Installed Software & OS Services Operating System MS SQL 2014 IIS (Varian WebServices), and Shared Framework Services. File Storage (CIFS), DICOM Services (File and DB Services) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. DCF Core Service CPU/RAM (cores/gb) - Up to 2 Linacs / 6 Eclipse Users - Up to 4 Linacs / 12 Eclipse Users - Up to 6 Linacs / 18 Eclipse Users - Up to 8 Linacs / 24 Eclipse Users 2 cores / 8 GB 2 cores / 8 GB 2 cores / 4 GB 2 cores / 4 GB 4 cores / 14 GB 3 cores / 12 GB 2 cores / 4 GB 3 cores / 6 GB 6 cores / 20 GB 4 cores / 16 GB 3 cores / 8 GB 4 cores / 8 GB 8 cores / 26 GB 5 cores / 20 GB 4 cores / 8 GB 5 cores / 10 GB Data Storage Growth ~15 GB/year/linear accelerator 1 N/A ~ 50 GB/year/linear Accelerator 2 Storage Partitioning 3 N/A -System Partition (C:) ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log 75 GB - Configuration + Logs 250 GB N/A - Dump Partition (E:) ~75 GB Temp + Dump Files N/A N/A N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 2 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 3 The data partition sizes for the database & file services are estimates for a single linear accelerator for approximately 5 years of use. Partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage). Specifically, the DCF Core Service needs access to data called 'beam data' which is a representation of physical characteristics of the radiation beams from an accelerator. This data does not vary frequently only when it is re-measured, the size of data can vary depending on the number of versions kept, number & types of beams etc. a rough estimate would be ~3 GB per accelerator. Other server partition sizes recommended for log files and other temporary storage such as DICOM files prior to importing for use with ARIA and/or Eclipse and can be adjusted as needed. Page 20

22 ARIA for Radiation Oncology and Eclipse The following section provides the technical specifications for customers deploying ARIA for Radiation Oncology and Eclipse as an integrated platform. Server Sizing Guidelines Installed Software & OS Services Operating System CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) / 6 Eclipse Users - Up to 4 Linacs (60 ARIA RO Users) / 12 Eclipse Users - Up to 6 Linacs (90 ARIA RO Users) / 18 Eclipse Users - Up to 8 Linacs (120 ARIA RO Users ) / 24 Eclipse Users Data Storage Growth Storage Partitioning 4 -System Partition (C:) Varian System Database Server Data Warehouse Server MS SQL 2014 MS SQL 2014, SSRS (SQL Server Reporting Services) Platform Server File Server DICOM Server DCF Server IIS (Varian WebServices) and Shared Framework Services File Storage (CIFS) File, DB & IT Service (1 instance per Accelerator) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. DCF Core Service 4 cores / 8 GB 8 cores / 16 GB 4 cores / 8 GB 2 cores / 8 GB 2 cores / 4 GB 2 cores / 4 GB 8 cores / 16 GB 8 cores / 32 GB 6 cores / 16 GB 2 cores / 8 GB 3 cores / 6 GB 3 cores / 6 GB 12 cores / 24 GB 12 cores / 32 GB 8 cores / 24 GB 3 cores / 8 GB 4 cores / 8 GB 4 cores / 8 GB 16 cores / 32 GB 16 cores / 64 GB 1 10 cores / 32 GB 4 cores / 8 GB 5 cores / 10 GB 5 cores / 10 GB ~15 GB/year/linear accelerator 2 ~13 GB/year/linear accelerator - Data Partition (D:) 100 GB DB + Log 150 GB DB + Log Files - Dump Partition (E:) ~75 GB Temp + Dump Files Storage Speed 150 GB Temp + Dump File N/A ~ 50 GB/year/linear Accelerator 3 ~100 GB for System & Installation Files 75 GB - Configuration + Logs N/A 250 GB ~100 GB for logs N/A N/A N/A N/A N/A N/A Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps Network Interface 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes for the database & file services are estimates for a single linear accelerator for approximately 5 years of use. Partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage). Specifically the DCF Core Service needs access to data called 'beam data' which is a representation of physical characteristics of the radiation beams from an accelerator. This data does not vary frequently only when it is re-measured, the size of data can vary depending on the number of versions kept, number & types of beams etc. a rough estimate would be ~3 GB per accelerator. Other server partition sizes recommended for log files and other temporary storage such as DICOM files prior to importing for use with ARIA and/or Eclipse and can be adjusted as needed. Page 21

23 ARIA Comprehensive Cancer Solution (CCS) The following section provides the technical specifications for customers deploying a CCS (ARIA Comprehensive Cancer Solution) environment. Server Sizing Guidelines Installed Software & OS Services Operating System CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) / 30 ARIA MO Users / 6 Eclipse Users - Up to 4 Linacs (60 ARIA RO Users) / 60 ARIA MO Users / 12 Eclipse Users - Up to 6 Linacs (90 ARIA RO Users) / 90 ARIA MO Users / 18 Eclipse Users - Up to 8 Linacs (120 ARIA RO Users) / 120 ARIA MO Users / 24 Eclipse Users Data Storage Growth Storage Partitioning 4 -System Partition (C:) Varian System Database Server MS SQL 2014 Data Warehouse Server MS SQL 2014, SSRS (SQL Server Reporting Services) Platform Server File Server DICOM Server DCF Server IIS (Varian WebServices) and Shared Framework Services File Storage (CIFS) File, DB & IT Service (1 instance per Accelerator) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. DCF Core Service 5 cores / 8 GB 8 cores / 16 GB 4 cores / 8 GB 2 cores / 8 GB 2 cores / 4 GB 2 cores / 4 GB 10 cores / 16 GB 8 cores / 32 GB 6 cores / 16 GB 2 cores / 8 GB 3 cores / 6 GB 3 cores / 6 GB 15 cores / 24 GB 12 cores / 32 GB 8 cores / 24 GB 3 cores / 8 GB 4 cores / 8 GB 4 cores / 8 GB 20 cores / 32 GB 16 cores / 64 GB 1 10 cores / 32 GB 4 cores / 8 GB 5 cores / 10 GB 5 cores / 10 GB ~15 GB/year/linear accelerator 2 - Data Partition (D:) 100 GB DB + Log - Dump Partition (E:) ~75 GB Temp + Dump Files Storage Speed Network Interface ~13GB/year/linear accelerator 150 GB DB + Log Files 150 GB Temp + Dump File N/A ~50 GB/year/linear accelerator 3 ~100 GB for System & Installation Files 75 GB - Configuration + Logs N/A 250 GB ~100 GB for logs N/A N/A N/A N/A N/A N/A Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes for the database & file services are estimates for a single linear accelerator for approximately 5 years of use. Partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage). Specifically the DCF Core Service needs access to data called 'beam data' which is a representation of physical characteristics of the radiation beams from an accelerator. This data does not vary frequently only when it is re-measured, the size of data can vary depending on the number of versions kept, number & types of beams etc. a rough estimate would be ~3 GB per accelerator. Other server partition sizes recommended for log files and other temporary storage such as DICOM files prior to importing for use with ARIA and/or Eclipse and can be adjusted as needed. Page 22

24 PHYSICAL SERVER RECOMMENDED DEPLOYMENT The following are the recommended requirements for deploying Varian ARIA OIS for RO, ARIA OIS for MO and Eclipse software with pure physical servers. For customers with existing physical hardware running a previous version of Varian's software note that the hardware recommendations supplied here include resources for running on the Combo Server when Eclipse has been purchased. If the DCF Core Service is running on a FAS see the appendix provided below to determine if you're existing hardware is sufficient to run this version. Page 23

25 ARIA for Radiation Oncology Server Sizing Guidelines Combo Server Data Warehouse Server Installed Software & OS Services Operating System CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) - Up to 4 Linacs (60 ARIA RO Users) - Up to 6 Linacs ( 90 ARIA RO Users) - Up to 8 Linacs (120 ARIA RO Users) Data Storage Growth Storage Partitioning 4 -System Partition (C:) MS SQL 2014, IIS (Varian WebServices), Shared Framework MS SQL 2014, SSRS (SQL Server Reporting Services) Services, File Services(CIFS), DICOM Services (File, DB & IT Services (1 instance per Accelerator)) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. 11 cores / 22 GB 8 cores / 16 GB 16 cores / 36 GB 8 cores / 32 GB 22 cores / 54 GB 12 cores / 32 GB 28 cores / 68 GB 16 cores / 64 GB 1 ~15 GB/year/linear accelerator 2 for DB storage ~50 GB/year/linear accelerator for file storage 3 ~13 GB/year/linear accelerator ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log 150 GB DB + Log Files - Dump Partition (E:) ~75 GB Temp + Dump Files 150 GB Temp + Dump File - File Partition (F:) ~300 GB file data + Configuration & Logs N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). Page 24

26 ARIA OIS for Medical Oncology Server Sizing Guidelines Combo Server Installed SW & OS Services MS SQL 2014, File Services (CIFS) and IIS (Varian WebServices) Operating System Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. CPU/RAM (cores/gb) - Up to 30 ARIA MO Users 6 cores / 16 GB - Up to 60 ARIA MO Users 10 cores / 24 GB - Up to 90 ARIA MO Users 15 cores / 32 GB - Up to 120 ARIA MO Users 20 cores / 40 GB Data Storage Growth Storage Partitioning 3 -System Partition (C:) ~15 GB/year/Oncologist 1 for DB Storage ~5 GB/year/Oncologist for file storage 2 ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log - Dump Partition (E:) ~75 GB Temp + Dump Files - File Partition (F:) ~50 GB Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 2 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 3 The data partition sizes are estimates for a single Oncologist practice for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs. Page 25

27 Eclipse Only Server Sizing Guidelines Installed Software & OS Services Operating System Combo Server MS SQL 2014, IIS (Varian WebServices), Shared Framework Services, File Services (CIFS), DICOM Services (File & DB Services) & DCF Core Services Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. CPU/RAM (cores/gb) - Up to 2 Linacs (6 Eclipse Users) 8 cores / 24 GB - Up to 4 Linacs (12 Eclipse Users) 12 cores / 36 GB - Up to 6 Linacs (18 Eclipse Users) 17 cores / 52 GB - Up to 8 Linacs (24 Eclipse Users) 22 cores / 64 GB Data Storage Growth Storage Partitioning 3 -System Partition (C:) ~15 GB/year/linear accelerator 1 for DB Storage ~50 GB/year/linear accelerator for file storage 2 ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log - Dump Partition (E:) ~75 GB Temp + Dump Files - File Partition (F:) ~300 GB file data + Configuration & Logs Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 2 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 3 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). DCF Core needs access to data called 'beam data'. This data does not vary frequently, the size of data can vary depending on the number of versions kept, number & types of beams etc. a rough estimate would be ~3 GB per accelerator. While the partition this data is stored on must be available to the OS at the time DCF Core is installed it can reside on a network partition provided the access speed is sufficient. Page 26

28 ARIA for Radiation Oncology & Eclipse Server Sizing Guidelines Combo Server Data Warehouse Server Installed Software & OS Services Operating System CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) / 6 Eclipse Users - Up to 4 Linacs (60 ARIA RO Users) / 12 Eclipse Users - Up to 6 Linacs (90 ARIA RO Users) / 18 Eclipse Users - Up to 8 Linacs (120 ARIA RO Users) / 24 Eclipse Users Data Storage Growth Storage Partitioning 4 -System Partition (C:) Varian System Database (MS SQL 2014), IIS (Varian MS SQL 2014, SSRS (SQL Server Reporting Services) WebServices), Shared Framework Services, File Services (CIFS), DICOM Services (File, DB and IT Services (1 per Accelerator)) & DCF Core Service Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. 14 cores / 32 GB 8 cores / 16 GB 22 cores / 50 GB 8 cores / 32 GB 31 cores / 70 GB 12 cores / 32 GB 40 cores / 90 GB 16 cores / 64 GB 1 ~15 GB/year/linear accelerator 2 for DB storage ~50 GB/year linear accelerator for file storage 3 ~13 GB/year/linear accelerator ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log 150 GB DB + Log Files - Dump Partition (E:) ~75 GB Temp + Dump Files 150 GB Temp + Dump File - File Partition (F:) ~300 GB - file data + Configuration & Logs N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). DCF Core needs access to data called 'beam data'. This data does not vary frequently, the size of data can vary depending on the number of versions kept, number & types of beams etc. a rough estimate would be ~3 GB per accelerator. While the partition this data is stored on must be available to the OS at the time DCF Core is installed it can reside on a network partition provided the access speed is sufficient. Page 27

29 ARIA Comprehensive Cancer Solution (CCS) Server Sizing Guidelines Combo Server Data Warehouse Server Installed Software & OS Services Operating System CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) / 30 ARIA MO Users / 6 Eclipse Users - Up to 4 Linacs (60 ARIA RO Users) / 60 ARIA MO Users / 12 Eclipse Users - Up to 6 Linacs (90 ARIA RO Users) / 90 ARIA MO Users / 18 Eclipse Users - Up to 8 Linacs (120 ARIA RO Users) / 120 ARIA MO Users / 24 Eclipse Users Data Storage Growth Storage Partitioning 4 -System Partition (C:) Varian System Database (MS SQL 2014), IIS (Varian WebServices), Shared Framework Services, File Services (CIFS), DICOM Services (File, DB & IT Services (1 per Accelerator)) & DCF Core Service (If Eclipse included) MS SQL 2014, SSRS (SQL Server Reporting Services) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. 15 cores / 32 GB 8 cores / 16 GB 24 cores / 50 GB 8 cores / 32 GB 34 cores / 70 GB 12 cores / 32 GB 44 cores / 90 GB 16 cores / 64 GB 1 ~15 GB/year/linear accelerator 2 or Medical Oncologist for DB storage ~50 GB/year/accelerator or Medical Oncologist for file storage 3 ~100 GB for System & Installation Files ~13 GB/year/linear accelerator - Data Partition (D:) 100 GB DB + Log 150 GB DB + Log Files - Dump Partition (E:) ~75 GB Temp + Dump Files 150 GB Temp + Dump File - File Partition (F:) ~300 GB - file data + Configuration & Logs N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). DCF Core needs access to data called 'beam data'. This data does not vary frequently, the size of data can vary depending on the number of versions kept, number & types of beams etc. a rough estimate would be ~3 GB per accelerator. While the partition this data is stored on must be available to the OS at the time DCF Core is installed it can reside on a network partition provided the access speed is sufficient. Page 28

30 SECONDARY PHYSICAL SERVER RECOMMENDED DEPLOYMENT As noted previously, for larger customers (>6 Linear Accelerators or >90 users) wanting to use a pure physical deployment separating the Varian System Database from the rest of the combined services is highly desirable to best be able to manage the database resource requirements and performance as well as managing the costs for the servers. For such customers Varian recommends using the following deployment model and specifications. Note that in this model the DCF Core Service is installed on the 'Platform & File Server'. Page 29

31 ARIA for Radiation Oncology Server Sizing Guidelines Varian System Database Server Data Warehouse Server Platform & File Server Installed Software & OS Services MS SQL 2014 MS SQL 2014, SSRS (SQL Server Reporting Services) IIS (Varian WebServices), Shared Framework Services, File Services (CIFS), DICOM Services (File, DB & IT Service (1 per Accelerator)), Operating System Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) - Up to 4 Linacs (60 ARIA RO Users) - Up to 6 Linacs (90 ARIA RO Users) - Up to 8 Linacs (120 ARIA RO Users) 4 cores / 8 GB 8 cores / 16 GB 7 cores / 16 GB 6 cores / 14 GB 8 cores / 32 GB 10 cores / 22 GB 8 cores / 20 GB 12 cores / 32 GB 14 cores / 34 GB 10 cores / 26 GB 16 cores / 64 GB 1 18 cores / 42 GB Data Storage Growth ~15 GB/year/linear accelerator 2 ~13 GB/year/linear accelerator ~50 GB/year/accelerator 3 Storage Partitioning 4 -System Partition (C:) ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log 150 GB DB + Log Files ~300 GB - file data + Configuration & Logs - Dump Partition (E:) ~75 GB Temp + Dump Files 150 GB Temp + Dump File N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). Page 30

32 ARIA OIS for Medical Oncology The following section provides the technical specifications for customers deploying only ARIA OIS for Medical Oncology. Server Sizing Guidelines Varian System Database Server Platform & File Server Installed Software & OS Services Operating System MS SQL 2014 File Services (CIFS) and IIS (Varian WebServices) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. CPU/RAM (cores/gb) - Up to 30 ARIA MO Users - Up to 4 60 ARIA MO Users - Up to 90 ARIA MO Users - Up to 120 ARIA MO Users 4 cores / 8 GB 2 cores / 4 GB 8 cores / 16 GB 2 cores / 4 GB 12 cores / 24 GB 3 cores / 8 GB 16 cores / 32 GB 4 cores / 8 GB Data Storage Growth ~15 GB/year/Oncologist 1 ~ 10 GB/year/Oncologist 2 Storage Partitioning 3 -System Partition (C:) ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log 50 GB - Dump Partition (E:) ~75 GB Temp + Dump Files N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 2 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 3 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs. Page 31

33 Eclipse Only The following section provides the technical specifications for customers deploying only Eclipse. Server Sizing Guidelines Varian System Database Server Platform & File Server Installed Software & OS Services MS SQL 2014 IIS (Varian WebServices), Shared Framework Services, File Services (CIFS), DICOM Services (File & DB Services) & DCF Core Service Operating System Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. CPU/RAM (cores/gb) - Up to 2 Linacs / 6 Eclipse Users 2 cores / 8 GB 6 cores /16 GB - Up to 4 Linacs / 12 Eclipse Users 4 cores / 14 GB 8 cores / 22 GB - Up to 6 Linacs / 18 Eclipse Users 6 cores / 20 GB 11 cores / 32 GB - Up to 8 Linacs / 24 Eclipse Users 8 cores / 26 GB 14 cores / 38 GB Data Storage Growth ~15 GB/year/linear accelerator 1 ~50 GB/year/linear Accelerator 2 Storage Partitioning 3 -System Partition (C:) ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log ~300 GB - file data + Configuration & Logs - Dump Partition (E:) ~75 GB Temp + Dump Files N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 2 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 3 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). DCF Core needs access to data called 'beam data'. This data does not vary frequently, the size of data can vary depending on the number of versions kept, number & types of beams etc. a rough estimate would be ~3 GB per accelerator. While the partition this data is stored on must be available to the OS at the time DCF Core is installed it can reside on a network partition provided the access speed is sufficient. Page 32

34 ARIA for Radiation Oncology and Eclipse The following section provides the technical specifications for customers deploying ARIA for Radiation Oncology and Eclipse as an integrated platform. Server Sizing Guidelines Varian System Database Server Data Warehouse Server Platform & File Server Installed Software & OS Services MS SQL 2014 MS SQL 2014, SSRS (SQL Server Reporting Services) Operating System CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) / 6 Eclipse Users - Up to 4 Linacs (60 ARIA RO Users) / 12 Eclipse Users - Up to 6 Linacs (90 ARIA RO Users) / 18 Eclipse Users - Up to 8 Linacs (120 ARIA RO Users) / 24 Eclipse Users IIS (Varian WebServices), Shared Framework Services, File Services (CIFS), DICOM Services (File, DB and IT Services (1 per Accelerator)) & DCF Core Service Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. 4 cores / 8 GB 8 cores / 16 GB 10 cores / 22 GB 6 cores / 16 GB 8 cores / 32 GB 14 cores / 34 GB 12 cores / 24 GB 12 cores / 32 GB 19 cores / 46 GB 16 cores / 32 GB 16 cores / 64 GB 1 24 cores / 58 GB Data Storage Growth ~15 GB/year/linear accelerator 2 ~13 GB/year/linear accelerator ~50 GB/year/linear Accelerator 3 Storage Partitioning 4 -System Partition (C:) ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log 150 GB DB + Log Files ~300 GB-file data + Configuration & Log - Dump Partition (E:) ~75 GB Temp + Dump Files 150 GB Temp + Dump File N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). DCF Core needs access to data called 'beam data'. This data does not vary frequently, the size of data can vary depending on the number of versions kept, number & types of beams etc. a rough estimate would be ~3 GB per accelerator. While the partition this data is stored on must be available to the OS at the time DCF Core is installed it can reside on a network partition provided the access speed is sufficient. Page 33

35 ARIA Comprehensive Cancer Solution (CCS) The following section provides the technical specifications for customers deploying a CCS (ARIA Comprehensive Cancer Solution) environment consisting of ARIA for Radiation Oncology, ARIA OIS for Medical Oncology with or without Eclipse. Server Sizing Guidelines Varian System Database Server Data Warehouse Server Platform & File Server Installed Software & OS Services MS SQL 2014 MS SQL 2014, SSRS (SQL Server Reporting Services) Operating System CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) / 30 ARIA MO Users / 6 Eclipse Users - Up to 4 Linacs (60 ARIA RO Users) / 60 ARIA MO Users / 12 Eclipse Users - Up to 6 Linacs (90 ARIA RO Users) / 90 ARIA MO Users / 18 Eclipse Users - Up to 8 Linacs (120 ARIA RO Users) / 120 ARIA MO Users / 24 Eclipse Users Data Storage Growth Storage Partitioning 4 -System Partition (C:) IIS (Varian WebServices), Shared Framework Services, File Services (CIFS), DICOM Services ( File, DB & IT (1 per Accelerator)) & DCF Core Service (if Eclipse included) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. 5 cores / 8 GB 8 cores / 16 GB 10 cores / 24 GB 10 cores / 16 GB 8 cores / 32 GB 14 cores / 34 GB 15 cores / 24 GB 12 cores / 32 GB 19 cores / 46 GB 20 cores / 32 GB 16 cores / 64 GB 1 24 cores / 58 GB ~15 GB/year/linear accelerator or Medical Oncologist 2 ~13 GB/year/linear accelerator ~100 GB for System & Installation Files ~50 GB/year/linear Accelerator or Medical Oncologist 3 - Data Partition (D:) 100 GB DB + Log 150 GB DB + Log Files ~300 GB-file data + Configuration & Log - Dump Partition (E:) ~75 GB Temp + Dump Files 150 GB Temp + Dump File N/A Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes are estimates for a single linear accelerator or Medical Oncologist for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). DCF Core needs access to data called 'beam data'. This data does not vary frequently, the size of data can vary depending on the number of versions kept, number & types of beams etc. a rough estimate would be ~3 GB per accelerator. While the partition this data is stored on must be available to the OS at the time DCF Core is installed it can reside on a network partition provided the access speed is sufficient. Page 34

36 ADDITIONAL SERVER REQUIREMENTS IEM Interface Server IEM is a product for exchange of data between Varian's software and 3rd party systems using the HL7 protocol (commonly referred to as an HL7 interface engine or software). Varian is currently in the process of replacing the IEM interface engine with ARIA Connect but both products are actively supported at this time and can be deployed on the same server provided sufficient resources are provisioned for the workload they perform, as noted in the introduction please see the appropriate document for ARIA Connect technical specifications. Customers are strongly advised to transition to using ARIA Connect as the interface types become available. The following are the technical specifications for supporting IEM v15.1. IEM Service System Guidelines Specification Software Operating System Hardware Guidelines Interface Exchange Manager Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. Minimum recommended of 4 cores. 16 GB RAM Minimum recommended Minimum of 30 GB free disk space for software installation. Minimum of 100 Mbps NIC, 1 Gbps highly recommended. Storage Storage Partitioning The amount of CPU and RAM assigned to an IEM 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 in to production and adjust the amount of CPU and RAM as needed. Sufficient temporary free space for message processing. Specifically ~300 GB of free space if supporting document &/or faxing exchange Varian recommends the following storage partition scheme: System Partition ("C: Drive") ~80 GB for System & Installation Files ~10 GB for logging Temp Partition ("D Drive") ~300 GB if supporting documents in/outbound or faxing interfaace Network Interface 100 Mb/s minimum bandwidth, 1 Gb/s recommended Page 35

37 Citrix XenApp Server The following are the recommended specifications for deployment of the Eclipse, ARIA OIS for RO, ARIA OIS for MO and ARIA RTM client software on Citrix XenApp application servers. XenApp Server System Guidelines Specification Software Citrix XenApp 6.5 (64-bit) -> ARIA OIS for RO, ARIA RTM, Eclipse 1 Operating System CPU and RAM Citrix XenApp 7.6 LTSR (64-bit) ARIA OIS for MO, ARIA OIS for RO, ARIA RTM, Eclipse Microsoft Windows 2008 R2 SP1 (Standard or Enterprise) with Citrix XenApp 6.5 or Microsoft Windows Server 2012 R2 (Standard or Datacenter) with Citrix XenApp 7.6 LTSR (Long Term Service Release) 2. The following guidelines are recommended specifications. Actual hardware configurations required will vary depending on user load and Varian applications deployed. 4 Cores & 16 GB RAM recommended supports the following user counts: Per 15 users of ARIA OIS for RO with ARIA RTM Per 15 users of ARIA OIS for MO 6 Cores (2.5 GHz or better) & 24 GB RAM recommended supports the following user counts: Per 3 users of Eclipse The above user counts are for the identified applications when published to run on separate XenApp servers. The applications can be published to run on the same XenApp server but the amount of resources assigned to the XenApp server should be adjusted for the number of users expected of the given applications desired to run on the server. For example, to support 15 ARIA OIS for RO and 15 ARIA OIS for MO users on the same XenApp Server concurrently the server would require a minimum of 8 cores and 32 GB of RAM. Storage Partitioning Customers should regularly monitor resource utilization of Citrix XenApp servers and adjust available resources or number of servers in a farm to meet their actual workload. Varian recommends the following storage partition scheme: System Partition ("C: Drive")- System & Installation files - ~100 GB Network Interface 100 Mb/s minimum bandwidth, 1 Gb/s recommended Maximum of 20 ms latency between client & Citrix XenApp server to maintain good interactive performance. o This applies to Eclipse Contouring Applications Maximum of 50 ms latency for all other operations not using Eclipse Contouring Applications Video Card Customers may want to consider using a Video Card to reduce lag (allow increased network latency ~20ms) or plan for their introduction by using 2U servers that would better be able to support the ability to use video cards in the future. Customers using hardware virtualization are guided towards the NVIDIA M10 (or related family) or equivalent Video Cards must meet the proper OpenGL & DirectX compatibility for the client software Page 36

38 1 NOTE: ARIA OIS for MO v15.1 & higher client software no longer supports running on Windows Server 2008 R2 SP1 and is therefore no longer supported on Citrix XenApp 6.5 or below. 2 With XenApp 7.6 Citrix introduced the concept of a Long Term Service Release (LTSR) intended to be stable with respect to features against which only bug fixes and security updates are applied. Varian validates our software only against this branch of Citrix XenApp; customers using a different branch are advised that Varian can provide no advice as to the proper operation of our software on such a branch and has no intention of validating against other than the LTSR branch. Page 37

39 HARRP Servers Varian's High Availability and Rapid Recovery Protection (HARRP) solution is powered by Vision Solutions Double-Take Software and is designed to protect your clinical data and allow customers to rapidly resume clinical operations in the event of a server hardware failure. HARRP provides continuous data protection and ensures minimal data loss and rapid recovery from primary system outage or disaster recovery by replicating changes in data and configuration from a 'source' (or production) server to the 'HARRP' or 'target' server. HARRP is intended to support customers using pure physical deployments. The following are the technical specifications for supporting the deployment of HARRP. HARRP Server System Guidelines Specification Software DoubleTake software & licenses supplied by Varian o DoubleTake v7.1 has been validated with v15.x of Varian software on Windows Server 2012 R2 or Windows Server 2016 Standard. o Varian does not currently supply a HARRP product to be used with Windows Server 2012 Datacenter Edtions Operating System Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard Only) Both the 'source' and 'target' servers must be running the same edition and version of the Operating System. CPU and RAM The HARRP target server hardware must meet the same hardware requirements as the production source server hardware that the HARRP solution is deployed to protect in order to maintain the same performance. Storage Since the HARRP solution performs bit-level replication of the data of the production servers being protected, the data storage requirements for the HARRP failover servers must be maintained at the same level as the production servers. Storage Partitioning The partitioning scheme of storage for HARRP target servers must match the partition scheme of the source (production) server that the HARRP target server has been deployed to support. Network Interface 100 Mb/s minimum bandwidth, 1 Gb/s recommended Page 38

40 APPENDIX A PURE PHYSICAL DEPLOYMENT FOR EXISTING CUSTOMERS The following section is provided only for ease of reference for existing customers of Eclipse (Eclipse only, ARIA & Eclipse or CCS with Eclipse) where the DCF Core Service is deployed on a FAS to help determine if any existing combo server will meet the requirements for this release. If the existing combo server does not meet the recommendations provided here that does not mean the server has to be replaced as opposed to providing a second smaller server to run some of the services (the 'DICOM Services' are a good candidate); however if you do intend to entirely replace the combo server (either due to age or other factors) customers should use the recommendations supplied above to allow for supporting the DICOM Services and DCF Core on a single pure physical combo server. For reference purposes the deployment model discussed here is show in Figure 4 Figure 4: Combo Server with DCF Core on FAS or Workstation Page 39

41 ECLIPSE ONLY Combo Server (without DCF Core) Combo Server Installed Software & OS Services Operating System Varian System Database (MS SQL 2014), IIS (Varian WebServices), Shared Framework Services, File Services (CIFS), DICOM Services (File & DB Services) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. CPU/RAM (cores/gb) - Up to 2 Linacs / 6 Eclipse Users 6 cores / 22 GB - Up to 4 Linacs / 12 Eclipse Users 9 cores / 30 GB - Up to 6 Linacs / 18 Eclipse Users 13 cores / 44 GB - Up to 8 Linacs / 24 Users 17 cores / 54 GB Data Storage Growth ~15 GB/year/linear accelerator 1 Storage Partitioning 3 ~ 50 GB/year/linear Accelerator 2 -System Partition (C:) ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log - Dump Partition (E:) ~75 GB Temp + Dump Files - File Partition (F:) ~300 GB-file data + Configuration & Log Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 2 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 3 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). Page 40

42 ARIA FOR RADIATION ONCOLOGY & ECLIPSE Combo Server (without DCF Core) Installed Software & OS Services Operating System CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) / 6 Eclipse Users - Up to 4 Linacs (60 ARIA RO Users) / 12 Eclipse Users - Up to 6 Linacs (90 ARIA RO Users) / 18 Eclipse Users - Up to 8 Linacs (120 ARIA RO Users) / 24 Eclipse Users Combo Server Data Warehouse Server Varian System Database (MS SQL 2014), IIS (Varian MS SQL 2014, SSRS (SQL Server Reporting Services) WebServices), Shared Framework Services File Services (CIFS), DICOM Services (File, DB and IT Services (1 per Accelerator)) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. Data Storage Growth ~15 GB/year/linear accelerator 2 Storage Partitioning 4 12 cores / 28 GB 8 cores / 16 GB 19 cores / 44 GB 8 cores / 32 GB 27 cores / 62 GB 12 cores / 32 GB 35 cores / 80 GB 16 cores / 64 GB 1 ~ 50 GB/year/linear Accelerator 3 ~13 GB/year/linear accelerator -System Partition (C:) ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log 150 GB DB + Log Files - Dump Partition (E:) ~75 GB Temp + Dump Files 150 GB Temp + Dump File - File Partition (F:) ~300 GB-file data + Configuration & Log NA Storage Speed Network Interface Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). Page 41

43 ARIA COMPREHENSIVE CANCER SOLUTION (CCS) Combo Server (without DCF Core) Combo Server Data Warehouse Server Installed Software & OS Services Operating System Varian System Database (MS SQL 2014), IIS (Varian WebServices), Shared Framework Services, File Services (CIFS), DICOM Services (File, DB & IT Services (1 per Accelerator) MS SQL 2014, SSRS (SQL Server Reporting Services) Microsoft Windows Server 2012 R2 or Windows Server 2016 (Standard or Datacenter) 64 bit only. CPU/RAM (cores/gb) - Up to 2 Linacs (30 ARIA RO Users) / 30 ARIA MO Users / 6 Eclipse Users - Up to 4 Linacs (60 ARIA RO Users) / 60 ARIA MO Users / 12 Eclipse Users - Up to 6 Linacs (90 ARIA RO Users) / 90 ARIA MO Users / 18 Eclipse Users - Up to 8 Linacs (120 ARIA RO Users) / 120 ARIA MO Users) / 24 Eclipse Users 13 cores / 28 GB 8 cores / 16 GB 21 cores / 44 GB 8 cores / 32 GB 30 cores / 62 GB 12 cores / 32 GB 39 cores / 80 GB 16 cores / 64 GB 1 Data Storage Growth ~15 GB/year/linear accelerator or Medical Oncologist 2 Storage Partitioning 4 ~ 50 GB/year/linear accelerator or Medical Oncologist 3 ~13 GB/year/linear accelerator -System Partition (C:) ~100 GB for System & Installation Files - Data Partition (D:) 100 GB DB + Log 150 GB DB + Log Files - Dump Partition (E:) ~75 GB Temp + Dump Files 150 GB Temp + Dump File - File Partition (F:) ~300 GB-file data + Configuration & Log N/A Storage Speed Equivalent to Direct Attached Storage with 6ms Access Time and storage bandwidth of 3 Gbps Network Interface 100 Mb/s minimum bandwidth, 1 Gb/s recommended 1 Analytics (reporting and visualizations if using InSightive) can consume significant RAM resources depending on the nature of the report (reports summarizing data across multiple DB tables or across long time periods for time based analytics). Customers designing their own reports are encouraged to monitor the Data Warehouse server when publishing new reports and adjust resources as necessary to meet desired performance. 2 Database storage growth depends on many factors including but not limited to # of patients per day being treated. Customers are advised to monitor their data storage growth to ensure sufficient free space is always available. The data storage growth estimate is split as ~10 GB for the DB itself & ~5 GB for the Temp & Dump files. 3 File based data storage growth can depend on many factors including but not limited to the # of patients per day being treated, the number and type of imaging events performed and the number and type of electronic documents imported. Customers are encouraged to monitor their data storage growth and adjust accordingly to ensure sufficient free space is available. 4 The data partition sizes are estimates for a single linear accelerator for approximately 5 years of use, total partition sizes should be adjusted as necessary to accommodate a specific customer's needs as well as if placement of other data on this same partition may occur (TrueBeam log files or other file storage even temporary). Page 42

44 APPENDIX B: SERVICE APPLICATION DESCRIPTION Figure 5 is a conceptual view of the deployment of Varian's 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 3 rd party systems) and the Varian server software and is provided to help facilitate further description of the Varian and 3 rd party server software below. Figure 5: Varian Software Conceptual View Table 2 below provides a description of the Varian (and Operating System) services depicted in Figure 5including the naming convention/terms introduced by the figure as well as identifying some 'workload' considerations that impact the computer resources allocated to them. Note that the services used by any given customer will depend on the purchased Varian software applications and support modules. Table 2: Service Applications Name Function Services Product/Feature Purchased Varian System Database Page 43 Production Database MS SQL ARIA RO, ARIA RTM, ARIA MO, Eclipse Considerations: The Varian System Database is the workhorse for daily work done by 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.