This is an additional solution and requires a separate license.

The Veson IMOS Platform (IMOS) Data Lake is a highly scalable cloud solution that delivers a holistic view of a client's data in an easy-to-consume format.

It is intended for Business/Data Analysts, Project Managers, Heads of IT, or anyone who is responsible for leveraging vast quantities of historical data to recommend justifiable courses of action to maximize performance in the present.

For more information on how to use the Data Lake, see Data Lake Best Practices.

How It Works

The Data Lake provides table extracts from a client's operational database in the Veson IMOS Platform, transforms those extracts into Report Designer reporting format, and places the transformed extracts into a secure, encrypted download location. The secure location is accessible only to the client and is protected by an industry-standard authentication mechanism. To ensure optimal download performance, the data is stored in the same geographic region as the client: North America, Europe, or Asia-Pacific.

With the data easily accessible and in a standardized format, clients typically choose to ingest the information into a downstream data warehouse or business intelligence (BI) solution.

Clients may download the content from their secure location on a regular basis. For convenience, seven days' worth of data is retained in the Data Lake at all times. By default, the data is refreshed every 24 hours; upon request, the data can be refreshed as frequently as once per hour.

The Data Lake is managed by Veson Nautical and is monitored in real-time.

Frequently Asked Questions

On-premise database replication facilitates direct queries and reports run against the replicated (on-premise) database, to feed BI and data warehouse solutions, or other in-house systems. The replication processes can be labor intensive and unreliable for large data sets, and the client must continue to modify their reporting and data transformation processes when the source Veson IMOS Platform database schema changes.

Data Lake solves this issue in two ways. First, Data Lake transforms the Veson IMOS Platform database extracts into Report Designer format prior to making the extracts available to clients, which makes them immune to schema changes. Second, the extracts are sent to the client on a daily or hourly basis, making database replication unnecessary.

Replication is also used traditionally for business continuity, for times when one data center is not available, clients can continue to access data in a replica. Amazon Web Services (AWS) provides redundancy that removes the likelihood of a single point of failure in any part of the Veson IMOS Platform stack (storage, compute, networking), so traditional on-premise replication for business continuity and disaster recovery is not necessary.

Backup and restore operations are typically undertaken in response to the corruption or loss of a server, or to archive the database data at regular intervals for analysis and/or compliance requirements.

Data Lake provides similar functionality by extracting the Veson IMOS Platform database tables on a daily or hourly basis and making them available to clients to import into their reporting, BI, or data warehouse solution. AWS provides the redundancy that removes the likelihood of a single point of failure in any part of the Veson IMOS Platform stack (storage, compute, networking), rendering backup and restore for data recovery unnecessary.

Each extraction from the Veson IMOS Platform operational database is a full load of the current database tables. After transformation, the extract files are compressed to ~90% of their original size, then delivered to the client’s directory for download.

Yes. Clients will need to transform the data they download from the Reporting Repository, and the target format will depend on the data warehouse or BI solution they are using.

The extracted files represent the state of the client’s Veson IMOS Platform operational database at the point of extraction. The client is responsible for adapting the data in the destination system to account for changes between extract file versions.

If the client is concerned about data change frequency, they are likely a better fit for the hourly update model.