Other sections of the WellLine documentation provide detailed information on each field of the data model, including definitions, formatting, and examples of fully-formed events
id
fieldcode
and subcode
valuescode
/subcode
values to create eventTypeGroup
and eventType
values + output themmeasures
values + output themA scenario for illustration:
1.A database contains four tables:Wells
,Observations
,Problems
, andLessons_Learned
Wells
has referential information that needs to be joined to the other tablesObservations
has daily reports about work performed at a wellsiteProblems
has a correlation toObservations
when there was non-productive timeLessons_Learned
has a correlation toProblems
when an investigation was performed 2.A determination is made: observations, problems, and lessons learned would ideally be displayed as individual events in WellLine 3.The necessary joins are made betweenWells
and the other tables, to incorporate needed information (e.g. well name) 4.To create separate outputs for the remaining tables, each table is run through its own distinct series of tools 5.In the output step, each is output with a unique name, e.g. "Observation_001.jsonl", "Problem_001.jsonl", "LessonLearned_001.jsonl"
The idea of "essential data" in the Filter Tool will be specific per-source and generally includes one or more portions of the source that should pass a check (i.e. "not null"). Also useful for making sure each input contains information required for WellLine inclusion, e.g. a date.
id
field is used by several future tools and containers, and is a unique identifier for each event.id
values are generated, they will either cause errors during upload or they will overwrite previously-uploaded data.typeId
field (see Populating the Data Model).eventTypeGroup
and eventType
values, used in their synonymous "metadata" files.MAIN ACTIVITY
:SUB_ACTIVITY
: measure
"metadata" values, which are needed by section Measures.referenceEntityIds
and subjectEntityIds
fields (see Populating the Data Model).typeId
and name
values, which are needed by section Transformation - Entities.typeId
of the entity, while the value in the field will be the name
of the entity. For more information, see Transformation - Entities.typeId
values. These typedId
values appear as dropdown options in ConnectionViewer.[WELL_ID]
values then appear as entities in this group.[RIG]
values then appear as entities in this group.[mudType]
values then appear as entities in this group.startedOn
field stores the start datetime for the event, and is a required field.
Here, the original start datetime is converted to required ISO formatting:content
field stores free text and is a required field. This field is mined by WellLine's entity extraction processing, and it displays in the EventStream.subjectEntityIds
field is used to store the primary subject(s) of the event. This is generally the well ID, well name, or other concrete well-related entities.referenceEntityIds
field is used to store entities where serve as "references" to the event. These are entities such as rig names, mud additives, personnel names, and more.subjectEntityIds
should be given their own IIF
statement here:measures
field is used to store the measures of the event. This is generally depths, production metrics, or other physical quantities.id
field should be unique for every row, so a simple unique filter on this field should ensure uniqueness.id
field creation logic (from Events - ID step) to ensure it is producing unique values as intended.typeId
is used to group entities within ConnectionViewer.
Value name
becomes a selection within its group.eventType
and eventTypeGroup
"metadata" files are gathered in section Transformation - Metadata - Event Types, then processed in the Alteryx container titled, "Event hierarchy processing".code
values are used to create eventTypeGroup
values, which generally are the highest level of a coding system hierarchy. The following set of tools creates these values:id
code
valuename
code
valuedescription
groupId
"all"
eventTypeGroup
values should eventually point to a groupId
of "all", as in the above examples.subcode
values are used to create eventType
values, which generally are the lowest level of a coding system hierarchy. The following set of tools creates these values:id
code
and lowercase subcode
valuestypeId
values (created in the Event Type Creation step, above) must match one of these id valuesname
subcode
valuedescription
groupId
code
value associated with this subcode
eventType
values must point to a defined eventTypeGroup
value.measures
"metadata" files are gathered in section Transformation - Metadata - Measures, then processed in the Alteryx container titled, "measureTypes file creation".referenceEntityIds
vs subjectEntityIds
, or any other fields? Ask the WellLine team for advice! You can contact product support by using the chat support in the bottom-right corner of your screen.