Project Concept

Figure 3: Project Concept Workflow

The Project Concept introduces an opportunity or issue and outlines why it should be addressed. 

Its purpose is to make it as easy as possible to submit a proposal and get feedback from the FFCoVE on the likelihood of it becoming a project. This phase ends with a decision from the FFCoVE that the proposal doesn’t proceed (and we will tell you why) or approval to proceed to a Project Definition (or straight to a business case).

There are two options for creating and submitting the Project Concept; complete an online submission or populate an MS Word template. Links to both of these options are at the bottom of this page.

The Project Concept has the lowest possible threshold in that there is no limit as to how many project concepts can be submitted nor what the scope of those project concepts might be. On receipt, the Portfolio Management Office will explore all possible options to determine the potential benefit to the sector, including:

  • Alignment with the FFCoVE Strategic Plan (and if not aligned, determine if a possible case exists to convince the FFCoVE Board to change the Strategic Plan or to agree an exception
  • Seeking clarification if needed on the proposal and why the submitter considers it important to resolve
  • Identifying other project concepts (or expressions of interest which other sector organisations have expressed) which this concept might align with.  The Portfolio Manager has a responsibility to ensure the scope is not blown out to the point where it would be difficult to justify (i.e. becomes too complex/risky and/or too expensive and/or likely to take too long to implement etc.)

Don’t go into too much detail; we need just enough information to understand what your proposal is about. It’s possible that someone else has already got a solution or is working on one. If so, we’re happy to put you in touch with that organisation and you can decide if:

  • their solution will work for you,
  • you want to join that initiative, or
  • you just want them to keep you informed of progress.

Otherwise, we’ll come back to you:

  • for more information,
  • with a Project Definition template so that you can move to the next phase, or
  • to explain why we don’t think the proposal is viable.

So, ultimately, this phase ends with a decision from the FFCoVE that the proposal is approved to proceed to a Project Definition (or straight to a business case) or doesn’t proceed at all (and we will tell you why).