lngbc.eulngbc.eu/system/files/deliverable_attachments/d8.1 proje… · web viewthis opens the way...

EUROPEAN COMMISSION

DG MOVE

SEVENTH FRAMEWORK PROGRAMME

GC.SST.2012.2-3 GA No. 321592

Project websitewww.lngbluecorridors.eu

Deliverable No. LNG-BC D8.1Deliverable Title Project WebsiteDissemination level

PublicWritten By Stijn Vernaillen (VITO) 13/11/2013Checked by Tobias Denys (VITO) 13/11/2013Approved by Tobias Denys (VITO)/ Javier Lebrato (NGVA) 13/11/2013Issue date 13/11/2013

LNG-BC document.docx Public

2/50

Executive SummaryAbout the project

The Blue Corridors project’s aim is to establish LNG as a real alternative for medium & long distance transport - first as a complementary fuel and later as an adequate substitute for diesel.

Up to now the common use of gas as fuel was for heavy vehicles running on Natural Gas (NG) only for municipal use, urban buses and garbage collection trucks. In both types of application engine performance and autonomy are good with present technologies, being well adapted to this alternative and cleaner fuel.

However analyzing the consumption data, the equivalence in autonomy of 1 litre of diesel oil is 5 litre of CNG, compressed to 200 bar. Five times more volume of fuel prevents the use of CNG in heavy road transport, because its volume and weight would be too big for a long distance truck.

This opens the way for LNG (Liquefied Natural Gas), which is the way to transport natural gas by ship to any point of the globe. NG liquefies at 162º C below zero, and the cost in energy is only 5% of the original gas.This state of NG gives LNG the advantage of a very high energy content. Only 1,8 litre of LNG are needed to meet the equivalent autonomy as using 1 litre of diesel oil.

A 40 tonne road tractor in Europe needs a tank of 400 to 500 litres for a 1.000 km trip; its equivalent volume with liquid gas would be 700 to 900 litres of LNG, a tank dimension that could be easily fitted to the lateral of the truck chassis. LNG is therefore opening the use of NG to medium and long distance road transport.

LNG has huge potential for contribution to achieving Europe’s policy objectives such as the Commission’s targets for green house gas reduction, air quality targets, while at the same time reducing dependency on crude oil and guarantying supply security. Natural gas heavy duty vehicles already comply with Euro V emission standards and have enormous potential to reach future Euro VI emission standards without complex exhaust gas after treatment technologies, which cause increasing procurement and maintenance costs.

To accomplish its objective it has defined a roadmap of LNG refueling points along four corridors covering the Atlantic area (green line), the Mediterranean region (red line) and connecting Europe’s South with the North (blue line) and its West and East (yellow line) accordingly. In order to implement a sustainable transport network for Europe, the project has set the goal to build approximately 14 new LNG or L-CNG stations, both permanent and mobile, on critical locations along the Blue Corridors whilst building up a fleet of approximately 100 Heavy Duty Vehicles powered by LNG. These vehicles will be provided by the main important truck manufacture in terms of liquefied natural gas as Volvo, Iveco and Renault Trucks.

This European project is financed by the Seventh Framework Programme (FP7), with the amount of 7.96 M€ (total investments amounting to 14.33 M€), involving 27 partners from 11 countries.

This document corresponds to the first deliverable within work package 8. It is a guideline about the creation process of the project website. Currently it is already available in internet through the next link: http://www.lngbluecorridors.eu/ which can be consulted by any user. It has a public access.

LNG Blue Corridors Project is supported by the European Commission under the Seventh Framework Programme (FP7). The sole responsibility for the content of the website lies

with the authors. It does not necessarily reflect the opinion of the European Union. Neither the FP7 nor the European Commission are responsible for any use that may be made of the information contained therein.

About the websiteThe purpose of the LNG Blue Corridors website is threefold. In its most basic form the website is used to communicate about the project -what is the project about, what are the deliverables, what’s the current status of the project,... In this form it has some basic static information available. Newsitems can be posted on the website and documents can be shared with the world.

The second, more important, part of the website is focused on the promotion and sharing of knowledge related to LNG for transport. The goal of this part of the website is to become the go-to place for people involved in LNG for transport, users/owners of LNG vehicles and the general public. It provides a platform for (registered) users to add and share information, comment and improve information in order to improve this information.

The third part of the website is more focused on the collaboration between the partners of the project. Within the functionality of the public site, a private section is generated where partners can easily share documents, discuss the various topics of the project and create issues/ task for eachother.

In the following pages of this working document the various components and functionalities of the website are described in depth. This document is used for the further development of the website. However, the website is a living tool that can change during the development of the website depending on the evolution of the project through time and lessons learned during the project.

The various elements are:

Content Types : The content for the website can be grouped in different content types. Each content type has its own specific fields and its own specific functionality.

Wireframes: A wireframe is a visual representation of the skeletal framework of the website. Wireframes depict the page lay-out and the different elements visible on the webpage depending on the content that is being viewed.

Userflows: Userflows are visual reprensentations of the various steps that happen when a user interacts with the website. One of the flows can be the various steps in user registration.

DisclaimerThe LNG Blue Corridors research project has been funded with support from the European Commission in the context of the Seventh Framework Programme (FP7). This Website reflects only the views of the LNG Blue Corridors consortium members, the Commission cannot be held responsible for any use that may be made of the information contained herein.

The information on this website is provided "as is", and no guarantee or warranty is given that the information is suitable for any particular purpose. The above referenced consortium members shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials subject to any liability which is mandatory due to applicable law.


ContentsExecutive Summary................................................................................................................................3

About the project...............................................................................................................................3

About the website..............................................................................................................................4

Disclaimer...........................................................................................................................................4

1 Structure and terminology...........................................................................................................10

1.1 Sections................................................................................................................................10

1.1.1 Project Communication Platform..................................................................................10

1.1.2 Public Knowledge Sharing Platform..............................................................................11

1.1.3 Internal Project Collaboration Platform........................................................................11

1.2 Nodes & Entities...................................................................................................................11

1.2.1 Entity types...................................................................................................................11

1.2.2 Bundles.........................................................................................................................11

1.2.3 Fields.............................................................................................................................11

1.2.4 Entity.............................................................................................................................13

1.2.5 Organic Groups.............................................................................................................13

1.3 Users.....................................................................................................................................14

1.3.1 Types of users...............................................................................................................14

1.3.2 User Roles.....................................................................................................................14

2 Sitemap........................................................................................................................................16

2.0 Frontpage.............................................................................................................................16

2.1 About the project.................................................................................................................16

2.1.1 Mission.........................................................................................................................17

2.1.2 Plans/Timeline..............................................................................................................17

2.1.3 Ambitions......................................................................................................................17

2.1.4 Methodology................................................................................................................17

2.1.5 Partners........................................................................................................................17

2.1.6 Results..........................................................................................................................17

2.1.7 Contact.........................................................................................................................18

2.2 News & Events......................................................................................................................18

2.2.1 News.............................................................................................................................18

5/50


2.2.2 Newsletter....................................................................................................................18

2.2.3 Events...........................................................................................................................18

2.2.4 Press.............................................................................................................................19

2.2.5 Documents and publications........................................................................................19

2.3 Knowledge Platform.............................................................................................................19

2.3.1 Refilling Stations...........................................................................................................20

2.3.2 Vehicles.........................................................................................................................21

2.3.3 Organisations................................................................................................................21

2.3.4 FAQ...............................................................................................................................21

2.3.5 Links..............................................................................................................................21

2.3.6 Forum...........................................................................................................................21

2.4 My Account..........................................................................................................................22

2.4.1 Login/Logout.................................................................................................................22

2.4.2 My Profile.....................................................................................................................22

2.5 Partner Platform...................................................................................................................22

2.5.1 Workpackages..............................................................................................................23

2.5.2 Tasks.............................................................................................................................23

2.5.3 Documents....................................................................................................................23

2.6 Global Pages.........................................................................................................................23

2.6.1 Terms&Conditions........................................................................................................23

2.6.2 Privacy Policy................................................................................................................23

2.6.3 Cookie Compliance.......................................................................................................24

2.6.4 FP7 Disclaimer..............................................................................................................24

3 Content Types..............................................................................................................................25

3.1 Basic Content Page...............................................................................................................25

3.1.1 Description....................................................................................................................25

3.1.2 Functionality.................................................................................................................25

3.1.3 Fields.............................................................................................................................25

3.1.4 Permissions...................................................................................................................26

3.2 Article...................................................................................................................................26

3.2.1 Description....................................................................................................................26

3.2.2 Functionality.................................................................................................................26

6/50


3.2.3 Fields.............................................................................................................................26

3.2.4 Permissions...................................................................................................................27

3.3 Event.....................................................................................................................................27

3.3.1 Description....................................................................................................................27

3.3.2 Functionality.................................................................................................................27

3.3.3 Fields.............................................................................................................................27

3.3.4 Permissions...................................................................................................................28

3.4 Refilling Station.....................................................................................................................28

3.4.1 Description....................................................................................................................28

3.4.2 Functionality.................................................................................................................28

3.4.3 Fields.............................................................................................................................29

3.4.4 Permissions...................................................................................................................29

3.5 Organisation.........................................................................................................................30

3.5.1 Description....................................................................................................................30

3.5.2 Functionality.................................................................................................................30

3.5.3 Fields.............................................................................................................................30

3.5.4 Permissions...................................................................................................................31

3.6 Vehicle..................................................................................................................................31

3.6.1 Description....................................................................................................................31

3.6.2 Functionality.................................................................................................................31

3.6.3 Fields.............................................................................................................................31

3.6.4 Permissions...................................................................................................................32

3.7 FAQ.......................................................................................................................................32

3.7.1 Description....................................................................................................................32

3.7.2 Functionality.................................................................................................................32

3.7.3 Fields.............................................................................................................................32

3.7.4 Permissions...................................................................................................................32

3.8 Document.............................................................................................................................33

3.8.1 Description....................................................................................................................33

3.8.2 Functionality.................................................................................................................33

3.8.3 Fields.............................................................................................................................33

3.8.4 Permissions...................................................................................................................33

7/50


3.9 Forum...................................................................................................................................34

3.9.1 Description....................................................................................................................34

3.9.2 Functionality.................................................................................................................34

3.9.3 Fields.............................................................................................................................34

3.9.4 Permissions...................................................................................................................35

3.10 Newsletter............................................................................................................................35

3.10.1 Description....................................................................................................................35

3.10.2 Functionality.................................................................................................................35

3.10.3 Fields.............................................................................................................................35

3.10.4 Permissions...................................................................................................................35

3.11 Issue/Task.............................................................................................................................36

3.11.1 Description....................................................................................................................36

3.11.2 Functionality.................................................................................................................36

3.11.3 Fields.............................................................................................................................36

3.11.4 Permissions...................................................................................................................37

3.12 Group....................................................................................................................................37

3.12.1 Description....................................................................................................................37

3.12.2 Functionality.................................................................................................................37

3.12.3 Fields.............................................................................................................................37

3.12.4 Permissions...................................................................................................................38

4 Wireframes...................................................................................................................................39

4.0 General.................................................................................................................................39

4.0.1 Content Regions...........................................................................................................39

4.0.2 Basic Layouts................................................................................................................40

4.1 Frontpage.............................................................................................................................40

4.2 About the project.................................................................................................................42

4.2.1 General Page.................................................................................................................42

4.2.2 Partners List..................................................................................................................42

4.2.3 Refilling Stations List.....................................................................................................43

4.3 News & Events......................................................................................................................44

4.3.1 News Page....................................................................................................................44

4.3.2 Newsletter....................................................................................................................45

8/50


4.3.3 Events Page...................................................................................................................46

4.4 Organic Group Page..............................................................................................................47

5 User flows.....................................................................................................................................48

5.1 User Registration Flow..........................................................................................................48

5.2 Content Creation Flow..........................................................................................................49

5.3 Guidelines to promote the forum.........................................................................................50

List of Tables.....................................................................................................................................51

List of figures....................................................................................................................................51

9/50


1 Structure and terminologyTo create a well-functioning website various elements are required. In this section of the document the structural elements like sections, entity types, fields, bundles, organic groups, user and user role are explained.

1.1 SectionsThe website is divided in 3 sections. In its most basic form the website is used to communicate about the project. This section of the website is accessible to all types of users and contains basic information about the project, public deliverables and news items. This is the “Project Communication Platform”.

The second section of the website is used to share public knowledge related to the topic of the project. This section is called the “Public Knowledge Sharing Platform”. This section is accessible for all types of users. Authenticated users will be able to add content to this section of the website. Depending on the user role this content is first reviewed by a user with an editor role before being make public to assure the quality of the content and to avoid spam.

The third section of the website is only accessible to the partners of the project. This section is used as a collaboration platform for the partners. Partners can share information, ask questions to other partners and upload deliverables to this section. Parts of this section can be made public.

1.1.1 Project Communication PlatformThe project communication platform focusses on dissemination of information related to the project. This includes “what,why and how” information on the project, recent news items, (related) events,…

10/50


1.1.2 Public Knowledge Sharing PlatformThe Public Knowledge Sharing Platform is an section on the website where registered users can help build the information about LNG Trucks and refilling stations.

1.1.3 Internal Project Collaboration PlatformThe Internal Project Collaboration Platform provided the project partners with a workspace to collect information, discuss various topics and follow up tasks and issues.

1.2 Nodes & EntitiesFor the development of the website the opensource content management system Drupal 7 is used. This software has its own vocabulary which will be used throughout the document. The definitions as stated on the Drupal.org1 website are stated below:

1.2.1 Entity typesIn earlier versions of Drupal, the field system was only used on content types. Now, thanks to the Entity API, we can add fields to other things, like comments. Fieldable entities make Drupal eminently flexible. An entity type is a useful abstraction to group together fields. Let’s consider some examples of entity types:

Nodes (content) Comments Taxonomy terms User profiles

You can also build new kinds of entity types where the options above don't suit your needs. For more information, read further about using the hook_entity_info and extension by Entity API: entity_crud_hook_entity_info.

1.2.2 BundlesBundles are an implementation of an entity type to which fields can be attached. You can consider bundles as subtypes of an entity type. With content nodes (an entity type), for example, you can generate bundles (subtypes) like articles, blog posts, or products. Not all entity types have bundles, however. For example, users do not have separate bundles (subtypes). For the entity types that do allow bundles, you can create as many bundles (subtypes) as you want. Then, using the Field system, you can add different fields to each bundle. Examples include a file download field on Basic Pages and a subtitle field on Articles.

1.2.3 FieldsA field is a reusable piece of content. In technical terms, each field is a primitive data type, with custom validators and widgets for editing and formatters for display. You can read further for a developer's guide to using the Drupal 7 Fields API.

What's important to know as it relates to Entities is that Fields can be added to any of the bundles (or entity types) to help organize their data. Say, for example, you create a content type with an unstructured text field and use HTML to structure parts of it, like a summary section, or prices. That would make it more difficult, then, to control how these

1 An Introduction to Entities: https://drupal.org/node/1261744

11/50

http://drupal.org/node/443536

http://drupalcode.org/project/entity.git/blob/refs/heads/7.x-1.x:/entity.api.php

http://api.drupal.org/api/drupal/modules--system--system.api.php/function/hook_entity_info/7

https://drupal.org/node/1261744


were displayed, or to make connections between different types of related content. This is where using fields is essential.

1.2.3.1 Field Types

Below is a list of the various field types that are used throughout the website in combination with the various entities.

Table 1-1Overview of field types

Type Description

Text A text field is a somple field t oinput basic text without the possibility of adding formatting

Long Text Unlimited number of text possible. Depending on the permissions granted, this text can be styled, images can be added etc. Ref; “rich content”

Entity Reference This field links one entity to another entity. For example an refilling station has an entity reference field “owner” which links to an organization. Only the title of the entity needs to be submitted, the rest of the information can be retrieved from the linked entity

Location field This is a preformatted field with the different inputs for an address (street, city, postalcode,…).

Geofield This field is used to translate the location field to coordinates so that a projection on a map can be made?.

Office hours A field formatted to input openinghours for a certain location

Get Directions This field type generated driving directions based on user input and the location field.

Decimal A decimal value which can be used for calculations

Term reference A field that can be used to refer to terms in a vocabulary. (eg. Tags)

File field Possibility to upload content to an entity (like attachements). This can be in the form of a file or an image.

OG Field “Organic Group field”. Indicates if an entity is an organic group or not.

OG Visibility Indicates if the organic group is public or private

OG Subscribe Indicates if it is possible to register for a certain group.

OG Permissions Indicates if a group can have custom permission settings or not.

12/50


1.2.4 EntityAn entity would be one instance of a particular entity type such as a comment, taxonomy term or user profile or a bundle such as a blog post, article or product.

You can use entity_load to load any entity. Note, however, that the core does not provide a save or delete function, but thanks to Entity API module the missing pieces are added (entity_create(), entity_save(), entity_delete(), entity_view() and entity_access()).

Putting this in Object-Oriented Design/Programming terms...

If you come from an OOD/P background and are trying to better understand what these key D7 concepts are, the following suggested mapping might help (albeit not strictly true from a purist’s perspective) :-

An entity type is a base class A bundle is an extended class A field is a class member, property, variable or field instance (depending on your

naming preference) An entity is an object or instance of a base or extended class

All these four OOD/P concepts are special in that they are serialisable (stored - e.g. to a database or file). Serialisation takes place via the Entity API.

1.2.5 Organic GroupsA Group as used in the Organic Groups Module of Drupal is a collection of Content and/or People. Groups can be what you find on groups.drupal.org or Facebook.

Examples:

Social Networking Groups: Organic Groups can be configured to pre-existing social networking concepts such as those that are found on Facebook, Tagged, MySpace and even Groups.Drupal.org (g.d.o.)Social Networking Groups can be created and maintained by the users of the site allowing the members of your site to take control over their social experience and the content they desire or find appropriate to the topics they desire to explore.Groups essentially removes the rigid boundaries of current "forum" based sites, and allow the users of the site to define their own topics and the scope in which these topic contain. Groups can also be self moderated allowing Group moderators the ability to control the audience of their content. Thus Groups can be open to all, moderated approval, or invite only and the ability to maintain their user base is distributed to group owners.

Content Management: Organic Groups allow for very unique content management custom solutions. Content of the "Group Content Type" has the unique ability to belong to multiple Groups at once. This reduces duplication and increases content accessibility. Utilizing users to adopt content allows users to create their own libraries of content without having to create duplication. Content is thus associated with the user and can be maintained by the user, and group maintainers can then manage content in ways that help their audience.

User Relationships: Groups provide unique opportunities to create user relationships based on Nodes and/or Content, rather than the typical friendship modules. This does not diminish the friendship based relationship model, but provides a unique model based on structured relationships. Since Groups are

13/50

http://drupal.org/project/entity

http://api.drupal.org/api/drupal/includes--common.inc/function/entity_load/7


based around Nodes, Administration of the user relationships can be assigned to a moderator(s). This structural approach can meet unique needs for distributed moderation while also providing the option for freedom of user created relationships.

Flexibility: The flexibility of groups is broad. People have used groups in a wide variety of sites. Often times the word "Group" is never seen by the end users.

Organic Groups provide the possibility to created separate sections of the website focused on specific topics which can be made public or private. These organic groups can be linked to from the main page or exist as a subdomain (eg. www.lngbluecorridors.eu/infrastructure). This can be done at any time in the project with minimal effort when needed.

1.3 UsersA user is an entity that has certain permissions on the website. A user can have one “user type” and multiple “user roles”. A user type defines if the user is known or unknown to the system. Permissions on the website (eg. Create content) are granted based on a user role. One user can have multiple user roles.

1.3.1 Types of users1.3.1.1 Anonymous Users

Anonymous users are all the users who are not logged into the website. This type of users is the basic type of user and is the user with the least open permissions.

1.3.1.2 Authenticated Users

Authenticated users are users who have registered on the website by providing at least a username, email address and password. Authenticated users can log in to the website by using their username and password which unlocks features and functionality to the user. Access to these unlocked features depends on the role of the user.

1.3.2 User RolesUser roles define who has what permissions on the website. One type of user can have a combination of user roles. Depending on the user role the user can create certain types of content, can approve content for publishing or can access certain sections of the website. Permissions of the various user roles are defined below in general and in the description of the various node types.

Working with various user roles provides the opportunity to engage a broader public in the generation of relevant knowledge and involve them in the project.

1.3.2.1 Pre-approved user role

The Pre-approved user role is automatically assigned to users who have created a profile but have not yet validated their email address. For the user there is no difference in functionality between anonymous and pre-approved user role. As soon as the user has validated his email address (through following a link that has been mailed to the email address provided) the user will automatically switch to the Authenticated User Role (see below). If the email address is not validated within 3 days of creating the account, the account will be deleted.

14/50

http://www.lngbluecorridors.eu/infrastructure


1.3.2.2 Authenticated user role

The authenticated user role is the standard user role of anybody who has registered for a user account and who has validated his/her email address. An authenticated user is able to post articles and events to the website but is not allowed to make them public. Content created by an authenticated user role still needs to be validated by an Editor user profile.

1.3.2.3 Refilling station owner

A “Refilling station owner” has the same access as the authenticated user and can create a “Refilling Station Node”. This user role can’t directly make content public. Content created by this type of user needs to be reviewed by an editor. This type of user is allowed to edit the content he/she created but modifications also need to be approved by an editor before they’re made public.

1.3.2.4 Vehicle Owner

A “Vehicle Owner” has the same access permissions as the authenticated user but can also create “Vehicle nodes”. The content created by this user role needs to be approved by somebody with an editor role.

1.3.2.5 Partner

A “partner user role” is dedicated to users working for one of the partner organisations and involved in the project. This type of user role can create and publish various node types.

1.3.2.6 Editor

An editor is allowed to place any kind of content public/private. This user role is responsible for the content management of the website.

1.3.2.7 Administrator

The administrator user role has access to all of the content and settings of the website. An administrator is responsible for the well-functioning of the website.

15/50


2 SitemapThe sitemap of the website gives an overview of the various pages present in the website. The first level of the sitemap is a representation of the main menu available at the top of the page except for the “global pages” which include “terms of use”, “privacy policy”,… pages which can be reached through various dialogs. Orange colored items in the sitemap are only accessible for partners. Green items will have content visible depending on the permission of the user. For example the “deliverables” section will show public deliverables for non-partner users (or anonymous users); partners will see all the deliverables available on the website.

2.1 FrontpageThe frontpage contains dynamic information about the project. The frontpage is used to quickly communicate information about the project and to show updates on the website. In 4.2 Frontpage (p38) two possible lay-outs and a list of content is shown.

2.2 About the projectThe “About the project” page contains basic information about the project. It gives the project mission, some short notes on plans/timeline, ambitions and methodology used. On this page there’s also a list of all the project partners logos and the last 3 newsitems posted to the website. Other content that can be included on this page are the public deliverables.

16/50

Sitemap

About the project

News & Events

Knowledge platform

Project Platform

My Account

Global pages

About the project

Mission Plans/Timeline Ambitions Methodology Partners Results

dashboard

deliverables

Contact


2.2.1 Mission“LNG Blue Corridors aims to improve knowledge and awareness of LNG as an alternative fuel for medium and long distance road transport.”

2.2.2 Plans/Timeline “The core of the project is the roll out and demonstration of four LNG Blue Corridors. This will include building 14 new LNG or L-CNG stations and building up a fleet of about 100 LNG Heavy Duty Vehicles which will operate along the corridors.”

2.2.3 Ambitions“The project will run for 4 years and will connect over 12 Member States and align itself with existing demonstrations running at national level.”

2.2.4 Methodology“LNG Blue Corridors unites the critical mass of experience in LNG transport and infrastructure technology. It involves cooperation between heavy duty vehicle manufacturers, fuel suppliers, fuel distributors and fleet operators.”

2.2.5 PartnersThe project partners are presented on the website in various ways. On the one hand there’s the block view which is used on the “About the Project” page directly. This block contains the logos of the various project partners. These logos link through to a detail page of the organization where the logo, name, contant info and project related information is shown.

Beside the block and the detail view, there’s also a list view of all the organisations where the logo, name, project related information (role within the project) and website link is shown. The name and the logo link through to the details page of the partner.

2.2.6 ResultsOn this page results of the project are posted. The structure of this page will depend on the exact outcomes of the various project stages.

2.2.6.1 Dashboard

The dashboard shows general statistics about the project like number of new/planned/realized stations within the project, number of kilometers tracked,tonnes of CO2-emissions avoided…

The tool for the collection of this information is separate from the website.

2.2.6.2 Deliverables

On this page a list of (downloadable) deliverables is shown. The list depends only shows the deliverables that are accessible to the user (eg. Partners can see the private deliverables on this page, anonymous users can only view the public deliverables). Deliverables will be made available as PDFs.

2.2.7 ContactThe contact pages contains contact information of the project responsible and contains a webform that can be used to contact the project coordinator.

17/50


2.3 News & EventsThe “News & Events” section of the website contains the latest news articles and events posted by partners and approved users.

2.3.1 NewsThis page gives a list of news items and events posted to the website.

2.3.2 NewsletterOn a regular basis a newsletter is send out with updates on the project. Users can subscribe and unsubscribe from the newsletter.

2.3.2.1 Subscribe/Unsubscribe

Screen where users can subscribe/unsubscribe from the project newsletter.

2.3.2.2 Newsletter Archive

A list of all the past newsletters as they have been mailed to users subscribed to the newsletters

2.3.3 Events2.3.3.1 Upcoming Events

List of upcoming events both related to the project as related to LNG in general

2.3.3.2 Calendar View

Overview of the events formatted as a (mont/week/year) calendar. A link to the iCal-feed will be provided on these pages

18/50

News & Events

News Newsletter

Subscribe/Unsubscribe

Archive

Events

Upcoming events

Calendar view

Past Events

Presentations

Press

Press releases

HQ-Images

Press Mentions

Promotional videos

Documents & Publications Social Meda


2.3.3.3 Past Events

Archive page of the past events.

2.3.3.4 Presentations

If for an event presentations are given and the slides have been provided by the speaker, they can be put under this section for later reference.

2.3.4 PressThe press section contains all the information that can be usefull for press agencies who want to write something about the project and will collect press-mentions about the project for future reference.

2.3.4.1 Press Releases

The press statements send out by the project when something newsworthy is made public.

2.3.4.2 High Quality Images

A series of high quality images that can be freely used by press agencies for their publications and which are related to the project.

2.3.4.3 Press Mentions

An overview of mentions of the project in the press.

2.3.4.4 Promotional videos

A list of videos made by the partners or which have been created by new agencies.

2.3.5 Documents and publicationsA list of all the documents (including deliverables) and (scientific) publications related to the project.

2.4 Knowledge PlatformThe knowledge platform collects all the public information that comes out of the project and provides usefull information related to LNG. Registered users can subscribe to this group and add their own content to the group. The content needs to be approved by reviewers before it is made public.

19/50


2.4.1 Refilling StationsThis is a list of all the refilling stations identified by the partners. This list is not limited to the refilling stations directly related to the project. Each refilling station has a location added to it and where possible some technical details about the station (type of connector; opening hours).

A descripting video will be introduced in this section to explain the performance station in terms of liquefied gas filling .

2.4.1.1 Overview

Overview of all the stations in list form.

2.4.1.2 Map

Overview of all the refilling stations in map form

2.4.1.3 Guidelines

An overview of guidelines which have come out of the project related to the construction and operation of refilling stations.

2.4.1.4 Best Practices

An overview of best practices identified by the project related to the construction and operation of refilling stations.

2.4.1.5 Add Location

The possibility for registered users to add a refilling station to the list. Depending on the user role, this location is made public immediately or needs to be reviewed by an editor.

20/50

Knowledge platform

Refilling stations

Map

Overview

Guidelines

Best Practices

Add Refilling station

Vehicles

Overview

Add your vehicle

Statistics

Organisations

Map

Addressbook

FAQ Links Forums


2.4.2 VehiclesThis section shows the various trucks running on LNG. Registered users can add their vehicle to the list.

This information will be completed during the first year of the project. Initially the trucks manufacture will provide info about €V version and finally in 2014 about €VI version. Both of them will be explained properly .

Moreover a descripting video will be introduced in this section to explain the different technologies in terms of liquefied natural gas regarding the truck brands participant in this project.

Public and private user can access to this information

2.4.2.1 Overview

List of all the vehicles collected.

2.4.2.2 Add Vehicle

Page to add a vehicle to the list.

2.4.3 OrganisationsOrganisations which are related to LNG trucks and can be useful for users.

2.4.3.1 Map

An overview map of the various organisations and their location.

2.4.3.2 Address book

An searchable list of organisations related to LNG Trucks

2.4.3.3 Add organization

Page for users to add organizations to the list. Content posted will be reviewed by an editor

2.4.4 FAQOverview of Frequently Asked Questions related to the project.

2.4.5 LinksA list of links to other projects related to LNG. This list will include links to EC document on LNGfication of the European fleet and links to other research activities.

2.4.6 ForumA general discussion forum with topics related to LNG Trucks. Topics can be created by registered users. Partners are motivated to participate actively in the forums (5.3 Guidelines to promote the forum)

2.5 My Account

21/50


2.5.1 Login/LogoutPage to login or logout of the website. If the user does not have login information he/she can create a login here.

2.5.2 My Profile2.5.2.1 View profile

The user can view his/her profile on this page.

2.5.2.2 Edit profile

The edit page of the profile. Users can add and review their information here.

2.6 Partner PlatformThe Partner Platform is only accessible and visible for partners. Within this organic group subgroups are created for each workpackage. Each partner is assigned to one or more workpackages. The partners can view all the content in all the workpackages but can only post in the workpackages they have registered for.

2.6.1 WorkpackagesA list of the various work packages and their description. The description of various WPs is readable for the general public. The content within the work packages is only visible to the partners unless specifically indicated otherwise.

22/50

My account

Login/Logout My profile

view profile

edit profile

My notes & Favourites My content

Partner platform

Workpackages Tasks

Overview of tasks

My tasks

Issue Queue Documents/Downloads Internal forum


2.6.2 TasksA list of all the tasks as defined in the project related to the workpackages.

2.6.2.1 Overview of tasks

All the tasks within the project.

2.6.2.2 My tasks

The tasks of the workpackages the partner is member of.

2.6.3 Documents2.6.3.1 List of documents

A list of all the public and private documents generated by partners.

2.6.3.2 Add documents

Page to add documents to the private section of the website

2.7 Global Pages

2.7.1 Terms&ConditionsGeneral Terms&Conditions related to the use of the website

2.7.2 Privacy PolicyThe Privacy Policy used related to the personal information of the users.

2.7.3 Cookie ComplianceNotification that the website uses cookies to track users (anonymously) for statistics and to improve user experience

2.7.4 FP7 DisclaimerDisclaimer about the financial support granted by the EC and that the information of on the website represents the views of the partners in the project and is not necessarily that of the European Commission.

23/50

Global pages

Terms & Conditions Privacy Policy Cookie Compliance Disclaimer


3 Content TypesA “Content Type” is a group of fields that together provide a in depth information about content. For example, an Image Content Type does not only contain the actual image but also has a title field, a description field, size field,…

Another example is an “Article Content Type”. This content type is defined by a title field, summary content field, full content field, published date, reviewed date, author field, url field,… The fields separate from each other do not provide useful information. When grouped together the information becomes useful.

By using various content types to collect information for the website and store this information in a database it is possible to link content together, create various views/representations of the content and limit the

3.1 Basic Content Page3.1.1 DescriptionThe Basic Content Page is used for static information on the website. This information is not regularly updated and contains general information like a description of the projects, the methodology used or information about the various work packages.

3.1.2 Functionality- Content can be placed in a review cyclus (Draft, Published, Needs Review) and

version management is in place. - Only “Editors” can change the content of these pages. - Basic Content pages can contain sub-pages (like books). - Basic Content pages can have a menu item assigned to them

3.1.3 FieldsTable 3-2 Basic Content Page Fields

Required Name Type Info

* Title Text

Body Long Text

Author User Reference

Workflow Status Dropdown Current state of the revision (published, needs review, draft,…)

3.1.4 PermissionsTable 3-3 Permissions for basic content page

Action Anonymous User

Authenticated User

Project Partner Editors

24/50


Create No No Yes (draft) Yes

Modify No No Yes (draft) Yes

Publish No No Yes Yes

3.2 Article3.2.1 DescriptionThe Article Node type is used for dynamic and time related information on the website. This includes news items, newsletters etc

The Article Content Page uses the following wireframes:

- 4.1.2 Basic Layouts


version management is in place. - Authenticated users can create draft versions and can change their draft content- Only “Editors” can publish the content of these pages.

3.2.3 FieldsTable 3-4 Basic Content Page Fields


* Title Text

Body Long Text


Link URL Link to the original content or to more in-depth information


3.2.4 PermissionsTable 3-5 Permissions for article


Authenticated User


Create No Yes (draft) Yes (draft) Yes

25/50


Modify No Yes (own/draft)

Yes (draft) Yes


3.3 Event3.3.1 DescriptionThe Event Content Page is used for event information. This content type has a date assigned to it. As soon as this date has passed the current date, the item is archived

The Event Content Page uses the following wireframes:


version management is in place. - Only “Editors” can change the content of these pages. - Event nodes have a date- Event nodes can be placed in a calendar- An iCal-feed for linking/importing in a calendar app is created.- Location fields, making it possible to place an event on a map.

3.3.3 FieldsTable 3-6 Event Content Page Fields


* Title Text

Body Long Text


Event type List Type of event (conference, workshop,…)

Date Date Start/End date of the event

Location Location/GeoData

Location where the event will happen


Section OG Group The section of the website the content belongs too and if it is visible to everybody or only to the members of that section

26/50


3.3.4 PermissionsTable 3-7 Permissions for events


Authenticated User


Create No Yes Yes Yes


Yes Yes


3.4 Refilling Station3.4.1 DescriptionA refilling station is a location based content type that contains information on places where LNG is available and where trucks can stop to refill. This content type can be created by various user roles but only partners can make this content type public after review. Refilling stations contain all the necessary technical information for truck drivers so they know if they can refill their truck at that location.

3.4.2 Functionality Technical information Location information “Get Directions to” functionality “Opening hours” of the refilling station Non-technical information (shop available etc) Export as CSV/XLS

3.4.3 FieldsTable 3-8 Fields for refilling station


* Title Text

Body Long Text


Owner Entity Reference

Link to an organization

Technical Parameters Various To be defined throughout the project

27/50


Non-technical Parameters

Various To be defined throughout the project

* Location Location field Can be an address or lat/long

Map Geofield

Get Directions Get Directions field

Opening Hours

3.4.4 PermissionsTable 3-9 Permissions for refilling station


Authenticated User




Yes Yes


3.5 Organisation3.5.1 DescriptionAn organisation can be any type of legal body which is related to LNG. Organisations are grouped in various categories. The information of the various partners is also collected in the organisations content type. Organisations typically contain a name, logo, category, contact information, linked users

3.5.2 Functionality Location Category Viewable on a map Can be linked to vehicles & refilling stations Public or private

28/50


3.5.3 FieldsTable 3-10 Fields for organisation


* Title Text

Body Long Text


Link with LNG? Long text Description on how the organization is linked to LNG for Trucks

Location Location field

e-mail Email field Not visible but can be used to contact an organization throught the LNGBC website

Category Term reference The category the organization is linked to

In Depth info Various To be decided throughout the project

Get Directions Get Directions field

Members User Reference Link to registered users on the website.

3.5.4 PermissionsTable 3-11 Permissions for organisation


Authenticated User




Yes Yes


3.6 Vehicle3.6.1 DescriptionA Vehicle content type describes a model of a certain brand. It contains field describing technical and non-technical specifications. It is not a unique vehicle and is preferably freely available on the market.

29/50


3.6.2 Functionality- Overview list- Filters according to specifications- Can be added by registered users- Part of approval workflow- Export as CSV/XLS

3.6.3 FieldsTable 3-12Fields for vehicle


* Model Text Model+/type identification

Body Long Text


* Brand Entity Reference

Link to organization

Technical specs Various To be decided

Non-technical specs Various To be decided

Image File field

3.6.4 PermissionsTable 3-13 Permissions for vehicle


Authenticated User




Yes Yes


3.7 FAQ3.7.1 DescriptionFAQ or Frequently Asked Questions are used as a question and answer tool. It contains a question that is posed often and a standard reply to that question. All users can indicate if a answer was usefull or not. This functionality is used to finetune the answers

30/50


3.7.2 Functionality- List view- Flag as usefull

3.7.3 FieldsTable 3-14 Fields for FAQ


* Question Text

* Answer Long Text

Was this usefull flag

3.7.4 PermissionsTable 3-15 Permissions for FAQ


Authenticated User




Yes Yes


3.8 Document3.8.1 DescriptionA document is a content type that contains a file (like attached pdf). It is used to make content available for download to the general public. This content can be of various natures like a public deliverable, high quality images, press releases, brochures, posters, logos,...

It is part of version management and a review cyclus. Only editors can add content to this section of the website.

3.8.2 Functionality- Review workflow- Has attachement- Filterable list

31/50


3.8.3 FieldsTable 3-16 Fields for document


* Title Text

Body Long Text Description of the document

Document Type List Deliverable, presentation,…

Attachement File field

3.8.4 PermissionsTable 3-17 Permissions for document


Authenticated User


Create No No Yes Yes

Modify No No Yes Yes


3.9 Forum3.9.1 DescriptionA forum is a public place, inside the website, to discuss various topics about LNG field. Depending on the user role, different functionality will be made available (like allow to post without approval, remove messages,...).

Like it has explained previously, LNG as fuel has been considered an alternative for diesel in long distance on road in the last years.

The main obstacle to use this kind of vehicles is to have enough infrastructure to use them throughout Europe as well as the unknowledge with this regard.

This technology is not very known for the time being. For that reason, using this forum is a good way to share information about LNG vehicles, learn the different technologies implicated and their emissions, discuss the future station in some specific zone and at the same time, analyze reduction of cost compared to diesel vehicles.

Public and private user can access to this forum.

3.9.2 Functionality- Public forum (readable for anonymous users; registered users can reply to topics

32/50


- Private forums (only invited users can participate. Used for example for discussions between partners)

- Topics can be closed for comments

3.9.3 FieldsTable 3-18 Fields for forum


* Title Text


Forum List Which part of the forum the topic is part of

Group Audience OG Content To which organic group the topic belongs. Used to define default visibility (private/public)

Group Visibility OG Visibility Indicates if the group is public or private

3.9.4 PermissionsTable 3-19 Permissions for forum


Authenticated User




Publish No Yes Yes Yes

3.10 Newsletter3.10.1 DescriptionNewsletters are a content type which can be mailed to people related to natural gas environment. The subscribers don’t need to have a user account. The newsletter can be manually or automatically (tbd) filled with information like the latest articles, upcoming events,...

3.10.2 Functionality- Subscribe/Unsubscribe from newsletter- Newsletter categories (eg. vehicle info, tech info,...)- If automatic: interval between newsletters (weekly, monthly, quarterly,...)

33/50


3.10.3 FieldsTable 3-20 Fields for newsletter


* Title Text


Date Date Date of the newsletter

Category Term Reference

3.10.4 PermissionsTable 3-21 Permissions for newsletter


Authenticated User





3.11 Issue/Task3.11.1 DescriptionAn issue is a content type that is only available to partners. It is used to track problems, open task, deliverables unresolved, etc. An issue can be assigned to a specific user who can then indicate the progress/work done on the specific issue. Other users can comment and discuss on the topic and provide more information.

A task content type describes actions that need to be taken during the project and belong to the same. A task describes the job to do in a period of time, in which can arise different issues. It describes the various tasks of the project (like deliverables) and indicates their current status. Each task can have several issues related to it and can have subtasks. Email reminders can be send about the task to the task owner

Since most of the fields between Issues and Tasks are alike, this has been merged into one content type. A task is something that needs to be done. An issue is something that is blocking the execution of a task.

3.11.2 Functionality- Assign to a specific user

34/50


- Due date- Importance indication- Filterable list

3.11.3 FieldsTable 3-22 Fields for task/issue


* Title Text


Type List Task/Issue

Owner User Reference Person responsible for the task or person who created the issue

Progress Decimal Indicated the progress of a task/issue in %

Importance List Critical/High/Normal/…

3.11.4 PermissionsTable 3-23 Permissions for task/issue


Authenticated User





Assign task to other user

No No Yes Yes

3.12 Group3.12.1 DescriptionA group is used to create separate parts of the website like a group focused on a certain topic with its own permissions or the private partner section. Content published within a group followes the visibility rules of the group. If a group is private then only members of the group can see the content. If the group is public, the content can be viewed based on permissions on site level.

35/50


Only administrators can create a group. They can assign “group managers”. A group manager can approve and add members to the group

3.12.2 Functionality- Group content- Private/Public Groups

3.12.3 FieldsTable 3-24 Fields for Group


* Title Text


Group Visibility OG Visibility Indicates if the group is public or private

Group Subscribe OG Subscribe Makes it possible to subscribe to a group

Group Content OG Content Allowed content types in the group

3.12.4 PermissionsTable 3-25 Permissions for group


Authenticated User


Create No No No Yes


Publish No No No Yes

36/50


4 Wireframes“A website wireframe, also known as a page schematic or screen blueprint, is a visual guide that represents the skeletal framework of a website. Wireframes are created for the purpose of arranging elements to best accomplish a particular purpose. The purpose is usually being informed by a business objective and a creative idea. The wireframe depicts the page layout or arrangement of the website’s content, including interface elements and navigational systems, and how they work together. The wireframe usually lacks typographic style, color, or graphics, since the main focus lies in functionality, behavior, and priority of content. In other words, it focuses on what a screen does, not what it looks like. Wireframes can be pencil drawings or sketches on a whiteboard, or they can be produced by means of a broad array of free or commercial software applications. Wireframes are generally created by business analysts, user experience designers, developers, visual designers and other roles with expertise in interaction design, information architecture and user research.

Wireframes focus on:

The kinds of information displayed The range of functions available The relative priorities of the information and functions The rules for displaying certain kinds of information The effect of different scenarios on the display

The website wireframe connects the underlying conceptual structure, or information architecture, to the surface, or visual design of the website. Wireframes help establish functionality, and the relationships between different screen templates of a website. An iterative process, creating wireframes is an effective way to make rapid prototypes of pages, while measuring the practicality of a design concept. Wireframing typically begins between “high-level structural work—like flowcharts or site maps—and screen designs.”Within the process of building a website, wireframing is where thinking becomes tangible.

Aside from websites, wireframes are utilized for the prototyping of mobile sites, computer applications, or other screen-based products that involve human-computer interaction.”2

4.1 General4.1.1 Content RegionsContent regions are areas of the webpage where content can be placed. Some of the content is fixed for all pages (eg. Logo); other content varies with each page (eg. Article content). The position of the regions also depends on the screen size of the device the website is viewed on. On mobile devices for example, the menu will become a dropdrown; the small footers will be place underneath each other instead of next to each other. Since the website will most of the time be viewed on a desktop computer, only those wireframes and the layout on this type of screen is shown.

2 Definition according to Wikipedia: http://en.wikipedia.org/wiki/Website_wireframe

37/50

http://en.wikipedia.org/wiki/Website_wireframe


Table 4-26 Wireframe Content Regions

1. Logo position2. Main menu3. Breadcrumbs4. Search box area5. Highlights (used for eg. Slideshow

on the frontpage)6. Content (main content region)7. Footer1-Footer48. Footer (fixed footer for privacy

statement, term of use, copyright notice,…)

4.1.2 Basic Layouts4.2 Frontpage

The image below shows the structure of the homepage. At the top there’s the main menu which will be visible on all the other pages. Below is a slideshow with quick and visual information on the project. Below that is the latest news item and an overview of the 3 latest newsitems to the right of it. This last list will start from the second to last newsitem.

Below the news section is some fixed information on the project with an overview map of the refilling stations available.

The content of the footer section is not decided yet. This area can contain fixed content like quick links to parts of the website, registration/subscription links,...

38/50

1 23 4

5

6

78


Table 4-27 Frontpage layouts

1. Main menu2. Slideshow with visual information

on the project and call for action3. Latest news item4. 3 latest news/events posted on the

website5. Short note about the mission of the

project with link to “About the project” page

6. Short note on methodology/ambition/…

7. Overview map with all the available LNG refilling stations and link to overview page

8. Contact info9. Disclaimer FP710. Sitemap11. Links to other LNG sites

1. Project Mission2. Our plans, our ambitions, our

approach3. Slideshow with call for action or

basic info on the project4. Overview map of refilling stations5. Latest news/events6. Footer content (zie 8-11 above)

39/50

1

3

2

4

5 6 7

8 9 10 11

13

2

45

6


4.3 About the project4.3.1 General Page

Table 4-28 About the project overview page

1. Project Mission Statement2. Our plans, our ambitions, our

approach3. Partner logos linking to detail page

of each partner4. Latest news/events posted to the

website

4.3.2 Partners ListTable 4-29 List of partners

1. Filter list of parters based on various parameters

2. Partner logo3. Partner name4. Description of the role of the

partner within the project

40/50

4321

4321


4.3.3 Refilling Stations ListTable 4-30 Refilling stations list + alternative

1. Overview map with all the refilling stations. Clicking on a pointer shows name + location of the refilling station

2. Filters3. List of refilling stations matching

the filter criteria

1. Filters2. Individual map of the refilling

station3. Name of the refilling station4. Extra information on the refilling

station

41/50

321

4321


4.4 News & Events4.4.1 News Page4.4.1.1 News detail

Table 4-31 Detail of a article/news item

1. Filter content2. Images related to the content of the

article/event3. Full article content

4.4.1.2 News list

Table 4-32 List view of articles/news


article/event6. Short description of the

article/event

42/50

321

321


4.4.2 Newsletter4.4.2.1 List

Table 4-33 Newsletters list


newsletter3. Short description of the newsletter

4.4.2.2 Detail

The format of the newsletter is used both for online viewing as for the emailed newsletter.

Table 4-34 Detail of a newsletter

1. Title of the newsletter2. Main articles in the newsletter3. News from the LNG sector4. LNG Related events5. Contact information project

coordinator6. Unsubscribe links + disclaimer

43/50

1 2 3

12 3

4

56


4.4.3 Events Page4.4.3.1 Event detail

Table 4-35 Event details


article/event3. Full event content

4.4.3.2 Event list

Table 4-36 Event list


article/event3. Short description of the

article/event

44/50

1 2 3

1 2 3


4.5 Organic Group PageThe Organic Group page is related detailed view of an Organic Group. It relates to the following items in the sitemap:

- 2.4 Knowledge Platform- 2.6 Partner Platform- 2.6.1 Workpackages

Table 4-37 Organic group wireframe

1. Group image2. Group Description3. Links to create content in the group4. List of group members

(name+picture)5. Paged list of group content

45/50

1 23

4

5


5 User flows5.1 User Registration Flow

Figure 5-1 User registration flow

1. The user starts the login/registration process.

2. If the user already has an account he can input his username and password.

3. If the username and password are correct the user is logged in to the website and send to his profile page

4. If the username or password are incorrect an error message is shown and the user will be asked to re-input his credentials. A link to register is also provided.

5. If the user does not have a username or password yet he can register on the website by filling in some required field.

6. The user input data is stored and the administrator of the website is notified of the new user registration

7. The admin approved/blocks the new user.

8. If the admin approves the new user a message is send to the new user with a one-time login link. If the new user is blocked by the admin nothing will happen and the new user will not receive login information.

9. When approving a new user, the admin assigns a user role for the new user

10. The new user receives a one-time login for his account and can set his password. After setting his password he is logged in to the website and can start using advanced functionality of the website.

11. In case the user is block, the user information is stored in the database but the user will not be able to login anymore

46/50


5.2 Content Creation FlowUsers can create different types of content depending on their user role. Also depending on their user role, the content created by them will go through an approval cyclus. The flow of the content creation is shown on the right.

1. User initiates the content creation by selecting the type of content he want to create.

2. The user fills in all the required and non-required fields and submits the content.3. The content is saved as a draft and is only visible to the user who created the

content (author) and users with specific permissions to see draft content.4. A notification is send out to editors (users with permission to see and edit draft

content)5. An editor reviews the content and approves or disapproves the content.

o If the content is approved the content is made visible to all the people who have permission to see the content and the process is ended

o If the content is not approved by the editor, the creator is notified of this with tips/suggestions for improvement.

6. Content is edited by the author and resubmitted in the workflow. The workflow starts over from point 4.

Figure 5-2 Content generation flow diagram

5.3 Guidelines to promote the forum

47/50


Below is a list of guidelines which will be kept in mind related to activating the forum and keeping it active.

- Partners are asked to actively participate in the forum and answer questions on the forum.

- Interesting topics will be posted by the partners on a regular basis- Partners are also asked to actively participate in other forums/blogs related to the

topic of the project.- Guest “bloggers” who are specialist on a certain related topic will be asked to

write a forum topic to discuss on a regular basis.- Possibility to share forum posts on social media- Automatic posting to LNGbluecorridor twitter account. - Contributing to Wikipedia on topics related to LNG

48/50


ReferencesList of Tables

Table 1-1Overview of field types......................................................................................12Table 3-1 Basic Content Page Fields.................................................................................25Table 3-2 Permissions for basic content page...................................................................26Table 3-3 Basic Content Page Fields.................................................................................26Table 3-4 Permissions for article.......................................................................................27Table 3-5 Event Content Page Fields................................................................................27Table 3-6 Permissions for events......................................................................................28Table 3-7 Fields for refilling station...................................................................................29Table 3-8 Permissions for refilling station.........................................................................29Table 3-9 Fields for organisation.......................................................................................30Table 3-10 Permissions for organisation...........................................................................31Table 3-11Fields for vehicle..............................................................................................31Table 3-12 Permissions for vehicle...................................................................................32Table 3-13 Fields for FAQ..................................................................................................32Table 3-14 Permissions for FAQ........................................................................................32Table 3-15 Fields for document........................................................................................33Table 3-16 Permissions for document...............................................................................33Table 3-17 Fields for forum...............................................................................................34Table 3-18 Permissions for forum.....................................................................................35Table 3-19 Fields for newsletter........................................................................................35Table 3-20 Permissions for newsletter..............................................................................35Table 3-21 Fields for task/issue........................................................................................36Table 3-22 Permissions for task/issue...............................................................................37Table 3-23 Fields for Group...............................................................................................37Table 3-24 Permissions for group.....................................................................................38Table 4-1 Wireframe Content Regions..............................................................................40Table 4-2 Frontpage layouts.............................................................................................41Table 4-3 About the project overview page......................................................................42Table 4-4 List of partners..................................................................................................42Table 4-5 Refilling stations list + alternative....................................................................43Table 4-6 Detail of a article/news item.............................................................................44Table 4-7 List view of articles/news..................................................................................44Table 4-8 Newsletters list.................................................................................................45Table 4-9 Detail of a newsletter........................................................................................45Table 4-10 Event details...................................................................................................46Table 4-11 Event list.........................................................................................................46Table 4-12 Organic group wireframe................................................................................47

List of figuresFigure 5-1 User registration flow.......................................................................................48Figure 5-3 Content generation flow diagram....................................................................49

49/50

Partners

http://www.idiada.es/

http://www.ballast-nedam.nl/

http://www.cloud-energy.eu/

http://www.crf.it/

http://www.drivesystems.be/

http://www.eihp.hr/

http://www.eni.com/

http://www.enoslng.si/

http://www.erdgas-mobil.de/

http://www.fluxys.com/

http://www.galpenergia.com/

http://www.gasrec.co.uk/

http://www.gasnaturalfenosa.com/

http://www.gnvert-gdfsuez.com/

http://www.sonorgas.pt/

http://www.ham.es/

http://www.hardstaffgroup.co.uk/

http://www.iveco.com/

http://www.linde-gas.com/

http://www.mendyra.com/

http://www.tmonfort.es/

http://www.ngvaeurope.eu/

http://www.corporate.renault-trucks.com/

http://www.energigas.se/

http://www.vito.be/

http://www.volvotrucks.com/

http://www.westport.com/