Once the data center is built and systems are live, who watches them every day? JP1 brings batch job scheduling, integrated monitoring, and IT asset inventory together on one platform, so operations no longer depend on someone watching a screen.
JP1 (Integrated Operations Management JP1) is, in plain terms, the central control room for a corporate IT department. Servers, databases, network devices, virtualization platforms, and employee endpoint computers are scattered everywhere. JP1 collects their status and events onto a single management host and presents them through dashboards, topology maps, and alert rules.
Beyond watching, it also acts. Daily routine batch jobs such as closing the books, reconciliation, and report generation (a batch job is a routine process that runs automatically on a schedule without anyone operating it) can be chained into a flowchart using the scheduling engine. If any step fails, the responsible engineer is notified automatically, the step retries, or an alternative path takes over.
JP1 is not a single product but more than a dozen modules that can be bought independently and connected together. Most customers start with one or two and expand from there. According to Hitachi's own figures, JP1 held the number one market share for integrated operations management software in Japan in fiscal year 2024.
The users, budget owners, and evaluation criteria differ between the two, so they are best evaluated separately:
Orders, purchasing and inventory, receivables and payables, the general ledger, and payroll all live in ERP. The users are sales, warehouse, and accounting staff, and the budget owner is usually the owner or CFO.
Whether a server is down, whether the overnight batch finished, how many computers the company has and what software is installed on them, and whether licenses are fully covered. The users are IT operations engineers, and the budget owner is the IT manager.
The two are not an either/or choice; they complement each other at different layers. ERP is the system that needs looking after, and JP1 is the operations platform that looks after it. A common setup has JP1/AJS3 handle ERP's nightly closing and report batch: when it runs, what happens if it fails, and what happens next once it completes.
JP1 uses modular licensing, so modules can be deployed in stages as needed. Below are the modules Taiwanese customers evaluate most often, each with a plain-language explanation and who it suits.
The central console for the whole JP1 family. It gathers events from servers, databases, network devices, and other JP1 modules into one screen and correlates them with rules. It can work out that 200 alerts actually came from one failed switch.
Suited to IT departments with many systems and departments that have gone numb from alert overload.
An enterprise-grade scheduling engine, and one of the most classic and commonly deployed-first modules in the JP1 family. Use a flowchart to define a flow such as "close the books at 23:00 daily, reconcile on success, then generate and send the report; on failure, notify and retry automatically up to three times." Works across Windows, Linux, and UNIX.
Suited to manufacturing, financial, and retail chain businesses with overnight batch jobs.
Automatically inventories the hardware specs, installed software, license coverage, and update status of every computer. Also supports remote troubleshooting, restricting USB use, and keeping operation logs for audits.
Suited to companies that need to pass ISO 27001 or personal data audits, or that want to know exactly how many computers they have and who holds them.
This is not a feature module sold on its own. It is the required foundation underneath IM3 and AJS3, handling JP1 event generation, forwarding, and permission management. It must be installed on every host being monitored, or the management host will not receive events.
This is the item most often left out of a quote. List JP1/Base and the agent count for each endpoint in the quote to avoid extra charges at delivery.
Continuously collects performance data (CPU, memory, disk I/O, network traffic) from operating systems, databases, and virtualization platforms and plots them as trend charts. This catches bottlenecks in real time and uses historical trends to estimate when a server will run out of headroom, as a basis for expansion budgets.
Its Remote Monitor for Virtual Machine officially supports VMware, Hyper-V, KVM, and Docker.
Uses SNMP and ICMP to automatically discover devices and draw a topology map, and performs root cause analysis, for example working out that 30 downstream devices lost connection because one upstream core switch failed.
Vendor-neutral and not tied to a hardware brand, suited to campuses and factories with a mix of equipment brands.
An IT service desk that logs fault reports, user enquiries, and change requests as cases, tracking status and turnaround. Can connect with IM3 so monitoring alerts open tickets automatically.
Suited to IT departments that serve internal users and need a record of handling for audits.
Packages repetitive operational tasks (power on/off, backup, routine processing) into one-click service templates, reducing manual errors and capturing SOPs that would otherwise stay in a senior engineer's head.
Suited to teams stretched thin, worried that staff turnover will leave a gap in operations.
A standalone product in Hitachi's security category, handling file encryption, removable device control, and data loss prevention (DLP); this is separate from ITDM2's asset inventory.
Hibun has long focused mainly on the Japanese market. Supply and support terms for Taiwan should be confirmed with the supplier before the proposal.
Rather than a feature list, here are three situations IT departments actually run into that show what JP1 does.
A single data center often has several management consoles at once, each responsible for a different layer that does not really overlap with the others. Compared below.
Company-wide service availability, whether batch jobs finished, and the IT asset register and license compliance. What it watches is whether the work got done.
Whether anyone is attacking you, and whether you can produce the security audit logs. What it watches is the attack chain and compliance evidence.
Network device health, wireless signal quality, and a specific user's connection experience. What it watches is the network layer.
It only sees the nodes, virtual machines, and storage inside its own cluster, not systems outside it.
HPE Aruba Networking Central watches the network, Fortinet watches attacks, and the hyperconverged console watches its own cluster. Each of them only sees its own slice. JP1 sits above all of them, pulling every alert into one command center, and can then act automatically: retrying a batch job that did not finish, or opening a ticket when monitoring catches a bottleneck.
In one line: JP1 watches whether systems run smoothly, whether the work got done, and whether the assets are accounted for; FortiAnalyzer watches whether anyone is attacking you and whether you can produce audit logs. The former is IT Operations, the latter is Security Operations, and their report formats and audit purposes are completely different. JP1's operational logs cannot replace the security device logs that regulations require.
HPE Aruba Networking Central's depth of management for its own network equipment (firmware distribution, wireless spectrum analysis) is an advantage tied to that ecosystem. JP1/NNMi's strength is showing the whole company on one diagram when equipment brands are mixed. In a single-brand environment, we recommend sticking with that brand's own console. For related planning, see Enterprise Networking and Web & API Protection (WAF).
Technical integration approach: this kind of cross-platform integration uses standard syslog and API forwarding to feed events into JP1. We make no claim that JP1 has a vendor-certified official integration module with any particular networking, security, or hyperconverged platform. The actual workable integration path is confirmed by POC testing on real equipment before it goes into the proposal.
If you are evaluating a virtualization platform replacement or a VMware alternative, also see the IT operations management section on the Hyperconverged Infrastructure & VMware Alternatives page for how the operations layer is handed over. Once the new platform is live, JP1 takes over monitoring, batch scheduling, and the asset register so there is no gap in operations.
GN-AI Information Consulting is a Hitachi JP1 partner, providing the full service chain from evaluation and build through to annual maintenance, with the same team of engineers throughout.
Front-line support is handled by our own engineers; issues that need vendor involvement are escalated on your behalf. Support tiers, response methods, and the escalation path are agreed with the supplier before the maintenance contract is signed and written into the contract terms. Responsibilities are made clear at the contract stage.
JP1 is enterprise-grade commercial software; both deployment and operation require investment. Weighing deployment cost against benefit, it tends to be worthwhile at around 20 or more servers, with regular overnight batch jobs, and 3 or more IT staff. This is a reference figure for before the proposal; the actual calculation still depends on your environment and workload.
JP1/Performance Management's Remote Monitor for Virtual Machine officially supports VMware, Hyper-V, KVM, and Docker. Whether a specific hyperconverged platform is on JP1's official compatibility list is confirmed with the vendor before the proposal, based on the vendor's answer and POC testing. On the ERP side, a common approach is to have JP1/AJS3 schedule and monitor overnight batch jobs; see ERP Business Management.
HULFT's vendor is Saison Technology Co., Ltd. (listed on the Tokyo Stock Exchange Standard market, ticker 9640), not Hitachi. Using JP1/AJS3 to schedule and monitor file transfer jobs is workable in principle. The specific integration path is confirmed with the supplier before the proposal. See the IT operations management section on the Hyperconverged Infrastructure & VMware Alternatives page.
Want to evaluate the deployment scope and module combination for JP1 first?
Contact us See the full service chainLeave your contact details and a description of your needs. An engineer will contact you to help assess the architecture plan, deployment approach, and annual maintenance scope.