NGMS Solution Architecture (V0-9 Update)

8/13/2019 NGMS Solution Architecture (V0-9 Update)

1/22

Corporate Information Services (CIS)

Business Analysis, Architecture and Solutions

Solution Architecture

National Groundwater Modelling System (NGMS)

Author Illyr Bosniak

Enquiries To Illyr Bosniak / Steven SmithVersion 0.9

Status !date

u!lished on "#th $anuary "00#

Template Version %.&

Authorised By ''uthorised By (ustom *ro!erty)++

"aster #ile $ocation ,,-NN%,1,B2I-,*ro3e4t r4hite4ture 5ile *lan,09*rogrammes and *ro3e4ts,IS *ro3e4ts,NGMS,5ilesut,%9%9%C.do4

he re4ommendations in this !a!er are valid 8or a !eriod o8 si% monthsa8ter the authorisation date. I8 the !ro3e4thas not im!lemented the re4ommendations within this !eriod the !ro3e4t must 4onsult with the *ro3e4t r4hite4tureteam to 4on8irm the 4on4lusions and re4ommendations in this re!ort 4ontinue to e a!!ro!riate.


2/22

National Groundwater ModellingSystem (NGMS)

:ersion; 0.9

Solutions r4hite4ture 1ate; "#th $anuary "00#

'do4ument identi8ier+

&istri!ution $ist ('an Approved $ist)

Business Analysis,Architecture And Solutions(BAAS)Maggie Bosniak BS Manager uthorisation*eter /ommentSteven Smith *ro3e4t r4hite4t *eer 2eview$a4?ui S!en4er !!li4ations ar4hite4ture omment

ro*ect TeamIS *rogramme Manager In8ormation

Mark Sherwood IS *ro3e4t Manager ommentBusiness nalyst In8ormation

Service &eliveryNaresh Mistry *GI @ *ro3e4t -ntry Manager ommentMaeve M4Neela est Strategist omment=aura 1oyle S1 e4hni4al Standards ommentIain Blairhris Meredith

S1 r4hite4t eam =eaderIn8rastru4ture *rogramme Manager

ommentomment

revor Brown vailaility and a!a4ity Manager ommentndrew Irving Servi4e =evel Management ommenthris -meny*aul $ohnson

Strate+ic and Architecture

Su!!ort and Maintenan4eS1 "nd=ine

ommentomment

1al3it Banger hie8 r4hite4t ommentom *ayne -nter!rise r4hite4t ommentSteve $ones IS Se4urity 88i4er omment

Supplier

ame to !e inserted*ro3e4t Manager In8ormation

-evision .istory

:ersion 1ate *ulished mendments

0.A %7

th

1e4emer"00 =atest 1ra8t @ (uthors $ohn Bridgen/2i4hard $asi4ki)

0.# "#th5eruary"00A

:ersion 8ollowing in4or!oration o8 review 8eeda4k 8or 0.A 125(uthor Nigel $ohnson) @ !!roved do4ument

0.9 "#th$anuary "00# Maintenan4e u!date to a!!roved solution ar4hite4ture do4ument to4on8irm solutions ar4hite4ture remain a!!ro!riate

on8idential -nvironment gen4yC "0%& *age " o8 ""


3/22


:ersion; 0.9



Contents

1 EXECUTIVE SUMMARY...................................................................................................................................4

1.1 CONCLUSIONS...................................................................................................................................................4

1.2 RECOMMENDATIONS.........................................................................................................................................4

2 INTRODUCTION.................................................................................................................................................6

2.1 BACKGROUND...................................................................................................................................................6

2.2 DOCUMENTOBJECTIVES...................................................................................................................................6

2.3 DOCUMENTSCOPE............................................................................................................................................6

2.4 SUMMARYOFBUSINESSREQUIREMENT...........................................................................................................7

3 HIGH LEVEL SOLUTION ARCHITECTURE................................................................................................9

3.1 LOGICALARCHITECTURE.................................................................................................................................

3.2 PHYSICALARCHITECTURE..............................................................................................................................11

3.3 DATAVIE!....................................................................................................................................................11

3.4 INTEROPERABILITYVIE!...............................................................................................................................124 HIGH LEVEL SOLUTION COMPONENTS..................................................................................................13

4.1 MASTERCONTROLLER"MC# .........................................................................................................................13

4.2 DATABASESERVER "DB#...............................................................................................................................13

4.3 MODULE$SHELLSERVER................................................................................................................................13

4.4 OPERATORCLIENT "OC#................................................................................................................................13

5 TEST ARCHITECTURE...................................................................................................................................13

6 HIGH LEVEL INFRASTRUCTURE DEFINITION......................................................................................14

6.1 CLIENT............................................................................................................................................................14

6.2 COMMUNICATIONS..........................................................................................................................................1%

6.3 SERVER...........................................................................................................................................................1%

6.4 SUPPORTSERVICES.........................................................................................................................................16

7 SECURITY..........................................................................................................................................................16

7.1 CONFIDENTIALITY...........................................................................................................................................167.2 ACCESSANDAUTHENTICATION.....................................................................................................................16

7.3 DATAINTEGRITY............................................................................................................................................16

7.4 NON&REPUDIATION..........................................................................................................................................16

7.% AVAILABILITY.................................................................................................................................................16

8 DATA MIGRATION..........................................................................................................................................16

9 COMPLIANCE...................................................................................................................................................17

.1 ENTERPRISEARCHITECTUREGUIDANCE........................................................................................................17

.2 UK GOVERNMENTSTANDARDS.....................................................................................................................1'

1 RE!USE..............................................................................................................................................................18

1(.1 USEOFE)ISTINGCOMPONENTS....................................................................................................................1'

1(.2 OPPORTUNITIESFORRE&USE.........................................................................................................................1'

11 RIS"...................................................................................................................................................................18

12 CONCLUSIONS................................................................................................................................................19

13 RECOMMENDATIONS..................................................................................................................................19

14 REFERENCES..................................................................................................................................................2

15 GLOSSARY.......................................................................................................................................................2

16 APPENDIX A....................................................................................................................................................21

on8idential -nvironment gen4yC "0%& *age & o8 ""


4/22


:ersion; 0.9



/ E%ecutive Summary

he Groundwater Modelling (GM) 8un4tion has re4ognised the need 8or an overar4hing I 8rameworkto su!!ort the stru4tured and 4ontrolled running o8 groundwater models. his re4ognition has arisen8rom a numer o8 GM initiativesC namely a Strategi4 2eview o8 GMC a summary im!lementation !lan(!rodu4ed y the Dead 88i4e Dydrogeology team). hese models have een develo!ed at a 4ost o8hundreds o8 thousands o8 !ounds (in some 4asesC) and !resently run in dedi4ated


5/22


:ersion; 0.9



1ata 4ustodian and IS Se4urity undertake data 4lassi8i4ation and risk assessment to enalese4urity re?uirements to e 8ed into essella 8or the system under develo!ment

he !ro3e4t should 4onsider the 8easiility o8 using the o88line/test environment 8or !rodu4tion in adisaster re4overy s4enario

on8idential -nvironment gen4yC "0%& *age 7 o8 ""


6/22


:ersion; 0.9



1 Introduction

10/ Bac2+round

he Groundwater Modelling (GM) 8un4tion has re4ognised the need 8or an overar4hing I 8rameworkto su!!ort the stru4tured and 4ontrolled running o8 groundwater models. his re4ognition has arisen8rom a numer o8 GM initiativesC namely a Strategi4 2eview o8 GMC a summary im!lementation !lan(!rodu4ed y the Dead 88i4e Dydrogeology team). hese models have een develo!ed at a 4ost o8hundreds o8 thousands o8 !ounds (in some 4asesC) and !resently run in dedi4ated


7/22


:ersion; 0.9



5or 4larity in this Solution r4hite4tureC mu4h o8 the 4ontent in4luding all the diagrams have eenre!rodu4ed 8rom the r4hite4ture 1esign 1o4ument with !ermission.

he s4o!e o8 this do4ument is the envisaged highlevel solution ar4hite4ture to e delivered y the*hase 6 rollout o8 the National Groundwater Modelling System ut does not yet in4lude 4onsiderationo8 the ar4hiving susystem.

105 Summary of Business -equirement

he 8ollowing usiness re?uirements were identi8ied in the NGMS e4hni4al ssessment.

he GM 8un4tion within the gen4y has a numer o8 Hmodules and data sets that !resently o!eratewithin nonstru4tured Hstand alone environments. here is little in8rastru4tureen8or4ed 4ontrol over therunning o8 these modules against eEisting GM models and data sets nor is any audit trail is !rodu4ed.

Given the signi8i4ant eE!enditure invested in model develo!ment to dateC the 8ramework must e

4a!ale o8 running eEisting G< models without modi8i4ation.

numer o8 4onsultants are working (8or the gen4y) remotely (i.e. not 8rom gen4y !remises). t!resent these 4onsultants re?uire 4o!ies o8 oth module and data sets to o!erate within their ownstand alone environments.

It is !er4eived that there is a needC within the ody o8 eEternal organisations that the gen4y regulates(e.g.


8/22


:ersion; 0.9



In the event o8 the loss o8 or damage to the hosting 8a4ility the gen4yJs eEisting A" hour disasterre4overy arrangements will a!!ly. No interim servi4e will e eE!e4ted within this A" hour !eriod.

Access to Service

he servi4e will e used y gen4y sta88 ased in the regions during normal o88i4e hours. 44essoutside o8 these hours is desirale ut not mandated as a re?uirement.

&ata Security and -ecovery

In the event o8 data storage in8rastru4ture 8ailure the maEimum !eriod o8 a44e!tale data loss is "6hours. ver weekend or holiday !eriods this should e?uate to A" hours 8rom the last working day.

7sers (profile 8 num!ers) and erformance

numer o8 roles have een identi8ied. hese are listed elow with total and 4on4urrent usageestimates assigned to ea4h.

-ole "a%0 no 7sers "a%0 Concurrent users

:iewers K sers (internal) '&00 %7

ustodian (internal only) %7 &

National Su!er ser (internal only) " "

System Manager (IS role) % %

&ata classification0

he data that will e held within the !rodu4tion system delivered in !hase 6 has not een 8ormally4lassi8ied and a risk assessment/data 4lassi8i4ation eEer4ise should e undertaken y the data4ustodian in 4on3un4tion with IS Se4urity.

he systemC whi4h is still in develo!mentC does not 4urrently authenti4ate users or a!!ly role aseda44ess to system resour4es 4onse?uently !rior to the risk assessment only nonsensitive data shoulde held within it.

&ata volume and archive requirements0

he 8ollowing tale !resents estimates o8 the initial data storage re?uirements 8or NGMS !hase 6!rodu4tion (online) systemC as do4umented in Dardware K In8rastru4ture 1esign 1o4ument L %6 andased u!on the 8inding during the !hase & !ilot im!lementation. he 8igure in4ludes a douling o8a4tual re?uired storage s!a4e to enale disk to disk a4ku! to e taken.

he year %C Oear "C values re!resent an assumed growth o8 "7F !.a.

Totalstora+erequired

(9B)

Initial data load %A70

on8idential -nvironment gen4yC "0%& *age # o8 ""


9/22


:ersion; 0.9



Oear % ""00

Oear " "A70

Oear & &700

Oear 6 6&A7

he data storage re?uirements 8or the o88line/ testing system will e de!endent u!on whether or notthe test system will host a 8ull instan4e o8 the !rodu4tion systemC in4or!orating the # regions or a singlePworst 4ase region.

he N55S !ro3e4t is 4urrently investigating the !re8erred ar4hiving solution 8or its re?uirements. It islikely to e an eEternal system (i.e. a se!arate dataase and management tool 8rom the 4ore solution).NGMS will !roaly 8ollow the same routeC there8ore the ar4hiving re?uirements will not e 4onsidered8or the design o8 the 4ore in8rastru4ture o8 NGMS.

4 .i+h $evel Solution Architecture

he Solutions r4hite4ture is eE!ressed using a numer o8 di88erent view!oints to des4rie the targetar4hite4ture re?uired to 8ul8il the identi8ied re?uirements in4luding; =ogi4alC 1ataC *hysi4al and Se4urity.


10/22


:ersion; 0.9



his logi4al view o8 the NGMS system shows the 8un4tionality o8 ea4h o8 the ma3or 4om!onents. -a4hsigni8i4ant 4om!onent is des4ried in overview in the 8ollowing suse4tions.

40/0/ System Controller : &ispatcher

he system 4ontroller / dis!at4her s4hedules and dis!at4hes re?uests 8or model runs and othera4tivities. It understands the state o8 ea4h o8 the a4tive models and 4om!onents.

40/01 Central Stora+e

entral dataase storage 8or all model datasetsC re!orts and models.

40/04 &ata "anipulation 7tilities

sed 8or editing model data.

40/05 &ata Import and E%port 7tilities

tilities used 8or im!orting and eE!orting data to and 8rom the NGMS system.

40/0; "odule Controller

ontrols the eEe4ution o8 the models.

40/0< Adapter(s)

*rovides the inter8a4e to &rd!arty so8tware.

40/0= "odule(s)

he modules are so8tware written s!e4i8i4ally 8or NGMS to !rovide the modelling 4a!ailities.

40/0 Thic2 Client 7ser Interface

*rovides the modelling user with the aility to 4ontrol the in!ut and out!ut to/8rom models.

40/0> Thin Client 7ser Interface (?e! Bro@ser)

*rovides the user with the aility to view any out!ut datasets that are !ulished on the we server

4om!onent.

40/0/ -eport u!lisher

Generates all data that will e availale on the we server to thin 4lient users.

1es4rie logi4al astra4tion layer

on8idential -nvironment gen4yC "0%& *age %0 o8 ""


11/22


:ersion; 0.9



401 hysical Architecture

he *hysi4al r4hite4ture shown in the diagram elow will a!!ly to the 8ull system in the *hase 62ollout.

he diagram illustrates the !ro!osed ar4hite4ture. he key !oints are as 8ollows;

single =inuE ased server to host the Master ontroller 4om!onents

single =inuE server to host the ra4le So8tware and 1ataases.

44ess to shared network storage 8or the ra4le dataase.

t least 7 Shell Servers in *rodu4tion.

Swit4h to allow a dedi4ated link etween the Master ontroller/1ataase server and the shellservers. Signi8i4ant network tra88i4 is re?uired etween these 4om!onents and re?uires isolation8rom the main network tra88i4.

404 &ata Vie@

he data view is illustrated in the diagram elow.

on8idential -nvironment gen4yC "0%& *age %% o8 ""


12/22


:ersion; 0.9



Module data sets Boundary 4onditions

IN*. 1. S-.S

0.*. 1. S-.S

Module results

SOS.-M IN.-2N= 1.

he data held within the system 4om!rises all the in!ut data re?uired to run a moduleC the out!ut datagenerated as a result o8 running a module and the system 4on8iguration data re?uired y the Masterontroller to enale it to 8un4tion as re?uired.

405 Interopera!ility Vie@

he intero!eraility view is illustrated in the diagram elow.

1ata9ase (1B)

NIQ

Master

ontroller (M)

NIQ

Module/Shell

servers

0ra4le


13/22


:ersion; 0.9



s 4an e seen 4ommuni4ation o8 the data sets etween the shell server and the dataase server viathe Master ontroller is y means o8 the $ava Messaging Servi4e ($MS). here are no 4urrent !lans 8orthe solution to intera4t with any eEternal systems. lthough the o!erator 4lient will enale users toundertake a 4ertain amount o8 system 4on8iguration loading o8 new data sets will e undertakenmanually at the 4entral systems.

5 .i+h $evel Solution Components

50/ "aster Controller ("C)

he Master ontroller (M) 4om!onents are the heart o8 the server. he M is a 4entral managementa!!li4ationC to 4ontrol the 3o s4heduling and data eE4hange etween the 4lientC the 4entral dataaseand the shell server. he M 4ontains a askManager whi4h maintains a task list and s4hedules anddis!at4hes tasks to shell servers via $MS.

he M will e hosted on a SuSe =inuE !lat8orm and re?uires the 4urrent version o8


14/22


:ersion; 0.9



DoweverC the !hase & !ilot delivered a D*Q ased solution and as the !hase 6 solution will eased around SuSe =inuE then it will re?uire a test/o88line system that is also ased around SuSe=inuE.

he test ar4hite4ture is illustrated in the diagram elow.

Master ontroller /

1ata9ase (M/1B)

NIQ


15/22


:ersion; 0.9




16/22


:ersion; 0.9



he !ro!osed server hardware re?uired 8or im!lementing the solution on either Blade or traditionalserver hardware is !rovided in !!endiE % and is su3e4t to 4hange as the 4osts are !urely indi4ativeand re?uire 4on8irmation.

he o!erating system and 4ore a!!li4ations will all e installed using 2I1 % (Mirrored) disk arrayswith the shared storage re?uirement 8rom the -nter!rise Storage rea Network initially estimated at%.7 @ ".0 and eE!e4ted to grow to & in &7 years .


17/22


18/22

the same a!!roa4h as N55S.

*rin4i!le %& @ -nsure se4urityC 4on8identiality and !riva4y o8in8ormation

-E!e4ted to e 4om!liant. . he data4ustodian and IS Se4urity shouldundertake data 4lassi8i4ation and riskassessment to 4on8irm this; see2e4ommendations (%&)

*rin4i!le %6 @ onstrain diversity om!liant.

*rin4i!le %7 @ !timise servi4e ?uality 8or a!!ro!riateBusiness ontinuity

-E!e4ted to e 4om!liant. hiseEtended !ilot !hase o8 NGMS will!rove that the N55S ar4hite4ture isan a!!ro!riate !lat8orm 8orgroundwater models. he servi4e wille de8ined during the !ilot.

>01 7 9overnment Standards0

he solution is 4om!liant with the eGi8 mandate on the use o8 QM= 8or data integration (as QM= isused 8or data eE4hange etween the Master 4ontroller and Module/Shell Servers).

/ -e6use

/0/ 7se of e%istin+ components

he NGMS design is 8undamentally the same as that used y N55S.

/01 3pportunities for re6use

s this !roves and demonstrates the eEtensiility o8 the N55S ar4hite4ture that ar4hite4ture is!otentially made more widely reusale.

// -is2

he !ilot eEer4ise identi8ies the need 8or


19/22

/1 Conclusions

he !ro!osed ar4hite4ture is ased on an eEisting *rodu4tion systemC is already eing !iloted andhas een devised and develo!ed y a su!!lier (1el8t Dydrauli4s and essella) with a !roven tra4kre4ord o8 delivery.

he ar4hite4ture 4om!lies with ar4hite4tural standards.

he ar4hite4ture is de4ou!led and s4alaleC and there8ore has the 8leEiility to 4o!e with 4hange.

/4 -ecommendations

he o88line and online systems use the agreed SuSe =inuE -nter!rise Server (S=-S) and


20/22

/5 -eferences

%. e4hni4al Standards SummaryC :ersion 7.AC sh 1attani (hie8 r4hite4t) -nter!rise r4hite4tureeam.

". -nter!rise r4hite4ture verar4hing *rin4i!lesC :ersion AC sh 1attani (hie8 r4hite4t)C -nter!riser4hite4ture eam.

&. e4hni4al 2e8eren4e Model (2M)C :ersion ".7C *aula DarrisC -nter!rise r4hite4ture eam

6. NGMS&DIS:0."rdware K In8rastru4ture 1esign 1o4umentC :ersion 0."C $ohn God8reeC essella

7. NGMS6!lanningTv"C :ersion "C *eter Gi3sersC essella

/; 9lossary

erm -E!lanation

Model !rogram modelling the ehaviour o8 groundwater.hese are 4urrently hosted lo4allyC ut under this!ro!osal the models will e hosted 4entrally on theshell servers.

N55S National 5lood 5ore4asting System; a !rodu4tionsystem that trailed the use o8 the ar4hite4ture now!ro!osed 8or NGMS

NGMS National Groundwater Modelling System

Shell server server hosting one or more o8 the groundwatermodels. Sometimes also 4alled an 5SS Server or a

5-


21/22

/< Appendi% A

Blade 3ption Indicative Cost 4

"aster Controller Server (/uad 4ore (% E >uadore Qeon Q7&77 / ". GD 2M " GB Gigait-thernet) %

dditional *ro4essor (>uadore Qeon Q7&77 / ". GD) 0

6G Memory Module 6

%6G SS 1isk "

SN Meanine DB %

&B Server (/< 9B) (..) DT

B=604 >uad 4ore (% E >uadore Qeon Q7&77 / ". GD 2M " GB Gigait-thernet) %


6G Memory Module 6

%6G SS 1isk "

SN DB %

Shell Server (uad 4ore (% E >uadore Qeon Q7&77 / ". GD 2M " GB Gigait-thernet) %


6G Memory Module %

%6G SS 1isk "

SN DB %

Enclosure Costs DT

4A000 BladeSystem hasssis ; Su!!orts #E5D or %EDD Blades ; %0 %

:irtual onne4t -thernet "

ooling 5ans %0

:irtual onne4t SN 5ari4 "

*ower Su!!ly nits

Advanta+es

88ers a more s4alale solution ased on manu8a4ture re4ommendations 8or modelling and

simulation a!!li4ations

-asily eE!anded as & slots will remain in the 4hassis 8or eE!ansion or in4lusion o8 resilien4y i8

re?uired and ?uad 4ore !ro4essors with o!tion to add se4ond !ro4essor rather than add more!hysi4al ma4hines


22/22

akes u! less !hysi4al s!a4e (%0 o8 ra4k s!a4e)

Date post:	04-Jun-2018
Category:	Documents
Upload:	smitasamrat
View:	221 times
Download:	0 times

NGMS Solution Architecture (V0-9 Update)

Documents