Technical Design Overview R1C2

Online Member Transactions (OMT)
Release 1 Capability 2 - My Portfolio Manager Technical Design Overview
Version: 0.1 Status: Draft Date: 30 August 2011 Owner: RACV
Modification History Version 0.1 Date 08/09/2011 Description of Change Initial draft Author Suresh Addala
Architectural Endorsement Version Date Endorsement Status Architect Majola Oosthuizen Suresh Addala Udaya Rayapur Sandeep Madan Simon Vanderlicht
Governance Approval Version Date TGC comments Governance Member
Formatted: Font color: Text 1
document1technical design overview r1c2 2011-09-08 am.docx
Page 2 of 28
Table of Contents
1 2
2.1 2.2
DOCUMENT PURPOSE SCOPE

Document scope Business scope
5 5
5 5
HIGH LEVEL MODELLING
65
95 96 118 118
3.1 Level 1 Business Models 3.1.1 L1 OMT Process Model 3.2 Level 2 Process Models 3.2.1 L2 Landing page Process
OMT LANDING PAGE (BR-1)
128
128 138 159 159 159 169 169 1710 1710 1710 1810 1810 1810 1810 1910 1910 1910 1910 2011 2011 2011 2011 2011 2111 2111 2111 2111 2111 Error! Bookmark not defined.11 2211 2211 2211 2212 2312 2312 2312 2312 2312
4.1 Design overview My Portfolio Manager (BR-301) 4.1.1 L3 Activity Model 4.1.2 Portal components 4.1.3 Services components 4.1.4 Database components 4.2 Design Overview Member Details (BR-301) 4.2.1 L3 Activity Model 4.2.2 Portal Components 4.2.3 Services Components 4.2.4 Database Components 4.3 Design Overview Expired and Cancelled Products (BR-301) 4.3.1 L3 Activity Model 4.3.2 Portal Components 4.3.3 Services Components 4.3.4 Database Components 4.4 Design Overview View ERA Product Details (BR-301) 4.4.1 L3 Activity Model 4.4.2 Portal Components 4.4.3 Services Components 4.4.4 Database Components 4.5 Design Overview View EHA Product Details (BR-301) 4.5.1 L3 Activity Model 4.5.2 Portal Components 4.5.3 Services Components 4.5.4 Database Components 4.6 Design Overview View Home Insurance Product Details (BR-301) 4.6.1 L3 Activity Model 4.6.2 Portal Components 4.6.3 Services Components 4.6.4 Database Components 4.7 Design Overview View Vehicle Insurance Product Details (BR-301) 4.7.1 L3 Activity Model 4.7.2 Portal Components 4.7.3 Services Components 4.7.4 Database Components 4.8 Design Overview View/Print/Email Certificate of Insurance (COI) (BR-301) 4.8.1 L3 Activity Model 4.8.2 Portal Components
Page 3 of 28
4.8.3 4.8.4
Services Components Database Components
2312 2312 2312 2312 2412 2412 2413 2413 2413 2513 2513 2513
4.9 Design Overview View Supporting Product Policy Details (BR-301) 4.9.1 L3 Activity Model 4.9.2 Portal Components 4.9.3 Services Components 4.9.4 Database Components 4.10 Design Overview View Club Product Details (BR-301) 4.10.1 L3 Activity Model 4.10.2 Portal Components 4.10.3 Services Components 4.10.4 Database Components
5 6
6.1 6.2 6.3
APPENDIX 1: DATA MODELS APPENDIX2: PROCESS MODEL LEVELS

BPMN Levels Business process modelling levels Level of models provided in OMT capability requirement documents
2613 2614
2614 2714 2815
Page 4 of 28
Document purpose
1. Project management: To serve as evidence of progress at milestones of the OMT project plan. 2. Governance: To expose principles of the design back to the TGC to enable monitoring and directing of the solution design to conform to the letter and spirit of OMT capability requirements. 3. Architecture: To surface the integrated design to ensure that the many detailed design specifications work together as a whole.
The Technical Design Overview satisfies three purposes:
Scope
2.1 Document scope

The Technical Design Overview exposes the following elements of design: 1. Technical business, process and activity flows which identify: a. User interactions b. Portal views and operations c. OMT web services d. Hub services e. Data tables 2. Portal components: pages, portlets, views, operations 3. Service components: services, operations, messages 4. Database components: tables
2.2 Business scope

A Technical Design Overview exposes the technical design of a single Capability Requirements document. This Technical Design Overview covers Capability Requirement R1C1 v1.2, which includes the following: 1. BR-3 OMT Landing Page a. BR-301 - Personal Information - Display Only Items b. BR-303 - Member Options* c. BR-304 - Member Communications d. BR-305 - OMT Landing Page Content e. BR-306 - RACV Club Branding 2. BR-2 Login & Password BR-207 Expired Membership
Page 5 of 28
Outstanding Issues
Build Activity COI Tasks Hub Services do not provide any service interface that can provide all the required fields for COI Activities in Progress IAL interfaces/ services needs to be evaluated for the same. WIP [7/9] HUON has provided the documents. HCL to go thru the documents and come up with list of clarifications required Data mapping for Product Details have been created and needs to be validated with BAS. Jira task reference is: https://racvbas.onjira.com/browse/OMT-124 06/09/2011 - Discussion with Insuarance team is in progress and also initial discussion happened with SAP R3 and eCRM technical team. Recommendation Need to see the feasibility to deffer till R1C6 OMT Id
Formatted Table
Release R1C2
R1C2
Product/ Policy Details
The Policy Detail can be fetched from IAL, similarly need to identify how to fetch details for ERA and EHA products.
Need to see the feasibility to deffer till R1C6
180
R1C2
Product and Policy Summary
Hub Services used for the Summary (retreiveLOB) may not provide updated information.
Confirm from BAS whether different source systems contribute to this or hub service (RetrieveLOB). HCL to schedule a meeting to discuss this.
Can go ahead with current service interface. Simultaneously, investigate on other possibilities to fetch the summary.
180
R1C2
Availability of IAL/HUON environment
what systems to connect to based on the IAL release timelines
Data mapping for Product Details have been created and needs to be validated with BAS. Jira task reference is: https://racvbas.onjira.com/browse/OMT-124 06/09/2011 - Discussion with Insuarance team is in progress
R1C2 R1C2 R1C2 R1C2 R1C2 R1C2 R1C2 R1C2
Connectivity requirements for IAL Connectivity to IAL Integration method used in interacting with IAL Availability of MARS/SAPR3 Connectivity requirements for MARS/SAPR3 Connectivity to MARS/SAPR3 Integration method used in interacting with MARS/SAPR3 Availability & connectivity to OPERA environment
What information is required to connect to IAL Setting up the connection to IAL Policy details can be fetched from IAL. More specific info on what services to be used or how to fetch the info is required. what are the servers to connect to. What are the connectivity requirements for MARS/SAPR3 Provide connectivity to required integration environment for integration, do we have to use SAP Adapter? Is it the system to get the club membership info? How to connect to this environment? Are there services that provide the info as of today or OMT has to write services? More clarificaitons expected on 9/9/11 Initial discussion happened with SAP R3 and eCRM technical team.
181
182
183 184 185
Page 6 of 28
Release R1C2 R1C2 R1C2 R1C2
Build Activity Services information for IAL Services information for MARS/SAPR3 Services information for OPERA Sample XMLs
Tasks Specific services to be used to serve the functionality in the capability Specific services to be used to serve the functionality in the capability Specific services to be used to serve the functionality in the capability IAL messages for fetch and update
Activities in Progress Set of xmls and documents were shared with HCL. HCL to go thru these and come back with questions if any. Discussion with BAS in progress Discussion with BAS in progress Requested sample XMLs from Geln
Recommendation
OMT Id 186 185 187
Formatted Table
3
Release R1C2 Build Activity COI Issues/ Risk Hub Services do not provide any service interface that can provide all the required fields for COI The Policy Detail can be fetched from IAL, similarly need to identify how to fetch details for ERA and EHA products. Activities in Progress IAL interfaces/ services needs to be evaluated for the same. WIP Data mapping for Product Details have been created and needs to be validated with BAS. Jira task reference is: https://racvbas.onjira.com/browse/OMT-124 06/09/2011 - Discussion with Insuarance team is in progress and also initial discussion happened with SAP R3 and eCRM technical team. Discussion with BAS in progress Recommendation Need to see the feasibility to deffer till R1C6 Need to see the feasibility to deffer till R1C6
Formatted: Normal, Right: 0" Formatted: Font: (Default) +Body (Calibri), Font color: Background 1 Formatted: Right: 0.16", Space Before: 6 pt
R1C2
Product/ Policy Details
R1C2
Product and Policy Summary
Hub Services used for the Summary (retreiveLOB) may not provide updated information.
Can go ahead with current service interface. Simultaneously, investigate on other possibilities to fetch the summary.
R1C2
Availability & connectivity to HUON environment
Policy details can be fetched from IAL. More specific info on what services to be used or how to fetch the info is required.
Data mapping for Product Details have been created and needs to be validated with BAS. Jira task reference is: https://racvbas.onjira.com/browse/OMT-124 06/09/2011 - Discussion with Insuarance team is in progress Initial discussion happened with SAP R3 and eCRM technical team.
R1C2 R1C2
Availability & connectivity to MARS/SAPR3 environment Availability & connectivity to OPERA environment SME: Availability of HUON SMEs for complete functional and technical information. (100% availability of the resource who is immediate contact for HCL) SME: Availability of MARS/SAPR3 SMEs for complete functional and technical information. (100% availability of the resource who is immediate contact for HCL)
How the ERA and EHA is fetched from source systems? Is it the system to get the club membership info? How to connect to this environment? Are there services that provide the info as of today or OMT has to write services? Impact on deliverables and timelines if appropriate information is not provided on time
R1C2
R1C2
Impact on deliverables and timelines if appropriate information is not provided on time
Page 7 of 28
R1C2
R1C2 R1C2 R1C2 R1C2 R1C2
SME: Availability of OPERA system SMEs for complete functional and technical information. (100% availability of the resource who is immediate contact for HCL) Services information for IAL Services information for MARS/SAPR3 Services information for OPERA Sample XMLs Availability & connectivity of HUON service to fetch insurance information Availability & connectivity of SAPR3/MARS services to fetch ERA and EHA information Availability & connectivity of OPERA services to fetch club membership information Clarifications on Gap Analysis
Impact on deliverables and timelines if appropriate information is not provided on time
Specific services to be used to serve the functionality in the capability Specific services to be used to serve the functionality in the capability Specific services to be used to serve the functionality in the capability IAG messages for fetch and update
Discussion with BAS in progress Discussion with BAS in progress Discussion with BAS in progress Requested sample XMLs from BAS
R1C2
R1C2
R1C2
Possible rework if gap analysis is not confirmed
Page 8 of 28
High level modelling
For a description of the organisation of models into levels, refer to the appendix, section 68.
4.1 Level 1 Business Models

Level 1 models show how the business as a whole interacts with industry players, without distinguishing between internal details such as roles and systems. Level 1 model may differentiate by organisational units and product lines. 4.1.1 L1 OMT Process Model
Figure 1 is the Level 1 model of the overall OMT process from the perspective of OMT Release 1. An overview of this high level business process is as follows: 1. All OMT users will enter the OMT portal via a login process. This login process includes all aspects of login, such as authentication and registration. 2. After successful login, users will be presented with a landing page, which is presented in different ways depending on context. 3. On the landing page the user can select to proceed with one of many processes as shown in a vertical row on the right. Only some of those processes are addressed in R1C2, the scope of this document. 4. When the selected process has been completed without termination, the user will return to the OMT Landing page process. 5. The cycle is continued until the user terminates the process. As a rule, each of the Level 2 and Level 3 sub-processes in Figure 1 matches specific requirements of a single capability. The capability is annotated to the name. For example, the OMT Landing Page Process addresses requirements of R1C2. Process models marked as R1C2 are covered in this document. Some capability requirements are identified at lower level models. For example, Member Registration, a R1C3 requirement, is contained as a sub process of the L2 Member Login process.
Page 9 of 28
Figure 1: Level 1 OMT process
Page 10 of 28
4.2 Level 2 Process Models

Level 2 models expose individual processes from Level 1. Most Level 2 models will contain subprocesses and few if any atomic activities, although some Level 2 models are simple enough to expose all atomic activities. 4.2.1 L2 Landing page Process
Figure 2: L2 Landing Page Process (R1C2)
The Level 2 Member Login process functions as follows: 1. After user successfully logs in, a landing page is displayed to the user with product and asset information. 2. From the landing page the user can choose to do one of the following: a. Show COI details: This will fetch the Certificate of Information (COI) from HUON source system. b. Show ERA details: This will fetch the Emergency Road Assistance (ERA) information for the user registered products. c. Show EHA details: This will fetch the Emergency Home Assistance (ERA) information for the user registered products. d. Show Club Membership: This will fetch the club membership details to the user.
document1Technical design overview r1c2
Page 11 of 28
5
5.1
OMT Landing Page (BR-1)

Process flow provided by business
OMT My Portfolio Manager

R1C2-PM1
My Portfolio Manager R1C2 Member logs out/ terminates session PM1-27 PM1-1 End End
Action
No View further info? PM1-16 Member selects to view policy or product document e.g. PDS, brochure PM1-17 Member views COI Yes PM1-27
Yes
Member
Member logs into OMT
Exit
Member Selects Action
Member selects to view policy or product information PM1-12
Member request COI No email? PM1-28 Member receives COI email PM-30
Member selects to pay for a product or policy PM-33 Member selects online customer services (contact us, FAQ etc) PM1-35 Member selects to view or update personal details PM1-36
PM1-11 Member views product or policy related document PM1-21 Member selects to view Certificate of Insurance (COI) PM1-22 Member views COI ineligibility message PM-32
OMT System
Member OMT Account active? PM1-2 Yes
Inform member that OMT access is no longer available PM1-3 No Apply RACV Club branding Display Member Portfolio PM1-10
OMT System requests policy or product information PM1-13 OMT System presents product/ policy information PM1-15
OMT System requests product or policy document PM1-18
No Member eligible to view COI? PM1-23 OMT System presents product/ policy document PM1-20 Yes OMT System informs member or COI ineligibility PM-31
COI emailed to MemberYes
OMT System provides hyperlink to existing racv.com.au payment services PM-34
Online Customer Services R1C5
Update Details R1C4
PM1-29
Racv.com .au OMT System presents COI
PM1-7 OMT System requests Member status and membership type PM1-4 Apply RACV Member branding PM1-8
OMT System requests COI information PM-24
PM-26
RACV Systems
Yes Member status and membership type returned (YOM & Card Colour) PM1-5 RACV Club Member? RACV Membership status determined (Active/Inactive) PM1-9 Policy or product information returned PM1-14 Product or policy document identifier returned PM1-19 COI information returned PM-25
No
PM1-6
Figure 3 - Flow from R1C2 Capabilities Requirements
OMT My Portfolio Manager.pdf
Page 12 of 28
5.2 Design overview My Portfolio Manager (BR-301)

5.2.1 L3 Activity Model Error! Reference source not found.Figure 4 shows the activity model of the Member Portfolio process.
Figure 4 - L3 My Porfolio Manager Process R1C2
Page 13 of 28
Portfolio Manager Process R1C2 L3.pdf
Comment [UBR1]: PDF not extracted to right paper. It should be on A3 with FIT TO PAGE property set Field Code Changed
Portfolio Manager Process R1C2 L3.pdf
Page 14 of 28
The above figure shows the complete Member Portfolio process starting from retrieving List of Businesses for Member to Retrieving specific product details. Steps involved are as following: 1. The List of Products related to the Logged in member is retrieved and displayed. 2. When member clicks on one of the products listed on the portfolio, the corresponding contract/ policy details are retrieved and displayed. 3. Member is provided with an option to view additional Product or Policy information documents like Brochures, PDS, and SPDS 4. Member is also provided with an option to view the COI for insurance products, in case the eligibility criteria is met to view the COI. 5.2.2 Portal components
MyPortfolioManager MyPortfolioPortlet OMTMyPortfolioPortletView getClubType() getERASummary() getEHASummary() getVehicleInsuranceSummary() getHomeInsuranceSummary() printPortfolio()
Portal Page Portlet in page View Rendered Operations
5.2.3
Services components
Operation Name Messages
Formatted Table
Service Name
MemberPortfolioMgrProcess
retrieveMemberPortfolio
retrieveMemberPortfolioRequ est retrieveMemberPortfolioResp onse
5.2.4 NA
Database components
Page 15 of 28
5.3 Design Overview Member Details (BR-301)

5.3.1 L3 Activity Model
Comment [UBR2]: Image should be replaced as it is a blurred image.
Figure 5 - L3 Member Details R1C2

Comment [UBR3]: Same PDF file comment applies here
Party Service R1C2 L3.pdf
Field Code Changed
Party Service R1C2 L3.pdf
Page 16 of 28
Steps to get Member details 1. Party Entity Service provides multiple operations, one of which is retrieveParty() , which will be used to retrieve the Member details. 2. Party Service uses Hub wrapper to integrate with Cornerstone to invoke Retrieve Party service. 3. Retrieve party service provides different level of information based on inquiry level 5.3.2 Portal Components
MemberDetails MemberDetails OMTMemberDetailsPortletView getMemberDetails()
5.3.3
Services Components
Formatted Table
Service Name
PartyService
retrieveParty
retrievePartyRequest retrievePartyResponse
5.3.4 NA
Database Components
Page 17 of 28
5.4 Design Overview Expired and Cancelled Products (BR-301)

Comment [UBR4]: Image quality
Figure 6 - L3 Expired and Cancelled ProductsR1C2
Steps to retrieve expired and cancelled products. 1. Party Services retrieveLOB() operation will be used to retrieve the List of Products related to a member. 2. Party Service uses Hub wrapper to integrate with Cornerstone to invoke Retrieve LOB service. 3. Retrieve LOB service provides different level of information based on inquiry level. 4. Service can also retrieve products with different product status Active, Inactive or all products based on inquiry status set on this service.
5.4.2
Portal Components
OMTExpiredAndCancelledProducts OMTExpiredAndCancelledProductsPortlet OMTExpiredAndCancelledProductsPortletView - getExpiredAndCancelledProductsDetails()
5.4.3
Services Components
Service Name
PartyService
retrieveLOB
retrieveLOBRequest retrieveLOBResponse
Page 18 of 28
5.4.4
Database Components
5.5 Design Overview View ERA Product Details (BR-301)

Comment [UBR5]: Image quality for all the images provided to be checked
Figure 7 - L3 View ERA Product Details R1C2
Contract Service R1C2 L3.pdf

Field Code Changed
Contract Service R1C2 L3.pdf
Note: Currently its assumed Product details related to member will be returned by Corner Stone Hub. This service will be modified if product details need to be directly retrieved from backed ERA Product System instead of going through Cornerstone Hub. 1. Contract Entity Service provides multiple operations of which is retrieveContract() will be used to retrieve the ERA product details. 2. Contract Service uses Hub wrapper to integrate with Cornerstone to invoke Retrieve Contract service. 3. Retrieve contract service provides different level of information based on inquiry level 5.5.2 Portal Components
ERAProductDetails ERAProductDetailsPortlet ERAProductDetailsPortletView getERAProductDetails() printDetails()
Page 19 of 28
5.5.3
Services Components
Service Name
ContractService
retrieveContract
retrieveContractRequest retrieveContractResponse
5.5.4
Database Components
5.6 Design Overview View EHA Product Details (BR-301)

Figure 8 - L2 View EHA Product Details R1C2
For PDF view, refer to ContractService R1C2 L3.pdf Note: Currently its assumed Product details related to member will be returned by Corner Stone Hub. This service will be modified if product details need to be directly retrieved from backed EHA Product System instead of going through Cornerstone Hub. 1. Contract Entity Service provides multiple operations of which is retrieveContract() will be used to retrieve the EHA product details. 2. Contract Service uses Hub wrapper to integrate with Cornerstone to invoke Retrieve Contract service. 3. Retrieve contract service provides different level of information based on inquiry level 5.6.2 Portal Components
EHAProductDetail EHAProductDetailsPortlet EHAProductDetailsPortletView getEHAProductDetails() printDetails()
Page 20 of 28
5.6.3
Services Components
Service Name
ContractService
retrieveContract
5.6.4
Database Components
5.7 Design Overview View Home Insurance Product Details (BR-301)

Figure 9 - L3 View Home Insurance Product Details R1C2
For PDF view, refer to ContractService R1C2 L3.pdf Note: Currently its assumed Product details related to member will be returned by Corner Stone Hub. This service will be modified if product details need to be directly retrieved from backend Insurance System Huon instead of going through Cornerstone Hub. 1. Contract Entity Service provides multiple operations of which is retrieveContract() will be used to retrieve the Home Insurance details. 2. Contract Service uses Hub wrapper to integrate with Cornerstone to invoke Retrieve Contract service. 3. Retrieve contract service provides different level of information based on inquiry level 5.7.2 Portal Components
HomeInsurance OMTHomeInsurancePortlet OMTHomeInsurancePortletView - getHomeInsuranceDetails() - printDetails()
Page 21 of 28
5.7.3
Services Components
Service Name
ContractService
retrieveContract
5.7.4
Database Components
5.8 Design Overview View Vehicle Insurance Product Details (BR-301)

Figure 10 - L3 View Vehicle Insurance Product Details R1C2
For PDF view, refer to ContractService R1C2 L3.pdf Note: Currently its assumed Product details related to member will be returned by Corner Stone Hub. This service will be modified if product details need to be directly retrieved from backend Insurance System Huon instead of going through Cornerstone Hub. 1. Contract Entity Service provides multiple operations of which is retrieveContract() will be used to retrieve the Vehicle Insurance details. 2. Contract Service uses Hub wrapper to integrate with Cornerstone to invoke Retrieve Contract service. 3. Retrieve contract service provides different level of information based on inquiry level
5.8.2
Portal Components
VehicleInsurance OMTVehicleInsurance OMTVehicleInsurancePortletView
Portal Page Portlet in page View Rendered
Page 22 of 28
Operations
- getVehicleInsuranceDetails() - printDetails()
5.8.3
Services Components
Service Name
ContractService
retrieveContract
5.8.4
Database Components
5.9 Design Overview View/Print/Email Certificate of Insurance (COI) (BR-301)

5.9.1 L3 Activity Model Approach to retrieve COI information is still under review. 5.9.2 Portal Components
VehicleInsurance/HomeInsurance OMTCertificateOfInsurancePortlet OMTCertificateOfInsurancePortletView getCOIDetails() createPDF() sendEmail() printCOI()
5.9.3
Services Components
Service Name
MemberPortfolioMgrProcess
retrieveCOI
retrieveCOIRequest retrieveCOIResponse
5.9.4
Database Components
5.10 Design Overview View Supporting Product Policy Details (BR-301)

5.10.1 L3 Activity Model Approach to retrieve supporting policy information is still under review.
Page 23 of 28
5.10.2 Portal Components

Portal Page Portlet in page View Rendered Operations ERAProductDetails/EHAProductDetails/VehicleInsurance/HomeInsur ance ProductPolicyDetails ProcuctPolicyDetailsPortletView - getProductType() - getPurchaseDate() - renderContent()
5.10.3 Services Components

Service Name Operation Name Messages
MemberPortfolioMgrProce ss
retrieveProductDocume nt
retrieveProductDocumentReq uest retrieveProductDocumentRes ponse
5.10.4 Database Components
5.11 Design Overview View Club Product Details (BR-301)

Figure 11 - L3 View Club Product Details R1C2
For PDF view, refer to ContractService R1C2 L3.pdf

Page 24 of 28
Note: Currently its assumed Product details related to member will be returned by Corner Stone Hub. This service will be modified if Club product details need to be directly retrieved from backend RACV Club System instead of going through Cornerstone Hub. 1. Contract Entity Service provides multiple operations of which is retrieveContract() will be used to retrieve the Member Club details. 2. Contract Service uses Hub wrapper to integrate with Cornerstone to invoke Retrieve Contract service. 3. Retrieve contract service provides different level of information based on inquiry level 5.11.2 Portal Components
Portal Page Portlet in page View Rendered Operations ClubDetails OMTClubDetailsPortlet OMTClubDetailsPortletView - getClubDetails() - printDetails()
5.11.3 Services Components

Service Name Operation Name Messages
ContractService
retrieveContract
5.11.4 Database Components
Page 25 of 28
Appendix 1: Data Models

OMT_LINK_STATUS OMT_LOGIN_TEMP OMT_TEMP_ID_PK EMAIL MEMBER_NUMBER FIRST_NAME SURNAME DOB COUNTRY STREET_ADDRESS SUBURB STATE POSTCODE PHONE_NUMBER PASSWORD SECRET_Q_1_ID_FK SECRET_ANSWER_1 SECRET_Q_2_ID_FK SECRET_ANSWER_2 SECRET_Q_3_ID_FK SECRET_ANSWER_3 PK FK1 OMT_HUB_USER RACV_USER_ID_PK OMT_ID_FK STATUS LAST_ACTIVE COMPLETED_DATE OMT_SESSION_ID PK FK1 ID_PK OMT_ID_FK LINK VALIDITY_IN_MINUTES LAST_TRAN_TIME
*
OMT_LOGIN
OMT_PWD_STATUS PK FK1 ID_PK OMT_ID_FK PASSWORD LAST_TRAN_TIME
* *
PK
OMT_ID_PK EMAIL LOGIN_ID PASSWORD PWD_LOCK_ATTEMPTS PWD_LOCK_TIMESTAMP IS_ACTIVE LOCK_BY_SCV LAST_TRAN_TIME SECRET_Q_1_ID_FK SECRET_ANSWER_1 SECRET_Q_2_ID_FK SECRET_ANSWER_2 SECRET_Q_3_ID_FK SECRET_ANSWER_3
FK1 FK2 FK3
SECRET_QUESTIONS PK QUESTION_ID QUESTION
FK1
FK2 FK3
* *
Figure 12 - OMT R1C1 Entity Relationship diagram
Appendix2: Process Model Levels

This section, which describes Process Model Levels in general, will be issued as a separate document. It should not be part of Technical Design Overview documents, but is included to this document, as first Technical Design Overview document released, to aid understanding.
The proposed process models provided in the Technical Design Overview are divided into levels. The concept of levels exists in two ways in business process modelling.
7.1 BPMN Levels

Models developed for the OMT project follow the BPMN (Business Process Modelling Notation) standard. BPMN is a standard for business modelling notations. It is concerned with shapes, symbols and structures used irrespective of the business context. The BPMN standard distinguishes between three levels: BPMN Level 1: Descriptive BPMN At this level the shapes and symbols provided are a limited set and the rules of modelling are relaxed to be readily understood by non technical business users. For the OMT project, the models provided by business should merely satisfy BPMN Level 1 requirements. BPMN Level 2: Analytical modelling At this level, all of the BPMN shapes and symbols are available and all of the modelling rules should be followed. Models at this level are still concerned with a business oriented perspective in the sense that the models are restricted to what can be seen on diagrams. For the OMT project, BPMN Level 2 models should expansions of the Level 1 models, and be developed by technical personnel. BPMN Level 3: Executable models
Page 26 of 28
At this level there are no additional shapes and symbols to those used in BPMN Level 2, and the rules are similar too. The difference is that executable details are fully captured as standard BPMN attributes in BPMN Level 3 models. For example, BPMN Level 3 models will include the message structures passed from one activity to the next, which enables the model to run as simulation. Currently there is no RACV requirement for models to be executable. However, it is a current TGC requirement that Technical Design Overview documents should provide insight into messages, database structures, services and screens. Consequently OMT models delivered by HCL should partially be developed at BPMN Level 3.
7.2 Business process modelling levels

Business process modelling, on the other hand, focuses on the process itself and includes both business and technology elements. In business process modelling the notion of levels refers to the industry practice of vertically decomposing models into more and more detailed sub-models. There are many proposals as to how this should be done (see for example Infosys comparison ). As a common trend, however, models are grouped at the following three levels, at least: 1. Conceptual a business viewpoint. 2. Process - The structure of how the business operates. 3. Procedural the detail of specific tasks. This grouping is considered sufficient for the OMT project. Note, a model at any level can be further subdivided into sub-models at the same level. Levels ought to express the context; it is not merely an expression of the vertical position. In addition to the above, it should be mentioned that Level 0 models have an industry wide perspective. They express how the business (such as RACV) interacts with players in industries in a demand and supply relationship. Consequently the levels proposed for the OMT project are: Level 0: Industry Models Express how the business (e.g. RACV) interacts with players in industries in a demand and supply relationship. Level 0 modelling is usually a corporate activity, and is out of scope of Technical Architecture Overview documents. Level 1: Business Models Express how business services interact with industry players. In the OMT project these services generally equate to business functions or capabilities. This level does not distinguish between individual actors or systems, but may distinguish between product offerings and organisational units. Level 1 models are developed and included in OMT Technical Architecture Overview documents. Level 2: Process Models Express the main processes within business areas to deliver products through human tasks and IT operations. In the OMT project a Level 2 model would typically describe the process behind single capability requirements, such as Member Login or Member Registration. Level 1 models describe, for example, how these capabilities work together to provide services to members. Level 2 models are included in OMT Technical Architecture Overview documents. Note some of these models, if developed, may contain only a single Level 3 process, and nothing else. In those cases an acceptable approach could be for Level 1 models to refer to Level 3 models directly. Level 3: Activity Models
Page 27 of 28
Express processes of lowest level tasks modelled with activities associated with roles and systems functions.
7.3 Level of models provided in OMT capability requirement documents

OMT capability documents released to date provide a process flow model for each capability requirement. The models provided by business are not structured into levels, but are used as inputs for technical personnel to develop models in WebSphere Process Modeller (WPM), where they are restructured and refined to produce the models provided in the Technical Design Overview documents. For ease of mapping between OMT capability requirements and the models developed in WPM, the names of model developed for the OMT project will follow the following convention: L<Level#> <Model name> [(R<Release#>[C<Capability#>])] For example, a model with the following name: L1 OMT Process (R1C1) Means: This is a level 1 model of the OMT Process which is specified as a requirement in the OMT Release 1 Capability 1 document. Note that the release and capability numbers are only added when applicable.
Page 28 of 28

Technical Design Overview R1C2

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Technical Design Overview R1C2

Загружено:

Авторское право:

Доступные форматы

Online Member Transactions (OMT)

Release 1 Capability 2 - My Portfolio Manager Technical Design Overview

Version: 0.1 Status: Draft Date: 30 August 2011 Owner: RACV

Governance Approval Version Date TGC comments Governance Member

Formatted: Font color: Text 1

document1technical design overview r1c2 2011-09-08 am.docx

DOCUMENT PURPOSE SCOPE

HIGH LEVEL MODELLING

OMT LANDING PAGE (BR-1)

Formatted: Font color: Text 1

document1technical design overview r1c2 2011-09-08 am.docx

Services Components Database Components

APPENDIX 1: DATA MODELS APPENDIX2: PROCESS MODEL LEVELS

Formatted: Font color: Text 1

document1technical design overview r1c2 2011-09-08 am.docx

The Technical Design Overview satisfies three purposes:

2.1 Document scope

2.2 Business scope

Formatted: Font color: Text 1

document1technical design overview r1c2 2011-09-08 am.docx

Product/ Policy Details

Need to see the feasibility to deffer till R1C6

Product and Policy Summary

Availability of IAL/HUON environment

what systems to connect to based on the IAL release timelines

R1C2 R1C2 R1C2 R1C2 R1C2 R1C2 R1C2 R1C2

183 184 185

Formatted: Font color: Text 1

document1technical design overview r1c2 2011-09-08 am.docx

Release R1C2 R1C2 R1C2 R1C2

OMT Id 186 185 187

Product/ Policy Details

Product and Policy Summary

Availability & connectivity to HUON environment

Impact on deliverables and timelines if appropriate information is not provided on time

Formatted: Font color: Text 1

document1technical design overview r1c2 2011-09-08 am.docx

R1C2 R1C2 R1C2 R1C2 R1C2

Impact on deliverables and timelines if appropriate information is not provided on time

Possible rework if gap analysis is not confirmed

Formatted: Font color: Text 1

document1technical design overview r1c2 2011-09-08 am.docx

High level modelling

4.1 Level 1 Business Models

Formatted: Font color: Text 1

document1technical design overview r1c2 2011-09-08 am.docx

Figure 1: Level 1 OMT process

Formatted: Font color: Text 1

document1technical design overview r1c2 2011-09-08 am.docx

4.2 Level 2 Process Models

Figure 2: L2 Landing Page Process (R1C2)

Formatted: Font color: Text 1

document1Technical design overview r1c2

OMT Landing Page (BR-1)

OMT My Portfolio Manager

Member logs into OMT

Member Selects Action

Member selects to view policy or product information PM1-12

Member OMT Account active? PM1-2 Yes

OMT System requests product or policy document PM1-18

COI emailed to MemberYes

OMT System provides hyperlink to existing racv.com.au payment services PM-34

Online Customer Services R1C5