B IG H AN D CO R E PR O D U CT TE CH N ICAL R E Q U IR E ME N TS

BIGHAND ENTERPRISE
Software version: 4.2 Last edited date: 26 October 2011

Contents

Contents
Contents BigHand Core Topology
Introduction Centralised Computing Environment Distributed Hybrid

2 3
3 4 5 6

Core Components
BigHand Database BigHand Workflow Server Filestore(s) BigHand Services Host BigHand External Workflow Server Active Directory Users & Computers BigHand Active Directory Services BigHand System Administration BigHand Windows Client BigHand Standalone Terminal server (Citrix) Terminal Server (Windows) Thin client (PC) Thin client (Terminal)

7
8 9 10 11 12 13 14 15 16 17 18 19 20 21

BigHand Core Topology

BigHand Core Topology

Introduction
BigHand is a future-proof technology which can be implemented in a variety of ways, allowing the application to remain flexible to your organisation's requirements. The implementation scenarios are: 1) Centralised 2) Distributed 3) Hybrid Components can be installed on the same physical / virtual server or on separate servers with the exception of BigHand Telephony and Speech Recognition.

Centralised Computing Environment

BigHand can be implemented in a centralised environment where all server components are located in a main site or data centre while client connections are made over the LAN/WAN.

The above diagram represents an implementation based on centralised server side components. The main server hosts the global master database, which stores all voice file metadata. The voice files are not stored in the database - to ensure optimum database performance - but in a separate filestore. All the server side software is hosted in the main site, with clients connecting to the server(s) via LAN, WAN and VPN.

Distributed
BigHand can be implemented in a distributed environment where BigHand services and filestores are installed in each geographic site to support the users within each location.

The above diagram represents an implementation based on more autonomous offices, having their own server side components. The master database is still located in the main site, but each site hosts its own BigHand services and filestore. The BigHand services in each site refers to the master database to store and retrieve voice file metadata. The servers store files locally to reduce WAN traffic, but the central database keeps track of where all the systems files are located, allowing work to be shared. This model lends itself to sites with greater autonomy, and assumes that a large share of the voice file created in a site will be transcribed in the same site. The majority of this models WAN traffic is metadata, and most file transfer is confined to the site LANs.

Hybrid
Alternatively BigHand can be implemented in a hybrid environment where you have a mix of both centralised and distributed, with large remote sites being supported by their own BigHand services and filestores whilst smaller satellite sites/offices connect to BigHand using Terminal Server (Citrix/Terminal Services).

Users connect to their local server through LAN, WAN, VPN or Terminal Server, making use of potentially better network links within the regions. This limits the amount of bandwidth used by BigHand on network links, assuming voice files rarely move between regions.

Core Components

Core Components
BigHand is based on three-tier, service-oriented architecture with the following core components:
l l l l l l l l l

BigHand Database BigHand Workflow Server BigHand Filestore BigHand Services Host BigHand External Workflow Server BigHand System Administration BigHand Windows Client Terminal Server Terminal Client

The technical requirements for each core component is detailed in the following sections.

Core Components

BigHand Database
Description: Component of: The BigHand database stores records of all the voice files submitted to BigHand, such as the author, workflow destination and user data, as well as the system configuration. BigHand core

Connects to: None Target of: Processor: Memory (RAM): BigHand Server, BigHand Services Minimum: Pentium IV Recommended: Dual Xeon 3.6GHz 800MHz FSB or higher Minimum: 1 GB Recommended: 2 GB

Storage Minimum: 1 GB requirement: Recommended: 4 GB Operating System*: .NET Framework: Connection info: Minimum: Windows Server 2003 Recommended: Windows Server 2008, Windows Server 2008 R2 (64-bit versions supported) Not required TCP/IP Ethernet. Recommended: 1 Gbps

Co-exist with other Yes services Minimum database platform: MSDE 2000 or MSSQL Server Express Edition with latest service patches. Recommended database platform: MSSQL Server 2005 or MSSQL Server 2008 with latest service packs. Other information: * BigHand recommends that the latest relevant Service Packs and Windows Updates are installed on the Operating System before installing this component. Recommended: 10/100/1000 Mbps Network DTC must be enabled on the database server. Memory is dependent on the size of the database.

Core Components

BigHand Workflow Server

Description: Component of: A Windows service that manages file transfer and database updates on behalf of the applications that it serves. BigHand core

Connects to: Database, filestore(s). Target of: Processor: Memory (RAM): BigHand Windows Client, Telephony, Outsourcing module. Minimum: Pentium IV Recommended: Dual Xeon 3.6GHz 800MHz FSB or higher Minimum: 1 GB Recommended: 2 GB

Storage Minimum: 200 MB* requirement: Operating System: Minimum: Windows Server 2003 Recommended: Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2 (64-bit versions supported)

.NET Minimum: .NET Framework version 2.0. Framework: Connection info: TCP/IP Ethernet. Client TCPport range 5114-5118, connects to SQLServer on TCP1433. Recommended Ethernet connection speed: 1 Gbps * For application purposes (see filestore for storage requirements)
BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component. Other information: In a distributed environment, it requires a service account that is a db_owner of the BigHand database, and has read/write/delete permissions to the filestore(s). Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

Core Components

Filestore(s)
The BigHand system uses one or more filestores to keep voice files. Often the filestores are co-located with BigHand Server services. The filestores must be accessible, for read Description: / write / delete operations, by all BigHand Server services and all BigHand Services Host services, to enable multi-site work sharing. Component of: BigHand core

Connects to: None Target of: Processor: Memory (RAM): BigHand Server services, BigHand Services N/A N/A

Storage Approx 1.4 MB per 10 minutes of recording requirement: Operating System: N/A

.NET N/A Framework: Connection info: TCP/IP Must be shared with the service accounts that run BigHand Server and BigHand Services. Other information: Storage requirement (MB) = 7 x 0.14 x number of users x avg. recording duration per user per day (minutes) (Approx. 0.14 MB per minute - with GSM codec) (7 days default time to store completed voice files)

10

Core Components

BigHand Services Host

Description: Component of: Connects to: Target of: Processor: Memory (RAM): Storage requirement: Operating System: .NET Framework: Connection info: A Windows service that hosts a collection of WCFweb services enabling communication between BigHand software components and the BigHand database. BigHand core Database, filestore(s) System Administration, BigHand Windows Client, Web Client, BigHand Active Directory Services, BigHand Gateway, External Workflow Server, Security Faade As for BigHand Server service As for BigHand Server service As for BigHand Server service Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64 bit versions supported)* .NET Framework version 3.5 WCFweb services, file system access, MSDTC

Co-exist with Yes other services * BigHand recommends that the latest relevant Service Packs and Windows Updates are installed on the operating system before installing this component. Network DTC (Distributed Transaction Co-ordinator) must be enabled. The BigHand database host server must also have network DTC enabled. Other information: The device drivers for the portables must be installed to convert web submissions to BigHand format (if web submission is required). Requires a service account that is a db_owner of the BigHand database. This account must have read/write/delete permissions to the BigHand filestore(s). Minimum specification may increase if other applications outside of BigHand are also running on the same machine. The windows service 'Port Sharing' must be enabled and started.

11

Core Components

BigHand External Workflow Server

This Windows service checks for voice files that users have sent to Speech Recognition. The service monitors the database to provide email notifications to users and escalate workflows. The service also monitors directories for Grundig LAN Docking files and files for the automatic import of data for practice builder and profiling. Speech Recognition, Email Notifications, Session Import (Profiling and Practice Builder), Grundig LAN Docking, Workflow Escalation

Description

Component of:

Connects to: BigHand Services Host and BigHand Transcription Server. Target of: Processor: Memory (RAM): Transcription Server* As for BigHand Services As for BigHand Services

Storage As for BigHand Services requirement: Operating System: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64 bit versions supported)

.NET .NET Framework version 3.0 Framework: Connection info: Co-exist with other services WCF

Yes * The service independently polls the BigHand database, taking action as necessary. It is not explicitly the target of any component other than the Transcription Server, which notifies ExternalWorkflow Server when a transcription is complete.
BigHand recommends that the latest relevant Service Packs and Windows Updates

Other information:

are installed on the Operating System before installing this component. Minimum specification may increase if other applications outside of BigHand are also running on the same machine. This component may need to be located on a separate server if there is a high usage of Speech Recognition. This is because of the additional processor requirements for conversion of the audio files.

12

Core Components

Active Directory Users & Computers

When BigHand is integrated with Active Directory, user management is performed in Description: Active Directory, and is disabled in BigHand. Users are authenticated in BigHand by virtue of their Windows authentication (Single sign-on). Component of: Windows Server operating system

Connects to: Active Directory Target of: Processor: Memory (RAM): BigHand Active Directory Services N/A* N/A

Storage N/A requirement: Operating System: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64 bit versions supported)

.NET N/A Framework: Connection info: Other information: Ethernet * The specification of your domain controller(s) is beyond the scope of this document. A dedicated security group must be set up for BigHand users. This group may contain nested groups. Some BigHand components must run under Windows 'service accounts'. These accounts are created and authorised in Active Directory.

13

Core Components

BigHand Active Directory Services

BigHand Active Directory Services synchronises BigHand with Active Directory to Description: simplify user management and provide 'single sign on' for users (Windows authentication) . Component of: BigHand core

Connects to: BigHand Services Host Target of: Processor: Memory (RAM): BigHand System Administration N/A* N/A*

Storage N/A requirement: Operating System: N/A*

.NET N/A* Framework: Connection info: Co-exist with other services TCP/IP

Yes * This component should reside on the BigHand Services Host server. If the Directory Service will synchronise users from multiple domains, the BigHand Directory Services should be installed on a BigHand Services Host in each domain. You will need to set up trust relationships. Requires a service account if you do not co-locate this service with the BigHand Services Host.

Other information:

14

Core Components

BigHand System Administration

Description: A client application for carrying out BigHand system administration tasks. Component of: BigHand core

Connects to: BigHand Services Host Target of: Processor: Memory (RAM): User As per operating system As per operating system

Storage Minimum: 100 MB; Recommended: 200 MB requirement: Operating System: Windows XP (SP2), Windows Vista, or Windows 7 (64-bit versions supported)

.NET .NET Framework version 3.0 Framework: Connection info: Other information: Web services connections (WCF)
BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component.

15

Core Components

BigHand Windows Client

Description: Component of: The BigHand Windows Client is most commonly used for creating and transcribing BigHand voice files on the user's PC. BigHand core

Connects to: BigHand Server, BigHand Services Target of: Processor: Memory (RAM): User Minimum: Pentium IV; Recommended: Core 2 duo Minimum: As per operating system requirements

Storage Minimum: 100 MB; Recommended: 200 MB requirement: Operating System: Windows XP, Windows Vista, or Windows 7 (64-bit versions supported)

.NET Minimum: .NET Framework version 3.0 Framework: Connection info: TCP/IP. Minimum 128 kbps for VPN. MSI installer version 4.5 on client machines and any terminal servers that will serve the BigHand Windows Client. * .NET Framework version 3.0 is the minimum requirement. Soundcard required if using analogue / serial (non-USB) devices. Powered USB port required for USB microphone or portable recording device. Other information: Additional requirements for Speech Recognition support: Windows XP with SP2 (or later OS) Microsoft Word 2003, 2007, 2010, 2010x64 Additional requirements for Word Playback Tools: Dragon Correction Object Additional requirements for Client Side Speech Recognition: Dragon NaturallySpeaking SDK Client Edition Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

16

Core Components

BigHand Standalone
This module is installed by default with the BigHand Windows Client. A client-side Description: module that simply records or plays voice files. Provides business continuity if the BigHand database or server components are unavailable for an extended period. Component of: BigHand core

Connects to: N/A Target of: Processor: Memory (RAM): User As for BigHand Windows Client As for BigHand Windows Client

Storage As for BigHand Windows Client requirement: Operating System: As for BigHand Windows Client

.NET .NET Framework version 3.0 Framework: Connection info: N/A* * This application does not require a network connection; however, you may wish to transport voice files by email or to a network share. The application shares components with the BigHand Windows Client and must therefore be installed alongside the BigHand Windows Client. BigHand Standalone is installed with the client, by default, but you can choose not to install it. Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

Other information:

17

Core Components

Terminal server (Citrix)

Description: Component of: The BigHand Windows client application runs on the Citrix terminal server. The client is installed on the server and ICA plug-in users connect to the terminal server. Optional module

Connects to: BigHand Server, BigHand Services Target of: Processor: Memory (RAM): BigHand thin client plug-in Depends on shared application environment Depends on shared application environment

Storage Depends on shared application environment requirement: Operating System: Minimum: MetaFrame Presentation Server 4.0 Recommended: XenApp 5 (32-bit)

.NET Minimum: .NET Framework version 3.0 Framework: Connection info: ICA Recommended additional bandwidth per active user = 40 kbps (with optimisations off). Note: With optimisations on the bandwidth is reduced. Additional bandwidth will be required for multiple users or if other applications outside of BigHand are also being used on the Citrix or Terminal Server. Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

Other information:

18

Core Components

Terminal Server (Windows)

Description: Component of: The BigHand client application runs on the Windows terminal server. The client is installed on the terminal server and plug-in users connect to the terminal server. Optional module

Connects to: BigHand Server, BigHand Services Target of: Processor: Memory (RAM): BigHand thin client plug-in Depends on shared application environment Depends on shared application environment

Storage Depends on shared application environment requirement: Operating System: Recommended: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64-bit versions supported)

.NET Minimum: .NET Framework version 3.0 Framework: Connection info: RDP Recommended additional bandwidth per active user = 60 kbps (with optimisations off). Note: With optimisations on the bandwidth required is reduced. Additional bandwidth will be required for multiple users or if other applications outside of BigHand are also being used on the Citrix or Terminal Server. Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

Other information:

19

Core Components

Thin client (PC)

In a centralised computing environment, BigHand can run on PCs acting as Citrix or Description: Windows thin client terminals. The BigHand plug-in works via either protocol (ICA / RDP). Component of: Optional module

Connects to: Terminal server Target of: Processor: Memory (RAM): User Minimum: Pentium IV; Recommended: Core 2 duo Minimum: 128 MB; Recommended: 256 MB

Storage Minimum: 5 MB; Recommended: 10 MB requirement: Operating System: Windows XP, Windows Vista, Windows 7 (64 bit versions supported*)

.NET .NET Framework version 2.0 Framework: Connection info: ICA / RDP USB, or RS232 serial port required for hardware connection (Analogue sound card required if using serial port device) Connection speed minimum: 128 kbps; recommended: 128 kbps or more Internet Explorer 6 or later. RDP5 or ICA32 Version 6.01 or above or ICAWEB version 6.3 or above required. * 64-bit Windows Vista is not supported as a terminal services client.
.NET Framework version 2.0 is the minimum requirement.

Other information:

Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

20

Core Components

Thin client (Terminal)

Description: Component of: In a centralised computing environment, BigHand can run on Citrix or Windows thin client terminals. The BigHand plug-in works via either protocol (ICA / RDP). Optional module

Connects to: Citrix server or Windows Terminal Server Target of: Processor: Memory (RAM): User Requirement as for Windows 7 Embedded*. (Flash memory) Minimum: 128 MB Recommended: 256 MB

Storage Minimum: 5 MB requirement: Recommended: 10 MB Operating System: Windows XP Embedded with SP2 Windows 7 Embedded

.NET .NET Framework version 2.0 Framework: Connection info: ICA or RDP * If using portable recorders (and DeviceSync) with terminals, BigHand recommends at least a 1 GHz processor because the processing power of the terminal affects DeviceSync speed. USB, or RS232 serial port required for hardware connection (Analogue sound card required if using serial port device) Other information: Connection speed minimum: 56 kbps; recommended: 128 kbps or more Internet Explorer 6 or later. RDP5 or ICA32 Version 6.01 or above or ICAWEB version 6.3 or above required.
.NET Framework version 2.0 is the minimum requirement.

Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

21