archive as being the Producers and Consumers.
There is also another type of customer named the
designated community which is a potential
consumer.
Figure 4: OAIS Functional Entities (CCSDS, 2012).
The points of contact between the archive and
the customers are the functional entities Ingest and
Access. In Access there are two types of interactions
identified as queries and orders. These were
identified for Ingest as “Long-term preservation of
AIP”, which is the value that producers take out of
the archive. For the consumers interactions it were
identified two value propositions, one for the queries
depicted as “Resource Discovery” in the BMC and
one for orders which is identified as “Access to
Preserved Information” in the BMC.
From these value propositions the channels were
identified, the channels building block “describes
how a company communicates with and reaches its
customer segments to deliver a value proposition”.
(Osterwalder, 2009) In order to deliver the three
value propositions identified earlier there is the need
to create the appropriate channels as such it was
identified one channel for each of the value
propositions. In order to enable long-term
preservation of AIPs for Producers there is the need
to have a “Submission Service” to ingest data into
the archive for long-term preservation. Two enable
the resource discovery value proposition a query
service is needed to allow consumers to search for
holdings of interest in the archive. And finally to
access the preserved information there needs to be
an order service which allows consumers the retrieve
the identified holdings of interest from the archive.
The next step was to identify the customer
relationships which are described as “the types of
relationships a company establishes with specific
customer segments”. (Osterwalder, 2009) To engage
with Producers and ingest content the archive needs
to establish a “Submission Agreement” which
describes the data model of the information to be
ingested in the form of a Submission Information
Package (SIP), besides this the archive must also
allow a “SIP Submission Session” that allow
Producers to submit SIPs for ingest into the archive.
For resource discovery the relationship between the
archive and consumers is established using a
“Search Session” in which consumers perform
queries on the archive holdings. Finally, consumers
engage in an “Event or Adhoc DIP Dissemination
Session” to retrieve holdings of interest in the form
of a DIP which is created according to an “Order
Agreement” which has been agreed upon by both the
archive and Consumers.
The key resources describe “the most important
assets required to make a business model work”.
(Osterwalder, 2009) In order to allow for long-term
preservation of an AIP there is the need to have an
“Archiving Infrastructure” which supports the
ingesting of an AIP and also the preserved objects
described as “Preserved AIP” in the BMC. To allow
resource discovery of holdings in the archive the
“Archiving Infrastructure” is also needed to support
the execution of queries and the “Descriptive
Information” to allow consumers to find the relevant
holdings. Finally, to allow the access to the
preserved information the “Archiving Infrastructure”
is needed to support the generation of a DIP from an
AIP according to the Order Agreement. To finalize
the rationale behind the creation of this generic
BMC the key activities are identified. Key activities
describe “the most important things a company must
do to make its business model work”. (Osterwalder,
2009) If we look again to the functional entities of
an OAIS (Figure 4) the key activities are the
functional entities from OAIS. In order to allow for
long-term preservation of AIPs, the archive must
perform “SIP Ingestion and AIP generation” which
is the Ingest Functional Entity, it must also perform
“Preservation Planning”, “AIP Storage” which is the
Archival Storage Functional Entity and must
perform “Archive Administration” which is the
Administration Functional Entity. To allow resource
discovery the archive must perform “Data
Management” which allows access to descriptive
information necessary to identify relevant holdings
in the archive. Finally, for the archive to allow
access to preserved information it must perform
“DIP Dissemination” which is the Access Functional
Entity and must also have “Archive Administration”.
Regarding the Key Partnerships, Cost Structure
and Revenue Streams these could not be properly
identified from OAIS and according to our vision
these are context dependent. For example, an archive
can have software providers as key partners if the
DigitalCurationCosts-ARiskManagementApproachSupportedbytheBusinessModelCanvas
303