Business Need

DEX 7 – Operational FeedbackBusiness Need

IntroductionThis exchange enables the transmission of

information on the condition and usage of a supported product. Feedback includes:

• support task records, including product data collected by the task;

• product state and usage records; • resource element state and usage records; • product configuration information; • any issues arising from work.

DEX 7 – Operational FeedbackBusiness Process

This DEX enables the transmission of information on the condition and usage of a supported product gathered during its operation. This DEX will provide inputs and triggers for maintenance tasks (Work_package_definition) and feedback information generated through the execution of maintenance tasks is covered by the Work_ package_ report DEX.

Examples of information about the usage of a supported product: • flying hours on an aircraft; • mileage travelled by an automobile; • number of starts for an electrical generator; • volume of fluid pumped through a pipeline or process plant; • operational cycles for a gas turbine engine; • occurences of operation outside preset limits i.e. overspeed, or overstress; • feedback from system monitoring; • fatigue index; • location of the part or product.

DEX 7 – Operational FeedbackScope (1)

The following are WITHIN the scope of this DEX:

• Recording the transmission of information; • Reporting the usage of a product as realized; (Note the usage is the

activities that a product has been engaged in). • Reporting the current configuration of the product as realized; • Reporting the condition of a product as realized, before, during or after

performing a support activity or operational usage, recorded as properties, states or observations; (Note this includes reporting the fault state, as defined or otherwise in the FME(C)A, observed on a product as realized).

• Reporting the location of the product as realized; • The identification of the FME(C)A. (Note the definition of the FME(C)A is

covered by the Fault_states DEX). • The environment is which a product was operating.

DEX 7 – Operational FeedbackScope (2)

The following are OUTSIDE the scope of this DEX:

• Reporting the work performed on a product as realized;

• Reporting the resources used to perform work on a product as realized. (Note the reporting of work performed and resources used is covered by the Work_package_report DEX).

• The definition of the FME(C)A. (Note the definition of the FME(C)A is covered by

the fault states DEX).

DEX 7 – Operational FeedbackOverview

Use of a Reference Data LibraryTransmission of feedback information

Capability (C010)Reference data

Capability (C014)Messaging

Identification of the subject of the feedback:the Product as realized

Capability (C060)Referencing Product

as realized

Operational feedback

Capability (C066)Representing aWork request

Capability (C068)Referencing Product

as realizedconfiguration

State of the Product as realized

Capability (C049)Representing

product location

Capability (C041)Representing anobserved state

Capability (C048)Representing an

evaluated condition


actual environment

Capability (C030)Representing and

assigning properties

Capability (C064)Representing Work

done

Capability (C011)Referencing

Documentsed results(FEM(C)A)

Activities that the Product asrealized was engaged in


activity

Capability (C046)Representing a

variance

Capability (C037)Assigning

Documents

Capability (C005)RepresentingDocuments

Capability (C065)Representing Work

order

Information Management

Capability (C016)Representing

Person Organization

Capability (C036)Assigning Date

Time

Capability (C058)Representingjustification

Capability (C001)Assigning Identifiers

Capability (C019)Assigning Approvals

DEX 7 – Operational FeedbackCAPABILITIES -TABLE

Capability % Complete

Remarks

C032 – Representing_ activity 90 Replaced product change C041 - Representing_state_observed 90 C044 - Representing_environment_actual 90 Renamed C048 - Representing_condition_evaluated 90 C049 - Representing_product_location 90 C064 - Representing_work_done 90 New C065 – Representing_work_order 90 New C066 – Representing_work_request 90 New C068 – Referencing _product_as realised_configuration

90 New

C047 – Product_ change Deleted (replaced by Rep work order and Rep work done and Rep work request)

C033 – Representing_product_usage Deleted replaced by C032 C057 - Referencing_prloduct_configuration No longer required by DEX 7

Note: The above capabilities are classified as 90% complete as they have not yet been tested

DEX 7 – Operational FeedbackDEPENDENT CAPABILITIES -TABLE

Dependent Capabilities Lead Remarks C001 - Identification Tim Turner Critical to DEX 7 – RISK. Reported Complete.

C005 – Representing_documents Tim Turner Completion date unknown but not considered a risk

C010 – Reference_data Leif Gyllstrom Completion estimate 30 Nov 03

C011 – Representing_a_documented_result Leif Gyllstrom Completion estimate 30 Dec 03

C014 - Messaging Sean Barker Critical to DEX 7 – completion date unknown but not considered a risk

C016 - Representing a person in an organisation

Nigel Newling Completion date unknown. RISK

C019 – Assigning_approvals Completion date unknown. RISK

C030 - Representing and asigning properties Tom Hendrix Critical to DEX 7– completion date unknown. RISK

C036 – Assigning_ date_ time Nigel Newling Critical to DEX 7 –completion date unknown. RISK

C037 – Assigning_documents ? Completion date unknown. RISK

C046 - Representing a variance Nigel Newling Completion date unknown. RISK

C058 – Representing_justification Unknown Completion date unknown. RISK

C060 – Referencing_product_as_realised Eric Reiger Critical to DEX 7 –completion date unknown

C007 – Representing_a_state_type Leif Gyllstrom Completion estimate 30 Nov 03

C026 - Representing a condition Leif Gyllstrom Completion estimate 30 Nov 03

C027 - Representing a location Leif Gyllstrom Completion date unknown

DEX 7 – Operational FeedbackReference Data Development

Activity Lead % Complete

Target Date Remarks

Development Normative Reference Data Development

Rob Bodington

12 Dec 03 Normative Ref Data to be sufficiently developed to allow initial DEX functionality check .

Business Reference Data Development

Les Debenham

5% Apr 04 Full set of Ref Data to be developed to make DEX 7 usable in commercial environment. Note. 1. Initially Les and Mike to develop

RD as a mind map. 2. Once the raw RD has been

developed the XML can be created using the 'spreadsheet' or if Rob's time permits a conversion tool.

3. The team should consider the

utilisation of TRILS as a potential source of Ref Data.

DEX 7 – Operational FeedbackSummary of Remaining Work

Activity Target Date

Remarks

Quality checking Testing Validation Identify and Map real data from applications

Apr 04 Guestimate 15 days in total (10 days Modeller + 5 days SME) Can be funded by MOD

Reference Data - Development Apr 04 Full set of Business Ref Data to be developed to make this DEX usable in a commercial environment. Guestimate 40 days in total (20 days SME + 20 days Modeller) Can be funded by MOD

Missing Capabilities Properties Product as realized Product Configuration Scheme Justification Date Time

asap Guestimate 30 days Modeller and 10 days SME CANNOT BE FUNDED THE MOD

DEX 7 – Operational FeedbackStatus / Remaining Work

• Capabilities / DEXs– The ones that DEX 7 are responsible for are complete but

requires• Checking – have all entities been used?• Testing – not yet• This requires test data + availability of ALL capabilities

• Testing– Requires ALL capabilities used by the DEX to be complete

before the consistency of the EXPRESS can be tested.– Requires test data to cover the scope of the DEX.

• Reference Data– Model reference data complete– Business reference data in work – complete April 2004

DEX 7 – Operational FeedbackIssues / Remaining Work

• Quality– We need to review ALL the DEX/Capabilities wrt to quality, consistency, accuracy– Checklists will help– Effort for DEX7

• Modeller effort: 3 days• Subject Expert: 3 days

• Validation– Check that the DEX EXPRESS is complete– Requires all capabilities used by DEX to be in place– Requires development of long form – XML or EXPRESS– Effort for DEX7


• Testing• Neutral test files

– We should continue development of Bike test data to cover DEX7– The data should provide support to ALL the DEXs– We should use the data as an input to translator test rallies– Effort for DEX7


• Real test data– We should identify some real data from applications– Map to DEX7– Effort for DEX7

• Modeller effort: ? days• Subject Expert: ? days


• Reference Data– “It is modelling!”

• Needs Subject expert + modeller input– Needs scoping– Perhaps use TRILS– How are we to proceed with ISO 15926?

• What database is available?• Is it web accessible – both as OWL and Web Services?• What tools are available for building the ref data?• How does it interface to the PLCS model?

– Effort for DEX7 – Can be funded by MOD• Infrastructure development: ????• Modeller effort: 20 days• Subject Expert: 20 days

• Infrastructure– How do we publish in OASIS?

• They may well have different requirements.– Improvements– HTML publications

• Paul Nolan committed – progress?– Issue logs

• Paul Nolan committed – progress?


• Missing Capabilities – cannot be funded by MOD– Properties


– Product as realized• Modeller effort: 10 days• Subject Expert: 3 days

– Product configuration• Modeller effort: 2 days• Subject Expert: 1 days

– Scheme• Modeller effort: 4 days• Subject Expert: 1 days

– Justification• Modeller effort: 2 days• Subject Expert: 0 days

– Date time, Person Organization• Modeller effort: 2 days• Subject Expert: 0 days

• TOTAL EFFORT• Modeller effort: 30 days• Subject Expert: 10 days