Duck creek Architect

Role:1

 

Responsible for the design and build out of the Oracle Solaris platform. This includes the design of the Logical domains required and the design of the Oracle VM Manager to control the configuration of the SOLARIS platforms running on Oracle Solaris T7 series hardware. Experience of the design of environments to support large Oracle databases including Oracle Dataguard and eBusiness suite.

 

Role:2

 

Network architect with a broad understanding of network technologies and experience of design and implementation for detailed data centre design and build project. Requires specific experience of CISCO technologies including network routing switching and security. Certification and/or experience of CISCO products including ASR and CISCO Firepower an advantage.

 

Role:3

Strong project manager with experience of upgrade and decommissioning projects. Will be required to manage • Decommissioning of existing data centre environment alongside managing a Wintel upgrade. • Expected to be on customer site up to 4 days per week. • Must have demonstrable experience of good control of project delivery using Prince 2 or equivalent. • Will be working as part of a large programme team of 65 people.

Role:4

 We need an expert who would have experience in writing the Data Centre Operations Manual and Procedures. Manual needs to contain below set of information. WAN Connectivity Management (adding a remote location, routing, WAN encryption, aggregation etc) • Firewall Administration (create/modify/decom) • Load Balancer (create/modify/decom) • Workload integration (adding New Devices to the Fabric) • Data Plane policing (e.g. changing the bandwidth consumption policies, i.e. QoS) • Alert Management (processing of monitoring traps) Storage Create/update procedure for Firmware upgrades Create/update procedure for Storage Fault management Create/update procedure User account management Create/update procedure Network interface management Oracle Hardware – where Databases reside T7-4 and M12 hardware procedures to be replicated based on current T4/T5 and M8000.

Role:5

A list of duties(JD) for a Migration Engineer: • App discovery – either workshop with SMEs or email to get migration questionnaire filled out. This forms basis for migration design document. • Attend regular update meetings with customer and Atos teams for progress on deliverables, any issues and potential risks and blockers. • Create MDD (migration design document) detailing CMO and FMO architecture, needs to include detailed HLD and LLD if required. • Attend customer IRF (Infrastructure Review Forum) meetings to get approval for any newly deployed servers that form basis for App being migrated i.e. fresh SQL servers or Print servers that integrate to the moved App. • MDD needs peer review and subsequent walkthroughs with customer and App SMEs to get approval. • Populate firewall templates for network team to create rules to allow the migrated App to work in its new environment. • Create necessary proxy rules to allow internet connectivity for Apps that require it. • Create change request tickets and seek approvals from all support teams identified within the App. • Attend customer CAB to get approval for changes and for migration to go ahead. • Detailed run books need creating documenting all steps required by Atos and CBS IT teams during migration work this needs to include timings and touchpoint comms to stakeholders. • Liaise with test teams to rectify defects during IVT, AVT, and UAT testing via HP Application LifeCycle Manager. • Post migration support activities include customer HyperCare period with senior CBS management teams to update any issues on regular sunrise calls. Lasts 2 weeks after App migration. Potential out of hours cover required during this time.

Role:6

 A list of duties(JD) for a Migration Engineer: • App discovery – either workshop with SMEs or email to get migration questionnaire filled out. This forms basis for migration design document. • Attend regular update meetings with customer and Atos teams for progress on deliverables, any issues and potential risks and blockers. • Create MDD (migration design document) detailing CMO and FMO architecture, needs to include detailed HLD and LLD if required. • Attend customer IRF (Infrastructure Review Forum) meetings to get approval for any newly deployed servers that form basis for App being migrated i.e. fresh SQL servers or Print servers that integrate to the moved App. • MDD needs peer review and subsequent walkthroughs with customer and App SMEs to get approval. • Populate firewall templates for network team to create rules to allow the migrated App to work in its new environment. • Create necessary proxy rules to allow internet connectivity for Apps that require it. • Create change request tickets and seek approvals from all support teams identified within the App. • Attend customer CAB to get approval for changes and for migration to go ahead. • Detailed run books need creating documenting all steps required by Atos and CBS IT teams during migration work this needs to include timings and touchpoint comms to stakeholders. • Liaise with test teams to rectify defects during IVT, AVT, and UAT testing via HP Application LifeCycle Manager. • Post migration support activities include customer HyperCare period with senior CBS management teams to update any issues on regular sunrise calls. Lasts 2 weeks after App migration. Potential out of hours cover required during this time.