Lars Taxén, [email protected]
PLM and incremental / parallel development
Lars TaxénDepartment of Science and Technology, Campus Norrköping, Linköping
University
[email protected], +46 73 0977864
Lars Taxén, [email protected]
C7 functions
CAMEL Ph3 / IN
A
X
E
M
G
W
T
r
a
c
k
GCP TRACK
Design Base
1.5
GPRS+SMS
f) GDB
SMS
a) CAPC
d) 1/APT
f) GDB
MAP SCCP
Segmentation
a) CAPC
d) 1/APT
Title: AXE Anatomy for 2.0
2/0062-FCPW 101 50 PA51
Editor: EED/X/D Stefan Berg
Date: 2002-04-11
PRA-Date: 2001-11-15(RFA 28.02.)
01-10-22
01-10-08
01-10-08
2E
01
2E
02
Dependency
2J
01
Basic Call
with AXE
01-10-15
01-10-30
APG40 / APZ11.1
Design base on
functional level, not
necessarily on product
level
01-11-15
new CSD
H.324
fallback
d) 1/APT
2U
01
2U
02
01-06-18
halfrate
removal
d) 1/APT
01-09-20
GT Mod. for
Connection
less traffic
a) CAPC
01-09-10
2J
04
Announcement
changes
a) CAPC
b) CNCP
01-09-10
2DA
03
Advanced call
cases with
AXE/Cello
BICC drop 2
compl. basic
call
a) CAPC
01-07-16
BICC drop 3
SS
a) CAPC
2DA
05
new HW
lift SMAC into 2.0
(incl. drop 2)
a) CAPC
b) CNCP
c) CSPP
d) 1/APT
f) GDB
h) SMAC part
2S
06
01-10-22
GPRS
charging
characteristics
f) GDB
01-10-08
2E
04
RONASSSP
a) CAPC
01-10-08
2E
05
ATI
g) SCP-T
01-09-10
2E
06
Cause of no
CLI
a) CAPC
d) 1/APT
2F
16
01-07-30
U2G HO
for CSD
a) CAPC
d) 1/APT
2F
13
01-10-08
SS
U2G HO + SRNS Relo.
R-TDM
CSD
IN
BICC ++
- MGW validation
- AXE-Cello
interwork
a) CAPC
b) CNCP
Server Recovery &
MGW node
recovery
b) CNCP
a) CAPC
d) 1/APT
Multiple MGW
support
- NRM impacts for
multiple MGWs
b) CNCP
enhanced traffic cases: depending on GCP
UMTS CSD calls
via GCP
b) CNCP
a) CAPC
d) 1/APT
enhanced traffic cases: depending on BICC
CSD calls via
GCP ++
a) CAPC
CH, CW
b) CNCP
a) CAPC
d) 1/APT
01-08-13
01-08-13
01-0
8-1
3
01-10-08
01-11-05
01-09-10
01-11-05
01-11-05
2CA
05
OMS
- call path
tracing
a) CAPC
b) CNCP
01-07-16
2C
01 Reception of bearer
release indications
(call release)
a) CAPC
b) CNCP
2C
03
2O
01
2O
02
Inter-System,
intra-MSC
Handover (via
GCP)
b) CNCP
a) CAPC
Inter-System, inter-
MSC Handover
(via GCP)
+ charging
a) CAPC
02-02-18
2P
02
2P
03
2P
01
MPTY,
IN conference,
O&M monitoring, LI
conference
b) CNCP
a) CAPC
01-11-05
02-03-15
2R
02
2R
01
Recovery on
termination,
termination group
and MGW level
a) CAPC
b) CNCP
01-10-22
01-11-19
Basic Call with Cello
Basic Call with Cello:
2 or more servers,
using BICC, using 1 MGW
UMTS-to-UMTS mobile speech call
periodic audit
a) CAPC
b) CNCP
01-10-08
01-11-05
2C
04
01-07-26
01-10-30
01-09-20
periodic audit
& test calls
a) CAPC
b) CNCP
01-11-12
01-10-22
01-11-19
Speech via GCP
load control
a) CAPC
b) CNCP
d) 1/APT
01-10-08
01-11-05
2C
05
01-08-13
MGW selection
PRA calls
a) CAPC2F
10
01-10-22
02-02-18
01-10-08
LI
2L
01
LI for new
architecture (via
GCP)
d) 1/APT
b) CNCP
a) CAPC
01-10-22
02-02-18
Test calls (via
GCP)
b) CNCP
a) CAPC
01-10-08
01-11-05
MGW + MGC cold
start
- O&M for MGW start
- Context/term.
handling for MGW
start
a) CAPC
b) CNCP
01-07-02
2CA
01
Simple Call
- context/term. handling
for calls
- basic protocol handling
a) CAPC
b) CNCP
d) 1/APT
2CA
02
01-09-20
01-07-16
01-07-10
01-10-22
02-02-18
2Q
01
2Q
02
digit sending (via
GCP), tones
d) 1/APT
b) CNCP
a) CAPC
01-10-30
01-10-08
02-02-18
MGW selection
for IN calls
a) CAPC2Q
03
Interactive
messageing
(design base)
a) CAPC
b) CNCP
EC procedures
b) CNCP
c) CSPP
a) CAPC
01-09-10
2F
06
2CA
06
2CA
04
01-09-10
01-11-05
2T
03
2T
04
G2U HO
Inter-MSC
G2U HO
a) CAPC
d) 1/APT
Subsequent HO
cases & charging
a) CAPC
d) 1/APT
2G
01
2G
02
01-09-30
01-10-22
01-09-10
Intra-MSC
G2U HO
a) CAPC
d) 1/APT2G
03
01-07-02
2F
11
Satelite page load
balancing
d) 1/APT
01-08-13
2F
12
Traffic
Based
Pricing
RMP
Service
Interface
b) CNCP
Service User
a) CAPC
Service User
d) 1/APT
01-09-10
01-08-27
01-09-10
2H
01
2H
02
2H
04
01-09-20
01-07-30
Traffic handling
a) CAPC
b) CNCP
01-10-08
01-11-05
2T
02
configuration,
blocking/
deblocking
a) CAPC
b) CNCP
01-09-10
2T
01
MGW Selection
at re-routing
a) CAPC
01-07-30
2DA
09
Japan Specific
TTC C7
d) 1/APT
2W
01
2W
02
FNR file I/O
f) GDB
01-08-13
01-09-15
01-09-10
CALEA + GS
support
a) CAPC
d) 1/APT
01-10-22
2F
08
AXE par. &
DSA
a) CAPC
d) 1/APT
2F
20
01-10-22
Available LSVs:
LSV 30: 01-05-21 LSV 31: 01-06-04 LSV32: 01-06-18 LSV 33: 01-07-02 LSV 34: 01-07-16 LSV35: 01-07-30 LSV 36: 01-08-13 LSV 37: 01-08-27 LSV 38 01-09-10 LSV 39: 01-09-24 LSV 40: 01-10-08 LSV 41: 01-10-22 LSV42: 01-11-05 CM1: 01-11-19 CM2: 01-12-03 CM3: 01-12-17 CM4: 2002-01-07 CM5: 2002-01-21 CM6: 2002-02-04 CM7: 2002-02-18
LPT Test calls
a) CAPC
2F
21
01-09-10
01-xx-xxFT ready;
FORLOPP
improvem.
21230/33
b) CNCP
2M
09
RPS FC
b) CNCP
2M
0601-10-22
Restart
reason
b) CNCP
2M
07
01-10-22
SPoE
a) CAPC
b) CNCP
2M
02
STS
a) CAPC
01-12-17
2M
05
Satelite backward
compatibility
a) CAPC
d) 1/APT
01-08-13
2F
07
early Shockley
a) CAPC
b) CNCP
c) CSPP
2S
05
01-07-02
CSPP:
01-07-16
SMS Waiting
f) GDB
01-10-08
2F
27
ANSI 41 NP
a) CAPC
f) GDB
01-10-22
2F
22
UMTS auth.
redundancy
enha.
f) GDB
01-10-08
2F
24
Outgoing (+incoming)
AAL2 connections,
I.trunk (ALI FW)
Reset procedures
a) CAPC
b) CNCP
2D
01
01-07-16
01-07-26
New Architecture Platform
01-07-10
New Services Platform
01-07-10MGW Selection (Simple):
- only for AXE MGW
- internal OIP
- only basic call
a) CAPC
d) 1/APT
2A
01
01-07-02
MTP3B long
messages STC
CB interface
a) CAPC
01-05-21
2B
01
BICC CS1 --
- basic call
a) CAPC
2B
03
01-07-02
MTP3B long
messages MTP
CB interface
a) CAPC01-07-02
2B
04
MTP3B long
messages
support
a) CAPC
b) CNCP
01-08-13
2DA
07
BICC drop 3
special services
a) CAPC
01-09-24
2DA
08
01-07-30
01-09-20
Basic Call with AXE MGW :
2 or more servers,
using BICC, using only AXE MGWs,
UMTS-to-UMTS mobile speech call,
UMTS-to-GSM mobile speech call,
GSM-to-UMTS mobile speech call,
GSM-to-GSM mobile speech call
C-HSSL
a) CAPC
b) CNCP
2S
09
01-09-10
APG40
charg.
g) SCP-T
a) CAPC
2M
1001-10-08
2DA
04
TLV merge
a) CAPC
d) 1/APT
01-09-10
2F
28
Number portability
MNP functions
a) CAPC
d) 1/APT
01-08-1301-08-20
2K
01
APIO
b) CNCP
2M
1201-10-22
AP
Communic.
b) CNCP
01-10-22
2M
11
MTAP
improvments
b) CNCP
01-10-22
2M
14
SW record
b) CNCP
01-10-22
2M
15
Iur
d) 1/APT
a) CAPC
01-10-22
2F
30
Shared Netw.
d) 1/APT
2F
32
01-10-22
Long RANAP
messages
a) CAPC
d) 1/APT
2J
05
01-10-08
BICC drop 4
APM & Comp.
Handling
a) CAPC
01-10-08
2DA
10
Security
a) CAPC
b) CNCP
01-10-22
2M
13
GOH
b) CNCP
2M
03
01-10-22
MAPv3 MT-
SMS
f) GDB
01-10-22
2F
34
AMR for GSM
d) 1/APT
01-09-10
2F
02
Single Cl.
Group
a) CAPC
b) CNCP
01-10-22
2M
16
FTP virtual
root
a) CAPC
b) CNCP
01-10-22
2M
17
SEQS
a) CAPC
2F
14
01-10-22
Can. Meter Puls
a) CAPC
d) 1/APT
2F
35
Satelite CIP tone
+ CSD
a) CAPC
d) 1/APT
01-09-10
2F
31
Security
Context
d) 1/APT
2F
36
01-10-22
RAB Mod.
d) 1/APT
2F
37
01-10-22
2Q
04
digit receiving (via
GCP)
b) CNCP
a) CAPC
01-11-05
OP / SQN
f) GDB
01-10-22
2F
23 2F
33
New OIP Pack.
d) 1/APT
a) CAPC
01-10-08
TRAMification of
TSS (2.0 scope)
Part I
a) CAPC
2F
18
01-10-08
MONCO
a) CAPC
b) CNCP
2F
29
Long RANAP
messages, CO
a) CAPC
d) 1/APT
2J
06
01-11-05
UMTS&GSM
term. FTM
f) GDB
2U
04
01-10-22
UMTS&GSM
term. FTM
a) CAPC
d) 1/APT
2U
03
01-09-10
ALI-
Beaomon
interw.
b) CNCP
2S
08
01-10-22
Announceme
nt changes II
b) CNCP
01-10-08
2DA
11
TRAMification of
TSS (2.0 scope)
Part II: Russan,
1.5 spillover
a) CAPC
d) 1/APT01-11-05
2F
38
HO for CSD calls via
GCP
b) CNCP
a) CAPC
d) 1/APT
2P
05
01-11-05
02-03-15
G2U HO,
architecture split
test cases (test
only!)
d) 1/APT
2P
06
02-01-28
SRNC
reallocation (via
GCP; same
MGW)
b) CNCP
01-10-22
02-02-18
Local
subscription
d) 1/APT
2F
39
01-10-22
UMTS positioning
a) CAPC
d) 1/APT
f) GDB
01-11-05
2F
26
FTM clean up
a) CAPC
d) 1/APT
f) GDB
2U
05/
06
01-11-05
FORLOPP
improvem.
21220/25
b) CNCP
2M
18
HO Charging
a) CAPC
d) 1/APT
01-07-02
2F
09
01-11-05
Service
User, IN
calls
a) CAPC
01-09-10
2H
05
Service
User, ANSI
TSS
a) CAPC
01-10-22
2H
06
TRAMification of
TSS (2.0 scope)
Part III: Israel
& French
a) CAPC
02-02-04
CN-I
2F
40
TRAMification
of PBX
a) CAPC
01-11-05
2F
41
01-xx-xx
01-yy-yy
1. date: delivery of
all products except
GACON; all FT that
can be done without
GACON is ready!
2. date : FT ready,
including GACON
test cases. INDUS
can start to use it.
ECP101
c) CSPP
02-01-22
2S
10
EA cleanup
a) CAPC
d) 1/APT
01-11-05
2F
42
PRA
monitoring
CN-I
a) CAPC
01-12-17
2F
44
Delivered to LSV, FT done
Delivered to LSV, FT not compl.eted
Under design or FT, not delivered to LSV,
requires major management attention
Under design or F, not delivered to LSV, some
issues require attention
Under design or F, not delivered to LSV, no
problem.
Handover
improve.
a) CAPC
d) 1/APT
2F
4501-11-05
Timer
improvements
b) CNCP
d) 1/APT
01-11-05
2Q
05
Kc over MAP
d) 1/APT
2F
46
01-11-05
Verification of
UMTS AMR
modes
c) CSPP
01-12-03
2F
17
DES mark
d) 1/APT
a) CAPC
2F
47
01-11-05
01-10-22
MONT fix
a) CAPC
d) 1/APT
2F
48
01-12-17
CAI & CARI
a) CAPC
2F
49
01-12-17
Iran CAS
a) CAPC
2F
43
periodic
audit
clean-up
b) CNCP
02-02-04
2C
06
02-02-15
CN-I
CALEA for CMS40
a) CAPC
b) CNCP
d) 1/APT
02-04-30
CN-I
2F
50
Lars Taxén, [email protected]
Trends impacting PLM ...
• Complexity
• Change
• Diversification
– outsourcing, mergers, acquisitions
– new in-house functions, e.g. Marketing & Sales, Services
– extended enterprise, networks
Lars Taxén, [email protected]
… cause emergent PLM problems
• Concepts, terminology
– confusion about meaning and interpretation increases
• Interdependencies
– increases btw. processes, product structures, information systems
• Product structures
– separate structures in different areas
• Coordination
– increased confusion about how coordination should be apprehended
• Commitments and agreements
– unclear
• Information System architectures
– evolve ad-hoc
Lars Taxén, [email protected]
What is PLM?
“PLM is a strategic business approach that applies a consistent
set of business solutions in support of the collaborative
creation, management, dissemination, and use of product
definition information across the extended enterprise from
concept to end of life – integrating people, processes, and
information. PLM forms the product information backbone for a
company and its extended enterprise.” (CIMdata, 2003)
Must be useful in practice - operational
Must address emergent problem areas
Lars Taxén, [email protected]
Elements of PLM
Lars Taxén, [email protected]
Traditional perspective on PLM
• Processes (BPR)
– Business Process Reengineering
• Information systems (ERP, PDM)
– Enterprise Resource Planning, Product Data Management
• Product structures
• Mostly isolated initiatives
Lars Taxén, [email protected]
Alternative perspective on PLM
• Coordination of cooperating practices
– Coordination: “The management of dependencies between activities”
– Practice: a group of actors producing something for other actors
• Shared meaning
• Interdependencies
• Commitments and agreements
Lars Taxén, [email protected]
The starting point - theory
• A search light - illuminates what is important
• See how things are related
• A common, shared framework in discussions
• Grounded in trustworthy knowledge
• Practical purposes
– Analyse a confused situation
– Developing information systems
“There is nothing so practical as a good theory.” Kurt Lewin
Lars Taxén, [email protected]
The Activity Domain Theory
Building a house
Lars Taxén, [email protected]
The Activity Domain Theory ...
Actors
Motive has
Outcome producesActivity Domain
has
Object works on
• Examples on Activity Domains
– A restaurant
– A carpenter
– House manufacturing company
– ...
Lars Taxén, [email protected]
Example: Activity domains for building a house
• Turnkey contractor– Masens House Ltd.
• Carpeting and cement work
– Nail & Cement Ltd.
• HVAC
– HVAC Consulting
• Electricity
– Electricity Unlimited
A
B
C
Lars Taxén, [email protected]
Main Activity Domains at Ericsson
Many Services unitsEach Service Unit supports many products and is active on many markets
Many products, many PDU’sEach product on many marketsand many supply and service units
In Service Support Installed Base
Marketing & Sales Customers, Tenders
Many markets, many MU’sEach market are working with many products and many supply and service units
Supply & Implementation Orders
Many Flow Control CentersFor each FC many products and markets
PLM
Research & Development, Product
Lars Taxén, [email protected]
… The Activity Domain Theory ...
Context Model
signifies the structure
of the
Actors
Motive has
Outcome producesActivity Domain
has
Object works on
• Examples on Context Models
– Information model
– Business model
– Product structure
– Data model
– Information Architecture
– ...
Lars Taxén, [email protected]
Context Model - Masens House Ltd.
Building element
House
Wall
HVAC
Roof
Floor
Frame
House foundation
Electricity
is_a
Needs(affordance)
includes
acts_on
Work package (Increment)
Activity domain
Customer
Needs(affordance)
Lars Taxén, [email protected]
Context - what is a grand piano?
Tone!
Same object – different qualities depending on context
Tons!
Lars Taxén, [email protected]
Dependencies
house
groundwork
Basis for house foundation
house foundation
Anchoring frame
Foundation for floor
Connection of electricity
Connection of HVAC
frame
Anchoring walls
Anchoring roof
walls roof HVAC electricityfloor
Protection against ground
Water, draining, heatProtection from
aboveProtection from side Light, cooking
Anatomy
Lars Taxén, [email protected]
… The Activity Domain Theory ...
Context Model Process Model
signifies the structure
of the
signifies dependencies between
activities
relates to
Actors
Motive has
Outcome producesActivity Domain
has
Object works on
• Examples on Process Models
– Business process
– Development process
– Supply process
– ...
Lars Taxén, [email protected]
Events – time dimension
Nail & Cement Ltd.A
HVAC ConsultingB
Electricity UnlimitedC
Delayed
On-going
Finished
Not started
Frame
House foundation
Groundwork
Walls
Roof
Floor
HVAC
Electricity
House
Lars Taxén, [email protected]
Events – time dimension
Nail & Cement Ltd.A
HVAC ConsultingB
Electricity UnlimitedC
Delayed
On-going
Finished
Not started
Frame
House foundation
Groundwork
Walls
Roof
Floor
HVAC
Electricity
House
Make
groundwork
A
Lars Taxén, [email protected]
Events – time dimension
Nail & Cement Ltd.A
HVAC ConsultingB
Electricity UnlimitedC
Delayed
On-going
Finished
Not started
Frame
House foundation
Groundwork
Walls
Roof
Floor
HVAC
Electricity
House
Make
groundwork
A
Build
frame
Fix
electricity
Lay floor Fix
HVAC
AA B C
Lars Taxén, [email protected]
Events – time dimension
Nail & Cement Ltd.A
HVAC ConsultingB
Electricity UnlimitedC
Delayed
On-going
Finished
Not started
Frame
House foundation
Groundwork
Walls
Roof
Floor
HVAC
Electricity
House
Make
groundwork
A
Build
frame
Fix
electricity
Lay floor Fix
HVAC
AA B C
Nail
walls
Lay
roof
AA
Lars Taxén, [email protected]
Events – time dimension
Nail & Cement Ltd.A
HVAC ConsultingB
Electricity UnlimitedC
Delayed
On-going
Finished
Not started
Frame
House foundation
Groundwork
Walls
Roof
Floor
HVAC
Electricity
House
Make
groundwork
A
Build
frame
Fix
electricity
Lay floor Fix
HVAC
AA B C
Nail
walls
Lay
roof
AA
Lars Taxén, [email protected]
Events – time dimension
Nail & Cement Ltd.A
HVAC ConsultingB
Electricity UnlimitedC
Delayed
On-going
Finished
Not started
Frame
House foundation
Groundwork
Walls
Roof
Floor
HVAC
Electricity
House
Make
groundwork
A
Build
frame
Fix
electricity
Lay floor Fix
HVAC
AA B C
Nail
walls
Lay
roof
AA
Finish
house
A
Lars Taxén, [email protected]
Progress
house
groundwork
frame
walls roof HVAC electricityfloor
house foundationDELAYED
IN DESIGN
READY
NOT STARTED
Lars Taxén, [email protected]
Progress
house
groundwork
frame
walls roof HVAC electricityfloor
house foundationDELAYED
IN DESIGN
READY
NOT STARTED
Lars Taxén, [email protected]
Progress
house
groundwork
frame
walls roof HVAC electricityfloor
house foundationDELAYED
IN DESIGN
READY
NOT STARTED
Lars Taxén, [email protected]
Progress
house
groundwork
frame
walls roof HVAC electricityfloor
house foundationDELAYED
IN DESIGN
READY
NOT STARTED
Lars Taxén, [email protected]
Progress
house
groundwork
frame
walls roof HVAC electricityfloor
house foundationDELAYED
IN DESIGN
READY
NOT STARTED
Lars Taxén, [email protected]
… The Activity Domain Theory ...
Context Model Process Model
signifies the structure
of the
relates to
interacts with other ADs according to Actors
Motive has
Outcome producesActivity Domain
has
Object works on
Transition Model
• Examples
– Different languages
– Cultural differences
– Different currencies
– Product identification rules
– ...
signifies dependencies between
activities
Lars Taxén, [email protected]
… The Activity Domain Theory ...
Context Model Process Model
signifies the structure
of the
relates to
interacts with other ADs according to Actors
Motive has
Outcome producesActivity Domain
has
Object works on
Domain Coreis stabilized by
Transition Model
• Examples
– Rules
– Standards
– Norms
– ...
signifies dependencies between
activities
Lars Taxén, [email protected]
… The Activity Domain Theory ...
Context Model Process Model
signifies the structure
of the
relates to
interacts with other ADs according to Actors
Motive has
Outcome producesActivity Domain
has
Information System (IS)
IS Architecture (ISA)
supports the activities in
Object works on
Domain Coreis stabilized by
constitute in relation to each other
Implemented in
Transition Model
Implemented in
signifies dependencies between
activities
Lars Taxén, [email protected]
Demo - Information system support
Lars Taxén, [email protected]
Information system - context model definition
Lars Taxén, [email protected]
Information system - related objects, data
Lars Taxén, [email protected]
Beroendematris
Lars Taxén, [email protected]
What about incremental development?
• Increment
– a development task split in smaller parts
– builds on a verified base
– is a verifiable addition to the system
– is a development task: a “mini-project”
– has a ready date
Analysis Implementation TestPlan Integrate
Plan
Integrate
Lars Taxén, [email protected]
03-11-01
03-10-01
03-09-1503-09-01
03-08-01
Possible increments
house
groundwork
frame
walls roof HVAC electricityfloor
house foundation
Lars Taxén, [email protected]
Dependencies - increments
03-11-01
03-10-0103-09-1503-09-01
03-08-01
groundwork
Increment 1
Increment 2 Increment 3 Increment 4
Increment 5
Lars Taxén, [email protected]
Coordination of 3G development projects
• Four Activity Domains (Sweden, Germany)
• Global information system support (eMatrix)
• Continuous change of information system implementation
– ~500 / year
• Used by ~140 main and sub-projects between 1998-2002
Lars Taxén, [email protected]
Profound impacts
“Especially for the execution part I think we would not have been able
to run this project without the tool. I think if you simply look at the
number of work packages, the number of products that we have
delivered, the number of deliveries that we have had, if we would have
had to maintain that manually, that would have been a sheer disaster.”
(Project manager, MSC node, 3G mobile system)
Lars Taxén, [email protected]
Restructuring PLM
• Activity domains in the organisation
• Clean-up of terminology
• Multi-domain product structure
• Prototype of a core information system
• Balancing between control and autonomy
• Alternative business process model
Lars Taxén, [email protected]
Business process - traditional
Performance Need or Incident
Solution Need
Changes & Expectations
& Gap
New Standards & Technology
Performance Fulfilment
Solution Fulfilment
Product in Service
PC0 PC1 PC2 PC3 PC4 PC5
PC6 SC8
SC1
SC6SC3
SC5
SC4SC2
SC7
Design Market Offer
Create Business
SalesSupply
SolutionImplement Solution
In-Service Support
Design & Verify Product
Define
y
Define Business
Opportunity
Exhibit Product in
Service
Specify Product
Define Product Content
Account Management
Product Management
System Management
Design & Test Management
Supply Management
Global Services
Management
Prepare Deploymen
t
Lars Taxén, [email protected]
Business process - alternative
DefineBusiness
Opportunity
DefineProductContent
PrepareDeployment
ExhibitProduct
in Service
SpecifyProduct
CreateBusiness
Sales In ServiceSupport
ImplementSolution
SupplySolution
Performance fulfillment
Product in service
Solution fulfillment
Performance need / Incident
Market offer
New standards & techn.
Product Impl Specification
Verified Product
Product Release Intent
Product ready for deploym.
Solution need
Changes & exp.& Gap
Market Offer Intent
Request for Quotation, RFQ
Order / Contract
Product on site
DesignMarketOffer
Design &Verify
Product
SC1: Approval of business opportunitySC2: Product development / termination decisionSC3: Product model approvalSC4: Design Implementation DecisionSC5: Announcement decisionSC6: Product quality approvedSC7: Market release decisionSC8: Full deployment acknowledged
PC0: Offer requestedPC1: Offer enteredPC2: Product arrivedPC3: Ready for AcceptancePC4: Customer AcceptancePC5: Product in service (?), see SC7PC6: Solution fulfillment
SC7
PC0
PC1
PC2
SC8
PC3,4,5
PC6
SC5
SC1
SC2
SC3,4
SC6
?
A A B B B C C DA A A A
Lars Taxén, [email protected]
Dependency diagram ABB
Courtesy: Joakim Lilliesköld, KTH
Lars Taxén, [email protected]
Towards an alternative PLM foundation
Lars Taxén, [email protected]
Towards an alternative PLM foundation
In Service
SupportMarketing &
Sales
Supply &
Implementation
PLM
Research &
Development,
Activity Domains
Lars Taxén, [email protected]
Towards an alternative PLM foundation
In Service
SupportMarketing &
Sales
Supply &
Implementation
PLM
Research &
Development,
Activity Domains
Context Model
Lars Taxén, [email protected]
Towards an alternative PLM foundation
Gjuta
grund
Bygga
stomme
Spika
väggar
Lägga
Tak
Dra
el
Lägga
golvDra in
VVS
Färdigställa
hus
A A AA A B C A
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Process model
In Service
SupportMarketing &
Sales
Supply &
Implementation
PLM
Research &
Development,
Activity Domains
Context Model
Lars Taxén, [email protected]
Towards an alternative PLM foundation
Gjuta
grund
Bygga
stomme
Spika
väggar
Lägga
Tak
Dra
el
Lägga
golvDra in
VVS
Färdigställa
hus
A A AA A B C A
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Process model
Information System
In Service
SupportMarketing &
Sales
Supply &
Implementation
PLM
Research &
Development,
Activity Domains
Context Model
Lars Taxén, [email protected]
Towards an alternative PLM foundation
In Service
SupportMarketing &
Sales
Supply &
Implementation
PLM
Research &
Development,
Activity Domains
Gjuta
grund
Bygga
stomme
Spika
väggar
Lägga
Tak
Dra
el
Lägga
golvDra in
VVS
Färdigställa
hus
A A AA A B C A
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Process model
Information System
Focus on shared meaning
Context Model
Lars Taxén, [email protected]
Towards an alternative PLM foundation
In Service
SupportMarketing &
Sales
Supply &
Implementation
PLM
Research &
Development,
Activity Domains
Gjuta
grund
Bygga
stomme
Spika
väggar
Lägga
Tak
Dra
el
Lägga
golvDra in
VVS
Färdigställa
hus
A A AA A B C A
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Stomme
Grund
Mark
Väggar
Tak
Golv
VVS
El
Hus
Process model
Information System
Focus on shared meaning
The Activity Domain Theory
Context Model Process Model
signifies the structure of
the
signifies how activities are
coordinated in the
relates to
interacts with other ADs according to Actors
Motive has
Outcome produces Activity Domain
has
Information System (IS)
IS Architecture (ISA)
supports the activities in
Object works on
Domain Coreis stabilized by
constitute in relation to each other
Implemented in
Transition Model
Implemented in
• Confusion about meaning ?
• Control of dependencies ?
• Different product structures ?
• Confusion about coordination ?
• Commitments and agreements ?
• IS architectures ad-hoc ?
Context Model
Lars Taxén, [email protected]
References
• Taxén L (2003) A Framework for the Coordination of Complex Systems’ Development, Dissertation No. 800. Linköping University, Dep. of Computer &Information Science, 2003. Downloadable from http://www.ep.liu.se/diss/science_technology/08/00/index.html
– The Activity Domain Theory
– A framework for coordination (includes the PDM system eMatrix)
– The history of the framework at Ericsson
– Experiences from using the framework in the 3G systems development
• Taxén L, Svensson D (2005) Towards an Alternative Foundation for Managing Product Life-Cycles in Turbulent Environments, International Journal of Product Development (IJPD), 2(1-2), 24-46.
– Results from the PLM restructuring initiative at Ericsson
• Anderstedt J&U, Karlsson M, Klasson M (2002) Projekt och Helhet - att leda projekt ipraktikent, Stockholm: Författarna
– Integration driven development, anatomies
• Taxén, L. (2009). Using Activity Domain Theory for Managing Complex Systems. Information Science Reference. Hershey PA: Information Science Reference (IGI Global). ISBN: 978-1-60566-192-6.
Lars Taxén, [email protected]
C7 functions
CAMEL Ph3 / IN
A
X
E
M
G
W
T
r
a
c
k
GCP TRACK
Design Base
1.5
GPRS+SMS
f) GDB
SMS
a) CAPC
d) 1/APT
f) GDB
MAP SCCP
Segmentation
a) CAPC
d) 1/APT
Title: AXE Anatomy for 2.0
2/0062-FCPW 101 50 PA51
Editor: EED/X/D Stefan Berg
Date: 2002-04-11
PRA-Date: 2001-11-15(RFA 28.02.)
01-10-22
01-10-08
01-10-08
2E
01
2E
02
Dependency
2J
01
Basic Call
with AXE
01-10-15
01-10-30
APG40 / APZ11.1
Design base on
functional level, not
necessarily on product
level
01-11-15
new CSD
H.324
fallback
d) 1/APT
2U
01
2U
02
01-06-18
halfrate
removal
d) 1/APT
01-09-20
GT Mod. for
Connection
less traffic
a) CAPC
01-09-10
2J
04
Announcement
changes
a) CAPC
b) CNCP
01-09-10
2DA
03
Advanced call
cases with
AXE/Cello
BICC drop 2
compl. basic
call
a) CAPC
01-07-16
BICC drop 3
SS
a) CAPC
2DA
05
new HW
lift SMAC into 2.0
(incl. drop 2)
a) CAPC
b) CNCP
c) CSPP
d) 1/APT
f) GDB
h) SMAC part
2S
06
01-10-22
GPRS
charging
characteristics
f) GDB
01-10-08
2E
04
RONASSSP
a) CAPC
01-10-08
2E
05
ATI
g) SCP-T
01-09-10
2E
06
Cause of no
CLI
a) CAPC
d) 1/APT
2F
16
01-07-30
U2G HO
for CSD
a) CAPC
d) 1/APT
2F
13
01-10-08
SS
U2G HO + SRNS Relo.
R-TDM
CSD
IN
BICC ++
- MGW validation
- AXE-Cello
interwork
a) CAPC
b) CNCP
Server Recovery &
MGW node
recovery
b) CNCP
a) CAPC
d) 1/APT
Multiple MGW
support
- NRM impacts for
multiple MGWs
b) CNCP
enhanced traffic cases: depending on GCP
UMTS CSD calls
via GCP
b) CNCP
a) CAPC
d) 1/APT
enhanced traffic cases: depending on BICC
CSD calls via
GCP ++
a) CAPC
CH, CW
b) CNCP
a) CAPC
d) 1/APT
01-08-13
01-08-13
01-0
8-1
3
01-10-08
01-11-05
01-09-10
01-11-05
01-11-05
2CA
05
OMS
- call path
tracing
a) CAPC
b) CNCP
01-07-16
2C
01 Reception of bearer
release indications
(call release)
a) CAPC
b) CNCP
2C
03
2O
01
2O
02
Inter-System,
intra-MSC
Handover (via
GCP)
b) CNCP
a) CAPC
Inter-System, inter-
MSC Handover
(via GCP)
+ charging
a) CAPC
02-02-18
2P
02
2P
03
2P
01
MPTY,
IN conference,
O&M monitoring, LI
conference
b) CNCP
a) CAPC
01-11-05
02-03-15
2R
02
2R
01
Recovery on
termination,
termination group
and MGW level
a) CAPC
b) CNCP
01-10-22
01-11-19
Basic Call with Cello
Basic Call with Cello:
2 or more servers,
using BICC, using 1 MGW
UMTS-to-UMTS mobile speech call
periodic audit
a) CAPC
b) CNCP
01-10-08
01-11-05
2C
04
01-07-26
01-10-30
01-09-20
periodic audit
& test calls
a) CAPC
b) CNCP
01-11-12
01-10-22
01-11-19
Speech via GCP
load control
a) CAPC
b) CNCP
d) 1/APT
01-10-08
01-11-05
2C
05
01-08-13
MGW selection
PRA calls
a) CAPC2F
10
01-10-22
02-02-18
01-10-08
LI
2L
01
LI for new
architecture (via
GCP)
d) 1/APT
b) CNCP
a) CAPC
01-10-22
02-02-18
Test calls (via
GCP)
b) CNCP
a) CAPC
01-10-08
01-11-05
MGW + MGC cold
start
- O&M for MGW start
- Context/term.
handling for MGW
start
a) CAPC
b) CNCP
01-07-02
2CA
01
Simple Call
- context/term. handling
for calls
- basic protocol handling
a) CAPC
b) CNCP
d) 1/APT
2CA
02
01-09-20
01-07-16
01-07-10
01-10-22
02-02-18
2Q
01
2Q
02
digit sending (via
GCP), tones
d) 1/APT
b) CNCP
a) CAPC
01-10-30
01-10-08
02-02-18
MGW selection
for IN calls
a) CAPC2Q
03
Interactive
messageing
(design base)
a) CAPC
b) CNCP
EC procedures
b) CNCP
c) CSPP
a) CAPC
01-09-10
2F
06
2CA
06
2CA
04
01-09-10
01-11-05
2T
03
2T
04
G2U HO
Inter-MSC
G2U HO
a) CAPC
d) 1/APT
Subsequent HO
cases & charging
a) CAPC
d) 1/APT
2G
01
2G
02
01-09-30
01-10-22
01-09-10
Intra-MSC
G2U HO
a) CAPC
d) 1/APT2G
03
01-07-02
2F
11
Satelite page load
balancing
d) 1/APT
01-08-13
2F
12
Traffic
Based
Pricing
RMP
Service
Interface
b) CNCP
Service User
a) CAPC
Service User
d) 1/APT
01-09-10
01-08-27
01-09-10
2H
01
2H
02
2H
04
01-09-20
01-07-30
Traffic handling
a) CAPC
b) CNCP
01-10-08
01-11-05
2T
02
configuration,
blocking/
deblocking
a) CAPC
b) CNCP
01-09-10
2T
01
MGW Selection
at re-routing
a) CAPC
01-07-30
2DA
09
Japan Specific
TTC C7
d) 1/APT
2W
01
2W
02
FNR file I/O
f) GDB
01-08-13
01-09-15
01-09-10
CALEA + GS
support
a) CAPC
d) 1/APT
01-10-22
2F
08
AXE par. &
DSA
a) CAPC
d) 1/APT
2F
20
01-10-22
Available LSVs:
LSV 30: 01-05-21 LSV 31: 01-06-04 LSV32: 01-06-18 LSV 33: 01-07-02 LSV 34: 01-07-16 LSV35: 01-07-30 LSV 36: 01-08-13 LSV 37: 01-08-27 LSV 38 01-09-10 LSV 39: 01-09-24 LSV 40: 01-10-08 LSV 41: 01-10-22 LSV42: 01-11-05 CM1: 01-11-19 CM2: 01-12-03 CM3: 01-12-17 CM4: 2002-01-07 CM5: 2002-01-21 CM6: 2002-02-04 CM7: 2002-02-18
LPT Test calls
a) CAPC
2F
21
01-09-10
01-xx-xxFT ready;
FORLOPP
improvem.
21230/33
b) CNCP
2M
09
RPS FC
b) CNCP
2M
0601-10-22
Restart
reason
b) CNCP
2M
07
01-10-22
SPoE
a) CAPC
b) CNCP
2M
02
STS
a) CAPC
01-12-17
2M
05
Satelite backward
compatibility
a) CAPC
d) 1/APT
01-08-13
2F
07
early Shockley
a) CAPC
b) CNCP
c) CSPP
2S
05
01-07-02
CSPP:
01-07-16
SMS Waiting
f) GDB
01-10-08
2F
27
ANSI 41 NP
a) CAPC
f) GDB
01-10-22
2F
22
UMTS auth.
redundancy
enha.
f) GDB
01-10-08
2F
24
Outgoing (+incoming)
AAL2 connections,
I.trunk (ALI FW)
Reset procedures
a) CAPC
b) CNCP
2D
01
01-07-16
01-07-26
New Architecture Platform
01-07-10
New Services Platform
01-07-10MGW Selection (Simple):
- only for AXE MGW
- internal OIP
- only basic call
a) CAPC
d) 1/APT
2A
01
01-07-02
MTP3B long
messages STC
CB interface
a) CAPC
01-05-21
2B
01
BICC CS1 --
- basic call
a) CAPC
2B
03
01-07-02
MTP3B long
messages MTP
CB interface
a) CAPC01-07-02
2B
04
MTP3B long
messages
support
a) CAPC
b) CNCP
01-08-13
2DA
07
BICC drop 3
special services
a) CAPC
01-09-24
2DA
08
01-07-30
01-09-20
Basic Call with AXE MGW :
2 or more servers,
using BICC, using only AXE MGWs,
UMTS-to-UMTS mobile speech call,
UMTS-to-GSM mobile speech call,
GSM-to-UMTS mobile speech call,
GSM-to-GSM mobile speech call
C-HSSL
a) CAPC
b) CNCP
2S
09
01-09-10
APG40
charg.
g) SCP-T
a) CAPC
2M
1001-10-08
2DA
04
TLV merge
a) CAPC
d) 1/APT
01-09-10
2F
28
Number portability
MNP functions
a) CAPC
d) 1/APT
01-08-1301-08-20
2K
01
APIO
b) CNCP
2M
1201-10-22
AP
Communic.
b) CNCP
01-10-22
2M
11
MTAP
improvments
b) CNCP
01-10-22
2M
14
SW record
b) CNCP
01-10-22
2M
15
Iur
d) 1/APT
a) CAPC
01-10-22
2F
30
Shared Netw.
d) 1/APT
2F
32
01-10-22
Long RANAP
messages
a) CAPC
d) 1/APT
2J
05
01-10-08
BICC drop 4
APM & Comp.
Handling
a) CAPC
01-10-08
2DA
10
Security
a) CAPC
b) CNCP
01-10-22
2M
13
GOH
b) CNCP
2M
03
01-10-22
MAPv3 MT-
SMS
f) GDB
01-10-22
2F
34
AMR for GSM
d) 1/APT
01-09-10
2F
02
Single Cl.
Group
a) CAPC
b) CNCP
01-10-22
2M
16
FTP virtual
root
a) CAPC
b) CNCP
01-10-22
2M
17
SEQS
a) CAPC
2F
14
01-10-22
Can. Meter Puls
a) CAPC
d) 1/APT
2F
35
Satelite CIP tone
+ CSD
a) CAPC
d) 1/APT
01-09-10
2F
31
Security
Context
d) 1/APT
2F
36
01-10-22
RAB Mod.
d) 1/APT
2F
37
01-10-22
2Q
04
digit receiving (via
GCP)
b) CNCP
a) CAPC
01-11-05
OP / SQN
f) GDB
01-10-22
2F
23 2F
33
New OIP Pack.
d) 1/APT
a) CAPC
01-10-08
TRAMification of
TSS (2.0 scope)
Part I
a) CAPC
2F
18
01-10-08
MONCO
a) CAPC
b) CNCP
2F
29
Long RANAP
messages, CO
a) CAPC
d) 1/APT
2J
06
01-11-05
UMTS&GSM
term. FTM
f) GDB
2U
04
01-10-22
UMTS&GSM
term. FTM
a) CAPC
d) 1/APT
2U
03
01-09-10
ALI-
Beaomon
interw.
b) CNCP
2S
08
01-10-22
Announceme
nt changes II
b) CNCP
01-10-08
2DA
11
TRAMification of
TSS (2.0 scope)
Part II: Russan,
1.5 spillover
a) CAPC
d) 1/APT01-11-05
2F
38
HO for CSD calls via
GCP
b) CNCP
a) CAPC
d) 1/APT
2P
05
01-11-05
02-03-15
G2U HO,
architecture split
test cases (test
only!)
d) 1/APT
2P
06
02-01-28
SRNC
reallocation (via
GCP; same
MGW)
b) CNCP
01-10-22
02-02-18
Local
subscription
d) 1/APT
2F
39
01-10-22
UMTS positioning
a) CAPC
d) 1/APT
f) GDB
01-11-05
2F
26
FTM clean up
a) CAPC
d) 1/APT
f) GDB
2U
05/
06
01-11-05
FORLOPP
improvem.
21220/25
b) CNCP
2M
18
HO Charging
a) CAPC
d) 1/APT
01-07-02
2F
09
01-11-05
Service
User, IN
calls
a) CAPC
01-09-10
2H
05
Service
User, ANSI
TSS
a) CAPC
01-10-22
2H
06
TRAMification of
TSS (2.0 scope)
Part III: Israel
& French
a) CAPC
02-02-04
CN-I
2F
40
TRAMification
of PBX
a) CAPC
01-11-05
2F
41
01-xx-xx
01-yy-yy
1. date: delivery of
all products except
GACON; all FT that
can be done without
GACON is ready!
2. date : FT ready,
including GACON
test cases. INDUS
can start to use it.
ECP101
c) CSPP
02-01-22
2S
10
EA cleanup
a) CAPC
d) 1/APT
01-11-05
2F
42
PRA
monitoring
CN-I
a) CAPC
01-12-17
2F
44
Delivered to LSV, FT done
Delivered to LSV, FT not compl.eted
Under design or FT, not delivered to LSV,
requires major management attention
Under design or F, not delivered to LSV, some
issues require attention
Under design or F, not delivered to LSV, no
problem.
Handover
improve.
a) CAPC
d) 1/APT
2F
4501-11-05
Timer
improvements
b) CNCP
d) 1/APT
01-11-05
2Q
05
Kc over MAP
d) 1/APT
2F
46
01-11-05
Verification of
UMTS AMR
modes
c) CSPP
01-12-03
2F
17
DES mark
d) 1/APT
a) CAPC
2F
47
01-11-05
01-10-22
MONT fix
a) CAPC
d) 1/APT
2F
48
01-12-17
CAI & CARI
a) CAPC
2F
49
01-12-17
Iran CAS
a) CAPC
2F
43
periodic
audit
clean-up
b) CNCP
02-02-04
2C
06
02-02-15
CN-I
CALEA for CMS40
a) CAPC
b) CNCP
d) 1/APT
02-04-30
CN-I
2F
50
Top Related