There are many tabs available in Credo5. At first glance it may be confusing as to what each tab is for and what terms such as Object and Event mean. This section should explain this.

View files are simply your key to a view of a selection of records in your Credo database. When you open Credo you will see the “View” tab which contains many views to show various items in Credo, such as different types of Objects, Events, Anomalies and more. Views can be further organised with the use of folders, which can be Private and only visible to the user who creates the folder, or Public and accessible to all users.

In some areas of Credo (e.g. the View tab) there are two types of folders available to the user. These are PRIVATE and PUBLIC.

PRIVATE folders are for individual users only. The PRIVATE folders are visible to the individual only.

PUBLIC folders are visible for all users to consult on a read only basis.

“ + ” signs indicate that sub levels are available. Double clicking on this sign will reveal those levels.

The short cut key F8 can be used to show the sub levels (expand the tree) and F9 can be used to hide the sub levels (collapse the tree).

In Credo, users are known as Players. Each person who uses Credo needs to be created as a Player inside the application to allow them to use Credo.

Players have Oracle roles assigned to them to determine their security level. The Players then have a further security filter as individual Permissions are selected for each Player. If the Player has a certain Qualification that is important to the system it can also be added.

If the Workflow module has been purchased, Teams can be created and Players can be assigned to the Teams. Teams can be setup to only allow Players to join if they have a suitable Qualification.

The Workflow section consists of a Process Tree which contains a number of Tasks. Each Task is carried out by a certain Team. A Workpack (an Event and a Report Template) moves through these Tasks and at each stage, the Report Template can be opened and the relevant section edited by the Team carrying out that particular task. Other sections of the Report Template can be restricted to allow only the relevant Team to edit the Report at a certain Task in the Workflow.

An Object represents an item of Equipment stored in the Credo database such as a Pipe, Vessel or Column.

Objects can be created at both Top and Sub Level. Typically the Top Level Object would be the main piece of Equipment e.g. a Pipe. There would then be Sub Level Objects such as Vessels.

There are many different Object Property Tables available which can be used to store all data connected to an Object; from the material it is manufactured from, to regression results. In short, you can enter as much data as is required to define the Object, within reason of course. Where there is no predefined Property Table that meets your needs, ‘user definable’ properties have been provided which should allow enough room for even the most detailed Objects. The properties that are shown in an Object View are configured by the Credo administrator and cannot be changed by the end user.

Points are commonly stored against Objects at the second level of the Object hierarchy. A Point represents a specific location on the Object where a measured value such as a wall thickness reading can be stored.

There is no limit to the amount of Points that can be created for any one Object.

The Calculator module can be used to calculate a chosen formula against a Point. The result can then be sent to a field in the Point table for the users to view. The calculator is an additional Credo module which is purchased separately from Credo.

Events can be created for any Objects in an Object View. An Object represents an item of Equipment stored in the Credo database such as a Pipe, Vessel or Column. Many Objects will require inspections to be carried out. This could be a Visual Examination, Thickness Reading or another type of inspection. Each inspection can be thought of as an Event.

A list of all Events that have been scheduled or planned. These may have been completed or not started yet.

An Event Plan allows you to specify Event parameters for an Object. When the Event Plan is ‘Applied’, an Event is created based on the predefined parameters.

An Object can have as many Event Plans as is required, one for each type of Inspection being the most common example. The Event Planner tab helps to automate the creation of new Inspections (Events) based on a custom inspection interval. The Planner will compare the Object Event Plan to the current Event schedule and create new Events as required.

A new Event Date is calculated in two ways:

1. The interval is added to a user defined OBJSTARTPLAN value which is a property of the Object.
2. The Interval is added to the most recent CLOSED inspection which has a valid EMDATECLOSED date value and shares the same EVENTNAME as the Event Plan EVPEVENTNAME.

An anomaly is a defect found whilst carrying out an inspection that may need a corrective action. Anomalies can either be stored as sub events or by using the Anomaly tab (legacy).

Objects, Events and Points can have Attachments and URLs attached to them. Attachments can be documents, images, sketches or any other file related to the item in Credo. URLs are website addresses to useful sites relating to the item in Credo.

The “Notepad” tab against Objects or Events is a simple text editor which can be used to store information about the selected Object or Event.

As the Notepad is a graphical text editor, it contains many features that you will find in software such as Microsoft Word. For example, features are available to format text, copy and paste from other applications and more.

The Functional Location feature allows you to create and manage the relationship between moveable Objects such as PSVs and other Objects. If an Object in the Database is connected or related to another Object in the Database, the “Connect” tab can be used to display the Properties and related information for the other Object (Events, Points etc).

The following image explains how the various parts connect together in Credo: