Laserfiche WebLink
image below presents these 2 fields. The codes for configuration may change based on <br />implementation setup. The importance is to identify a manual shut off meter verses a <br />remote disconnect capable smart meter. <br />DEVICE <br />fpplicatlan <br />3-11A1ER v <br />Device Cotle <br />O <br />2 MRCR <br />EumaceS <br />038a284a3 <br />9 <br />Arrive rune <br />n <br />Q, G AIDE <br />runre 1301- GAL I REGISTER ADD <br />TOGETHER 1,i:ears <br />Purchase Order# <br />Bill Conng 30!-GALI REGISTER ADD <br />TOGETHER v Fe€lsters 1 <br />Purchase Date <br />IrzVL13M <br />`iw <br />Customer Number <br />020-1954.300 <br />Purchase Cast <br />DO <br />Install Dale <br />1]RB/]111a <br />ru]Wlllel Name <br />k ME5 PFR:E <br />Inst,11 Cast <br />W <br />Prem Address 1 <br />16795 TOLL RD <br />returned Date <br />Prem Address 2 <br />Work Order Number 0 <br />Prem Add —I <br />Work Order year <br />0 <br />Ciry <br />RENO <br />SetDate <br />12128/2014 <br />rommam <br />Meter Date <br />D00000000OuDD <br />1. <br />99 <br />GO DEFADLT <br />Battery Date <br />M <br />Warrant, Date <br />0 <br />eameFyTime <br />0Dx00o000O0oD <br />Warrant, Type <br />0 <br />G, @ mr.ml <br />SIUR Retluri ien <br />Mike t <br />Number@TS <br />No. UeF Cems Cnn hae6 <br />IP Address <br />Maintenance Date <br />MMem PM1nne <br />119C1e/IIn115eU1e <br />0-Ikdbe <br />IIMIU <br />Ownership Flag <br />Pascworn <br />Bidirec Tonal <br />Name <br />AMI EIS <br />y-PMIMeter <br />WerkerM <br />g0YVODDED <br />AMI type <br />1 <br />4 ©q_All MANUAL <br />KSlled Dale <br />AMI Kind <br />DO-- <br />q0 <br />Imd# <br />0 <br />Q� <br />N. <br />OperatorI <br />0 <br />4 <br />Notes <br />Installed <br />12 014 <br />drum in Smofl�rd <br />LesIOV✓e(ei[ /(Lyy n/Ny/GI/GJ GJ:uv.uu <br />5.3.2. The current Hand Held process is modified to exclude AMI meters in the download <br />where reads are provided from the MDM. This will get implemented in AMI Stage 2. <br />5.4. Billing Requests <br />5.4.1. The M D M S and enQuestawill implement the MultiSpeak®® <br />2 5 H -113 Page 106 <br />