MDM_123
•Transferir como PPTX, PDF•
0 gostou•345 visualizações
Master Data Management 1-2-3 Download PPT to animate and read comments panel
Recomendados
Recomendados
Mais conteúdo relacionado
Mais de Andrew Zolnai
Mais de Andrew Zolnai (20)
Último
Último (20)
MDM_123
- 1. 1 Master Data Mgmt. blueprint Project data/ Interp. Project data/ Interp. Archive / Master “Gold Copy” Seismic / Daily Prod Data Freeze Data Migrate Add Delta New Server Project Data / Interpret Staging Server Seismic / Daily Prod Static WMS Dynamic WFS GIS / Interoperability Viewing portal (click to animate slide show read more in notes panel)
Notas do Editor
- Data from vendors & partners (outside) / asset teams & central repository (inside) is interpreted locally From time to time (after project closure, or before a lease sale, etc.) data is promoted or staged: A data custodian / DM team ensures their accuracy and sends bad data back for clean-up (UWI naming & CRS the most common issue, as are shot point or log trace errors) If clean then data are referenced to the master data repository (aka. Archive) This is the good copy in corporate central repository that can be re-used by all: This goes along with a metadata repository management to help find same Viewing portal relies on that for distribution across teams or to partners and agencies Add geoportal stack (GIS / interoperabilty on master data, static and dynamic viewers as needed) Rarely starts with this situation, one usually folds an existing system into a new framework: Agree on a ‘freeze date’ to start migrating all data to an isolated testing environment Migrate the data and create/adjust/improve all the workflows to meet business needs Agree on a ‘go live date’ when: All workflows are deemed by asset/function teams to work Old test environment becomes new production environment Old production is kept as fail-over just in case something fails Add ‘delta’ (incremental data accumulated since freeze date) New environment fully functional, then retire the old environment