170 likes | 250 Views
Project CORES PRJ-0079079 FM Applications Infrastructure Workshop. Stéphane Courtin, GPM Oct 13th , 2010. Agenda. Objective of the workshop Background information Team Workshop Next steps. Agenda. Objective of the workshop Background information Team Workshop Next steps.
E N D
Project CORESPRJ-0079079FM Applications InfrastructureWorkshop Stéphane Courtin, GPM Oct 13th, 2010
Agenda • Objective of the workshop • Background information • Team • Workshop • Nextsteps
Agenda • Objective of the workshop • Background information • Team • Workshop • Nextsteps
Objective of the Workshop • Some FM Security applications and systems have to bedeployed to support hte new CORES building • Today’s objective is to • providerecommendation on possible Infrastructure solutions thatwould fit with the requirements • Defineconstraints • Open questions whereneeded
Agenda • Objective of the workshop • Background information • Team • Workshop • Nextsteps
BackgroundBelgium Sites • Belgium – Brussels (BRU) CORES Building Alma Court ELC Legal GMED Dilbeek JJMedical Biosense Waterloo Cordis
Agenda • Objective of the workshop • Background information • Team • Workshop • Nextsteps
Participants • BU I/T • André Koch overall Project TechnicalLead – MDD BU I/T • JanneRummukainen Janssen I/T CISO supporting FM • TBD Janssen I/T supporting FM Application • WWE • Dominique Lammerant WWEProject Manager • Dany Wouters () • Johan de VriendtHonewell Project Manager • I/T Shared Services • Hiten Shah Solution Integrator • Nick Keating Beacon – Network Cabling • Luc Kneepkens Global Network (LAN/WIFI) • Hans Tuytelaars Global Network (WAN/Firewall) • Ryan Sobray WWIS • Kor de Vries Business Continuity • Nancy de Blecker I/T SS Q&C • Luc Vanparijs Backup • Guido VanmeertiPC Support • Stéphane Courtin Infrastructure Project Manager
Participants – constraints • BU I/T CISO identified – has not been onboardedyet • BU I/T Janssen PM not identified • Honeywell not availabletoday • The team willworktoday on somelimited scenarii based on realistichypothesis • Recommendationswillbesharedwith all Stakeholders • Based on stakeholders feedback, follow up workshop willbeorganized to come to the Final Design
Agenda • Objective of the workshop • Background information • Team • Workshop • Nextsteps
WorkshopInitial Scope and Requirements • Scope & Requirements • EBI Security (Intrusion detection, FireAlarm, Access Control) • 1 Production Server in Beerse • 1 Stand By/Fail over Server in Beerse • 1 Security workstationwith 3 screens in Beerse • 1 Security workstationwith 1 42 ’’screen in Beerse • 1 Security workstationwith 3 screens in Brussels • Communication between EBI servers/workstations/DVM Servers • DVM (Digital Video Management) • 1 Production Server in Brussels • 1 Production Database Server in Brussels • 1 Stand By/Fail Server in Brussels • 1 Stand By/Fail Database Server in Brussels • Dedicated Network for Video Cameras • Communication between EBI servers/workstations/DVM Servers – 160Mb needed (average) between Beerse and Brussels, so image from 6 cameras (out of 14+) canbedisplayed on Beerse Security PC • EBI and DVM Wintelservers and workstations • Cannotbepatched (OS, MSSQL…) before validation from Honeywell (21 daysleadtime) • Have to beaccessedremotely by externalvendor (Honeywell) for remote support
WorkshopOutcomes Option 1 – Infrastructure managed by ITSS • ITSS provides and supports Servers, Network LAN and WAN for FM Applications • All FM devices must be on Isolated Network • To allowsystems to NOT bepatchedaccording to J&J schedule – Patching R&R TBD • To allowremoteaccessfromexternalvendor • The CORES Building connectionwillbe 1Gb redundant LAN Extension to Beerse • It willprovide full diversity • Itsbandwidthcanbeadapted in the future (for explstartwith 1Gb thendecrease if real consumption shows lowerneed) • IsolatedVLANs • canbedistributed over LES between Brussels and Beerse • Isolated VLAN will have to beconfigured on all Network switches (Beerse + Brussels) wheresome CORES FM deviceswillbeplugged (security PC, servers…) • No new Network HW isneeded to implementthis, but thiswillrequireadditional config work • Remoteuserscan have access to IsolatedVLANs
WorkshopOutcomes • EBIServers • have to bephysical servers, sotheycanbeisolated (isolation of VM has never been testedatJ&J, current EBI in Beerse is not isolated) • Will belocated in Beerse (exact location TBD) • Will be DL385G7 – detailledspecs to belookedat • Similar solution exists in Raritan (Hiten to share contact name) • DVM Servers • must be in Brussels with local backup system • Will be DL385G7 – detailledspecs to belookedat • Must beconnected to EVA SAN Storage to store the 5Tb +2Tb + xGb, and to allow SAN Backup (avoid LAN Backup fromIsolated Network, thatwouldsaturate the LES)SAN Model to bedefined by the Storage team • Requiredbandwidth for Cameras to beconfirmed HNW (todaypresented as 36Mb per camera, more than Global Connect…) • 2 additional Cisco switcheswillberequired for the Camera Network – Needspecsfrom HNW
WorkshopOutcomes • PC • PCswith 3 screensnevertested. Guido to check with Lenovo if thisissupported. • If Lenovo OK, canbesupported by iPC team • Needspecsfrom HNW on screensresolution and refresh rate required • Will be on Isolated VLAN
WorkshopOutcomes • Option 2 – Solution fullymanaged by HNW • PCs, Servers, Network LAN, WAN circuits provided and supported by HNW • No connection to JJNET • Requires NTR Waiver • Requiresthat the whole Infrastructure isprovided and managed by HNW, including Network linkbetween Beerse and Brussels • HNW to add WAN Infrastructure and circuits in the Design/Budget, dedicated to FM Applications • Having communication betweenIsolatedVLANs out of ITSS control, between 2 sites, is not an option