In trying to describe Foundry to C-suite leadership that don't always "get" enterprise data, I prefer Palantir's term of "data operating system" for its accuracy. The unique value of Foundry is its dynamic data ontology, consolidate derived data objects, and the capability to integrate those derived data objects directly into native visualization and LCAP tools. Though true, that's a pretty dense value statement for an executive that has data many layers of priority down on his or her mind. "Digital twin" is also accurate. People usually only get it when they see a use-case on Foundry. If the ontology isn't compelling, usually seeing all the disparate data associated with a uniquely identified object consolidated in a single location is more so.