Test ModelDigital customer intimacy strategyIT ManagementClaim ManagementProduct ManagementCustomer CareCustomer serviceCustomer relationship managementService channel managementCustomer data managementClaim administrationClaim settlementSocial media appsDigital Media strategySocial Media managementMarketing staffTechnical staffBankFinanceClaimsUnderwritingActuarialInsurance sellingTravel insurance sellingLuggage insurance sellingTake out travel insuranceTake out luggage insuranceCustomer info processingCustomer insurance retrievalInsurance sellerWeb formLuggage insurance departmentLuggage insurance sellerMedical insurance sellerMedical insurance departmentLuggage insurance salesMedical insurance salesSales SupportSales departmentBasic administrationProcess requestFinancial handlingCollect PremiumCustomer informationPremium collectionReceive requestSubmit claimInsurerInsurance PolicyPolicy SummaryOnline InsuranceWeb front-endClaim submissionOnline insurance portfolio and claims managementClaimsVERSA-CLAIMQ-CLAIMApplication ComponentRuby Application ComponentPython Application ComponentC++ Application ComponentP-CONFIGBRIMSSIM-INSUREEnterprise Data WarehouseMarket StatisticsMarket AnalysisProduct AnalysisCandidate Business Rule SetCandidate Product ConfigurationBusiness Analytics SuiteArchiSurance Back Office SuiteHome & Away Policy AdministrationRisk AssessmentCustomer data APIPolicy data APIClaim data APICustomer data accessClaim data managementPolicy data managementPolicy CreationCalculate RiskCalculate PremiumCreate PolicyStore PolicyCustomer file dataDamage claim dataInsurance policy dataFinancial AdministrationAccountingBillingFinancial ApplicationDisplay accounts statusCreate invoiceSend invoiceInsurance Request DataPolicy Creation ServiceThis is the documentation for the policy creation service.Billing Request ReceivedAccounting componentBilling ComponentTransaction administrationAdministrate transcationsLAN L1Front Office application serverBack Office application serverWeb serverUNIX Server FarmUNIX Server nUNIX Server n+1LAN L2MainframeTransaction ServerDBMSMessage QueuingNas File ServerFirewallInternetDatabase ServiceFile ServiceNetwork ServiceApplication server AS1BladeJ2EE Application ServerApplication serverClient deviceMessage queuingInternet Web HostingApplication HostingContent RepositoryApplication ContainerApplication ServerInternet Web ServerArchiSurance general-purpose server clusterArchiSurance back-up server clusterIntermodal FreightLocal TruckingNational Distribution CenterOverseas ShippingManufacturing PlantPre-Assembled Circuit BoardInternal AntennaPlastic CaseAssembly LineVehicle Telematics applianceLocal Distribution CenterDatabase replicationReplication AdministrationHandle local updatesHandle remote updatesMonitor replication statusReplicate database updatesRemote Data replicationDatabase UpdateDomain name serversSingle point of access for all insurance productsKeep high satisfaction ratingFrequent customer complaints (copy)Integrated portfolio and claims managementLoss of customersProvide personal assistance to customerSystems should be customer facingProvide online portfolio and claims managementAdditional personnel cost should be limitedGoverning BoardCIOCEOCFONon-Executive DirectorCustomerCustomer satisfactionShareholder satisfactionStock valueProfitEconomic changesComplaining CustomersLeaving CustomersLack of insight in claim statusInconvenient claim submissionLack of insight in portfolioIncomplete and inconsistent informationHelpdesk SupportLong waiting queuesHigh service timesImprove ProfitabilityIncreased ProfitabilityIncreased RevenueIncreased Market ShareServe Customers wherever they areImprove Customer interactionServices should be available through mobile browsers and appsSolutions should be built with cross-platform frameworksActing in advisory capacityOur company is approachableIntegrated back-office systemSoftwareHardwareBaselineTransition 1Transition 2 Alternative ATransition 2 Alternative BTransition 3TargetCustomer TestingProposed Final DeliverableProgram Application Portfolio RationalizationProject Back-office system integrationProject CRM system integrationCustomer Enhancement ProgramRetire Legacy SystemImplement New CRMCustomer Service ProjectHow to address customer needsArchiSurance OfficeAnd junction for realizing digital intimacy strategyOr Junction (back office suite servers)And Junction Claim Management realizationSocial MediaAnd Junction Transition 1And junction transition 2Junction6Made this a textual strength07 Technology ViewThe layered viewpoint pictures several layers and aspects of an Enterprise Architecture in one diagram. There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the “grouping” relationship for a natural partitioning of the entire set of objects and relationships that belong to a model. The technology, application, process, and actor/role layers belong to the first category. The structural principle behind a fully layered viewpoint is that each dedicated layer exposes, by means of the “realization” relationship, a layer of services, which are further on “serving” the next dedicated layer. Thus, we can easily separate the internal structure and organization of a dedicated layer from its externally observable behavior expressed as the service layer that the dedicated layer realizes. The order, number, or nature of these layers are not fixed, but in general a (more or less) complete and natural layering of an ArchiMate model should contain the succession of layers depicted in the example given below. However, this example is by no means intended to be prescriptive. The main goal of the layered viewpoint is to provide an overview in one diagram. Furthermore, this viewpoint can be used as support for impact of change analysis and performance analysis or for extending the service portfolio.08 View with all Relation TypesThe layered viewpoint pictures several layers and aspects of an Enterprise Architecture in one diagram. There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the “grouping” relationship for a natural partitioning of the entire set of objects and relationships that belong to a model. The technology, application, process, and actor/role layers belong to the first category. The structural principle behind a fully layered viewpoint is that each dedicated layer exposes, by means of the “realization” relationship, a layer of services, which are further on “serving” the next dedicated layer. Thus, we can easily separate the internal structure and organization of a dedicated layer from its externally observable behavior expressed as the service layer that the dedicated layer realizes. The order, number, or nature of these layers are not fixed, but in general a (more or less) complete and natural layering of an ArchiMate model should contain the succession of layers depicted in the example given below. However, this example is by no means intended to be prescriptive. The main goal of the layered viewpoint is to provide an overview in one diagram. Furthermore, this viewpoint can be used as support for impact of change analysis and performance analysis or for extending the service portfolio.04 Motivation ViewThe motivation viewpoint allows the designer or analyst to model the motivation aspect, without focusing on certain elements within this aspect. For example, this viewpoint can be used to present a complete or partial overview of the motivation aspect by relating stakeholders, their primary goals, the principles that are applied, and the main requirements on services, processes, applications, and objectsMade this a textual strength06 Strategy ViewThe layered viewpoint pictures several layers and aspects of an Enterprise Architecture in one diagram. There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the “grouping” relationship for a natural partitioning of the entire set of objects and relationships that belong to a model. The technology, application, process, and actor/role layers belong to the first category. The structural principle behind a fully layered viewpoint is that each dedicated layer exposes, by means of the “realization” relationship, a layer of services, which are further on “serving” the next dedicated layer. Thus, we can easily separate the internal structure and organization of a dedicated layer from its externally observable behavior expressed as the service layer that the dedicated layer realizes. The order, number, or nature of these layers are not fixed, but in general a (more or less) complete and natural layering of an ArchiMate model should contain the succession of layers depicted in the example given below. However, this example is by no means intended to be prescriptive. The main goal of the layered viewpoint is to provide an overview in one diagram. Furthermore, this viewpoint can be used as support for impact of change analysis and performance analysis or for extending the service portfolio.02 Business ViewThe layered viewpoint pictures several layers and aspects of an Enterprise Architecture in one diagram. There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the “grouping” relationship for a natural partitioning of the entire set of objects and relationships that belong to a model. The technology, application, process, and actor/role layers belong to the first category. The structural principle behind a fully layered viewpoint is that each dedicated layer exposes, by means of the “realization” relationship, a layer of services, which are further on “serving” the next dedicated layer. Thus, we can easily separate the internal structure and organization of a dedicated layer from its externally observable behavior expressed as the service layer that the dedicated layer realizes. The order, number, or nature of these layers are not fixed, but in general a (more or less) complete and natural layering of an ArchiMate model should contain the succession of layers depicted in the example given below. However, this example is by no means intended to be prescriptive. The main goal of the layered viewpoint is to provide an overview in one diagram. Furthermore, this viewpoint can be used as support for impact of change analysis and performance analysis or for extending the service portfolio.01 Application ViewUpdated to make this an Application Cooperation Viewpoint
Customer data access now just an access to Customer data file03 Implementation and Migration ViewThe layered viewpoint pictures several layers and aspects of an Enterprise Architecture in one diagram. There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the “grouping” relationship for a natural partitioning of the entire set of objects and relationships that belong to a model. The technology, application, process, and actor/role layers belong to the first category. The structural principle behind a fully layered viewpoint is that each dedicated layer exposes, by means of the “realization” relationship, a layer of services, which are further on “serving” the next dedicated layer. Thus, we can easily separate the internal structure and organization of a dedicated layer from its externally observable behavior expressed as the service layer that the dedicated layer realizes. The order, number, or nature of these layers are not fixed, but in general a (more or less) complete and natural layering of an ArchiMate model should contain the succession of layers depicted in the example given below. However, this example is by no means intended to be prescriptive. The main goal of the layered viewpoint is to provide an overview in one diagram. Furthermore, this viewpoint can be used as support for impact of change analysis and performance analysis or for extending the service portfolio.05 Physical ViewThe layered viewpoint pictures several layers and aspects of an Enterprise Architecture in one diagram. There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the “grouping” relationship for a natural partitioning of the entire set of objects and relationships that belong to a model. The technology, application, process, and actor/role layers belong to the first category. The structural principle behind a fully layered viewpoint is that each dedicated layer exposes, by means of the “realization” relationship, a layer of services, which are further on “serving” the next dedicated layer. Thus, we can easily separate the internal structure and organization of a dedicated layer from its externally observable behavior expressed as the service layer that the dedicated layer realizes. The order, number, or nature of these layers are not fixed, but in general a (more or less) complete and natural layering of an ArchiMate model should contain the succession of layers depicted in the example given below. However, this example is by no means intended to be prescriptive. The main goal of the layered viewpoint is to provide an overview in one diagram. Furthermore, this viewpoint can be used as support for impact of change analysis and performance analysis or for extending the service portfolio.Linked ViewsA view with links to the other views in the model