Ticket #51 (new task)

Opened 9 years ago

Last modified 9 years ago

Process Profile from O&M and ISO 19115

Reported by: sventour Owned by: sventour
Priority: critical Milestone: V3.5 UML Final
Component: UML Information Model Version: V3.5
Keywords: Cc: lawrence, sjdcox, domlowe

Description

At the current version of MOLES 3.4 we specialise the OM_Process to MO_Process which is an aggregation of acquisition and/or computation steps.
The MO_Acquisition class is an aggregation of MO_Instrument, MO_Platform and MO_Operation (specialiasations from ISO 19115-2).

As stated in ISO 19156
'The purpose of an observation process is to generate an observation result. An instance of OM_Process is often an instrument or sensor, but may be a human observer, a simulator, or a process or algorithm applied to more primitive results used as inputs. '

Therefore ,following O&M, the instrument should be associated directly with MO_Process and not the MO_acquisition. The MO_Platform or MO_operation is metadata about the acquisition but not the process. Process is the instrument.
Also an MO_Acquisition which contains and operation e.g.flight ( in the current version the MO_Operation is mandatory) cannot be reused in another observation which was happened in another period of time. However, an instrument can – an instrument can be used in 0 to many observations as is the multiplicity of OM_Process to OM_Observation association.

Proposal:
a)Profile
The empty class OM_Process is specialised to ProfileProcess? class which is an agrregation of instruments (MI_Instrument) and/or computation steps (software runs) (LE_ProcessStep).

MI_Insrtument, MI_Platform and MI_Operation aggregate to MI_AcquisitionInformation.
In a similar mamnner LE_ProcessStep and LE_Source aggregate to LI_Lineage.
see attached: Process Overview Profile.jpeg
b)Profile specialisation
The profile can be specialised according to the requirements of the specific application e.g.MOLES, METAFOR, INSPIRE-Environmental MOnitoring Facilities etc
see attached: Process Overview Profile specialisation.jpeg

Attachments

Process Overview profile.jpg Download (174.9 KB) - added by sventour 9 years ago.
Process Overview Profile Specialisation.jpg Download (218.3 KB) - added by sventour 9 years ago.

Change History

Changed 9 years ago by sventour

Changed 9 years ago by sventour

comment:1 Changed 9 years ago by sventour

  • Cc lawrence, sjdcox, domlowe added

comment:2 Changed 9 years ago by lawrence

We agree there is an issue here: primarily reusable OM_Processes should be accompanied by event specific parameters in the observation.

But there is a difference between LE_Processing (which has event specific parameter, and thus shouldn't be a specialisation of OM_Process if we read it one way), and MI_Instrument ,which then has no event specificity, but is a noun and process describes an action ... which might be reusable ...

Consider dealing this last, or postponing to V3.5

comment:3 Changed 9 years ago by lawrence

  • Priority changed from blocker to critical
  • Version changed from V3.4 to V3.5
  • Milestone changed from V3.4 UML Final to V3.X Next Release
Note: See TracTickets for help on using tickets.
 Trac Powered
Site hosted at the
British Atmospheric Data Centre
for the