466x Filetype XLSX File size 0.02 MB Source: platforma
Note that the Word document is the authoritative one. This spreadsheet is merely a convenient way of summarizing the bidder's technical proposal.
Please refer to the Word document for the full description of the requirements, as the summary is does not contain the full description.
Scope Requirement ID
Architecture Rq:Modularity
Architecture Rq:Openness
Architecture Rq:OpenSource
Architecture Rq:OpenFormat
Architecture Rq:Authentication
Architecture Rq:Reuse
Architecture Rq:Multi-tenancy
Architecture Rq:Scalability
Architecture Rq:Localization
Architecture Rq:Resilience
Architecture Rq:MultiDataCenter
Architecture Rq:3Tier
Architecture Rq:Privacy
Architecture Rq:Encryption
Architecture Rq:Documentation
Architecture Rq:Design
Architecture Rq:CreationOfPerson
UI Rq:Web
UI Rq:Language
UI Rq:Ergonomy
UI Rq:IFF
Hosting Rq:ISC
Hosting Rq:Env
Hosting Rq:Backup
Hosting Rq:Monitoring
Hosting Rq:Virtual
Hosting Rq:OS
Hosting Rq:DB
Hosting Rq:SLA
Hosting Rq:Installation
Sizing Rq:Users
Sizing Rq:Perf
SIzing Rq:MaxEntity
Sizing Rq:Volume
Sizing Rq:BOM
Sizing Rq:ImpactExisting
Log Rq:Log
Log Rq:LogFormat
AI Rq:ArtificialIntelligence
Maintenance Rq:Maintenance
Maintenance Rq:KnowledgeTransfer
Security Rq:Security
Security Rq:SecurityTests
Integration [Rq:Integration]
Integration [Rq:IntegrationPlan]
Note that the Word document is the authoritative one. This spreadsheet is merely a convenient way of summarizing the bidder's technical proposal.
Please refer to the Word document for the full description of the requirements, as the summary is does not contain the full description.
Requirement summary
The proposed solution must be modular. Each module must be re-usable in the context of the Analytical platform, but from
an external system as well. It must offer its own API. Each module and its API must be documented and supported.
The proposed solution must be easy to extend. It must be easy to add new components offering new features as new
needs appear.
The proposed solution should be based on open-source components
The proposed solution must be open and limit the usage of non-standard technologies. In particular, it must store the
information in an open standard format and must be able to interface with components in standard protocols and open
formats.
The solution must be integrated with our centralized authentication and authorization management to manage the user
and his access rights.
The proposed solution should reuse as much as possible the components already available in the INTERPOL Information
System, when these components are suitable for the use of the Analytical Platform.
The proposed solution must be able to manage multiple tenants, each tenant being used for a specific criminal
domain/Criminal Analysis File.
The proposed solution must be designed to be scalable.
The proposed solution should be able to localize its tenants in any of the INTERPOL datacenters, so the tenants be the
closest to the analysts who access them
The proposed solution must be resilient. The proposed design must not present single point of failure. It must be able to
meet the availability target specified in SLA defined in Annex 6.2.
The solution must be designed to be deployed on multiple data centers in active-passive mode.
The proposed solution should adhere as much as possible to a standard 3-tier architecture.
The solution must be designed with privacy in mind. The solution must guarantee the isolation of the tenants (no leak of
data from one tenant to the other)
The solution must be able to encrypt all the communication and all the data at rest.
The solution must be fully documented.
The solution must implement a state-of-art design.
The solution must manage the creation of persons entities through the existing compliance check mechanisms.
When possible, web interfaces are preferred. The web interfaces must not require to install additional software or
browser’s plugin on user computer (Java, Flash, ...).
If the solution supports thick and web clients, the functionalities available in each mode must be clearly identified.
The user interfaces must be localizable. It must support the four official languages of the Organization (English, French,
Spanish and Arabic).
The user interfaces should be innovative and ergonomic, focused on the user (user driven)
The custom-made web interfaces must use the “INTERPOL Front Framework”.
INTERPOL Secure Cloud must be used to host the solution.
The solution must be deployed in 3 separated environments:
- Production environment
- Qualification (Pre-Production) environment
- Training environment
The solution must comply with our backup policy and backup tool.
The solution must be integrated with our agentless monitoring platform (privileging SNMP & Web Requests).
The solution must be hosted on Virtual Servers (vSphere & Intel CPU). INTERPOL can accept container based solutions
The solution should be compliant with our standard OS and VM policy.
The solution should use INTERPOL standard RDBMS: Oracle, PostGreSQL, MySQL, MSSQL.
The tenderer must agree to comply with INTERPOL’s "Service Level Agreement" described in Annex 6.2. If not, deviation
should be justified.
The solution must be installable by INTERPOL’s team. The tenderer must describe in his proposal how his solution will be
deployed.
The solution must support a number of concurrent connections at least equal to the number of users defined in chapter
2.2 of the INTERPOL IAPP Narrative document.
The solution must be designed to offer the best response times. In particular, the Entreprise Search feature must yield
results in less than 0.5s.
Long running features (such as import batches) must be run in background and must not block the user’s work.
The tenderer must clearly specify the maximum number of entities that can be managed, in particular in the visualization
tools.
The solution must initially be sized to manage 10 tenants, with a total volume of about 1TB.
The tenderer must include in his response an estimative build of material to host the solution supporting the initial
number of users, number of tenants and volume.
The tenderer must include in his proposal a description of the impacts of his proposed solution on the existing Information
System.
The solution must produce the logs specified in CCT.
The solution must produce the logs according to the format specified in Annex 6.1.
Artificial Intelligence (AI) and Deep Learning should be used as much as possible to simplify the User Experience and
improve both Quality of Data and Productivity of Users.
The tendered must provide a quotation for the support of the solution for 5 years.
The tenderer must include in his response a knowledge transfer plan.
The solution must meet INTERPOL's security constraints
The solution must pass security tests.
The solution must be fully integrated into the existing Information System
The tenderer must include in his proposal a high-level integration plan explaining how he intends to integrate the different
components together and into the existing Information System
no reviews yet
Please Login to review.