What Is the Hotel Core System "NEHOPS"? The Jtas Cleaning Integration, Explained

On June 11, 2026, NEC and Edeyans announced a stronger integration between two hotel systems: NEC's hotel core system "NEHOPS" and Edeyans' room-cleaning system "Jtas." Information that used to be handed over once a day is now delivered the moment it is needed, and free-text memos are read by AI and reflected into cleaning instructions.

The press release is full of phrases like "real-time integration" and "expanded linked items," but on their own they do not convey what actually gets better. This article untangles, in order: what NEHOPS is for and who uses it, what Jtas does, what "integration" concretely means in terms of which data is exchanged, how the experience changes for guests and staff, and how to think about the outage risk that comes with a core system.

What is NEHOPS?

NEHOPS is a hotel core business system provided by NEC. In the hotel industry, such a system is called a "PMS" (Property Management System). It handles, in one place, the clerical work needed to run a hotel: booking registration, front-desk check-in/check-out, room assignment, restaurant and banquet reservations, purchasing, and revenue accounting. It is, in effect, the hotel's "brain."

A defining trait of NEHOPS is that these functions are designed as a single integrated system from the start. Reservations staff, front-desk clerks and accounting all share information on the same system rather than using separate software. If a booking from a reservation site is imported automatically, for example, it prevents manual-entry errors and double bookings and makes sales analysis immediate.

It is offered mainly as a cloud service (SaaS), with NEC's dedicated operators handling system operation—so a hotel can adopt and run it without an in-house IT department. According to NEC, NEHOPS is deployed at about 1,000 hotels and is said to hold roughly a 70% share of cloud PMS in Japan—one of the largest of its kind. It is used across the board, from large city hotels to lodging-focused hotels with pared-down front desks, to nationwide chains, regardless of size or format.

Where is it used?

Publicly disclosed deployments run from several hundred to about 1,000 facilities. Named examples include Nagoya Montblanc Hotel, Asakusa View Hotel, Kurashiki Ivy Square, and resort hotels of the Okinawa Kariyushi group. Besides NEC, it is also delivered through sales and support partners such as NEC Nexsolutions, NCS&A; and Sanwa Computer, reaching regional hotels widely.

On the other hand, public confirmation of NEHOPS use at the very top-tier chains (specific names like Imperial Hotel or New Otani) is limited. Given its market share, it is likely used at many facilities, but this article sticks to confirmed cases. Either way, when you check in for a trip or business stay, NEHOPS is a strong candidate for the system running behind the scenes—and you would not be far off picturing it that way.

What is Jtas?

The other system, Jtas, is a cleaning-focused system (a cleaning DX platform) from Edeyans. Hotel cleaning is a humble but critical job of managing which rooms, by whom, in what order, and with what instructions, get cleaned. Jtas digitizes this work and greatly cuts on-site effort through automatic cleaning-instruction sheets, results aggregation and automated instruction delivery.

Notably, it directly addresses two of the hotel industry's current pains: labor shortages and the rise in inbound (foreign) visitors. It offers a generative-AI lost-and-found feature and multilingual support so instructions reach staff regardless of nationality, and it is featured in the Japan Tourism Agency's labor-shortage program. It has been deployed in 80,000-plus rooms cumulatively, including at major hotel chains and Forbes five-star hotels. It has also integrated with multiple hotel systems beyond NEHOPS, such as aipass, OPERA Cloud and tap.

What does "integration" concretely mean?

The word "integration" in a press release is vague, but technically it means connecting two systems via an API (a window through which software exchanges data) so one can receive, in a usable form, information the other holds. Here, that means passing the cleaning-related data from NEHOPS—which holds booking and stay information—to Jtas, used on the cleaning floor.

This is not the first time the two have been linked. In the first phase that began in October 2024, room status on the NEHOPS side could be checked from Jtas to judge cleaning timing immediately, and cleaning-instruction sheets could be generated automatically from NEHOPS data. Crucially, the two systems exchange only cleaning-related information; guest personal data such as names is not included in the integration. From the outset, there is a sound separation that does not expand personal data in exchange for convenience.

This June 2026 update is the second phase. Raising the "content" and "speed" of the integration a notch is the heart of this enhancement.

What the phase-2 enhancement changes

The enhancement changes three main things.

First, real-time delivery. Until now, order items (extra amenities, baby cots and the like—quantity, name, memo) and requests were handed over once a day. That meant a change made on check-in day did not reach the cleaning floor right away, so the front desk had to fill the gap by phone. Now this is reflected as it happens, sparing the phone calls and preventing missed deliveries from miscommunication. Processing everything once a day in a lump is called "batch processing"; this shifts to streaming it the moment it is needed.

Second, AI auto-review. The newly linked "free memo" (a field the front desk writes in freely) is read by AI, which extracts cleaning-related items (loaning a specific amenity, an individual cleaning instruction, etc.) and applies them to instructions automatically—AI taking over the chore of parsing free text one entry at a time. Third is the expansion of linked items: beyond free memos, baby-cot counts, room-change information, early-in/late-out flags, and related-booking information are now passed along.

How the experience changes for guests and staff

Now consider what this brings to the floor and to guests. From the guest side, the clearest gain is a higher chance that "what you asked for is actually ready." A same-day request—a baby cot added for a family, a humidifier to borrow—reaches the cleaning and prep staff instantly and accurately, reducing the letdown of arriving to find the requested item missing. Multilingual support also makes foreign guests' requests less likely to slip through the language barrier.

On the staff side, phone and verbal handoffs between the front desk and the cleaning floor decrease. This is more than time saved. Verbal handoffs invite mishearing and forgetting, and the follow-up checks and apologies were themselves a burden. When information flows accurately through the system, mistakes fall and so do confirmation exchanges. For cleaning floors hit hard by labor shortages, it underpins maintaining quality with limited headcount. Where many staff are non-Japanese, the value of instructions arriving independent of language is even greater.

An outage/risk view (the author's opinion)

From here, this is analysis including the author's view, not a recital of facts. Convenience aside, connecting systems also creates new risks. Here are the points worth keeping in mind.

First, credit where due: the design that excludes personal data from the integration. Exchanging only what cleaning needs, and not passing guest names, is a sound call for data security, in the author's view. Narrowing to "only what is necessary" rather than "everything" when expanding an integration also fits today's privacy-first climate.

On the other hand, note that real-time integration tightens the coupling between the two systems. With a once-a-day exchange, a temporary outage of one side had limited impact. With instant linkage, a glitch in either side is more likely to hit cleaning operations immediately. NEHOPS in particular is a core system with roughly a 70% share of cloud PMS. The structure where an outage of the core spreads beyond a single facility is contiguous with the chaos in ANA's core-system migration we covered earlier. Note that we have not confirmed any major outage of NEHOPS itself; this merely points out, as a general principle, the trade-off where dependence rises in exchange for convenience.

One more point: the mechanism where AI interprets free text and turns it into cleaning instructions always carries the chance of misreading. If the instructions AI extracts are executed on the floor as-is, a misread can translate straight into a service lapse. Where to leave room for a human to make the final check will shape quality. None of this is to say "don't integrate"; it is the flip side of an obvious truth—the more convenience you reach for, the more your readiness for outages and errors matters.

Summary

This NEHOPS-Jtas enhancement links "the hotel's brain (the core system)" and "the cleaning floor's system" faster and more deeply. Requests taken at the front desk reach the cleaning floor accurately without phone or verbal relays, and free-text memos are turned into instructions by AI. For an industry facing labor shortages and inbound demand at once, it is a practical move to cut on-site burden while holding service quality.

These behind-the-scenes systems are invisible to guests, but the accumulation of such integrations surfaces as smoother check-ins and the reassurance of finding what you asked for. The more we lean on the core systems that enable that convenience, the more their stable operation matters—a useful lens for watching where hotel DX goes next.

Frequently asked questions

Sources

• ▸PR TIMES - NEC's NEHOPS strengthens integration with the Jtas room-cleaning system (June 11, 2026)
• ▸Cloud Watch - NEHOPS strengthens integration with the Jtas cleaning system
• ▸NEC - Hotel core business system NEHOPS
• ▸HOTELIER - About NEHOPS
• ▸EDEYANS - Hotel room-cleaning management system Jtas
• ▸EDEYANS note - Real-time integration with NEHOPS: background and growing track record
• ▸Japan Tourism Agency - Hotel room-cleaning management system Jtas
• ▸NEC Nexsolutions - NEHOPS case study (Nagoya Montblanc Hotel)