Initializing DMSample data

Generate the data that you need to fully explore DMSample use cases by creating and running the Initialize Application case. By initializing DMSample data, you populate database tables with sample customer and analytical records, simulate the previous customer interactions and survey results, create simulation data sources, and generate work assignments that you can view in the Case Manager portal.
Before you begin: Configure your operator ID with the following settings:
  • Access group: DMSample:Administrators
  • Team: default@DMOrg

    Figure: Specifying operator access group and team

For more information, see Creating an operator ID.
  1. In the header of Dev Studio, click Create > New > Initialize Application.
  2. On the Initialize Application tab, initialize the case by clicking Start.
  3. Complete all case stages by following on-screen instructions.
    Each stage contains a detailed description of the artifacts that you generate by progressing through the case.
  4. Verify that the system populated Interaction History reports with impressions and responses:
    1. In the header of Dev Studio, click Configure > Decisioning > Monitoring > Interaction History.
    2. Check if the Interaction History reports contain data.
      For example: 

      Figure: Sample Interaction History reports

      Accept rate tab on the Decisioning: Interaction History landing page. The presented chart shows the accept rate for each proposition group. Tablets have the highest accept rate, they are followed by gifts, membership, phones, and tariffs. Insurance coverage has the lowest accept rate.
      Interaction History is the data layer that stores all interactions with customers. The interactions consist of customer responses to given propositions. By providing Interaction History records to a next-best-actions strategy, you can discover which proposition your customer is most likely to accept.
  5. Verify that the system created data sources for Visual Business Director:
    1. In the header of Dev Studio, click Configure > Decisioning > Monitoring > Visual Business Director.
    2. Check if Visual Business Director datasets contain data.
      For example: 

      Figure: Visual Business Director data sources

      Data Sources tab of Decisioning: Visual Business Director. Data sources are Visual Business Director data sets in this application. The data sources listed include: Actuals, Established Professional, Potential Entrepreneur, and Young Professional. The Actuals data source contains Interaction History records. Each data source has a start and end date for monitoring data, and the number of records that pertain to the data source. You can configure the start date for monitoring data by expanding the data source entry.
      With Visual Business Director, you can visualize decision results and fully understand the likely impact of each decision before you make that choice.
  6. Verify if the system created adaptive models:
    1. In the header of Dev Studio, click Configure > Decisioning > Model Management.
    2. Check if the Model Management landing page contains models.
      For example: 

      Figure: Adaptive models on the Model Monitoring landing page

      List of adaptive models on the Model Monitoring landing page
    3. Click a model name to view the reports.

      Figure: Monitoring adaptive model performance

      Monitoring tab of Adaptive model: Sales Model. Chart: success rate and performance for different propositions, for example Samsung Galaxy J7, Huawei P10 64GB, or Apple IPhone SE.
      Adaptive models calculate who is likely to accept or reject an offer by capturing and analyzing response data in real time. With adaptive models, you can select the best offer for your customer without providing information on previous interactions.
  7. Verify that the event browser, which contains the Customer Movie timeline, contains events.
    1. In the navigation pane of Dev Studio, click Records.
    2. Expand the Data Model category, and then click Data Flow.
    3. Click any Data Flow rule that writes data in the event store, for example, Offer CMF.
    4. On the Data Flow tab, right-click the Event summary convert shape, and then click Preview.
    5. On the clipboard page, copy a customer ID from the pxCustomerId property.
    6. In the header of Dev Studio, click Configure > Decisioning > Infrastructure > Customer Movie > Event Catalog.
    7. In the Action column, start a run for the data flow that you selected in step 7.c by clicking Start.
    8. When the data flow runs in the event catalog are completed, click the Event Browser tab.
    9. In the Search criteria section, in the Customer ID field, enter the customer ID that you copied in step 7.e.
    10. Click Find events.
    11. Check if the customer timeline contains events of various types.
      For example: 

      Figure: Events for customer CE-715 in the event browser

      Search criteria; Search using Customer ID; Customer ID CE-715; Time range Last year; Three dropped calls in the last 24 hours; Basic Coverage offered, outcome was Reject; -15 on Silver subscription S-9
      In the event catalog, you can create multiple event types to collect customer data from specific input streams or batch uploads. With Customer Movie, you can make informed and personalized decisions for your customers.
What to do next: Populate predictive models reports by generating responses. For more information, see Initializing predictive model monitoring.