Business Unit: Engineering & Maintenance Branch, Asset Management Division - Asset Services & Governance, EMB
Start Date: 01 June 2025
End Date : 19th December 2025
Hours of work: 8 max hrs a day, 40 hrs per week (no overtime will be paid – 6 hours or less will be half) – if daily
Is the role Hybrid: Business expectations 2-3 days per week in the office
Direct Reports: No - role will engage widely and work closely with multiple stakeholders
Possibility of extension: Possible however unlikely
Team Structure: This role is part of the RCM replacement Tool Implementation Program Core Team. The Core Team will comprise 7 key roles, supported by the Summplers implementation team and key business Subject Matter Experts
Sydney Trains Context
Sydney Trains operates in the rail sector of the Transport for NSW cluster, and maintains over 756,000 rail assets that includes 1,599km of track, 1,536km of overhead wiring, 2,263 electric and diesel fleet cars, and 169 stations. Sydney Trains has annual maintenance budget of $1.5 billion and an asset portfolio valued at over 46 billion. On average, there are 147 million passenger journeys recorded across the Sydney Trains network every year.
As the largest rail operator in Australia, Sydney Trains is committed to delivering safe, clean, reliable, customer-focused and efficient rail services which is demonstrated through our key priorities.
Business Area
Asset Services & Governance is responsible for the determination of preventive maintenance requirements for both existing (in-service) and new assets and the specification of technical maintenance tasks documented in Technical Maintenance Plans (TMPs). The development of TMPs, utilises Reliability-Centered Maintenance (RCM) and Failure Mode Effects and Criticality Analysis (FMECA) methods.
A wide range of stakeholders are engaged across the TMP lifecycle which include maintenance divisions for Infrastructure and Rolling Stock (Fleet), Major Works (New Assets), Customer Operations, Engineering Systems Integrity, and Transport.
RCM Tool (MIMIR) Replacement Program Overview
Sydney Trains employs Reliability Centred Maintenance (RCM) analysis to enhance network resilience and asset reliability to enhance Rail operations.
The current RCM tool (called ‘MIMIR’) has reached end of life with technology obsolescence and incompatibility with modern systems and architecture’s being driving factors to sunsetting the system combined with the risk of failure to meet key obligations potentially leading to noncompliance with legislation and TfNSW technical standards.
RCM analysis techniques are used in the development of Technical Maintenance Plans (TMPs) for both new and in service assets to identify, assess, and document the preventative maintenance tasks necessary to assure the achievement of business objectives for a given set of assets.
Multiple options were considered for replacement of MIMIR to mitigate this risk with the chosen option to select though competitive tender an industry-based solution.
Legacy Data Environment
There are 3 versions of MIMIR database housed in Microsoft Assess Databases (v97 and v2003) used within the organisation. MIMIR allows users to duplicate databases and save them locally or on a network drive. Over the lifespan of the system, this has resulted in many hundreds of databases have been kept supporting historical TMP optimisation decisions, and recommendations.
Although the database schema for all 3 versions is similar, they are not identical, and each version will have different data migration requirements for sourcing, cleansing, and preparation for loading of legacy data. There are no APIs available for data migration from MIMIR (Access 97/2003).
Spreadsheets have been used as an alternative when MIMIR functions stopped working. In some cases, spreadsheets hold the latest RCM information for newly acquired assets.
RCM analysis performed by external organisations has been published in the form of PDF, with the FMEA/FMECA information embedded within it. This information will require manual interpretation and extraction to enable entry into the new system
About the Role
The RCM Senior Data Analyst will engage with key stakeholders for all activities related to RCM legacy data identification, review, classification, validation, cleansing, migration, and quality assurance of existing data sources to the vendors system.
The role will work with the internal stakeholders and approved vendors on RCM data design, integration, solution design requirements, and ensure all data activities meet the requirements for data quality and completeness, testing, data governance, availability, currency, usability, integrity, and security, aligned to organisational policy and technical standards.
Day to day Duties:
· Establish RCM data governance processes and procedures for the management of RCM data quality aligned to ISO 8000 series of published standards – (global standard for Data Quality and Enterprise Master Data).
· Establish master data processes and data hierarchy suitable for RCM analysis and document data definitions, dictionaries, data processes and reference materials
· Determine the As-Is and future-state data requirements in conjunction with business stakeholders.
· Manage the capture, identification, assessment, collation and validation of existing RCM data sources.
· Work with stakeholders to analyse data requirements across multiple sources to identify data quality & deficiencies, to develop tools & processes to extract, transform & clean the data to an accepted accuracy.
· Establish processes with key internal stakeholders to collect MRA data and hand over to the TMP team for new assets as they become operational.
· Provide subject matter expertise to business stakeholders to facilitate agreement and sign-off on data quality requirements, data load templates, and the review and assurance of migrated data.
Key challenges
· Work with stakeholders across potentially hundreds of data sources, requiring review, validation, cleansing, and quality assurance of legacy RCM data in a highly technically assured environment that is standards driven
· Understand relationship between components of business processes and the data requirements that support those process through the TMP lifecycle.
· Work independently with follow through and maintain a flexible approach to respond to a fast-paced changing environment.
Requirements
Technical Capabilities
· Experience in Azure cloud solutions, (Fabric, Synapse, Data Factory) and Power BI (or similar data visualisation tool).
· Proficient in SQL with the ability to write & develop complex queries and validate / verify outputs.
· Technical ability to write & test Python scripts to drive automation and data quality.
· Knowledge and experience with SAP EAM data structures and standards, preferably in the Sydney Trains environment
Key knowledge, skills, and experience
· Strong interpersonal skills, critical thinking, data analysis, and proficiency in translating complex data into simplified models, with good communication & articulation skills.
· Tertiary qualification in a field such as Software Engineering, Computer Science, Statistics, Mathematics, Data Science, or equivalent, with a preference for a degree or diploma and significant relevant experience.
· Experience in data modelling, orchestration, automation and translating business rules into data models & frameworks.
· Demonstrated experience in managing and engaging stakeholders, facilitating workshops, determining data requirements from business requirements, and gaining business endorsement on agreed outcomes.
· Technical knowledge of system architecture and standards and ability to communicate and engage with IT architecture and systems experts on data and systems requirements.
· Experience in documenting and interpreting the data requirements for asset management lifecycle processes and practices in alignment with ISO or equivalent standards.
· Experience in establishing Data Security and Data Governance processes.
· Capacity to operate both independently using initiative and self-direction and as a team member to produce consistently high-quality work.