Client case

Viking Line, PIM

We received an inquiry from Viking Line regarding the management of product information. They handle a large number of items whose information is stored in many different places, which in turn makes it difficult to get an overview.

We helped Viking Line with a fully tailored PIM system so they can easily manage their large volumes of data.

The assignment included:

  • Technical pre-study
  • Limetta PIM (Product Information Management)

Feasibility study

The project began with the execution of a pre-study. The study aimed to map Viking Line's needs and resulted in a specification for Limetta PIM for Viking Line as well as an updated cost estimate. The study was divided into two workshops, preparatory and follow-up work, and the creation of the specification.

 

Implemented PIM solution

The purpose of the project was to adapt Limetta PIM to Viking Line's requirements and preferences. The project was carried out using an agile project methodology, which meant that Viking Line had the opportunity to prioritize what should be done within the framework of the project.

By prioritizing functionality and resources, Viking Line had the opportunity to influence the project's schedule and budget. The products were organized into a flat structure based on object type - ship, cabin, hotel, route, meals etc. Each object type in turn has texts, images and other objects linked to it.

In total, it involves thousands of products and several updates per day from the internal booking system.

Launch contents:

Manage large amounts of data consisting of products and their resources. Clear web interface Imported data from business systems that enables editors to update and manage products which are then made available to EPiServer sites and the booking client. Interface in one language (English) Product information with language support for six languages (Swedish, Russian, Finnish, Estonian, German and English). Users are managed internally in Limetta PIM
  • Different roles; Administrator and Editor with different rights
  • Workflow with publishing as well as standard setup of information panels (to approve, recently changed, comments)
  • Approved information, including images, is published to a database with an open API
  • Published information is always available to systems such as EPiServer sites, booking client and intranet