Asset Information Requirements In support of Sellafield’s Operational lifecycle

1. Asset Information Requirements In support of Sellafield’s Operational lifecycle

2. Workshop introduction • Who we are • What we’ll cover • Why it’s important

3. Sellafield has the same infrastructures as a small town. • Utilities, including water steam and chemicals. • Facilities Management Service. (Inc. maintenance) • An armed police force. • A civilian guard force. • Emergency services. i.e. Fire and Rescue, • and a medical team Inc. paramedics • Laundry. • Postal Service. • Canteens. • Shops. • A road and rail networks (Inc. maintenance). • Stores Network • Dive team. • Etc. …

4. Why Operationally we need a consistent Tagging Code strategy? • Current asset portfolio • 640,000 registered Tags • ½ million registered spares. • In excess of 88,000 active maintenance services Requirements • Consistent Tag information and codes are a key information source which impact on a number of Sellafield Ltd processes and systems. • Tag information is one of the key enablers for short and long term asset management of Plant and Equipment. • If not collected and maintained at the appropriate point in a project, It will be more expensive and difficult to retrospectively gather and apply. • BIM is the foundation for all new builds at Sellafield and necessitates the use of a consistent Tagging Code strategy

5. Tag Labelling installation is dependant on the environment and their geospatial location

6. Asset Register Examples of some of the attributes that are required to support the whole life cycle for the Asset Maintenance Instruction O&M Manual Scheduling Info Drawings Settings/ Parameters Asset Location Spares/ Obsolescence Calibration Equipment Required Parent/Child Associations (Planning) Category Tagging & Labelling Function/ Duty

7. Current Process (New build) Assets are typically created during the project design phase (recorded in some media i.e. spreadsheets?). Usually supplied at the end of build stage of a structure or facility. Was manually inputted into the MEL but use of Smart Data tools allows for bulk inputting! Projects provide the construction organisation with SL processes and procedures for the Identification and labelling of assets together with the labelling standards, materials to be used etc.. In turn Construction should provide consistent information relating to the P&E build. Existing Build Operations are expected to collection, maintain Asset information Inc. Tagging and Labelling. NB Inspection of Assets and their tagging are usually included as part of the planned Examination Inspection Maintenance and Testing regime performed by the Operations Maintenance team. In addition Operators are also expected to perform labelling integrity checks as part of their work activities

8. Current Labelling Nomenclatures Attributes Inconsistent Labelling Nomenclature Example #1 PRESSURE LOOP PdIA-349 PRESSURE LOOP PdIA-349 Inconsistent Tag Labelling DIFF PRESSURE PIA-349 DEMIN WATER PRESSURE P-349

9. Current Labelling Nomenclatures Inconsistent Labelling Nomenclature Example #3

10. ‘Situation and Current Practices’ referenced in the Challenge Statement. Problem statement: • Current processes generally require manual intervention resulting in the risk of Information loss across the operational lifecycle of a facility. • Identifying the appropriate material and fixings for tags is at best, based on the design of the Plant and at worst what materials the local teams are able to manufacture. • Tagging standards have matured incrementally across the life of the site. • Some site departments have attempted to introduce Bar coded tagging i.e. fire services and Facilities Management. • Understanding of Tagging information is hindered by inconsistent information and understanding • One official tag register but many informal tag registers • Tagging governance is inconsistent across the business • Applying and managing a consistent nomenclature to new tags is not easily achieved • Projects and Suppliers have used diverse tagging nomenclatures in creating labels • Operations also have used diverse tagging nomenclatures to create labels. • Changes to tagging data usually via SL’s configuration change management process. This is a manual process requiring relevant stakeholders to formally agree to and act upon these modifications. • Tag records when updated i.e. changes in status, conditions, documentation references etc. are not always consistent or linked to the Tag/Asset registers.

11. Functional Class ELECTRIC MOTOR Attributes (53) BUILDING RATED SPEED DIRECTION OF ROTATION Etc…… Documentation PROCESS ENGINEERING DIAG SINGLE LINE DIAG EQUIPMENT DATA SHEET Etc. …. Example of the proposed Functional Tag & Physical Equipment Nomenclature Functional Asset Functional Asset Tag Asset Label BXXX-M-000000012 000000012 BXXX- M-000000012 SHEAR PACK MOTOR 000000012 NB Functional Asset Label would be a concatenation of their Functional class & attribute data. M ******** Interchangeable Plant Equipment Physical Class (14) AC MOTOR Attributes (3) MANUFACTURER MODEL SERIAL NUMBER Etc. ….. Documentation OPERATING MANUAL SPARES PARTS LIST Ref No 000000322 000000322 Physical Asset Label Physical Equipment *NB Functional Class is aligned to the Functional Requirements of the Asset Physical Class is aligned to the requirements of the Equipment

12. The Future of Sellafield’s Physical Asset Operational Management Requirements : • ‘Cradle to grave’. Consistent information from Project design, manufacture, transportation, storage, installation through to asset disposal. • Ability to assign agnostic ref codes to all functional Tags and Physical assets, allowing for real time and lifecycle tracking. • Identify, collection, and registration of asset information to support Technical basis for lifecycle maintenance and decision making. • Machine readable Plant labelling i.e. Bar codes, Quick Response Codes (QR) coding, Radio-frequency Identification (RFID) etc. • Intelligent centralised operations collaborative interfaces for asset tracking. • Provision of analytics e.g. cost, risk, performance, efficiency, safety etc. • Potential integration with existing enterprise solutions e.g. Enterprise Asset Management software. • Ensures that functional and physical assets are aligned with their documentation/information attributes.

13. The Future of Sellafield’s Physical Asset Operational Management Requirements (continued) • Improved configuration management of physical assets. • Potential to integrate links to safety, legal or security requirements. • Potential to Improve consistent standard working practices. • Collaborative and efficient work streams with PPP and internal operational teams. • Visualisation of assets against a digital model (digital twin?). • The control and governance of data. • High level of security/access rights. • Efficient mobile working and decision making. • Improved asset management. • Efficiencies from use of improved quality of data which in turn reduces further duplication, Improved data integrity. • Reduced time locating information. • Improved documentation, inspection certification, records and knowledge management.