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 ]
7.5 INFORMATION/DATA EXCHANGE
7 ?
7.1 ?
7.2 Operational Needs 34
7.3 Stakeholder Needs 36
7.4 EasyBiz Data Elements 50
7.5 Information/Data Exchange - THIS WEB PAGE 50
7.6 Operational Policies and Standards 53
7.5 Information/Data Exchange
This section describes the "triggers" that cause data gathered from EasyBiz to sent and
retrieved from another system.
TABLE 11 - EASYBIZ INFORMATION/DATA EXCHANGES
ID TRIGGER FROM TO INFORMATION
1 Form is completed and EasyBiz Portal Designated Council 1 Amount
options completed in Payment Gateway 2 Credit Card Details
the form determine the 3 some type of identifer
cost of the permit.
User selects to pay for
permit, enters credit card
details and presses submit
2 Payment gateway Designated EasyBiz Portal Outcome of transaction
processes transaction Council (approved or rejected),
Payment if approved the receipt
Gateway number
Provider
3 Form is completed EasyBiz Portal EasyBiz Web Validated and verified
in EasyBiz and user Services Hub transaction data (form
presses submit data, supporting
information, payment
data e.g. receipt
number) in EasyBiz
common data format
4 EasyBiz Web Services EasyBiz Web Council Back-End Validated and verified
Hub to send transaction Services Hub System transaction data (form
data to Council Back data, supporting
End System information, payment
data e.g. receipt
number) in either
EasyBiz common data
format or vendor
proprietary data format
5 Transaction data is Council Back- EasyBiz Web Receipt number that
received by council End System Services Hub small/home based
business can use to
track the assessment
of their permit
application.
6 Acknowledgement is EasyBiz Web EasyBiz Portal Receipt number that
sent to EasyBiz Portal Services Hub small/home based
to advise user council business can use to
has received transaction track the assessment
data of their permit
application.
7 Small/home based EasyBiz Portal EasyBiz Web Name of business,
business requests to Services Hub address of business
create an EasyBiz
profile
8 Business details sent EasyBiz Web Third party Name of business,
to third party for Services Hub (e.g.Victorian address of business,
validation Business Master Registration details
e.g. business Key, Australian
registration details Business Register)
9 Business details are 3rd party EasyBiz Web Business either exists
validated against the Services Hub or doesn't exist in
3rd party business register, plus
register registration details
10 Business who is EasyBiz Web EasyBiz Portal Business is advised
requesting to create a Services Hub whether exist in
profile in EasyBiz is register or not.
advised whether or not
they are registered
11 Request report from Council backend EasyBiz Web Time, date, transaction
EasyBiz Portal regarding system Services Hub name parameters
what "transaction data"
has been sent
12 Request report from EasyBiz Web EasyBiz Portal Time, date, transaction
EasyBiz Portal based Services Hub name parameters
upon "report" parameters
defined by council
13 Collate and send report EasyBiz Portal EasyBiz Web Transaction identifier,
details based upon Services Hub number of transactions
report parameters etc that were submitted
by the EasyBiz Portal
to the EasyBiz Web
Services Hub
14 On-send report details EasyBiz Web Council backend Transaction identifier,
to council Services Hub system number of transactions
etc that were submitted
by the EasyBiz Portal
to the EasyBiz Web
Services Hub
15 Cost of a permit, Council Back- EasyBiz Web Name of permit, licence
licence or registration End System Services Hub or registration, cost of
form is changed by permit, licence or
council registration
16 EasyBiz portal updates EasyBiz Web EasyBiz Portal Name of permit, licence
cost of permit, licence Services Hub or registration, cost of
or registration form permit, licence or
for council registration
17 Registered EasyBiz EasyBiz Portal EasyBiz Web Name of business,
user enters address Services Hub address of business
of business premise premise
that the permit,
licence or
registration application
relates to
18 Business premise EasyBiz Web Council Back- Name of business,
address is sent to Services Hub End System address of business
council for validation premise
that it is exists in
a council and which
council it exists in
19 Business premise is Council Back- EasyBiz Web Business address
validated by council End System Services Hub exists in council,
that it exists in an business address
EasyBiz Consortium doesn't exist in an
Council EasyBiz Consortium
Council
20 Registered EasyBiz EasyBiz Web EasyBiz Portal Business address
user is advised as Services Hub exists in council,
to whether business business address
premise exists in doesn't exist in an
an EasyBiz EasyBiz Consortium
Consortium Participating Council
21 Registered EasyBiz EasyBiz Portal EasyBiz Web Permit, licence or
users wishes to renew Services Hub registration number
a permit, licence or
registration
22 Permit, licence or EasyBiz Web Council Back- Permit, licence or
registration to be Services Hub End System registration number
renewed is to be checked
against council records
23 Permit, licence or Council Back- EasyBiz Web Permit, licence or
registration number is End System Services Hub registration number
correct or not correct or not, if
correct details
regarding the permit,
licence or registration
to be renewed e.g. name
of applicant, address,
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 ]
