Exhibit D - Forms of Statement of Work

Deliverables/Tasks

Acceptance Criteria

CMX will configure the standard Modules to house and maintain Internal and/or External organizations and locations.

Users are given the proper experience when logged into CMX1 Platform and can fulfill the primary functions based on CMX’s standard configuration when interacting with the Modules available within the system to manage and maintain organization and organization location records in the system.

CMX will configure the standard Modules for Users, and User profiles, to create the experience necessary for distinct CUSTOMER “internal” User types (e.g. program admin, food safety, QA, procurement, etc.), and “external” User types (e.g., distributor, supplier, auditor, etc).

Users are given the proper experience when logged into the CMX1 Platform and can fulfill the primary functions based on CMX’s standard configuration when interacting with the Modules available within the system. Profiles established on the User app, govern how a User can interact with all Modules, and profile granularity is based on the level of detail the then-current system can provide about any User.

CMX will configure the standard data firewall levels for internal and external Users, which controls User access to records.

Users of all profiles can be given explicit access to all data, or only certain data, as needed, by the levels CUSTOMER deems necessary. 

CMX will configure the standard landing page(s) that provides action-oriented information and/or navigational links relevant for all User types.

CUSTOMER Users that reach the CMX1 Platform through login arrive on the landing page that provides them the appropriate experience.

Deliverables/Tasks

Acceptance Criteria

CMX/CUSTOMER will jointly review standard workflow for on-boarding suppliers and distributors, and based on the configuration, will then determine if any changes need to be made for the following processes: 

• New supplier/distributor (legal only)
• New supplier/distributor + facilities (without product)
• New supplier + facilities (with product)
• Existing supplier/distributor, new facilities (without product)
• Existing supplier, new facilities (with product)
• Existing supplier facility + product

CMX will work with Customer to understand all configurations required for enabling the on-boarding workflows within standard product capabilities, from instantiation through to completion, including all expected permissions/access rules, form inputs, document attachments, notifications/escalations, and important milestones/timestamps that need to be reported on.

Users with proper permissions can create an onboarding request to onboard new/existing partners and products, and these records will go through proper workflows, ensuring all necessary information is collected and vetted in advance of final approval letter being issued. 

Information collection will be facilitated through one or more of CMX standard sub-processes. CMX will configure forms within these sub-processes to collect information Customer requires in a manner consistent with the standard configuration of product capabilities. 

CMX will configure a final approval letter based on existing design to meet customer business requirements by introducing Customer logo, and verbiage changes where necessary. 

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

CMX will setup documents as per CMX’s standard configuration settings in Document Module to ensure that documents collected during the on-boarding process are correctly managed by the system.

Documents collected during onboarding that need to be replaced/updated will expire and interested parties will be notified such that updated documents can be added and approved through the system.

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

CMX will enable all navigational elements & queues necessary to allow organizations and CUSTOMER Users to participate in the on-boarding process of suppliers, distributors, contacts, and documents post launch.

Users (both internal and external to CUSTOMER) with proper permissions can access queues, filter/search them to easily find and navigate into on-boarding records.

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

CMX will configure WRM to support the correct approval assignments.

Workflows will include the following elements that Customer elects to leverage in the configuration (all or some of the following): 

1. Supplier information worksheet (organization level) w/ supporting documents
2. Facility capabilities questionnaire (organization location level) w/ supporting documents
3. 1 or more of the following sub-processes
1. Food ingredients questionnaire
2. Facility audit
3. Labels & graphics
4. Supplier ingredient sourcing 
5. Facility and/or corporate documents

Approval steps will be created through workflow role management application (“WRM”) to ensure the correct Customer internal User reviews each form/sub-process as per Customer business requirements. WRM will include a configuration such that assignments for key business processes can be made by the role individuals play within their respective brands.  

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

CMX will enable status-driven email notifications, and time-based escalations to facilitate on-boarding workflow as specified in the final requirements.

When an action item is assigned, the system will send out an email notification with a link to the record that requires attention to the responsible party. 

CMX will enable existing summary task email notifications as desired by Customer (daily and/or weekly task summary reports).

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

CMX will create and/or update information in the Supplier, Distributor or Contact profile with information captured during onboarding. 

Documents and records of various types (e.g. supplier, facility, contacts, etc.) are created & updated in a manner consistent with the information collected during onboarding specific to Customer unique configuration(s). All records created have necessary attributes and those attributes are set correctly to go into maintenance mode.

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

Enable access to the approved products list report, which is filterable by region, country, and other attributes contained within a specification.  (REQUIRED IF PRODUCT SPECIFICATIONS ARE LICENSED WITH ONBOARDING)

CUSTOMER Users of the right User type(s) and permissions can review the associations between a product specification, supplier facilities and countries.

Customer understands that all configurations setup will conform to CMX’s standard product configuration options

If onboarding is purchased along with Product Specification, Product Approval is available for implementation.

Deliverables/Tasks

Acceptance Criteria

CMX/CUSTOMER: Jointly review the Product Specification  Module workflow and determine final requirements for approval/review configuration options for creating, approving, and maintaining (revisions & variations) product specifications. 

CMX will work with CUSTOMER to determine the ideal universal product configuration of the specification Module, which is supported by CMX1’s then-current Product Specification capabilities.

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

Configure specification category and sub-categories, and specification numbering logic as per CMX1 product capabilities.

CMX will configure categories and sub-categories such that each specification can be properly categorized with up to 5 levels of meta-data. 

CMX will setup numbering such that each specification is given a unique number. Numbering will be based on CMX1 standard specification numbering scheme but can also include a manually assigned client specification number field. 

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

Configure specification workbooks, including general information, packaging, finished product standards, ingredients/formulation, processing control points and nutrition to support CUSTOMER requirements. 

CMX has the ability to add 1 additional custom workbook per Customer needs.

CMX will leverage standard form fields and add new ones (as needed) as per CUSTOMER’s requirements. CUSTOMER understands that other Modules and reports rely on certain fields/sections to function within CMX and cannot be modified without breaking key functionality (eg. Specification ID). 

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

Configure specification approval and collaboration workflows to support CUSTOMER business requirements.

CMX will configure the specification workflow to meet CUSTOMER business requirements by turning on/off supported CMX product workflow steps, including (pre-draft, draft, draft pending nomenclature, draft finalized, pending final review 1-4, final), to create CUSTOMER ideal specification workflow. 

CMX will configure CMX1’s standard collaboration workflow such that internal CUSTOMER Users with proper permissions can assign the specification to another internal User, or a supplier, to update content and then submit back. 

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

Configure standard specification PDF report such that a PDF of the specification record can be generated at any time during the specification workflow

Users with proper permissions can generate CMX standard specification PDF report with CUSTOMER logo, and all specification fields.

Customer understands that all configurations setup will conform to CMX’s standard product configuration options. 

Configure notifications to support CUSTOMER specification workflow.

Users receive notifications when action is required on a specification. Notification verbiage can be adjusted (within product constraints) to match CUSTOMER desired language and will contain CUSTOMER logo. 

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

Enable all navigational elements & queues necessary to allow supplier and CUSTOMER Users to access product specifications. 

Users (of both supplier and CUSTOMER) with proper permissions can access queues and filter/search them to easily find and navigate into product specification records.

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

CMX will configure the standard Modules to house and maintain Incidents.

Users are given the proper experience when logged into Incident Management.

CMX/CUSTOMER : Jointly review the Incidents Module workflow and determine final requirements for approval/review

configuration options for a universal product feedback

workflow across all brands.

CMX can clearly understand any changes to CMX

standard workflow and notification settings.

Both parties agree that CUSTOMER business goals can

be accomplished within the configurable constraints of the

CMX existing product workflow capabilities, and that

configuration will be universal across all brands.

Customer understands that all configurations setup will

conform to CMX’s standard product configuration options.

Make form available for CUSTOMER internal Users with the

right profiles, as well as restaurant-level users.

End-Users with proper permissions can create a new

product feedback record and capture all of the requisite

information for both product-related issues, as well as

service/delivery issues.

Create all navigational elements & queues necessary to allow

distributors, Customer users, and Suppliers to collaborate on

product feedback as specified in final design.

End-Users (Distributors, Suppliers, and Customer) with

proper permissions can access queues, filter/search them

to easily find and navigate into product feedback records

to take action on them.

Customer understands that all configurations setup will

conform to CMX’s standard product configuration options.

Create status-driven and time-based notifications to inform

appropriate users when records require their attention.

End-Users receive notifications when records require their

attention or when records have remained in the same

status for a certain period of time.

Customer understands that all configurations setup will

conform to CMX’s standard product configuration options.

CMX will create exception report to highlight product feedback

records that have become overdue.

End-Users with proper permissions can view an exception report to

understand what users/entities have not addressed product feedback

records in an acceptable period of time.

CMX will introduce support for product managers to set

threshold limits for monitoring of quality issues based on type

of issue/ingredient combinations.

End-users with the right privileges can setup threshold limits (by day) for ingredients/products by issue type, such that they start getting alerts when certain limits are met/exceeded. Alerts will provide a summary table, or a link to a report where they can see all of the cases by filtering to the ingredient/issue in question.

CMX will attempt to bring in existing historical thresholds, and will

make an interface available to authorized end-users

Deliverables/Tasks

Acceptance Criteria

CMX will configure the standard Modules to configure the Recalls module.

Users are given the proper experience when logged Recalls.

Incorporate Master Data (including integrations) into Recall

module such that end-users can leverage the best possible data

on what supplier products have been delivered to what DCs and in turn to what Restaurants.

Authorized end-users can easily leverage existing and up-to-date supply

chain and product distribution data so that the system can automatically setup lists of parties that need to be contacted for a given event, with ability to add additional contacts, as necessary.

Configure interface for authorized corporate users to create

product recall records, which allow for the centralized

management of, and reporting on the stage of the event, all

communications, all affidavits for all impacted locations and

associated users/e-mail addresses. The recall record shall provide all of the information required to successfully execute a product recall at all of the supported stages.

Call, text, and email reminders can be configured for each

communication setup.

Authorized end-users can create recall records which contain all of the

following information: a Product Disposition Form (Affidavit with

accompanying info for restaurant/dc to indicate how much product is

removed), a list of impacted locations and e-mails, above-restaurant

contacts who should be copied, the stage of the event and any

notes/settings that are relevant, and notification settings (including text

and voice).

Create interface for authorized end-users to create and associate groups (lists of e-mails) with product recall events using a tool that leverages Sonic’s restaurant hierarchy and other attributes to identify and select a specific set of e-mail addresses that should be involved in a recall event. A list of e-mails can be inserted into the “To” line of the recall e-mails, and a list of e-mails can be inserted into the “CC” line of the recall e-mails.

Authorized end-users can create groups that are suited to the recall

situation at hand, and all of the e-mails that get associated with the recall are leveraged to send the initial Product Disposition Form notification and any reminder e-mails that should go out.

Enable communication landing pages that provide recall action-

oriented information and/or navigational links relevant for all 

user types. Page should include recall status report outlining the recall along with real time reporting indicating, number of emails sent, acknowledgements, affidavits sent/completed. The report should be viewable based on team hierarchy. Reporting should be available to list out all restaurants (with engagement data) in different stages of recall.

End-users can easily understand the status of a communication,

including:

Who received it (DCs & Restaurants) and whether any bad

email addresses may have been included in communication list

Who acknowledged (DCs & Restaurants) receiving the recall

(based on clicking through from link in email)

If applicable, how much product was present in each restaurant,

and how much was taken out of inventory that could be served

to customer 

Which Above Store Leaders  have been successfully contacted

DELIVERABLES/ TASKS

ACCEPTANCE CRITERIA

CMX1 will allow CUSTOMER to upload and automatically request documents from vendors when they come up for expiration.

The CMX1 platform will automatically request updated documents for vendors in the system based on configurations set up within the system. 

CMX will manually import a file of vendors into system.

Keep this if they did not buy Onboarding or ActivityStudio.

CUSTOMER will provide an excel data file of vendors (eg. locations) that they want to collect documents for.

User interface for uploading and managing documents.

User interface should be intuitive and easy to use for both administrators and vendors.

User interface for uploading and managing documents:

• Support various document formats such as PDF, Word, and Excel
• Provide an option to assign metadata to documents, such as vendor name and document type
• Enable sorting and filtering of documents based on metadata
• Allow for quick and easy uploading and deletion of documents

Customer understands that all configurations setup will conform to CMX’s standard product configuration options.

Ability to set document requirements for each type of vendor.

Document requirements (Acknowledge, Confirm or deny terms, submission and approval, sign & submission & approval), will be configurable and able to capture the specific information for each vendor.

Different workflows for each document requirement.

Workflows should allow for the correct users to review and approve, if necessary.  Each workflow will have clear notifications and actions required.

Notification system for vendor document requests and updates.

Notification system will be able to alert administrators and vendors of any new or updated document requests.

Document expiration tracking and notification

Document expiration tracking will be automatic with clear alerts and actions required for the vendor when documents are close to expiring.  Expiration notification thresholds are configurable.

Deliverables/Tasks

Acceptance Criteria

Configure Product Evaluation & Inspection module, such that users can access all functionality as currently supported in product

Customer users can:

• Create Product Evaluation & Inspection Templates (forms)
• Start Product Evaluations
• Make Product Inspection templates available for Suppliers to start when needed

Customer understands that all configurations setup will

conform to CMX’s standard product configuration options.

CMX to configure Product Specifications and Finished Product Standards such that forms can be created from existing specifications and existing Finished Product Standards 

Users with proper permissions can setup generic forms and forms based on specific products, which are collections of configured data entry forms with varying levels. (e.g. Case, Bag, Item) as currently supported in Product

• Customer can setup how many data entry points are expected for each FPS that is included in form. 
• Customer can provide instructions for each FPS entry in form
• Customer can elect to provide attachment and/or reference photos
• Customer end-users are able to capture notes and attachments during the evaluation/inspection process
• Customer end-users can added items, bags, cases, etc.

Customer understands that all configurations setup will

conform to CMX’s standard product configuration options. 

Create business rules for each product evaluation such that parameters that fall out of range create findings.

Customer can build complex rules for compliance such that all FPS items can be automatically evaluated for adherence to standards, as supported by then-current product capabilities.

Customer understands that all configurations setup will

conform to CMX’s standard product configuration options.

Deliverables/Tasks

Acceptance Criteria

Setup permissions such that the right types of users can access the lab test reports to access information and upload new results. 

CMX will work with Checkers to ensure the right types of internal and external users have access to lab test results, and are able to upload new lab tests files. 

Configure upload workflow such that users with proper permissions can: (1) create a new record, (2) download upload instructions, (3) download import template.  Once template is populated with test data, the user will be able to upload the file, and the system will process it, providing any validation errors that prevented the data from being imported (if issues are present). 

CMX will ensure Internal and External users can easily upload test data, and that any data quality issues can be corrected if present. 

If data can’t be successfully paired with the product/facility records, an administrative interface will allow test data to be paired with the right product/facility relationships.  

Customer understands that all configurations setup will

conform to CMX’s standard product configuration options.

Configure lab test container app to support additional columns/data as needed.

CMX will work with Checkers to add additional columns/attributes to the import app and container app, on an as-needed basis to ensure the platform can manage all of the requisite data. 

Customer understands that all configurations setup will

conform to CMX’s standard product configuration options.

Deliverables/Tasks

Acceptance Criteria

As part of CMX's retail Standards Management solution, known as ActivityStudio , CMX will configure the standard Modules to house and maintain organization (corporation) and organization locations (restaurants).

Users are given the proper experience when logged into ActivityStudio, and can view/interact with the appropriate organization and organization location(s) per their data firewall access set in the User app.

CMX will configure the standard Modules for Users, and User profiles, to create the out of the box experience necessary for distinct CUSTOMER “internal” corporate Users, and location-level Users.

Users are given the proper experience when logged into ActivityStudio, and can fulfill the ActivityStudio-supported primary functions that CUSTOMER desires when interacting with the Modules available within the system. Profiles established on the User app, govern how a User can interact with all Modules, and profile granularity is based on the level of detail the then-current system can provide about any User.

CMX will configure standard access control list permissions for identified corporate and location-level Users, which controls those User’s access to records.

Users of all profiles can be given explicit access to all data, or only certain data, as needed, by the levels CUSTOMER deems necessary.

CMX will provide CUSTOMER access to our administrative tools to set up User names, hierarchy access, role and contact information

CUSTOMER will be able to access ActivityStudio and create User records and control what they are entitled to see when logging in.

CMX will enable ActivityStudio’s standard “action items” landing page that provides action-oriented information and/or navigational links relevant for all User types.

CUSTOMER Users that reach the ActivityStudio system through login arrive on the landing page that provides overdue and open tasks assigned to the User for each Module.

CMX will configure the ActivityStudio notifications Module to ensure CUSTOMER User roles and access rights are setup correctly to receive the appropriate supported notifications.

Users will be notified as per CUSTOMER User roles and  business requirements. Existing notification templates can be configured by CUSTOMER content editors to reflect desired language and desired frequency of send. Examples of existing templates include new audit scheduled, audit completed, action items due/overdue, etc.

Define Activity – CMX will work alongside CUSTOMER to understand and configure the basic framework of 1 audit (“activity”) program as supported in CMX’s then-current product.

CUSTOMER can successfully set up the framework of a new activity, clone an existing activity, and make edits to an existing activity. Components of the activity framework include naming an activity, writing the description of an activity, configuring if the activity will be scored, if it will include corrective actions, how the workflow/ assignments/notifications will function, and how the form will be built.

Configure Form – CMX will work alongside CUSTOMER to understand and build 1 activity form. CMX will configure the Module to support an unlimited number of audits and assessments, which utilize CMX’s then-current standard question templates developed for the assessment form.

CUSTOMER Users will understand the different components available while building a form, including departments, topics, question templates, and unique features available in each question template. CUSTOMER will have the ability to manage and update audit content (question text, reason codes, instructions, policies, etc.) without the assistance of CMX based on then-current product capabilities.

Configure Scoring – CMX will work alongside CUSTOMER to configure how 1 activity should be scored, and how to set up ratings and goals, as supported by CMX’s then-current scoring capabilities.

CUSTOMER Users will be able to set up scoring and configure ratings and goals for each activity, consistent with the options and features that are currently available.

Configure Workflow & Associated Notifications – CMX will work alongside CUSTOMER to configure 1 activity workflow and the notifications for each workflow step, as supported by CMX’s then-current workflow and notification capabilities.

CUSTOMER will have the ability to assign audits or assessments to auditors and/or locations on an ad hoc basis. CUSTOMER can set up pre-activity, perform activity, and post activity steps. CUSTOMER can configure notification recipients and copy for each workflow step. CUSTOMER can configure reminders and the copy for reminder emails.

Configure Corrective Actions for 1^st Natively- Conducted Activity – CMX will work alongside CUSTOMER to configure how corrective action plans are documented and reviewed in 1 activity based on then- current CMX corrective action configuration capabilities in the solution known as “ActivityStudio”.

CUSTOMER will have the ability to configure who is assigned the task of documenting corrective action plans and how long they have to document, what fields will be included in each corrective action plan, and who reviews corrective action plans and how long they have to approve/return the plan. CUSTOMER can configure notification recipients and copy for notifications related to the corrective action plan workflow.

Configure PDF Report – CMX will work alongside CUSTOMER to configure a downloadable summary PDF report for 1 activity, based on CMX’s then-current workflow and notification capabilities.

CUSTOMER will have the ability to configure the fields on a PDF report based on existing configuration options of the CMX system.

CMX will support repeat finding detection during audits, and in findings reports as per current capabilities of ActivityStudio product.

CUSTOMER can see the issues noted on the previous audit during the current one. Issues that are confirmed as repeats are reported as such on both the PDF audit report, and in online, queue-based reports. Repeats will only be calculated based on audits performed in the ActivityStudio system.

CMX will configure findings and corrective action apps to leverage data captured by question templates / audit forms as per current capabilities of ActivityStudio product.

CUSTOMER can report on issues generated in retail store audits/assessments and can assign and review corrective action plans to responsible retail store Users.

CMX will configure the audit attachments app to leverage images captured by question templates / audit forms.

CUSTOMER can capture images in each question template by uploading a file or taking a photo with the camera feature. These images will be captured and displayed in the audit form, in the audit attachments queue, and in the PDF report, if desired.

CMX will provide the necessary standard ActivityStudio training materials to assist CUSTOMER program administrator Users with building an activity, scheduling an activity, conducting an activity, and performing post-activity tasks.

CUSTOMER Users will understand how to use the system.

CMX will configure the audit Module to work offline in a manner consistent with what capabilities are supported in a disconnected state in then-current version of CMX1 Platform, ActivityStudio product, and approved Native App / Device Specification configuration the software is being used on.

CUSTOMER licensed offline Users will have the ability to schedule and conduct an audit with no Wi-Fi connection. CUSTOMER Users will be able to review the PDF report without a Wi-Fi connection. CUSTOMER Users must sync their device after performing an audit offline to ensure audit results are properly uploaded upon completion.

Deliverables/Tasks

Acceptance Criteria

CMX will work with Customer to set up proper permissions to enable the PolicyStudio module such that internal users with the desired profiles have access to create & edit policies.

Customer end-users with the desired permissions can access administrative interfaces to create and edit policies. 

Customer end-users who have policies published for their user profiles can access and view policies. 

CMX will provide a demo of Policy Administration and publishing, and ensure the right customer end-users are set up to start administering policies. 

Training will cover both administration in the system, and the ability to import policies via .xlxs files en masse. 

Customer has the right level of user access for real users to begin administering and publishing policies. 

Customer understands how to create/edit policies in the system, as well as via import from excel.

Deliverables/Tasks

Acceptance Criteria

CMX: Standard integrations include one of the following formats:

1. One-time data feeds mapped to our standard import templates
2. Basic API integrations that support CMX master data
3. Scheduled file drops for CMX to consume for master data
4. Single Sign On with basic user provisioning

Customer will provide CMX with the details to one of the defined formats. Changes to the format could cause changes on the CMX integration which may have impact on professional service costs.

Integration 1

Integration 2 

Deliverables/Tasks

Acceptance Criteria

Setup standard Module data extracts for Tableau

CMX system creates extract files of standard entity columns for each product Modules.

Setup schedule for each extract out of production system into reporting server. Extracts run on a 24 hour schedule.

Extract files are automatically created every day.

Provide hours of Tableau consulting to help design reports, create reports, and edit currently-available standard reports.

CMX provides support for Customer reporting needs. Total hours specified in section 7 below

Provide key internal Customer Users with access to report-building interface in Tableau server and ensure they have access to all available and current extract files.

Customer Users with access to Tableau server can leverage data extracts to create ad-hoc reports, save them, and share them.

Deliverables/Tasks

Acceptance Criteria

CMX will provide a translation dictionary template to Customer for areas that need to be translated.

For languages already supported by the CMX1 platform, standard fields are already translated.  Customer is responsible for translating any custom attributes. 

Customer sends translation file to CMX.  CMX will upload it into system and have Customer review the new translations in the system.

The majority of the CMX1 platform can be translated into multi languages.  An exception would include any items in open text fields.  Dynamic translations are not provided.

Customer will review all navigational headers, field names, form questions, email verbiage to confirm accuracy of translations.

Compliance Metrix Team

Executive Sponsor

Strategic Account Manager

Implementation Director

Customer Team

Business Owner(s)

Project Manager(s)

Subject Matter Expert(s) (Subject)

IT Support & Procurement

Base Implementation

$x,xxx

Module Implementations

Add-Ons

Historical Data Feed (one time import)

Integrations

Number of Activities/Audits needing ActivityStudio Setup Assistance (less than 100 questions per audit)

MultiLingual

Tableau Hours

included

Total Implementation Cost 

ComplianceMetrix, Inc

Accepted and Agreed to:

Customer: [CUSTOMER]

Signature

Signature

Print Name

Print Name

Title

Title

Date

Date