An important part of the requirement specification is the interface description – the description of the interfaces to other systems. An interface connects systems with different physical, electrical and mechanical properties.
The definition of an interface specifies common properties. This can also include a protocol for communication and data exchange. Interfaces exist wherever different systems have to work together. They form the transition from one system to another – for communication, data exchange, control and documentation.
The interface between human and machine is particularly important. The software and control system largely determines how efficiently a plant operates. Therefore, intuitive operation and safety mechanisms against operating errors are equally essential.
When do organisational interfaces arise?
Interfaces also arise between departments, divisions and companies. This is typically the case when
- a task can only be solved through cooperation between several departments or divisions,
- the parties involved are of equal rank and neither superior nor subordinate to one another
- and no higher-level body coordinates the cooperation.
Interfaces therefore always involve coordination effort. If the parties involved are not coordinated properly, time and information are quickly lost.
Typical problems at interfaces
Interfaces separate the shared understanding and pursuit of goals. Common consequences are:
- coordination problems that lead to failure
- different subcultures, e.g. language, planning horizons or external companies
- conflicts over departments, motives, resources and distribution
- communication breakdowns
- unclear responsibilities
- poor flow of information
- high complexity
Goals of an interface description
- align and describe goals
- avoid incomplete stand-alone solutions
- manage conflicts at an early stage
- act as a “translator” between the parties involved
Clearly define handover points
Explicitly naming the interfaces in the processes is particularly important, because this is where different tasks interlock. Points where work passes from one hand to the next are especially sensitive and prone to errors.
It is therefore worth defining performance and quality criteria for these handover points. This way, you do not have to compensate for errors that occurred in the previous process step. A good interface description also ensures process reliability and transparency and avoids costly rework.
Every dependency between two systems should be explicitly formulated and documented. A system should always depend on a clearly defined interface of the other module – not on its implementation. In this way, the interface of a module can be considered separately from its implementation.
SEEFRIED Verfahrenstechnik GmbH supports you in drawing up your requirement specification. In addition, we define the interfaces to upstream and higher-level systems – for example to utilities and media in agitation and homogenisation technology as well as to the MES and ERP system.
Frequently Asked Questions about interface descriptions
Why does an interface description belong in the requirement specification?
Interfaces connect systems with different characteristics – such as the plant, controls, energy, media, MES and ERP. If they are not clearly described, time and information are lost and errors and costly rework result.
Which problems typically occur at interfaces?
Unclear responsibilities, poor information flow, communication breakdowns, conflicting goals between departments or external companies, and incomplete stand-alone solutions.
What should an interface description contain?
Every dependency between two systems should be explicitly formulated and documented – including performance and quality criteria at handover points and, where applicable, the protocol for communication and data exchange.
How exactly do you support us?
We help you prepare your requirement specification and define the interfaces of agitation and homogenization technology to upstream and superordinate systems such as energy, media, MES and ERP.