Branch Discovery Service

Paul Farrell (CRO)John Murray (ERS) Stefan Ellström (Bolagsverket)

Branch Discovery Service

Branch Discovery Service

Agenda

• EU Branch Directive Pilot (11th)• Application in Production• What now?• BRITE• User experiences

Branch Discovery Service

A little history...

• Problem was aired at ECRF 2004• Cooperation between the CRO, Dublin &

Companies House, UK• Early warning system for a ‘host’ registration

authority on changes in the ‘home’ registration.

• Prototype application• Simple design

Branch Discovery Service

In Production

• Branch Discovery service created• Web service design• Sample .NET application developed• Partners

– Companies House, UK– Companies Registration Office, Ireland– Bolagsverket, Sweden– Bronnoysund Register Centre, Norway

Branch Discovery Service

In Production

Business Register 1(HostRegister)

InterRegistry CommunicationServer

Business Register 2(HomeRegister)

Subscribe to company 0001 in BR2

Request list of its companies that other BR's have subscribed to

List of subscribed companies returned

Publish company status updates (if changed) for subscribed companies

Request an update of company status for subscribed companies

Company status returned

Time

Subscription & Publication

Branch Discovery Service

Deployment

• Web services based• Secure – SSL• Digital certificates issued to all participants• Central server hosted by CRO• Directory of Registers

Branch Discovery Service

Registry Integration

• Ease of Integration• Automatic interface generation (WSDL

deployed)• Platform/technology independent• Phased integration• Flexibility

Branch Discovery Service

Deployment

Inter-registryServer

Register

Inter-regadapator

Sample application

Web services

LocalDB

CH, UK

Register

Inter-regadapator

Sample application

CRO, Ireland

Register

Inter-regadapator

Sample application

BOLS, Sweden

Register

Inter-regadapator

Sample application

BRC, Norway

Inter-registry Server

Branch Discovery Service

BRC, Norway Integration

InterRegWeb Services

Web service request layer

Business logic layer DB

BRC Legacy systemBRC Servers

Batch jobsRegistrationapplications

Web

IRC Servers

Branch Discovery Service

BOLS approach

• Bolagsverket’s IT environment based on - Unisys mainframe - Java / J2EE (mostly for integration)

• Design and implementation based on 4 use cases : - watch Interreg status on parent companies - subscribe for status changes - alert case holders - transfer status of subscribed Swedish companies

Branch Discovery Service

BOLS Interreg integration

InterRegWeb Services

Web service request

layer

Branch handling DB

BRC Legacy systemand case holder clients

BOLS Java application servers

Batch job forsubscriptions

UC #2

BOLS PublicWeb Site

Internet

Batch job forstatus update

UC #3

Legacy system

RegistrationApplications

UC #1

Legacy integrator

Batch job forstatus checks

and alert UC #4

Branch Discovery Service

BOLS user interface

Branch Discovery Service

User Experiences - BOLS

• Using Web Services is easy (maybe easier than internal integrations).

• Automatic interface generation (WSDL deployed) makes coding faster

• Branch discovery application is small and light – makes it easy to use

• Good security level

Branch Discovery Service

User Experiences – BOLS cont.

• The internal information handling and process definitions can be complex, for instance:

- translation of a company’s ‘status’ - what process should a liquidation start ?- “invalid” values (eg. misspellings) in the BR register of other registers

Branch Discovery Service

User Experiences – BOLS cont #2.

• We didn’t expect any technical problems in integration -– and we didn’t get any either !( in two days, the communication was established).

• Success factors: - possibility to integrate to legacy systems - identification of parental company - decisions of how status changes should be handled