One Virtual Source

Technical Architecture

June, 2019
 Infrastructure – OVS Web
IT Architecture – OVS Web – Minimum Requirements Considerations
❑ Server App and Database can be hosted in
Client Environment
different servers.

Server
Web
OVS
Database 1Database 2 ❑ Databases can be in any reachable location:
cloud, data farm, regular servers, etc.
ovs.company.net
Real-Time WKF’s Output User/Engineer
Mix of SQL Server, Oracle,
❑ Multiple AD Groups can be configured to

configuration
Read project
Real-Time and other
protocols (cloud based
support) define different roles in the OVS Project, e.g.,
For Single Logon
Administrators, Managers, Production
Engineers, Reservoir Engineers, showing in
User/Engineer
context different content of the dashboards.
Read project
configuration

OVS OVS Project

Surveillance Database
(SQL Server)
Additional Considerations for Web Server
Server User/Engineer
(Will run the
unattended ❑ Minimum of 16 GB RAM.
Processes
and SBE)
❑ 4+ Processors.

❑ OVS Project Database only contains configuration information. No client

❑ Locate the Web Server close to the Project
User/Engineer
data is stored. Database.
❑ Workflow Outputs database will store workflow’s results that are not
currently supported in any other database.
❑ Active Directory integration is available to provide a single sign-on
❑ CPUs should be scalable according to
experience and provide entitlements to the company’s databases. concurrent users.

❑ IIS w/ URL Rewrite module

 Infrastructure – Security Considerations
IT Architecture – Local Web server Security Considerations
❑ Single Sign-on (SSO) from Web Client to Web
Location 1 – Centralized Windows Server ( Regional )
dbs Services using Windows Authentication
DB 1 DB 2

ovs-asset..net ❑ Connectivity to source databases using

DB 3
functional accounts running with Windows
Location 2 - Asset
Impersonation, or database credentials.
Functional accounts preferred.
Real-Time

Users
(Asset)

Additional Considerations for System Administration

❑ IE11 mode – company policies may render
Read project intranet sites in compatibility mode by default.
configuration
As OvsWeb client requires sites to be rendered
OVS OVS Project
Surveillance Database
in IE11 mode, whitelisting may be required.
Server
❑ SSO requires permission for automatic logon
in Intranet Zone
 OVS Web Hardware Requirements

Minimum Requirements
OVS Group recommends 3 environments to be configured for projects, DEV, TEST, and PROD. Minimum specs for each environment are as given below.
Note that DEV and TEST environments may be configured on a single machine or VM. PROD environments should be allocated their own independent machine or VM
resources.
Installation Scenario Deployment type Operating RAM Processor Hard disk space Additional Server
and scale System Software

Single server with a 1 – 50 users Windows 8GB+ 64-bit, 4 80 GB for system IIS w/ URL Rewrite
built-in or external Server 2012+ 16GB+ cores drive module
SQL Server database recommende
d

Software Architecture
Each individual OvsWeb instance will require:
❑ Ovs Web Services - a web application, running on IIS. Requires own app pool
❑ Ovs Web Client – ordinary web site. HTML5 single page application (SPA). Requires
IE11, Edge or Chrome. Chrome or Edge recommended for best experience.
❑ Project Database – SQL Server project database
❑ An architecture diagram is shown on the right.

Additional considerations
❑ IE11 mode – company policies may render intranet sites in compatibility mode by
default. As OvsWeb client requires sites to be rendered in IE11 mode, whitelisting
may be required.
❑ Windows Authentication & Impersonation – in order to support Windows
Authentication across the system, functional or service accounts should be
provisioned with access to source databases