Mainly used during the "operation" phase, OPIDIS is software which can be adopted upstream of the project life cycle: directly from the "engineering" phase.
This, to avoid various constraints relative to the operations (structuralization rules, coherence of metadatas, delivery of native files), and errors stemmed from the initial documentation. But also, to take advantage of a quality database from the starting up of the installations. It allows organizations to avoid any additional budget, and to limit strongly the deadlines to get an optimal information system (often requiring many years).
Focus on the adoption of OPIDIS according to the various phases of the project life cycle
1. OPIDIS implemetation during the « Operation » phase
This is an Electronic Technical Document Management solution
Strengths
- Benefit from an Electronic Technical Document Management solution with the documents stemming from the data book
|
Weaknesses
- Constraints relative to the operations (structuralization rules, coherence of metadatas, delivery of native files) not dreaded during the project
- “Best-tried” implementation with what we get back from the data book
- Operations database available between 4 and 8 months after the starting up of the installations
- Quality of the database (realized from the data book) not optimal (PDF copies delivery and not native files, unexploitable metadatas)
- Existing errors in the untreated documentation because they are identified too late
- Not guaranteed access to the information (no coherence between the various reference tables)
- Additional costs (case of PDF files delivery, and delivered documentation) for an optimal use of the target system (information system interface)
- Additional budgets not planned for the “operation” phase and important deadlines to get an optimal system
|
2. OPIDIS implementation during the « Engeeniring » phase
This is a compliant information system, and not only an Electronic Technical Document Management solution
Strengths
- Production of documents with consideration of the future constraints (indexation, access to the documentation in particular and to the technical information)
- Quality control of the delivered files and respect of rules according to the deliveries of package in the native format
- Errors corrected during the entire project. Optimal quality of the documentation for the delivery of the data book
- “Operation” database delivered for the starting up without additional cost for the project or the final operators
- Technical documentation available on every stage of the project in a centralized reference table, and in particular for the starting up of the installations, with simple and intuitive access
- Easier tasks (commissionning, start-up, training, procedures writing, procedures of maintenance, plans of inspection)
|
Weaknesses
- Difficulty to impose structuralization rules (often necessary to guarantee a coherent target system: syntactic recognition of metadatas)
- Deliveries not always made in the native format (sometimes in PDF), not making easy the validation of the delivered documents quality
|
3. OPIDIS implementation before the "engeeniring" phase (during the "feed")
OPIDIS implementation can be made upstream of the "Engineering" phase: during the "feed". Thus, there are additional interests in this implementation:
- Guarantee of a reliable and coherent target information system based on the expertise of ARTESYS International for the EPD calls for tender
- Defined rules to obtain this reliable and coherent target information system, integrated into the specifications and becoming contractual
- Quality of the documentation delivered in the future packages, (with the delivery of native files in every stage for their validation)
- Feed database proposed to the EPC to make easier the answer to the consultation, with simple access to the centralized and validated documentation
|
