rolls-royce data storytelling challenge scenario … · for the scope of the data storytelling...

ROLLS-ROYCE DATA STORYTELLING CHALLENGE – SCENARIOBRIEFINGDOCUMENT

2IntroductionThe purpose of this document is to describe the scenario in the accompanying Visualisation Data Set.

In this document, an overview is provided of the Services, Cost and Availability Forecasting (SCAF) Model utilised by Rolls-Royce, which is followed by the scenario for the simulation forecast, and a brief introduction to the stakeholders interested in viewing the forecast output.

ContentsThe SCAF Model ............................................ 3

Competition Scenario .................................. 5

The Data Set .................................................. 9

Definitions and Acronyms ......................... 12

Data Set References .................................... 15

Questions and Contact .............................. 39

3The SCAF ModelForecasting is a critical capability in Rolls-Royce in support of winning new business, maintaining existing long term service contracts and developing new service solutions.

The SCAF Services, Cost and Availability Forecasting (SCAF) Model was created with the aim of providing next-generation business forecasting capability across several functions within Rolls-Royce. The model provides predictions of when engines will be removed from service, as well as demand for high value parts, maintenance cost and capacity, used for medium and long term business planning.

In particular, a SCAF run simulates aircraft operations and models how the condition of the engines is affected by executing these operations. It also models the necessary maintenance work to keep the engines in a serviceable state. Moreover, the simulation includes scheduled changes to operations (e.g. increase/decrease in frequency) and to aircraft and engines (e.g. adding new aircraft/engines or retiring them).

The main system components in the SCAF model are:

• The roles, which represent system actors responsible for business function• The processes, which illustrate the tasks completed by the roles• The assets, which represent the structural elements of the model• The facilities, which refer to physical locations in the system

For the purpose of this document, only descriptions of the facilities and assets are included.

FacilitiesThe SCAF model includes the following facilities:

a) Operating site: This is where the aircraft (called platforms) and the people responsible for managing them and keeping them serviceable (i.e. roles) are located. It is also where the people who are responsible for managing the flight operations are located, and where the people responsible for managing the local inventory levels (of spare engines) are based.

b) Maintenance site: This is where the people who repair the engines (called assets) are based, and they also look after the inventory of spare assemblies and components.

c) Testing site: this is where engines are sent to test after they have been rebuilt in the maintenance site.

4AssetsThe following assets are available in the SCAF model:

• Platform: this is an aircraft, which will have two engines fitted• Equipment: represents a single engine• Assembly: a module inside the engine. An engine is a construct of a number

of assemblies• Component: is a part inside an assembly. Several components can be present

in an assembly. Components have several failure modes, which can be visible at inspection or at maintenance

A visual representation of the assets (and corresponding terms) is shown in Figure 1. Please note that the figure is for illustrative purposes only and the exact number of assets may vary.

Figure 1: Assets and their corresponding terms

In a SCAF simulation, components age as they are operated, and from time to time they may ‘fail’ according to a sampled failure distribution. In this case, failure means that it requires maintenance rather than it has been destroyed. When the engine experiences a failure, or if a component has exceeded its pre-determined life limit, the engine is removed from the aircraft and sent to maintenance. The aircraft is out of service whilst this engine removal and refit of an alternative takes place. Upon the engine presenting at an engine repair site, any component that has failed or exceeded its ‘soft life’ will be rejected for maintenance, and any other component that is subject of a maintenance policy or has worn beyond serviceability limits will also be rejected. All rejected components will be examined to see if they are repairable; those that are will be repaired, those that are not will be replaced. The engine is then re-assembled when all the parts of the build kit have been collated (which comprises both existing serviceable parts, repaired parts and new parts); it is then tested and returned to service.

SCAF is a multi-pass simulation model. One possible future prediction is made per pass, and because we sample random numbers it is necessary to do multiple passes to generate a range of possible future outcomes – the end prediction is a statistical analysis across all the possible futures predicted.

AIRCRAFT(‘PLATFORM’ IN THE DATA SET)

ENGINE (‘EQUIPMENT' IN THE DATA SET)

MODULE (‘ASSEMBLY’ IN THE DATA SET)

PART (‘COMPONENT’ IN THE DATA SET)

5Competition ScenarioIn the scenario, we consider an operator who manages a fleet of aircraft. This is sub-divided into three sub-fleets, where each sub-fleet is assigned to a different operation (which is described in terms of flying hours per month over time). There are a number of aircraft assigned to each task, and the rate of flying may change over time. Each platform has two engines and each engine has 13 modules/assemblies, which in turn have several components.

The forecast spans a timeframe of 15 years. During the planned period, one of the sub-fleets increases in size, another one decreases in size and the last one remains unchanged.

Figure 2: Hierarchy of assets within the operator’s fleet

OPERATES 3 SUB-FLEETS

EACH AIRCRAFT HAS

2 ENGINES

EACH ENGINE HAS 13 MODULES

EACH MODULE IS MADE UP OF A VARYING NUMBER OF COMPONENTS

THE SCENARIO AIRLINE

Subfleets change over time as new aircraft arrive and older ones are retired.

Subfleets change over time as new aircraft arrive and

older ones are retired.

6

We also consider one repair base and one overhaul base. Aircraft fly from and to the operating site, and when engines are removed for whatever reason, they are sent to a maintenance site (a repair base is one type of maintenance site where engines may be repaired, an overhaul site is another type of maintenance base where the engine will be repaired and overhauled – the difference being the amount of proactive maintenance work that is undertaken to restore performance).

The overhaul is a heavy maintenance task, where the objective is to ensure the engine is fit for a ‘full service life’ – typically 4 years; whereas the repair is a light maintenance task, where the objective is to restore the engine for the remainder of its service life (an engine may need repair if it encounters wear or damage beyond normal expectations).

The repair time can vary during the forecast period as a result of policies or due to queuing time. The operator has a constraint on the number of spare engines. He has to replace engines that are sent for repair, thus when an engine is not available to replace one that has been removed, the aircraft will be grounded until a new spare engine or a repair engine becomes available.

For the scope of the Data Storytelling Challenge, the scenario we take into consideration includes the discovery of a component that starts to fail unexpectedly at high life, which disrupts the normal operation of the fleet. A modification campaign will then be released in order to fix the problem. A modification campaign is a plan to replace a component with a new standard (similar to a recall in automotive). There are choices over urgency depending on how critical the recall is.

Competition Scenario (continued)

7Competition Scenario (continued)The image below summarises the challenge at the heart of the scenario. It shows that engines should always be in one of two states - either In Operation or In Maintenance. Our role (using SCAF) is to optimise the flow of engines from Operations to Maintenance such that engines are never queueing for maintenance, aircraft are never left grounded, and we avoid oversupply of spares.

Figure 3: The scenario in summary - optimising engine use

IN OPERATION

IN MAINTENANCE

OUR JOB IS TO MAINTAIN ENGINES IN

THE MOST COST-EFFECTIVE, LEAST DISRUPTIVE WAY

OVER FIFTEEN YEARS

SPARE ENGINESSUB-FLEET 1 SUB-FLEET 2 SUB-FLEET 3

WEAR AND TEAR

BUSINESS POLICIES

REPAIR BASELIGHT MAINTENANCETo repair accidental damage

OVERHAUL BASEHEAVY MAINTENANCE

To renew the engine

8StakeholdersIn this section, we describe some of the real people in the business scenario (stakeholders) who are interested in viewing the reports generated from the forecast data.

• “Operator”: the main goal of the Operator is reliability (we assume that safety needs will always be satisfied, and therefore the goal is actually to deliver safe aircraft to flight operations). All aircraft and engines need regular maintenance to retain reliability and so the Operator needs to plan for aircraft downtime, in order to make sure enough aircraft are available when needed. To mitigate the risk of aircraft on ground (AOG), due to maintenance or reliability issues, there may be a need to use lease engines, and as such the Operator is interested in the availability of lease engines

• “Commercial Officer”: the Commercial Officer is interested in minimising the cost per year to perform maintenance and the overall cost in the contract, including any lease charges

• “Workshop Manager”: the Workshop Manager wants to achieve an even load on the MRO facility to minimise the time spent with rejected engines in queues, and thus needs information about the future demand of workshop visits, the degree of work to be done per workshop visit and spare parts availability

• “Spares Planner”: the Spares Planner is in charge of inventory management, and makes orders for new parts to the supply chain, such that the parts are available when needed, but the overall stock level is minimised, to reduce holding costs and overhead

• Supply chain: handles the demand for new parts

STAKEHOLDER OBJECTIVE INFORMATION REQUIRED

Operator • Minimise aircraft downtime

• Maximise fl eet reliability

• Maintenance scheduling

• Availability of lease engines

Commercial Offi cer • Minimise maintenance costs

• Minimise engine lease costs

• Maintenance scheduling

• Engine availability

Workshop Manager • Avoid maintenance queues

• Optimise facility use

• Future workshop visit requirements

• Expected maintenance requirements per visit

• Spare parts availability

Spares Planner • Ensure spare parts are available on demand

• Avoid oversupply costs

• Spare part stock levels

• Parts demand forecast

Supply Chain Manufacturer • Ensure spare parts are available and delivered on demand

• Spare part stock levels

• Parts demand forecast

Figure 4: Stakeholders

9The Data Set The data set contains the fictional output of multiple SCAF forecast iterations. It will be released as a Microsoft Access SQL database.

In the following sections, we include a high-level overview of the information in the data set, with a detailed description included in the Data References section of this document.

Clarification of the no exchange boolean value1 = “Yes” and 0 = “No”

What this means is if the value for “NO_EXCHANGE” = 1 (i.e. “Yes”) exchange of the modules/components is not allowed.

If the value for “NO_EXCHANGE” = 0 (i.e. “No”) exchange of the modules/components is allowed.

10Input dataThe data used as input to the SCAF simulation run is described in Table 1.

Table 1: Input data

Category Description

Fleet It contains information about the platforms in the fleet, as well as the list of assets (engines, assemblies and components) fitted within each of them. It also specifies the task to which each platform is assigned.

Operations It contains information related to the operational tasks, such as number of platforms required for each task, flight frequency and duration. It also specifies scheduled changes related to moving platforms and engines between different operating sites, and changes related to flying rate, etc.

Arisings It contains information related to planned/unplanned events, such as failures, probability of discovering failures, etc.

Regular Inspections It contains information related to regular inspections to be carried out during the simulation time and their frequency.

Maintenance It contains information related to facilities available for the forecast run, their capacity, maintenance times (strip and repair), transport times, etc. It also specifies details related to modification campaigns (start and finish dates, current and target modification standards, etc.) and platform maintenance.

Cost It contains information related to the cost incurred during shop visits for the recovery of an engine, for all labour involved in equipment and assembly strip and build activities, etc.

Stock It contains information related to the minimum number of assets in stock.

11Output DataThe data produced by a SCAF simulation run is described in Table 2.

Table 2: Output data

Category Description

Forecast It contains information related to the fleet configuration (platforms and assets fitted within each one of them) at the end of the simulation run and platform and engine activities. It also includes details about each workscope completed during the simulation time (type of workscope, cause of failure, etc).

Statistics It contains statistics collected by the model about failures that occurred, inventory level, task operations (flying hours, waiting hours, etc).

Post-Processing It contains information used in post-processing to generate reports for the interested stakeholders.

12Definitions and Acronyms

Term Definition

Arising An event of significance to the simulation which leads to a shop visit. It can be planned, such as exceeding hard life limits, or unplanned, such as a component failure.

Assembly An asset that contains components. This term will usually be used in terms of strip and build processes.

Asset An asset is a generic recursive term. The highest level asset will usually be a platform, which contains one or several engines, which will be made up of modules, which in turn break down into lower level components.

Component A component is the lowest level asset in our model.

Equipment Equipment is the general term for things that are attached directly to and removable from a platform. In our scenario, equipment is synonymous with engine.

Failure In the context of reliability engineering, failure usually implies an event that results in the replacement of one or more components during servicing, rather than a complete failure of these components in situ (i.e. an inspection of a turbine blade results in its replacement before it experiences a failure).

Failure mode A defect in design, process, quality or part application, which is the underlying cause of the failure or which initiates a process which leads to failure.

Hard life This is the mandated life limit for the component. The component will not be allowed to be used beyond this point.

HOOS Held out of Service.

13Definitions and Acronyms (Continued)

Term Definition

Inspect/Inspection A process carried on after an aircraft has landed. The inspection may reveal some failures, depending on the visibility of those failures and the probability of detection at that visibility.

LLP Life Limited Part, i.e. a component that has a hard life.

LRU Line Replaceable Unit.

Modification Campaign

A modification campaign refers to alternative modification standards of components and modification progression policies.

Modification Standard This is a key attribute of a component that defines where it may be installed and the life characteristics of the component - i.e. components of differing modification standards may have different life characteristics.

Module A term used for an assembly that is at the level of indenture immediately below engine.

MRO Maintenance, Repair, Overhaul.

Platform The highest level asset that is being modelled, i.e. the aircraft.

Primary failure A component failure is termed Primary if it is the failure that has caused an engine to be rejected.

Recondition The ability to return a component to an "as new" state with zero used life.

Recovery A generic term for making an unserviceable component or platform serviceable again through strip, repair, recondition, replacement and rebuild.

14Definitions and Acronyms (Continued)

Term Definition

Repair The ability to restore a component to operational use. The intention of a repair is simply to make the component serviceable again.

Secondary failure A component failure is termed Secondary if it has failed as a direct result of the Primary failure of another component.

Serviceable A serviceable asset is one whose performance and integrity is such that it is able to perform all its required activities. A serviceable asset may comprise one or more sub-components that have failed but which do not significantly degrade the overall assembly's ability to perform as required.

Soft life Soft life is a commercial threshold that indicates that an overhaul is cost effective if its age exceeds its soft life.

SV Shop Visit.

Workscope A workscope contains the activities undertaken at maintenance for assets to become serviceable again.

Table 3: Definitions and Acronyms

15Data Set ReferencesThis is a description of the data set.

Fleet Data

PlatformList

Name Type Size Description

PlatformID Text 255 Identifier of platform (e.g. aircraft serial number).

MARK Text 255 The mark (build standard) for this platform (used for build sets; can be left blank).

INTRODUCTION_DATE Date/Time 8 Date on which Platforms are introduced as a scheduled change.

StartingTaskID Long Integer 4 The task the platform is assigned to at model start. Can be left blank if not assigned to a specific task.

IN_HOOS Yes/No 1 Flag to indicate whether the platform is in HooS at the start of the simulation.

StartingSiteID Double 8 The ID of the site where the platform is at the start of the simulation.

16Data Set References (Continued)

EquipmentList


ID Long Integer 4

INSTALLATION_LOCATION Text 255

SerialNumber Text 255

BUILD_STANDARD Text 255 Build standard for this engine (used for build sets; can be left blank).

INSTALLATION_DATE Date/Time 8

REFURB_COUNT Long Integer 4

AGE_AT_LAST_REFURB Double 8

AGE_UNIT Text 255 Operating hours.

OPERATING_HOURS Double 8

OPERATING_CYCLES Double 8

SITE_ID Long Integer 4 For Equipment in storage.

INTRODUCTION_DATE Date/Time 8 Date on which the engine is introduced into the simulation. A date is only present for Equipment which are introduced into the spares pool (not fitted to a platform).


EquipmentList


LEASE Yes/No 1 A flag to indicate if the equipment has been leased from the OEM.

IN_HOOS Yes/No 1 Flag to indicate whether the equipment is in HooS at the start of the simulation.

IN_SHOP Yes/No 1 Flag to indicate if the Equipment is InShop.

DISPOSAL_DATE Date/Time 8 Date on which the engine is retired.


AssemblyList


ID Long Integer 4

PARENT_EQUIPMENT Text 255

ASSEMBLY_ID Text 255 Assembly Type.

BUILD_STANDARD Text 255 Build standard for this assembly (used for build sets; can be left blank.

ASSEMBLY_SERIALNUMBER Text 255

INSTALLATION_DATE Date/Time 8



SITE_ID Long Integer 4 For equipment in storage.

NO_EXCHANGE Yes/No 1

IN_HOOS Yes/No 1 Flag to indicate whether the assembly is in HooS at the start of the simulation.


ComponentList


ID Long Integer 4

PARENT_PLATFORM Text 255

PARENT_EQUIPMENT Text 255

PARENT_ASSEMBLY Text 255

COMPONENT_TYPE Text 255

COMPONENT_SerialNumber Text 255

MOD_STANDARD Text 255

AGE_UNIT Text 255



MANUFACTURE_DATE Date/Time 8

INSTALLATION_DATE Date/Time 8 The date at which it was installed into the ASSEMBLY.

SITE_ID Long Integer 4 For Equipment in storage.

NO_EXCHANGE Yes/No 1

REMAINING_FACTORED_LIFE_UNIT

Text 255


ComponentList


REMAINING_FACTORED_LIFE Double 8

IN_HOOS Yes/No 1 Flag to indicate whether the component is in HooS at the start of the simulation.

HOOS_FAILED Yes/No 1 Flag to indicate whether the component in HooS is in failed status.

REWORK_LEVEL Text 2 The rework level if component is InShop.


Operations

Task_Header


TaskID Long Integer 4

TaskDescription Text 48

SiteID Long Integer 4

StartDate Date/Time 8

EndDate Date/Time 8

PlatformsReqd Long Integer 4

FlightsRequired Long Integer 4

FlightDuration Double 8

FleetType Text 255 Low or "High" margin.

SoftLife Long Integer 4 The SoftLife that is associated with the task.


Maintenance

SiteDetails_Capacity


ID Long Integer 4

Site_ID Long Integer 4

Change_Date Date/Time 8 Date on which new parameters become effective.

Equipment_Strip Long Integer 4 Number of lines for strip of Assemblies from Equipment.

Assembly_Strip Long Integer 4 Number of lines for strip of Components from Assemblies. (Any 'line' can strip any assembly type).

Build Long Integer 4 Number of lines for rebuild of Equipment from Components and Assemblies.


Forecast

Output_AssemblyConfiguration


ID Long Integer 4

Experiment_ID Long Integer 4

RunNumber_ID Long Integer 4

Component_SerialNumber Text 255

Parent_Component_SerialNumber

Text 255


Create_Date Date/Time 8

OperatingHOURS Double 8

OperatingCYCLES Double 8

Standard Text 255 Build Standard of the Assembly (where applicable).


Output_AssetConfiguration


ID Long Integer 4





Text 255





Standard Text 255 Mod Standard (for Component) or Build Standard (for Equipment or Assembly), where applicable.

Refurb_Count Long Integer 4 The refurbishment count of the equipment.


Output_ComponentConfiguration


ID Long Integer 4





Text 255





MOD_STD Text 255 The MOD std of the component (where applicable).

Parent_Equipment Text 255 The parent equipment that the component is installed on.

RemainingFactored LifeHours

Double 8

RemainingFactored LifeCycles

Double 8

RemainingLifeHours Double 8

RemainingLifeCycles Double 8


Output_EquipmentConfiguration


ID Long Integer 4





Text 255





Standard Text 255 Build Standard of the Equipment (where applicable).

Refurb_Count Long Integer 4 The refurbishment count of the equipment.


Output_EquipmentActivities


ExperimentID Long Integer 4

RunNumber Long Integer 4

ActivityType Text 255 Activity type: Introduction, Disposal, etc.

ActivityDate Date/Time 8 Simulation timestamp at which the activity took place.

EquipmentSerialNumber Text 255 ESN that the activity applies to.

ActivitySequence Long Integer 4 Sequence order number of the activity for the ExperimentID, RunNumber and EquipmentSerial Number.

SiteID Long Integer 4 FK to SiteHeader database table. Only populated if the activity is site transition dispatch/delivery.

PlatformID Text 255 FK to PlatformList. Only populated if the activity is Removal or Installation.


Output_PlatformActivities




ActivityType Text 255 Activity type: Introduction, Disposal, etc.

ActivityDate Date/Time 8 Simulation timestamp at which the activity took place.

PlatformID Text 255 Platform tail number that the activity applies to.

ActivitySequence Long Integer 4 Sequence order number of the activity for the ExperimentID, RunNumber and PlatformID.

TaskID Long Integer 4 FK to Task_Header database table. Only populated if the activity is task assignment/unassignment.


Output_Initial_Failure


ID Long Integer 4

ExperimentId Long Integer 4 The experiment id from Experiment_Header.

RunNumber Long Integer 4 The run number from Experiment_Details.

AnyLogicWorkscopeId Long Integer 4 The workscope id generated in AnyLogic.

FailureReason Text 255 The reason for failure (This must be in Failure_Priority table).

FailedComponentId Text 255 The componentId of the Failed Component.

CauseCategory Text 255 The cause category for failure. Only populated for MODULE AssetType.

Standard Text 255 The mod standard of the component at the time of the failure, or the build standard of the equipment at the time of rejection.


Output_Initial_Failure (Continued)


FailedComponent SerialNumber

Text 255 The serial Number of the failed component.

AssetId Text 255 The Asset id for the workscope.

AssetType Text 255 The Asset type for the workscope (COMPONENT, MODULE, EQUIPMENT).

DiscoverySiteId Long Integer 4 The Siteid at which the failure was detected.

AssetSerialNumber Text 255 The Serial Number of the Asset for the workscope.

ReasonPriority Long Integer 4 The priority value for the failure reason (see Failure_Priority).

PlannedDate Date/Time 8 The planned workscope date.

Action Text 255 The action to recover the component (Repair, Recondition, Exchange).

RecoverySiteId Long Integer 4 The site at which the Component is recovered (repair or recondition siteId).

ParentWorkscopeId Long Integer 4 The originalWorkscope Id (links Exchange workscopes back to the original engine removal).

FailureModeId Long Integer 4 if no FailureMode, -1.


Output_Workscope




Type Text 255

RefurbishmentOrder Number

Long Integer 4

AnyLogicWorkscopeID Long Integer 4

Version Long Integer 4

SimulationTimePlanned Double 8

DatePlanned Date/Time 8

SimulationTimeCompleted Double 8 Simulation time of workscope completion.

DateCompleted Date/Time 8

WaitTime Double 8 Total queuing time during the workscope process.

EquipmentSerialNumber Text 255

EquipmentOperatingHours Double 8

State Text 255


Output_Workscope (Continued)


ModifiedFromPlanned Yes/No 1

RemovalType Text 255 Removal type: Arising, PELM or HSV.

StandardBefore Text 255 The build standard or mod standard of the asset at the time of workscope planning.

StandardAfter Text 255 The build standard or mod standard of the asset at the time of workscope completion.


Output_Workscope_Item


ID Long Integer 4




AnyLogicWorkscopeItemID Long Integer 4

ComponentSerialNumber Text 255

ReasonWhy Text 255

FailureModeID Long Integer 4

Action Text 255

SimulationTime Double 8

CalendarDate Date/Time 8

OperatingHoursBefore Double 8

OperatingCyclesBefore Double 8

RemainingFactored OperatingHoursBefore

Double 8

RemainingOperating CyclesBefore

Double 8

ModStandardBefore Text 255


Output_Workscope_Item (Continued)


OperatingHoursAfter Double 8

OperatingCyclesAfter Double 8

RemainingFactored OperatingHoursAfter

Double 8

RemainingFactored OperatingCyclesAfter

Double 8

RemainingOperating HoursAfter

Double 8

RemainingOperating CyclesAfter

Double 8

ModStandardAfter Text 255

State Text 255

WorkscopeVersion Long Integer 4



Output_Workscope_Module


ID Long Integer 4




AnyLogicWorkscopeItemID Long Integer 4

AssemblySerialNumber Text 255

Type Text 255

WorkscopeVersion Long Integer 4

DatePlanned Date/Time 8


PlannedAction Text 255

StandardBefore Text 255 The assembly (module) build standard at the start of this workscope item.

StandardAfter Text 255 The assembly (module) build standard at the end of this workscope item.


Statistics

StatsOutput_Failures


ID Long Integer 4



AnyLogicFailureEvent_id Long Integer 4

SimulationTime Double 8 Simulation time that the event happened.

FAILURE_MODE_id Long Integer 4

Parent_SerialNumber Text 255

FHOfThisFailure Long Integer 4

FCOfThisFailure Long Integer 4

FHOfLastFailure Long Integer 4

FCOfLastFailure Long Integer 4 Simulation time that the previous event happened.

ReasonForFailure Text 255 Was it hours or cycles, regular inspection that triggered the failures.


StatsOutput_InventoryLevel


ID Long Integer 4






AssetType Text 255 Asset type or special value "Spare Engine Demand" for spare engine demand levels.

Standard Text 255 Standard (mark, build standard, mod standard) for the asset type.

InventoryLevel Long Integer 4 Peak (max) inventory level for the month.

MeanInventoryLevel Double 8 Average inventory level for the month.

MaxInventoryLevel Long Integer 4 Peak (max) inventory level for the month.


StatsOutput_Operations


ID Long Integer 4





EquipmentSerialNumber Text 255

Hours Double 8 Total number of hours ‘flown’ by the engine during the simulation run.

HoursThisMonth Double 8 Total number of hours ‘flown’ by the engine during current month.

WaitingHoursThisMonth Double 8 Total number of waiting hours by the platform during current month.

39Questions and ContactIf you have any questions regarding the competition scenario or the data set, you can contact the competition team using the below contact details:

Telephone: 0117 244 8775

[email protected]

© Rolls-Royce plc 2017

The information in this document is the property of Rolls-Royce plc and may not be copied, or communicated to a third party, or used, for any purpose other than that for which it is supplied without the express written consent of Rolls-Royce plc.

Whilst this information is given in good faith based upon the latest information available to Rolls-Royce plc, no warranty or representation is given concerning such information, which must not be taken as establishing any contractual or other commitment binding upon Rolls-Royce plc or any of its subsidiary or associated companies.

Rolls-Royce Holdings plc Registered Office:65 Buckingham Gate LondonSW1E 6AT

T +44 (0)20 7222 9020 rolls-royce.com

Company number 7524813

mailto:RRdatachallenge%40cfms.org.uk?subject=Rolls%20Royce%20Data%20Challenge

rolls-royce data storytelling challenge scenario … · for the scope of the data storytelling...

Documents