{"id":80952,"date":"2020-05-10T01:42:22","date_gmt":"2020-05-09T23:42:22","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/monitoring-v-czode-kak-my-menyali-staruyu-bms-na-novuyu-chast-2"},"modified":"2020-05-10T01:42:22","modified_gmt":"2020-05-09T23:42:22","slug":"monitoring-v-czode-kak-my-menyali-staruyu-bms-na-novuyu-chast-2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/monitoring-v-czode-kak-my-menyali-staruyu-bms-na-novuyu-chast-2","title":{"rendered":"Monitorimi n\u00eb Qendr\u00ebn e t\u00eb Dh\u00ebnave: si e ndryshuam BMS-n\u00eb e vjet\u00ebr me t\u00eb re. Pjesa 2","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Monitorimi<\/p>\n

N\u00eb pjes\u00ebn e par\u00eb, ne fol\u00ebm p\u00ebr arsyen pse vendos\u00ebm t\u00eb z\u00ebvend\u00ebsonim sistemin e vjet\u00ebr t\u00eb BMS n\u00eb t\u00eb dh\u00ebnat tona me nj\u00eb t\u00eb re. Dhe jo vet\u00ebm ta z\u00ebvend\u00ebsojm\u00eb, por ta zhvillojm\u00eb nga e para sipas k\u00ebrkesave tona. N\u00eb pjes\u00ebn e dyt\u00eb tregojm\u00eb se si e b\u00ebm\u00eb k\u00ebt\u00eb.
\n<\/a><\/noindex><\/p>\n

Analiza e tregut<\/h2>\n

\nDuke marr\u00eb parasysh ato q\u00eb p\u00ebrmenden n\u00eb pjes\u00ebn e par\u00eb<\/a><\/noindex> d\u00ebshirat e shprehura dhe vendimin p\u00ebr t\u00eb hequr dor\u00eb nga p\u00ebrdit\u00ebsimi i sistemit ekzistues, ne shkruam nj\u00eb T\u00ebZ p\u00ebr t\u00eb k\u00ebrkuar zgjidhje n\u00eb treg dhe b\u00ebm\u00eb k\u00ebrkesa n\u00eb disa kompani t\u00eb m\u00ebdha q\u00eb merreshin vet\u00ebm me krijimin e sistemeve industriale SCADA.\u00a0<\/p>\n

P\u00ebrgjigjet e para prej tyre treguan se lider\u00ebt e tregut t\u00eb sistemeve t\u00eb monitorimit kryesisht vazhdojn\u00eb t\u00eb punojn\u00eb n\u00eb server\u00eb fizik\u00eb, megjith\u00ebse procesi i migrimit n\u00eb re n\u00eb k\u00ebt\u00eb segment ka nisur tashm\u00eb. Sa i p\u00ebrket rezervimit t\u00eb makinave virtuale - k\u00ebt\u00eb opsion asnj\u00eb nuk e p\u00ebrkrahte. M\u00eb shum\u00eb se kaq, shkaktohej mendimi se asnj\u00eb nga zhvilluesit e njohur n\u00eb treg nuk tregonte madje edhe kuptimin e nevoj\u00ebs p\u00ebr rezervim: \"re nuk bie\" ishte p\u00ebrgjigja m\u00eb e zakonshme. N\u00eb fakt, na u ofrua t\u00eb vendosnim monitorimin e Qendr\u00ebs s\u00eb Dh\u00ebnave n\u00eb nj\u00eb re, fizikisht t\u00eb vendosur n\u00eb k\u00ebt\u00eb Qend\u00ebr t\u00eb Dh\u00ebnave.<\/p>\n

K\u00ebtu duhet b\u00ebr\u00eb nj\u00eb shk\u00ebputje e vog\u00ebl p\u00ebr procesin e p\u00ebrzgjedhjes s\u00eb kontraktorit. \u00c7mimi, sigurisht, ka r\u00ebnd\u00ebsi, por gjat\u00eb \u00e7do tenderi p\u00ebr realizimin e nj\u00eb projekti t\u00eb nd\u00ebrlikuar, n\u00eb faz\u00ebn e dialogut me ofruesit, fillon t\u00eb ndihesh se kush nga kandidat\u00ebt \u00ebsht\u00eb m\u00eb i interesuar dhe i aft\u00eb ta realizoj\u00eb at\u00eb.\u00a0<\/p>\n

Kjo \u00ebsht\u00eb ve\u00e7an\u00ebrisht e dukshme n\u00eb projekte t\u00eb nd\u00ebrlikuara.\u00a0<\/p>\n

Duke u bazuar n\u00eb natyr\u00ebn e pyetjeve sqaruese p\u00ebr T\u00ebZ-n\u00eb, mund t\u00eb ndahet kontraktori n\u00eb ata q\u00eb jan\u00eb t\u00eb interesuar thjesht t\u00eb shesin (ndjehet presioni standard i menaxherit t\u00eb shitjeve) dhe ata q\u00eb jan\u00eb t\u00eb interesuar n\u00eb zhvillimin e produktit, duke d\u00ebgjuar dhe kuptuar porosit\u00ebsin, duke b\u00ebr\u00eb ndryshime konstruktive n\u00eb T\u00ebZ para p\u00ebrzgjedhjes p\u00ebrfundimtare (edhe pse p\u00ebrball\u00eb rrezikut real p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar nj\u00eb T\u00ebZ t\u00eb huaj dhe p\u00ebr t\u00eb humbur tenderin), e n\u00eb fund ishin thjesht t\u00eb gatsh\u00ebm t\u00eb pranonin sfid\u00ebn profesionale dhe t\u00eb b\u00ebnin nj\u00eb produkt cil\u00ebsor.<\/p>\n

T\u00eb gjitha k\u00ebto na b\u00ebn\u00eb t\u00eb drejtojm\u00eb v\u00ebmendjen ton\u00eb nga nj\u00eb zhvillues lokal relativisht i vog\u00ebl \u2013 grupi i kompanive \u00abSanline\u00bb, i cili iu p\u00ebrgjigj shumic\u00ebs s\u00eb k\u00ebrkesave tona menj\u00ebher\u00eb dhe ishte i gatsh\u00ebm t\u00eb realizonte t\u00eb gjitha nevojat p\u00ebr sistemin e ri BMS.\u00a0<\/p>\n

Rreziqet<\/h2>\n

\nNd\u00ebrsa lojtar\u00ebt e m\u00ebdhenj po p\u00ebrpiqeshin t\u00eb kuptonin se \u00e7far\u00eb donim dhe po zhvillonin nj\u00eb bised\u00eb t\u00eb ngadalt\u00eb me ne duke p\u00ebrfshir\u00eb specialist\u00eb n\u00eb nivelin presales, zhvilluesi lokal kishte caktuar nj\u00eb takim n\u00eb zyr\u00ebn ton\u00eb me pjes\u00ebmarrjen e ekipit t\u00eb tij teknik. N\u00eb k\u00ebt\u00eb takim, kontraktori p\u00ebrs\u00ebri demonstroi d\u00ebshir\u00ebn p\u00ebr t\u00eb marr\u00eb pjes\u00eb n\u00eb projekt dhe - m\u00eb e r\u00ebnd\u00ebsishmja - shpjegoi se si do t\u00eb realizohej sistemi i k\u00ebrkuar.\u00a0\u00a0\u00a0\u00a0<\/p>\n

Para takimit, ne kemi identifikuar dy rreziqe n\u00eb pun\u00ebn me nj\u00eb ekip q\u00eb nuk ka pasur mb\u00ebshtetje nga nj\u00eb kompani t\u00eb madhe komb\u00ebtare ose nd\u00ebrkomb\u00ebtare:<\/p>\n

    \n
  1. Specialist\u00ebt mund t\u00eb ken\u00eb tepruar me vler\u00ebsimin e mund\u00ebsive t\u00eb tyre dhe si rezultat mund t\u00eb mos p\u00ebrballen dot, p\u00ebr shembull, do t\u00eb p\u00ebrdorin softuer kompleks ose do t\u00eb projektojn\u00eb algoritme rezervimi q\u00eb nuk mund t\u00eb realizohen.<\/li>\n
  2. Pas p\u00ebrfundimit t\u00eb projektit, ekipi i projektit mund t\u00eb shp\u00ebrb\u00ebhet dhe, p\u00ebr pasoj\u00eb, mb\u00ebshtetja e produktit do t\u00eb jet\u00eb n\u00ebn k\u00ebrc\u00ebnim.<\/li>\n<\/ol>\n

    \nP\u00ebr t\u00eb minimalizuar k\u00ebto rreziqe, ne ftuam n\u00eb takim specialist\u00ebt tan\u00eb t\u00eb zhvillimit. Punonj\u00ebsit e kontraktorit potencial u intervistuan me kujdes n\u00eb lidhje me at\u00eb se si \u00ebsht\u00eb nd\u00ebrtuar sistemi, si planifikohet realizimi i rezervimit dhe p\u00ebr \u00e7\u00ebshtje t\u00eb tjera n\u00eb t\u00eb cilat ne, si sh\u00ebrbimi i operimit, nuk ishim mjaft kompetent.<\/p>\n

    Verdikti ishte pozitiv: arkitektura e platform\u00ebs BMS q\u00eb ekziston tashm\u00eb \u00ebsht\u00eb moderne, e thjesht\u00eb dhe e besueshme, mund t\u00eb p\u00ebrmir\u00ebsohet, skema e propozuar e rezervimit dhe sinkronizimit \u00ebsht\u00eb logjike dhe funksionale.\u00a0<\/p>\n

    Ne p\u00ebrballuam me rrezikun e par\u00eb. T\u00eb dytin e eliminuam, pasi mor\u00ebm konfirmimin nga kontraktori p\u00ebr gatishm\u00ebrin\u00eb e tij p\u00ebr t\u00eb na dor\u00ebzuar kodin burimor t\u00eb sistemit dhe dokumentacionin, si dhe duke zgjedhur gjuh\u00ebn e programimit Python, t\u00eb njohur mir\u00eb p\u00ebr specialist\u00ebt tan\u00eb. Kjo na garantoi mund\u00ebsin\u00eb p\u00ebr t\u00eb mbajtur sistemin me forcat tona pa asnj\u00eb v\u00ebshtir\u00ebsi dhe pa nj\u00eb periudh\u00eb t\u00eb gjat\u00eb trajnimi t\u00eb punonj\u00ebsve n\u00eb rast se kompania zhvilluese largohej nga tregu.<\/p>\n

    Nj\u00eb plus shtes\u00eb i platform\u00ebs ishte se ajo u zbatua n\u00eb kontejner\u00eb Docker: n\u00eb k\u00ebt\u00eb mjedis funksionojn\u00eb b\u00ebrthama, nd\u00ebrfaqja e uebit dhe databaza e produktit. Ky qasje ofron shum\u00eb p\u00ebrfitime, duke p\u00ebrfshir\u00eb parainstallimin e konfigurimeve p\u00ebr shpejt\u00ebsin\u00eb m\u00eb t\u00eb lart\u00eb t\u00eb implementimit t\u00eb zgjidhjes n\u00eb krahasim me \"klasiken\" dhe shtimin e thjesht\u00eb t\u00eb pajisjeve t\u00eb reja n\u00eb sistem. Prinicpi i \"t\u00eb gjitha s\u00eb bashku\" e thjeshton maksimalisht implementimin e sistemit: mjafton t\u00eb shkarkoni sistemin dhe mund ta p\u00ebrdorni menj\u00ebher\u00eb.\u00a0<\/p>\n

    Me nj\u00eb zgjidhje t\u00eb till\u00eb, \u00ebsht\u00eb m\u00eb e leht\u00eb t\u00eb b\u00ebni kopje t\u00eb sistemit, nd\u00ebrsa p\u00ebrmir\u00ebsimi dhe realizimi i p\u00ebrdit\u00ebsimeve mund t\u00eb b\u00ebhet n\u00eb nj\u00eb mjedis t\u00eb ve\u00e7ant\u00eb, pa ndalur pun\u00ebn e zgjidhjes n\u00eb t\u00ebr\u00ebsi.\u00a0\u00a0<\/p>\n

    Pas minimizimit t\u00eb t\u00eb dy rreziqeve, kontraktori paraqiti ofert\u00ebn. Ajo p\u00ebrmbante t\u00eb gjitha parametrat m\u00eb t\u00eb r\u00ebnd\u00ebsish\u00ebm p\u00ebr ne t\u00eb sistemit BMS.<\/p>\n

    Rezervimi<\/h2>\n

    \nSistemi i ri BMS duhet t\u00eb ishte n\u00eb cloud, n\u00eb nj\u00eb makin\u00eb virtuale.\u00a0<\/p>\n

    Asnj\u00eb harduer, asnj\u00eb server dhe t\u00eb gjitha shqet\u00ebsimet e lidhura me k\u00ebt\u00eb model implementimi \u2013 zgjidhja cloud na lejoj t\u00eb heqim dor\u00eb nga to p\u00ebrher\u00eb. U vendos q\u00eb sistemi do t\u00eb funksiononte n\u00eb cloud ton\u00eb n\u00eb dy lokacione t\u00eb Qendr\u00ebs s\u00eb t\u00eb Dh\u00ebnave n\u00eb Sh\u00ebn Petersburg dhe Mosk\u00eb. K\u00ebto jan\u00eb dy sisteme plotesisht funksionale, q\u00eb punojn\u00eb n\u00eb modin aktiv standby me qasje p\u00ebr t\u00eb gjith\u00eb specialist\u00ebt e autorizuar.\u00a0<\/p>\n

    Dy sistemet mbulojn\u00eb nj\u00ebra-tjetr\u00ebn, duke siguruar rezerv\u00eb t\u00eb plot\u00eb si n\u00eb kapacitetet llogarit\u00ebse ashtu edhe n\u00eb kanalet e transmetimit t\u00eb t\u00eb dh\u00ebnave. Po ashtu jan\u00eb konfiguruar masa t\u00eb tjera sigurie, duke p\u00ebrfshir\u00eb kopje rezerv\u00eb t\u00eb t\u00eb dh\u00ebnave dhe kanaleve, sistemeve, makinave virtuale n\u00eb t\u00ebr\u00ebsi, dhe nj\u00eb kopje rezerv\u00eb t\u00eb ve\u00e7ant\u00eb t\u00eb DB nj\u00eb her\u00eb n\u00eb muaj (burimi m\u00eb i \u00e7muar n\u00eb perspektiv\u00ebn e menaxhimit dhe analiz\u00ebs).\u00a0<\/p>\n

    D\u00ebshirojm\u00eb t\u00eb theksojm\u00eb se rezervimi si nj\u00eb opsion i zgjidhjes BMS u zhvillua posa\u00e7\u00ebrisht sipas k\u00ebrkes\u00ebs son\u00eb. Vet\u00eb skema e rezervimit dukej k\u00ebshtu:<\/p>\n

    \"Monitorimi<\/p>\n

    Mb\u00ebshtetje<\/h2>\n

    Nj\u00eb moment i r\u00ebnd\u00ebsish\u00ebm p\u00ebr nj\u00eb funksionim efektiv t\u00eb zgjidhjes BMS \u00ebsht\u00eb mb\u00ebshtetje teknike.\u00a0<\/p>\n

    K\u00ebtu t\u00eb gjitha jan\u00eb t\u00eb thjeshta: sistemi i ri do t\u00eb na kushtonte 35 000 rubla n\u00eb muaj p\u00ebr k\u00ebt\u00eb tregues sipas SLA \"reaksion brenda 8 or\u00ebve\", dometh\u00ebn\u00eb 35 000 x 12 \/ 80 = $5 250 n\u00eb vit. Viti i par\u00eb \u00ebsht\u00eb falas.\u00a0<\/p>\n

    P\u00ebr krahasim: mb\u00ebshtetje e sistemit t\u00eb vjet\u00ebr BMS nga tregtari kushtonte $18,000 n\u00eb vit me rritjen e shum\u00ebs p\u00ebr \u00e7do pajisje t\u00eb re t\u00eb shtuar! Nj\u00eb menaxher i dedikuar nuk ishte n\u00eb dispozicion nga kompania, t\u00eb gjith\u00eb komunikimi ndodhte p\u00ebrmes menaxherit t\u00eb shitjeve, i cili ishte i interesuar p\u00ebr ne si nj\u00eb bler\u00ebs potencial me theks t\u00eb caktuar n\u00eb p\u00ebrpunimin e k\u00ebrkesave.\u00a0<\/p>\n

    P\u00ebr nj\u00eb \u00e7mim m\u00eb t\u00eb ul\u00ebt mor\u00ebm mb\u00ebshtetje t\u00eb plot\u00eb p\u00ebr produktin, me nj\u00eb menaxher t\u00eb llogarive, i cili do merrte pjes\u00eb n\u00eb zhvillimin e produktit, me nj\u00eb pik\u00eb t\u00eb vetme hyrjeje etj. Mb\u00ebshtetja b\u00ebhej shum\u00eb m\u00eb fleksibile \u2013 fal\u00eb aksesit t\u00eb drejtp\u00ebrdrejt\u00eb te zhvilluesit p\u00ebr ndreqje t\u00eb shpejta n\u00eb \u00e7do aspekt t\u00eb funksionimit t\u00eb sistemit, integrimit p\u00ebrmes API etj.<\/p>\n

    Azhurnimet<\/h2>\n

    \nN\u00eb ofert\u00ebn p\u00ebr BMS-n\u00eb e re, t\u00eb gjitha azhornimet ishin t\u00eb p\u00ebrfshira n\u00eb kostot e mb\u00ebshtetjes, dmth. nuk k\u00ebrkonin pages\u00eb shtes\u00eb. P\u00ebrjashtim b\u00ebjn\u00eb zhvillimi i funksionaliteteve shtes\u00eb, p\u00ebrtej atyre q\u00eb jan\u00eb p\u00ebrcaktuar n\u00eb dokumentacionin teknik.\u00a0<\/p>\n

    Sistemi i vjet\u00ebr parashikonte pages\u00eb si p\u00ebr azhornimin e software-it t\u00eb integruar falas (tipi Java), ashtu edhe p\u00ebr korrigjimin e gabimeve. Nuk mund ta refuzonim k\u00ebt\u00eb, n\u00eb munges\u00eb t\u00eb azhornimeve, sistemi n\u00eb p\u00ebrgjith\u00ebsi \u2018ngucitej\u2019 p\u00ebr shkak t\u00eb versioneve t\u00eb vjetra t\u00eb komponenteve t\u00eb brendshme.<\/p>\n

    Dhe, natyrisht, nuk mund t\u00eb azhurnohej softueri pa blerjen e paket\u00ebs s\u00eb mb\u00ebshtetjes.<\/p>\n

    Qasje fleksibile<\/h2>\n

    \nNj\u00eb k\u00ebrkes\u00eb tjet\u00ebr thelb\u00ebsore u lidhi me nd\u00ebrfaqen. Ne donim t\u00eb ofronim qasje p\u00ebrmes shfletuesit t\u00eb internetit nga \u00e7do pik\u00eb, pa nevoj\u00ebn e pranish\u00ebm t\u00eb inxhinier\u00ebve n\u00eb vendin e Qendr\u00ebs s\u00eb t\u00eb Dh\u00ebnave. P\u00ebr m\u00eb tep\u00ebr, ne synonim krijimin e nj\u00eb nd\u00ebrfaqe t\u00eb animuar, n\u00eb m\u00ebnyr\u00eb q\u00eb dinamika e funksionimit t\u00eb infrastruktur\u00ebs t\u00eb ishte m\u00eb e dukshme p\u00ebr inxhinier\u00ebt n\u00eb detyr\u00eb.\u00a0<\/p>\n

    Po ashtu n\u00eb sistemin e ri duhej t\u00eb sigurohej mb\u00ebshtetje p\u00ebr formula p\u00ebr llogaritjen e funksionimit t\u00eb sensor\u00ebve virtual n\u00eb sistemet inxhinierike - p\u00ebr shembull, p\u00ebr shp\u00ebrndarjen optimale t\u00eb fuqive elektrike n\u00eb raftet me pajisje. P\u00ebr k\u00ebt\u00eb duhet t\u00eb kemi n\u00eb dispozicion t\u00eb gjitha operacionet matematikore t\u00eb zakonshme, t\u00eb aplikueshme p\u00ebr treguesit e sensor\u00ebve.\u00a0<\/p>\n

    M\u00eb pas, ishte e nevojshme t\u00eb kishte qasje n\u00eb databaz\u00ebn SQL me mund\u00ebsin\u00eb p\u00ebr t\u00eb marr\u00eb t\u00eb dh\u00ebnat e nevojshme rreth funksionimit t\u00eb pajisjeve - konkretisht, t\u00eb gjitha regjistrimet e monitorimit t\u00eb dy mij\u00eb pajisjeve dhe dy mij\u00eb sensor\u00ebve virtual\u00eb, t\u00eb cil\u00ebt gjeneronin rreth 20 mij\u00eb variabla.\u00a0<\/p>\n

    Ishte gjithashtu e nevojshme nj\u00eb moduli p\u00ebr llogaritjen e pajisjeve n\u00eb raft, q\u00eb ofronte nj\u00eb pamje grafike t\u00eb vendndodhjes s\u00eb pajisjeve n\u00eb \u00e7do nj\u00ebsis\u00eb me llogaritjen e pesh\u00ebs totale t\u00eb 'harduerit', duke mbajtur nj\u00eb bibliotek\u00eb pajisjesh dhe informacion t\u00eb detajuar p\u00ebr secilin element.\u00a0<\/p>\n

    Miratimi i T\u00eb Dh\u00ebnave dhe n\u00ebnshkrimi i kontrat\u00ebs<\/h2>\n

    \nN\u00eb at\u00eb moment, kur ishte e nevojshme t\u00eb fillohej puna mbi sistemin e ri, shk\u00ebmbimi i mesazheve me kompanit\u00eb 't\u00eb m\u00ebdha' ende ishte shum\u00eb larg diskutimit t\u00eb kostove t\u00eb ofertave t\u00eb tyre, prandaj ne e krahasuam ofert\u00ebn e marr\u00eb me shpenzimet p\u00ebr rinovimin e BMS s\u00eb vjet\u00ebr (shih. pjes\u00ebn e par\u00eb<\/a><\/noindex>), dhe si rezultat, ajo doli t\u00eb ishte m\u00eb t\u00ebrheq\u00ebse n\u00eb \u00e7mim dhe p\u00ebrputhej me k\u00ebrkesat tona.<\/p>\n

    Zgjedhja u b\u00eb.<\/p>\n

    Pas zgjedhjes s\u00eb kontraktorit, jurist\u00ebt filluan t\u00eb p\u00ebrgatisin kontrat\u00ebn, nd\u00ebrsa ekipet teknike nga t\u00eb dyja an\u00ebt po p\u00ebrmir\u00ebsonin T\u00eb Dh\u00ebnat. Si\u00e7 dihet, nj\u00eb T\u00eb Dh\u00ebna e detajuar dhe e sakt\u00eb \u00ebsht\u00eb baza e suksesit t\u00eb \u00e7do pune. Sa m\u00eb shum\u00eb konkret\u00ebsi t\u00eb ket\u00eb n\u00eb T\u00eb Dh\u00ebna, aq m\u00eb pak shp\u00ebrthime zhg\u00ebnjyese si 'ne donim ndryshe'.<\/p>\n

    Do t\u00eb jap dy shembuj t\u00eb nivelit t\u00eb detajimit t\u00eb k\u00ebrkesave n\u00eb T\u00eb Dh\u00ebna:<\/p>\n

      \n
    1. Qendrat e t\u00eb dh\u00ebnave jan\u00eb t\u00eb autorizuara t\u00eb shtojn\u00eb pajisje t\u00eb reja n\u00eb BMS, m\u00eb s\u00eb shumti kjo \u00ebsht\u00eb PDU. N\u00eb BMS-n\u00eb e vjet\u00ebr, ky ishte niveli 'administrator', i cili gjithashtu lejonte ndryshimin e parametrave t\u00eb t\u00eb gjith\u00eb pajisjeve, dhe ndarja e funksioneve ishte e pamundur. Ne nuk ishim t\u00eb k\u00ebnaqur me k\u00ebt\u00eb. N\u00eb versionin bazik t\u00eb disponuesh\u00ebm t\u00eb platform\u00ebs s\u00eb re, skema ishte e ngjashme. Ne menj\u00ebher\u00eb sh\u00ebnuam n\u00eb T\u00eb Dh\u00ebna se d\u00ebshironim t\u00eb ndaheshin k\u00ebto role: parametrat duhet t\u00eb ndryshoheshin vet\u00ebm nga nj\u00eb punonj\u00ebs i autorizuar, nd\u00ebrsa rojet duhej t\u00eb kishin ende mund\u00ebsin\u00eb t\u00eb shtonin pajisje. Kjo skem\u00eb u pranuar p\u00ebr realizim.<\/li>\n
    2. \u00a0N\u00eb \u00e7do BMS standard, ka tre kategori tipike njoftimesh: E KUQ \u2013 duhet t\u00eb reagoni menj\u00ebher\u00eb, E VERDH\u00cb \u2013 mund t\u00eb monitorohet, E BARDH\u00cb \u2013 \"Informative\". Tradicionalisht, ne e kemi p\u00ebrdorur njoftimin \"e bardh\u00eb\" p\u00ebr monitorimin e kalimeve t\u00eb parametrave komercial\u00eb, si kalimi i limitit t\u00eb fuqis\u00eb s\u00eb raftit t\u00eb klientit. Ky lloj njoftimi n\u00eb rastin ton\u00eb ishte i destinuar p\u00ebr menaxher\u00ebt dhe nuk ishte i interesit t\u00eb sh\u00ebrbimit t\u00eb operacioneve, por n\u00eb BMS-n\u00eb e vjet\u00ebr rregullisht bllokonte list\u00ebn e incident\u00ebve aktiv\u00eb dhe pengonte pun\u00ebn operative. Logjik\u00ebn dhe diferencimin vizual t\u00eb ngjyrave t\u00eb njoftimeve e konsideruam t\u00eb suksesshme dhe e ruajt\u00ebm, megjithat\u00eb n\u00eb TZ sakt\u00ebsisht e theksuam se njoftimet \"e bardh\u00eb\" duhet, pa t\u00ebrhequr v\u00ebmendjen e rojeve, t\u00eb \"shp\u00ebrndahen\" n\u00eb heshtje n\u00eb nj\u00eb seksion t\u00eb ve\u00e7ant\u00eb, ku do t\u00eb merret me to specialist\u00ebt komercial\u00eb.<\/li>\n<\/ol>\n

      \nMe nj\u00eb nivel t\u00eb ngjash\u00ebm detajesh ishin shkruar format e nd\u00ebrtimit t\u00eb grafik\u00ebve dhe nxjerrjes s\u00eb raporteve, konturet e nd\u00ebrfaqeve, lista e pajisjeve q\u00eb duhej t\u00eb monitoroheshin dhe shum\u00eb gj\u00ebra t\u00eb tjera.\u00a0<\/p>\n

      Ishte nj\u00eb pun\u00eb me t\u00eb v\u00ebrtet\u00eb kreative e tri grupeve t\u00eb pun\u00ebs \u2013 sh\u00ebrbimit t\u00eb klientit, i cili diktonte k\u00ebrkesat dhe kushtet e tij; specialist\u00ebve teknik\u00eb nga t\u00eb dyja an\u00ebt, t\u00eb cil\u00ebt kishin p\u00ebr detyr\u00eb t\u00eb shnd\u00ebrronin k\u00ebto kushte n\u00eb dokumentacion teknik; ekipit t\u00eb programuesve t\u00eb kontraktorit, t\u00eb cil\u00ebt realizonin k\u00ebrkesat e klientit sipas dokumentacionit teknik t\u00eb hartuar... Si rezultat, disa nga k\u00ebrkesat tona t\u00eb paq\u00ebndrueshme i p\u00ebrshtat\u00ebm me funksionalitetin e platform\u00ebs ekzistuese, disa kontraktori u angazhua t'i shkruante p\u00ebr ne.\u00a0<\/p>\n

      Pun\u00eb paralele e dy sistemeve<\/h2>\n

      \n\"Monitorimi
      \nKa ardhur koha e realizimit. N\u00eb praktik\u00eb, kjo do t\u00eb thoshte se i japim kontraktorit mund\u00ebsin\u00eb t\u00eb zhvilloj\u00eb nj\u00eb prototip t\u00eb BMS n\u00eb retn ton\u00eb virtuale dhe t\u00eb japim akses n\u00eb rrjet p\u00ebr t\u00eb gjitha pajisjet q\u00eb k\u00ebrkojn\u00eb monitorim.<\/p>\n

      N\u00eb k\u00ebt\u00eb moment, megjithat\u00eb, sistemi i ri nuk ishte ende gati p\u00ebr pun\u00eb. N\u00eb k\u00ebt\u00eb faz\u00eb, ishte e r\u00ebnd\u00ebsishme p\u00ebr ne q\u00eb t\u00eb ruanim monitorimin n\u00eb sistemin e vjet\u00ebr dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb t'u jepnim akses pajisjeve n\u00eb sistemin e ri. Nuk \u00ebsht\u00eb e mundur t\u00eb nd\u00ebrtohet nj\u00eb sistem normalisht, pa par\u00eb brenda tij pajisjet, t\u00eb cilat nga ana tjet\u00ebr nuk mund t\u00eb \u00e7aktivizohen nga monitorimi i sistemit t\u00eb vjet\u00ebr.\u00a0<\/p>\n

      A do devices withstand simultaneous polling by two systems, it was not obvious without real trials. There was a chance that dual simultaneous polling would lead to frequent response failures from the devices, resulting in numerous errors due to device unavailability, which would in turn block the operation of the old monitoring system.<\/p>\n

      The network department routed virtual paths from the prototype of the new BMS deployed in the cloud to the devices, and we received the results:\u00a0<\/p>\n