4.2 BigHand Enterprise Full Technical Requirement

BIGHAND FULL TECHN ICAL REQU IREMENTSSoftware version: BigHand 4.2

Last edited date: 10 November 2011

Contents

2

Contents

Contents 2

BigHand Core Product Technical Requirements 4

BigHand Core Topology 5Introduction 5

Core Components 9

BigHand Database 10

BigHandWorkflow Server 11

Filestore(s) 12

BigHand ServicesHost 13

BigHand ExternalWorkflow Server 14

Active DirectoryUsers&Computers 15

BigHand Active DirectoryServices 16

BigHand SystemAdministration 17

BigHandWindowsClient 18

BigHand Standalone 19

Terminal server (Citrix) 20

TerminalServer (Windows) 21

Thin client (PC) 22

Thin client (Terminal) 23

BigHand for Smartphones Technical Requirements 24BigHand for SmartphonesTopology 25

BigHand for BlackBerry® 26BigHand for BlackBerry® 26

BlackBerryEnterprise Server® 26

BlackBerryGateway 27

BigHandGateway 28

BigHand for iPhone® 29BigHand for iPhone® 29

Mobile Gateway 30

BigHand for Android® 31BigHand for Android® 31

Mobile Gateway 32

BigHand forWindows Mobile® 33BigHand for WindowsMobile® 34

Security Façade 35

BigHandMobility Technical Requirements 36Introduction 37

BigHandMobility Topology 38

BigHand Email Gateway 39BigHand EmailGateway (COM+) 41

BigHand Email Exchange Service (ExchangeWeb Services) 42

BigHandGateway 43

BigHand Telephony 44

Contents

3

BigHandWebClient 45

BigHand ReportingModule Technical Requirements 46Introduction 47

BigHand Analytics 48

BigHand Reporting Suite 49

BigHand Speech Recognition Technical Requirements 50

Introduction to Server Side Speech Recognition 51Dragon®NaturallySpeaking™ SDKServer 52

BigHand Transcription Server 53

BigHand Speech Recognition Pre-learning Utility 54

Introduction to Client Side Speech Recognition 55Dragon®NaturallySpeaking™ SDKclient edition 56

BigHand Integrations Module Technical Requirements 57Introduction 58

BigHand Integration with iManage 59

BigHandOutsourcingModule Technical Requirements 60Introduction 61

OutsourcingModule 62

AgencyAccess 63

BigHand SDK Technical Requirements 64BigHand Client SDK 65

SystemAdmin. SDK 66

BIGHAND CORE PRODUCT TECHN ICAL REQU IREMENTS

BigHand Core Topology

5

BigHand Core Topology

IntroductionBigHand is a future-proof technologywhich can be implemented in a variety of ways, allowing theapplication 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 theexception of BigHand Telephony and Speech Recognition.

6

Centralised Computing Environment

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

The above diagram represents an implementation based on centralised server side components. Themain server hosts the global master database, which stores all voice file metadata. The voice files arenot stored in the database - to ensure optimum database performance - but in a separate filestore.

All the server side software is hosted in themain site, with clients connecting to the server(s) via LAN,WAN and VPN.

7

Distributed

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

The above diagram represents an implementation based onmore autonomous offices, having theirown server side components. Themaster database is still located in themain site, but each site hostsits own BigHand services and filestore.

The BigHand services in each site refers to themaster database to store and retrieve voice filemetadata. The servers store files locally to reduceWAN traffic, but the central database keeps trackof where all the system’s files are located, allowing work to be shared.

Thismodel lends itself to sites with greater autonomy, and assumes that a large share of the voice filecreated in a site will be transcribed in the same site. Themajority of thismodel’sWAN traffic ismetadata, andmost file transfer is confined to the site LANs.

8

Hybrid

Alternatively BigHand can be implemented in a hybrid environment where you have amix of bothcentralised and distributed, with large remote sites being supported by their own BigHand servicesand filestoreswhilst 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 ofpotentially better network links within the regions. This limits the amount of bandwidth used byBigHand on network links, assuming voice files rarelymove between regions.

9

Core Components

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

l BigHand Database

l BigHandWorkflow Server

l BigHand Filestore

l BigHand ServicesHost

l BigHand ExternalWorkflow Server

l BigHand SystemAdministration

l BigHandWindowsClient

l Terminal Server

l Terminal Client

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

10

BigHand Database

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

Componentof: BigHand core

Connects to: None

Target of: BigHand Server, BigHand Services

Processor: Minimum: Pentium IVRecommended: Dual Xeon 3.6GHz 800MHzFSB or higher

Memory(RAM):

Minimum: 1GBRecommended: 2 GB

Storagerequirement:


OperatingSystem*:

Minimum:WindowsServer 2003Recommended:WindowsServer 2008,WindowsServer 2008 R2 (64-bit versionssupported)

.NETFramework: Not required

Connectioninfo: TCP/IP Ethernet. Recommended: 1 Gbps

Co-exist withotherservices

Yes

Otherinformation:

Minimumdatabase platform: MSDE 2000 or MSSQLServer Express Edition with latestservice patches.Recommended database platform: MSSQLServer 2005 or MSSQLServer 2008 withlatest service packs.

* BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

Recommended: 10/100/1000Mbps

Network DTC must be enabled on the database server.

Memory is dependent on the size of the database.

11

BigHand Workflow Server

Description: A Windows service that manages file transfer and database updates on behalf of theapplications that it serves.


Connects to: Database, filestore(s).

Target of: BigHandWindowsClient, Telephony, Outsourcingmodule.

Processor: Minimum: Pentium IVRecommended: Dual Xeon 3.6GHz 800MHzFSB or higher

Memory(RAM):


Storagerequirement: Minimum: 200MB*

OperatingSystem:

Minimum:WindowsServer 2003Recommended:WindowsServer 2003,WindowsServer 2008, or WindowsServer2008 R2 (64-bit versions supported)†

.NETFramework: Minimum: .NET Framework version 2.0.

Connectioninfo:

TCP/IP Ethernet. Client TCP port range 5114-5118, connects to SQL Server onTCP 1433. Recommended Ethernet connection speed: 1 Gbps

Otherinformation:

* For application purposes (see filestore for storage requirements)†BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

In a distributed environment, it requires a service account that is a db_owner of theBigHand database, and has read/write/delete permissions to the filestore(s).

Minimum specificationmay increase if other applications outside of BigHand are alsorunning on the samemachine.

12

Filestore(s)

Description:

The BigHand system uses one or more filestores to keep voice files. Often the filestoresare co-located with BigHand Server services. The filestoresmust be accessible, for read/ write / delete operations, by all BigHand Server services and all BigHand ServicesHostservices, to enablemulti-site work sharing.


Connects to: None

Target of: BigHand Server services, BigHand Services

Processor: N/A

Memory(RAM): N/A

Storagerequirement: Approx 1.4MB per 10minutes of recording

OperatingSystem: N/A

.NETFramework: N/A

Connectioninfo: TCP/IP

Otherinformation:

Must be shared with the service accounts that run BigHand Server and BigHandServices.

Storage requirement (MB) = 7 x 0.14 x number of users x avg. recording duration peruser per day (minutes)

(Approx. 0.14MB per minute - with GSM codec) (7 days default time to store completedvoice files)

13

BigHand Services Host

Description: A Windows service that hosts a collection ofWCF web services enablingcommunication between BigHand software components and the BigHand database.


Connects to: Database, filestore(s)

Target of: SystemAdministration, BigHandWindowsClient, WebClient, BigHand ActiveDirectory Services, BigHandGateway, ExternalWorkflow Server, Security Façade

Processor: As for BigHand Server service

Memory(RAM): As for BigHand Server service

Storagerequirement: As for BigHand Server service

OperatingSystem:

WindowsServer 2003,WindowsServer 2008,WindowsServer 2008 R2 (64 bitversions supported)*

.NETFramework: .NET Framework version 3.5

Connectioninfo: WCF web services, file system access, MSDTC

Co-exist withother services Yes

Otherinformation:

* BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on the operating system before installing this component.

Network DTC (Distributed Transaction Co-ordinator) must be enabled. The BigHanddatabase host server must also have network DTC enabled.

The device drivers for the portablesmust be installed to convert web submissions toBigHand format (if web submission is required).

Requires a service account that is a db_owner of the BigHand database. This accountmust have read/write/delete permissions to the BigHand filestore(s).


The windows service 'Port Sharing' must be enabled and started.

14

BigHand External Workflow Server

Description

ThisWindows service checks for voice files that users have sent to Speech Recognition.The servicemonitors the database to provide email notifications to users and escalateworkflows. The service alsomonitors directories for Grundig LAN Docking files and filesfor the automatic import of data for practice builder and profiling.

Componentof:

Speech Recognition, Email Notifications, Session Import (Profiling and PracticeBuilder), Grundig LAN Docking,Workflow Escalation

Connects to: BigHand ServicesHost and BigHand Transcription Server.

Target of: Transcription Server*

Processor: As for BigHand Services

Memory(RAM): As for BigHand Services

Storagerequirement: As for BigHand Services

OperatingSystem:

WindowsServer 2003,WindowsServer 2008,WindowsServer 2008 R2 (64 bitversions supported)†


Connectioninfo: WCF

Co-existwith otherservices

Yes

Otherinformation:

* The service independently polls the BigHand database, taking action as necessary. It isnot explicitly the target of any component other than the Transcription Server, whichnotifies External Workflow Server when a transcription is complete.†BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.


This component may need to be located on a separate server if there is a high usage ofSpeech Recognition. This is because of the additional processor requirements forconversion of the audio files.

15

Active Directory Users & Computers

Description:When BigHand is integrated with Active Directory, user management is performed inActive Directory, and is disabled in BigHand. Users are authenticated in BigHand byvirtue of their Windows authentication (Single sign-on).

Componentof: WindowsServer operating system

Connects to: Active Directory

Target of: BigHand Active Directory Services

Processor: N/A*

Memory(RAM): N/A

Storagerequirement: N/A

OperatingSystem:

WindowsServer 2003,WindowsServer 2008,WindowsServer 2008 R2 (64 bitversions supported)

.NETFramework: N/A

Connectioninfo: Ethernet

Otherinformation:

* The specification of your domain controller(s) is beyond the scope of this document. Adedicated security groupmust be set up for BigHand users. This groupmay containnested groups. Some BigHand componentsmust run under Windows 'serviceaccounts'. These accounts are created and authorised in Active Directory.

16

BigHand Active Directory Services

Description:BigHand Active Directory Services synchronises BigHand with Active Directory tosimplify user management and provide 'single sign on' for users (Windowsauthentication) .


Connects to: BigHand ServicesHost

Target of: BigHand SystemAdministration

Processor: N/A*

Memory(RAM): N/A*


OperatingSystem: N/A*

.NETFramework: N/A*


Co-existwith otherservices

Yes

Otherinformation:

* This component should reside on the BigHand ServicesHost server. If the DirectoryService will synchronise users frommultiple domains, the BigHand Directory Servicesshould be installed on a BigHand ServicesHost in each domain. You will need to set uptrust relationships. Requires a service account if you do not co-locate this service with theBigHand ServicesHost.

17

BigHand System Administration

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



Target of: User

Processor: As per operating system

Memory(RAM): As per operating system

Storagerequirement: Minimum: 100MB; Recommended: 200MB

OperatingSystem: WindowsXP (SP2), WindowsVista, or Windows 7 (64-bit versions supported)†


Connectioninfo: Web services connections (WCF)

Otherinformation:

†BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

18

BigHand Windows Client

Description: The BigHandWindowsClient ismost commonly used for creating and transcribingBigHand voice files on the user's PC.


Connects to: BigHand Server, BigHand Services

Target of: User

Processor: Minimum: Pentium IV; Recommended: Core™ 2 duo

Memory(RAM): Minimum: As per operating system requirements


OperatingSystem: WindowsXP,WindowsVista, or Windows 7 (64-bit versions supported)

.NETFramework: Minimum: .NET Framework version 3.0

Connectioninfo: TCP/IP. Minimum128 kbps for VPN.

Otherinformation:

MSI installer version 4.5 on client machines and any terminal servers that will serve theBigHandWindowsClient.

* .NET Framework version 3.0 is theminimum requirement.

Soundcard required if using analogue / serial (non-USB) devices. Powered USB portrequired for USBmicrophone or portable recording device.

Additional requirements for Speech Recognition support:WindowsXP 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


19

BigHand Standalone

Description:Thismodule is installed by default with the BigHandWindowsClient. A client-sidemodule that simply records or plays voice files. Provides business continuity if theBigHand database or server components are unavailable for an extended period.


Connects to: N/A

Target of: User

Processor: As for BigHandWindowsClient

Memory(RAM): As for BigHandWindowsClient

Storagerequirement: As for BigHandWindowsClient

OperatingSystem: As for BigHandWindowsClient


Connectioninfo: N/A*

Otherinformation:

* This application does not require a network connection; however, youmaywish totransport voice files by email or to a network share. The application shares componentswith the BigHandWindowsClient andmust therefore be installed alongside the BigHandWindowsClient.

BigHand Standalone is installed with the client, by default, but you can choose not toinstall it.


20

Terminal server (Citrix)

Description: The BigHandWindows client application runs on the Citrix terminal server. The client isinstalled on the server and ICA plug-in users connect to the terminal server.

Componentof: Optional module


Target of: BigHand thin client plug-in

Processor: Depends on shared application environment

Memory(RAM): Depends on shared application environment

Storagerequirement: Depends on shared application environment

OperatingSystem:

Minimum: MetaFrame Presentation Server 4.0Recommended: XenApp 5 (32-bit)

.NETFramework: Minimum: .NET Framework version 2.0 and version 3.0

Connectioninfo: ICA

Otherinformation:

Recommended additional bandwidth per active user = 40 kbps (with optimisations off).Note:With optimisations on the bandwidth is reduced. Additional bandwidth will berequired for multiple users or if other applications outside of BigHand are also being usedon the Citrix or Terminal Server.


21

Terminal Server (Windows)

Description: The BigHand client application runs on theWindows terminal server. The client isinstalled on the terminal server and plug-in users connect to the terminal server.



Target of: BigHand thin client plug-in

Processor: Depends on shared application environment

Memory(RAM): Depends on shared application environment

Storagerequirement: Depends on shared application environment

OperatingSystem:

Recommended:WindowsServer 2003,WindowsServer 2008,WindowsServer 2008R2 (64-bit versions supported)

.NETFramework: Minimum: .NET Framework version 2.0 and version 3.0

Connectioninfo: RDP

Otherinformation:

Recommended additional bandwidth per active user = 60 kbps (with optimisations off).Note: With optimisations on the bandwidth required is reduced. Additional bandwidth willbe required for multiple users or if other applications outside of BigHand are also beingused on the Citrix or Terminal Server.


22

Thin client (PC)

Description:In a centralised computing environment, BigHand can run on PCs acting asCitrix orWindows thin client terminals. The BigHand plug-in works via either protocol (ICA /RDP).


Connects to: Terminal server

Target of: User

Processor: Minimum: Pentium IV; Recommended: Core 2 duo

Memory(RAM): Minimum: 128MB; Recommended: 256MB


OperatingSystem: WindowsXP,WindowsVista, Windows 7 (64 bit versions supported*)

.NETFramework: .NET Framework version 2.0†

Connectioninfo: ICA / RDP

Otherinformation:

USB, or RS232 serial port required for hardware connection (Analogue sound cardrequired if using serial port device)

Connection speedminimum: 128 kbps; recommended: 128 kbps or more InternetExplorer 6 or later. RDP5 or ICA32 Version 6.01 or above or ICAWEB version 6.3 orabove required.

* 64-bit WindowsVista is not supported as a terminal services client.† .NET Framework version 2.0 is theminimum requirement.


23

Thin client (Terminal)

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


Connects to: Citrix server or Windows Terminal Server

Target of: User

Processor: Requirement as for Windows 7 Embedded*.

Memory(RAM):

(Flashmemory) Minimum: 128MBRecommended: 256MB

Storagerequirement:

Minimum: 5MBRecommended: 10MB

OperatingSystem:

WindowsXP Embedded with SP2Windows 7 Embedded

.NETFramework: .NET Framework version 2.0†

Connectioninfo: ICA or RDP

Otherinformation:

* If using portable recorders (and DeviceSync) with terminals, BigHand recommends atleast a 1 GHz processor because the processing power of the terminal affectsDeviceSync speed.

USB, or RS232 serial port required for hardware connection (Analogue sound cardrequired if using serial port device)

Connection speedminimum: 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 theminimum requirement.


BIGHAND FOR SMARTPHONES TECHN ICAL REQU IREMENTS

BigHand for SmartphonesTechnicalRequirements

25

BigHand for Smartphones Topology

The architecture below summarises the server side and additional components required forBlackBerry, iPhone,WindowsMobile and Android.

BigHand for BlackBerry®

26


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

l BigHand for BlackBerry client software

l BlackBerry Enterprise Server

l BigHandMobile Gateway

l BigHandGateway


Description: The BigHand client software for BlackBerry smartphones.

Componentof: Mobility Suite

Connects to: BlackBerryGateway via BES or BIS

Target of: User

Processor: N/A

Memory(RAM): N/A

Storagerequirement: 128 / 256 / 512MB*

OperatingSystem: BlackBerry device OS 4.5, 4.6, 4.7, 5.0, 6.0

.NETFramework: N/A

Connectioninfo: Mobile Data Services (MDS) over least cost route (USB, EDGE/GPRS)

Otherinformation:

* The amount of memory on the BlackBerry smartphone affects how much recording canbe stored. The storage can be extended using amemory card - BigHand for BlackBerryuses approximately 1MB for 10minutes of recording.

Supportedmodels: 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)

BlackBerry Enterprise Server®

The BlackBerry® Enterprise Server (BES) is installed and running (BES v4.0 or later). You will needpermission to create a software configuration policy on the BES if you are going to deploy BigHandBigHand for BlackBerry®

Blackberry Enterprise Server Express can be installed instead of Blackberry Enterprise Server whichcan support up to 2000+ with dedicated server(s) or 75 on the primarymail server.


27

BlackBerry Gateway

Description: A BigHand web application which receives voice files fromBigHand for BlackBerry.


Connects to: BigHandGateway

Target of: BigHand for BlackBerry

Processor: As required byOS and IIS*

Memory(RAM): As required byOS and IIS*

Storagerequirement: Approximately 100MB per user†

OperatingSystem:

WindowsServer 2003,WindowsServer 2008,WindowsServer 2008 R2 (64-bitversions supported)‡


Connectioninfo: HTTP/S

Co-existwith otherservices:

Yes

Otherinformation:

In a BIS environment the BlackBerryGateway needs to be installed on a public facinginternet server (in a DMZ) or to be routable through the firewall to allow secureconnections to the BlackBerry smartphones. It may share an IIS server or anothersimilarly isolated server.

* This component is installed on an IIS server. IIS versions 6 and 7 are supported. Theseweb servers are installed withWindowsServer 2003 andWindowsServer 2008respectively. If using IIS7 IIS6Management compatibilitymodemust also be installed.†Based on assumed usage of BigHandWindowsClient. This will vary at yourorganisation - BigHand uses approximately 1.4MB for tenminutes of recording.‡BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

BigHandGateway

28

BigHand Gateway

Description: A Windows service that processes voice files sent in by email or smartphone and thensubmits them to the BigHand core.

Componentof:

Mobility Suite - Email Gateway, BigHand for BlackBerry, BigHand for WindowsMobile,BigHand for iPhone and BigHand for Android


Target of: Email Gateway (COM+), Email Gateway (ExchangeWeb Services), Mobile Gateway

Processor: As for BigHand Server service*

Memory(RAM): As for BigHand Server service*

Storagerequirement: As for BigHand Server service*

OperatingSystem: As for BigHand Server service*


Connectioninfo: Web services, file system access†


Yes

Otherinformation:

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


BigHand for iPhone®

29


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

l BigHand for iPhone client software


l BigHandGateway (refer to BigHand for BlackBerry section)


Description: The BigHand client software for the iPhone.


Connects to: Mobile Gateway*

Target of: User

Processor: Depends onmodel†

Memory(RAM): Depends onmodel†

Storagerequirement: Approx. 380 kb per minute of recording.

OperatingSystem: iOS 3, iOS 4 or iOS 5†

.NETFramework: N/A


Otherinformation:

* When using BigHand for iPhone with the BigHand system. This software also has astandalonemode, which does not require any further BigHand software.†BigHand for iPhone has been tested on iPhone 3G, iPhone 3GS, iPhone 4, iPad andiPod Touch (provided that the headphones are connected while recording).


30

Mobile Gateway

Description: A BigHand web application which receives voice files fromBigHand for iPhone.



Target of: BigHand for iPhone



Storagerequirement: Approx. 100MB per user†

OperatingSystem:

WindowsServer 2003,WindowsServer 2008,WindowsServer 2008 R2 (64 bitversions supported)‡




Yes

Otherinformation:

* This component is installed on an IIS server. IIS versions 6 and 7 are supported. Theseweb servers are installed withWindowsServer 2003 andWindowsServer 2008respectively. If you are using IIS7, then IIS6Management CompatibilityModemust alsobe installed.†Based on assumed usage of BigHand client. This will vary at your organisation –BigHand uses approximately 1.4MB for tenminutes of recording.‡BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

The official name for this component is the 'BlackBerryGateway' although it is also usedfor the iPhone and Android applications.

BigHand for Android®

31


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

l BigHand for Android client software




Description: The BigHand client software for the Android smartphone.


Connectsto: Mobile Gateway

Target of: User

Processor: Depends onmodel*

Memory(RAM): Depends onmodel*

OperatingSystem: Android 2.1; Android 2.2; Android 2.3

.NETFramework: N/A


Otherinformation:

* BigHand for Android has been tested on the following devices: HTC Evo, HTCDesire/Incredible HD, HTCWildfire, MotorolaMilestone 2/Droid 2, SamsungGalaxy S,SamsungGalaxy S II

The screen resolutionswhich have been tested are: QVGA 240x320;WVGA 480x800,FWVGA 480x854.

Please contact your account manager for full details on handset/OS compatibility.


32

Mobile Gateway

Description: A BigHand web application which receives voice files fromBigHand for Android.



Target of: BigHand for Android



Storagerequirement: Approximately 100MB per user†

OperatingSystem:




Otherinformation:

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

It may share an IIS server or another similarly isolated server.

* This component is installed on an IIS server. IIS versions 6 and 7 are supported. Theseweb servers are installed withWindowsServer 2003 andWindowsServer 2008respectively. If using IIS7 IIS6Management compatibilitymodemust also be installed.†Based on assumed usage of BigHandWindowsClient. This will vary at yourorganisation – BigHand uses approximately 1.4MB for tenminutes of recording.‡BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

BigHand for WindowsMobile®

33

BigHand for Windows Mobile®

BigHand for WindowsMobile allows authors to record, edit, track and send their voice filesseamlessly to the BigHand system and requires the following components:

l BigHandWindowsMobile client software

l BigHand Email Gateway (see BigHand Email Gateway section in the 'BigHandMobility TechnicalRequirements')

l Microsoft Exchange Server

l Security Façade



34

BigHand for Windows Mobile®

Description: The BigHand client software for devices running theWindowsMobile operating system.


Connects to: Email Gateway and Security Façade

Target of: User

Processor: N/A

Memory(RAM): N/A

Storagerequirement: 128 / 256 / 512MB*

OperatingSystem:

WindowsMobile 5 Pocket PC,WindowsMobile 5 Smartphone,WindowsMobile 6Standard Edition, WindowsMobile 6 Professional Edition, WindowsMobile 6.1,WindowsMobile 6.5 (version 6 or later recommended)

.NETFramework: .NET Compact Framework versions 2.0 and 3.5

Connectioninfo: HTTP/S over default connection†

Otherinformation:

Microsoft SQL Server Compact 3.5 and the NetCFv3.5Messages .cabmust be installedon the smartphone

* The amount of memory on the smartphone affects how much recording can be stored.This can be extended using amemory card - BigHand uses approximately 1MB for 10minutes of recording.

Testedmodels: BigHand for WindowsMobile® has been tested on HTC: Touch Pro 2,Touch Pro, Touch Cruise, Touch Diamond, S730, S710, TyTN II. Palm: Treo Pro, Treo750. (HTC devices are often rebranded. Checkwith BigHand if you are unsure whetheryour devices are supported.)† The software uses the default transport mechanism selected on theWindowsMobileOS at the time when the voice file is sent. IncludesGPRS, 3G,Wi-Fi. The smartphonemust be certified to authenticate itself to the Security Façade. The required certificate isin place with the default install, but youmay need to add your own certificates if using anon-BigHand Server Authentication certificate on the Security Façade.


35

Security Façade

Description: Provides authentication and status updates for BigHand for WindowsMobile®.



Target of: BigHand for WindowsMobile®

Processor: As for operating system

Memory(RAM): As for operating system

Storagerequirement: As for operating system

OperatingSystem:

Recommended:WindowsServer 2003,WindowsServer 2008,WindowsServer 2008R2 (64 bit versions supported)*


Connectioninfo: HTTPS and net.TCP

Otherinformation:

The Security Façade is designed to run isolated from the BigHand ServicesHost (in aDMZ) to allow secure connections fromWindowsMobile smartphones. It may share anIIS server or another similarly isolated server.

The Security Façademust be certified with a Server Authentication certificate. Thecertificate namemust match the external facing IP address of the Security Façade andthe server address configured in BigHand for WindowsMobile.


BIGHAND MOBIL ITY TECHN ICAL REQU IREMENTS

BigHandMobility TechnicalRequirements

37

Introduction

Themobility options are as follows:

l BigHand Email Gateway

l BigHandWebClient

l BigHand Telephony

Please refer to the ‘BigHand for Smartphone Technical Requirements’ for devicemobility options.

38

BigHand Mobility Topology

The architecture below summarises the server side and additional components required for BigHandEmail Gateway, Telephony andWebClient.

BigHand EmailGateway

39

BigHand Email Gateway

The BigHand Email Gateway option enables users who record using a remote device to use a webbased or home email account to send voice files into the system (e.g. Hotmail, Gmail or OWA).

The BigHandWorkflow Server automatically routes the work to the chosen recipient(s) with nomanual file saving or email opening required. The subject line, priority and recipient of the email areinterpreted by the BigHand Email Gateway and the voice file appears in a transcriber’s work inprogress as normal.

Authors can also send voice files in .amr file format using email-capable smartphones.

The BigHand Email Gateway requires the following:

l BigHand Email Gateway

l BigHandGateway

BigHand EmailGateway

40

41

BigHand Email Gateway (COM+)

Description: A BigHand COM+ component which resides on the Exchange server*, monitoring oneor moremailboxes for messageswith voice file attachments.

Componentof: Mobility Suite - BigHand Email Gateway


Target of: BigHand for WindowsMobile® and email submissions

Processor: N/A*

Memory(RAM): N/A*

Storagerequirement: Negligible†

OperatingSystem:

Minimum:WindowsServer 2003; Recommended:WindowsServer 2003,WindowsServer 2008,WindowsServer 2008 R2 (64-bit versions supported)‡


Connectioninfo: N/A

Otherinformation:

* 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 afterprocessing.‡BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component. Clustering: Installthe BigHand Email Gateway on all physical nodes in an Exchange cluster. Do not installBigHand Email Gateway on virtual nodes.

42

BigHand Email Exchange Service (Exchange Web Services)

Description: A Windows service that communicateswith Microsoft Exchange to extract voice filessent to specificmailboxes and submit those attachments to the BigHand system.

Componentof: Mobility Suite - Email Gateway

Connects to: Microsoft Exchange and BigHandGateway

Target of: None*

Processor: N/A (as for OS)

Memory(RAM): N/A (as for OS)

Storagerequirement: Negligible †

OperatingSystem:



Connectioninfo: Web services calls using ExchangeWeb Services

Otherinformation:

The service does not need to be hosted adjacent to Exchange Server. MicrosoftExchange 2010 andMicrosoft Exchange 2007 SP1 are supported. Autodiscoverymustbe enabled on the Exchange Server.

* The service independently polls the Exchange looking for newly arrived voice fileattachments.† The service deletes themessages from themailboxes on the Exchange Server afterprocessing the attachments. Processing simply involves transferring the files to anotherBigHand component, the BigHandGateway.‡BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on the operating system before installing this component.

BigHandGateway

43

BigHand Gateway

Description: A Windows service that processes voice files sent in by email or smartphone and thensubmits them to the BigHand core.

Componentof:

Mobility Suite - Email Gateway, BigHand for BlackBerry, BigHand for WindowsMobile,BigHand for iPhone and BigHand for Android


Target of: Email Gateway (COM+), Email Gateway (ExchangeWeb Services), Mobile Gateway

Processor: As for BigHand Server service*

Memory(RAM): As for BigHand Server service*

Storagerequirement: As for BigHand Server service*

OperatingSystem: As for BigHand Server service*


Connectioninfo: Web services, file system access†


Yes

Otherinformation:

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


BigHand Telephony

44

BigHand Telephony

Description: A Windows service hosted on a telephony server. Thismodule records voice files overthe telephone and then submits them to the BigHand Server service.

Componentof: Mobility Suite – Telephony

Connects to: BigHand Server

Target of: Telephone voice calls

Processor: Minimum: Pentium IV

Memory(RAM): 1 GB

Storagerequirement: 10 GB

OperatingSystem: WindowsServer 2003*

.NETFramework: .NET 3.0



No – seeOther information

Otherinformation:

BigHand recommends a dedicated server for this component. The server must have aPCI TAPI telephony card with Global API support. Supported types include Intel DialogicD4PCIUFEU, D41JCTLS and D120JCT.

The target server requires enough physical space to house the PCI telephony card. The4 port card is a half-length card and the 6 or 12 port cards are full length PCI cards. Theserver must have a full size PCI slot. Newer serversmay only have PCI Express slots, inwhich case you will need to install and test the telephony card using an adapter. BigHandsupports regular 5v or 3.3v PCI slots and PCI-X slots commonly found on server grademachines. PCI-Express slots (aka PCIe) are not suitable.


Requires a service account if running in an Active Directory synchronised BigHandenvironment.

Internet Explorer 6 or later (required for the XML Parser).


BigHandWebClient

45

BigHand Web Client

Description: An ASP.NET application that accepts voice files uploaded through a web browserinterface.



Target of: User, via browser


Memory(RAM): 256MB

Storagerequirement: Negligible

OperatingSystem:

WindowsServer 2003,WindowsServer 2008 (64-bit versions supported)†, WindowsServer 2008 R2

.NETFramework: .NET Framework: Versions 2.0 and 3.0

Connectioninfo: HTTP/S andWCFweb services

Otherinformation:

* IIS version 6 or version 7 (Internet Information Services) required. A serverauthentication certificate is recommended to ensure file upload security.†BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

Tested browsers: IE6, IE7, IE8, IE9.

BIGHAND REPORTING MODULE TECHN ICAL REQU IREMENTS

BigHand ReportingModule TechnicalRequirements

47

Introduction

BigHand reportingmodule consist of the following reports:

l BigHand Analytics

l BigHand Reporting Suite

48

BigHand Analytics

Description: A suite of reports that helps users to analyse the organisation's use of the BigHandsystem.

Componentof: BigHand ReportingModule

Connects to: BigHand database

Target of: User

Processor: As for BigHand Enterprise Client

Memory(RAM): As for BigHand Enterprise Client

Storagerequirement:

Negligible for software only. Reports run inmemory based on live data, so no additionalstorage required unless you save/export reports.

OperatingSystem: WindowsXP,WindowsVista, or Windows 7*


Connectioninfo: The client machinemust be able tomake a direct connection to the BigHand database.†

Otherinformation:

The Crystal Reports softwaremay be independently installed alongside BigHandAnalytics but is not required. The redistributable report viewing software is included inthe BigHand package.

TheMicrosoft C++ 2005 Runtime X86may be required before the Crystal component(Crystal Reports 2008 Runtime SP2) can be installed.

* BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on the operating system before installing this component.†Windows authentication and SQL authentication are supported. The client accountmust have db_reader role in BigHand database.

BigHand Analytics reporting data is not limited to 30 days. This is only available withBigHand versions 3.4 and above.

49

BigHand Reporting Suite

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

Componentof: BigHand Core

Connects to: BigHand database via ODBC

Target of: User

Processor: As for operating system andMS Excel version

Memory(RAM): As for operating system andMS Excel version

Storagerequirement: As for operating system andMS Excel version

OperatingSystem: As for operating system andMS Excel version


Connectioninfo: ODBC

Otherinformation:

The Reporting Suite is supported onMicrosoft Excel 2003, 2007, and 2010 (Note:2010x64 is NOT supported). MDAC 2.6 or above (Microsoft Data AccessComponents).Excel Reports are limited to the last 31 days of data.

.

BIGHAND SPEECH RECOGN ITION TECHN ICALREQU IREMENTS

Introduction to Server Side Speech Recognition

51


BigHand Speech Recognition enables users to transcribe voice files with the BigHandWindowsclient using a wiredmicrophone, portablemicrophone, or smartphone and send them to a speechrecognition workflow.

The BigHandWorkflow Server uploads the file and updates the database. The BigHand ExternalWorkflow Server communicateswith the BigHand database and filestore via the BigHand ServicesHost.

The BigHand Transcription Server accepts the file from the BigHand ExternalWorkflow Server andgives 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 thespeech recognition profiles using transcribed voice files prior to use.

The Speech Recognition components are as follows:

l Dragon NaturallySpeaking SDK Server fromNuance Communications®

l BigHand Transcription Server

l BigHand ExternalWorkflow Server (see ‘BigHand Core Product Technical Requirements’document)

l Speech Recognition Pre-Learning Utility (optional)


52

Dragon® NaturallySpeaking™ SDK Server

Description: The Dragon NaturallySpeaking™ SDK Server fromNuance Communications providesserver-side speech recognition functionality for BigHand users.

Componentof: Speech Recognition

Connects to: BigHand Transcription Server*

Target of: BigHand Transcription Server*

Processor: Recommended: Intel® Pentium® 2.4 GHz (1.8 GHz dual core processor) or equivalentAMD processor. 2 MB L2Cache recommended.

Memory(RAM):

WindowsServer 2003: 1 GBminimum, 2GB recommendedWindowsServer 2008: 2 GBminimum, 4GB recommended

Storagerequirement: 2.5 GB‡

OperatingSystem: WindowsServer 2003,WindowsServer 2008, andWindowsServer 2008 R2§

.NETFramework: N/A

Connectioninfo: Sharedmemory


Must be installed on the samemachine as the BigHand Transcription Server.

Otherinformation:

* BigHand Transcription Server 'wraps' the DNS SDK Server.†Nuance states that 'BestMatch IV has the greatest recognition accuracy on dual-coresystemswith more than 2GB of RAM' and that it is designed for multi-coreenvironments.‡Minimum for a custom installation where you install only the program files and one setof speech files. The storage requirement also depends on the number of users. Thespeech profiles require several gigabytes of hard disk space. Ensure that you haveadequate storage for the profiles you want to install.§BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

User profiles also require storage space, up to amaximumof 2 GB per user.


53

BigHand Transcription Server

Description: A Windows service that wraps the Dragon NaturallySpeaking™ SDK Server fromNuance.

Componentof: BigHand Speech Recognition (Optional module)

Connects to: Dragon® NaturallySpeaking™ SDK Server

Target of: ExternalWorkflow Server

Processor: As for DNS SDK Server*

Memory(RAM): As for DNS SDK Server

Storagerequirement: 2 GB†

OperatingSystem:

WindowsServer 2003,WindowsServer 2008, andWindowsServer 2008 R2‡, 64-bitversions supported


Connectioninfo: WCF / HTTP


No – competition for resources can cause degradation in transcription accuracy.

Otherinformation:

* Same specification as for the Dragon NaturallySpeaking™ SDK Server. The BigHandTranscription Server must be co-located with the Dragon® NaturallySpeaking™ SDKServer. It should not be co-located with other programs/services.† The speech profiles require several gigabytes of hard disk space. Ensure that you haveadequate storage for the profiles you want to install.‡BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

User profiles also require storage space, up to amaximumof 2GB per user.


54

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: BigHand Services

Target of: User




OperatingSystem: WindowsXP,WindowsVista, Windows 7 (64-bit versions supported)


Connectioninfo: TCP

Otherinformation:

All BigHand components for Speech Recognitionmust be installed first.


Introduction to Client Side Speech Recognition

55


BigHand integrateswith Nuance Dragon® NaturallySpeaking™ to provide Client Side SpeechRecognition. Using BigHand Client Side Speech Recognition users can view and edit text as it istranscribed. Users can use voice commands to edit text, apply basic formatting from the BigHandconsole and export formatted text to Microsoft Word. Users can also insert the formatted text into atemplate using the BigHand profile feature.

For more information about Client Side Speech Recognition, refer to the Client Side SpeechRecognition User Guide. The Speech Recognition components are as follows:

l Nuance Dragon® NaturallySpeaking™ SDK client edition version 11

l BigHandWindowsClient. For information on technical requirements, see 'BigHand Core ProductTechnical Requirements'.


56

Dragon® NaturallySpeaking™ SDK client edition

Description: BigHand integrateswith Nuance Dragon® NaturallySpeaking™ to provide client sidespeech recognition.

Component of: Client Side Speech Recognition

Connects to: BigHandWindowsClient

Target of: N/A

Processor:

Minimum: 1GHz Intel® Pentium® or equivalent AMD processor or 1.66 GHz Intel®Atom® processor.

Recommended: 1.8 GHz Intel Dual Core™ or equivalent AMD processor.

Memory(RAM)*:

Minimum:

l 1GB for WindowsXP andWindowsVista

l 2GB for Windows 7 andWindowsServer 2003/2008

Recommended:

l 2GB RAM for WindowsXP andWindowsVista

l 4GB for Windows 7 andWindowsServer 2003/2008 64-bit

Storagerequirement: 2.5 GB†

OperatingSystem‡:

Microsoft Windows 7, 32-bit and 64-bit

Microsoft WindowsVista SP1 and SP2, 32-bit and 64-bit

Microsoft WindowsXP SP2 and SP3, 32-bit only

WindowsServer 2003 and 2008, SP1, SP2 and R2, 32-bit and 64-bit

.NETFramework: 3.0

Connectioninfo: Sharedmemory

Co-exist withother services: Must be installed on the samemachine as the BigHandWindows client

Otherinformation:

* Theminimum specificationmay increase if other applications are also running on themachine.† TheUser profiles also require storage space up to amaximumof 2GB per user.‡BigHand recommends that the latest relevant Service Packs andWindowsUpdatesare installed on theOperating System before installing this component.

BIGHAND INTEGRATIONS MODULE TECHN ICALREQU IREMENTS

BigHand IntegrationsModule TechnicalRequirements

58

Introduction

BigHand Integrations include the following:

l BigHand Integration with Autonomy iManage

59

BigHand Integration with iManage

Description:The iManage integration allows users to profile voice files with client andmatterinformation from either iManage itself or BigHand. The profiled voice file can be used byassistants to generate and store documents in iManage using the correct template.

Componentof: iManage Integration

Connects to: BigHand ServicesHost; BigHand iManage Server

Target of: BigHandWindowsClient




OperatingSystem: WindowsXP,WindowsVista, Windows 7 (64-bit versions supported)


Connectioninfo: TCP.


Yes

Otherinformation:

Prerequisites: iManage Filesite or Desksite, .NET3, BigHandWindowsClient withattachments.


BIGHAND OUTSOURCING MODULE TECHN ICALREQU IREMENTS

BigHandOutsourcingModule TechnicalRequirements

61

Introduction

BigHandOutsourcing components consist of the followingmodule:

l OutsourcingModule

62

Outsourcing Module

Description:TheOutsourcingModule is aWindows service which workswith the BigHand Server toexport voice files and write them to an outsourcing agency's web server. Themoduleacts as a 'virtual transcriber' within BigHand.

Componentof: OutsourcingModule

Connects to: BigHand Server, Agencyweb server

Target of: Authorised BigHand users

Processor: Minimum: Pentium IV*

Memory(RAM): 1 GB

Storagerequirement: 10 GB†

OperatingSystem: As per BigHandWindowsClient*




Yes

Otherinformation:

Login credentials (to the agency's web server) are required so that the OutsourcingModule can write voice files to a directory on the agency's web server.

* TheOutsourcingModule acts as a client to the BigHand Server. If a high throughput ofvoice files is expected, you should use a higher specification than a typical clientmachine.† The host server should have adequate storage to accommodate the anticipatedthroughput of outsourced voice files.

The service requires a service account if running in an Active Directory synchronisedBigHand environment.


63

Agency Access

Description:

The access point for an external transcription agency to the organisation's BigHandsystem. The agencymay have a web server that receives voice files from theorganisation's BigHandOutsourcingmodule.Alternatively, agency usersmay access the organisation's BigHand system, using theBigHand plug-in, via Citrix or Windows Terminal Services.

Componentof: N/A

Connects to: N/A

Target of: Outsourcingmodule*

Processor: N/A

Memory(RAM): N/A



.NETFramework: N/A

Connectioninfo: HTTPS (module) or ICA / RDP (thin client plug-in)

Otherinformation:

* Only if using theOutsourcingmodule and a target web server at the agency. Theagency's web server must have a shared 'import' directory to which theOutsourcingmodule can write files. The web server must also have a shared 'export' folder fromwhich theOutsourcingmodule can read the returned XML and, optionally, transcribeddocuments.

BIGHAND SDK TECHN ICAL REQU IREMENTS

65

BigHand Client SDK

Description: Software Development Kit which enables extension of the BigHandWindowsClient orintegration with third-party application.

Componentof: BigHand or third-party extensions to BigHand or integrationswith other software.

Connects to: BigHand or third-party system

Target of: BigHand extensions or third-party applications

Processor: N/A*

Memory(RAM): N/A




Connectioninfo: N/A

Otherinformation:

* Specifications dependent on application.

Note: The BigHand Client SDK currently does not work in thin client environment suchasCitrix, Terminal Services and VDI. This is a known limitation.

66

System Admin. SDK

Description: A software development kit that enables third-party developers to create applicationsthat use BigHand SystemAdministration functionality.

Componentof: BigHand or third-party extensions to BigHand or integrationswith other software.


Target of: Third-party application

Processor: Depends on application

Memory(RAM): Depends on application

Storagerequirement: Negligible*

OperatingSystem: Depends on application


Connectioninfo: Web services

Otherinformation:

* If you are using the BigHand SystemAdmin SDK, you will require resources forsupporting technologies such as your IDE (Integrated Development Environment) andthe BigHand software.

4.2 BigHand Enterprise Full Technical Requirement

Documents

Transcript of 4.2 BigHand Enterprise Full Technical Requirement