NCR, U 2730 - Transmisores de Vibración como Viscosidad, U 2730 - Alarmes…
30 Structures|Z10 Customers|AAC Anglo American|M41 EI&C
30 Structures|Z10 Customers|AAQ Quellavecco|M41 EI&C
Base objects diversity - Instrumentos Objetos Básicos de P&IDs podem variar de uma subunidade para outra
ou mesmo de um P&ID para outro, pois não compartilham um Base Object comum.
Criação de objetos de forma não padronizada no banco de dados, ou seja, a execução não realizado em conformidade com as normas da Siemens, conforme indicado no treinamento recebido do mesmo provedor.
Datasheets: All Smart Plant Instrumentation Datasheets were created in COMOS DB
Datasheets Fluor is creating were not in Smart Plant DB and for this technical relevant data were missing
No specific type defined or a type that COMOS could not categorized it to a specific base object and instead it sets a generic one.
There is no data error secondary effect in the database as all attributes related were migrated and are available to be consulted by End User.
Siemens has already tracked all cases and will correct it without any costs to Fluor/Anglo.
Siemens recognizes part of the claimed hours – Siemens recognized hours: 40h
Siemens has created instruments as “Functions” for the following reasons:
- it is defined in Anglo American COMOS Data Model with the purpose of data standardization. (Ref: CCM0170-
F-1-02_DOC-001 „Anglo American COMOS Data Model – Administration Manual)
- alarms have ISA representation on the P&IDs and therefore must be set as “Function”.
Siemens does NOT recognize this as nonconformity neither that this has caused any delays on
The mentioned folders which are coming from different sources in the database is not wrong. It is not only
a COMOS’ best practices but also is defined in Anglo American’s COMOS Data Model (Ref: CC-M0170-F-
1-02_DOC-001 „Anglo American COMOS Data Model – Administration Manual). The following rules apply:
- Engineering devices without any customer specific configuration are linked with standard COMOS
- Engineering devices with customer specific configuration according to Anglo American Corporate
standards are linked to “AAC” node base objects
Engineering devices with customer specific configuration according to Anglo American Quellaveco
standards are linked to “AAQ” node base objects
This item refers to same problems described in item 1 and similar issues basically related to wrong base
objects pointed to same engineering objects during data migration from Smart Plant to COMOS.
Please consider same answer as item 1.
Note that, Fluor’s staff training were provided to qualify users to work in COMOS independently if the
database has or not Anglo Americans specific content. COMOS allows users and companies to arrange
their structures and objects according to their needs without disabling COMOS core features of data
search, queries, inheritance and others. Therefore, any specific configuration done in accordance to Anglo
American COMOS Data Model do not impact in the tool usage.
A-Topic is related to “End Point Connection diagram”, which was not part of any Siemens scope (700832)
and COMOS was not even prepared to generate such document automatically. Siemens recognize, however, the set of a generic base objects in such cases can was not optimal (see our answer in item 1).
Siemens recognized hours: 40h
B-2730 has NO metadata available in SPI, The only technical data migrated to COMOS was coming via the MPL and SPPID.
Siemens recognized hours: 0h