Junction City Police Department Goes Live with EIS Records Management, Joining Lane County on the Same Platform

When a small-town police department picks the same records management vendor as the county sheriff's office next door, that's not a coincidence. That's due diligence.

On November 14, 2025, Junction City Police Department officially went live with EIS RMS, making it the latest Lane County, Oregon, agency running on the EIS platform. For a department serving roughly 6,300 residents from their station on Greenwood Street, this wasn't about chasing the newest thing. It was about getting the right tool for how they actually work.

Why Lane County Matters to This Story

Junction City PD didn't make this decision in a vacuum. When they started evaluating records management systems, they looked at what was already working in their own backyard.

Lane County Sheriff's Office (the agency that provides correctional services, patrol, criminal investigations, court security, prisoner transport, and civil process across Lane County) was already running EIS. The county's jail operations, including their public-facing Web Jail Viewer, run on EIS infrastructure.

When your county sheriff is already on a platform and it's working, that changes the conversation. You're not evaluating a vendor based on a demo and a promise. You're evaluating them based on what the agency down the road has experienced in production. You can pick up the phone and ask a real person: "Does this actually work?"

Junction City PD picked up the phone. And then they picked EIS.

What a Small Agency Actually Needs from an RMS

Let's be straightforward about something: a department serving 6,300 people doesn't have the same IT infrastructure as a metro agency. They likely don't have a dedicated records unit with six clerks. They probably don't have a full-time systems administrator whose only job is managing the RMS.

That means the system has to be:

Intuitive enough that officers can use it without a three-day training course. When you've got a small patrol roster and everyone's wearing multiple hats, the RMS can't be the thing that slows them down.

Reliable enough that it doesn't create work. If the system goes down or throws errors that require workarounds, a small department doesn't have the staffing to absorb that. Every hour spent fighting software is an hour not spent on patrol or investigations.

Supported by people who actually answer the phone. This is where small agencies get burned the most. You sign a contract, the implementation team leaves, and suddenly your "support" is a ticket portal with a 48-hour turnaround. That doesn't work when your sergeant is trying to close a report at 11 PM on a Saturday.

EIS's support center is available 24 hours a day, 7 days a week, 365 days a year. All after-hours calls go directly to a designated member of the EIS support team, not an answering service. The team includes technical resources and application specialists with direct public safety experience. For a department of Junction City's size, that's not a perk. It's a requirement.

What EIS RMS Actually Does

Here's the practical rundown on what Junction City PD went live with: RMS is EIS's current-generation records management system. It handles complete data collection and records management for law enforcement: incident reporting, case management, arrest records, NIBRS compliance, and everything in between.

The core design principle: single point of data entry. All components are integrated into common core products. Information passes between system modules, and existing data is brought forward, eliminating the need to re-key information. An officer enters a name during an incident report. That same data populates the arrest record, the case file, and the NIBRS submission without anyone typing it again.

For a small department, that's not just convenient. It's the difference between a report that takes 20 minutes and one that takes 45. Multiply that across every shift, every day, and you're looking at hundreds of hours per year that your officers get back.

EIS also supports:

• User Groups in RMS Query — If your agency has integrated User Groups into your crime codes, you can use those groups as search criteria in Incident Detail searches. That means investigators and supervisors can filter reports by specific operational categories, tailored to how your agency actually classifies its work, not a generic dropdown that doesn't match your needs.

• Search Supplement-Specific UDF Fields — EIS RMS allows searching by user-defined fields at the supplement level, not just the parent report. That's granularity most systems don't offer, and it matters when you're trying to find specific details buried in supplemental reports across dozens of cases.

• Multi-Agency XML Submissions — EIS supports multi-agency credentials for uploading incidents, domestic violence reports, and zero reports. Credentials are retrieved from the database based on the specified agency in the submission window. For a department operating within a larger county reporting structure, this keeps submissions clean and properly attributed.

• NIBRS Compliance — RMS handles NIBRS data collection as part of its core architecture, including point-of-entry validation, guided data collection for required fields, and automatic enforcement of FBI reporting rules. Oregon agencies submit through the state UCR program, and EIS handles both state and federal compliance layers.

The Regional Platform Advantage

Here's something that doesn't show up on a feature list but matters enormously for agencies in Lane County.

When Junction City PD and Lane County Sheriff's Office are both running EIS, they're on a common platform. That has real operational implications, especially when you consider that Junction City has its own municipal jail but operates within the broader Lane County criminal justice ecosystem.

Common platform means:

• Consistent data structures. When agencies share information (whether through mutual aid, task forces, or shared jail facilities), the data doesn't need to be translated, reformatted, or re-entered. It's already in the same language.

• Shared institutional knowledge. If a Lane County deputy has figured out how to run a specific query or build a particular report, that same workflow applies at Junction City PD. Training resources, tips, and workarounds transfer directly.

• Easier state reporting. Oregon's UCR program receives data from both agencies in the same format, reducing the friction and error rate that comes from running different systems with different submission methods.

This is why the "Lane County connection" isn't just a nice story about one agency following another's lead. It's a practical, operational advantage that compounds over time.

What the Go-Live Looked Like for Junction City Police Department

According to EIS, Junction City PD's command staff invested significant time and care into the transition. That tracks with how successful go-lives actually happen: leadership that treats the RMS migration as an operational priority, not an IT project they can delegate and forget about.

The go-live date was November 14, 2025. The system is now in production with a clean cutover to a system that's already proven in their region.

For Other Small Agencies Doing Their Homework

If you're a chief or commander at a department similar to Junction City's size (say, 5,000 to 15,000 residents, a handful of sworn officers, limited IT support), here's what their experience reinforces:

1. Ask your neighbors. If a nearby agency is already on a platform and it's working, that's worth more than a hundred demos. Real operational feedback from a peer agency in your region is the most reliable data point you'll get.

2. Prioritize support over features. Every RMS vendor's feature list looks similar on paper. The difference is what happens after the contract is signed. Does the vendor staff their support center with public safety professionals? Can you reach them at 2 AM? Will they know your configuration when you call?

3. Think regionally. If your county sheriff, your municipal court, and your neighboring PD are all on the same platform, the data sharing, reporting, and cross-agency collaboration benefits multiply. A fragmented technology landscape creates friction at every handoff point. Want to read another example of a successful transition? See how Dunnellon PD and Charleston County navigated a transition with EIS.

4. Look for financial flexibility. EIS holds a Sourcewell contract, which means qualifying agencies can access EIS's full public safety software suite through cooperative purchasing. This fulfills the lengthy RFP process requirements typically needed. For a small department with limited administrative bandwidth, that's a significant practical advantage.

If your agency is evaluating records management software, especially if you're a smaller department looking for a vendor who won't treat you like an afterthought, contact EIS or call (208) 580-0400.