Sustainability Analysis System

From Open Sustainability

Activity: Sustainability Analysis System

Objective

The Sustainability Analysis System activity involves scoping out the requirements for a technology system to manage the data and reporting.

This may involve additions to existing technology systems within an organization to capture new data or generate reports linking data such as purchasing, HR information and facilities, creating a bespoke program to or the scoping out of a new system. Generic workflow and issue mangement software is available to help manage the new data, but there are also a number of specialist environment/health/safety/CSR systems as well.

Some of the specialist comprehensive systems avilable are:

• CRedit360 - web-based CSR and sustainability data management and communication system
• Enablon - Corporate Responsibility and EH&S software solutions with expertise in Governance, Risk & Compliance

There are also systems for issue management within sustainability:

• Clear Standards - assess, analyze and reduce GHG emissions
• Greenstone - carbon accounting, reduction and offset solutions

Major Deliverables

• Possibly an RFP to software vendors
• System Requirements

Tasks

Refer to MIKE2.0 Method for Integrated Information Management

Objective: Review Phase 3 within MIKE2.0 for detailed requirments on how best to scope out a new way to manage the sustainability information.

Engage Information Technology team

Objective: Brief the IT team on the requirements, including data and information to be collated from existing systems.

Provide a Sustainability Orientation for the IT project team so as they have an understanding of what the information is and how it is to be used. Engaging them is also beneficial as their input into IT energy efficiency measures will be vital.

Data Profiling and Re-Engineering

Objective:

Infrastructure Management Process Design

Objective:

Reuse Design

Objective:

Design Test Cases for Sustainable Development

Objective:

An overall set of test cases is created for testing applications. Functional Testing and E2E Testing will be the areas of highest complexity.

Input:

• Test Strategy
• Develop Test Plans for Applications
• Test Requirements
• Requirements and Design for Application Development (done in parallel with design)

Core Supporting Assets

Yellow Flags

• Too few exception test cases – should be many more exception test cases than “happy path” test cases
• Test Design does not trace back to business and technical requirements
• Test Design does not include regression testing
• Test environments are not ready
• Testing approach is very document-centric and does not incorporate automated testing

Key Resource Requirements

• Test Manager
• Development Leads