The below specification is met when this item is purchased as part number 3999-10-PT100
Monitoring Sensors
•    The system must include sensors which can record the following: energy consumption from a standard UK 3 pin plug (BS 1363), humidity from 0-100%, carbon dioxide 0-5% concentration and temperature from -100C to 50C (covers xx lab equipment and conditions). 
•    Temperature probes have an accuracy of = +/- 0.5C.
•    CE Certified and fully compliance with relevant data transmission regulations e.g. Radio Emissions Directive.
•    Probes must have a waterproof option (IP65 or better).
•    Sensors can have their sample intervals adjusted by end users.
•    Sensors transmit real time measurements.
•    Data logging and retrieval sensor level.
•    Options for Sensor Calibration to include full UKAS or UKAS traceable calibrations (at test laboratory or on at customer site) for compliance with inspections.  

Monitoring Infrastructure
•    Secure handling of data incorporating end-to-end encryption – minimum AES 128 Encryption for Sensor Data Transmission
•    Should be able to run on site IT network, or operate entirely independently of local University IT network, i.e. with wireless sensors communication to gateways/routers with cellular connection.
•    Cellular connection must not be dependent upon one single network, roaming SIM. 
•    Option for UPS Battery back-up of Gateways/Routers and power-supply monitoring in the event of power outage
•    Remote gateway access by supplier for remote maintenance
•    Electrical operation of Gateway from a 230-volt, AC (50Hz), power supply with a three-pin plug to BS1363
•    Ultra-long range transmission range using “LoRa” or equivalent, for minimal infrastructure allowing fast/low cost installation and to transmit to remote gateway separately located in a building i.e. through walls or floors
•    Quick to install –Typical less than a day for a single building install
•    Power conditioning of gateways  to withstand power surges/spikes
•    Sensors are made from non-toxic materials.
•    Sensors transmit their data wirelessly.
•    Line of site range sensor to gateway =10km.

Online Software Platform
•    Full access to system information and alerts, from any device e.g. phone (iOS or Android), iPad/tablet (iOS or Android), Windows and AppleMac PC and Laptops. Secure access via TLS.
•    Intuitive and easy to use – minimal training requirement
•    Ability to set-up or change monitoring requirements by end users - including locations, sensor types, owners of the space or equipment monitored, alert thresholds, alert recipients
•    Location of sensors to be easily identified once deployed - Customer documents/images should be easily uploaded e.g. photos, floorplans, 3D images, sketches.  Sensors icons to be easily positioned by users onto images in their correct location. Ability to see sensors and data in various formats e.g. dashboard and sensor-annotated images – including floor plans, laboratory photo, 3D render, Site Maps, Google Maps (or equivalent).
•    Chart view showing periodic analysis on any parameter – including number of readings, averages, high/low. Energy use must be easily summarised over a selected period
•    User account with an administrator setting for access control – must have control of visibility of locations & sensors, including no access, view-only data, view & edit right. Audit log available in real-time
•    Summary of key performance indicators information panel, providing complete overview and statistics.  Reports to be exportable and have ability to comment on individual readings. Data must be user exportable data in a range of common formats including CSV.  Reports scheduled and produced automatically and on demand in real-time. Reports with selectable number of daily readings e.g. per day – 1, 2, 4, 6, 8, 12, 24
•    Alert conditions must be User configurable, and easily changed to support dynamic & changing requirements. Alert options via email, SMS or phone call. Alarms must be Multi-level with user configurable parameters e.g. delay rule, thresholds, time period.
•    Alerts must be formed in to alarm groups, including user configurable alerting and escalation rules. Alarm call recipients to be set in prioritised sequence; with acknowledgment and repeat call rounds in the event of no response
•    Alarms must have the option to add comments, which can be exported or emailed to 3rd parties. Alert summary information, including alarm incident numbers/statistics e.g. resolved/acknowledged.  Acknowledgement of an alarms can be broadcast to other recipients in the sequence to support “stand down” - avoiding everyone chasing the same event