Type of Project | Selection |
---|---|
Kick start | X |
Feasibility study | |
Demonstration project |
Theme | Selection |
---|---|
Aviation | |
Health | |
Infrastructure & smart cities | |
Media, culture & sport | |
Transport & Logistics | |
Safety & security | |
Energy | |
Education & Training | |
Food & Agriculture | |
Finance, Investment & Insurance | |
Tourism | |
Environment, wildlife & natural resources | X |
Maritime & Aquatic |
Space Assets | Selection |
---|---|
Satellite communications | |
Satellite navigation | |
Earth Observation | X |
Satellite AIS | |
Human spaceflight technologies |
Header Information | |
---|---|
Project Short Name | Project acronym or abbreviation |
Project Full Name | An explanation of the acronym or longer project name |
Contract Number | 4000xxxxxx (check the cover page of the project contract to find a number starting with 4000) |
Project Logo | Use simple, bold iconography. Company logos are NOT allowed as project logos. Consider hiring a graphic designer.![]() Image credit: BioConsult SH, Project: Spacewhale |
Teaser | Provide a brief description of the project in less than 60 words. It will not appear on the project web page itself but is used in project lists e.g. https://business.esa.int/projects and search results. |
Status | N/A () / Ongoing (X) / Completed () |
Project Web Page | |
---|---|
Objectives of the Service | ![]() Image credit: Terrascope Ltd, Project: Fatmap Describe in less than 200 words the objectives of the service, i.e., what are the key problems of the users, what is the solution you intend to provide, and how will you provide it. Also describe the objectives of the activity (Study or Project). Avoid phrases like “The objective is to investigate the technical feasibility and economic viability…”. Restrict the use of acronyms and ensure they are spelled out at first occurrence. |
Users and Their Needs | Describe in less than 200 words the user communities currently targeted, the users involved in the activity, or people who will be using the service/solution. Avoid extrapolating on “possible future users”. Define their needs and the challenges for the project to meet these needs (e.g., using a bullet list). Indicate the country/countries of the targeted users. |
Service/System Concept | Describe in less than 200 words the capability or information supplied to the user, i.e., type of information delivered, specific features or functionalities, and the capability the user will have when the service is deployed. Explain how the system works in simple terms (no jargon) for a wide audience. Explain the system architecture (on a high level). A simple diagram may be included but ensure it looks good. Avoid serif fonts or font sizes too small to be readable.![]() Image credit: Hydrologic, Project: Owasis |
Space Added Value | Describe in less than 200 words which space assets are used and the expected added value of using and/or combining space assets to achieve the goals as opposed to using current methods from potential existing competitors. |
Current Status | ![]() Image credit: Geoville, Project: Agespot Describe in less than 150 words the status of the project. Avoid generic statements like “user requirements gathering”; instead, say “Held three workshops in different French cities, each attended by 20 users”. Provide a brief summary of achievements, work currently in progress, and activities about to start. Update this section when major project events are passed, e.g., FAT test, SAT test. |
Prime Contractor | |
---|---|
Logo | ![]() |
Company Name | European Space Agency |
Country | France |
Website URL | https://www.esa.int/ESA |
Related Links | |
---|---|
News story on BBC | https://www.bbc.com/news |