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 System Solution Description 60 9.1 System Architecture 61 9.2 Transformation of EasyBiz common data 66 format into council specific data format 9.3 EasyBiz System Architecture Amendments - THIS WEB PAGE 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.3 EasyBiz System Architecture Amendments Due to various factors including the capacity of vendor resources to undertake integration work and the significant amount of work required to produce valid and acceptable EasyBiz schemas; it is unlikely that the target EasyBiz System Architecture will be fully implemented within the project timeframe. In the event that the target EasyBiz System Architecture is unable to be implemented, the following amendments will be made to the target EasyBiz System Architecture: A Email Push Integration Between EasyBiz Portal and council - the EasyBiz Portal will package up all transaction data (completed form, supporting documents, completed payment) and pass to council via email. Council receives the transaction data in the EasyBiz Common Data Format. The email will identify who sent the form, what the permit, licence or registration application is, when it was sent by EasyBiz and what the EasyBiz "receipt/transaction number" is. EasyBiz may be required to generate its own "receipt/transaction number". Council will have the ability to enter and edit the email address that EasyBiz sends the transaction data to. Council at a minimum would need to manually enter the transaction data into their own backend systems. Council's vendor would be invited to determine whether they can easily import the transaction data received via email into the back-end system. Council would need to use the EasyBiz receipt/transaction number to retrieve the transaction data should they receive an enquiry from the EasyBiz user. B Council Pull Integration Option - the same principle as above except council will regularly "poll" the EasyBiz web server, identify any "newly" created transaction data and pull that transaction data into their back-end system. Using a web service the council will be responsible for initiating this transaction; The impact upon the target EasyBiz System Architecture is illustrated in Appendix F - Amendments to target EasyBiz System Architecture. 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: 22:27 Sun 2006/08/27 Syd 2089
F: 22:43 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: