Discoverable process map types from a Service Oriented Architecture perspective

Process mining perspectives

Process map discovery is approachable from many angles. One could worry primarily about the control-flow of activities , or about social networks between resources (the organizational perspective), about properties of cases, or about time. Attributes such as time / cost / etc add extra info layers to the original  map. 

Discoverable process map types

From the Service Oriented Architecture perspective, the world is a stage for request-provide transactions. Such transactions are conducted directly or via broker(s). From this viewpoint, the type of a discoverable process map is dictated by:

Examples of requestor / provider / broker entities for the fields we have taken a closer look at are listed below.

Domain Requestor
(has needs)
Provider
(has skills)
Broker
(has information)
Healthcare Patient  Hospital, Ward 
Personnel (Medic, Nurse)
Family doctor
Manufacturing Pallet  Conveyor, Robotic Cell, Manufacturing Cell
Shop floor personnel
Message broker middleware
Logistics Truck  Supply Unit, Warehouse
Sport Athlete Training facility , Coach, Medical personnel
TYPE OF PROCESS MAP ACTIVITY TYPE (range count 5-100)
Service requestor Service provider Broker
ACTOR / CASE TYPE
(range count: many)
Service requestor

REQUESTS NETWORK

(many requestors -> few requestors) 

TRANSFERS | REFERRALS* (iff providers incl. persons)

(many requestors ->  few providers)

BROKER / SUPPLY  NETWORK

(many requestors -> few brokers)

Service provider

TENDERS

(many providers ->  few requestors)

RESOURCE ALLOCATION

(many providers ->few providers)

BROKER / DEMAND NETWORK

(many providers -> few brokers)

Broker

DEMAND (NEEDS) NETWORK

(many brokers -> few requestors)

SUPPLY (SKILLS | CAPABILITIES) NETWORK

(many brokers -> few providers)

BROKER / PARTNERSHIPS

(many brokers -> few brokers)