Service and asset management integration

Axel Forsman

Hi, I'm new to the product and would like to understand better the capabilities of the service and asset management integration.

My use case is similar to the following: Let's say that my asset register contains cars (by serial number). Each car has a standard maintenance/inspection plan

1) As an agent/admin, can I create a default inspection plan (based on a list of pre-defined issues) for each asset and schedule the inspection?

2) This same inspection plan I should be able to use for different assets (=cars), and for one asset (car model) I should be able to have different inspection plans (depending on the maintenance/service program).

3) While performing the actual inspection (based on the plan), can I (as a service engineer) create issues (defects) against the inspection plan items? E.g. as sub-items or linked issues?

Jeroen Poismans

Hi Axel and welcome to the community!

Without resorting to a page long answer, here is a high level apporach on how I would go about this.

• I assume an Inspection plan consists of multiple Inspection Tasks for this, so we get the terminology straight.
• These concepts should be in your Asset management as ObjectTypes:
  • Inspection plan: Name ... etc + Field containing all Inspection Tasks
  • Inspection Task: Name, description ...
  • Car: All information +
    • link to an Inspection Plan
    • Recurrency of inspection
    • Last inspection date

Now that you have the Assets setup it boils down to creating the correct Automation rules.

• Each day / week run a rule that selects Cars based on Recurrency and Last update attributes.
• For each eligable Car, create an issue and link the Car to that issue
• For each issue created this way:
  • Take the linked Car asset
  • Read the Inspection plan
  • Read every Inspection Task on the Inspection plan
  • Create a linked issue for each Inspection Task

Service Engineers can create and link defects to to the created Inspection Task issues via standard Jira functionality.

Jeroen