March 27, 2004

1
March 27, 2004
GRI Software Solution Proposal
Presentation by Contact info Natan
Zaidenweber CEO t415-401-7343 nat_at_stakeware.com
2
Contents of Presentation
(click on the underlined section to skip directly
to that topic)

• OBJECTIVES
• MAIN COMPONENTS
• Global View
• Stakeholder Engagement Solution
• Central Repository
• Reporting Wizard
• Center for Information Exchange
• SUMMARY OF BENEFITS

3
Objectives for this Proposal

• GRIs objective Create a series of tools geared
  toward bridging the existing "delivery" gap
  between GRI report writers and report readers.
• Company Background StakeWare inc. has developed
  in the last 3 years, at a cost of more than
  500K, an enterprise Web solution that automates
  the stakeholder engagement process and enables
  Triple Bottom Line reporting according to the GRI
  framework. It has recently initiated its go to
  market plans in the 1st quarter of 04 and closed
  its first customer, Forest Trends, in the last
  month. It is also engaged in discussions with a
  pipeline of potential client companies such as
  The Gap, Hewlett Packard, Deloitte Touche, Star
  Group Consultants and numerous others.
• StakeWares 3 objectives for this proposal
• Present the features and benefits of the its
  already built StakeWare stakeholder engagement
  and TBL dynamic reporting solution. Explain how
  concretely it could interact with the proposed
  solution of the GRI and how by integrating a
  stakeholder engagement solution this would
  significantly increase the value proposition of
  the GRI solution by offering a more complete
  integrated end-to-end customer solution and thus
  offer additional important benefits to the report
  writers.
• Present StakeWares own vision of the GRI
  proposed solution and how StakeWare has the
  domain expertise and technical expertise to build
  it and to finance it with an already engaged
  group of Venture Capitalist investors.
• Get StakeWare to be chosen as a strategic partner
  to the GRI by either supplying all of the total
  solution or part of the total solution.

4
Global View
Retrieve Info Agent Web Service
Publishing Info Agent Web Service
Report Preparers
Intranets
Report Users
Reporting Wizard
XGRL
XGRL
Shared Folders
Intranet Portals
Central Repository
Internet
Information Delivery
Embedded Applications
Stakeholder Maps
Retrieving Metadata
Publishing Metadata
Wireless Servers
Meeting Mgmt
Best Practices
Follow-up Workflow
Report Types Layouts Templates
Resources Methods Data Sets Users
Issue Identification
Web Access
Document Mgmt
Value of Information
Pegged Discussions
Semantic Rules
Transformation Aggregation Validation Busines
Rules
eXtensible Global Reporting Language
Information Exchange
Stakeholder Engagement
GRI Portal
5
Benefits of integrating a stakeholder engagement
solution with the GRI total solution

• This makes the GRI offering a complete end-to-end
  report preparer solution it connects and
  integrates dynamically the companys stakeholders
  into the reporting process
• When using the report wizard, the writer can use
  feedback from stakeholders to help choose the
  right indicators to report on. (Improved
  materiality of reports)
• After publishing a report, the writer can get
  qualitative feedback from the stakeholders such
  as the report readers on their perception of the
  companys performance on each of the indicators.
  (Better understanding of impact of reporting on
  stakeholder perception)
• Gives easy access to more than just quantitative
  data but also to all the companys historical
  stakeholder dialogue linked to any of the
  published or unpublished indicator results and
  programs. Decreases audit time for the writer
  and also decreases time to gather data to fill
  out questionnaires sent by report readers such as
  SRI funds. (Decreased questionnaire and
  reporting fatigue)
• Overall, it adds GRI indicator performance
  management tools to enable the company to know
  how it is perceived to be doing and to get
  feedback on how it could improve its GRI
  reporting process. (Dynamic feedback loop for
  on-going reporting process improvement)

6
The StakeWare Solution the different feature
sets

• REPORTING the StakeWare solution offers a
  customizable concept map to match any reporting
  framework chosen (GRI or other) by the reporting
  company thus enabling easy auditing, searching
  and reporting.
• STAKEHOLDER ENGAGEMENT best practices of
  stakeholder engagement are built into the
  solution giving the manager the flexibility to
  choose the right approach when doing any
  participatory task, thus optimizing the benefits
  of his companys stakeholder dialogue activities.
  
• STAKEHOLDER MAPS
• PARTICIPATORY MEETING MANAGEMENT
• ISSUE IDENTIFICATION and FOLLOW UP WORKFLOW
• DOCUMENT MANAGEMENT(CHECK-IN/OUT)
• DISCUSSIONS AND POWERFULL SEARCH FEATURES
• PERFORMANCE INDICATORS MANAGEMENT a dashboard
  view leveraging stakeholder surveys and a
  Bayesian inference engine (patent pending)
  enables the manager to identify potential issues
  earlier and in ways that are not possible through
  manual processes. This increased level of
  proactivity saves time and money while
  diminishing the on-going business risks .

7

Step by step discovery of the StakeWare
Stakeholder Engagement System
Step 1 Decide which reporting framework to use
and set up the concept map. All data will be
pegged accordingly for easy access, audit and
management.
GRI Category
GRI Aspect (Related Indicators in sub-directory
below it)
8

Step 2 Identify stakeholders and input the
names in the stakeholder section
according to level of priority i.e primary,
secondary stakeholders.
9
Participatory Meeting Management
Step 3 Start engaging with the stakeholders and
leverage meeting management features, issues
tracking, doc library to enable more efficient
on-going stakeholder dialogue.

10
Issue Management
11
Document Management(Version Control)
12
Discussions
13
Categorize Information Objects According to GRI
All tasks pertaining to stakeholder engagement
become information objects (meetings, minutes,
issues, docs and discussions) and are linked to
each appropriate reporting indicator,
Category
Environment

Aspect
Emissions
Indicator
Total Waste (EN11)
14

Step 4 Get feedback from stakeholders through
the survey function and manage the performance
indicators.

• Manager chooses what type of stakeholder feedback
  he requires to help make important decisions,
  creates the appropriate survey questions (A) and
  sends them out once or at regular intervals to
  track trends over time
• Reporting example
• Decide which indicators to include in a report
  based on stakeholder perception (What is
  important to them? Materiality)
• - Decide which programs to continue, stop or
  adjust by getting feedback on indicator
  performance (Perception of results)
• Stakeholder engagement example
• - Get on-going feedback on the process and make
  adjustments

A
Concept Map/ GRI framework
B
(B) Manager can access a frequency distribution
for each question answered (Histogram)
A concept map defines how performance indicators
are related with survey questions. A
probabilistic Bayesian network puts together this
qualitative representation and its quantitative
interaction expressed by probability tables. Both
representations define a standardized model
called scenario. Analysts can evaluate
alternative situations, i.e. importance of
stakeholder profile or set of questions by
generating different scenarios with only changing
the probabilistic representation.
15

Step 5 On-going issue identification using
patent pending Bayesian Networks inference
approach in a complex context, the system can
help identify potential issues based on
correlation of evidence from past experiences.
GRI Framework

C
Category
Aspect
Indicator
(C) All-in-one-place The system, using the
inference engine, generates a dashboard view of
results from the surveys and highlights potential
issues (red and yellow) around different aspects
and indicators. This complements the view of
current open issues and enables the manager a
good overall perspective at all times.
Bayesian modeling in this framework (Inference
engine) computes value of information given
stakeholder feedback. It computes how the
perception of a set of indicators impacts
their respective aspects and categories in the
GRI taxonomy. The system reports the results
in a dashboard view.
16

Step 6 Risk Management, analyst can probe the
indicators and obtain relevant information at
the next level down
E
D
Indicator
Stakeholders in the extremes
Stakeholders in the middle
Information object (meeting) associated with the
issue
(E) Dynamic generation of stakeholder maps enable
an even higher level of granularity in the
understanding of stakeholder perceptions and
highlights the stakeholders that are outliers on
a potential issue that should be contacted.
Clicking on a number in this map brings up the
profile of the specific stakeholder and all the
appropriate contact information.
(D) Once an indicator is identified as a
potential issue, further probing, by clicking on
the actual indicator opens a sub-level screen
shot, can facilitate the discovery and
understanding of the root issue including a
correlation of the data with a given information
object related to the issue i.e which meetings
talked about the specific issue?, who attended?,
which documents to read?, etc.
17

Step 7 Organize and search information objects
according to GRI taxonomy.
Triple Bottom Line Search lowers the audit time,
since information objects are weaved according to
process flow and GRI taxonomy
18
A. Central Repository

• Use a centralized, persistent, scalable
  repository to collect report data in one place
  and work with it there. A single repository that
  facilitates creation and accessing reports.
• The source data can be collected from distributed
  sites on a publish-and-subscribe basis. Each
  company decides which information is going to be
  published, how and when information can be
  extracted.
• A central repository based on a model-driven
  architecture
• Retrieving Metadata provides an abstract
  specification of how information could be
  extracted.
• Publishing Metadata defines how information will
  be reported.
• Semantic Rules establishes ways to transform,
  validate and combine data.

19
A.1 Automated Data Input

• A mechanism for populating a central repository.
• Simplifying procedures for accessing GRI data
  across different applications.
• Using GRI Taxonomy for generating a Concept Map
  representation. This provides an XML Schema and
  standard representation for accessing source
  data.
• Defining a Semantic Layer of how physical
  structures of data could be built and transformed
  to produce a consistent internal data
  representation.

20
A.1.1 Retrieving Metadata

• Information required to access original data
• Resources - Parametric definition where data is
  located
• Methods How indicators are generated
• Data sets Specification of source data for
  generating indicators
• Users - Access control and authentication

21
A.2 Search Facility

• Information users are able to search through an
  effective and extensive search function.
• GRI Taxonomy is used to define Semantic Tags.
• These semantic tags are associated with core
  indicators and source data.
• We define an Indicator-discovery mechanism for
  delimiting information to be selected.
• Searching data based on semantic tags.

22
A.3 eXtensible Global Reporting Language (XGRL)

• XGRL is an electronic markup language that uses
  GRI guidelines as standards to import and export
  information across different technologies.
• XGRL is based upon XML tags, which provide a
  standard method of communication that allows
  dialogue between completely different
  applications.
• It provides a mechanism to separate content from
  format.

23
A.4 Retrieving Information Agent Service

• It is a web service that maps high-level user
  requests for retrieving data sets, to low-level
  storage operations in the heterogeneous,
  distributed and data store environment.
• It uses information stored in the retrieving
  metadata to serve this function.
• It provides well-defined interfaces based on XGRL
  to a variety of data store applications.

24
B. Reporting Wizard

• A mechanism that standardizes and facilitates
  reporting as well as improves presenting
  information for strategic decision-making and
  management.
• Templates for defining data structures and
  layouts.
• Data flow for implementing an automatic
  generation.
• Menu-driven and data flow for guiding manual
  generation.

25
B.1 Automated Data Output

• Reports will be uploaded to the central
  repository. Output in XGRL could be exported to
  external applications for further development.
• Definition of core performance indicators for
  delimiting report.
• Use of publishing metadata for defining different
  type of outputs.
• Interfaces for facilitating communication with
  different external applications.

26
B.1.1 Publishing Metadata

• Information required for automatically producing
  a GRI report.
• Report Types - Format definition of each report
  type.
• Layouts Which elements should be presented in
  each report.
• Templates Standard definition of individual
  components for generating a report.

27
B.2 Publishing Information Agent Service

• It is a web service that facilitates publishing
  and exporting reports to different applications.
• It maps high-level report definition to low-level
  application requirements.
• It uses information stored in the publishing
  metadata to serve this function.
• It provides well-defined interfaces based on XGRL
  to a variety of publishing applications.

28
C. Center for Information Exchange

• It houses all GRI reporting tools. It will be a
  platform for sharing good practice in a
  standardized way. It contains web-based training
  solutions. It is accessible from the reporting
  wizard and central repository.
• The stakeholder engagement platform could be used
  for supporting a center for information exchange
  whose architecture includes Document management
• Training component
• Course management
• Tracking user and course interaction
• Presentation component
• Live training
• Delivery management
• Search mechanism based on semantic tags

29
C.1 Document Management

• It provides a mechanism for organizing and
  classifying documents
• It includes version control for updating
  documents. It avoids redundancy and keeps
  accessible the latest version.
• It defines access control by delimiting user
  roles reader, editor, publisher.
• It keeps a standardized way to display technical
  information and best practices.
• It facilitates collaboration among different
  users.

30
C.2 Training and Delivery Component

• It includes a web-training application.
• It supports a course management for keeping
  control of Course Material. It includes specific
  attributes for delimiting objectives, content,
  references and predefined requirements.
• It provides an evaluation procedure for tracking
  course and user interaction.
• It integrates audio, video and data to provide an
  online environment.
• It delivers presentations and course materials
  both following an schedule based on milestones or
  providing an access mechanism without
  requirements.

31
Summary of Benefits

• Central Repository Advantages
• Original data is located in the source sites
  facilitating updating information process.
• Semantic transformation improves information
  access to different sources.
• Development of XGRL.
• Reporting Wizard Advantages
• By using GRI taxonomy and XGRL tags, information
  needs to be gathered only once and then sent to
  the receiving application as an XML file.
• Ensure consistent and accurate dissemination of
  the GRI information.

• Click on box to jump to that section
• Objectives Global View
  Stakeholder Engagement
  Central Repository Reporting
  Wizard Information Exchange

32
Summary of Benefits (Continued)

• Center for Information Exchange Advantages
• A repository of previous experiences in the way
  to implement or enforce a GRI framework in
  different companies.
• It shares best practices and opens possibilities
  to collaborate by writing conjointly the same
  document.
• It is always accessible the latest version.
• It delivers online training.
• It provides a systemic way for searching
  information objects based on semantic tags.

• Click on a box to jump to that section
• Objectives Global View
  Stakeholder Engagement
  Central Repository Reporting
  Wizard Information Exchange