Skip to main content
Intelligent Automation | Job management
Need to automate increasingly diverse tasks to achieve greater efficiency and stable operations?
JP1/Automatic Job Management System 3 controls the execution of operations spanning multiple cloud services and on-premises environments, allowing you to automate entire operations running in large-scale, complex systems to achieve greater efficiency and stable operations.
JP1/Automatic Job Management System 3 (JP1/AJS3) automatically runs business operations linked with cloud services, web systems, and various other systems, and visualizes the overall execution status of business operations, making it easy to understand the status and accelerate response. These features help you achieve stable operation with improved efficiency.
With JP1/AJS3, even complex operations spanning systems and services in various environments (such as on-premises and cloud environments) can be smoothly and automatically executed in a specific order or according to certain execution conditions. Similarly, operations that have rules specific to a particular company or business operation can be automatically executed in a planned manner and in accordance with the company's calendar or the execution conditions of that business operation. For example, by linking operations executed by the order reception management, inventory management, and shipment management systems, you can automate a series of tasks including processing received orders, allocating inventory, and issuing shipment instructions. You can also automate a series of tasks executed in on-premises environments and by cloud services, for example, aggregating order reception data and then using a cloud service to predict and analyze demand. In this way, complex operations that span multiple systems and services can be automated as a whole, leading to more efficient operations.
You can easily understand the progress and status of automated operations. For example, you can check whether operations are running normally or whether an error or delay has occurred. If a task has ended abnormally or some other problem has occurred, you can take the appropriate action, such as re-executing or canceling the task. If an operation ends abnormally, you can identify the location and the date and time of the error (for example, "an error occurred in the aggregation processing at 10:00"). Then, after resolving the problem, you can re-execute the operation from the task that ended abnormally. Furthermore, you can check statuses on a mobile device from any location, including external locations, and even take the necessary action on the spot. By swiftly ascertaining the execution statuses of your operations and responding as needed, you can minimize operational delays and downtime for more stable operations.
You can visualize the flow and execution order of a series of operations, including those executed by cloud services, and control the execution of those operations according to the visualized order. JP1/AJS3 provides functions for detailed execution control to ensure that operations are executed in the right order. For example, you can specify for a task to start only after multiple preceding tasks end or to wait for the preceding task to end even if the execution of that task is delayed. You can also automatically select the next task to be executed based on the execution results of the preceding task. Additionally, you can implement control so that, if a problem is detected during the execution of a task, JP1/AJS3 automatically retries the task to resume operation. Alternatively, if operation cannot be resumed, you can execute special processing to handle the problem.
Because JP1/AJS3 makes it easy to link your mission-critical operations with external services, you can automate entire operations running in various environments. For example, you can link your mission-critical operations with a cloud service or a SaaS or web service that has a REST API, and then use the data handled by mission-critical operations, for other operations, processing, or analysis.
REST API : Representational State Transfer API
AWS : Amazon Web Services
Create a calendar of business days and non-business days, and then define scheduling rules such as the execution start time and processing cycle. JP1 automatically calculates the execution schedule based on these settings, helping you achieve detailed, flexible scheduling that matches your business operations.
In addition to executing a task once at the scheduled date and time, you can also specify tasks to be executed at preset intervals, such as every 3 hours, or in response to a specific event, for example, when a file is updated or an email is received. These and other features allow you to automatically execute tasks according to various triggers that occur in the course of your actual business operations.
Check the overview for the status and progress of tasks that are being executed. The overview shows you the progress of task execution, when the task is expected to finish (based on past results), and how much time is remaining. In addition to general information about all tasks, you can also check a chart indicating the progress or status ("Ended normally", "In progress", "Ended abnormally", etc.) of individual jobnets to quickly identify those that have ended abnormally or those that are in a particular state of interest. JP1 makes it easier for you to execute and monitor your tasks, because you can use a web browser to pause and resume jobnets even from outside your company.
JP1 provides convenient list displays both for the results of executed tasks and for the tasks that are scheduled to be executed. These lists can help you instantly identify jobs that did not start or end at the expected time. You can also add, edit, or delete task execution schedules from the provided windows.
Even for complex jobnets that include a large number of jobs, you can change the display so that only jobs executed on the current day are highlighted. Furthermore, each job icon changes color based on the execution status of that job ("In progress", "Complete", "On hold", "Delayed", etc.), making it easy to check the job's progress or status. You can also pause, re-execute, and forcibly end jobs from the GUI.
When editing tasks, there is no need to stop tasks that are currently in operation. Instead, you can schedule a switchover to a new jobnet. By registering a new or modified jobnet in advance, you can automatically switch over to the new set of tasks at a date and time you specify.
On-screen jobnet definitions and expected and actual results can be output to a file to be checked offline or to be used in a report. This flexible function allows you to select the items that you want to output and the file format that best meets your needs (CSV, Microsoft Excel, or PDF).
JP1 makes it easy to collect, modify, and apply job definitions. In particular, you can efficiently edit job definitions in Microsoft Excel by using functions such as Find and Replace All. This work can be split among multiple operators, with each person maintaining the definitions for the operations they are in charge of. By consolidating the definitions updated by multiple operators into a single file, you can then import and apply those definitions all at once. Working in Excel is especially useful, for example, when you want to change the names of development servers into those of production servers and then to apply all of those changes to the production environment in a single operation.
You can define SAP ERP jobs to be executed and monitored in JP1 simply by copying the jobs that are already defined in your SAP ERP systems.
This allows you to easily and efficiently link ERP systems with your other systems, so that all of your systems operate seamlessly, as if they were one.
Regular administrative tasks performed on PCs, such as data aggregation and operations executed by using RPA products, can be executed and monitored alongside processing performed on mission-critical systems as a single series of operations. Because you can easily link administrative tasks with your mission-critical processes, you can expand the scope of operations to be automated.