Data Concentrator Unit

There are expert companies around which have products and/or consultancy capability.

Without the description of the communication links you can use, it's quite difficult to make a sound decision about what is the appropriate solution for a distributed system.

In a first analysis, I would go for an architecture with a Central Server to do the interface with the billing system and Remote DCUs to collect data from meters and report them to the CS.

CS can be any RAID server with appropriate redundancy and archiving facility. Redundancy is a choice to be made depending on redundancy level chosen for R-DCUs. Front end comms may be required depending on how you can collect data from R-DCUs.

R-DCUs would have several levels of redundancy:

1. local redundant storage of data over a period of time which ensures that if comms is lost with CS, the data will not be lost

2. R-DCUs would collect data from their group of meters plus total or partial data from one or several other R-DCUs -R-DCU to R-DCU link only

3. critical meters would have a direct link to a couple of R-DCUs, so maintenance on one R-DCU is a limited risk

Depending on the choices made, this may lead to have redundant R-DCUs which is quite expensive to maintain if not already as an up-front cost.

Roll-out of this system, in terms of validation might be easier if there is a proper FAT performed.

Location of the R-DCUs is a point to address in considering the operational costs of comms link to CS and possibly other R-DCUs and meters. Other considerations can be taken into account if you also want to link the data with status of some local switchgear/transformer, ... and their control.

Thank you, for the Technical specifications updates.

1.Yes, I would need to have a back-up server that would still have the data should anything go wrong.Fortunately, the meters we currently use, can store up to 3-4 months of data even after disconnection.So, double-back will be a bonus.

2.I am fascinated by the function of this R-DCUs of collecting extra/partial data.So, it indicates that there will be multiple data obtained from other R-DCU's as well??

3.For maintanance, it is still a question for me.What kind of back-up should be used to get the data from the meters whilst the R-DCU is still maintained? The system should go on for 24/7 days basis, non-stop, since the billing system will be 100% interfaced with the CS, that's being communicated via the R-DCU's.

I will do further research from my side concerning all aspects provided to these companies that we expect.

Thanks once again,

itlity's comment about communication links is valid. The DCU locations will depend on the type of uplink from the meter, and also on the backhaul to the central station. Wired or wireless, a propagation study is necessary to determine ideal sites. You should also note that DCU locations for the different service territories will not be the same. The cost per meter in rural areas will be much higher than urban or suburban areas.

I've seen DCUs located at substations, regulators, reclosers, even mounted alone on a distribution pole. Some municipalities use other city facilities such as fire stations, park administration buildings, water booster stations, reservoirs & storage tanks, sewage lift stations, pretty much any place which has power and a backhaul data link.

If I were doing your project, I would assign the territories and let each vendor decide where to site their DCUs. If you limit their design options by dictating the locations, they may not take responsibility for any data loss which may occur.

Yes,I have already selected the sub-stations as a location.

This now takes me to my second assignment of handing in the territories, I have already indicated the sites, the only thing left is to get how many meters will each company be responsible for so as to break down the funds equally. See, this will be another challenge, but with these inputs you guys have posted, I am energised.

Thanks,