Jump to content

How Do I Draw Up a Specification Sheet?

Correctly Formulate Wishes And Requirements For Energy Monitoring Software

Every company that wants to introduce a new energy management software system should think through this resource-intensive investment. Only through careful gathering of requirements and detailed planning can a new system be implemented successfully and efficiently. Before a company decides hastily on a solution, all relevant technical features, functions, legal requirements and other requirements should be consolidated. So once the management has approved the go-ahead for the introduction of an energy monitoring system, a catalogue of requirements can be drawn up with all the necessary contacts, the so-called specifications.

 

What should be considered when drawing up a specification?

First, you should record the status quo with all relevant contacts: how is work done today and what is missing or not working?

Then you should collect the requirements regarding the resource needs, the infrastructure needs, the specific IT requirements of the company as well as the relevant interfaces. It is important that you do not look at your specifications in isolation at the IT level, but across all business processes and interfaces. Therefore, define the needs and requirements in the specifications with contacts from all departments. After you have collected all the relevant requirements, these should then be prioritised and recorded in detail.

Introduction Of a Specification In 4 Steps

  1. Elaboration of the requirements in the team
  2. Prioritisation: differentiation between mandatory and desirable requirements
  3. Detailing the requirements
  4. Structuring and outlining the requirements specifications

 

Typical Mistakes

  • Requirements specification vs. specifications: The wishes and requirements from the customer's or client's point of view belong in a requirements specification. No solution is described here, this is part of the requirements specification.
  • Product vs. project: Only the requirements for a technical system and not for the entire project belong in a requirements specification. The crucial difference here is that although project requirements are also very important, they become historical as soon as the project is completed. The requirements for a technical system therefore exist even after the project has been completed. Therefore, it is important not to mix these requirements.
  • Missing the mark: It is a balancing act how detailed you list your requirements in the specifications. If the requirements are too detailed, it can lead to delays in the project. Requirements that are too superficial can lead to misunderstandings. Finding the right level of detail often requires experience and intuition.
  • No system delimitation: It is important to describe the relevant system and also to delimit it from systems that are not affected by the software implementation.

 

Download sample specifications now