10

20
n
tio
ia
y c
PROFESSIONAL PETROLEUM
DATA MANAGEMENT ASSOCIATION

o
op ss
C A
Business (Data) Rules &
ot M
Data Quality
N D
Trudy Curtis
o P
D tP

CEO, PPDM Association

h
se ig
r
ea y
Pl op
C
 10
20
WHAT IS A BUSINESS RULE?

n
tio
ia
From the Business Rules Group:

y c o
Business Rules from the Business Perspective

op ss
C A
• ...a business rule is guidance that there is an obligation concerning conduct, action, practice, or
procedure within a particular activity or sphere.

ot M
N D
Two important characteristics of a business rule are:
o P
• There ought to be an explicit motivation for it.
D tP

• It should have an enforcement regime stating what the consequences would be if the rule were
broken.
h
se ig

Business Rules from the Information System Perspective

r
ea y
Pl op

• ...a business rule is a statement that defines or constrains some aspect of the business. It is
intended to assert business structure, or to control or influence the behavior of the business.
C

http://www.businessrulesgroup.org/defnbrg.shtml
 10
20
BUSINESS RULES & DATA RULES – CONNECTED?

n
tio
If business rules are about processes …

ia
And processes involve people and technology …

y c
And those interactions result in KID …

o
op ss
C A
Then business rules are about data!

ot M But they are not ALL about data

N D
o P
D tP

Data rules are business rules

but
h

not all business rules are about data

se ig
r

Data
ea y

The Business Rules Group provides an excellent framework for

Pl op

us to work in!
C
 10
20
INTEGRATED ARCHITECTURE

n
tio
ia
MDM
Ontologies

y c
Meta Data

o
Taxonomies

op ss
Physical

C A
Spatial/GIS

ot M SOR
PPDM SOR
N D
MDM
o P
D tPh

SOR
se ig
r
ea y

Business
Pl op

Rules
C

Policies, Practices & Procedures

 10
20
DISCUSSION TOPIC

n
tio
Professional Petroleum Data Management Association

ia
Business Rules Workshop: 1
Rule Source and PPP or Bus Rule is used Owner Where / how Documented? Available to

y c
description Rule? for what Implemented? Others?

o
purpose? In what form?

op ss
C A
ot M
N D
o P
D tP

Policy
h
se ig
r

Practice
ea y
Pl op
C

Procedure
 10
20
WHAT KINDS OF BUSINESS RULES EXIST?

n
tio
According to the Business Rules Group, three kinds of rules exist:

ia
y c
Definitions and Semantics (BRG = Structural Assertions):

o
• What is an XXX (where XXX is a key business object or term)?

op ss
- Many of these topics are the focus of existing or planned PPDM workgroups (i.e. “What is a Well”).

• What are the minimum data requirements for definition of a data object

C A
- (i.e. what is the minimum set of information required for a well)?

ot M
Transformation and Derivation Rules (BRG = Derivation):
N D
• How should the data be converted from a 14 digit API to a 12 digit API?
• How should well information from financial, drilling, land, G&G be reconciled?
o P
• How does the origin or source of the data affect its trustworthiness?
D tP

• How should I map data from one system into another?

• What about granularity challenges in my reference data?
h
se ig

Quality Rules (BRG = Action Assertions) … more on next slide

r

• Is this data correct?

ea y

• Can I trust this data?

Pl op

• Is this data complete?

http://www.businessrulesgroup.org/first_paper/BRG-whatisBR_3ed.pdf
C
 10
20
DATA QUALITY RULES

n
tio
• Simple

ia
- no completion date on an abandoned location

y c
- Lat/long should be accompanied by a CRS

o
• Interpretive

op ss
- [Completion Date > Spud Date > License Date]

C A
• Regional

ot M
- [Completion Date – Spud Date] < 180 days in the US
- Total depth < 9,000’ for xxx formation in Wattenberg field
N D
• Spatial
o P

- Tops picks < 10% variation within 0.5 mile radius

D tP

• Validation
h

- Has the data been verified procedurally?

se ig

• Trustworthiness
r

- Does the data conform to a standard set of quality rules?

ea y
Pl op

• Consistency
- Is the data internally consistent?
C
 C
Pl op
ea y
r
se ig
D tPh
o P
N D
ot M
C A
op ss
y c o
ia
tio
n
20
10
E&P LIFE CYCLE (DATA IS BUSINESS DRIVEN)
 10
20
WHERE DATA BASED BUSINESS RULES HIDE

n
tio
• In your user’s software applications

ia
• In ETL tools

y c o
• In your data cleansing tools

op ss
• Explicit or inferred in data models

C A
• Written in procedures, functions, internal code

ot M
• Written in views, security grants
N D
• Embedded and inferred in data content
o P
D tP

• In Word, PowerPoint, Excel documents …

h

• In diagrams and workflow models

se ig

• In people’s brains
r
ea y
Pl op
C
 10
20
DISCUSSION TOPIC

n
tio
Professional Petroleum Data Management Association

ia
Business Rules Workshop: 2

y c
Rule Source and description Available to your Who creates / Any conficts Retention Subject to Available to
company? owns the rule? with other strategy? variation or Others?

o
(Do you know what (Vendor, local known rules? change? In what form?
they are?) organization)

op ss
In your user’s software applications

C A
In ETL tools

ot M
In Mapping spreadsheets
N D
In your data cleansing tools
o P
Explicit or inferred in data models
D tP

Written in procedures, functions, internal

code
h

Written in views, security grants

se ig

Embedded and inferred in data content

r

In Word, PowerPoint, Excel documents …

ea y
Pl op

In diagrams and workflow models

In people’s brains
C
 10
20
PARTS OF A BUSINESS RULE (BRG)

n
tio
Business rules are atomic

ia
• They cannot be broken down into

y c
more detailed business rules

o
They consist of these parts

op ss
C A
• The policy
- general statement of direction for an

ot M
enterprise
N D
• The business rule statement
o P
- business rule in plain language
D tP

• The formal rule statement

- expression of the rule in a formal grammar,
h

- the definition of the grammar that is used

se ig

(SQL, BRML)
r

Don’t forget that rules must be

ea y

enforced.
Pl op

• They are not just suggestions!

C
 10
20
WHAT DATA RULES DO

n
tio
Help us standardize how data is defined

ia
• Common sets of terms and definitions that are based on the business, and that meet

y c
the needs of data managers, IT and business!

o
Govern how data is created and managed

op ss
• Well logs can’t be created until a well exists

C A
Enforce important policies that should be supported

ot M
• Well logs must always be associated with the appropriate Wellbore
N D
Support best practice recommendations
o P

• The What is a Well component terms and definitions should be applied corporately
D tP

Allow us to verify data quality / trustworthiness

h

• The deepest depth of a logged interval cannot be deeper than the deepest depth of a
se ig

Wellbore
r

• If data contains Latitude and Longitude, the CRS must also be populated
ea y
Pl op

• A well’s spud date may not be before the drilling permit date.
C
 10
20
PPDM & INDUSTRY PROPOSALS FOR
BUSINESS RULES

n
tio
Definitions of Business Terms

ia
• What is a ???

y c
- What is a Well is underway

o
- What is a Well Status is starting

op ss
- What is a Facility is planned

C A
• What are the minimum data requirements for definition of a data object?

ot M
Relationships and Constraints
N D
• Industry standard data model (PPDM 3.8)
o P
Best practice recommendations
D tP

• How should volumes be rolled up from a 14 digit API to a 12 digit API?

h

Data quality and trustworthiness

se ig

• Simple – no completion date on an abandoned location

r

• Interpretive – [Completion Date – Spud Date] < 180

ea y
Pl op

• Regional – Total depth < 9,000’ for xxx formation in Wattenberg field
• Spatial – Tops picks < 10% variation within 0.5 mile radius
C
 10
20
PPDM PROJECT:
RULES FOR DATA QUALITY AND TRUSTWORTHINESS

n
tio
Definitions BRG Structure

ia
• What is a data rule? • Policy statement

y c
• What is a ??? - Why the rule exists

o
• Narrative language, expressed in

op ss
Methodology and process
readable form.

C A
• How rules are collected and validated - Conditions of applicability (regional)

ot M
Sample rule set • Formal language expression
• Enough to be a good starting set - May be SBVR, based on PPDM 3.8 … (not
N D
decided)
o P
Web site
D tP

• Receive and validate new rules

• Publication to industry and members This is a member funded
h

project
se ig

• Searchable, retrievable

Communication strategy
r
ea y

Let us know if you would

Pl op

Training and education materials

Maintenance and growth like to participate
C
 10
20
WHERE TO END UP?

n
tio
More global or regional rules

ia
• But fewer overall, as we will consolidate and integrate!

y c o
Fewer individual or divisional rules

op ss
Implementation independent

C A
• Everyone uses the same core set of rules

ot M
• Criteria for selecting a vendor
N D
o P
More standard rules
D tPh
se ig
r
ea y
Pl op

Fewer local rules

C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
AUTHOR: The Business Rules Group

ia
http://www.businessrulesgroup.org/brmanifesto.htm

y c o
Copyright, 2006– 2009. Business Rules Group.

op ss
C A
ot M
N D
o P
D tPh
se ig
r
ea y
Pl op
C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 1. Primary Requirements, Not Secondary

ia
y c
1.1. Rules are a first-class citizen of the requirements

o
world.

op ss
1.2. Rules are essential for, and a discrete part of, business

C A
models and technology models.

ot M
N D
o P
Data rules are important; they must be
D tP

central
h
se ig

to every data management strategy

r
ea y
Pl op
C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 2. Separate From Processes, Not Contained

ia
In Them

y c o
2.1. Rules are explicit constraints on behavior and/or

op ss
provide support to behavior.

C A
2.2. Rules are not process and not procedure. They should
not be contained in either of these.
ot M
2.3. Rules apply across processes and procedures. There
N D
should be one cohesive body of rules, enforced
o P
consistently across all relevant areas of business
D tP

activity.
h

Data rules apply to the industry;

they are not different for every company.
se ig
r

Data rules should not change when you move between software applications.
ea y
Pl op

We need consistent, reliable data rules.

C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 3. Deliberate Knowledge, Not A By-Product

ia
3.1. Rules build on facts, and facts build on concepts as

y c
expressed by terms.

o
op ss
3.2. Terms express business concepts; facts make assertions
about these concepts; rules constrain and support these

C A
facts.

ot M
3.3. Rules must be explicit. No rule is ever assumed about any
N D
concept or fact.
o P
3.4. Rules are basic to what the business knows about itself --
D tP

that is, to basic business knowledge.

3.5. Rules need to be nurtured, protected, and managed.
h
se ig

Data rules need to be expressed, documented and shared.

r
ea y
Pl op

Data rules connect business and IT.

C

Industry (we) must take ownership of our rules.

 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 4.Declarative, Not Procedural

ia
4.1. Rules should be expressed declaratively in natural-language sentences for

y c
the business audience.

o
4.2. If something cannot be expressed, then it is not a rule.

op ss
4.3. A set of statements is declarative only if the set has no implicit sequencing.

C A
4.4. Any statements of rules that require constructs other than terms and facts

ot M
N D imply assumptions about a system implementation.
4.5. A rule is distinct from any enforcement defined for it. A rule and its
enforcement are separate concerns.
o P

4.6. Rules should be defined independently of responsibility for the who, where,
D tP

when, or how of their enforcement.

4.7. Exceptions to rules are expressed by other rules.
h
se ig

Data rules are not transient, but they can change with the business.
r
ea y
Pl op

Data rules are not vendor specific.

Data rules are not vague – they are very specific.

C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 5.Well-Formed Expression, Not Ad Hoc

ia
y c
5.1. Business rules should be expressed in such a way that

o
they can be validated for correctness by business
people.

op ss
C A
5.2. Business rules should be expressed in such a way that
they can be verified against each other for

ot M
consistency.
N D
5.3. Formal logics, such as predicate logic, are fundamental
o P
to well-formed expression of rules in business terms,
D tP

as well as to the technologies that implement business

rules.
h
se ig

Data rules require oversight by the business.

r
ea y

Data rules can’t contradict each other.

Pl op

Everyone needs to apply data rules consistently.

C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 6.Rule-Based Architecture, Not Indirect Implementation

ia
6.1. A business rules application is intentionally built to accommodate

y c
continuous change in business rules. The platform on which the

o
application runs should support such continuous change.

op ss
6.2. Executing rules directly -- for example in a rules engine -- is a

C A
better implementation strategy than transcribing the rules into
some procedural form.

ot M
6.3. A business rule system must always be able to explain the
N D
reasoning by which it arrives at conclusions or takes action.
o P
6.4. Rules are based on truth values. How a rule’s truth value is
D tP

determined or maintained is hidden from users.

6.5. The relationship between events and rules is generally many-to-
h

many.
se ig
r

Data rules and applications should be independent.

ea y
Pl op

Data rules can evolve as the business evolves.

C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 7.Rule-Guided Processes, Not Exception-Based

ia
Programming

y c
7.1. Rules define the boundary between acceptable and unacceptable

o
business activity.

op ss
7.2. Rules often require special or selective handling of detected

C A
violations. Such rule violation activity is activity like any other
activity.

ot M
7.3. To ensure maximum consistency and reusability, the handling of
N D
unacceptable business activity should be separable from the
handling of acceptable business activity.
o P
D tPh

Data rules reflect a complex business.

se ig

How many of your rules are embedded in your ETL tool? Do you know
r

what they are? Do your users know?

ea y
Pl op

Global and regional variations may be inevitable, but these can be

described and defined.
C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 8.For the Sake of the Business, Not Technology

ia
8.1. Rules are about business practice and guidance; therefore, rules

y c
are motivated by business goals and objectives and are shaped

o
by various influences.

op ss
8.2. Rules always cost the business something.

C A
8.3. The cost of rule enforcement must be balanced against business

ot M
risks, and against business opportunities that might otherwise be
lost.
N D
8.4. ‘More rules’ is not better. Usually fewer ‘good rules’ is better.
o P
D tP

8.5. An effective system can be based on a small number of

rules. Additional, more discriminating rules can be subsequently
added, so that over time the system becomes smarter.
h
se ig

Data rules are about the business!

r
ea y
Pl op

As we create and consolidate rules, the overall number should

go down, but they will be expressed better.
C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 9.Of, By, and For Business People, Not IT

ia
People

y c o
9.1. Rules should arise from knowledgeable business

op ss
people.

C A
9.2. Business people should have tools available to help
them formulate, validate, and manage rules.
ot M
9.3. Business people should have tools available to help
N D
them verify business rules against each other for
o P
consistency.
D tP

Data rules are by the business, for the business,

h

and about the business.

se ig
r
ea y

Data Managers must discover how to support the business in

Pl op

defining and describing rules.

C
 10
20
THE BUSINESS RULES MANIFESTO

n
tio
Article 10.Managing Business Logic, Not Hardware/Software

ia
Platforms

y c
10.1. Business rules are a vital business asset.

o
op ss
10.2. In the long run, rules are more important to the business than
hardware/software platforms.

C A
10.3. Business rules should be organized and stored in such a way

ot M
that they can be readily redeployed to new hardware/software
platforms.
N D
10.4. Rules, and the ability to change them effectively, are fundamental
o P
to improving business adaptability.
D tPh

Data rules should be a measurable asset.

se ig
r
ea y

Data rules are hardware, software, vendor independent.

Pl op

Data rules are practical and pragmatic, and evolve to suit the business.
C
 10
20
CONCLUSIONS

n
tio
Our Industry needs a standard, open set of business

ia
rules

y c o
The PPDM Association is working with industry to

op ss
create these

C A
• Some initiatives are underway now

ot M
• Others are planned
N D
We welcome your participation and input!
o P
D tP

• Our members drive and fund projects

• Many standards will be made publicly available
h
se ig
r
ea y
Pl op
C