This is a remote position.
EXPERIENCE AND EDUCATION:
Essential Qualifications/Experience:
· A deep understanding of the complexity and challenges of application synchronization across data centres in different geographic locations. (at least one project as reference in the CV in the role of technical lead or responsible architect in the last 3 years)
· Prior experience and successful implementation of tasks substantially similar (including ArcGIS Enterprise) to those specified in this SOW. (at least one reference project in the CV in the role of technical lead or responsible architect in the last 3 years)
· Thorough expertise of ArcGIS Enterprise architecture and best practices in an Enterprise Environment with synchronization business scenarios. (at least one reference project in the CV in the role of technical lead or responsible architect in the last 3 years)
DUTIES/ROLE:
WP ID |
Work Package Title |
WP1 |
Identify and document the synchronization needs |
Based on the Agency provided information on the NATO Core GIS Design/Architecture as well as the underlying IaaS and PaaS the Contractor shall identify and define all synchronization needs for the objective described before, incl. a. CoreGIS data, services, configurations, b. Account information c. Underlying PaaS service configurations like Load Balancer, Anti-Virus, firewall… Within this work package the contractor shall also a. Conduct one workshop (up to one (1) day) in The Hague (NLD) at the Agency’s premises to kick off the project, demonstrated the understanding of the objective and clarify with SMEs from the Agency the use case as well as identifying any additional information required from The Agency to execute WP1. b. Hold a system requirements review meeting (SRR) (up to one (1) day) in The Hague (NLD) at the Agency’s premises to present the identified synchronization needs. Based on the review meeting with the Agency the Contractor will prepare the final requirements to close out this work package. |
|
ID |
Deliverable(s) Description |
D1 |
Kick off meeting including clarification questions from the Contractor on technical environment as is design/architecture |
D2 |
System Requirements review (SRR) |
D3 |
Final requirements |
ID |
|
C1 |
|
C2 |
|
ID |
Acceptance Criteria |
A1 |
The final requirements are comprehensively all synchronization needs required to be addressed in the following work packages to achieve the objective as described above. As a minimum this shall include: a. CoreGIS data, services, configurations, b. Account information c. All underlying PaaS services required by the Core GIS to function seamlessly like: Identity Management Services, Access Management Services, Cyber Security Services (e.g. anti virus, firewall), File System Services, Database Services, Load Balancing Services. |
A2 |
Documented each synchronization need and the required synchronization cycle/currency of the synchronization |
A3 |
Documentation meets the requirements |
A4 |
Kick off meeting and SRR successfully completed. Contractor provided minutes of the meeting accepted by the Agency |
Additional Notes |
|
N/A |
WP ID |
Work Package Title |
WP2 |
Analyse propose and evaluate synchronization options |
For the in WP 1 agreed synchronization needs the Contractor shall identify different solutions (procedural and technical) analyse them and compare them against each other according the following parameters a) Level of automation b) Technical complexity c) Manual/procedural effort d) Min synchronization time achievable e) Usage of underlying IaaS/PaaS synchronization options, including availability in the Purchaser’s CIS environment. The Contractor shall review the parameters at the start of the work package and suggest additional or changes to them. The final set of parameters the synchronization options are evaluated against shall be agreed with the Purchaser. The Contractor shall hold two (2) preliminary design review (PDR) meetings: 1) PDR 1 shall be a one (1) day meeting in The Hague (NLD) at the Purchaser’s facility, where the Contractor will present all synchronization options identified for all synchronisation needs and present for at least 50% of the synchronization needs the comparison against the parameters. The Contractor shall incorporate all changes required as identified in PDR 1 not later than in the deliverables for PDR 2. 2) PDR 2 shall be held as an online meeting. The Contractor will present all synchronization options identified for all synchronisation needs including the complete comparison against the parameters. At the end of the meeting for each synchronization need the option to go forward into the final design (WP 3) will be agreed by the Purchaser. |
|
ID |
Deliverable(s) Description |
D1 |
Documented synchronization options and comparison against parameters for all synchronization needs identified in WP 1 |
D2 |
Preliminary Design Review 1 (PDR 1) |
D3 |
Preliminary Design Review 2 (PDR 2) |
ID |
Constraint(s) Description |
C1 |
Available network bandwidth |
C2 |
Reuse of existing PaaS level synchronization mechanisms |
ID |
Acceptance Criteria |
A1 |
The synchronization options are comprehensively identified and documented for all synchronization needs and compared against the parameters defined. For each synchronization a feasible option has been identified and agreed by the Purchaser |
A2 |
PDR 1 and PDR 2 successfully completed. Contractor provided minutes of the meetings are accepted by the Agency |
Additional Notes |
|
N/A |
WP ID |
Work Package Title |
WP3 |
Final design and proof of concept demonstrator |
The Contractor shall document the final design of the selected options from WP2 including procedural and technical process required for implementation. The final design documentation shall include as a minimum a) Design and implementation solution for all synchronization options b) Assumptions, constraints and requirements c) Software tools, IaaS and PaaS required d) Step by step process description (where required) The Contractor shall conduct a one (1) Critical Design Review (CDR) meeting in The Hague (NLD) at the Purchaser’s facility. The purpose of the CDR is to demonstrate that the maturity of the design is appropriate to support proceeding with full scale software and hardware implementation, integration and operation. The Contractor shall incorporate and update the design to the FSD based on the findings of the CDR. |
|
ID |
Deliverable(s) Description |
D1 |
Design documentation for CDR |
D2 |
CDR meeting |
D3 |
FSD documentation |
ID |
Constraint(s) Description |
C1 |
|
C2 |
|
ID |
Acceptance Criteria |
A1 |
CDR conducted according the SOW |
A2 |
FSD design delivered in accordance with the requirements of this contract |
Additional Notes |
|
N/A |
WP ID |
Work Package Title |
WP4 |
Feasibility demonstrator (optional) |
The Contractor shall setup a technical demonstrator to proof feasibility of selected synchronization aspects of the final design. The demonstrator shall cover the following synchronization scenarios: a) Synchronization of two (2) ArcGIS Enterprise published services from location to another including underlying data. b) ArcGIS Portal content and applications synchronization. c) Synchronization Core GIS geoinformation holdings across sites. After setup the Contractor shall demonstrate to NCIA SMEs the implementation of the scenarios based on the under WP 3 developed final design. The demonstration should be held at the Contractor’s facilities and cover 1. Proof of correct setup of the feasibility demonstrator according the final design developed under WP3 2. Execution of the synchronization scenarios as defined above |
|
ID |
Deliverable(s) Description |
D1 |
Technical feasibility demonstrator |
D2 |
|
D3 |
|
ID |
Constraint(s) Description |
C1 |
|
C2 |
|
ID |
Acceptance Criteria |
A1 |
Technical feasibility demonstrator |
A2 |
|
Additional Notes |
|
To support the feasibility demonstrator the Agency could make available on a temporary basis (up to 3 months) a) Test data b) ArcGIS Enterprise licenses |
Outsourcey
Alten
HMG Careers
Infrabyte Technology Solution Pvt. Ltd.
Postmedia Network Inc.