Request and implement changes

Change requests allow supplier relationship managers, quality compliance managers, and manufacturing plant managers to collaborate with their internal locations and external Partners to evaluate and implement process changes. For example, a Manufacturer might need to upgrade equipment at their internal manufacturing locations, or a Supplier might need to streamline the paperwork for their customers to lower cost.

Request a change

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.
  5. Select the Add Change Request icon.
  6. Fill in the following fields in the General section:
    1. Internal Only switch – Required. Indicates whether team members from the Partner company associated with the change request can view the change request being added:
      • Yes – (default) Only team members from the Owner company can view the change request being added.
      • No – Team members from the Partner company associated with the change request can view the change request being added.
    2. Summary field – Required. A brief description of the change request (255 characters maximum).
    3. Description field – A detailed description of the change request (5000 characters maximum).
    4. Priority drop-down – Required. The urgency with which the change request must be implemented:
      • Low – The change request is low priority.
      • Medium – The change request is medium priority.
      • High – The change request is high priority.
      • Critical – The change request is critical.
    5. Change Type drop-down – The type of change being implemented by the change request:
      • Supplier – The supplier needs to change.
      • Design – The design needs to change.
      • Equipment – The equipment needs to change.
      • Facility – The facility needs to change.
      • Material – The material needs to change.
      • Process – The process needs to change.
      • Specification – The specification needs to change.
      • Discrepancy Correction – An existing discrepancy needs to be corrected.
      • Indirect Supplier – The indirect supplier needs to change.
      • Other Change Type – If selected, fill in the field that displays with the type change being implemented by the change request.
    6. Initiating Company field – The company initiating the change request (i.e. the Owner or Partner company).
    7. Responsible Party at [Owner Name] field – The user at the Owner that is responsible for the change request's implementation (defaults to Unassigned if not entered).
    8. Responsible Department at [Owner Name] field – The business area of the Owner that is responsible for the change request's implementation (defaults to the job function of the user adding the change request, if available):
        • Business Development – The user responsible for implementing the change request is part of a Business Development team.
        • Clinical Research – The user responsible for implementing the change request is part of a Clinical Research team.
        • Contract Management – The user responsible for implementing the change request is part of a Contract Management team.
        • Corporate Management – The user responsible for implementing the change request is part of a Corporate Management team.
        • Customer Service – The user responsible for implementing the change request is part of a Customer Service team.
        • Engineering – The user responsible for implementing the change request is part of an Engineering team.
        • Information Technology – The user responsible for implementing the change request is part of an Information Technology (IT) team.
        • Operations – The user responsible for implementing the change request is part of an Operations team.
        • Packaging – The user responsible for implementing the change request is part of a Packaging team.
        • Production or Manufacturing – The user responsible for implementing the change request is part of a Production team or Manufacturing team.
        • Project Management – The user responsible for implementing the change request is part of a Project Management team.
        • Purchasing – The user responsible for implementing the change request is part of a Purchasing team.
        • Quality Assurance, Control, or Validation – The user responsible for implementing the change request is part of a Quality Assurance (QA) team, Control team, or Validation team.
        • Research, Development, or Formulation – The user responsible for implementing the change request is part of a Research team, Development team, or Formulation team.
        • Sales or Marketing – The user responsible for implementing the change request is part of a Sales team or Marketing team.
        • Supply Chain – The user responsible for implementing the change request is part of a Supply Chain team.
    9. Current Assignees at [Owner Name] field – The users from the Owner that are assigned to take action on the change request (defaults to Unassigned if not entered).
    10. Implementation Due Date field – Read-only for Partners. The date that the change request must be implemented by (defaults to a future date based on the network configuration set by an Administrator).
    11. Implementation Team field – The name of the location or group overseeing the change request implementation.
    12. Subject Matter Experts section – The people designated as experts on subjects related to the change request:
      1. Name field – The name of the subject matter expert.
      2. Email field – The email of the subject matter expert.
      Select the Add icon to add another row with the Name and Email fields displayed.
  7. Fill in the following fields in the Partner section:
    1. Partner Company field – Required if Internal Only is set to No. The Partner company that the change request is being submitted to.
    2. Responsible Party at [Partner Name] field – The user from the Partner company that is responsible for the change request's implementation (defaults to Unassigned if not entered).
    3. Responsible Department at [Partner Name] field – The business area of the Partner company that is responsible for the change request's implementation (defaults to the job function of the user adding the incident, if available):
        • Business Development – The user responsible for implementing the change request is part of a Business Development team.
        • Clinical Research – The user responsible for implementing the change request is part of a Clinical Research team.
        • Contract Management – The user responsible for implementing the change request is part of a Contract Management team.
        • Corporate Management – The user responsible for implementing the change request is part of a Corporate Management team.
        • Customer Service – The user responsible for implementing the change request is part of a Customer Service team.
        • Engineering – The user responsible for implementing the change request is part of an Engineering team.
        • Information Technology – The user responsible for implementing the change request is part of an Information Technology (IT) team.
        • Operations – The user responsible for implementing the change request is part of an Operations team.
        • Packaging – The user responsible for implementing the change request is part of a Packaging team.
        • Production or Manufacturing – The user responsible for implementing the change request is part of a Production team or Manufacturing team.
        • Project Management – The user responsible for implementing the change request is part of a Project Management team.
        • Purchasing – The user responsible for implementing the change request is part of a Purchasing team.
        • Quality Assurance, Control, or Validation – The user responsible for implementing the change request is part of a Quality Assurance (QA) team, Control team, or Validation team.
        • Research, Development, or Formulation – The user responsible for implementing the change request is part of a Research team, Development team, or Formulation team.
        • Sales or Marketing – The user responsible for implementing the change request is part of a Sales team or Marketing team.
        • Supply Chain – The user responsible for implementing the change request is part of a Supply Chain team.
    4. Current Assignees at [Partner Company Short Name] field – The users from the Partner company that are assigned to take action on the change request (defaults to Unassigned if not entered).
  8. Fill in the following fields in the Impact section:
    1. Impacted Products section – The products affected by the incident:
      1. Item or Packaging Code field – The specific item or packaging code type and value of the impacted product (e.g. GTIN-14 50378965679229).
    2. Impacted Locations section – The internal locations or external Partner Locations impacted by the change request.
      1. Location Type drop-down – Indicates whether the impacted location is internal or external:
        • Internal – The location belongs to the Owner company.
        • External – The location belongs to the Partner company.
      2. Name or ID field – The name or identifier of the location affected by the change request, which must exist in Master Data Exchange and be linked to the current network.
      3. Contact field – The user that is the regulatory contact for the location (defaults to the Regulatory Contact entered in Master Data Exchange for the location, if available).
    3. Reference IDs section – The internal reference IDs used by the Owner or Partner's external system of record to identify the change request.

      1. ID Type drop-down – The type of shipping document that is associated with a delivery involved with the change request:

        • Bill of Lading – The transaction is identified by a Bill of Lading number.
        • Destruction Order – The transaction is identified by a destruction order number.
        • Invoice Number – The transaction is identified by an invoice number.
        • Nota Fiscal – The transaction is identified by a Brazil nota fiscal document number.
        • Packing Slip Number – The transaction is identified by a packing slip number.
        • PO Number – The transaction is identified by a purchase order (PO) number.
        • PRO Number – The transaction is identified by a PRO freight number.
        • Return – The transaction is identified by a return authorization number.
        • Sales Order Number – The transaction is identified by a sales order number.
        • Shipment Number – The transaction is identified by a shipment notification number.
        • Transfer Number – The transaction is identified by a transfer order number.
        • Other – The transaction is identified by another type of identification number.
      2. Value field – Conditionally required if an ID Type is entered. The value of the selected ID Type (72 characters maximum).
      4. Select the Add icon to add another Impacted Products, Impacted Locations, and Reference IDs set.
    4. Risk Type drop-down – The type and level of risk associated with the change request:
      • Non-Technical - Low Risk – There is low non-technical risk associated with the change request.
      • Non-Technical - High Risk – There is high non-technical risk associated with the change request.
      • Technical - Low Risk – There is low technical risk associated with the change request.
      • Technical - High Risk – There is high technical risk associated with the change request.
      • Regulatory Risk – There is regulatory risk associated with the change request.
      • No Risk – There is no risk associated with the change request.
      • Other Risk Type – If selected, fill in the field that displays with the type and level of risk associated with the change request.
    5. Business Impact drop-down – The business function impacted by the change request:
      • Human Health – The change request impacts the company's business related to human health.
      • Animal Health – The change request impacts the company's business related to non-human animal health.
      • Research Labs – The change request impacts the company's research laboratory business.
      • External Manufacturing – The change request impacts the company's external manufacturing business.
      • Other Business Impact – If selected, fill in the field that displays with the business function impacted by the change request.
    6. Reason drop-down – The reason that the change request must be implemented:
      • Improve Quality or Compliance – The change request is a result from an effort to improve quality or achieve compliance.
      • Required Change from an Indirect Supplier – The change request originated with a requirement from an indirect supplier.
      • Customer Request – The change request originated with a customer request.
      • Increase Capacity – The change request is a result of a need to increase capacity.
      • Streamline Operations – The change request is a result of a need to streamline operations.
      • Save Costs – The change request is a result of a need to lower costs.
      • Required for Management or Business Needs – The change request originated with a requirement from management or business.
      • Other Reason – If selected, fill in the field that displays with reason that the change request must be implemented.
    7. Reason Notes field – Any additional descriptions or explanations for the change request and why it must be implemented (5000 characters maximum).
    8. Potential Risks field – A detailed explanation of other risks potentially associated with the change request (5000 characters maximum).
    9. Impact Evaluation field – A summary of the impacts associated with the change request (5000 characters maximum).
    10. Implementation Needed by Date field – The date that the change must be implemented by before the reason for the change impacts the business.
  9. Fill in the following fields in the Linked Processes section:

    1. Relationship field – The type of relationship the linked process has to the current change request:

      • Blocks – The linked process prevents the current change request’s resolution.
      • Blocked By – The current change request prevents the linked process's resolution.
      • Contains – The linked process is the parent of the current change request.
      • Contained By – The current change request is the parent of the linked process.
      • Dependent On – The linked process affects the current change request's resolution.
      • Dependency For – The current change request affects the linked process's resolution.
      • Relates To – The linked process is related to the current change request.
    1. ID or Summary field – The identifier or summary of another process related to the change request being added.
    Select the Add icon to add another linked process's Relationship and ID or Summary.
  10. Fill in the following fields in the Comments and Attachments section:
    1. Internal Only switch – Required. Indicates whether team members from the Partner company associated with the change request can view the comments and attachments:
      • Yes – Only team members from the Owner can view the comments and attachments.
      • No – (default) Team members from the Partner associated with the change request can view the comments and attachments.
    2. Comments field – Additional comments about the incident or explanations for the attachments (5000 characters maximum).
    3. Attachments field – Drag and drop a file to attach or select the browse link to search for the file. The file name must not exceed 250 characters. For a list of supported file types, see What file types can I include in an attachment
    Select the Add icon to add another row with the Comments, and Attachments, and Internal Only fields displayed.

  11. Select Add.

    The change request is saved.

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.
  5. Click Search in the Do menu.
  6. Filter to find the change request.
  7. Select the Action icon in the row for the incident.
  8. Select Copy.
  9. Fill in the following fields in the Copy Change Request panel:
    1. New Change Request Summary – A brief description of the change request (255 characters maximum).
    2. Internal Only switch – Required. Indicates whether team members from the Partner company associated with the change request can view the change request being added:
      • Yes – (default) Only team members from the Owner company can view the change request being added.
      • No – Team members from the Partner company associated with the change request can view the change request being added.
    3. Sections to Copy section – Required. When selected, the new change request uses the values entered for that section:
      • General checkbox – When selected, the values for the General section are copied to the new change request.
      • Partner checkbox – When selected, the values for the Partner section are copied to the new change request.
      • Impact checkbox – When selected, the values for the Impact section are copied to the new change request.
      • Linked Processes checkbox – When selected, the Linked Processes are copied to the new change request.
  10. Select Add.

    The panel closes and TraceLink saves the new incident with all of the copied values, with the following exceptions:

    • A new Change Request ID is generated for the change request.
    • The Date Reported becomes the date the change request is copied.
    • The Added By User becomes the user who created the copy of the change request.
    • The Responsible Party at [Owner Name] is set to Unassigned.
    • The Current Assignees at [Owner Name] is set to Unassigned.
    • The Responsible Party at Partner is set to Unassigned.
    • The Current Assignees at Partner is set to Unassigned.

Modify a change request

Setting the change request Status to In Implementation indicates that the change request has been created, reviewed, and submitted for implementation by the Owner company.

If the change request's current Status is Closed, the change request must be reopened.
  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.
  5. Click Search in the Do menu.
  6. Filter to find the change request.

  7. Select the Change Request ID for the change request.

  8. Select In Implementation from the Status drop-down in the top right of the screen.

    9. The change request's Status is updated from To Do to In Implementation.

When the change request is implemented, and the reviewers are ready to approve or reject the change request, one of them can close the change request so that other users know the change is implemented and whether it was approved or rejected.

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.
  5. Click Search in the Do menu.
  6. Filter to find the change request.

  7. Select the Change Request ID for the change request.

  8. Select Closed from the Status drop-down in the top right of the screen.
  9. Fill in the following fields in the Close Change Request [Change Request ID] panel:

    1. Resolution Type drop-down – Required. The reason why the change request is being closed:

      • Accepted – The change request has been accepted, implemented, and closed.
      • Accepted With Qualification – The change request has been accepted, implemented with one or more adjustments, and closed.
      • Rejected – The change request has been rejected.
      • Not Applicable – The change request has been closed because the request is not applicable.
      • Other Resolution Type – If selected, fill in the text field that displays with the final outcome of the incident.
    2. Closing Statement field – Any final comments about the change request.
    3. Attachments field – Drag and drop a file to attach or select the browse link to search for the file. The file name must not exceed 250 characters. For a list of supported file types, see What file types can I include in an attachment
  10. Select Close in the Close Change Request [Change Request ID] panel.
  11. Select Close in the confirmation dialog box.

    The change request is closed by changing the Status to Closed.

Reopening a change request updates the Status from Closed to In Implementation. Change requests may need to be reopened if a user has closed the change request accidentally or if the change request has not been fully implemented.

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.
  5. Click Search in the Do menu.
  6. Filter to find the change request.

  7. Select the Change Request ID for the change request.

  8. Select Under Investigation from the Status drop-down in the top right of the screen.
  9. Fill in the following fields in the Reopen Change Request [Change Request ID] panel:
    1. Internal Only switch – Required. Indicates whether team members from the Partner company associated with the change request can view the change request being added:
      • Yes – (default) Only team members from the Owner company can view the change request being added.
      • No – Team members from the Partner company associated with the change request can view the change request being added.
    2. Comments field – Captures any comments about reopening the change request (5000 characters maximum).
    3. Attachments field – Drag and drop a file to attach or select the browse link to search for the file. The file name must not exceed 250 characters. For a list of supported file types, see What file types can I include in an attachment
  10. Select Reopen in the in the Reopen Change Request [Change Request ID] panel.

    The change request is reopened by changing the Status to In Implementation.

Monitor ongoing change requests

Monitor change requests to understand the state of all change requests that supplier relationship managers, quality compliance managers, and manufacturing plant managers have access to at a high level. For example, supplier relationship managers might need to check on the process changes currently happening at a specific Partner, or manufacturing site managers might need to monitor the change requests entered for their site.

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.
  5. Click Search in the Do menu.
  6. Fill in one or more of the following fields to filter the results:
    • Partner field – The Partner involved with the change request.
    • Status drop-down – The status of the change request:
      • All
      • To Do – The change request is ready for review.
      • In Implementation – (default) The change request has been created, reviewed, and approved for implementation.
      • Closed – The change request has been implemented and is complete.
    • Change Request ID field – The change request's unique identifier.
  7. Select Show Additional Filters and fill in one or more of the following fields to further filter the results:
    • Summary field – A brief description of the change request.
    • Priority drop-down – Required. The urgency with which the change request must be implemented:
      • Low – The change request is low priority.
      • Medium – The change request is medium priority.
      • High – The change request is high priority.
      • Critical – The change request is critical.
    • Implementation Due Date field – The date that the change request must be implemented by.
    • Responsible Party field – The name of the person at the Owner or Partner company that is responsible for implementing the change request.
    • Current Assignee field – The name of the person at the Owner or Partner company that is currently assigned to implement the change request.
    • Transaction ID – The type of shipping document that is associated with a delivery involved with the change request.
    • Current Assignees at Owner – The users from the Owner company that are assigned to take an action on the change request.
    • Current Assignees at Partner – The users from the Partner company that are assigned to take an action on the change request.
    • Responsible Party at Owner – The user from the Owner company that is responsible for the change request's resolution.
    • Responsible Party at Partner – The user from the Partner company that is responsible for the change request's resolution.
    • Responsible Department drop-down – The business area of the Owner or Partner company that is responsible for the change request's implementation:
        • Business Development – The user responsible for implementing the change request is part of a Business Development team.
        • Clinical Research – The user responsible for implementing the change request is part of a Clinical Research team.
        • Contract Management – The user responsible for implementing the change request is part of a Contract Management team.
        • Corporate Management – The user responsible for implementing the change request is part of a Corporate Management team.
        • Customer Service – The user responsible for implementing the change request is part of a Customer Service team.
        • Engineering – The user responsible for implementing the change request is part of an Engineering team.
        • Information Technology – The user responsible for implementing the change request is part of an Information Technology (IT) team.
        • Operations – The user responsible for implementing the change request is part of an Operations team.
        • Packaging – The user responsible for implementing the change request is part of a Packaging team.
        • Production or Manufacturing – The user responsible for implementing the change request is part of a Production team or Manufacturing team.
        • Project Management – The user responsible for implementing the change request is part of a Project Management team.
        • Purchasing – The user responsible for implementing the change request is part of a Purchasing team.
        • Quality Assurance, Control, or Validation – The user responsible for implementing the change request is part of a Quality Assurance (QA) team, Control team, or Validation team.
        • Research, Development, or Formulation – The user responsible for implementing the change request is part of a Research team, Development team, or Formulation team.
        • Sales or Marketing – The user responsible for implementing the change request is part of a Sales team or Marketing team.
        • Supply Chain – The user responsible for implementing the change request is part of a Supply Chain team.
    • Location field – A location associated with the change request (e.g. an impacted location, a Partner location, an originating location).
    • Product field – The item code or packaging code of a product associated with the change request (e.g. an impacted product).
    • Change Type drop-down – The type of change being implemented by the change request:
      • Supplier – The supplier needs to change.
      • Design – The design needs to change.
      • Equipment – The equipment needs to change.
      • Facility – The facility needs to change.
      • Material – The material needs to change.
      • Process – The process needs to change.
      • Specification – The specification needs to change.
      • Discrepancy Correction – An existing discrepancy needs to be corrected.
      • Indirect Supplier – The indirect supplier needs to change.
      • Other Change Type – If selected, fill in the field that displays with the type change being implemented by the change request.
  8. Select Apply.

    The filtered results display in the table.

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.
  5. Click Search in the Do menu.
  6. Filter to find the change request.
  7. Select the Action icon in the row for the change request.
  8. Select Follow or Unfollow.

    9. When selected, if you are currently not following the change request, you begin following the change request. If you are currently following the change request, you stop following the change request.

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.
  5. Click Search in the Do menu.
  6. Filter to find the change request.
  7. Select the Action icon in the row for the change request.
  8. Select View Activity.

    9. The View Activity for [Change Request ID] screen displays.

Review change request metrics

Review a summary of change requests opened or closed in the last 6 months for the selected Network and Team. This data allows Owners to easily compare the numbers on a month-by-month basis and identify trends or outliers related to the opening and closing of change requests that may need further investigation.

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.

  5. Select the General tab.

    6. View the cards in the dashboard, which display pre-defined queries to demonstrate the state of all change requests at a high level. The labels on each card in the dashboard display a value as a link to the right. When selected, this link displays the table view of the change requests, filtered to the selected value. For example, if the value for Critical is selected, the table view displays with a filter applied to show only change requests with a Priority of Critical.

Summary card

A summary of all change requests for the Network, Team, and Process selected in the header. A horizontal bar chart displays on this card with the following values, based on whether the user is assigned a role with full or limited access:

  • Total Open Change Requests – The number of change requests with a Status of To Do or In Implementation.
  • Critical Change Requests – The number of change requests with a Priority of Critical.
  • No Activity This Week – The number of change requests that have not been updated in the last 7 days.
  • Closed This Week – The number of change requests that have been closed in the last 7 days.
  • Total Assigned To Me – The number of change requests that are currently assigned to the user.
  • Critical Change Requests – The number of change requests with a Priority of Critical.
  • No Activity This Week – The number of change requests that have not been updated in the last 7 days.
  • Closed This Week – The number of change requests that have been closed in the last 7 days.

By Priority card

A view of all change requests for the Network, Team, and Process selected in the header based on their Priority. A list displays on this card with the following values:

  • Critical – The number of change requests with a Priority of Critical.
  • High – The number of change requests with a Priority of High.
  • Medium – The number of change requests with a Priority of Medium.
  • Low – The number of change requests with a Priority of Low.

By Due Date card

A view of all change requests for the Network, Team, and Process selected in the header based on their Resolution Due Date. A list displays on this card with the following values:

  • Past Due – The number of change requests that have not yet been closed with a due date prior to the current date.
  • This Week – The number of change requests that have not yet been closed and are due within the next 7 days.
  • Next Week – The number of change requests that have not yet been closed and are due in the next 7 to 14 days.
  • In 2 or More Weeks – The number of change requests that have not yet been closed and are due in more than 14 days.

By Status card

A view of all change requests for the Network, Team, and Process selected in the header based on their Status. A list displays on this card with the following values:

  • To Do – The number of change requests with a Status of To Do.
  • In Implementation – The number of change requests with a Status of In Implementation.

By Partner card

Displays only for Full Access users from the Owner. A view of all change requests for the Network, Team, and Process selected in the header based on the Partners associated with the highest number of change requests with a Status of To Do or In Implementation. A list displays on this card with the 5 Partners that have the most open change requests.

By Location card

A view of all change requests for the Network, Team, and Process selected in the header based on the locations associated with the highest number of change requests with a Status of To Do or In Implementation. A list displays on this card with the 5 locations that have the most open change requests.

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.

  5. Select the Recent Performance tab.

    View the charts in the dashboard, which display a summary of change requests opened or closed in the last 6 months for the selected Network and Team. This data allows Owners to easily compare the numbers on a month-by-month basis and identify trends or outliers related to the opening and closing of change requests that may need further investigation. The following charts display:

Opened vs Closed chart

The number of change requests that have been opened next to the number of change requests that have been closed for each of the last 6 months.

Closed On-time chart

The number of change requests that have been opened on-time next to the number of change requests that have been closed late for each of the last 6 months.

Closeout Rate of Top Change Types chart

The type of change associated with the most change requests over the last 6 months and the average time taken to close those change requests. With this information, users can easily identify trends or outliers related to the closure of change requests with specific change types that may need further investigation.

Closeout Rate of Top Material Types chart

The material types associated with the most change requests over the last 6 months and the average time taken to close those change requests. With this information, users can easily identify trends or outliers related to the closure of change requests with specific material types that may need further investigation.

  1. Select a [Customer-defined APT Network] from the network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the Change Request Process in the header.
  4. Select the Go button in the header.

  5. Select the Partner Activity tab.

    View the charts in the dashboard, which display a comparison of different Partner change request data from the last 6 months for the selected Network and Team. This data allows Owners to see the types of changes and total number of changes Partners requested in the last 6 months, allowing Owners to quickly identify trends or outliers that may need further investigation. The following charts display:

Partner-initiated Change Requests

The number of change requests that have been initiated by Partners in the last 6 months.

Top Change Types Requested by Partners

A list of the 5 change types that were most requested by partners in the last 6 months. These metrics allow Owners to easily identify the top reasons that change requests are occurring so that they can be addressed.