Data Rules. rules.ppdm.org. Dave Fisher & Madelyn Bell BUSINESS RULES WORKSHOP. March Business rules workshop Nov 2013

Transcription

1 BUSINESS RULES WORKSHOP Data Rules Dave Fisher & Madelyn Bell rules.ppdm.org 1 March 2014

2 AGENDA Workshop objectives Definitions what is a data rule? It only grows with your help It takes longer then anyone expects Guidance for contributing data rules Next steps 2

3 THE IMPORTANCE OF THE KNOWLEDGE BASE Teach Certify Best Practices A collection of industry accepted business rules Portable Resources Business Rules Audit Accredit Data Rules Objective, measurable

4 DEFINITION DATA RULE Data rule: a statement to validate compliance to expected conditions or to identify exceptions Applies to data and information Defines specific tests, validations or constraints Always resolves to true or false Atomic: each rule checks only one thing A data rule is a type of business rule EXAMPLES 1. Top depth is less than base depth 2. An offshore well must have a water depth 3. Latitude value has a corresponding longitude 4

5 DEFINITION BUSINESS RULE Business rule: a statement that defines or constrains some aspect of the business. Describes an operation, definition and/or constraint that applies to an organization Workflows, policies, procedures, systems, etc. EXAMPLES 1. A well must not be spudded without a drilling permit. 2. All regulatory compliance filings (for wells) must be signed by the Drilling & Completions Manager. 3. A wellbore is a path of drilled footage from the Well Origin to a terminating point. 4. A data item that fails a data rule must be investigated 5

6 IT ONLY GROWS WITH YOUR HELP You: PPDM has a great place to share and download data rules that would be helpful for us. Boss: That sounds good. Go for it. You: One more thing. Sharing means I want to upload some of our data rules. Boss: No way! Our data rules are proprietary. NOW WHAT WILL YOU SAY? 6

7 DRAFT THE VALUE PROP FOR SHARING How does my organization benefit by sharing our rules with the industry via PPDM? More rules = tap into industry s knowledge Rules don t create business value. It s how we apply them to our data and processes. Leadership for more and better standards and practices Foundation of best practices for the industry 7

8 IT TAKES LONGER THEN EXPECTED November presentation focused on getting agreement on what data rules are and how to standardize the phrasing. December Landmark donated 460 well and 55 seismic data rules. January Those that asked got a copy of the current rule redesign. February - Rules webpage redesign was shared for testing. Now it s March! 8

9 GUIDANCE FOR CONTRIBUTING RULES PPDM Rules App now has about 150 rules. PPDM staff or volunteers will edit them to the standard style PPDM members will submit their rules for sharing Published rules will not be identified by source. But the PPDM editor may contact you for clarification. All subject domains are welcome seismic, production, etc. Spreadsheet or document format is OK Metadata (exceptions, metrics, etc.) - nice but not mandatory PPDM staff or volunteers will edit them to the standard style PPDM members use the Rules App to comment and download 9

10 CLASSIFICATION(S) Currently: Business Event Acidizing, Install Slotted Liner, Tying-in Lifecycle Event Drilling, Completing, Producing Business Role Chemical Engineer, Geological Engineer Subject Well Areas, Well Status, Well Classification, Wellbore We are doing: Domain Seismic, Well, Facility Group Well header, Well log, Well equipment Element Date, Location Test Type explicit (compare), null, metadata Rule type Data, Business, Rule Set 10

11 BACKUP The following slides are to better define the survey results that lead to how the rules are being rewritten 11

12 PPDM RULES SURVEY End user DBA 93 respondents Average 1.9 roles Software developer Data manager Data services Supervisor 53 via Survey Monkey 40 at fall conference 12

13 RESPONDENTS WHERE THEY WORK Asia - Oceania Middle East - Africa North America Europe Other America 93 respondents 13

14 responses RULE METADATA BUSINESS CLASSIFICATION essential important useful not impt business event life cycle phase business role 14

15 RULE METADATA TYPE OF DATA QUALITY consistent with other data duplicate detection complete relatedness to other data current conforms to real world 85 respondents no opinion not impt useful important essential 15

16 RULE STYLE FOR NUMERIC COMPARISONS DEPTHS Top < bottom Bottom > top No opinion responses Example: core top depth must be less than core bottom depth or core bottom depth must be greater than core top depth DATES Early vs late Late vs early No opinion responses Example: permit date must be earlier than spud date or spud date must be later than permit date 16

17 TIE RULES TO THE PPDM MODEL? essential important useful not impt 91 responses no opinion 17

18 DATA RULES FOR UNITS OF MEASURE? yes no no opinion 92 responses 18

19 RULES TO DETECT NULL VALUES Should we have data rules to check for missing values? Examples: If a well has a rig release date, spud date must exist. If a shot point has a latitude, longitude must not be null. If a well has a core analysis record, the core recovery length must not be null. The workshop agreed we need data rules for nulls. 19

20 REWRITE TO STANDARD STYLE 20 For some existing rules in the PPDM Rules App, rewrite them in the agreed style. Examples: 338: A core must have top and bottom depths Rule: If core top exists, core bottom depth must not be null. Rule: If core bottom exists, core top depth must not be null. 417: Production volumes must have dates that are after the rig release date Rig release date must be less than production volume date 348: The cored interval must be consistent with the length of the core barrel A core interval must not exceed the core barrel length 398: The top depth for a porous interval must be less than the bottom depth. For a porous interval, top depth must be less than base depth

21 RULES ADAPTED TO A PROJECT 605: The total depth of a well is less than 40,000 ft 437: The well spud date is greater than : A direction survey for a horizontal wellbore has at least one inclination greater than 75 degrees 317: Rotary table elevation for an offshore well is between 5 and 20 m 381: The top depth for a liner is greater than 2000 m These are examples of rules that could be modified to suit a specific project or area The number refers to the rule in the PPDM Rules App. Workshop consensus: this kind of rule is not the focus of our short-term efforts 21

22 SOME DATA RULES ARE HARD TO CODE 401: If a formation pick was made by log interpretation, a well log must exist for the relevant wellbore interval 366: A directional survey LAS file depth datum matches the depth datum in the directional survey data table 415: A well cannot be producing and injecting on the same date through the same production string 304: Casing flange elevation equals ground or seabed elevation 355: If a well directional survey has X,Y data, the survey type must be capable of measuring azimuth * 252: A well has a geographic location * * This business rule could be restated as a data rule. Workshop consensus: not our focus at this time. 22

23 PPDM RULES APP: rules.ppdm.org 23

24 FIND THE RULES YOU WANT OPTION 1 available now Search in the PPDM Rules App Examine the data rule statement Check the description (exception, tolerance, etc) Download single or batch; CSV, XML, etc. Code each rule (e.g. SQL), based on your dataset OPTION 2 could be developed in the future Search in the PPDM Rules App Examine the rule statement and description Download the rule coded for PPDM 3.8 Requires sharing, contractors, 3 rd parties 24

25 PPDM 3.8 RULE MODULE PPDM_RULE Captures rules governing the use of a system. Rules may be policies, practices, procedures or business [data] rules. Rules may be enforced through data base rules, application logic, user interfaces or best business practices. They may also define the way tasks are to be performed. PPDM_RULE_DETAIL Describe details about a rule. These rules may be textual or they may be captured as numbers, such as an allowable range of numbers that a column may contain. PPDM_RULE_COMPONENT Connect PPDM rules to the business objects they influence or are influenced by. Can be used to describe the geographic area, the specific wells that a rule controls, etc. PPDM_RULE_ENFORCEMENT Rules may be enforced by the data base DDL, software application logic, manual procedure etc. PPDM_RULE_XREF Track cases where the use of a rule may depend on the outcome of another rule implementation. For example, the second rule is only enforced if conditions for the first have passed successfully. Also use for replacing or refining rules, etc. 25

26 STYLE GUIDE FOR DATA RULES 1. The item to be tested is the subject of the sentence. 2. The item passes the test if the result is TRUE. 3. Write the rule as a logical statement independent of any data model. 4. For numeric or date comparison, write the subtraction to produce a positive outcome if true. 5. Do not include tolerance and exceptions in the rule statement. These belong in the description section. 6. Include details on diagnostics, resolution, impact and metrics. 26

27 TYPES OF DATA RULES Relatedness to other data: Latitude has Coord Ref System Duplicate detection: Well has only one surface location Consistent with other data: If oil production exists, the mineral lease must include oil Conforms to the real world: Completion date is less than production volume date Current: If spud date exists and status is not drilling, rig release date must also exist Complete: Core top depth also has base depth 27

28 NEXT STEPS By PPDM Existing rules rewrite to standard format New shared rules review and add to Rules App By industry Use the Rules App to select and use some rules Send PPDM some of your rules for public sharing Comment on existing rules via the Rules App Promote the value of data rules as an industry win-win Identify more value-added rules products YOU RULE! THANK YOU! 28