andy/mip
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Move WEBMIP_TEX from andy/shelves to main WEBMIP documentation area.

Browse Source 
git-svn-id: http://locode01.ad.dom/svn/WEBMIP/trunk@11593 248e525c-4dfb-0310-94bc-949c084e9493
This commit is contained in:
andrew.hardy
2009-06-24 09:47:27 +00:00
parent 7fba145f7c
commit f85b1331ca
51 changed files with 5879 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

339
Documentation/SupportingDocumentation/WEBMIP_TEX/fs_appendix_system_data.tex Normal file
View File

@@ -0,0 +1,339 @@
% This file was converted to LaTeX by Writer2LaTeX ver. 0.4b
% see http://www.hj-gym.dk/~hj/writer2latex for more info
\svnidlong
{$HeadURL$}
{$LastChangedDate$}
{$LastChangedRevision$}
{$LastChangedBy$}
\svnid{$Id$}
\section{System Data}
\label{sec:AppendixSystemData}
The system data descriptions provided in this appendix determine the
information stored within webMIP for Meter Modules, Housing, Base and
pricing elements. These elements will be controlled through the
administration functions provided by webMIP.
\subsection{Meter Modules}
\label{sec:AppendixMeterModules}
A meter module is the logical grouping of:
\begin{enumerate}
\item a meter to measure the flow of gas to a property;
\item a relief valve to protect the meter;
\item a slamshut valve to protect the property;
\item a regulator controlling the pressure of the gas flowing through
the meter;
\item a filter to remove contaminants from the gas;
\item pipework connected to the inlet of the meter;
\item pipework connected to the outlet of the meter.
\end{enumerate}
A meter module has the following attributes:
\begin{itemize}
\item module reference {}- the {\textquotesingle}name{\textquotesingle}
by which the module is referred to;
\item service pressure {}- the pressure at which the gas arrives at the
inlet of the module. This is often described as ranges (and subranges)
of pressure:
\begin{itemize}
\item LP {}- Low pressure;
\item MP {}- Medium pressure;
\item IP {}- Intermediate pressure;
\item HP {}- High pressure.
\end{itemize}
\item inlet connection {}- the connection made with the the service
pipe. This is described using the following attributes:
\begin{itemize}
\item orientation {}- the lie of the connection e.g.
{\textquotesingle}horizontal left{\textquotesingle};
\item connection {}- a standard description of the connector used e.g.
{\textquotesingle}(mm) PN16{\textquotesingle};
\item height {}- the position above the base at which the connection
will be found;
\item size {}- the diameter of the connection;
\end{itemize}
\item outlet connection {}- the connection made with the property. This
is described using the following attributes:
\begin{itemize}
\item orientation {}- the lie of the connection e.g.
{\textquotesingle}horizontal left{\textquotesingle};
\item connection {}- a standard description of the connector used e.g.
{\textquotesingle}(mm) PN16{\textquotesingle};
\item height {}- the position above the base at which the connection
will be found;
\item size {}- the diameter of the connection;
\end{itemize}
\item dimensions {}- describing the physical size and positioning of the
module using standard attributes of
{\textquotesingle}A{\textquotesingle} to
{\textquotesingle}H{\textquotesingle};
\item weight {}- the weight of the module in kilograms;
\item relief valve type {}- describes general characteristics of a
relief valve;
\item slamshut type {}- describes general characteristics of a slamshut
valve;
\item filter type {}- describes general characteristics of a filter;
\item regulator type {}- describes general characteristics of a
regulator;
\end{itemize}
A module can be requested with the following additional items:
\begin{itemize}
\item base {}- each module is associated with a single base;
\item housing {}- each module is associated with a single housing;
\item standard add{}-ons:
\begin{itemize}
\item AMR {}- automatic meter reading device;
\item EMS {}- energy management system;
\item convertor {}- to display a live conversion on the module;
\item bypass {}- additional pipework that allows maintenance,
replacement, etc. to take place on the meter without disrupting the
flow of gas to the property.
\end{itemize}
\end{itemize}
A module can be associated with:
\begin{itemize}
\item a drawing {}- a graphical representation of the module;
\item costs {}- the costs of buying and selling the module. This is
described using the following attributes:
\begin{itemize}
\item selling price {}- the price at which the module is sold;
\item delivery cost {}- the cost of delivery to the buyer;
\item region {}- the geographical region in which the costs are valid
(different regions may have different pricing structures).
\end{itemize}
\end{itemize}
\subsection{Meter}
A meter is a component of the module used to measure the flow of gas to
a property.
A meter has the following attributes:
\begin{itemize}
\item meter reference {}- the {\textquotesingle}name{\textquotesingle}
by which the meter is referred to;
\item measuring capacity. This is described using the following
attribute:
\begin{itemize}
\item Qmax {}- the maximum volume of gas that can be passed through the
meter per hour;
\end{itemize}
\item dimensions {}- describing the physical size and positioning of the
meter using standard attributes of
{\textquotesingle}A{\textquotesingle} to
{\textquotesingle}C{\textquotesingle} and
{\textquotesingle}Centres{\textquotesingle};
\item weight {}- the weight of the meter in kilograms;
\item connection type {}- a standard description of the type of the
connector used e.g. {\textquotesingle}PN16{\textquotesingle};
\item meter type {}- a standard description of the method that the meter
uses to measure flow e.g. {\textquotesingle}Rotary{\textquotesingle}.
\end{itemize}
A meter can be associated with:
\begin{itemize}
\item a drawing {}- a graphical representation of the meter;
\item costs {}- the costs of buying and selling the meter. This is
described using the following attributes:
\begin{itemize}
\item cost price {}- the price at which the meter is obtained;
\item delivery cost {}- the cost of delivery\footnote{\label{fnt:ftn1}Is
this the cost of delivery to NG Metering or cost of delivery to the
Supplier?};
\end{itemize}
\item a manufacturer {}- the organisation that constructed the meter.
\end{itemize}
\subsection{Housing }
\label{sec:AppendixHousing}
A housing encases a module. It is an optionally requested item on an
enquiry.
A housing has the following attributes:
\begin{itemize}
\item housing reference {}- the {\textquotesingle}name{\textquotesingle}
by which the housing is referred to;
\item dimensions {}- describing the physical characteristics of the
housing:
\begin{itemize}
\item length;
\item width;
\item height;
\item weight;
\end{itemize}
\item doors {}- the number of doors in the housing;
\end{itemize}
A housing can be associated with:
\begin{itemize}
\item a module {}- each module may be associated with a single housing;
\item a drawing {}- a graphical representation of the housing;
\item a manufacturer {}- the organisation that constructed the housing.
\item costs {}- the costs of buying and selling the housing. This is
described using the following attributes:
\item cost price {}- the price at which the housing is obtained;
\begin{itemize}
\item selling price {}- the price at which the housing is sold to the
customer;
\item labour cost {--} the cost of installing the housing (fixed at 10\%
of the selling price);
\item delivery cost {}- the cost of
delivery\textsuperscript{\ref{fnt:ftn1}};
\end{itemize}
\end{itemize}
\subsection{Base}
\label{sec:AppendixBase}
A module is situated on a base (often a concrete slab\}. It is an
optionally requested item on an enquiry.
A base has the following attributes:
\begin{itemize}
\item base reference {}- the {\textquotesingle}name{\textquotesingle} by
which the base is referred to;
\item dimensions {}- describing the physical characteristics of the
base:
\begin{itemize}
\item length;
\item width;
\item depth;
\end{itemize}
\item standard dimensions {\textquotesingle}A{\textquotesingle} to
{\textquotesingle}I{\textquotesingle}\footnote{Why are there two sets
of dimensions? }
\end{itemize}
A base can be associated with:
\begin{itemize}
\item a module {}- each module may be associated with a single base;
\item a drawing {}- a graphical representation of the base;
\item costs {}- the costs of buying and selling the housing. This is
described using the following attributes:
\begin{itemize}
\item cost price {}- the price at which the housing is obtained;
\item selling price {}- the price at which the housing is sold to the
customer;
\item delivery cost {}- the cost of
delivery\textsuperscript{\pageref{fnt:ftn1}};
\end{itemize}
\end{itemize}
\subsection{Drawing }
A drawing is a graphical representation of a physical object. The system
stores drawings so that they may be displayed as part of a reporting
object.
The system associates drawings with the following:
\begin{itemize}
\item module;
\item meter;
\item housing;
\item base.
\end{itemize}
\subsection{Standard add{}-ons}
\label{sec:AppendixStandardAddOns}
A number of standard (non{}-meter module specific) items may be
requested to be included with a meter module:
\begin{itemize}
\item AMR {}- automatic meter reading device;
\item EMS {}- energy management system;
\item Converter {}- to display a live conversion on the module;
\item bypass {}- additional pipework that allows maintenance,
replacement, etc. to take place on the meter without disrupting the
flow of gas to the property.
\end{itemize}
The system does not record the attributes of these items other than the
fixed costs for the AMR, EMS and convertor items.
\subsection{Pricing Data}
\label{sec:AppendixPricingData}
With the exception of Standard add{}-ons (see Appendix \ref{sec:AppendixStandardAddOns} ) all
cost/pricing information may be regional i.e. the price for an item may
differ according to the region in which the installation will take
place. Regions are based on post{}-codes\footnote{Composition of
postcode to region still unknown.}. Where there are no applicable
regional costs associated with an item, a non{}-regional price will be
used for that item.
Where the system selects a meter module or associated item and a
required supplier price is missing, the system is unable to produce a
quotation. The enquiry is treated as a request for a Manual Quote that
requires completion by D\&Q.
Where the system selects a meter module or associated item and a
required network price is missing, the system will produce a quotation
but there will be a manual process during
{\textquotesingle}job{\textquotesingle} entry onto SAP to determine the
relevant network costs.
Bypass pricing is handled off{}-line.
\subsection{Tripartite Agreement}
\label{sec:TripartiteAgreement}
The Tripartite Agreement prevents quotations being produced for
specified combinations of Suppliers, job types and postcodes.
The system will identify which Network the site address relates to by the supplied postcodes. When a supplier admin is set up by the webMIP administrator, the tripartite flag will either be {\textquotesingle}yes{\textquotesingle} or {\textquotesingle}no{\textquotesingle}. When a non - tripartite supplier code attempts to submit an enquiry for quotation of an install or exchange in a Tripartite only region - the system will reject and indicate that the customer will need to contact the regions asset owner for metering services.
The system will record the Tripartite Agreement attributes as:
\begin{itemize}
\item Supplier {--} a reference to a Supplier that has not signed up to
the Tripartite Agreement;
\item Job Type {--} the Job Type(s) that the Supplier cannot be quoted
for, one of:
\begin{itemize}
\item Installation of new meters;
\item Request for OFGEM Meter Accuracy Test (OFMAT);
\item Exchange of meters;
\item Removal of meters, including
{\textquotesingle}Adversarial{\textquotesingle} removal of meters;
\end{itemize}
\item Installation PostCode {--} the postcode where the installation is
to take place.
\end{itemize}
\subsection{Postcodes}
\label{sec:AppendixPostcodes}
The Post Codes will be loaded into the system as they currently relate to each network as they appear in the SAP Rainbow system at the time of go-live. In the eventuality that an individual post-code changes to relate to a different network it will be manually updated in system by the System Administrator.