VICTORIAN 32 COUNCIL EASYBIZ EXTENSION CONSORTIUM
EasyBiz Project Web Services Framework Specification,
Contract No. CT060718 Closing date: Wed 06 Sep 2006 - 1400 Melbourne time
[ Home ] [ LZIG Tenders ] [ This Tender ] [ Index This Tender ] [ Next Page ] [ Previous Page ] [ Joint Venture ] [ Copyright ]
9.1 SYSTEM ARCHITECTURE
9 System Solution Description 60 9.1 System Architecture - THIS WEB PAGE 61 9.2 Transformation of EasyBiz common data 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.1 System Architecture The EasyBiz System Architecture is divided into four tiers. The tiers are: A EasyBiz Portal; B Third Party Relationships; C EasyBiz Web Services Hub and; D Council Back-end systems/web services The development of the EasyBiz components that comprise that tier is the responsibility of a different software developer. Table 16 - Responsibility for development of components for each tier states who is responsible. Table 16 - Responsibility for development of components for each tier states who is responsible. TIER RESPONSIBLE A EasyBiz Portal EasyBiz System Developer B EasyBiz Web Services Hub EasyBiz Web Services Development Contractor C Council Web Services and Integration Council Vendor D Third Party Relationships EasyBiz Web Services Development Contractor Each tier comprises of a number of components and those components are described in Table x - EasyBiz Components. Table 17 - EasyBiz Components provides a description of each of the components/modules that will comprise the EasyBiz architecture. TABLE 17 - EASYBIZ COMPONENTS TIER COMPONENT DESCRIPTION OF COMPONENT A1 EasyBiz Portal Decision Tree (including The decision regarding the software management of Decision /application to be used for the Decision Tree) Tree component has yet to be made. A2 Forms Selector (including It is likely that Abode Forms Lifecycle manage forms, forms Manager Product will be used to create selector and distribution, and manage forms. partially completed forms) A3 Manage Security (including Consideration must be given to the manage user profile) Federated single sign on capabilities of the Victorian Business Master Key (VBMK) initiative and initiatives under the Federal Government Business Entry Point (BEP). User levels, Login/logout, user profiles, unauthorised usage, viruses/scams/bugs, privacy issues need to be considered. A4 Manage Reporting The decision regarding the solution for managing the reporting requirements is yet to be made. A5 Manage Content The decision regarding the solution to manage EasyBiz web content is yet to be made. A6 Payment Gateway Manager Consideration of existing Government (including manage based payment gateway systems, including distribution of payments) the Queensland federated payment system. Smart eDA B1 Third Party Download Form EasyBiz users are able to download forms Relationships from EasyBiz portal. B2 Third Party Data Sources Third party data sources include various Federal and State Government agencies that wish to share data with the EasyBiz Portal and councils. B3 Payment Gateway The EasyBiz Portal will use existing council payment gateway providers to undertake the processing of payments for the permit, licence or registration. The payment will be processed by the council's payment gateway and will send back to the EasyBiz Portal the outcome of the transaction and then the EasyBiz Portal will send transaction data to the EasyBiz Web Services Hub including the payment data e.g. payment transaction number which the council will use to match the payment in councils financial systems with the transaction data. C1 EasyBiz Web EasyBiz Web Services Hub The EasyBiz Web Services Hub will be Services Hub capable a Being the interface between EasyBiz Portal and Third Party Data Providers using web services b Being the interface between EasyBiz Portal and councils. EasyBiz Portal will send to the EasyBiz Hub transaction data (including form data and all attached supporting information) and the council (and council vendor) will have the choice of either: 1 Accepting the EasyBiz common data format and importing the data into a council system for further assessment/review. The council (vendor) will be responsible for "transforming" the EasyBiz common data format into a format that is acceptable to the council's back-end system. If council chooses this option, the EasyBiz Web Services Hub will provide a simple/easy method for councils that wish to "transform/map" from the EasyBiz common data format into their own council format e.g. a drag and drop method of mapping the EasyBiz common data format to the council specific format; or 2 Having the EasyBiz Web Services perform the "transformation" of the EasyBiz common data format into the council's vendor proprietary data format. This includes the discovery and understanding of the vendor proprietary format c Being capable of enabling a council to request "transaction data" in the EasyBiz common data format from the EasyBiz Web Services Hub using a standard communication protocol C2 Forms Distribution Manager The distribution of the forms completed in the EasyBiz portal will be managed at the EasyBiz Web Services Hub layer. The distribution of forms encompasses: a Managing the trigger of the EasyBiz "user" selecting submit and the transaction data then being sent to the EasyBiz Web Services Hub which will facilitate the sending of the "transaction data" to the relevant council. D1 Council Web Web Services Council vendors must develop and expose a Services and minimum of one web service which accepts the Integration Tier received by council, council sends to the EasyBiz Web Services Hub a "receipt number". The one web service is required to broker the transmission of one set of data for one particular purpose regardless of any specific council transactions e.g. the one web service is required to pass all data from EasyBiz Portal through EasyBiz Web Services Hub to council. The council has the choice of either accepting the EasyBiz Common Data Format or the agreed Council Data Format (via transformation being performed by the EasyBiz Web Services Hub). Additional web services that council/ vendors may well decide to develop in the future include: 1 Calculate Fee Amount - council receives from the EasyBiz Web Services Hub data that describes the permit, licence and registration application form that is being completed by the EasyBiz user. Council uses data to calculate the cost of the permit, licence or registration application and then returns the fee amount to the EasyBiz Web Services Hub, which is then picked up by the EasyBiz Portal to facilitate the payment of the permit, licence or registration application; 2 Validate Form Data - council receives transaction data from the EasyBiz Hub and performs back-end validation of the transaction data e.g. the business premise exists in council, the permit, licence or registration has not been previously applied for etc Council sends back to EasyBiz Web Services Hub a message that the transaction data is valid and the EasyBiz user should proceed with the completion of the form, attachment of supporting information and payment; 3 Enable Renewals - council receives a permit, licence or registration number from the EasyBiz Hub that the EasyBiz user wishes to renew. Council returns to the EasyBiz Hub which is picked up by the EasyBiz portal that the permit, licence or registration is due for renewal and the data that was previously provided by the small/home based business (enabling the small/home based business to update the information). 4 Exchange data between council and third party data/system providers - the EasyBiz Web Services Hub will enable council and third party data/ system providers to exchange data outside of the EasyBiz Portal. To enable these transactions, depending upon the council's vendor system capabilities, the council vendor may be required to develop special interfaces into the council system to be able to perform the required fee calculation or validation and return the required results. D2 Council Back End Systems Each council uses one or more vendor products to manage data concerning planning, building, local laws and food/health type transactions. RUBAC Electronic Information Management Methodology Copyright of Hamme Family Trust
[ Home ] [ LZIG Tenders ] [ This Tender ] [ Index This Tender ] [ Next Page ] [ Previous Page ] [ Joint Venture ] [ Copyright ]

                











































Revised: S: 01:40 Mon 2006/08/28 Syd 2089
F: 02:56 Mon 2006/08/28 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: