data format mapping between spine and iso/ts...
TRANSCRIPT
Data format mapping between SPINE and ISO/TS 14048
Raul Carlson Markus Erlandsson Karolina Flemström Ann-Christin Pålsson Ulf Tidstrand Johan Tivander IMI - Industrial Environmental Informatics For CPM - Centre for Environmental Assessment of Product and Material Systems CHALMERS UNIVERSITY OF TECHNOLOGY Göteborg, Sweden 2003
CPM Report 2003:8
2
Contents Comparison of conceptual models ..............................................................3 Improvements in ISO/TS 14048 compared to SPINE...............................4 Data format mapping between ISO/TS 14048 and SPINE .......................5 Appendix A. Mapping of nomenclatures .................................................15 A.1 Exclusive nomenclatures ......................................................................................... 15 A.2 Inclusive nomenclatures .......................................................................................... 16 A.3 SPINE nomenclature, including user defined nomenclature............................... 21 A.3.1 Nomenclatures related to mandatory attributes in SPINE ...................................... 21 A.3.2 Nomenclatures related to optional attributes in SPINE .......................................... 23 Appendix B SPINE (LCI)-attributes excluded from the mapping.........25 Appendix C Unique identification and version control of data sets.......26 Format analysis ................................................................................................................. 26 Identification mapping ISO/TS 14048 to SPINE.............................................................. 27 Identification mapping SPINE to ISO/TS 14048.............................................................. 27 Version control within SPINE@CPM .............................................................................. 28 References...................................................................................................30
3
Comparison of conceptual models Crucially, the SPINE and ISO/TS 14048 data formats are describing the same world, and they are using the same conceptual model to describe this world (see figure 1).
Modellingprinciples
Process
Validation
Inputs & outputs
Figure 1 SPINE and ISO/TS 14048 are based on the same conceptual model.
Both formats are focusing on models of technical systems. The concept for this is named Process in ISO/TS 14048 and Activity in SPINE. Using the ISO-language a process is a model-representation of a well-defined part of a technical system with a definite system scope and boundary. The process has inputs and outputs flowing over the system boundaries referred to as Inputs and outputs in ISO/TS 14048 and Flow in SPINE. A process or activity have as many inputs and outputs as has been identified for the technical system, each representing a substance or energy flow that are entering in to or leaving out from the boundary of the system. When creating the model of the technical system, i.e. the process, some modelling principles are applied. After the process has been documented, the quality of the modelling and the documentation are validated in different ways.
System modelSPINE: Activity14048: Process
Inputs and outputsSPINE: Flow14048: inputs and outputs
DocumentatorSPINE: Practitioner14048: Data generator
Figure 2 Comparison of naming of most important concepts.
The person who is documenting the process and inputs and outputs is referred to as a Data generator in ISO/TS 14048 and Practitioner in SPINE.
4
Improvements in ISO/TS 14048 compared to SPINE There are many minor differences between SPINE and ISO/TS 14048, and there are some major improvements in the latter. Specification of the receiving environment In SPINE it is only possible to describe the media that an input or output impacts using one dimension, while two dimensions have been used in ISO/TS 14048. This is an improvement since it now is possible to specify both the environment where the input or output meets the technical system, air, water, soil, etc., as well as the environment where the cause-effect chain of an input or output actually begins, i.e. type of land, type of water, etc. Arbitrary statistical function In SPINE it is possible to attach statistical information to a value by specifying min, max and standard deviation for the value. In ISO/TS 14048 any function can be used to specify such statistical information for a numerical value, such as normal, beta or logarithmic distributions or actual series of sample-values. Enhanced specification of field contents ISO/TS 14048 has a larger number of fields than SPINE. This is because more subject-headers and subtitles for the documentation requirements of LCA have been assigned more explicitly in ISO/TS 14048 than in SPINE.
Dat
a fo
rmat
map
ping
bet
wee
n IS
O/T
S 14
048
and
SPIN
E Th
e da
ta fo
rmat
map
ping
is p
rese
nted
in ta
ble
1.
Tabl
e 1
Lege
nd:
Ref
eren
ce n
o.
Th
e re
fere
nce
num
ber o
f IS
O/T
S 14
048
data
fiel
d as
sta
ted
in IS
O/T
S 1
4048
Ann
ex A
D
ata
field
The
nam
e of
the
ISO
/TS
1404
8 da
ta fi
eld
T - d
ata
type
L
Labe
l
ST
Sh
ort t
ext
FT
Free
text
R
R
eal
In
t
Inte
ger
M
R
M
athe
mat
ical
rule
MV
Mat
hem
atic
al v
alue
DF
D
ate
form
at
D
I
Dat
e in
terv
al
P
ic
P
ictu
re
D
ir
Dire
ctio
n
6, 2
0, 2
55, e
tc.
Var
char
with
cor
resp
ondi
ng m
axim
um le
ngth
N
- N
omen
clat
ure
X
E
xclu
sive
nom
encl
atur
e
I In
clus
ive
nom
encl
atur
e
R
Nom
encl
atur
e by
refe
renc
e in
oth
er re
late
d at
tribu
te
U
U
ser d
efin
ed n
omen
clat
ure
O -
Allo
wed
occ
urre
nces
1 O
ne o
ccur
renc
e
N
Unl
imite
d nu
mbe
r of o
ccur
renc
es
From
SPI
NE
Th
e na
me
of th
e su
bmitt
ing
data
fiel
d in
SP
INE
that
is m
appe
d to
the
ISO
/TS
1404
8 da
ta fi
eld.
To
SPI
NE
The
nam
e of
the
rece
ivin
g da
ta fi
eld
in S
PIN
E th
at th
e IS
O/T
S 14
048
data
fiel
d m
appe
d to
. If t
he w
ord
“app
end”
is
pres
ent,
it in
dica
tes
that
mor
e IS
O/T
S 14
048
field
s ar
e m
appe
d to
one
and
the
sam
e ta
rget
SP
INE
field
. “Li
st” i
ndic
ates
th
at th
e fie
lds
shou
ld b
e st
ored
as
a lis
t as
the
targ
et fi
eld
only
hav
e on
e oc
cura
nce
whi
le th
ere
are
mul
tiple
sou
rce
field
s.
Map
ping
val
ue
Indi
cate
s if
the
map
ping
is s
atis
fyin
g or
if d
ata
dist
orsi
on o
ccur
s
6
IS
O/T
S 14
048
SP
INE
Ref
e-re
nce
no
. D
ata
field
T
N
O
From
SPI
NE
To S
PIN
E T
N
O
M
appi
ng V
alue
1 Pr
oces
s
1
1 O
K 1.
1 Pr
oces
s de
scrip
tion
1
1
OK
1.1.
1 N
ame
L
1 O
bjec
tOfS
tudy
.Nam
e O
bjec
tOfS
tudy
.Nam
e 10
0
1 O
K
1.1.
2 C
lass
U
1
OK
1.1.
2.1
Nam
e L
R
1 O
bjec
tOfS
tudy
.Sec
tor
Firs
t ins
tanc
e to
O
bjec
tOfS
tudy
.Sec
tor i
f "S
ecto
r" is
fo
und
in R
efer
ence
to
nom
encl
atur
e, e
lse
appe
nd to
In
vent
ory.
Not
es a
s lis
t
40
U
1 O
K
1.1.
2.2
Ref
eren
ce to
no
men
clat
ure
ST
1
"SPI
NE
@C
PM
1997
Obj
ectO
fStu
dy.
Sect
or"
Sect
or.N
otes
if "S
ecto
r" is
foun
d in
R
efer
ence
to n
omen
clat
ure,
els
e In
vent
ory.
Not
es (a
ppen
d)
FT
1
OK
1.1.
3 Q
uant
itativ
e re
fere
nce
1
1
OK
1.1.
3.1
Type
S
T I
1 "S
ee p
roce
ss.p
roce
ss_d
escr
iptio
n.
tech
nolo
gy.te
chni
cal_
cont
ent
_and
_fun
ctio
nalit
y"
Inve
ntor
y.FU
Expl
anat
ion
(app
end)
FT
1 O
K
1.1.
3.2
Nam
e S
T
1 "S
ee p
roce
ss.p
roce
ss_d
escr
iptio
n.
tech
nolo
gy.te
chni
cal_
cont
ent
_and
_fun
ctio
nalit
y"
Inve
ntor
y.FU
Expl
anat
ion
(app
end)
FT
1 O
K
1.1.
3.3
Uni
t S
T I
1 "S
ee p
roce
ss.p
roce
ss_d
escr
iptio
n.
tech
nolo
gy.te
chni
cal_
cont
ent
_and
_fun
ctio
nalit
y"
Inve
ntor
y.FU
Expl
anat
ion
(app
end)
FT
1 O
K
1.1.
3.4
Am
ount
R
1 -
Inve
ntor
y.FU
Expl
anat
ion
(app
end)
FT
1 O
K
1.1.
4 Te
chni
cal s
cope
S
T I
1 O
bjec
tOfS
tudy
.Cat
egor
y O
bjec
tOfS
tudy
.Cat
egor
y 20
I
1 O
K
1.1.
5 Ag
greg
atio
n ty
pe
ST
X
1 -
Inve
ntor
y.D
ata
(app
end)
FT
1 O
K
Aggr
egat
ion
is ra
rely
don
e in
one
di
men
sion
onl
y 1.
1.6
Tech
nolo
gy
1
1
OK
1.1.
6.1
Shor
t tec
hnol
ogy
desc
ripto
r S
T
1 O
bjec
tOfS
tudy
.Act
ivity
Type
O
bjec
tOfS
tudy
.Fun
ctio
n (a
ppen
d)
Impo
rter m
anua
lly c
hoos
es th
e
Obj
ectO
fStu
dy.A
ctiv
ityTy
pe a
s "P
roce
ss" o
r "Tr
ansp
ort"
or N
ULL
15
U
1 O
K
1.1.
6.2
Tech
nica
l con
tent
an
d fu
nctio
nalit
y FT
1 O
bjec
tOfS
tudy
.Fun
ctio
n O
bjec
tofS
tudy
.Ow
ner
Inve
ntor
y.Fu
nctio
nalU
nit
Inve
ntor
y.FU
Expl
anat
ion
Obj
ectO
fStu
dy.F
unct
ion
(app
end)
FT
1 O
K
1.1.
6.3
Tech
nolo
gy p
ictu
re
Pic
1 St
atic
pic
ture
file
gen
erat
ed fr
om
info
rmat
ion
in ta
bles
Sub
Syst
emPo
sitio
n
Flow
Con
nect
ionK
nee
UR
L to
pic
ture
file
(cou
ld b
e st
ored
in
loca
l file
sys
tem
) in
Obj
ectO
fStu
dy.F
unct
ion
(app
end)
FT
1
OK
7
1.
1.6.
4 Pr
oces
s co
nten
ts
1
1
OK
1.1.
6.4.
1 In
clud
ed p
roce
sses
L
U
O
bjec
tOfS
tudy
.Id a
nd A
ctiv
ityId
(c
onca
tena
ted)
refe
rred
to b
y C
ompo
nent
ship
.Sub
Sys
tem
The
corr
espo
ndin
g A
ctiv
ity.Id
of
the
impo
rted
subs
yste
m re
ferr
ed
by
Com
pone
ntsh
ip.S
ubS
yste
m
30
U
O
K
1.1.
6.4.
2 In
term
edia
te
prod
uct f
low
s
U
U
O
K
1.1.
6.4.
2.1
Sour
ce p
roce
ss
L
1 O
bjec
tOfS
tudy
.Id a
nd A
ctiv
ityId
(c
onca
tena
ted)
refe
rred
by
Flow
Con
nect
ion.
Sup
plie
rAct
Id
The
corr
espo
ndin
g A
ctiv
ity.Id
of
the
impo
rted
subs
yste
m re
ferr
ed
by
Flow
Con
nect
ion.
Sup
plie
rAct
Id
30
1
OK
1.1.
6.4.
2.2
Inpu
t and
out
put
sour
ce
Int
1
Flow
Con
nect
ion.
Out
Flow
Num
ber
Flow
Con
nect
ion.
Out
Flow
Num
ber
Int
1
OK
1.1.
6.4.
2.3
Inpu
t and
out
put
dest
inat
ion
Int
1
Flow
Con
nect
ion.
InFl
owN
umbe
r Fl
owC
onne
ctio
n.In
Flow
Num
ber
Int
1
OK
1.1.
6.4.
2.4
Des
tinat
ion
proc
ess
L
1 O
bjec
tOfS
tudy
.Id a
nd A
ctiv
ityId
(c
onca
tena
ted)
refe
rred
to b
y Fl
owC
onne
ctio
n.C
onsu
mer
Act
Id
The
corr
espo
ndin
g A
ctiv
ity.Id
of
the
impo
rted
subs
yste
m re
ferr
ed
by
Flow
Con
nect
ion.
Con
sum
erA
ctId
30
1
OK
1.1.
6.5
Ope
ratin
g co
nditi
ons
FT
1
"See
pro
cess
.pro
cess
_des
crip
tion.
te
chno
logy
.tech
nica
l_co
nten
t _a
nd_f
unct
iona
lity"
Obj
ectO
fStu
dy.F
unct
ion
(app
end)
FT
1 O
K
8
1.
1.6.
6 M
athe
mat
ical
m
odel
1
1 O
K
1.1.
6.6.
1 Fo
rmul
ae
MR
U
If da
ta e
xist
s in
Flo
wC
onne
ctio
n R
atio
s, a
ll fie
lds
of
Flow
Con
nect
ion
exce
pt
Flow
Con
nect
ion.
Sys
tem
Id
are
map
ped
as a
list
to th
e su
perio
r sy
stem
onl
y. I.
e.:
Flow
Con
nect
ion.
Con
sum
erA
ctId
Fl
owC
onne
ctio
n.In
Flow
Num
ber
Flow
Con
nect
ion.
Sup
plie
rAct
Id
Flow
Con
nect
ion.
Out
Flow
Num
ber
Flow
Con
nect
ion.
InR
atio
Fl
owC
onne
ctio
n.In
Rat
ioU
pper
Fl
owC
onne
ctio
n.In
Rat
ioLo
wer
Fl
owC
onne
ctio
n.O
utR
atio
Fl
owC
onne
ctio
n.O
utR
atio
Upp
er
Flow
Con
nect
ion.
Out
Rat
ioLo
wer
---
-----
-----
-----
-----
------
-----
-----
----
If da
ta e
xist
s in
Act
ivity
Para
met
er, a
ll fie
lds
of
Activ
ityP
aram
eter
exc
ept
Activ
ityP
aram
eter
.Sys
tem
Id a
nd
Activ
ityP
aram
eter
.Met
aId
are
map
ped
as a
list
to th
e su
perio
r sy
stem
onl
y. I.
e.:
Activ
ityP
aram
eter
.Sub
Sys
tem
Id
Activ
ityP
aram
eter
.tTyp
e Ac
tivity
Par
amet
er.tV
alue
Ac
tivity
Par
amet
er.V
alue
Min
Ac
tivity
Par
amet
er.V
alue
Max
Ac
tivity
Par
amet
er.S
tand
ardD
ev
Activ
ityP
aram
eter
.Uni
t An
d th
e po
st in
QM
etaD
ata
refe
rred
by
Act
ivity
Par
amet
er.M
etaI
d. i.
e:
QM
etaD
ata.
Dat
aTyp
e Q
Met
aDat
a.M
etho
d Q
Met
aDat
a.D
ateC
onci
eved
Q
Met
aDat
a.Li
ttera
ture
Ref
Q
Met
aDat
a.N
otes
Obj
ectO
fStu
dy.F
unct
ion
(list
) (a
ppen
d)
FT
U
O
K Fl
owC
onne
ctio
n an
d A
ctiv
ityPa
ram
eter
ar
e no
t use
d in
any
cur
rent
ly k
now
n im
plem
enta
tion
of S
PIN
E.
1.1.
6.6.
2 N
ame
of v
aria
ble
MV
U
-
Obj
ectO
fStu
dy.F
unct
ion
(list
) (a
ppen
d)
FT
1
The
SP
INE
form
at d
oes
not p
rovi
de
supp
ort f
or u
nam
bigu
ousl
y co
nnec
ting
a na
me
of v
aria
ble
with
val
ue o
f var
iabl
e,
why
this
con
stru
ctio
n w
ill n
ot b
e us
ed.
1.1.
6.6.
3 Va
lue
of v
aria
ble
R
U
-
Obj
ectO
fStu
dy.F
unct
ion
(list
) (a
ppen
d)
FT
1
The
SP
INE
form
at d
oes
not p
rovi
de
supp
ort f
or u
nam
bigu
ousl
y co
nnec
ting
a na
me
of v
aria
ble
with
val
ue o
f var
iabl
e,
why
this
con
stru
ctio
n w
ill n
ot b
e us
ed.
9
1.
1.7
Valid
tim
e sp
an
1
1
OK
1.
1.7.
1 St
art d
ate
DF
1
- In
vent
ory.
Tim
eBou
ndar
y (a
ppen
d)
FT
1
Dat
a ty
pe m
ism
atch
- re
fere
nce
to o
ther
fie
ld n
ot p
ossi
ble
1.1.
7.2
End
date
D
F
1 -
Inve
ntor
y.Ti
meB
ound
ary
(app
end)
FT
1 D
ata
type
mis
mat
ch -
refe
renc
e to
oth
er
field
not
pos
sibl
e 1.
1.7.
3 Ti
me-
span
de
scrip
tion
FT
1
Inve
ntor
y.Ti
meB
ound
ary
Inve
ntor
y.Ti
meB
ound
ary
(app
end)
FT
1 O
K
1.1.
8 Va
lid g
eogr
aphy
1
1 O
K 1.
1.8.
1 Ar
ea n
ame
ST
I U
"S
ee p
roce
ss.p
roce
ss_d
escr
iptio
n.
valid
_geo
grap
hy. A
rea_
desc
riptio
n"
Inve
ntor
y.G
eogr
aphi
calB
ound
ary
(list
) (ap
pend
) FT
1 O
K
1.1.
8.2
Area
des
crip
tion
FT
1
Inve
ntor
y.G
eogr
aphi
calB
ound
ary
Inve
ntor
y.G
eogr
aphi
calB
ound
ary
(app
end)
FT
1 O
K
1.1.
8.3
Site
s S
T
U
Jurid
ical
Per
son
(all
field
s) re
ferre
d by
O
bjec
tOfS
tudy
.Site
In
vent
ory.
Geo
grap
hica
lBou
ndar
y (li
st) (
appe
nd)
FT
1
OK
1.1.
8.4
GIS
refe
renc
e L
I U
"S
ee
proc
ess.
proc
ess_
desc
riptio
n.va
lid_g
eogr
aphy
. Are
a_de
scrip
tion"
Inve
ntor
y.G
eogr
aphi
calB
ound
ary
(list
) (ap
pend
) FT
1 O
K
1.1.
9 D
ata
acqu
isiti
on
1
OK
. See
als
o 1.
2.14
Doc
umen
tatio
n 1.
1.9.
1 Sa
mpl
ing
proc
edur
e FT
1 "S
ee p
roce
ss.in
puts
_and
_out
puts
.d
ocum
enta
tion.
data
_tre
atm
ent"
Gen
eral
QM
etaD
ata.
Met
hod
(app
end)
FT
1 O
K
1.1.
9.2
Sam
plin
g si
tes
ST
U
-
Gen
eral
QM
etaD
ata.
Met
hod
(list
) (a
ppen
d)
FT
1
OK
1.1.
9.3
Num
ber o
f site
s R
1 -
Gen
eral
QM
etaD
ata.
Met
hod
(app
end)
FT
1 O
K
1.1.
9.4
Sam
ple
volu
me
1
OK
1.1.
9.4.
1 Ab
solu
te
ST
1
- G
ener
al Q
Met
aDat
a.M
etho
d (a
ppen
d)
FT
1
OK
1.1.
9.4.
2 R
elat
ive
R
1
- G
ener
al Q
Met
aDat
a.M
etho
d (a
ppen
d)
FT
1
OK
1.
2 In
puts
and
ou
tput
s
U
U
O
K
1.2.
1 Id
entif
icat
ion
num
ber
Int
1
Flow
.Flo
wN
umbe
r Fl
ow.F
low
Num
ber
Int
1
OK
1.2.
2 D
irect
ion
Dir
X
1 Fl
ow.S
ubTy
pe
- nom
encl
atur
e tra
nsla
tion
to m
atch
IS
O/T
S 1
4048
Flow
.Sub
Type
- a
dd p
ost w
ith th
e va
lue
"Sta
te" t
o Fl
ow.S
ubTy
pe n
omen
clat
ure
corre
spon
ding
to "N
on-fl
ow-r
elat
ed
aspe
cts"
in D
irect
ion
nom
encl
atur
e
6 X
1
OK
1.2.
3 G
roup
L
I 1
Flow
.Cat
egor
y
Flow
.Cat
egor
y
- add
pos
t to
Flow
Type
.Cat
egor
y no
men
clat
ure
if no
t pre
sent
20
X
1 O
K
1.2.
4 R
ecei
ving
en
viro
nmen
t L
X
1 Fl
ow.Im
pact
Med
ia (w
here
sup
erio
r =
Glo
bal),
NU
LL if
Flo
w.Im
pact
Med
ia =
"O
ther
"
Flow
.Impa
ctM
edia
if R
ecei
ving
en
viro
nmen
t spe
cific
atio
n is
em
pty
60
X
1 O
K
1.2.
5 R
ecei
ving
en
viro
nmen
t sp
ecifi
catio
n
L I
1 Fl
ow.Im
pact
Med
ia
Flow
.Impa
ctM
edia
Ad
d po
st to
Env
ironm
ent i
f not
pr
esen
t in
nom
encl
atur
e
60
I 1
OK
10
1.2.
6 En
viro
nmen
t co
nditi
on
FT
1
Envi
ronm
ent.N
otes
"M
ore
info
rmat
ion
may
be
foun
d in
m
odel
ling_
and_
valid
atio
n.m
odel
ling_
ch
oice
s.cr
iteria
_for
_exc
ludi
ng_
elem
enta
ry_f
low
s"
Inve
ntor
y.N
atur
eBou
ndar
y (li
st)
(app
end)
FT
1 O
K. I
nven
tory
.Nat
ureB
ound
ary
refe
rs to
Ac
tivity
1.2.
7 G
eogr
aphi
cal
loca
tion
ST
1
Geo
grap
hy.A
reaN
ame
incl
udin
g th
e fu
ll hi
erar
chic
al n
omen
clat
ure
path
G
eogr
aphy
.Are
aTyp
e G
eogr
aphy
.Not
es
refe
rred
by
Flow
.Impa
ctR
egio
n
Geo
grap
hy.A
reaN
ame
refe
rred
by
Flow
.Impa
ctR
egio
n
Add
post
to G
eogr
aphy
if n
ot
pres
ent i
n no
men
clat
ure
255
X
1 O
K. T
he G
eogr
aphy
.Are
aNam
e fie
ld
data
type
def
initi
on is
cha
nged
from
va
rcha
r(40)
to v
arch
ar(2
55)
1.2.
8 R
elat
ed e
xter
nal
syst
em
1
1
OK
1.2.
8.1
Orig
in o
r de
stin
atio
n S
T
1 "S
ee
inpu
ts_a
nd_o
utpu
ts.d
ocum
enta
tion
.dat
a_tre
atm
ent"
Spec
ific
QM
etaD
ata.
Not
es
FT
1
OK
1.2.
8.2
Tran
spor
t typ
e S
T
1 "S
ee p
roce
ss.in
puts
_and
_out
puts
. do
cum
enta
tion.
data
_tre
atm
ent"
Spec
ific
QM
etaD
ata.
Not
es
FT
1
OK
1.2.
8.3
Info
rmat
ion
refe
renc
e S
T
1 "S
ee p
roce
ss.in
puts
_and
_out
puts
. do
cum
enta
tion.
data
_tre
atm
ent"
Spec
ific
QM
etaD
ata.
Not
es
FT
1
OK
1.2.
9 In
tern
al lo
catio
n FT
1 "S
ee p
roce
ss.in
puts
_and
_out
puts
. do
cum
enta
tion.
data
_tre
atm
ent"
Spec
ific
QM
etaD
ata.
Not
es
FT
1
OK
1.2.
10
Nam
e
1
1 O
K 1.
2.10
.1
Nam
e te
xt
L R
1
Subs
tanc
e.D
efau
ltNam
e re
ferr
ed b
y Fl
ow.S
ubst
ance
Id
Subs
tanc
e.D
efau
ltNam
e re
ferr
ed
by F
low
.Sub
stan
ceId
Ad
d po
st to
Sub
stan
ce if
not
pr
esen
t in
nom
encl
atur
e
150
U
1 O
K. T
he S
ubst
ance
.Def
aultN
ame
field
da
ta ty
pe d
efin
ition
is c
hang
ed fr
om
varc
har(4
0) to
var
char
(150
) in
SPI
NE
1.2.
10.2
R
efer
ence
to
nom
encl
atur
e S
T I
1 "S
PIN
E@
CP
M19
97S
ubst
ance
" Su
bsta
nce.
Not
es re
ferr
ed b
y Fl
ow.S
ubst
ance
Id (a
ppen
d)
FT
1
OK
. SP
INE
is d
esig
ned
for o
ne s
ingl
e su
bsta
nce
nom
encl
atur
e, IS
O/T
S fo
r an
unlim
ited
num
ber o
f sub
stan
ce
nom
encl
atur
es.
1.
2.10
.3
Spec
ifica
tion
of
nam
e S
T
1 Su
bsta
nce.
Not
es re
ferr
ed b
y Fl
ow.S
ubst
ance
Id
Subs
tanc
e.N
otes
refe
rred
by
Flow
.Sub
stan
ceId
FT
1
OK
. Not
es m
ay c
onta
in a
ny re
leva
nt
data
for t
he s
ubst
ance
.
1.2.
11
Prop
erty
U
U
C
once
ptua
lly O
K 1.
2.11
.1
Nam
e L
1
Flow
Pro
perty
.tTyp
e Fl
owP
rope
rty.tT
ype
Add
post
to P
rope
rtyTy
pe if
not
pr
esen
t Pr
oper
tyTy
pe.C
ateg
ory
= "im
porte
d fro
m IS
O/T
S 1
4048
"
40
1
OK
1.2.
11.2
U
nit
L Y
1 Fl
owP
rope
rty.U
nit
Flow
Pro
perty
.Uni
t 10
1 O
K
1.2.
11.3
A
mou
nt
R
1
Flow
Pro
perty
.Qua
ntity
Fl
owP
rope
rty.Q
uant
ity
40
1
Poss
ible
dat
a lo
ss o
f "Fl
owP
rope
rty
.Qua
ntity
Min
", "F
low
Prop
erty
.Q
uant
ityM
ax” a
nd "F
low
Prop
erty
.S
tand
ardD
ev"
Dat
a ty
pe m
ism
atch
: im
poss
ible
to m
ap
non-
num
eric
val
ues,
suc
h as
"YE
S",
"NO
", "r
ed",
"rec
ycla
ble"
etc
.
11
1.2.
12
Am
ount
U
Impo
rt is
onl
y ap
plic
able
if o
ne o
r mor
e of
the
SPIN
E p
aram
eter
nam
es
"Qua
ntity
", "Q
uant
ityM
in",
"Qua
ntity
Max
an
d "S
tand
ardD
ev" c
an b
e id
entif
ied
in
the
ISO
/TS
140
48 d
ata
set.
The
iden
tific
atio
n m
ust b
e do
ne b
y th
e im
porte
r. 1.
2.12
.1
Nam
e L
I 1
"SPI
NE
95Q
uant
ity"
N/A
-
- -
Dat
a lo
ss
1.2.
12.2
U
nit
1
OK
1.2.
12.2
.1
Sym
bol o
r nam
e L
I 1
Flow
.Uni
t Fl
ow.U
nit
Add
post
to U
nit n
omen
clat
ure
if no
t pre
sent
10
1
OK
1.2.
12.2
.2
Expl
anat
ion
ST
1
Uni
t.Not
es
Uni
t.Not
es (a
dd N
otes
col
umn
to
Uni
t tab
le if
not
pre
sent
) FT
1 O
K
1.2.
12.3
Pa
ram
eter
U
4
Poss
ible
dat
a lo
ss
1.2.
12.3
.1
Nam
e L
I 1
"Qua
ntity
" or "
Qua
ntity
Min
" or
"Qua
ntity
Max
or "
Sta
ndar
dDev
" N
/A
- I
1 Po
ssib
le d
ata
loss
1.2.
12.3
.2
Valu
e R
1 Fl
ow.Q
uant
ity o
r Flo
w.Q
uant
ityM
in o
r Fl
ow.Q
uant
ityM
ax o
r Fl
ow.S
tand
ardD
ev re
spec
tivel
y
Flow
.Qua
ntity
or F
low
.Qua
ntity
Min
or
Flo
w.Q
uant
ityM
ax o
r Fl
ow.S
tand
ardD
ev re
spec
tivel
y
if on
e or
mor
e of
the
corre
spon
ding
par
amet
ers
can
be
iden
tifie
d by
the
impo
rter i
n th
e IS
O/T
S 1
4048
dat
a se
t
255
1
Poss
ible
dat
a lo
ss
1.2.
13
Mat
hem
atic
al
rela
tions
1
O
K
1.2.
13.1
Fo
rmul
ae
MR
U
"See
pro
cess
.pro
cess
_des
crip
tion.
te
chno
logy
.tech
nica
l_co
nten
t _a
nd_f
unct
iona
lity"
Obj
ectO
fStu
dy.F
unct
ion
(as
a lis
t) FT
1 O
K
1.2.
13.2
N
ame
of v
aria
ble
MV
U
-
Obj
ectO
fStu
dy.F
unct
ion
(as
a lis
t) FT
1 O
K
1.2.
13.3
Va
lue
of v
aria
ble
R
U
-
Obj
ectO
fStu
dy.F
unct
ion
(as
a lis
t) FT
1 O
K
1.2.
14
Doc
umen
tatio
n
U
2
OK
. One
allo
wed
occ
urre
nce
per F
low
, an
d on
e pe
r Act
ivity
1.
2.14
.1
Dat
a co
llect
ion
L
1 Q
Met
aDat
a.D
ataT
ype
QM
etaD
ata.
Dat
aTyp
e
Add
post
to
QM
etaD
ataT
ype.
Nam
e no
men
clat
ure
if no
t pre
sent
100
U
1 O
K
1.2.
14.2
C
olle
ctio
n da
te
DI
1
Qm
etaD
ata.
Dat
eCon
ceiv
ed
QM
etaD
ata.
Dat
eCon
ceiv
ed
23
1
OK
1.
2.14
.3
Dat
a tre
atm
ent
FT
1
QM
etaD
ata.
Met
hod
QM
etaD
ata.
Not
es
QM
etaD
ata.
Rep
rese
nts
List
of P
rope
rtyTy
pe.N
otes
QM
etaD
ata.
Met
hod
FT
1 O
K. S
ee a
lso
1.1.
9 D
ata
acqu
isiti
on fo
r ge
nera
l QM
etaD
ata
1.2.
14.4
R
efer
ence
to d
ata
sour
ce
ST
U
Q
Met
aDat
a.Li
ttera
ture
Ref
Q
Met
aDat
a.Li
ttera
ture
Ref
(lis
t) FT
1 Q
Met
aDat
a.Li
ttera
ture
Ref
may
con
tain
m
ore
than
1 re
fere
nce
in th
e sa
me
field
12
2
Mod
ellin
g an
d va
lidat
ion
1
1
OK
. The
sys
tem
mod
elle
r and
sys
tem
va
lue
are
both
des
crib
ed in
the
mod
ellin
g an
d va
lidat
ion.
Cor
resp
onds
in
gen
eral
to p
arts
of I
nven
tory
. 2.
1 In
tend
ed
appl
icat
ion
FT
1
Inve
ntor
y.In
tend
edU
ser
Inve
ntor
y.G
ener
alP
urpo
se
Inve
ntor
y.D
etai
ledP
urpo
se
Inve
ntor
y.D
etai
ledP
urpo
se
FT
1
OK
2.2
Info
rmat
ion
sour
ces
ST
U
in
vent
ory.
Publ
icat
ion
Inve
ntor
y.D
ata
(list
) (ap
pend
) FT
1 O
K. C
onte
xt d
ata
not s
uppo
rted
in
ISO
/TS
1404
8 w
hy in
form
atio
n so
urce
s pr
efer
ably
are
doc
umen
ted
dire
ctly
in
rela
tion
to th
eir c
orre
spon
ding
dat
a va
lue.
Any
add
ition
al in
form
atio
n so
urce
re
fere
nces
may
app
ear i
n th
e In
vent
ory.
Dat
a fie
ld, b
ut th
is is
not
an
exte
nsiv
e lis
t. 2.
3 M
odel
ling
prin
cipl
es
1
1
OK
2.3.
1 D
ata
sele
ctio
n pr
inci
ple
FT
1
"See
m
odel
ling_
and_
valid
atio
n.ot
her.i
nfor
mat
ion"
Inve
ntor
y.D
ata
(app
end)
FT
1 O
K
2.3.
2 Ad
apta
tion
prin
cipl
es
FT
1
"See
m
odel
ling_
and_
valid
atio
n.ot
her.i
nfor
mat
ion"
Inve
ntor
y.D
ata
(app
end)
FT
1 O
K
2.3.
3 M
odel
ling
cons
tant
s
U
OK
2.3.
3.1
Nam
e S
T I
1 "S
ee p
roce
ss.p
roce
ss_d
escr
iptio
n.
tech
nolo
gy.te
chni
cal_
cont
ent
_and
_fun
ctio
nalit
y"
Obj
ectO
fStu
dy.F
unct
ion
(app
end)
FT
1 O
K
2.3.
3.2
Valu
e R
1 -
Obj
ectO
fStu
dy.F
unct
ion
(app
end)
FT
1 O
K
2.4
Mod
ellin
g ch
oice
s
1
1 O
K 2.
4.1
Crit
eria
for
excl
udin
g el
emen
tary
flow
s
FT
1
Inve
ntor
y.N
atur
eBou
ndar
y In
vent
ory.
Nat
ureB
ound
ary
(app
end)
FT
1 O
K
2.4.
2 C
riter
ia fo
r ex
clud
ing
inte
rmed
iate
pr
oduc
t flo
ws
FT
1
Inve
ntor
y.O
ther
Bou
ndar
ies
Inve
ntor
y.O
ther
Bou
ndar
ies
(app
end)
FT
1 O
K
2.4.
3 C
riter
ia fo
r ex
tern
aliz
ing
proc
esse
s
FT
1
"See
mod
ellin
g_an
d_va
lidat
ion.
m
odel
ling_
choi
ces.
crite
ria_f
or_
excl
udin
g_in
term
edia
te_
prod
uct_
flow
s"
Inve
ntor
y.O
ther
Bou
ndar
ies
(app
end)
FT
1 O
K
2.4.
4 Al
loca
tions
pe
rform
ed
1
1
OK
2.4.
4.1
Allo
cate
d co
-pr
oduc
ts
ST
1
"See
m
odel
ling_
and_
valid
atio
n.al
loca
tions
_per
form
ed.a
lloca
tion_
expl
anat
ion"
Inve
ntor
y.Al
loca
tions
(app
end)
FT
1 O
K
2.4.
4.2
Allo
catio
n ex
plan
atio
n FT
1 In
vent
ory.
Allo
catio
ns
Inve
ntor
y.Al
loca
tions
(app
end)
FT
1 O
K
13
2.
4.5
Proc
ess
expa
nsio
n
1
1 O
K 2.
4.5.
1 Pr
oces
s in
clud
ed in
ex
pans
ion
ST
1
"See
mod
ellin
g_an
d_va
lidat
ion.
pr
oces
s_ex
pans
ion.
proc
ess_
ex
pans
ion_
expl
anat
ion"
Inve
ntor
y.La
tera
lExp
ansi
on
FT
1
OK
2.4.
5.2
Proc
ess
expa
nsio
n ex
plan
atio
n FT
1 In
vent
ory.
Late
ralE
xpan
sion
In
vent
ory.
Late
ralE
xpan
sion
FT
1 O
K
2.5
Dat
a qu
ality
st
atem
ent
FT
1
"See
mod
ellin
g_an
d_va
lidat
ion.
ot
her_
info
rmat
ion"
In
vent
ory.
Dat
a (a
ppen
d)
FT
1 O
K
2.6
Valid
atio
n
U
1
OK
2.6.
1 M
etho
d FT
I
1 "S
ee m
odel
ling_
and_
valid
atio
n.
othe
r_in
form
atio
n"
Inve
ntor
y.D
ata
(list
) (ap
pend
)
FT
1
OK
The
nom
encl
atur
e ca
n be
dis
rega
rded
w
ith th
e m
otiv
atio
n th
at:
1. A
free
-text
type
d da
ta fi
eld
is n
ot
suita
ble
to a
ct w
ithin
a fo
reig
n ke
y co
nstru
ctio
n in
a re
latio
nal d
atab
ase
2. It
ser
ves
no u
rgen
t pur
pose
2.
6.2
Proc
edur
e FT
1 "S
ee m
odel
ling_
and_
valid
atio
n.
othe
r_in
form
atio
n"
Inve
ntor
y.D
ata
(list
) (ap
pend
)
FT
1
OK
2.6.
3 R
esul
t FT
1 "S
ee
mod
ellin
g_an
d_va
lidat
ion.
othe
r.inf
orm
atio
n"
Inve
ntor
y.D
ata
(list
) (ap
pend
)
FT
1
OK
2.6.
4 Va
lidat
or
ST
1
Jurid
ical
Per
son
(all
field
s) re
ferr
ed
by In
vent
ory.
Rev
iew
er
Inve
ntor
y.D
ata
(list
) (ap
pend
) FT
1 O
K. S
PIN
E c
an o
nly
refe
r to
one
Rev
iew
er
2.7
Oth
er in
form
atio
n FT
1 In
vent
ory.
Dat
a In
vent
ory.
Not
es
Inve
ntor
y.A
pplic
abili
ty
Inve
ntor
y.N
otes
(app
end)
FT
1 O
K
14
3
Adm
inis
trat
ive
info
rmat
ion
1
OK
3.1
Iden
tific
atio
n nu
mbe
r L
1
Obj
ectO
fStu
dy.Id
& A
ctiv
ity.Id
In
vent
ory.
Not
es (a
ppen
d)
New
Obj
ectO
fStu
dy.Id
and
Ac
tivity
.Id a
re c
reat
ed u
pon
impo
rt to
SP
INE
FT
1
OK
. Orig
inal
dat
a se
t ide
ntifi
er is
sto
red
for t
rans
pare
ncy
whe
n m
appi
ng to
S
PIN
E. D
ata
conv
ersi
on a
lway
s im
plie
s da
ta d
isto
rtion
and
hen
ce th
e da
ta s
et is
di
ffere
nt a
fter c
onve
rsio
n. A
new
dat
a se
t ide
ntifi
er is
hen
ce c
reat
ed u
pon
conv
ersi
on.
3.2
Reg
istra
tion
auth
ority
L
1
"CP
M (C
ente
r for
Env
ironm
enta
l As
sess
men
t of P
rodu
ct a
nd M
ater
ial
Sys
tem
s), C
halm
ers
Uni
vers
ity o
f Te
chno
logy
, Göt
ebor
g, S
wed
en"
Inve
ntor
y.N
otes
(app
end)
FT
1
OK
3.3
Vers
ion
num
ber
Int
1
1 In
vent
ory.
Not
es (a
ppen
d)
FT
- O
K. D
ata
publ
ishe
d in
SPI
NE
@C
PM
ra
rely
cha
nge,
why
no
expl
icit
vers
ion
cont
rol i
s de
fined
with
in S
PIN
E@
CP
M.
3.4
Dat
a co
mm
issi
oner
S
T
1 Ju
ridic
alP
erso
n re
ferr
ed b
y In
vent
ory.
Com
mis
sion
er
Jurid
ical
Per
son.
Mai
lAdd
ress
re
ferr
ed b
y In
vent
ory.
Com
mis
sion
er
200
U
1 O
K
3.5
Dat
a ge
nera
tor
ST
1
Jurid
ical
Per
son
refe
rred
by
Inve
ntor
y.P
ract
ition
er
Jurid
ical
Per
son.
Mai
lAdd
ress
re
ferr
ed b
y In
vent
ory.
Pra
ctiti
oner
20
0 U
1
OK
3.6
Dat
a do
cum
ento
r S
T
1 "S
ee m
odel
ling_
and_
valid
atio
n.
info
rmat
ion_
sour
ces"
In
vent
ory.
Pub
licat
ion
(als
o pu
blic
atio
n) (a
ppen
d)
FT
1
OK
3.7
Dat
e co
mpl
eted
D
F
1 In
vent
ory.
Dat
eCom
plet
ed
Inve
ntor
y.D
ateC
ompl
eted
10
1 O
K
3.8
Publ
icat
ion
ST
1
"See
mod
ellin
g_an
d_va
lidat
ion.
in
form
atio
n_so
urce
s"
Inve
ntor
y.P
ublic
atio
n (a
lso
data
_doc
umen
tor)
(app
end)
FT
1 O
K
3.9
Cop
yrig
ht
ST
1
Inve
ntor
y.C
opyr
ight
In
vent
ory.
Cop
yrig
ht
60
1
OK
3.
10
Acce
ss re
stric
tions
S
T
1 In
vent
ory.
Avai
labi
lity
Inve
ntor
y.Av
aila
bilit
y 25
5
1 O
K
Appendix A. Mapping of nomenclatures This chapter describes the specific mapping rules applied to attributes that have a corresponding nomenclature. Specific attention must be taken towards ISO/TS 14048 exclusive nomenclatures and nomenclaturised attributes in SPINE that are required in order to be compatible with SPINE@CPM information system.
A.1 Exclusive nomenclatures aggregation_type referring to the attribute data_documentation_of_process.process.process_description.aggregation_type Corresponding SPINE nomenclature:
This attribute does not exist explicitly in SPINE Mapping:
data_documentation_of_process.process.process_description.aggregation_type is mapped to the Inventory.Data field in SPINE. Since the aggregation is rarely done in one single dimension it may be confusing to interpret this attribute why it is not found to be a problem to leave the aggregation_type nomenclature out from the mapping.
direction referring to the attribute data_documentation_of_process.process.inputs_and_outputs.direction Corresponding SPINE nomenclature:
FlowType.Type referring to the attribute Flow.SubType FlowType.Type differs slightly from direction. The value: "Non-flow-related aspects" is missing in FlowType.Type.
Mapping:
data_documentation_of_process.process.inputs_and_outputs.direction is mapped 1 to 1 to the the Flow.SubType field. The name “State” is added to the FlowType.Type nomenclature and then mapped to “Non-flow-related aspects”. The reason that “State” and not “Non-flow-related aspects” is added to the FlowType.Type nomenclature is that there is a field length limitation of 6 characters in the current data model.
16
receiving_environment referring to the attribute: data_documentation_of_process.process.inputs_and_outputs.receiving_environment Corresponding SPINE nomenclature:
Environment.Name where the attribute Environment.Superior name equals to "Global"; referred by the attribute Flow.ImpactMedia. The reference may be indirect by the hierarchical structure of the Environment table1. Environment differs slightly from recieving_environment. The name "Other" is present in Environment.Name where the Environment.Superior is "Global".
Mapping:
data_documentation_of_process.process.inputs_and_outputs.receiving_environment is mapped 1 to 1 to the the Flow.ImpactMedia field via the hierarchical structure of the Environment table. If the Environment.Name is the value "Other" then NULL is mapped from SPINE to ISO/TS 14048, and the explanation is mapped to the data_documentation_of_process.process.inputs_and_outputs. receiving_environment_specification attribute.
A.2 Inclusive nomenclatures quantitative_reference.type referring to the attribute: data_documentation_of_process.process.process_description.quantitative_reference.type Corresponding SPINE nomenclature: The attribute and concept differs substantially between the formats Mapping: All attributes describing the data_documentation_of_process.process.process_description.quantitative_reference including data_documentation_of_process.process.process_description .quantitative_reference.type are appended to ObjectOfStudy.Function. technical_scope referring to the data field: data_documentation_of_process.process.process_description.technical_scope Corresponding SPINE nomenclature:
ProcessType.Category referring to the attribute ObjectOfStudy.Category ProcessType.Category differs slightly from technical_scope. ProcessType.Category contains more than the recommended names for technical_scope.
1 Compare to the nomenclature receiving_environment_specification
17
Mapping: data_documentation_of_process.process.process_description.technical_scope is mapped 1 to 1 to the ObjectOfStudy.Category. If a value is not present in the target nomenclature it is added when performing the mapping.
area_name referring to the attribute: data_documentation_of_process.process.process_description.valid_geography.area_name Corresponding SPINE nomenclature: The attribute and concept differs substantially between the formats Mapping:
ISO/TS 14048 to SPINE: data_documentation_of_process.process.process_description.valid_geography
.area_name is appended as a list to Inventory.GeographicalBoundary SPINE to ISO/TS 14048:
Inventory.GeographicalBoundary is mapped to data_documentation_of_process .process.process_description.valid_geography.area_description GIS_reference referring to the attribute: data_documentation_of_process.process.process_description.valid_geography.gis_reference Corresponding SPINE nomenclature: The attribute and concept differs substantially between the formats Mapping:
ISO/TS 14048 to SPINE: data_documentation_of_process.process.process_description.valid_geography .gis_reference is appended as a list to Inventory.GeographicalBoundary SPINE to ISO/TS 14048: Inventory.GeographicalBoundary is mapped to data_documentation_of_process .process.process_description.valid_geography.area_description
group referring to the attribute: data_documentation_of_process.process.inputs_and_outputs.group Corresponding SPINE nomenclature: FlowType.Category referring to the attribute Flow.Category. FlowType.Category differs slightly from group. Mapping:
data_documentation_of_process.process.inputs_and_outputs.group is mapped 1 to 1 to Flow.Category. If the value is not present in the target nomenclature, it is added when performing the mapping.
18
receiving_environment_specification referring to the attribute: data_documentation_of_process.process.inputs_and_outputs.receiving_environment _specification Corresponding SPINE nomenclature:
Environment.Name referred by the attribute Flow.ImpactMedia 2. Environment.Name differs slightly from recieving_environment_specification.
Mapping:
SPINE to ISO/TS 14048: data_documentation_of_process.process.inputs_and_outputs.receiving_environment_ specification attribute is mapped to the Flow.ImpactMedia attribute if not empty. If empty it is not mapped. ISO/TS 14048 to SPINE: If a data set contains a post in inputs_and_outputs with a receiving_environment_specification name that is not specified in the Environment.Name table, the missing name is added to the Environment.Name nomenclature with the Environment.Superior field as the receiving_environment.
name.reference_to_nomenclature referring to the attribute: inputs_and_outputs.name.reference_to_nomenclature Corresponding SPINE nomenclature: None Mapping:
The idea to have a nomenclature for nomenclatures is useful, but requires a worldwide administration to define the valid names. Until that happens the inputs_and_outputs.name.reference_to_nomenclature is mapped to Substance.Notes. The name of the SPINE@CPM substance nomenclature: "SPINE@CPM1997Substance" is mapped to inputs_and_outputs.name.reference_to_nomenclature.
2 Compare to the nomenclature receiving_environment
19
amount.name referring to the attribute: data_documentation_of_process.process.inputs_and_outputs.amount.name Corresponding SPINE nomenclature: The attribute and concept of differs between the formats Mapping: The name of the amount from SPINE is always "SPINE95Quantity". Import to SPINE is only applicable if one or more of the SPINE parameter names "Quantity", "QuantityMin", "QuantityMax and "StandardDev" can be identified in the ISO/TS 14048 data set. The identification should be done by the importer. parameter.name referring to the attribute: data_documentation_of_process.process.inputs_and_outputs.amount.parameter.name Corresponding SPINE nomenclature: The quantitative attributes of the table Flow; namely: Flow.Quantity, Flow.QuantityMin, Flow.QuantityMax, Flow.StandardDev. Mapping:
SPINE to ISO/TS 14048: The name of the parameters from SPINE is always "Quantity", "QuantityMin", "QuantityMax", and "StandardDev". Attributes that doesn't contain any data are not converted. ISO/TS 14048 to SPINE: Import to SPINE is only applicable if one or more of the SPINE parameter names "Quantity", "QuantityMin", "QuantityMax and "StandardDev" can be identified in the ISO/TS 14048 data set. The identification should be done by the importer. If others than these parameters are found these will not be imported and will hence be lost upon conversion.
unit.symbol_or_name referring to the attributes: data_documentation_of_process.process.inputs_and_outputs.property.unit data_documentation_of_process.process.inputs_and_outputs.unit.symbol_or_name data_documentation_of_process.process.process_description.quantitative_reference.unit Corresponding SPINE nomenclature: Unit.Name referred by the attribute Flow.Unit, FlowProperty.Unit, Substance.DefaultUnit, SubstanceProperty.Unit, and ActivityParameterType.Unit
20
Mapping: data_documentation_of_process.process.inputs_and_outputs.property.unit and data_documentation_of_process.process.inputs_and_outputs.unit.symbol_or_name are mapped to FlowProperty.Unit and Flow.Unit respectively. Any value appearing in the data field in the data_documentation_of_process.process.inputs_and_outputs.property and/or data_documentation_of_process.process.inputs_and_outputs.unit.symbol_or_name attribute is added to the corresponding Unit.Name nomenclature if not already present. data_documentation_of_process.process.process_description.quantitative_reference.unit is mapped to ObjectOfStudy.Function , see quantitative_reference.type. When mapping from SPINE to ISO/TS 14048, ObjectOfStudy.Function is mapped to data_documentation_of_process.process .process_description_technical_content_and_functionality
modelling_constants.name referring to the attribute: data_documentation_of_process.modelling_and_validation.modelling_principles.modelling _constants.name Corresponding SPINE nomenclature: This attribute does not exist in SPINE Mapping:
ISO/TS 14048 to SPINE: All attributes in data_documentation_of_process.modelling_and_validation .modelling_principles.modelling_constants including data_documentation_of_process .modelling_and_validation.modelling_principles.modelling_constants.name are appended as a list to ObjectOfStudy.Function. SPINE to ISO/TS 14048: ObjectOfStudy.Function is mapped to data_documentation_of_process.process .process_description_technical_content_and_functionality
method referring to the attribute: data_documentation_of_process.modelling_and_validation.validation.method Corresponding SPINE nomenclature: This attribute does not exist in SPINE Mapping:
ISO/TS 14048 to SPINE: All attributes in data_documentation_of_process.modelling_and_validation.validation including data_documentation_of_process.modelling_and_validation.validation.method are appended as a list to Inventory.Data. SPINE to ISO/TS 14048:
Inventory.Data is mapped to data_documentation_of_process.modelling_and _validation.other_information
21
A.3 SPINE nomenclature, including user defined nomenclature
A.3.1 Nomenclatures related to mandatory attributes in SPINE The attributes referring to the nomenclatures in this chapter are required for the data set to be compatible with the SPINE@CPM information system. ActivitySubtype.Name ActivitySubtype.Name relates to the attributes ObjectOfStudy.ActivityType and Activity.Subtype. Corresponding ISO/TS 14048 nomenclature: None (i.e ActivitySubtype.Name is a user defined nomenclature) Mapping: ObjectOfStudy.ActivityType is mapped to data_documentation_of_process.process.process_description.technology.short _technology_descriptor. When converting from ISO/TS 14048 to SPINE the importer must provide the information for the ObjectOfStudy.ActivityType, as "Process" or "Transport". FlowType.Type See chapter A.1 - direction FlowType.Category See chapter A.2 - group Environment.Name See chapter A.2 - receiving_environment_specification Geography Geography.AreaName relates to the attribute Flow.ImpactRegion Corresponding ISO/TS 14048 nomenclature: None (i.e Geography.AreaName is a user defined nomenclature) Mapping: Geography.AreaName including the full hierarchical path, Geography.AreaType, Geography.Notes, referred by Flow.ImpactRegion is mapped to data_documentation_of_process.process.inputs_and_outputs.geographical_location Any value appearing in the data field in the data_documentation_of_process.process.inputs_and_outputs.geographical_location attribute is added to the corresponding Geography.AreaName nomenclature if not already present.
22
Substance Substance.DefaultName relates via Substance.Id to the attribute Flow.SubstanceId Corresponding ISO/TS 14048 nomenclature: The nomenclature from which the inputs_and_outputs.name.name_text is collected is stated in the inputs_and_outputs.name.reference_to_nomenclature field. (The inputs_and_outputs.name.reference_to_nomenclature is itself defined in ISO/TS 14048 as having a nomenclature, but this will not influence the mapping unless a routine of how to treat this nomenclature is agreed upon worldwide). Mapping: Substance.DefaultName is mapped to data_documentation_of_process.process.inputs_and_outputs.name.name_text where the data_documentation_of_process.process.inputs_and_outputs.name.reference_ to_nomenclature is always "SPINE@CPM1997Substance". Any value appearing in the data field in the data_documentation_of_process.process.inputs_and_outputs.name.name_text attribute is added to the corresponding Substance.DefaultName nomenclature if not already present. data_documentation_of_process.process.inputs_and_outputs.name. reference_to_nomenclature and data_documentation_of_process.process.inputs_and _outputs.name.reference_to_nomenclature are both mapped to Substance.Notes. Unit.Name See chapter A.2 - unit.symbol_or_name
23
A.3.2 Nomenclatures related to optional attributes in SPINE JuridicalPerson JuridicalPerson relates to the attributes ObjectOfStudy.Site, ObjectOfStudy.Owner, Inventory.Practitioner, Inventory.Reviewer, and Inventory.Commissioner. Corresponding ISO/TS 14048 nomenclature: None (i.e JuridicalPerson is a user defined nomenclature) Mapping: When exporting from SPINE@CPM via ISO/TS 14048 all the fields in one record in the JuridicalPerson table will be concatenated into the corresponding ISO/TS 14048 attributes. Inventory.Practitioner is mapped 1 to 1 to data_documentation_of_process.administrative_information.data_generator Inventory.Reviewer is mapped to data_documentation_of_process.modelling_and_validation.validation.validator data_documentation_of_process.modelling_and_validation.validation.validator is appended as a list to Inventory.Data Inventory.Commissioner is mapped 1 to 1 to data_documentation_of_process.administrative_information.data_commissioner ObjectOfStudy.Owner has no explicit corresponding ISO/ST 14048 attribute and is mapped to data_documentation_of_process.process_description.technology .technical_content_and_functionality ObjectOfStudy.Site is mapped to data_documentation_of_process.process.process_description.valid_geography.sites. data_documentation_of_process.process.process_description.valid_geography.sites is appended as a list to Inventory.GeographicalBoundary It is very likely that the data about the same JuridicalPerson in different data sources will differ regarding the exact typing of characters of the names and/or addresses. Therefore, whenever data is imported into SPINE@CPM from an ISO/TS 14048 data set it is possible that a record about the juridical person already exists in SPINE@CPM with a different typing of names and/or addresses. If there is not an exact match between the typing when importing, a new record will be inserted in SPINE@CPM, which may result in more than one record referring to the same juridical person. ProcessType See chapter A.2 - technical scope
24
Sector Sector.Name relates to the attribute ObjectOfStudy.Sector Corresponding ISO/TS 14048 nomenclature: None (i.e Sector.Name is a user defined nomenclature) Mapping: ObjectOfStudy.Sector is mapped to data_documentation_of_process.process.process_description.class.name where the data_documentation_of_process.process.process_description.class.reference_to _nomenclature is always "[email protected]". If "Sector" is found in the first instance of data_documentation_of_process .process.process_description.class.reference_to _nomenclature as a sub-string then the first instance of the data_documentation_of_process.process.process _description.class.name is mapped to ObjectOfStudy.Sector. All the data_documentation_of_process.process.process_description.class.name and data_documentation_of_process.process.process_description.class.reference_to _nomenclature is mapped to Inventory.Notes.
25
Appendix B SPINE (LCI)-attributes excluded from the mapping
Activity: Aggregated Finished Category Allocation BaseFlow FlowConnection InRatio InRatioUpper InRatioLower OutRatio OutRatioUpper OutRatioLower FlowProperty QuantityMin QuantityMax StandardDev MetaId FlowType Notes ProcessType Notes PropertyType Notes Composition Substance MassEquivalence SubstanceProperty UnitEffect
26
Appendix C Unique identification and version control of data sets. If any changes whatsoever from the original ISO/TS 14048 formatted data set occur, the data set is different from the original. Data changes include data conversion distortions and correction of figures and spelling errors. It is desirable that the original ISO/TS 14048 data set identifier is sustained if a data set is communicated between databases. However, data conversion almost always implies data distortion which means that the data set is not identical after conversion. This means that it is questionable if the unique identifier should be preserved after conversion. The SPINE@CPM organisation endeavours to maintain a well defined data administration which includes keeping consistency of data sets within SPINE@CPM. However, it cannot be taken for granted that consistency is kept before data enters into SPINE@CPM and after data is communicated to another organisation with another information system.
Format analysis The process concept in ISO/TS 14048 is a combination of the ObjectOfStudy and Activity concepts in SPINE. An ObjectOfStudy can contain zero or more Activities but a specific Activity can only be related to exactly one ObjectOfStudy. There is no explicit data field to document the version of an ObjectOfStudy or Activity in SPINE. An ObjectOfStudy is in SPINE uniquely identified by one attribute: ObjectOfStudy.Id This term constitute the key to access all the data related to one unique SPINE ObjectOfStudy in SPINE@CPM (including all related Activities). An Activity is in SPINE uniquely identified by one attribute: Activity.Id This term constitute the key to access all the data related to one unique SPINE Activity (including the single related ObjectOfStudy). Note that the ObjectOfStudy.Id is a true foreign key to Activity, i.e. An Activity cannot exists in SPINE without a reference to an ObjectOfStudy. A process is in ISO/TS 14048 uniquely identified by the three attributes: data_documentation_of_process.administrative_information.identification_number data_documentation_of_process.administrative_information.registration_authority data_documentation_of_process.administrative_information.version_number These three terms constitute the key to access all the data related to one unique ISO/TS 14048 formatted process.
27
Identification mapping ISO/TS 14048 to SPINE Since a data conversion almost always implies data distortion it is not good practice to sustain the original data set identifier after conversion. However it is useful to store the original identifier to increase the transparency of a converted data set. When data is converted from ISO/TS 14048 into SPINE the original ISO/TS 14048 identifier data: data_documentation_of_process.administrative_information.identification_number data_documentation_of_process.administrative_information.version_number data_documentation_of_process.administrative_information. is therefore saved at the end of the Inventory.Data field with the syntax described in the example below: Example ---------Begin ISO/TS 14048 original identifier do not edit--------- [identification_number]IMI-20020901-123IMI-20020902-456 [version_number]1 [registration_authority]CPM - Centre for Assessment of Product and Material Systems, Chalmers University of Technology Göteborg, Sweden ---------End ISO/TS 14048 original identifier do not edit--------- Upon data conversion, a check is done if there exists an identical string as described in the example above in any of the Inventory.Data fields in the receiving SPINE formatted database. If this is the case, it is assumed that the ISO/TS 14048 data set has already been imported into the SPINE database. The person performing the conversion must then decide if the existing data set in the SPINE database shall be kept or be overwritten. If the data is to be overwritten or if the exact string is not found in the receiving SPINE database, the data is inserted and a new unique ObjectOfStudy.Id and Activity.Id is created. All original ISO/TS 14048 data sets imported into SPINE@CPM are systematically stored as files which can be retrieved if needed.
Identification mapping SPINE to ISO/TS 14048 When mapping the unique identity of a SPINE Activity data set from SPINE@CPM the following apply:
- data_documentation_of_process.administrative_information.identification_number correspond to ObjectOdStudy.Id concatenated with Activity.Id
- The version_number is always 1 - The registration_authority is "CPM - Centre for Assessment of Product and Material
Systems, Chalmers University of Technology Göteborg, Sweden"
28
Example Existing SPINE data: ObjectOfStudy.Id = IMI-20020901-123 Activity.Id = IMI-20020902-456 After data conversion into ISO/TS 14048: data_documentation_of_process.administrative_information.identification_number = IMI-20020901-123IMI-20020902-456 data_documentation_of_process.administrative_information.version_number = 1 data_documentation_of_process.administrative_information.registration_authority = "CPM - Centre for Assessment of Product and Material Systems, Chalmers University of Technology Göteborg, Sweden" ISO/TS 14048 allows any subset of data_documentation_of_process to be communicated. This gives a possibility to export an ObjectOfStudy from SPINE@CPM that doesn't contain any Activitiy. In this case only the ObjectOfStudy.Id will be exported to the data_documentation_of_process.administrative_information.identification_number.
Version control within SPINE@CPM Before a data set is inserted into SPINE@CPM it is reviewed, and necessary alterations are made such as obvious spelling errors and clarifications of inconsistencies according to the SPINE@CPM review process [4]. The only time it would be useful to apply a version control of a data set is if is changed after it is inserted and published in the SPINE@CPM database. Since this situation is rarely occurring within SPINE@CPM, no specific administration routines are defined at this time to implement version control of data sets. If this situation does happen, the person who makes the change adds appropriate information about the changes in the Inventory.Notes field. However the data in the fields: ObjectOfStudy.Id, Activity.Id and Inventory.DateCompleted is not changed. When converting a data set from SPINE@CPM to ISO/TS 14048 the version is always 1. Since there is no version control within SPINE@CPM this means that, if the data set is converted to ISO/TS 14048 before and after the change, the unique identifier will be the same, but the data content is slightly different3. The Inventory.Data attribute in SPINE has a one to one mapping to the data_documentation_of_process.modelling_and_validation.other_information attribute in ISO/TS 14048. If a SPINE@CPM data set that was originally converted from an ISO/TS 14048 formatted data set is converted back into ISO/TS 14048, the information in the Inventory.Data field including the original ISO/TS 14048 identifier is mapped to the data_documentation_of_process.modelling_and_validation.other_information attribute. If this new ISO/TS 14048 data set is converted back again into SPINE@CPM the Inventory.Data field will contain both the first data identifier and the second, with the
3 The cost of implementing a rigorous version control administration is at this time expected to be too high compared to the estimated benefits. However, when the SPINE@CPM database is converted to a format based directly on ISO/TS 14048, the data set identification and version control routines will be reviewed and redefined.
29
second at the very end of the Inventory.Data field. This is a way to keep track of the conversion history of the data set. The different stages related to the import and export of ISO/TS 14048 formatted data sets to and from SPINE@CPM is illustrated in figure 3.
Stage 1
14048 data set submitted to SPINE@CPM
SPINE@CPM review
Data set conversion to SPINE including change of identifier
Review report
Revision of data set
Stage 3
Reviewed data set
Stage 2
Not reviewed data set
Publication in SPINE@CPM
Stage 4
Published data set
SPINE@CPM database
Revision after publication
Stage 5
Published data set with changes
Data set conversion to 14048 including change of identifier
Stage 6
14048 data set exported from SPINE@CPM
SPINE@CPM
Rest of the world
Id A Id C
Id B
Id B
Id B Id B
Storage of original file
Id A
Ref: Id A
Ref: Id A
Ref: Id A
Changesnotes
Ref: Id A
Ref: Id B
Stage 1
14048 data set submitted to SPINE@CPM
SPINE@CPM review
Data set conversion to SPINE including change of identifier
Review report
Revision of data set
Stage 3
Reviewed data set
Stage 2
Not reviewed data set
Publication in SPINE@CPM
Stage 4
Published data set
SPINE@CPM database
Revision after publication
Stage 5
Published data set with changes
Data set conversion to 14048 including change of identifier
Stage 6
14048 data set exported from SPINE@CPM
SPINE@CPM
Rest of the world
Id A Id C
Id B
Id B
Id B Id B
Storage of original file
Id A
Ref: Id A
Ref: Id A
Ref: Id A
Changesnotes
Ref: Id A
Ref: Id B
Figure 3. Stages of a data set. The data set identifier changes only upon data conversion between the
formats. A reference to the original data set is always documented to a converted data set. Only published data can be retrieved from SPINE@CPM. At rare occasions a data set is revised after
publication (stage 4 to stage 5). This does not imply a change of the data set identifier in SPINE@CPM.
30
References 1. ISO/TS 14048:2002; “Environmental management – Life Cycle Assessment –
Data documentation format”, ISO/TC 207/SC 5/WG 2/TG N 20, SIS 2. Carlson R., Löfgren G., Steen B.; "SPINE, A Relation Database Structure for Life
Cycle Assessment"; Göteborg; IVL-REPORT; September 1995 3. Carlson R., Pålsson A-C; "Establishment of CPM's LCA Database"; CPM Report
1998:3, 4. Pålsson A-C.; "Review of LCI-data at SPINE@CPM"; CPM Internal Report 1999