European Commission - Specific RTD Programme in the field of Information Technologies

SPECIFIC INFORMATION
DOCUMENT

ESPRIT
Demonstration Actions
Continuous Submission

"Supporting the growth and the spread of the Information Society"

February 1997

CONTENTS

1. Introduction

1.1. Objectives

1.2. Scope

1.3. Topics

1.4. Organisation of work

2. Participation

2.1. Rules on Participation

2.2. Financial and Contractual Conditions

3. Evaluation, Format and Criteria

3.1. The evaluation and selection process

3.2. Questions to be answered in a Proposal

3.3. Proposal preparation and evaluation criteria

4. Submitting a Proposal

5. Further Information

6. Annexes

Form 1 : Proposal Administrative Summary

Form 2 : Individual Participant Profile

List of Codes

Acknowledgement of Receipt Form

Glossary

7. List of National Contact Points

1. Introduction

This document introduces procedures and rules for preparing proposals for demonstration actions in the Esprit programme. It may relate to task 0.7 and 5.16 of the Work programme and any of the programme domains.

• Software Technologies (ST),
• Technologies for Components and Subsystems (TCS),
• Multimedia Systems (MS),
• Long Term Research (LTR),
• Open Microprocessor Systems Initiative (OMI),
• High Performance Computing and Networking (HPCN)
• Technologies for Business Processes (TBP), and
• Integration in Manufacturing (IiM).

Proposals are called for under a single-step evaluation process and can be submitted continuously during the period indicated in the relevant Call for Proposals.

Proposers who want to prepare an R&D; proposal need to consult the separate Specific Information Documents for R&D; Proposals.

A number of Specific Information Documents is made for proposals for other types of Preparatory, Support and Technology Transfer Activities than Demonstration Actions.

Proposers who are new to Esprit are advised to refer first to the Introduction for Proposers and the Work programme of Esprit.

All documents are available on request at the Esprit Information Desk:

Tel: +32 2 296.85.96 Fax: +32 2 296.83.88 E-mail: Esprit@dg3.cec.be

or at the Webpage

/esprit/home.html

1.1 Objectives

The objective of Esprit is:

"to provide and demonstrate the technological building blocks for information society applications and for application in industry to strengthen the competitiveness of all EU industry."

Demonstration actions within the programme aim at:

• demonstrating the applicability and usability of available Information Technologies, its relevance and potential for industry's competitiveness, and more generally for building the Information Society
• stimulation and promotion of the rapid take-up of IT R&D; results in industry, in particular SMEs.

1.2 Scope

Proposals prepared following this document should fit within the overall scope of the IT programme and comply with the objectives as given above.

R&D; projects in the Esprit programme may include demonstration of their results. Moreover, best practice first user or specific demonstration activities in the programme (see Esprit: An Introduction for Proposers) add to the above objectives. Please consult other Specific Information Documents for such actions.

Demonstration actions prepared according to this document refer to task 0.7 and 5.16 of the Work programme and should not duplicate Support and Transfer activities described in other tasks in the Work programme. It should complement and enhance such activities by addressing other topics or multiple domains in the Esprit Work programme.

The activities could include organisational or promotional measures to enhance the effect of the demonstration or reach a wider audience.

Demonstration actions could be building on the R&D; results produced in the Esprit programme but may also relate to other available technology. It may include the introduction in certain industrial sectors of mature technology available on the market, and to demonstrate best practice in its use. It may also include cooperation of potential vendors and users in demonstrating applicability of proto-type technology in representative user environments to the benefit of the user and the group they represent, and the vendor to prepare or extend its potential market.

European wide impact of Esprit demonstration actions is crucial. This could be clear from European-wide cooperation in the group of proposers, eg. by technology providers from certain member states, and demonstrating user companies in another member state. However it is allowed to submit a proposal as a single organisation if it would be more appropriate to conduct the action by one organisation, and it is demonstrated beyond any doubt that the action is of European-wide relevance.

Proposers must be aware of the ongoing Esprit activities and either propose in synergy with them or provide evidence in justification of a different complementary approach.

1.3 Topics

All demonstration actions must relate to the topics of the Esprit Work programme. It could be:

• Single Demonstration Actions, which do not fit in any of the other support and transfer activities described in the Esprit Information package and which aim at demonstration of specific IT results in certain industrial sectors.
• Coordinated clusters of demonstration activities. Each of the activities might be conducted by one organisation or in one country, but the coordinated cluster is transnational and has a clear added value at the European level.

Such clusters are either proposed as a cluster or, in case the coordination mechanism has already been set up by the Commission the individual activities are proposed directly by one organisation. An example of the latter is given below.

OMI small demonstrator projects for SMEs (task 5.16)

The main objective of the Open Microprocessor systems Initiative (OMI) is to provide Europe with a strong capability in efficient, cost effective, and re-usable microprocessor systems design through the development of an open environment for design, application and production of microprocessor systems, with particular emphasis on embedded systems.

OMI small demonstrator projects for SMEs are an important validation of the OMI open systems approach and are aimed to stimulate the improvement of design of products and processes in SMEs. They are addressed specifically to small system houses and small end user system developers. SMEs should implement best practice in the development and application of microprocessor based systems, hardware and software. This includes the use of better design tools or methodology, use of more advanced technology for higher integration, higher performance or increased functionality. Emphasis in these demonstrator projects should also be placed on organisational issues as well as the methodologies, tools and technology.

Examples of demonstration of the OMI approach could include:

• Integration of a core CPU and FPGA (Field Programmable Gate Array) at board level
• Migration from proprietary, in-house operating systems to open kernel systems
• Adoption of architecture neutral techniques and components to improve software portability.

Demonstrator projects in any of the application domains indicated in task 5.9 of Domain 5 - OMI (see Esprit Work programme) may be proposed as OMI small demonstrator projects.

1.4 Organisation of work

Proposed actions should work towards concrete results and must from the outset have clear implementation plans. Actions should be compact and comprise the minimum number of partners necessary to execute the work. Unnecessary duplication of skills and activities should be avoided.

Proposers should prepare their proposals in accordance with the structural recommendations and evaluation criteria given in section 3 of this Specific Information Document. All the necessary administration forms required to submit a proposal are provided in the accompanying annexes or available on diskettes. or on the Esprit Web pages.

2. Participation

2.1 Rules on Participation

From EU member states

The programme is open to all legal entities - i.e. people and organisations - established and carrying out RTD activities in the Member States of the European Union (industrial firms both large and small enterprises aimed at bringing products and services to the market - universities, higher education institutes, research organisations, etc.), and to the Joint Research Centre of the EC.

The group of proposers should normally contain at least two non-affiliated participants from different member states or from one member state and one state associated and financially contributing to the Programme. Proposals from one organisation are acceptable if the European added value of the proposal is demonstrated beyond doubt, or it forms part of a EU wide demonstration cluster (eg. for OMI small demonstrator projects). SMEs proposing OMI small demonstrator projects may seek support from OMI User Support Nodes (see Specific Information Document on OMI User Support Network & Management Organisation).

From associated and financially contributing states

Participation in this programme, with financial contribution from the EU, is open to any legal entity established or carrying out RTD activities in a third country associated with and contributing financially to the implementation of this Programme.

These are currently: Iceland, Israel, Liechtenstein and Norway.

From other European countries, Australia, Canada and South Africa

Legal entities established and carrying out RTD activities in other European countries or in countries who have concluded an S&T; agreement with the EU (not financially contributing as described above) may participate in the programme on condition that:

• the participation is in the interest of EU policies
• the minimum stipulated number of legal entities from the EU and associated and financially contributing states are involved

These states are at printing date: Albania, Armenia, Azerbaijan, Belarus, Bulgaria, Cyprus, Czech Republic, Estonia, Georgia, Hungary, Latvia, Lithuania, Malta, Moldavia, Poland, Romania, Russia, Slovakia, Slovenia, Turkey and Ukraine, for which financial support by the EU, would in the case of acceptance of the proposal, normally be provided from funds other than the Esprit budget (an explicit request for such funding has to accompany the proposal).

Swiss, Australian and Canadian organisations may participate under the above conditions, but without funding from the EC. It is expected that agreement with South Africa will be reached in early 1997, so that organisations from South Africa may from then on also participate under the above conditions without EC funding.

Organisations from other states

Legal entities established in states other than above listed, may participate on condition that:

• the participation contributes effectively to the implementation of the Programme and provides mutual benefit to the interests of the EU and the state concerned
• the minimum stipulated number of legal entities from the EU or associated and financially contributing states are involved

Organisations from Japan, Korea, New Zealand, Taiwan and the USA are not eligible for funding from the EU.

For organisations from other countries, financial support by the EU may be provided from funds other than the Esprit budget. An explicit request for such funding has to accompany the proposal.

International organisations

International Organisations may participate on condition that:

• the participation contributes effectively to the implementation of the Programme
• the minimum stipulated number of legal entities from the EU or associated and financially contributing states are involved

Financial support from the Esprit Programme may be provided to international organisations situated in Europe on a case by case basis. An explicit request for such funding has to accompany the proposal.

2.2 Financial and Contractual Conditions

If your proposal is successful in the evaluation and is selected for further negotiation, the Commission services will contact you for finalisation of the Project Programme and budgetary aspects.

The Project Officer assigned to be the responsible Commission official will provide you with the necessary documentation. The time needed in this phase depends on the complexity and evaluators' comments, but normally negotiations would take between 4 and 8 weeks if the work is well planned by the consortium.

The contract to be used for Demonstration actions will normally be a standard shared cost RTD contract or an Accompanying Measure contract.

The contract provides explicit definitions of the partnership, the reporting obligations, the allowable costs and other financial conditions and the intellectual property rights conditions. The contractual terms cannot be overruled by a consortium agreement, but the latter is recommended to provide further detail for the consortium on management and exploitation aspects.

Some essential contractual/financial aspects for the contracts are the following:

• The Commission may contribute up to 100% of the allowable cost of the action. Allowable costs are normally restricted to the additonal cost needed to implement the action. Labour costs are allowed; equipment costs for equipment which is supposed to be extra costs for the implementation of the demonstration can be included, travel and meeting costs, dissemination, promotion and communication costs could be allowed.
• Labour cost would include actual salaries and social charges, but normally none or only limited overhead costs.
• For all costs it must be demonstrated that they are actually extra costs to implement the demonstration. Those costs which do only relate to the introduction of new technology in the users enterprise are not allowable, nor do normal marketing costs of technology providers.
• If the Commission contributes 100% of allowable costs, the consortium must normally give the copyright on, or ownership of, any results of the action to the Commission.

The Commission has published an information booklet concerning the contracting conditions and the standard contract. You can obtain this booklet by request from :

**** e-mail: info-dg12@DG12.cec.be; fax: +32/2 295 82 20 ****

3. Evaluation and Criteria

3.1 The evaluation and selection process

The ESPRIT programme has procedures for both one and two step proposal submission and evaluation.

The submission and evaluation of the proposals as described in this information package will be done in a single step. Proposers must submit a full proposal before any evaluation takes place.

All proposals are evaluated by a panel of specially selected experts who are all bound by a confidentiality agreement and a code of conduct to avoid conflicts of interest. The evaluation will be exclusively based on the criteria set out in this section and will include assessment of the conformity of the work with the objectives and topics as stated in sections 1.1 and 1.3 of this Specific Information Document. The evaluation will be carried out under the responsibility and co-ordination of the Commission who will also interact with associate Programmes, e.g. Telematics Applications, ACTS, IMT.

3.2 Questions to be answered in a Proposal

When making a proposal, proposers should ask themselves the following questions:

• Why is the proposed work needed?
• What does it deliver?
• Who does the work?
• How is the work performed?

The Why

The industrial relevance concerns the industrial context the proposal refers to, including market situation, needs and opportunities, technical state-of-the-art, and outstanding problems.

The What

The objectives set the specific business and technical targets to be achieved by the proposers, whereas results define the concrete outcomes of the project. They should be innovative within their specific industrial context and provide benefits to a wider community than solely the proposers themselves.

The Who

The proposers include both individual proposers with their profiles and skills and their collaboration, where synergism among partners roles should appear. The soundness of the proposing group is not limited to the technical ability to perform the work, but includes aspects such as whether the work is in-line with the core business of proposers and whether business co-operation among participants is possible, credible and potentially successful.

The How

Exploitation planning addresses the ways to achieve business objectives and provide the expected benefits during and after the project, whereas the work planning mainly concerns the identification of activities needed to achieve technical objectives and how they are co-ordinated with the business aspects.

Duration and resources concerns the staffing and time scale of activities identified in the work plan, whereas Project management focuses on how all the components above are managed to achieve success.

You should keep the above basic questions in mind while fulfilling the criteria detailed below. These criteria address the different aspects of a proposal in detail, and will be used by the expert evaluators to assess how it answers the basic questions above, while conforming with the scope and objectives of the Programme and showing the necessary European-level added value.

The criteria are designed to provide a fair, practical and consistent way of establishing to what extent proposals meet the goals of Esprit. The same set of criteria are used in all evaluations of Industrial R&D; proposals.

3.3 Proposal preparation and evaluation criteria

In this section we will specify the recommended structure of, and the evaluation criteria which need to be satisfied by proposals.

A proposal is comprised of two parts :

Part 1: providing the administrative and financial data

Part 2: providing the technical description of the proposed project.

You may submit proposals in any official language of the EC. However, it is appreciated to supply at least the summary in English as this will assist the speedy evaluation of proposals.

The description of the proposal structure given below, includes the criteria which have to be addressed in each of the sections. Certain criteria might be addressed in several sections. In such cases it is advised to refer in the relevant section to other places in the proposal which should be taken into account for assessment.

Part 1: administrative and financial data

To complete Part 1 of the proposal you need to complete all the forms as given in Annex 1. You can obtain an electronic version of these forms on a diskette or download it from the Esprit Web pages. You are strongly recommended to use this method of data preparation and send the prepared diskette along with the proposal.

If you use the diskette or Web software to prepare a diskette, it will make it easier to fill in the data correctly. You can also make clear print-outs and it will help Commission services to enter your data quickly in their database. Of course, you may complete the paper forms, or the forms as they are provided by other programmes for RTD Project proposals, as these contain the same questions. In either case, please follow carefully the detailed instructions.

A complete Part 1 comprises :

• The duly completed forms 1a, 1b and 2 as given in the Annex A
  • Form 1a must include the signed declaration of the co-ordinator concerning possible involvement of his organisation in other related or similar proposals in the same or other Calls, in Esprit or other EC programmes.
  • Form 1a must also contain a short (max. 1,000 characters) project synopsis. This will be used by both programme staff and external evaluators during the evaluation and will be copied on the evaluation reports provided to the Member State Committee. It should state what is covered in the proposed project, its rationale and importance.
    Please note that the Commission will not edit or reduce the synopsis in any way. If the synopsis is longer than 1,000 characters, all characters above this will be lost automatically.
  • Form 1b must present the proposal resource breakdown per partner as well as other administrative information concerning the proposal.
  • Form 2 must be completed by each participant, including associate partners, and present the individual participant profiles.
• A written statement of each participating organisation, signed by a representative of the organisation duly empowered to do so, and authorising its participation.

Part 2: Description of the Proposed RTD Project

Part 2 (your project description) should follow the recommended structural outline given below and provides all the information requested in not more than 30 pages. It should contain the following sections:

• Technical summary
• Project objectives and scope
• Industrial relevance
• European dimension
• Project work plan
• Exploitation plan
• Project management
• The proposers
• Duration and resources

The description of these sections as well as the criteria used for assessment are given below. Evaluators will be asked to use these evaluation criteria to assess your proposal.

It goes without saying that evaluators are best helped in conducting their task if the information provided is concise and follows the recommended structure. Any irrelevant information should be avoided.

Technical Summary

This section should be one page and should capture the essence of the proposal. It should summarise :

• The technical and business objectives, the approach and the expected technical and exploitable results (WHAT)
• The position of results in the target market segments, and their match with an actual or anticipated industrial demand (WHY).
• The structure of the consortium and the role of partners (WHO).

Note: This may be a copy of the 1000 character summary given in Part 1 (form 1a).

Project Objectives and Scope

The rationale for the project should be clarified. In particular:

• the specific measurable project objectives and how they will be measured (yardsticks)
• the technical state-of-the-art followed by the methodologies and technologies being used and developed in order to achieve the project results.

Criteria to be addressed in this section are:

• Does the proposal fall within the scope and objectives of the IT programme and its work programme
• Does the proposal fall within the scope of the Call to which it applies
• Does the proposal comply with the objectives as described in section 1 of this document
• Does the proposal comply with a topic described in section 1 of this document and in particular with one of the Esprit Work programme tasks or themes
• Does the proposal clearly describe the technical objectives, show progress with current state of the art and define appropriate means to measure their successful achievement
• Does the proposal clearly describe the foreseen business and industrial objectives and describes how they will be attained from the technical results

Industrial relevance and impact on society

Important aspects are:

• the industrial context, the market opportunities and the potential industrial impact
• an analysis of the market situation including main segments
• the needs and opportunities with an analysis of foreseen competition

Criteria to be addressed in this section are:

• Do proposers demonstrate a clear view of the relevant market segments and their current position in those segments
• Do proposers show awareness of the status of their main competitors in the relevant market areas and include in their proposal, where appropriate, a quantified analysis of the market opportunity
• Do proposed results clearly relate to existing or anticipated industrial demand and identifiable market requirements
• Is the potential impact on industry sectors and on working conditions outlined.
• Do the results lead to innovations in goods, services or production processes and are the benefits of such innovations significant and clearly described
• Is the relevance of the results to the information infrastructure and its potential impact on society convincingly demonstrated

European dimension

Address the relevance of the work to the competitivety of European industry and the interdependence with ongoing national, European or international programmes

Criteria to be addressed in this section are:

• Are the rules on participation as defined in section 2.1 satisfied.
• Does the proposal show a clear added value in carrying out the proposed work at European level
• Where appropriate, have proposers described dependencies on related projects or proposals carried out within national, European or international programmes

Project Work plan

Describe concisely the work planned to achieve the objectives of the project and include the following elements :

• introduction and analysis of the work
• structured description of the work defined as work packages, tasks with identification of partner contributions and responsibilities
• description of timetable of deliverables, milestones, and expected results (e.g. prototypes, reports, etc.)
• bar & pert charts to illustrate the sequence and dependencies of the planned work

Criteria to be addressed in this section are:

• Is a clear presentation given of major development phases, associated milestones and deliverables, and are they clearly related to the stated project objectives.
• Are proposed results and deliverables assessable and are quantitative yardsticks provided against which to measure the project progress.
• Are tasks, including those related to information dissemination and exploitation of results, clearly defined and scheduled, and their inter-dependencies identified.
• Is the contribution of each participant unambiguously related to the work packages by indicating their technical contribution and commitment of effort to each of the tasks.
• Are major technological risks identified and sound contingency plans formulated.

Exploitation plan

Outline the consortium's strategy for exploitation of the foreseen project results. It should include the exploitation plans of each of the partners in terms of :

• identification of exploitation and definition of products
• positioning in, and monitoring of, the relevant markets
• IPR strategies
• how the transition from R&D; to commercial exploitation is planned
• plans for dissemination of results and promotion actions to obtain a wide audience; in particular OMI small demonstrator actions should produce a final report that can be disseminated Europe-wide
• plans to encourage the take up of pre-normative results
• how the plan will be reviewed and updated

Criteria to be addressed in this section are:

• Does each partner demonstrate the ability to make significant own investment in the proposed developments, and explain the expected return on investment.
• If a technology vendor is involved, does the demonstration form part of a convincing exploitation strategy of this proposer
• Does the proposal describe possible arrangements, including IPR issues, between partners
• Does the proposal describe relevant information dissemination activities and how the planned exploitation would benefit from them.

Project management

The project management could form one of the work packages described under Project Work plan. Here one should address:

• roles and resources dedicated to project management and control, in particular for work package and overall project co-ordination
• project management processes, mechanisms for corrective actions and decision making procedures
• interdependencies and relationships with national, Community or other relevant projects and programmes should be explained

Criteria to be addressed in this section are:

• Are proposed project management procedures effective, clearly described and include appropriate provisions for conflict resolution.
• Are proposed co-ordination, reporting and progress monitoring procedures clearly described and do they include mechanisms for corrective actions as required.
• Are project and task level roles and responsibilities identified, allocated and suitably distributed amongst the partners.

The Proposers

Present the rationale for the specific consortium and include:

• a description of each partner, their skills and experience
• the role of each partner in the project
• brief details of the "key" staff involved in the project

Criteria to be addressed in this section are:

• Are the number of proposers and their roles, skills and experience sufficient and necessary for achieving the expected business and technical objectives. Is the profile of partners clearly described.
• Do proposers demonstrate their capabilities and plans in sufficient depth to inspire confidence that they will achieve and exploit the results.
• Is a significant and balanced co-operation between partners proposed, from both the technical and the business perspective.

Duration & Resources

The duration should be rationalised in relation to the objectives to be achieved. Estimates of the resources (manpower, equipment, etc.) should be presented for each partner for each work package and summarised at the project level.

OMI small demonstrator projects are typically less than 18 months and in the order of 100-200KEcu funding.

Criteria to be addressed in this section are:

• Are realistic estimates given of the total costs and funding in ECU's for the project as a whole and for each of the partners separately
• Does the proposal set out the estimated effort, expressed in person-years, for each partner and work package in accordance with achieving the results
• Is the duration realistic and in line with objectives.

4. Submitting a Proposal

Each proposal must have a co-ordinating proposer, shortly co-ordinator, and this section of the information package is primarily directed to him. Normally, the co-ordinator will become the project co-ordinator, if the proposal is ultimately successful

Proposals should be submitted by you, co-ordinator, and you will be responsible for the liaison with the Commission.

You should submit one full original of each proposal plus 6 copies. This includes the forms and any useful information you choose to include, as long as it is relevant and limited in length.

It is your responsibility to assemble the proposal and you should submit it in one parcel.

It is also your responsibility to ensure that the proposal is delivered at the appropriate address before expiration of the deadline.

Delivery of your Proposal

Your proposal should be sent by courier or postal services or delivered by hand to:

You must clearly mark on the parcel:

'Confidential: Proposal for the programme for RTD in Information Technologies (Esprit)'

Important note

Do not send proposals by fax or E-mail. Do not announce by fax or telephone that the proposals are in the mail. Faxes and telephone calls of this nature hinder the operation of the Commission in handling proposals, and will not be acknowledged. Until two weeks have elapsed, do not telephone or fax to enquire whether your proposal has been received.

Do not send or deliver your proposal to Esprit Commission Offices. This would create considerable delays. The only correct address is the one mentioned above.

Continuous Submission

Proposals for Demonstration actions can be submitted continuously during the period described in the latest Call of Esprit. The precise information should be carefully checked and adhered to. Proposals which are received after the end of the period indicated in the latest Call are not eligible.

Acknowledgement of Receipt Form

You should include – in the parcel in which the proposal is delivered - a separate envelope containing the official 'Acknowledgement of Receipt' form as given in the Annex. On this you – the co-ordinator - must put your organisation's name and address and the title of the proposed project. This will ensure that the acknowledgement is returned to you correctly addressed.

Before it is returned, however, the Commission's reception staff will record the date of receipt and a unique reference number on the form. This reference number must be used in all subsequent correspondence relating to the proposal.

You should ensure that all proposers are given the proposal reference number and use it in all contacts with the Commission.

If you do not receive an 'Acknowledgement of receipt' within two weeks after the closing date of the Call, or the date of submission in case of a continuous Call, you should send a fax to the IT Programme office (Fax: + 32 2 6637200), indicating the acronym, title, domain, type of action and name of co-ordinator. You will receive an answer by fax within one week. You are strongly advised to retain proof of dispatch if the proposal is mailed or send by courier.

Submitting the proposals to other programmes

You are advised to submit proposals only once and to not send proposals which are essentially the same to different domains of the Esprit Programme or different programmes.

If the proposal is related to other Esprit domains or to other Community programmes you are advised to indicate this in the proposal itself or in an attached covering letter.

In any case you should give details on similar proposals on form 1a and sign the declaration.

The IT programme will take your comments in account and when appropriate involve the other domains or other programmes in the evaluation.

The IT programme reserves the right to redirect the proposals to another domain than indicated by the proposers or to another programme if EC staff or evaluators indicate that that would be more appropriate.

5. Further Information

If there are further questions on the content of this Specific Information Document or if there is a need for further clarification in matters relating to the call, please contact:

6. Annexes

Form 1a : Proposal Administrative Summary

Form 1b : Proosal Administrative Summary (continued)

Form 2 : Individual Participant Profile

List of Codes

Acknowledgement of Receipt Form

Glossary

LIST OF CODES

European Commission
Directorate General III: Industry
RTD: Information Technologies

Glossary

7. Esprit National Contact Points

National Contact Points will help if you have any questions about the Programme and the preparation of proposals.

A list of National Contact Points is available for consultation.

The URL of this document is /esprit/src/demo.htm

It was last updated on 24 February 1997 and is maintained by Susan Panter