Portugal-Lisbon: IT consultancy services for EMSA`s horizontal IT

Transcription

OJ/S S97
21/05/2015
174761-2015-EN
Agency - Service contract - Contract notice - Open procedure
1/11
This notice in TED website: http://ted.europa.eu/udl?uri=TED:NOTICE:174761-2015:TEXT:EN:HTML
Portugal-Lisbon: IT consultancy services for EMSA's horizontal IT components: portal, identity management,
integration and non-functional capabilities, data warehouse and geographic information systems
2015/S 097-174761
Contract notice
Services
Directive 2004/18/EC
Section I: Contracting authority
I.1)
Name, addresses and contact point(s)
European Maritime Safety Agency
Praça Europa 4
For the attention of: Raul Arsenio da Silva
1249-206 Lisbon
PORTUGAL
E-mail: [email protected]
Internet address(es):
General address of the contracting authority: http://www.emsa.europa.eu/
Further information can be obtained from: The above mentioned contact point(s)
Specifications and additional documents (including documents for competitive dialogue and a dynamic
purchasing system) can be obtained from: The above mentioned contact point(s)
Tenders or requests to participate must be sent to: The above mentioned contact point(s)
I.2)
Type of the contracting authority
European institution/agency or international organisation
I.3)
Main activity
General public services
I.4)
Contract award on behalf of other contracting authorities
The contracting authority is purchasing on behalf of other contracting authorities: no
Section II: Object of the contract
II.1)
Description
II.1.1)
Title attributed to the contract by the contracting authority:
IT consultancy services for EMSA's horizontal IT components: portal, identity management, integration and nonfunctional capabilities, data warehouse and geographic information systems.
II.1.2)
Type of contract and location of works, place of delivery or of performance
Services
Service category No 7: Computer and related services
NUTS code PT171
II.1.3)
Information about a public contract, a framework agreement or a dynamic purchasing system (DPS)
The notice involves the establishment of a framework agreement
II.1.4)
Information on framework agreement
Framework agreement with several operators
21/05/2015
S97
http://ted.europa.eu/TED
Supplement to the Official Journal of the European Union
1/11
OJ/S S97
21/05/2015
174761-2015-EN
2/11
Number of participants to the framework agreement envisaged: 3
Duration of the framework agreement
Duration in years: 4
Estimated total value of purchases for the entire duration of the framework agreement
Estimated value excluding VAT: 3 900 000 EUR
II.1.5)
Short description of the contract or purchase(s)
The purpose of this procurement is to establish an acquisition channel for the IT technical domains presented in
each of the following lots:
— lot 1: portal technology,
— lot 2: identity management and single sign-on,
— lot 3: integration and non-functional capabilities,
— lot 4: data warehouse, ETL and related technologies,
— lot 5: geographic information systems.
This will enable EMSA to acquire high-quality services to support the ICT sector of EMSA in:
— supporting the development, enhancement, maintenance and operations of EMSA horizontal software
components and modules in line with EMSA technical architecture that will be integrated and/or worked together
with existent or new maritime applications,
— performing studies, assessments, recommendations and other types of investigations in the different fields
and components defined in the EMSA system landscape present in the general conditions of the ICT framework
contract.
This procurement will result in the following:
— for lot 2 and lot 5 it will result in the award of a framework IT contract with 1 contractor per lot,
— for lot 1, lot 3 and lot 4 it will result in the award of a multiple framework IT contract with reopening of
competition with 3 successful contractors per lot.
II.1.6)
Common procurement vocabulary (CPV)
72600000, 72200000, 72227000
II.1.7)
Information about Government Procurement Agreement (GPA)
The contract is covered by the Government Procurement Agreement (GPA): no
II.1.8)
Lots
This contract is divided into lots: yes
Tenders may be submitted for all lots
II.1.9)
Information about variants
Variants will be accepted: no
II.2)
Quantity or scope of the contract
II.2.1)
Total quantity or scope:
II.2.2)
Information about options
Options: no
II.2.3)
Information about renewals
This contract is subject to renewal: no
II.3)
Duration of the contract or time limit for completion
Duration in months: 48 (from the award of the contract)
Information about lots
21/05/2015
S97
2/11
OJ/S S97
21/05/2015
174761-2015-EN
3/11
Lot No: 1
Lot title: Portal technology
1)
Short description
The portal concept is to present the user with a single Web page that brings together or aggregates content
from a number of other systems or servers. For portals that present application functionality to the user,
the portal server is in reality the front piece (presentation tier) of a server configuration that includes some
connectivity to the application server. The underneath application server is part of the service-oriented
architecture (SOA) tiers which perform the actual functions of the application.
The server hosting the portal may only be a 'pass through' for the user. By use of portlets, application
functionality can be presented in any number of portal pages. For the most part, this architecture is transparent
to the user.
The main features of a common portal are:
— single sign-on (SSO): portals can provide single sign-on capabilities between their users and various other
systems. This requires a user to authenticate only once,
— integration: the connection of functions and data from multiple systems into new components/portlets/Web
parts with an integrated navigation between these components,
— federation: the integration of content provided by other portals, typically through the use of WSRP (Web
services for remote portlets) or similar technologies,
— customisation: the look and feel of the user environment is customisable. Also refers to the ability to prioritise
the most appropriate content based on attributes of the user and metadata of the available content,
— personalisation: personalisation is more about matching content with the user. Based on a user profile,
personalisation rules are used to match the 'services', or content, to the specific user,
— access control: the ability for the portal to limit specific types of content and services or just the users that are
supposed to have access to it. For example, it can be used to distinguish between an application user profile
from an administrator one. Please note that EMSA access control is fully integrated with IDM.
— enterprise search: search enterprise content.
Contractors can be invited to provide services in the portal technical domain, like (but not limited to) the
following ones:
— design, implementation, test and deployment of new portlets,
— default portal configuration for the addition of new organisational entities (e.g. communities, organisations,
roles, user groups, permissions) and their relationships,
— configuration of default portlets (e.g. Web content, Wiki, announcements, messages, content management)
to support new requirements,
— extension of the default portal implementation or default portlets implementation to answer new business
requirements,
— specific developments and configurations related to the integration of new or existent systems or
infrastructures,
— specific configurations related to EMSA's technical environments,
— the look and feel of improvements and the creation of new themes, including graphic design, Web design and
user experience (UX) of the portal framework,
— version upgrades.
2)
72600000, 72200000, 72227000
3)
Quantity or scope
Estimated value excluding VAT: 720 000 EUR
21/05/2015
S97
3/11
OJ/S S97
21/05/2015
174761-2015-EN
4)
Indication about different date for duration of contract or starting/completion
5)
Additional information about lots
Multiple framework IT contract with reopening of competition with 3 successful contractors.
4/11
Lot No: 2
Lot title: Identity management and single sign-on
1)
Short description
User access requires each user to assume a unique digital identity across applications and networked
infrastructures, which enables access controls to be assigned and evaluate against this identity.
Single sign-on (SSO) is a mechanism whereby a single action of user authentication and authorisation can
permit a user to access all computers and systems where he has access permission without the need to enter
multiple passwords. A service providing coordination and integration at (single) sign-on level conveys benefits to
an enterprise through:
— reduction of human errors, a major component of systems failure, therefore highly desirable but difficult to
implement,
— reduction in the time taken by users in sign-on operations to individual domains, including reducing the
possibility of such sign-on operations failing,
— improved security due to the reduced need for a user to handle and remember multiple sets of authentication
information,
— reduction in the time taken, and improved response, by system administrators in adding and removing users
to the system or modifying their access rights,
— improved security through the enhanced ability of system administrators to maintain the integrity of user
account configuration including the ability to inhibit or remove an individual user's access to all system
resources in a coordinated and consistent manner.
Related to identity management and single sign-on technical domains, tenderers might be invited to provide
services like, but not limited to, the following ones:
— analysis of new requirements and design of technical integration strategy for new components, systems and/
or applications,
— integration of both existent and new components, systems and/or applications with the identity management
platform part of EMSA's system landscape present in the general conditions of the ICT framework contract,
— analysis, design, configuration, implementation, test and deployment of new user provisioning processes into
specific systems,
— design and implement improvements and/or changes in the existent provisioning processes to answer new
business requirements,
— improvement and upgrades of EMSA IDM platform.
2)
72600000, 72200000, 72227000
3)
Quantity or scope
4)
5)
Framework IT contract with 1 contractor.
Lot No: 3
21/05/2015
S97
4/11
OJ/S S97
21/05/2015
174761-2015-EN
5/11
Lot title: Integration and non-functional capabilities
1)
Short description
An enterprise service bus (ESB) consists of a software architecture construct which provides fundamental
services for complex architectures via an event-driven and standards-based messaging engine (the bus). ESBs
are typically implemented using middleware technologies based on recognised standards.
An ESB generally provides an abstraction layer on top of an enterprise messaging system implementation lying
between the business applications and enabling communication among them. Ideally, the ESB should be able to
replace all direct contact with the applications on the bus, so that all communication takes place via the ESB.
In order to achieve this objective, the ESB must encapsulate the functionality offered by its component
applications in a meaningful way. This typically occurs through the use of an enterprise message model. The
message model defines a standard set of messages that the ESB will both transmit and receive. When the
ESB receives a message, it routes the message to the appropriate application. Often, because that application
evolved without the same message model, the ESB will have to transform the message into a format that the
application can interpret. An adapter fulfils the task of effecting that transformation.
With regards to ESB, the tenderers might be invited to provide services like, but not limited to, the following
ones:
— design, implementation, test, configuration and deployment of business services, proxy services, business
rules and processes orchestration,
— design, implementation, test, configuration and deployment of composite applications,
— design, implementation, test, configuration and deployment of integration and messaging components
including services for messaging transformation, routing and enrichment,
— ESB administration, monitoring and optimisation.
A business process is a series or a network of added value activities, performed by their relevant roles or
collaborators, to purposefully achieve the common business goal. Business process management (BPM)
activities can be grouped into 5 categories:
— design: encompasses both the identification of existing processes and the design of 'to-be' processes. Areas
of focus include representation of the process flow, the actors involved in it, alerts and notifications, escalations,
standard operating procedures, service-level agreements, and task handover mechanisms,
— modelling: takes the theoretical design and introduces combinations of variables, which determine how the
process might operate under different circumstances,
— execution: one of the ways to automate processes is to develop or purchase an application that executes
the required steps of the process. However, in practice, these applications rarely execute all the steps of
the process accurately or completely. Another approach is to use a combination of software and human
intervention, this more complex approach making the documentation process more difficult,
— monitoring: encompasses the tracking of individual processes so that information on their state can be easily
seen and statistics on the performance of 1 or more processes can be provided. An example of tracking is being
able to determine the state of a user request (e.g. request received, awaiting processing, already dispatched) so
that problems in its operation can be identified and corrected,
— optimisation: process optimisation includes retrieving process performance information from the modelling or
monitoring phase; identifying the potential or actual bottlenecks and the potential opportunities for cost savings
or other improvements and then applying those enhancements in the (re)design of the process.
Tenderers can be invited to provide services in the BPM technical domain, like (but not limited to) the following
ones:
— defining an architecture for the SOA Suite components, including defining deployment diagrams and
operational procedures,
21/05/2015
S97
5/11
OJ/S S97
21/05/2015
174761-2015-EN
6/11
— functional analysis of new and/or existent business processes,
— design and modelling of new business processes in accordance to the BPM implementation framework,
— implementation of new business processes and/or BPM composite applications,
— monitoring, adaptation and optimisation of deployed business processes and/or BPM composite
applications.
Non-functional analysis of a system encompasses, at least, the following set of activities:
— capacity analysis and planning: generally, capacity estimations are required when a new application is
developed; current applications are consolidated; and/or applications are downsized from a powerful server
with a large number of CPUs and many gigabytes of memory supporting a large number of users. Capacity
planning shall encompass, at least, the following areas of analysis: CPU consumption; memory usage; network
throughput and bandwidth; storage capacity; application workload,
— performance review: reveal obvious performance issues in systems or applications by walking through
common user scenarios and analysing what is happening on the front and back ends,
— network analysis: diagnose network performance delays from large data transfers and high number of
network round-trips. Provide end user response time projections for any network line speed and latency,
— load, scalability and performance assessments: identify and isolate performance bottlenecks in an application
under a simulated workload. Report metrics such as the number of concurrent users, transaction throughputs
and end user response times. Determine the impact on application performance as a result of hardware scaleup or scale-out, 64-bit operating system migrations, database server upgrades or other changes. Monitor realtime performance in the target environment and measure transaction response times which are outside of
service level agreements.
The outcome of the aforementioned non-functional analysis-related activities shall be:
— prioritising the issues that were found,
— improving application/system performance through tuning and optimisation of services,
— providing suggestions based on best practices and optimisation strategies.
In what concerns the non-functional analysis technical domain, tenderers may be invited to provide EMSA with,
as a minimum, services in the fields of:
— execute non-functional assessments over existent system/applications to identify existent bottlenecks,
possible future problems,
— provide recommendations to solve or reduce the impacts of identified problems,
— execute capacity assessments over existent systems/applications to identify possible optimisations or to
anticipate and correct possible future lack of resources that could lead to systems/applications unavailability or
crashes,
— provide recommendations and best practices to be followed.
2)
72600000, 72200000, 72227000
3)
Quantity or scope
4)
5)
Lot No: 4
Lot title: Data warehouse, ETL and related technologies
21/05/2015
S97
6/11
OJ/S S97
21/05/2015
174761-2015-EN
7/11
1)
Short description
Data warehousing is combining data from multiple and usually varied sources into 1 comprehensive and
easily manipulated database. Common accessing systems of data warehousing include queries, analysis and
reporting. Because data warehousing creates 1 database in the end, the number of sources can greatly vary,
provided that the system can handle the volume of data involved. The final result, however, is homogeneous
data which can be more easily manipulated.
Data warehousing can be characterised as a subject-oriented, integrated, time-variant and non-volatile
collection of data in support of a decision-making process.
— Subject-oriented: data that gives information about a particular subject instead of about a company's ongoing
operations.
— Integrated: data that is gathered into the data warehouse from a variety of sources and merged into a
coherent whole.
— Time-variant: all data in the data warehouse is identified with a particular time period.
— Non-volatile: data is stable in a data warehouse. More data is added but data is never removed. This enables
management to gain a consistent picture of the business.
ETL (extract transformation and loading) technology is used to extract data from source databases, transform
and clean the data and load it into a target database. The typical life cycle of an ETL process consists of the
following execution steps:
— cycle initiation,
— build reference data,
— extract (from data sources like databases, files, applications, Web services, e-mails, etc.),
— validate,
— transform (clean, apply business rules, check for data integrity, create aggregates or disaggregates),
— stage (load into staging tables, if used),
— audit reports (for example, on compliance with business rules. Also, in case of failure, helps to diagnose/
repair),
— publish (to target tables),
— archive,
— clean up.
In the scope of DW, ETL and related technologies, tenderers might be invited to provide services like, but not
limited to, the following ones:
— analysis, design, implementation, test and deployment of new data extraction, transformation and loading
processes using different data sources,
— analysis, adaptation, testing and deployment of existent DW and ETL processes,
— design, implementation, test and deployment of new reporting processes,
— analysis, adaptation, testing and deployment of existent reporting processes,
— integration of business processes with ETL processes.
2)
72600000, 72200000, 72227000
3)
Quantity or scope
4)
5)
21/05/2015
S97
7/11
OJ/S S97
21/05/2015
174761-2015-EN
8/11
Lot No: 5
Lot title: Geographic information systems
1)
Short description
A geographic (or geographical) information system (GIS) is any system that captures, stores, analyses,
manages, and presents data that is linked to location being a merge of cartography and database technology.
GIS systems are used in cartography, remote sensing, land surveying, photogrammetry, geography, urban
planning, emergency management, navigation and localised search engines.
Therefore, the term describes any information system that integrates, stores, edits, analyses, shares and
displays geographic information. In a more generic sense, GIS applications are tools that allow users to create
interactive queries (user-created searches), analyse spatial information, edit data, maps, and present the results
of all these operations.
Specifically for EMSA, the usage of GIS applications encompasses the following main functionalities:
— manage (capture, store, process, present) the position of the vessels,
— manage (capture, store, process, present) earth observation data (satellite, 'in situ', and airborne),
— perform geospatial analysis and statistics,
— creation and edition of maps (vector and raster data).
GIS systems in EMSA support several maritime applications, some examples are:
— electronic nautical charts,
— vessels monitoring,
— oil spill detection and monitoring.
In what concerns the geographic information systems technical domain, tenderers might be invited to provide
services within, but not limited to, the following EMSA project:
— electronic nautical charts:
EMSA currently uses an electronic nautical charts distribution system for usage on EMSA maritime applications.
This system provides ENCs, using a standard WMS interface, that are used as the base layer on the EMSA
maritime applications;
EMSA is considering a possible rebuild of this system, either by enhancing the current one or by building a new
system that would provide further performance, availability and ease of management;
GIS competences.
In what concerns the geographic information systems technical domain, tenderers might be invited to provide
services like, but not limited to, the following technical competences:
— creation and editing of maps,
— managing map layers and associated labelling,
— integration of geospatial data,
— creation of reports based on geospatial data,
— execute and automatise spatial analysis,
— development of geospatial applications,
— installation, configurations and troubleshooting of geospatial applications using the EMSA-referenced GIS
tools,
— knowledge of referenced geospatial standards like OGC and Inspire,
— capabilities to analyse EMSA's geospatial applications in terms of quality of service (performance, availability
and capacity) and associated data,
— database expertise with spatial data schemas including optimisation of queries/schemas using Oracle
Spatial,
— expertise in the electronic nautical charts domain and related distribution systems.
21/05/2015
S97
8/11
OJ/S S97
21/05/2015
174761-2015-EN
2)
72600000, 72200000, 72227000
3)
Quantity or scope
4)
5)
Framework IT contract with 1 contractor.
9/11
Section III: Legal, economic, financial and technical information
III.1)
Conditions relating to the contract
III.1.1)
Deposits and guarantees required:
Not applicable.
III.1.2)
Main financing conditions and payment arrangements and/or reference to the relevant provisions
governing them:
III.1.3)
Legal form to be taken by the group of economic operators to whom the contract is to be awarded:
Please refer to the tender specifications available on the EMSA website.
III.1.4)
Other particular conditions
The performance of the contract is subject to particular conditions: no
III.2)
Conditions for participation
III.2.1)
Personal situation of economic operators, including requirements relating to enrolment on professional
or trade registers
Information and formalities necessary for evaluating if the requirements are met: Please refer to the tender
specifications available on the EMSA website.
III.2.2)
Economic and financial ability
Information and formalities necessary for evaluating if the requirements are met: Please refer to the tender
specifications available on the EMSA website.
III.2.3)
Technical capacity
Information and formalities necessary for evaluating if the requirements are met:
Please refer to the tender specifications available on the EMSA website.
III.2.4)
Information about reserved contracts
III.3)
Conditions specific to services contracts
III.3.1)
Information about a particular profession
Execution of the service is reserved to a particular profession: no
III.3.2)
Staff responsible for the execution of the service
Legal persons should indicate the names and professional qualifications of the staff responsible for the
execution of the service: yes
Section IV: Procedure
IV.1)
Type of procedure
IV.1.1)
Type of procedure
Open
IV.1.2)
Limitations on the number of operators who will be invited to tender or to participate
21/05/2015
S97
9/11
OJ/S S97
21/05/2015
174761-2015-EN
10/11
IV.1.3)
Reduction of the number of operators during the negotiation or dialogue
IV.2)
Award criteria
IV.2.1)
Award criteria
The most economically advantageous tender in terms of the criteria stated in the specifications, in the invitation
to tender or to negotiate or in the descriptive document
IV.2.2)
Information about electronic auction
An electronic auction will be used: no
IV.3)
Administrative information
IV.3.1)
File reference number attributed by the contracting authority:
EMSA/OP/09/2015.
IV.3.2)
Previous publication(s) concerning the same contract
no
IV.3.3)
Conditions for obtaining specifications and additional documents or descriptive document
Payable documents: no
IV.3.4)
Time limit for receipt of tenders or requests to participate
3.7.2015 - 16:00
IV.3.5)
Date of dispatch of invitations to tender or to participate to selected candidates
IV.3.6)
Language(s) in which tenders or requests to participate may be drawn up
Any EU official language
IV.3.7)
Minimum time frame during which the tenderer must maintain the tender
until: 31.12.2015
IV.3.8)
Conditions for opening of tenders
Date: 13.7.2015 - 14:00
Place:
EMSA premises.
Persons authorised to be present at the opening of tenders: yes
Additional information about authorised persons and opening procedure: The opening session will be public.
A representative of each tenderer may attend the opening of the bids. At the end of the opening session, the
chairman of the opening committee will indicate the names of the tenderers and the decision concerning the
admissibility of each offer received. The prices indicated in each received bid will not be communicated. Should
you wish to attend, please send a request (at least 5 calendar days before the date of the opening) to the
following e-mail address: [email protected] indicating the name of the attending person and the
tenderer he/she represents.
Section VI: Complementary information
VI.1)
Information about recurrence
This is a recurrent procurement: no
VI.2)
Information about European Union funds
The contract is related to a project and/or programme financed by European Union funds: no
VI.3)
Additional information
Contact between the contracting authority and tenderers is prohibited throughout the procedure save in
exceptional circumstances and only under the following conditions:
— Before the final date for submission of tenders:
21/05/2015
S97
10/11
OJ/S S97
21/05/2015
174761-2015-EN
11/11
* At the request of the tenderer, EMSA may provide additional information solely for the purpose of clarifying the
nature of the contract.
Any requests for additional information must be made in writing and sent to the following e-mail address
[email protected]
EMSA is not bound to reply to requests for additional information made less than 5 working days before the
deadline for submission of tenders.
* EMSA may, on its own initiative, inform interested parties of any error, inaccuracy, omission or any other
clerical error in the text of the call for tenders.
* Any additional information including that referred to above will be published on the EMSA website in the
'Procurement' section. The website will be updated regularly and it is the tenderers' responsibility to check for
updates and modifications during the tendering period.
— After the opening of tenders:
* If clarification is required or if obvious clerical errors in the tender need to be corrected, EMSA may contact the
tenderer provided the terms of the tender are not modified as a result.
EMSA may, at a later stage, exercise the option to increase the estimated value of the contract via negotiated
procedure with the successful tenderer in accordance with Article 134(1)(f) of the rules of application to the
Financial Regulation.
VI.4)
Procedures for appeal
VI.4.1)
Body responsible for appeal procedures
General Court of the European Union
rue du Fort Niedergrünewald
2925 Luxembourg
LUXEMBOURG
E-mail: [email protected]
Internet address: http://www.curia.europa.eu
Fax: +352 4303-2100
VI.4.2)
Lodging of appeals
Precise information on deadline(s) for lodging appeals: Within 2 months of the notification to the plaintiff, or,
in absence thereof, of the day on which it came to the knowledge of the plaintiff. A complaint to the European
Ombudsman does not have as an effect either to suspend this period or to open a new period for lodging
appeals.
VI.4.3)
Service from which information about the lodging of appeals may be obtained
VI.5)
Date of dispatch of this notice:
11.5.2015
21/05/2015
S97
11/11

Portugal-Lisbon: IT consultancy services for EMSA`s horizontal IT

Transcription

Similar documents

Field sponsors - EMSA Soccer Complex

An Oshtemo Community Event for all!

Ted Tromps` certificate

Full Tractor Ted Set

Sana and Ted

R E M A R K S

Ted Turner`s pinstripe art

CVU ANNOUNCEMENTS Thursday, October 30, 2014 White Day

Ted Britt Ford improves sales and lowers cost with KeyAdvantage!