Thinking about the problems we are trying to solve here at Litbit, I have no choice but to take a step back on regular basis and analyze them differently from the traditional engineering approaches.
The whole concept of: Spec -> Design -> Architect -> Build ->Deploy ->Maintain comes as a secondary function. The main exercise is how do you translate logic, security and intelligence in an orchestrated manner down to machines that have traditionally not benefited from those functions.
In that light I am going to write about how we think about our engineering problems and how they relate to our design patterns. This is the opening for a 6 part series on the subject.
Litbit thinks of “industrial internet of things” in terms of who our customers are and how we can make their lives easier.
Our customers are the machines that power our modern day lives. They are the mechanical systems, the cooling systems, the heating systems, the electrical systems, the water systems, the security systems and so on and so forth.
And the question becomes: what are the parameters we think about to enable these machines to take advantage of modern software life cycles?
All in all we have brought our design pattern into 6 distinct areas of focus, which we call “initiatives”. As we come up with ideas, they have to relate backwards into any of the following initiatives.
Who? - who are you? Who else needs to know about you? Who do you need to know about?
What? - What do you speak? What do you need to know? What are your functions?
How? - How are you setup? How to do you relate?
Where? - Where are you setup relative to other pieces?
When? - When do you operate? When do you need to know about others activities?
Why? - Why do you need to know about the information you are asking for? Why do others need to know about the information you produce?
The above initiatives play into our orchestration methodology which in turn deliver the core features of Litbit’s operating system (DIOS) geared directly towards its customers (machines that enable our modern world):
- Hardware Agnostic code
- Hardened Security with Policy Management
- APIs and Webhooks for Smooth App Integrations
- Litbit + 3rd Party Industrial App Store
- Automated Software Distribution & Backups
- Cloud Integrated without Cloud Dependency
...to be continued in Part 2