Hitachi

JP1 Version 12 JP1/Navigation Platform Content Editing Guide


6.9.6 Examples of analyzing the usage of Operational Content

The following provides examples of analyzing the usage of Operational Content. For details about the procedure for displaying the reporting window in these examples, see 6.9.1 Analyzing the usage of Operational Content.

Organization of this subsection

(1) To understand which pieces of Operational Content are frequently executed

The reporting window can show the number of times Operational Content is executed, which allows you to understand frequently executed pieces of Operational Content. By combining this information and the number of executions for each node, you can also determine whether Operational Content is executed correctly (from the metrics such as the frequency of error occurrence and existence of unnecessary branches).

The following shows the procedure for displaying the number of times Operational Content is executed in the reporting window:

  1. In the reporting window in analysis item selection mode, select Analyze the overall status..

  2. In the reporting window in Operational-Content-based analysis result display mode, select Analyze by the number of executions..

  3. Click the Analyze button.

(2) To understand which pieces of Operational Content require time for execution

The reporting window can show the average execution time of Operational Content, which allows you to understand which pieces of Operational Content require more time for execution. The pieces of Operational Content that require more time for execution might need to be improved.

The following shows the procedure for displaying the average execution time of Operational Content in the reporting window:

  1. In the reporting window in analysis item selection mode, select Analyze the overall status..

  2. In the reporting window in Operational-Content-based analysis result display mode, select Analyze by average execution time..

  3. Click the Analyze button.

(3) To simplify the operation by deleting unnecessary branches

You can check for any unnecessary branches by understanding the nodes that are executed infrequently. Deleting branches to infrequently executed nodes might simplify the Operational Flow.

The following shows the procedure for displaying the infrequently executed nodes in the reporting window:

  1. In the reporting window in analysis item selection mode, select Analyze the overall status..

  2. In the reporting window in Operational-Content-based analysis result display mode, select Analyze by the number of executions..

  3. Click the Analyze button.

  4. Select the piece of Operational Content that you want to improve.

(4) To check whether the Operational Flow is working as expected

You might be able to check for any inappropriate node explanations from the number of executions for each node. Fewer-than-expected executions for nodes along a branch probably means that users cannot reach a branch as expected because the explanation of the branch-source node is difficult to understand. In such a case, by revising the explanation of the branch-source node, you might be able to improve the Operational Content so that Operational Flow works as expected.

The following shows the procedure for displaying the number of executions for each node in the reporting window:

  1. In the reporting window in analysis item selection mode, select Analyze the overall status..

  2. In the reporting window in Operational-Content-based analysis result display mode, select Analyze by the number of executions..

  3. Click the Analyze button.

  4. Select the piece of Operational Content that you want to improve.

(5) To understand the hurdles for a specific user

The reporting window can show the number of operational errors made by a user for pieces of Operational Content or nodes. By checking the pieces of Operational Content or nodes on which a specific user is likely to make an input mistake, you can understand the hurdles for that user.

The following shows the procedure for displaying (in the reporting window) the number of operational errors made by a user on pieces of Operational Content or nodes:

  1. In the reporting window in analysis item selection mode, select Analyze a specific user status..

  2. In the reporting window in Operational-Content-based analysis result display mode, enter the user ID, and then select Analyze by the number of errors..

  3. Click the Analyze button.

    The pieces of Operational Content for which the user frequently makes an error are displayed.

  4. Select a piece of Operational Content.

    The nodes for which the user frequently makes an error are displayed.

(6) To understand the hurdles for all users

By checking the number of operational errors made for Operational Content or nodes, you can understand the pieces of Operational Content whose Operational Flow does not proceed smoothly, or the nodes whose explanations are difficult to understand.

  1. In the reporting window in analysis item selection mode, select Analyze the overall status..

  2. In the reporting window in Operational-Content-based analysis result display mode, select Analyze the overall status..

  3. Click the Analyze button.

    The pieces of Operational Content for which input errors are frequently made are displayed.

  4. Select a piece of Operational Content.

    The nodes for which input errors are frequently made are displayed.