Project for the Regional Advancement of Statisticsstatistics.caricom.org/Files/Meetings/PRASC/Mtg_BR/... · Pros • Easy to implement • No need to have IT specialist Cons • Can

Project for the Regional

Advancement of Statistics

in the Caribbean - PRASC

Component: Business Survey Infrastructure

01/02/2018Statistics Canada • Statistique Canada3

René Beaudoin

Director, Statistical Registers and Geography Division

BR Data Model and System

May 2017

Outline

BR System

BR Environment

Guiding Principles

IT Considerations

Data Model

The Objectives of a BR System

User friendly modules

Provide interfaces common to all users

Use business rules to ensure data integrity

Navigate through all business information with ease

Facilitate direct updates by users

Allow Batch processes (administrative data)

Access to historical information (snapshots)

Ensure a level of security control

BR Environment

Administrative Data

Module

Survey Interface

File Module

(Snapshots, Collection

• Legal/Operating Entities

• Tombstone

• Unique ID

• ISIC

• Size Variables

• Business Status

• Etc.

• Contact Persons

• Name

• Phone Number

• Fax Number

• Email Address

•Etc.

• Business Statistical Structure • Enterprise/Establishment

Survey Feedback

Module

Guiding Principles

The use of proven standards and technology will:

• Reduce project risks

• Reduce development time

• Reduce cost

The use of existing IT infrastrucure will:

• Create efficiencies and reduce costs

Keep software diversity at a minimum in order to reduce:

• Dilution of our core knowledge

• Fracturing the expertise

IT Development Methodology

Business requirements

System design

Prototyping * / Development

Testing

Documentation & Training

Roll-out / Transition

Decommissioning of the old system

Maintenance

* iterative process

Systems Infrastructure

Define the requirements for your system

Consider non-functional requirements:

• Size of your data repository

• Number of users

• Number of transactions/day, second, etc.

• Acceptable response time

• Existing technology

• Expertise

• Cost/Budget

• Number of environments (development, Testing,

Production etc.)

Systems Infrastructure – Cont’d

Consider functional business requirements:

• System Features

Online Browser

Search Function

Update Capability

Extract Function

This will drive the choices you make for your

technology and architecture.

Security Management

Authorisation?• Access on “need to know” basis

• Define a repeatable process for authorisation

• Document it

• Director approval required?

• Manage role based on access level

Browsing

Updating

• Mechanism to remove access after people leave

division/department or no “need to know”

Establishing a BR: IT Considerations

If you have a small business population (<5,000 units) and small user

community (< 5 users)

Excel or other spreadsheets could be considered

• Easy to implement

• No need to have IT specialist

• Can not use the multi-user functionalities

• Can not separate the Database Back-end from the application

• Limited security management

• Difficult to automate the use of administrative data to maintain the BR

• No transaction log

(cont’d)

Database Management System (DBMS) is highly

beneficial

• Manages relational units

• Provides basis to manage updates

• Facilitates querying

• Contains a good security management functionality

• Can separate the Database Back-end from the application

• Can use the multi-user functionalities

DBMS options:

• SQL Server (various editions and cost options)

• Oracle Database

• Open-source (MySQL community version, MariaDB)

(cont’d)

User interface options

• .NET

• JAVA

• Open-source (Ruby on Rails, Python, PHP, Perl)

Open-source vs off-the-shelf

• Open-source is “free”, although fee based support and premium

editions are available

Core Generic BR Data Model

Business Table

StatisticalNumber

LegalName

OperationalName

Address

PhoneNumber

ISICSource

ISICDate

Revenue

RevenueSource

RevenueDate

NumberOfEmployees

NumberOfEmployeesSource

NumberOfEmployeesDate

WagesSource

WagesDate

BusinessTypeCodes

BusinessStatusCodes

StatisticalStructure Table

ChildStatisticalNumber

ParentStatisticalNumber

Contact Table

ContactID

StatisticalNumber

Address

PhoneNumber1

PhoneNumber2

FaxNumber

EmailAddress1

EmailAddress2

BusinessLog Table

StatisticalNumber

LogDate

UpdateSource

LegalName

OperationalName

Address

+ All other needed attributes from

Business Table

Hierarchical

Link Table for

Legal/Operating

Entities

Assumption:

Contact can

have only one

Business

Transaction Log

that records all

needed

transactions

Auxiliary BR Data Tables

Business Table

StatisticalNumber

LegalName

OperationalName

Address

PhoneNumber

ISICSource

ISICDate

Revenue

RevenueSource

RevenueDate

NumberOfEmployees

BusinessTypeCodes

BusinessStatusCodes

BusinessTypeCodesTable

BusinessTypeCodes

LongDescription

ExternalKeys Table

StatisticalNumber

RegistrarNumber

VATNumber

TaxNumber

EmployerNumber

BusinessStatusCodes Table

BusinessStatusCodes

LongDescription

Example – Ste Lucia Data Model

BusinessStatisticalStructure

LegalStructure

BusinessTypeCodes

BusinessStatusCodes

Contact

OptionalBusinessAttributes

Registrar

BusinessLog

StatisticalNumberPK

LegalName

OperationalName

ChildStatisticalNumberPKFK

ParentStatisticalNumberFK

ChildStatisticalNumberPKFK

ParentStatisticalNumberFK

Assumption: Child can have only one

parent.

Assumption: Child can have only one

parent.

Address

PhoneNumber

BusinessTypeCodeFK

BusinessStatusCodeFK

Revenue

NumberOfEmployees

RevenueSource

SalesSource

WagesSource

ISICSource

BusinessTypeCodePK

LongDescription

BusinessStatusCodePK

LongDescription

ContactIDPK

StatisticalNumberFK

Assumption: Contact can have only one Business.

BuildingNumber

PhoneNumber1

FaxNumber

EmailAddress1

StatisticalNumberPKFK

Others?

VATNumberPK

StandardRatedSupplies

TotalOutputTax

YearPK

MonthPK

ZeroRatedSupplies

ExemptSupplies

TotalSupplies

NICNumberPK

NumberOfEmployees

RegistrarOfCompNum

TradeName

AddressLine1

DateOfRegistration

EmailAddress

PhoneNumber

AddressLine2

Location

District

TotalContributions

Sector

NatureOfBusiness

YearPK

RegistrarNumberPK

Address?

CreationDate?

ExistingBR

Formal Businesses

InformalBusinesses

Assumption: One-time load operation from

existing BR

IRDNumberPK

TradeName

MailingAddress

MailingCity

PhoneNumber

FaxNumber

EmailAddress

ValTaxSupply

Primary_ISIC

Secondary_ISIC

TaxSuppStartDate

LegalStatus

Representative

YearPK

ExternalKeys

IRDNumberFK

VATNumberFK

Assumption: Relationships never change over time

NICNumberFK

RegistrarNumberFK

NumberOfSalariedEmployees

NumberOfSalariedEmployeesSource

Other such tables could be added for other fields, such as ISIC, ISCO, source, etc, as required.

RevenueDate

NumberOfSalariedEmployeesDate

SalesDate

WagesDate

ISICDate

District

Street

PhoneNumber2

EmailAddress2

LegalName

OperaitonalName

LogDatePK

Address

Include all other attributes from Business table

UpdateSource

Conclusion

Use proven technology

Keep software diversity at a minimum

Identify the resource expertise

Clearly identify the platform based on business

need (Size of population, # of users)

Clearly define the data model

Identify the variables and the transactions to log

You can contact the PRASC team at:

prasc@statcan.gc.caor

statcan.prasc-prasc.statcan@canada.ca

Project for the Regional Advancement of Statisticsstatistics.caricom.org/Files/Meetings/PRASC/Mtg_BR/... · Pros • Easy to implement • No need to have IT specialist Cons • Can

Documents

Pros manufii13th2014mf.pdf

Pros Nine 13

Pros Investigations.authcheckdam

Why eProcesss Pros

Slide Pros

Inclusion: Pros & Cons

Pros Arethn

Geothermal Energy pros Cons Nuclear Power pros Cons Solar...

ArcGIS Secure Mobile Implementation...

pros & cons

Micro Pros

SURINAME - CARICOM...

Regional Seminar -...

Tech Pros - Presentation

House Painting The Pros And Not Quite Pros

PROS Clarification -...