Generic specifications - What the ?!*k

Over the years I have written a few control strategy specifications for buildings.

 By the way - the pictures are some buildings where I have worked on controls specifications over the years (they have no real purpose  - but nice photos break up the words quite nicely don't you think?).

St Johns Cambridge
On more than one occasion I have been asked to write a "generic specification", which does sound really quite stupid.

Why? - Per Wikipedia  - An oxymoron (plural oxymora or oxymorons) (from Greek ὀξύμωρον, "sharp dull") is a figure of speech that combines contradictory terms.

Certainly any document that is wholly generic, cannot be specific to anything other than a genera. So a "Generic Specification" is a self-contradiction - Like military Intelligence :)

But, rather like a curates` egg which euphemistically describes selectivity :
White Tower (part of Tower of London) (Boiler Sequencing)
HSBC Hong Kong (Virtual study of turbines)

Host (solicitously) - "How is your egg?"
Curate (politely) - "Rather good! - in parts",

it is I suppose, quite reasonable to adopt the idea of a standard template. A template applies to all instances where it is applied and so in and of itself it is wholly generic, the differences (or specifics) can populate the template that are particular to some control plant.

So the idea of a generic template is not so crazy. It is actually what many controls text books attempt to describe. However an on-line tool could be interactive, and generate high quality potentially interactive (as a learning tool) output.

This has me wondering - would readers (there are not so many of you) find it useful if I started producing some careful specification of generic controls solutions for the HVAC field, that could be safely cut and pasted with the "blanks filled in"?

BP Sunbury (Air-Handlingy)
London Guildhall (Boiler  Sequencing and Economizers)
Please note I am pathologically uninterested in choice of hardware or whose control system is flavour of the day - so long as at least communications and discovery are open protocol , but my focus is on  control strategies that perform well pragmatically.

To my mind BMS systems are essentially and should be treated as a commodity.

Obviously (I hope), my focus would be on design for efficiency.

I envisage a series of libraries eg for a VT zone several control solutions types can apply depending on plant supported by them and they can be paramterized as follows:

The zone has a name (obviously a text input field), and primary source of hot water
Selectors (eg Fahrenheit / Celsius) will support internationalisation (that is to say Amercians)
Barclay's One Churchill Place
Heat Recovery
Parameters etc  (eg for a linearly compensated  yariable temperature zone one would need to specify slope and offset or two pairs of co-ordinates typically to map Outside Air Temperature to Target Zone Flow Temperature.)

A suitably labelled, illustrative diagram would be accompanied, together with pseudo implementation code or function block diagrams to assist implementation. Plus comments and issues to be aware of from an efficiency perspective

If anyone is interested please do leave a comment below (otherwise I will just do it as and when it takes my fancy - it has to be of more value and interest than an auto-biography!).

Related articles
Enhanced by Zemanta