Skip to content

RMW brings in Polaris to operate rmwHub

RMW’s manufacturers have laid the foundation for shared gear marking. Polaris is now operating rmwHub, bringing software expertise and ongoing support to help that work grow.

Email

rmwHub — Powered by Polaris, with the Polaris logo.

The Ropeless Manufacturers Workgroup (RMW) has brought in Polaris Marine Technologies to operate rmwHub and support its long-term development. The partnership combines the manufacturers’ knowledge of on-demand fishing with Polaris’s software engineering and infrastructure expertise.

Both the production and test services have moved to Polaris infrastructure. The Polaris team now handles day-to-day operations, building on the work RMW has done to connect participating gear systems through shared location data.

A shared foundation for on-demand fishing

On-demand fishing depends on more than the equipment that retrieves gear. When gear is deployed without a permanent surface buoy, fishermen still need a way to see where it is. Different manufacturers’ systems need a common way to share that information.

RMW’s manufacturers came together around that challenge. Through rmwHub, participating systems exchange virtual gear-location records so authorized applications can show shared locations and support approved management, enforcement and research uses. Manufacturers can develop their own equipment and applications while contributing to infrastructure that serves the wider industry.

That collaboration is the foundation of the partnership with Polaris: a stable ecosystem in which different on-demand technologies can thrive.

Software expertise for the long term

RMW has demonstrated the concept. Polaris’s role is to build on it with the engineering, maintenance and operational support needed for dependable production infrastructure. Its priorities are stability, security and making the hub easier for teams to build on.

RMW continues to own rmwHub and set its data standards, governance and access policies. Polaris operates the service under those policies, maintaining hosting and the API, managing credentials and subscriptions, and providing onboarding and hub support. Manufacturers and software providers maintain their integrations and remain the first point of support for their users.

The subscription program helps fund the ongoing cost of running the service. It gives the hub an operating model to support continued maintenance and the people who rely on it.

What comes next

Polaris is working with subscribers on integration requirements and consistent submissions under RMW’s Data Rules. A separate test environment gives teams a place to develop and check their integrations with non-production data before arranging production access. The records and fields an application can receive remain subject to RMW’s policies and applicable approvals.

Further improvements to synchronization and more granular access controls are planned. Polaris will work with integrators as the service develops and provide at least 30 days’ notice of changes that are not backward compatible.

Existing subscribers should review the agreements and Data Rules circulated by email and confirm their operational and billing contacts with Polaris. Organizations exploring a new connection can contact Polaris with a description of their project and the data they need to submit or receive. The team can help them work through testing, subscription requirements and access.

RMW and Polaris share a goal: making this infrastructure dependable for the teams building on rmwHub and the people relying on it for years to come.