Transformation of Digital Requirements: An Enabler for Successful Complex Projects

2021 ◽  
Author(s):  
Abe Hudson ◽  
Jim Marsh
Keyword(s):  
Management System ◽  
Lessons Learned ◽  
Mitigation Strategies ◽  
Management Tool ◽  
Requirements Management ◽  
Complex Projects ◽  
System Data ◽  
Database Operations

Abstract This paper discusses the lessons learned from transforming upstream operational requirements from a document environment into a requirements management tool (database). Operations requirements from upstream practices, procedures, specifications, and guides were migrated from a document centric environment into a requirements management system (data centric). Here, requirements were assigned attributes denoting the organization and accountable operational role that requirement. Many organizations, operating complex offshore procedures, especially where operations are highly regulated, are looking to move their operational requirements from a document centric environment to a data centric environment. This paper highlights some potential pitfalls and mitigation strategies for ensuring a successful migration.

ICS CONTRIBUTES TO THE NORTH CAPE OIL SPILL RESPONSE1

1997 ◽  
Vol 1997 (1) ◽  
pp. 737-742
Author(s):  
LT Tina M. Burke ◽  
LT John P. Flynn
Keyword(s):  
Oil Spill ◽  
Management System ◽  
Lessons Learned ◽  
Coast Guard ◽  
Management Tool ◽  
Incident Management ◽  
Incident Command System ◽  
Incident Command ◽  
The North ◽  
Oil Spill Response

ABSTRACT In recent years, the usefulness of the incident command system (ICS) has received much attention. Much of the oil industry and several government agencies involved in all types of emergency response have been using ICS for many years. In addition, the U.S. Coast Guard formally adopted the national interagency incident management system (NIIMS) ICS as the response management system of choice in February of 1996. The response to the tank barge North Cape grounding was a complex multiagency effort that brought with it many of the issues and problems responders face when dealing with crisis situations. This paper describes the ICS-based organization that was established to respond to the major North Cape oil spill, analyzes the organization compared to standard ICS, and discusses how the ICS framework and principles contributed to the success of the response. It also explains how closer conformity to standard ICS could have remedied many of the issues that later surfaced as lessons learned, resulting in improved response efficiency. The North Cape response provides a vivid example of how ICS is a helpful management tool that, if rigorously learned and applied in a widespread fashion, can greatly enhance the nation's oil spill response posture.

Common Pitfalls and Shortcomings of Lessons Learned Programs

2014 ◽  
pp. 221-233
Author(s):  
Ian Fry
Keyword(s):  
Quality Control ◽  
Learning Organization ◽  
Management System ◽  
Lessons Learned ◽  
Mitigation Strategies ◽  
System Quality ◽  
Knowledge Capture ◽  
Implementation Processes ◽  
Implementation Level ◽  
Lasting Change

While many organizations attempt to implement a Lessons Learned program, very few reach a state of becoming a “Learning Organization.” Surveys conducted by Knoco show that when asked how effective the program was, the average self-assessed score is 48%. Much of the problem is a lack of sufficient skilled and appropriate people, assessment and implementation processes, technology and governance; but even when these are in place, the single most common problem is that lessons are treated as observations and rarely used to drive lasting change. In addition, we find issues such as a lack of governance around the lesson-learning process, the lessons database is seen as a repository not a lessons management system, quality control is needed at the input stage, and ensuring sufficient evaluation. This chapter describes these problems and outlines some mitigation strategies to shift observations and knowledge capture to a more applied implementation level.

Benefits of Using Requirements Management Tools on a Digitized API 17O Document

2021 ◽  
Author(s):  
Reynaldo Celestial Climacosa ◽  
Sierra Foster Matlock ◽  
Joveline Anne Ollero ◽  
David Miller
Keyword(s):  
Oil And Gas ◽  
American Petroleum Institute ◽  
Lessons Learned ◽  
Management Tool ◽  
Background Information ◽  
Requirements Management ◽  
Management Tools ◽  
Requirements Quality ◽  
High Integrity ◽  
Oil And Gas Companies

Abstract Currently oil and gas companies are spending billions of dollars on digitalization efforts. One important aspect of a project that needs to be digitized are requirements. Most oil and gas companies receive project documentation and requirements as PDF files. Receiving PDF documents make it very difficult for companies to manipulate the content to identify which parts of the document are requirements and which parts are just background information. In addition, documents that contain requirements have poorly written requirements that are ambiguous, and can have many interpretations, making it difficult to show compliance. To solve the issues caused by poorly written requirements and receiving PDF files instead of receiving requirements in a more usable format, the solution is to rewrite the requirements and use a requirements management (RM) tool to put the requirements in a database. The American Petroleum Institute (API) 17O 2nd Edition document and a representative list of High Integrity Pressure Protection System (HIPPS) product requirements are used to show the benefits of using a requirements management tool. This paper will describe the prerequisites prior to selecting an RM tool, show how using a requirements quality analyzer tool can aid in preparing requirements to be imported into an RM tool, demonstrate the main benefits of using an RM tool in a project context, and discuss lessons learned from adding an RM tool to a document-based project.

scholarly journals Archnet 2.0: Building a new asset management system for MIT’s online architectural library of the Islamic World

2017 ◽  
Author(s):  
Andrea Schuler
Keyword(s):  
Asset Management ◽  
Management System ◽  
Lessons Learned ◽  
Management Tool ◽  
Islamic World ◽  
Archival Material ◽  
Database Structure ◽  
Course Syllabi ◽  
And Migration ◽  
Asset Management System

Archnet 2.0 is a new front end website and back end cataloging tool and asset management system for Archnet (http://archnet.org), the largest openly accessible online architectural library focusing on the Muslim world. The site, a partnership between the Massachusetts Institute for Technology and the Aga Khan Trust for Culture (AKTC), contains articles and publications, images, maps and drawings, video, archival material, course syllabi, and site records relating to architecture in the Islamic world. By 2012, when the Aga Khan Documentation Center (AKDC) at MIT, part of the MIT Libraries, took over the digital library, the site has become dated and was no longer meeting the needs of its users. A software development firm was hired to build new front and back ends for the site. This paper explores the development of the new back end cataloging and asset management tool, including the reasoning behind building a new tool from scratch; considerations during development such as database structure, fields, and migration; highlights of features; and lessons learned from the process.

Sign in / Sign up

Export Citation Format

Share Document