B IG H AN D F U L L TE CH N ICAL R E Q U IR E ME N TS

Software version: BigHand 4.2 Last edited date: 10 November 2011

Contents

Contents
Contents BigHand Core Product Technical Requirements BigHand Core Topology
Introduction 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)

2 4 5
5 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

BigHand for Smartphones Technical Requirements

BigHand for Smartphones Topology

24
25

BigHand for BlackBerry

BigHand for BlackBerry BlackBerry Enterprise Server BlackBerry Gateway

26
26 26 27

BigHand Gateway BigHand for iPhone

BigHand for iPhone Mobile Gateway

28 29
29 30

BigHand for Android

BigHand for Android Mobile Gateway

31
31 32

BigHand for Windows Mobile

BigHand for Windows Mobile Security Faade

33
34 35

BigHand Mobility Technical Requirements

Introduction BigHand Mobility Topology

36
37 38

BigHand Email Gateway

BigHand Email Gateway (COM+) BigHand Email Exchange Service (Exchange Web Services)

39
41 42

BigHand Gateway BigHand Telephony

43 44

Contents

BigHand Web Client BigHand Reporting Module Technical Requirements

Introduction BigHand Analytics BigHand Reporting Suite

45 46
47 48 49

BigHand Speech Recognition Technical Requirements Introduction to Server Side Speech Recognition
Dragon NaturallySpeaking SDK Server BigHand Transcription Server BigHand Speech Recognition Pre-learning Utility

50 51
52 53 54

Introduction to Client Side Speech Recognition

Dragon NaturallySpeaking SDK client edition

55
56

BigHand Integrations Module Technical Requirements

Introduction BigHand Integration with iManage

57
58 59

BigHand Outsourcing Module Technical Requirements

Introduction Outsourcing Module Agency Access

60
61 62 63

BigHand SDK Technical Requirements

BigHand Client SDK System Admin. SDK

64
65 66

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 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
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.

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.

10

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.

11

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)

12

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.

13

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.

14

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.

15

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:

16

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.

17

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.

18

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:

19

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 2.0 and 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:

20

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 2.0 and 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:

21

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.

22

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.

23

B IG H AN D F O R SMAR TPH O N E S TE CH N ICAL R E Q U IR E ME N TS

BigHand for Smartphones Technical Requirements

BigHand for Smartphones Topology

The architecture below summarises the server side and additional components required for BlackBerry, iPhone, Windows Mobile and Android.

25

BigHand for BlackBerry

BigHand for BlackBerry

BigHand for BlackBerry smartphones allows authors to record, edit, track and send their voice files seamlessly to the BigHand system and requires the following components:
l l l l

BigHand for BlackBerry client software BlackBerry Enterprise Server BigHand Mobile Gateway BigHand Gateway

BigHand for BlackBerry

Description: The BigHand client software for BlackBerry smartphones. Component of: Mobility Suite

Connects to: BlackBerry Gateway via BES or BIS Target of: Processor: Memory (RAM): User N/A N/A

Storage 128 / 256 / 512 MB* requirement: Operating System: BlackBerry device OS 4.5, 4.6, 4.7, 5.0, 6.0

.NET N/A Framework: Connection info: Mobile Data Services (MDS) over least cost route (USB, EDGE/GPRS) * The amount of memory on the BlackBerry smartphone affects how much recording can be stored. The storage can be extended using a memory card - BigHand for BlackBerry uses approximately 1 MB for 10 minutes of recording. Supported models: 9800 (Torch), 9780 (Bold), 9700 (Bold), 9550 (Storm), 9500 (Storm), 9360 (Tour), 9000 (Bold), 8900 (Javelin), 8820, 8800 Series, 8520 (Curve), 8300 (Curve), 8320 (Curve), 8100 (Pearl)

Other information:

BlackBerry Enterprise Server

The BlackBerry Enterprise Server (BES) is installed and running (BES v4.0 or later). You will need permission to create a software configuration policy on the BES if you are going to deploy BigHand BigHand for BlackBerry Blackberry Enterprise Server Express can be installed instead of Blackberry Enterprise Server which can support up to 2000+ with dedicated server(s) or 75 on the primary mail server.

26

BigHand for BlackBerry

BlackBerry Gateway
Description: A BigHand web application which receives voice files from BigHand for BlackBerry. Component of: Mobility Suite

Connects to: BigHand Gateway Target of: Processor: Memory (RAM): BigHand for BlackBerry As required by OS and IIS* As required by OS and IIS*

Storage Approximately 100 MB per user requirement: Operating System: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64-bit versions supported)

.NET .NET Framework version 3.5 Framework: Connection info: Co-exist with other services: HTTP/S

Yes In a BIS environment the BlackBerry Gateway needs to be installed on a public facing internet server (in a DMZ) or to be routable through the firewall to allow secure connections to the BlackBerry smartphones. It may share an IIS server or another similarly isolated server.

Other information:

* This component is installed on an IIS server. IIS versions 6 and 7 are supported. These web servers are installed with Windows Server 2003 and Windows Server 2008 respectively. If using IIS7 IIS6 Management compatibility mode must also be installed.
Based on assumed usage of BigHand Windows Client. This will vary at your

organisation - BigHand uses approximately 1.4 MB for ten minutes of recording.

BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component.

27

BigHand Gateway

BigHand Gateway
Description: Component of: A Windows service that processes voice files sent in by email or smartphone and then submits them to the BigHand core. Mobility Suite - Email Gateway, BigHand for BlackBerry, BigHand for Windows Mobile, BigHand for iPhone and BigHand for Android

Connects to: BigHand Services Host Target of: Processor: Memory (RAM): Email Gateway (COM+), Email Gateway (Exchange Web Services), Mobile Gateway As for BigHand Server service* As for BigHand Server service*

Storage As for BigHand Server service* requirement: Operating System: As for BigHand Server service*

.NET .NET Framework version 3.0 Framework: Connection info: Co-exist with other services: Web services, file system access

Yes * This component may be installed on the BigHand server. If the component is installed on a separate server, the specification of this gateway server should approximately match the BigHand server. Requires a service account can use the BigHand Server account.
Requires either to write to a directory, or upload via file service (recommended).

Other information:

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

28

BigHand for iPhone

BigHand for iPhone

BigHand for iPhone smartphones allows authors to record, edit, track and send their voice files seamlessly to the BigHand system and requires the following components:
l l l

BigHand for iPhone client software BigHand Mobile Gateway BigHand Gateway (refer to BigHand for BlackBerry section)

BigHand for iPhone

Description: The BigHand client software for the iPhone. Component of: Mobility Suite

Connects to: Mobile Gateway* Target of: Processor: Memory (RAM): User Depends on model Depends on model

Storage Approx. 380 kb per minute of recording. requirement: Operating System: iOS 3, iOS 4 or iOS 5

.NET N/A Framework: Connection info: HTTP/S * When using BigHand for iPhone with the BigHand system. This software also has a standalone mode, which does not require any further BigHand software.
BigHand for iPhone has been tested on iPhone 3G, iPhone 3GS, iPhone 4, iPad and

Other information:

iPod Touch (provided that the headphones are connected while recording).

29

BigHand for iPhone

Mobile Gateway
Description: A BigHand web application which receives voice files from BigHand for iPhone. Component of: Mobility Suite

Connects to: BigHand Gateway Target of: Processor: Memory (RAM): BigHand for iPhone As required by OS and IIS* As required by OS and IIS*

Storage Approx. 100 MB per user requirement: Operating System: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64 bit versions supported)

.NET .NET Framework version 3.5 Framework: Connection info: Co-exist with other services: HTTP/S

Yes * This component is installed on an IIS server. IIS versions 6 and 7 are supported. These web servers are installed with Windows Server 2003 and Windows Server 2008 respectively. If you are using IIS7, then IIS6 Management Compatibility Mode must also be installed.

Other information:

Based on assumed usage of BigHand client. This will vary at your organisation

BigHand uses approximately 1.4 MB for ten minutes of recording.

BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component. The official name for this component is the 'BlackBerry Gateway' although it is also used for the iPhone and Android applications.

30

BigHand for Android

BigHand for Android

BigHand for Android smartphones allows authors to record, edit, track and send their voice files seamlessly to the BigHand system and requires the following components:
l l l

BigHand for Android client software BigHand Mobile Gateway BigHand Gateway (refer to BigHand for BlackBerry section)

BigHand for Android

Description: The BigHand client software for the Android smartphone. Component Mobility Suite of: Connects to: Target of: Processor: Memory (RAM): Operating System: Mobile Gateway User Depends on model* Depends on model* Android 2.1; Android 2.2; Android 2.3

.NET N/A Framework: Connection HTTP/S info: * BigHand for Android has been tested on the following devices: HTC Evo, HTC Desire/Incredible HD, HTC Wildfire, Motorola Milestone 2/Droid 2, Samsung Galaxy S, Samsung Galaxy S II

Other information: The screen resolutions which have been tested are: QVGA 240x320; WVGA 480x800, FWVGA 480x854. Please contact your account manager for full details on handset/OS compatibility.

31

BigHand for Android

Mobile Gateway
Description: A BigHand web application which receives voice files from BigHand for Android. Component of: Mobility Suite

Connects to: BigHand Gateway Target of: Processor: Memory (RAM): BigHand for Android As required by OS and IIS* As required by OS and IIS*

Storage Approximately 100 MB per user requirement: Operating System: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64-bit versions supported)

.NET .NET Framework version 3.5 Framework: Connection info: HTTP/S The Mobile Gateway needs to be installed on a public-facing internet server (in a DMZ) or to be routable through the firewall to allow secure connections to the Android smartphone. It may share an IIS server or another similarly isolated server. Other information: * This component is installed on an IIS server. IIS versions 6 and 7 are supported. These web servers are installed with Windows Server 2003 and Windows Server 2008 respectively. If using IIS7 IIS6 Management compatibility mode must also be installed.
Based on assumed usage of BigHand Windows Client. This will vary at your

organisation BigHand uses approximately 1.4 MB for ten minutes of recording.

BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component.

32

BigHand for Windows Mobile

BigHand for Windows Mobile

BigHand for Windows Mobile allows authors to record, edit, track and send their voice files seamlessly to the BigHand system and requires the following components:
l l

BigHand Windows Mobile client software BigHand Email Gateway (see BigHand Email Gateway section in the 'BigHand Mobility Technical Requirements') Microsoft Exchange Server Security Faade BigHand Gateway (refer to BigHand for BlackBerry section)

l l l

33

BigHand for Windows Mobile

BigHand for Windows Mobile

Description: The BigHand client software for devices running the Windows Mobile operating system. Component of: Mobility Suite

Connects to: Email Gateway and Security Faade Target of: Processor: Memory (RAM): User N/A N/A

Storage 128 / 256 / 512 MB* requirement: Operating System: Windows Mobile 5 Pocket PC, Windows Mobile 5 Smartphone, Windows Mobile 6 Standard Edition, Windows Mobile 6 Professional Edition, Windows Mobile 6.1, Windows Mobile 6.5 (version 6 or later recommended)

.NET .NET Compact Framework versions 2.0 and 3.5 Framework: Connection info: HTTP/S over default connection Microsoft SQL Server Compact 3.5 and the NetCFv3.5 Messages .cab must be installed on the smartphone * The amount of memory on the smartphone affects how much recording can be stored. This can be extended using a memory card - BigHand uses approximately 1 MB for 10 minutes of recording. Other information: Tested models: BigHand for Windows Mobile has been tested on HTC: Touch Pro 2, Touch Pro, Touch Cruise, Touch Diamond, S730, S710, TyTN II. Palm: Treo Pro, Treo 750. (HTC devices are often rebranded. Check with BigHand if you are unsure whether your devices are supported.)
The software uses the default transport mechanism selected on the Windows Mobile

OS at the time when the voice file is sent. Includes GPRS, 3G, Wi-Fi. The smartphone must be certified to authenticate itself to the Security Faade. The required certificate is in place with the default install, but you may need to add your own certificates if using a non-BigHand Server Authentication certificate on the Security Faade.

34

BigHand for Windows Mobile

Security Faade
Description: Provides authentication and status updates for BigHand for Windows Mobile. Component of: Mobility Suite

Connects to: BigHand Services Host Target of: Processor: Memory (RAM): BigHand for Windows Mobile As for operating system As for operating system

Storage As for operating system requirement: Operating System: Recommended: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64 bit versions supported)*

.NET .NET Framework version 3.5 Framework: Connection info: HTTPS and net.TCP The Security Faade is designed to run isolated from the BigHand Services Host (in a DMZ) to allow secure connections from Windows Mobile smartphones. It may share an IIS server or another similarly isolated server. Other information: The Security Faade must be certified with a Server Authentication certificate. The certificate name must match the external facing IP address of the Security Faade and the server address configured in BigHand for Windows Mobile. * BigHand recommends that the latest relevant Service Packs and Windows Updates are installed on the Operating System before installing this component.

35

B IG H AN D MO B IL ITY TE CH N ICAL R E Q U IR E ME N TS

BigHand Mobility Technical Requirements

Introduction
The mobility options are as follows:
l l l

BigHand Email Gateway BigHand Web Client BigHand Telephony

Please refer to the BigHand for Smartphone Technical Requirements for device mobility options.

37

BigHand Mobility Topology

The architecture below summarises the server side and additional components required for BigHand Email Gateway, Telephony and Web Client.

38

BigHand Email Gateway

BigHand Email Gateway

The BigHand Email Gateway option enables users who record using a remote device to use a web based or home email account to send voice files into the system (e.g. Hotmail, Gmail or OWA). The BigHand Workflow Server automatically routes the work to the chosen recipient(s) with no manual file saving or email opening required. The subject line, priority and recipient of the email are interpreted by the BigHand Email Gateway and the voice file appears in a transcribers work in progress as normal. Authors can also send voice files in .amr file format using email-capable smartphones. The BigHand Email Gateway requires the following:
l l

BigHand Email Gateway BigHand Gateway

39

BigHand Email Gateway

40

BigHand Email Gateway (COM+)

Description: Component of: A BigHand COM+ component which resides on the Exchange server*, monitoring one or more mailboxes for messages with voice file attachments. Mobility Suite - BigHand Email Gateway

Connects to: BigHand Gateway Target of: Processor: Memory (RAM): BigHand for Windows Mobile and email submissions N/A* N/A*

Storage Negligible requirement: Operating System: Minimum: Windows Server 2003; Recommended: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64-bit versions supported)

.NET .NET Framework version 2.0 Framework: Connection info: N/A * This component is resident on Exchange Server. Exchange Server 2000, 2003 or 2007 (before SP1) required (64 bit versions supported).
Voice files are processed as they arrive at the Exchange Server and are deleted after

Other information:

processing.
BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component. Clustering: Install the BigHand Email Gateway on all physical nodes in an Exchange cluster. Do not install BigHand Email Gateway on virtual nodes.

41

BigHand Email Exchange Service (Exchange Web Services)

Description: Component of: AWindows service that communicates with Microsoft Exchange to extract voice files sent to specific mailboxes and submit those attachments to the BigHand system. Mobility Suite - Email Gateway

Connects to: Microsoft Exchange and BigHand Gateway Target of: Processor: Memory (RAM): None* N/A (as for OS) N/A (as for OS)

Storage Negligible requirement: Operating System: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64-bit versions supported)

.NET .NET Framework version 3.5 Framework: Connection info: Web services calls using Exchange Web Services The service does not need to be hosted adjacent to Exchange Server. Microsoft Exchange 2010 and Microsoft Exchange 2007 SP1 are supported. Autodiscovery must be enabled on the Exchange Server. * The service independently polls the Exchange looking for newly arrived voice file attachments.
The service deletes the messages from the mailboxes on the Exchange Server after

Other information:

processing the attachments. Processing simply involves transferring the files to another BigHand component, the BigHand Gateway.
BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the operating system before installing this component.

42

BigHand Gateway

BigHand Gateway
Description: Component of: A Windows service that processes voice files sent in by email or smartphone and then submits them to the BigHand core. Mobility Suite - Email Gateway, BigHand for BlackBerry, BigHand for Windows Mobile, BigHand for iPhone and BigHand for Android

Connects to: BigHand Services Host Target of: Processor: Memory (RAM): Email Gateway (COM+), Email Gateway (Exchange Web Services), Mobile Gateway As for BigHand Server service* As for BigHand Server service*

Storage As for BigHand Server service* requirement: Operating System: As for BigHand Server service*

.NET .NET Framework version 3.0 Framework: Connection info: Co-exist with other services: Web services, file system access

Yes * This component may be installed on the BigHand server. If the component is installed on a separate server, the specification of this gateway server should approximately match the BigHand server. Requires a service account can use the BigHand Server account.
Requires either to write to a directory, or upload via file service (recommended).

Other information:

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

43

BigHand Telephony

BigHand Telephony
Description: Component of: A Windows service hosted on a telephony server. This module records voice files over the telephone and then submits them to the BigHand Server service. Mobility Suite Telephony

Connects to: BigHand Server Target of: Processor: Memory (RAM): Telephone voice calls Minimum: Pentium IV 1 GB

Storage 10 GB requirement: Operating System: Windows Server 2003*

.NET .NET 3.0 Framework: Connection info: Co-exist with other services: TCP/IP

No see Other information BigHand recommends a dedicated server for this component. The server must have a PCI TAPI telephony card with Global API support. Supported types include Intel Dialogic D4PCIUFEU, D41JCTLS and D120JCT. The target server requires enough physical space to house the PCI telephony card. The 4 port card is a half-length card and the 6 or 12 port cards are full length PCI cards. The server must have a full size PCI slot. Newer servers may only have PCI Express slots, in which case you will need to install and test the telephony card using an adapter. BigHand supports regular 5v or 3.3v PCI slots and PCI-X slots commonly found on server grade machines. PCI-Express slots (aka PCIe) are not suitable. * BigHand recommends that the latest relevant Service Packs and Windows Updates are installed on the Operating System before installing this component. Requires a service account if running in an Active Directory synchronised BigHand environment. Internet Explorer 6 or later (required for the XMLParser). Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

Other information:

44

BigHand Web Client

BigHand Web Client

Description: Component of: An ASP.NET application that accepts voice files uploaded through a web browser interface. Mobility Suite

Connects to: BigHand Services Host Target of: Processor: Memory (RAM): User, via browser As required by OS and IIS* 256 MB

Storage Negligible requirement: Operating System: Windows Server 2003, Windows Server 2008 (64-bit versions supported), Windows Server 2008 R2

.NET .NET Framework: Versions 2.0 and 3.0 Framework: Connection info: HTTP/S and WCF web services * IIS version 6 or version 7 (Internet Information Services) required. A server authentication certificate is recommended to ensure file upload security. Other information:
BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component. Tested browsers: IE6, IE7, IE8, IE9.

45

B IG H AN D R E PO R TIN G MO D U L E TE CH N ICAL R E Q U IR E ME N TS

BigHand Reporting Module Technical Requirements

Introduction
BigHand reporting module consist of the following reports:
l l

BigHand Analytics BigHand Reporting Suite

47

BigHand Analytics
Description: Component of: A suite of reports that helps users to analyse the organisation's use of the BigHand system. BigHand Reporting Module

Connects to: BigHand database Target of: Processor: Memory (RAM): User As for BigHand Enterprise Client As for BigHand Enterprise Client

Storage Negligible for software only. Reports run in memory based on live data, so no additional requirement: storage required unless you save/export reports. Operating System: Windows XP, Windows Vista, or Windows 7*

.NET .NET Framework version 3.0 Framework: Connection info: The client machine must be able to make a direct connection to the BigHand database. The Crystal Reports software may be independently installed alongside BigHand Analytics but is not required. The redistributable report viewing software is included in the BigHand package. The Microsoft C++ 2005 Runtime X86 may be required before the Crystal component (Crystal Reports 2008 Runtime SP2) can be installed. Other information: * BigHand recommends that the latest relevant Service Packs and Windows Updates are installed on the operating system before installing this component.
Windows authentication and SQLauthentication are supported. The client account

must have db_reader role in BigHand database. BigHand Analytics reporting data is not limited to 30 days. This is only available with BigHand versions 3.4 and above.

48

BigHand Reporting Suite

Description: Component of: A collection of reports and charts, based on data extracted from the BigHand database, to help users analyse the organisation's use of BigHand. BigHand Core

Connects to: BigHand database via ODBC Target of: Processor: Memory (RAM): User As for operating system and MS Excel version As for operating system and MS Excel version

Storage As for operating system and MS Excel version requirement: Operating System: As for operating system and MS Excel version

.NET .NET Framework version 2.0 Framework: Connection info: Other information: . ODBC The Reporting Suite is supported on Microsoft Excel 2003, 2007, and 2010 (Note: 2010x64 is NOT supported). MDAC 2.6 or above (Microsoft Data Access Components). Excel Reports are limited to the last 31 days of data.

49

B IG H AN D SPE E CH R E CO G N ITIO N TE CH N ICAL R E Q U IR E ME N TS

Introduction to Server Side Speech Recognition

Introduction to Server Side Speech Recognition

BigHand Speech Recognition enables users to transcribe voice files with the BigHand Windows client using a wired microphone, portable microphone, or smartphone and send them to a speech recognition workflow. The BigHand Workflow Server uploads the file and updates the database. The BigHand External Workflow Server communicates with the BigHand database and filestore via the BigHand Services Host. The BigHand Transcription Server accepts the file from the BigHand External Workflow Server and gives it to Dragon for transcription. Dragon transcribes the voice file and gives a resulting text. The Speech Recognition Pre-learning Utility is an optional component which can be used to train the speech recognition profiles using transcribed voice files prior to use. The Speech Recognition components are as follows:
l l l

Dragon NaturallySpeaking SDK Server from Nuance Communications BigHand Transcription Server BigHand External Workflow Server (see BigHand Core Product Technical Requirements document) Speech Recognition Pre-Learning Utility (optional)

51

Introduction to Server Side Speech Recognition

Dragon NaturallySpeaking SDK Server

Description: Component of: The Dragon NaturallySpeaking SDK Server from Nuance Communications provides server-side speech recognition functionality for BigHand users. Speech Recognition

Connects to: BigHand Transcription Server* Target of: Processor: Memory (RAM): BigHand Transcription Server* Recommended: Intel Pentium 2.4 GHz (1.8 GHz dual core processor) or equivalent AMD processor. 2 MB L2 Cache recommended. Windows Server 2003: 1 GB minimum, 2 GB recommended Windows Server 2008: 2 GB minimum, 4 GB recommended

Storage 2.5 GB requirement: Operating System: Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2

.NET N/A Framework: Connection info: Co-exist with other services: Shared memory

Must be installed on the same machine as the BigHand Transcription Server. * BigHand Transcription Server 'wraps' the DNSSDKServer.
Nuance states that 'BestMatch IV has the greatest recognition accuracy on dual-core

systems with more than 2 GB of RAM' and that it is designed for multi-core environments. Other information:
Minimum for a custom installation where you install only the program files and one set

of speech files. The storage requirement also depends on the number of users. The speech profiles require several gigabytes of hard disk space. Ensure that you have adequate storage for the profiles you want to install.
BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component. User profiles also require storage space, up to a maximum of 2 GB per user.

52

Introduction to Server Side Speech Recognition

BigHand Transcription Server

Description: Component of: A Windows service that wraps the Dragon NaturallySpeaking SDK Server from Nuance. BigHand Speech Recognition (Optional module)

Connects to: Dragon NaturallySpeaking SDK Server Target of: Processor: Memory (RAM): External Workflow Server As for DNSSDKServer* As for DNSSDKServer

Storage 2 GB requirement: Operating System: Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2, 64-bit versions supported

.NET .NET Framework version 3.5 Framework: Connection info: Co-exist with other services: WCF / HTTP

No competition for resources can cause degradation in transcription accuracy. * Same specification as for the Dragon NaturallySpeaking SDK Server. The BigHand Transcription Server must be co-located with the Dragon NaturallySpeaking SDK Server. It should not be co-located with other programs/services.

Other information:

The speech profiles require several gigabytes of hard disk space. Ensure that you have

adequate storage for the profiles you want to install.

BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component. User profiles also require storage space, up to a maximum of 2GB per user.

53

Introduction to Server Side Speech Recognition

BigHand Speech Recognition Pre-learning Utility

Description: This tool is used to train the speech recognition engine using completed voice files.

Component of: Speech Recognition Connects to: Target of: Processor: Memory (RAM): Storage requirement: Operating System: .NET Framework: Connection info: Other information: BigHand Services User As for BigHand Windows Client As for BigHand Windows Client As for BigHand Windows Client Windows XP, Windows Vista, Windows 7 (64-bit versions supported) .NET Framework version 3.0 TCP All BigHand components for Speech Recognition must be installed first. Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

54

Introduction to Client Side Speech Recognition

Introduction to Client Side Speech Recognition

BigHand integrates with Nuance Dragon NaturallySpeaking to provide Client Side Speech Recognition. Using BigHand Client Side Speech Recognition users can view and edit text as it is transcribed. Users can use voice commands to edit text, apply basic formatting from the BigHand console and export formatted text to Microsoft Word. Users can also insert the formatted text into a template using the BigHand profile feature. For more information about Client Side Speech Recognition, refer to the Client Side Speech Recognition User Guide. The Speech Recognition components are as follows:
l l

Nuance Dragon NaturallySpeaking SDK client edition version 11 BigHand Windows Client. For information on technical requirements, see 'BigHand Core Product Technical Requirements'.

55

Introduction to Client Side Speech Recognition

Dragon NaturallySpeaking SDK client edition

Description: BigHand integrates with Nuance Dragon NaturallySpeaking to provide client side speech recognition.

Component of: Client Side Speech Recognition Connects to: Target of: BigHand Windows Client N/A Minimum: 1 GHz Intel Pentium or equivalent AMD processor or 1.66 GHz Intel Atom processor. Recommended: 1.8 GHz Intel Dual Core or equivalent AMD processor. Minimum:
l l

Processor:

1 GB for Windows XP and Windows Vista 2 GB for Windows 7 and Windows Server 2003/2008

Memory (RAM)*:

Recommended:
l l

2 GB RAM for Windows XP and Windows Vista 4 GB for Windows 7 and Windows Server 2003/2008 64-bit

Storage requirement:

2.5 GB Microsoft Windows 7, 32-bit and 64-bit

Operating System:

Microsoft Windows Vista SP1 and SP2, 32-bit and 64-bit Microsoft Windows XP SP2 and SP3, 32-bit only Windows Server 2003 and 2008, SP1, SP2 and R2, 32-bit and 64-bit

.NET Framework: Connection info:

3.0 Shared memory

Co-exist with Must be installed on the same machine as the BigHand Windows client other services: * The minimum specification may increase if other applications are also running on the machine. Other information:
The User profiles also require storage space up to a maximum of 2GB per user. BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component.

56

B IG H AN D IN TE G R ATIO N S MO D U L E TE CH N ICAL R E Q U IR E ME N TS

BigHand Integrations Module Technical Requirements

Introduction
BigHand Integrations include the following:
l

BigHand Integration with Autonomy iManage

58

BigHand Integration with iManage

The iManage integration allows users to profile voice files with client and matter Description: information from either iManage itself or BigHand. The profiled voice file can be used by assistants to generate and store documents in iManage using the correct template. Component of: iManage Integration

Connects to: BigHand Services Host; BigHand iManage Server Target of: Processor: Memory (RAM): BigHand Windows Client As for BigHand Windows Client As for BigHand Windows Client

Storage As for BigHand Windows Client requirement: Operating System: Windows XP, Windows Vista, Windows 7 (64-bit versions supported)

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

Yes Prerequisites: iManage Filesite or Desksite, .NET3, BigHand Windows Client with attachments. Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

Other information:

59

B IG H AN D O U TSO U R CIN G MO D U L E TE CH N ICAL R E Q U IR E ME N TS

BigHand Outsourcing Module Technical Requirements

Introduction
BigHand Outsourcing components consist of the following module:
l

Outsourcing Module

61

Outsourcing Module
The Outsourcing Module is a Windows service which works with the BigHand Server to Description: export voice files and write them to an outsourcing agency's web server. The module acts as a 'virtual transcriber' within BigHand. Component of: Outsourcing Module

Connects to: BigHand Server, Agency web server Target of: Processor: Memory (RAM): Authorised BigHand users Minimum: Pentium IV* 1 GB

Storage 10 GB requirement: Operating System: As per BigHand Windows Client*

.NET .NET Framework version 3.0 Framework: Connection info: Co-exist with other services: TCP/IP

Yes Login credentials (to the agency's web server) are required so that the Outsourcing Module can write voice files to a directory on the agency's web server. * The Outsourcing Module acts as a client to the BigHand Server. If a high throughput of voice files is expected, you should use a higher specification than a typical client machine.

Other information:

The host server should have adequate storage to accommodate the anticipated

throughput of outsourced voice files. The service requires a service account if running in an Active Directory synchronised BigHand environment. Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

62

Agency Access
The access point for an external transcription agency to the organisation's BigHand system. The agency may have a web server that receives voice files from the Description: organisation's BigHand Outsourcing module. Alternatively, agency users may access the organisation's BigHand system, using the BigHand plug-in, via Citrix or Windows Terminal Services. Component of: N/A

Connects to: N/A Target of: Processor: Memory (RAM): Outsourcing module* N/A N/A

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

.NET N/A Framework: Connection info: HTTPS (module) or ICA / RDP (thin client plug-in) * Only if using the Outsourcing module and a target web server at the agency. The agency's web server must have a shared 'import' directory to which the Outsourcing module can write files. The web server must also have a shared 'export' folder from which the Outsourcing module can read the returned XML and, optionally, transcribed documents.

Other information:

63

B IG H AN D SD K TE CH N ICAL R E Q U IR E ME N TS

BigHand Client SDK

Description: Component of: Software Development Kit which enables extension of the BigHand Windows Client or integration with third-party application. BigHand or third-party extensions to BigHand or integrations with other software.

Connects to: BigHand or third-party system Target of: Processor: Memory (RAM): BigHand extensions or third-party applications N/A* N/A

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

.NET .NET Framework version 3.0 Framework: Connection info: Other information: N/A * Specifications dependent on application. Note: The BigHand Client SDK currently does not work in thin client environment such as Citrix, Terminal Services and VDI. This is a known limitation.

65

System Admin. SDK

Description: Component of: A software development kit that enables third-party developers to create applications that use BigHand System Administration functionality. BigHand or third-party extensions to BigHand or integrations with other software.

Connects to: BigHand Services Host Target of: Processor: Memory (RAM): Third-party application Depends on application Depends on application

Storage Negligible* requirement: Operating System: Depends on application

.NET .NET Framework version 3.0 Framework: Connection info: Other information: Web services * If you are using the BigHand System Admin SDK, you will require resources for supporting technologies such as your IDE (Integrated Development Environment) and the BigHand software.

66