Capital Project Execution
You should expect substantial savings generating SIS compliance documentation. First, why have multiple tools when aeShield supports the process safety lifecycle from soup to nuts?
(See Figure 1)
Figure 1 - Consolidated Toolkit
Second, with a data model from a risk ranking to an individual device on a protection layer, information seamlessly transfers from one discipline to the next. Traditionally, multiple tools combined with multiple technical disciplines have created communication inefficiencies and version control nightmares throughout the project especially when change occurs – as it always does.
Lastly, aeShield comes equipped with the ability to build protection layer templates and even group multiple templates into equipment under control (i.e. - fired devices, compressor stations, etc.). The following documents can be “templatized”:
- SIF List
- IPL List
- Safety Requirement Specification
- Cover Document
- SIF Datasheet
- Design and Verification Report
- Cover Document
- IL Verification per SIF
- Non-SIF IPL Requirements Datasheet
- Intersections on Cause & Effect Matrices
- Test procedures accounting for every device requiring periodic testing
For example, you can have your most SIS competent engineers architect designs for future use and use aeShield’s intuitive user permission model to lock-down the approved design in a library.
(See Figure 2)
Figure 2 - Simple Compressor Station Cartoon
Templates can be built from scratch or copied from existing designs already built in the application. Moving forward, junior engineers or contractors can instantiate designs, replace tags, and modify only what makes this new protection layers or equipment design unique.
(See Figure 3)
Figure 3 - Workflow and Tag Replacement Screenshot
In summary, the 1-2-3 punch of a consolidated toolkit, single source of truth for data under revision control, and “templatization” will produce substantial saving as opposed to the tradition approach. Depending on your copy-factor (similarity between protection layers and equipment under control), you WILL reduce man-hours, drive consistency, and ensure functional safety regarding your capital project.
Please contact us immediately to use your capital project figures in a calculator to learn how much savings are at stake.
Click the tabs below to see more example of how aeShield® can help streamline your project execution processes.
aeShield® provides administrators the ability to define roles and assign users to roles for specific needs. Permissions can be assigned based on location allowing users to have different permissions at different facilities. Having control over permissions also allows administrators to easily add contract workers and assign specific permissions for those users.
Information is vital when making decisions across the organization. Having data readily available for reporting and sharing with others in the organization is vital. aeShield® centralizes your process safety data and makes it available in a central location. Data can be shared more easily and updates to that data managed more efficiently. Reports from aeShield® can be exported in multiple formats to be used across the organization.
The management of change (MOC) process in aeShield® requires promotion of edited project level data before that data can become the master, or AsBuilt data. Data must be 'checked' and then 'approved' before promoted to AsBuilt. Associates within your organization can be identified as users with authority to perform the 'check', 'approve' and 'AsBuilt' Direct Work toward correct competencies.
Project managers can easily track activity percentage completion and document 'check' and 'approval' status through our reporting such as the 'Test Plan Status' report shown below.
Project journals give those reviewing projects the ability to monitor project status, communicate with team and access documentation quickly. Project journals have a comment component where activity performed against the project is displayed and custom comments can be entered by the team. The file component allows team members to upload relevant files and documentation against the project. Customizable project categories allow users to associate comments and files to specific project areas. This information can then be rolled-up across the organization through widgets in the health meter designed to monitor project categories for comments and associated files.
Through the templatization features of aeShield® common templates can be created for a project allowing for more consistency and less data entry during project execution. Templates can be created for safety instrumented function (SIF) design, safety requirements specification (SRS) datasheet and functional proof test plans through test procedures.