Document process v7
0 likes66 views
The document discusses business process management and component thinking. It provides definitions and concepts related to business processes, including activities, tasks, inputs, outputs, and stakeholders. It also discusses documenting processes, including procedures, workflows, user interfaces, data rules, and integration. Examples of processes, sub-processes, procedures, and user interfaces are demonstrated.
Document process v7
- 3. WHY? Inaccurate requirements management Do not meet Original Goals vs. Business Objectives Inadequate /Poor Communication Source : http://www.pmi.org/learning/pulse.aspx
- 4. AETINS’ APPROACH ISF Guidance BIZ VCB of ISF BIZ BPM of ISF BPM BWL Generate d BPM Practical Guidance of ISF THINK CONSOLIDATE UNDERSTAND
- 5. HOW? Requirement Specification Technical Specification Design Specification Development 100% by Business People 100 % by Business- Techno People 100% by Technical People with Analytical Skills 100% by Technical People with Analytical & Programming Skills TRACEABILITY 1 432
- 6. Composition of Enterprise Business Processes Biz Rules Product Rules Service Rules Workflow Documents
- 7. BUSINESS PROCESS MANAGEMENT Body of principles, methods and tools to design, analyze, execute and monitor business processes, with the ultimate goal of improving them.
- 8. Documenting a Process Process, Sub Process, Sub- Sub Process Procedures Workflows UI & Work Buddy (WB) Data Rules Business Company Policies Statutory Requirement Defacto (Country, Industry) BRIA Integration Action Decision/ Inference Computation Constraint
- 9. IMPORTANT DEFINITIONS TERM DEFINITION PROCESS A business process or business method is a collection of related, structured activities and tasks that produce a specific service or product (serve a particular goal) for a particular customer or customers ”a collection of activities that takes one or more kinds of input and creates an output that is of value to the customer.” ACTIVITY A business process is broken down into various activities TASK A unit of an Activity
- 10. “A business process is as collection of interrelated events, activities and decision points that involve a number of actors and objects, and that collectively lead to an outcome that is of value to at least one customer” Dumas, 2013
- 12. Input Output Stakeholder Objective Function 1 Function 2 THE PROCESS- ACROSS FUNCTIONS
- 13. Location 1 Location 2 Input Output Stakeholder Objective THE PROCESS – ACROSS LOCATIONS
- 14. DEMO
- 15. EXAMPLE PROCESS
- 17. PROCEDURES Process/ Sub Process / Sub-Sub Process Activity Tasks Quote Capture quotation • Fill up proposal form • Proof of documents Check insurability • Check the decision on Agent Status, Insured Status and Insured Age Perform auto underwriting • NA Procedure: How activity is executed/performed Tasks: The smallest identifiable and essential piece of job that serves as a unit of work
- 18. WORKFLOW Process/ Sub Process / Sub-Sub Process Activity Task Role Quote Capture quotation • Fill up proposal form • Proof of documents Internal staff/ Intermediary Check insurability • Check the decision on Agent Status, Insured Status and Insured Age System Perform auto underwriting • NA System
- 19. USER INTERFACES
- 20. WORK BUDDY SUPPORTING ITEMS (For UNDERWRITER) Blacklist Quotation History Review Renewal Claim Details Recent Transactions BookmarksDraft the UI
- 21. UI & WORK BUDDY INVENTORY Role User Interface Work buddy Intermediary Capture quotation screen NA Internal Staff Capture quotation screen NA Underwriter • Underwrite quotation page • Loading/discount screen • Accept/reject the proposal Underwriting work buddy
- 22. DATA REPOSITORY Group Category Capture Data Description/Content (Business Term) Editing (N, A, AN) Validation UI Label UI Name Other Related Data Policy Holder /Participant Details Participant type Individual/ Company Insured / Policy Holder Type A,1 N/A Participant Type Capture Quotation Screen • Certificate of vessel • Claim history Policy Holder /Participant Details Company /insured details a) ID Code b) ID No c) Name d) Address a) Identification type b) Identification Number c) Name d) Address a)A,? b) AN,? c) A,? d) AN, 3 lines N/A a) Identification Code b) Identification No c) Name d) Address -postcode -state Policy Details Period of insurance Commence ment & expiry date Commencement Date & Expiry Date N,8 DD/MM/YYYY Commencement date Expiry date Risk Details Type of cargo Meat, paper, dairy etc. Cargo Type A,? N/A Cargo Type Risk Details Type of packing Wooden box, crates, etc. Packaging Type A,? N/A Packaging Type Risk Details Voyage description Destination from & to Voyage From Voyage To A,? N/A Voyage From Voyage To Risk Details Basis of valuation FOB, C&F, CIF etc Basis of valuation A,? N/A Basis of valuation Risk Details Estimate annual Annual Estimate annual turnover N,? N/A Estimate annual turnover
- 23. RULES REPOSITORY Role Business Rules Component Names System • ISF_COMP
- 24. TECHNICAL REPOSITORY Technical Design SpecTechnical Validating and Editing
- 25. BRIA INVENTORY UI Display Data Layout Quotation • Policy holder details • Cargo details • Voyage details • Premium details As example
- 26. REPORT EXAMPLE
- 29. INTEGRATION REPOSITORY Integration Service Input Data Output Data Database integration Quotation details Operational Decision Management (ODM) Integration Insured IC , Date of Birth, Business Registration, Risk Details (Cargo, Vessel, Voyage detail & etc)
- 30. COMPONENT THINKING Policy Holder Policy Premium Risk - Marine Single Voyage Risk – Marine Open Policy Risk – Marine Open Cover Benchmark: System Analysis reduces errors
- 33. ENHANCE USER INTERFACE, WORK BUDDY AND REPORT LAYOUTS * User Interface / Work Buddy design will be enhanced based on the design specified in the Requirement phase.
- 34. (KIV) WORKFLOW TASK ASSIGNED TO DESCRIPTION
- 35. TASK : VARIABLE TASK VARIABLE COMMENTS Capture Quotation dDate Date and time when quotation is captured vUserName User name of the person who captures quotation vTaskName Name of the task performed by the user vIPAddress IP Address of the user In addition to the INPUT/OUTPUT variables, new variables which are required for programming will be added here.
- 36. (KIV) DATA MODEL
- 37. TASKWISE RULES INPUT OUTPUT vAgentStatus vInsurabilityResult vInsuredStatus nInsuredAge
- 38. VALIDATE INTEGRATION XML Mapping Single Record - S/Multi Record - M Type Description Values/Format Customer Details CustomerDetails ParticipantType S String Pariticipant Type Individual- I or Company- C Upper Case Ex : I IdentificationType S String Type of Identification (PP,NRIC etc..) Format : Upper Case Characters Ex : PP, NRIC … IdentificationNumber S String Identification Number Ex : H3743672 CompanyID S String Company Code Ex : AETINS CompanyBranch S String Branch of the Company Ex: HO Name S String Name of the Company or Individual based on the participant Type Aetins SDN. BHD Address M String Address of the company or Individual PolicyDetails ProductType S String Product Name Ex : TOC DataBranch S String Branch of the login user EX : HOD PaymentType S String Mode of Payment 01 - Cash 02 - Credit Card 03 - Bank Deduction EX : 03 QuotationValidityPeriod S Int Validity period of Quotation Ex : 15 BusinessType S String Type of Business Ex. Direct - D/ Facultative Inward - FEx : D TransactionCurrency S String Currency of Transaction Ex : MYR AgentDetails M String Agent Details Capture Proposal Details To Store the Proposal Details and Create Quotation No. Valid input XML (refer the RequestText XML ) Valid output XML (refer the RequestText XML )
- 40. DESIGN This design will detail the implementation of the requirements as defined in the requirements and technical specifications.