... | ... | @@ -33,7 +33,7 @@ capability, architectural, operational and openness/extensibility requirements: |
|
|
|
|
|
| \# | Description | Business rationale | Principle |
|
|
|
|----|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
|
|
|
| 1 | Data can be ingested with low friction | Need to seamlessly integrate with systems of record, to start with the industry standards owned by SLB | Capability |
|
|
|
| 1 | Data can be ingested with low friction | Need to seamlessly integrate with systems of record, to start with the industry standards | Capability |
|
|
|
| 2 | New data is available in workflows with minimal latency | Deliver new data in context of the end-user workflow – seamlessly and fast. | Capability |
|
|
|
| 3 | Domain data and services are highly usable | The business anticipates a large set of use-cases where domain data is used in various workflows. Need to make the consumption simple and efficient | Capability |
|
|
|
| 4 | Scalable performance for E&P workflows | E&P data has specific access requirements, way beyond standard cloud storage. Scalable E&P data requires E&P workflow experience and insights | Capability |
|
... | ... | |