VICTORIAN 32 COUNCIL EASYBIZ EXTENSION CONSORTIUM
 
EasyBiz Project Web Services Framework Specification,
Contract No. CT060718 

Closing date: Wed 06 Sep 2006 - 1400 Melbourne time

9.2 TRANSFORMATION OF EASYBIZ COMMON DATA FORMAT INTO COUNCIL SPECIFIC DATA FORMAT

9	System Solution Description 							60
	9.1 	System Architecture 							61
	9.2 	Transformation of EasyBiz common data - THIS WEB PAGE			66
		format into council specific data format 
	9.3 	EasyBiz System Architecture Amendments 					67
	9.4 	Performance Requirements 						68
	9.5 	Hosting of EasyBiz Solution 						69
	9.6 	System Personnel 							69
	9.7 	System Constraints 							70
	9.8 	Technology Forecast 							70

9.2 Transformation of EasyBiz common data format into council specific data format


It is the responsibility of the EasyBiz Web Services Hub to perform any required data
transformation from the EasyBiz common data format into a council (vendor proprietary) 
specific data format.

The extent/number of transformations that the EasyBiz Web Services Hub will need to 
facilitate is estimated to be 58.

This estimation is based upon:

A	The EasyBiz common data format needing to be transformed into 10 vendor proprietary
	data formats;

B	For each vendor, their proprietary data format then needing to be transformed into a
	council specific data format 

	Most councils have taken the proprietary format provided to them by their vendors and 
	further customised the proprietary format to suit specific council requirements 

	eg the vendor may call the person submitting a planning permit application an 
	"applicant" and the council using the vendor system may call the person submitting 
	the planning permit application the "proponent", therefore council will have 
	"customised" the vendor's proprietary format. 

	Due to confidentiality reasons, the number of councils using a vendor system can be
	identified against the vendor system, but the breakdown of number of councils using 
	10 vendor systems are:

	a	7 councils use Vendor A;

	b	9 councils use Vendor B;

	c	4 councils use Vendor C;

	d	2 councils use Vendor D;

	e	7 councils use Vendor E;

	f	11 councils use Vendor F;

	g	3 councils use Vendor G;

	h	1 council uses Vendor H;

	i	2 councils use Vendor I;

	j	2 councils use Vendor J;

** Note -> A council can use multiple vendors.


RUBAC Electronic Information Management Methodology Copyright of Hamme Family Trust

                

        









































                                

                                

                                

                                

                                

                                

                                

                                

Revised:      S: 21:58 Sun 2006/08/27 Syd 2089
 
                                F: 22:27 Sun 2006/08/27 Syd 2089

Who:    aer

Authorised:   prh

Created:  09:45 Tue 13/06/2000   Syd  2065

By:     kmb

Revision:   3a4h1.002

Original Page: 3a4h

Change date:  

Who:   

Authorised: