From the limited point of view by FourOh-LLC, the key difference between the two is the migration path of data. Without piling on a buch of definitions here is a short explanation.
Information is data with some structure, context, usefulness. For example, a steel gear inside a box have all sort of properties (data), but without something utilizing those properties (such as a Preventive Maintenance Schedule) they are meaningless. The gearbox has hundreds if not thousand of properties, and the "tribal knowledge" is the filter which validates the useful set. The "corporate culture" is the mechanism which controls access to that knoweldge, assures its survival and transition, and more, in a dispiclined and predicatble manner (business logic, resource planning, supply chain or spare parts).
FourOh-LLC builds a Manufacturing Dictionary, with a vocabulary structured in a key-value pairs. For example, inside the gearbox, one of the gears require a "set screw". The Dictionary around this set screw is constructed from Tribal Knowledge, as the set screw is "serviced", "bought", inspected". For servicing: "set-screw = torque", and for buying: "sets-screw=supplier", "set-screw=price".
This sort of approach is somewhat compatible with SQL, non-SQL, XML and of course with CVS. FourOh-LLC is a development, evaluation platform, and the data does not need to be "normalized" - but it must conform to Industry Standards such as ASMT, IPC, etc..
This is the migration path which is going to attempt to bridge the Tribal Knowledge to the Industry 4.0 platforms, vocabularies and dictionaries. This is only a draft, and there are many more details to add. The concept is developing under the Dokuwiki link.
Wikipedia:
#^https://en.wikipedia.org/wiki/Tribal_knowledge#^https://en.wikipedia.org/wiki/Organizational_cultureDokuwiki:
#^https://welcome.factoryfouroh.net/dokuwiki/abc_delta:abc_di:dictionary_is_key-value_pairs
