Version: 6.3.3

Plan Missions

This page provides instructions and best practices for creating and planning missions for campaigns.

Prerequisites

Before continuing be sure that you have completed the activities on the following page:

Prepare Campaigns

Add Missions

Missions are a key component of a Campaign that are meant to achieve a goal state. Missions use interventions that are optimized for cohorts to achieve the desired goal. Missions are tested and measured by running simulations using synthetic or simulated datasets prior to deployment to production.

  1. Log in to Fabric Console and select a Project.

  2. Click the Campaign Summary card.

  3. Click Start (if Missions have not been added to the Campaign) or Add Mission (if Missions have already been added).

  4. Enter a brief but descriptive Title for the Mission.

  5. Review the auto-generated Name for the Mission. By default this is auto-generated. You may toggle the auto-generated switch to off and edit the name or enter a unique URL-friendly name. (Names must be 20 characters or fewer)

  6. Enter a Description that will be meaningful to collaborators.

  7. Select a Cohort that is the target of the Mission. The selection filters the Goals available for the Mission; only Campaign Goals that have a KPI that targets the selected Cohort are available for selection.

  8. Click Next at the bottom left.

  9. Select a Goal for the Mission. The selected Goal provides KPIs and measures that the interventions target.

  10. Compose a Goal Condition expression that defines the Goal Condition (e.g. has_flu_shot.eq(true). The expression should reflect the desired state for a single member of the Cohort after the interventions have been executed. The Profile Schema library is displayed as a reference. These are the attributes available for the query.

    Best Practices: A collaborator who is a domain expert should be enlisted to define Goal State expression.

  11. Click Next at the bottom left.

  12. (Optional) To add simulated attributes to the mission click Add Attribute. Simulated attributes are attributes that don't yet exist, but that you may require for simulating a mission.

    • a. Enter an Attribute Name.
    • b. Select a Data Type for the attribute (Options: Integer, Double, Boolean, String).
    • c. Provide an Initial Value to assign to the attribute.
    • d. Click Save below the final field.

    A table of Simulated Attributes is generated after saving the new attribute.

    Add another simulated attribute by clicking Add Attribute.

    Edit or Delete Calculated Attributes

    To the right of each simulated attribute is a vertical ellipsis action menu that allows you to:

    • Edit: Opens the configuration wizard, so you can make changes.
    • Delete: Removes the attribute. Use this action with extreme care because removing an attribute may have downstream consequences if it is used in an intervention.
  13. Click Save at the bottom of the page to save the Mission.

When the Mission is saved, it is added to the Missions list on the Campaign Summary page. The default status displayed for Mission is EDITING. After you deploy the Mission or Campaign the status is displayed as DEPLOYED.

Add Interventions

About Interventions

As a prerequisite to adding interventions, you must have a Mission created.

Interventions are the specific activities that are used to generate the models that are tested via simulations and ultimately deployed to production. Interventions are composed of:

  • Cost: The cost of the action measured on a scale of 0.01-1 that evaluates factors like effort, financial expenditure, time required to implement, or other factors that must be considered in the decision making process. (default is 0.01)
  • Wait-time: The amount of time to gather Feedback for the Intervention during runtime. When this time has elapsed Feedback is no longer collected.
  • Pre-condition (optional): The condition that must be in place before an intervention can be undertaken written as a logical or boolean expression. For example a pre-condition of sending a phone reminder is that the cohort members must have phone numbers provided in the profiles. Pre-conditions are defined with queries that reference one or more Mission conditions. When you add a pre-condition, it is added to a library of conditions, so it can be re-used across Interventions for the Mission.
  • Effect: The desired end-state for the intervention written as a logical or boolean expression. For example: 5% of the cohort group makes an appointment after receiving 3 notifications.
  • Action: The Action is what will execute for the intervention when the Campaign is deployed. Actions are optional for running mission simulations, but required in order to deploy interventions.

A Mission may have one or more Interventions.

Add Interventions to a Mission

  1. Log in to Fabric Console and select a Project.

  2. Click the Campaign Summary card.

  3. Click the Mission card to open the Interventions tab where you can add and edit interventions.

  4. The Mission Goal is displayed on the left. Under that click Add Intervention.

  5. A panel opens on the right that displays the intervention elements that can be configured (Cost, Pre-Condition, Effects, Actions). When you add elements to the intervention, the composition panel opens over the summary panel.

  6. Enter a brief but descriptive Name for the Intervention.

    Best Practice: Make sure the name is brief but descriptive enough that collaborators can understand the Intervention at a glance.

Set the cost

Cost represents any variable that effects the execution of the intervention such as labor, time, difficulty, or monetary outlay. The cost can be considered as relative to other interventions configured for the campaign. The simulation considers cost in its plan ranking.

  1. Set the slider to represent the Cost of the intervention.

Set the Wait Time

Wait time is the amount of time that the Mission Runtime Cycle collects feedback data for the Intervention.

  1. Set the Wait Time.
  2. Select the Wait Time Units.

Since different interventions have different Wait Times, a Cohort member subset cycle runs until the longest Wait Time has elapsed, but feedback data is only collected for the set Wait Time for each Intervention.

Add Pre-Conditions

A Pre-condition is defined using an expression. The expression represents the conditions that must be met for the intervention to be enacted.

An intervention can have only one Pre-condition. To change the pre-condition hover over the box and click the trash can icon to remove an existing pre-condition expression. Then follow the instructions below to add a new expression.

The attributes available for the expression are shown in the Profile Schema Library to the left of the configuration panel.

  1. (Optional) In the Intervention summary panel, click Add pre-condition.
  2. In the Pre-conditions panel that opens construct an expression based on schema attributes and logic expressions that define the Pre-condition. Start typing to expose a list of schema attributes and expressions. Click on attributes and expressions to add them to the Pre-condition expression.
  3. Click Yes to add the Pre-condition expression to a library where it can be selected for other interventions.
  4. Enter a Name for the Pre-condition.
  5. Click Continue at the bottom of the panel when you are done.

Manage Pre-conditions

  1. Click + Add Pre-condition to open the attributes panel to the left.
  2. Scroll down the Attribute Library until you get to Pre-conditions.
  3. Click the vertical ellipsis.
  4. Click Edit Pre-conditions.
  5. A list of Pre-conditions that have been added to the library is displayed.
  6. In each row click the vertical ellipsis menu to edit or delete record.
  7. Click the Add Pre-condition button to open a panel where you enter the name and expression.
  8. Click Save to add the Pre-condition to the list.

Add Effects

Effect expressions reflect the conditions that must be met for the intervention to be considered successful on an individual cohort level. The effect expression should be closely aligned with the KPIs for the goal you selected for the Mission (e.g. has_flu_shot.eq(true))

One or more Effects may be added to an intervention.

  1. In the Intervention summary panel click Add Effect. The compose panel opens.
  2. Enter an Effect Name.
  3. In the Effect panel that opens construct an expression based on schema attributes and logic expressions that define the Effect. Start typing to expose a list of schema attributes and expressions. Click on attributes and expressions to add them to the Effect expression.
  4. Select the expected Probability for this effect by moving the slider. Probability is measured from 0.01-1 (0.01 is the default.)
  5. Click Continue at the bottom of the panel to add the Effect to the summary.
  6. To add another Effect click + above and to the right of the box.

To remove an Effect hover over the box to expose the trash can icon. Click to remove the Effect expression.

Add Actions

Next, you may add the Action for the intervention. An Action is run when the intervention is deployed, so it may be added later in the process, after simulations have been used to determine the most effective interventions.

  1. In the Intervention summary panel click Add Skill.
  2. Select a pre-configured Skill that when deployed and invoked runs the mission intervention in production.
  3. Click Continue to save the Action to the summary panel.

Save the Intervention Configuration

Click Save to save the Intervention configuration. A graphical display allows you to view interventions on the Interventions canvas. (Tab at center top of screen)

Click Add Intervention to add another intervention to the mission.

When you run a simulation, interventions may be combined into plans that can be reviewed in a later step.

Delete Missions

  1. Click the vertical ellipsis menu in the Mission card that you want to delete.
  2. Click Delete.
  3. Verify that you want to delete to mission.

Next Steps

Run mission simulations