Product Vision
by Aitor & Cristo
Clarifications / Notes
-
We are not bypassing our leaders, we are escalating this topic because it is quite important for us and for the company.
-
We don't want to be right, we want to do things right.
-
Our proposals are not a whim of ours, they are thought out for the entire company.
- If we didn't believe it was critical to talk about this, we wouldn't be having this conversation now.
Current Architecture
Data sources (sensors)
Serial Server
Serial (USB)
CPU
Client network
CoreIntegrity
Client Internet
- Data flows in one way
- Client owns infrastructure
- Client owns maintenance and support channels
- Dependency of commercial Serial Servers
Proper Architecture
Data sources (sensors)
CPU
CoreMarine network
CoreIntegrity
CoreMarine Internet
- Data flows bidirectionally
- CoreMarine owns infrastructure, maintenance and support channels.
- Everything is connected to network, from vessels sensors to cloud apps
- Apart from CoreIntegrity we have 2 more apps:
- CoreAnalytics: All data stored in one place to be accesible for the whole CoreMarine team
- CoreDevices: Management whole data sources
CoreAnalytics
CoreDevices
Why this new approach?
From client side
- Safer: CoreMarine is not connected to its asset / vessel
- Easier: They don't need to work, we do the installation and configurations
- Faster: Almost nothing coordination between client-CoreMarine departments, reducing time-to-market
From CoreMarine side
- Faster: Development, Deployment, Monitoring, Maintenance-Support.
- Cheaper: Less time -> less money, better performance -> better incomes.
- Painless: Adapt projects flow to our working flow.
- Safer: CoreMarine is not connected to any client asset / vessel (less risks) and implementing safer communications.
Why this new approach?
More reasons
- We are not proposing disrupting approaches, it is kind of standard in offshore industry and IoT projects.
- It is not modern, it is the current way to work.
- Data sources (sensors) are not static:
- They required to apply different setups depending on issues.
- Setups have to be checked on starts, from time to time, etc.
- Less network restrictions provide the possibility to integrate modern battle-tested market solutions into our products -> We don't need to reinvent the wheel
- If we were faster improving our products and we would start thinking to talk about new products catalogue like "CoreIntegrity lite" (installed in the vessels).
How to achieve this?
- Each data source will be in a box with network connection (ethernet).
- We will bring our own network cables, router, internet connection (Starlink, ...).
- We will install and check everything in situ or we will contract ad-hoc external people for that.
- We will test internally every piece of hardware or software before sell it and deploy it.
Buying CoreIntegrity implies the first 3 points.
- It is not CoreIntegrity and 3 points
- CoreIntegrity is CoreIntegrity + 3 points
Selling any CoreIntegrity new feature implies the last point.
- Sales-driven = Sell prototipes
- Engineering-driven = Sell products
How to achieve this?
Trust on us!!!
Trust on our knowledge / expertise
Aitor:
- State of the art in offshore market
- Experience with high tech offshore technologies
Cristo:
- IoT projects from scratch
- Learnaholic (product development, technologies, etc)
- We need to be consulted before selling any new idea
- Engineering-driven please, not Sale-driven
- We need equipment to tests any idea.
- Please a budget to buy equipment and not have to justify what we're going to spend every last penny on.
Thank you
Copy of CoreNotion
By crisconru
