This opportunity is closed for applications

The deadline was Tuesday 28 June 2016
GEANT Limited

GÉANT Inventory System

0 Incomplete applications

18 Completed applications

15 SME, 3 large

Important dates

Tuesday 14 June 2016
Deadline for asking questions
Tuesday 21 June 2016 at 11:59pm GMT
Closing date for applications
Tuesday 28 June 2016 at 11:59pm GMT


Summary of the work
New inventory system (DB & GUI) to document optical and IP network resource information. A key improvement compared to the existing system will be automatic population of inventory and configuration information from the GÉANT network equipment. Users will also create and edit records using the GUI.
Latest start date
1st September 2016
Expected contract length
12 months including integration and training.
No specific location, eg they can work remotely
Organisation the work is for
GEANT Limited
Budget range
Total spend with chosen supplier is not to exceed €400,000.

About the work

Why the work is being done
GÉANT Operations requires a single centralised repository for capturing and recording GÉANT network and service information. This will replace its existing operational database that is built and maintained-in house and uses MySQL with a PHP-based GUI. The offered system must support entering, changing, presenting and searching for a variety of all resources recorded within the system. A key improvement compared to the existing system is expected to be automatic population of inventory and configuration information from the GÉANT network equipment.

Expected start date July 2016, completion date early 2017.
Problem to be solved
The existing in-house software used by GEANT Operations and associated departments is out-dated hence difficult and time-consuming to support to ensure it meets today's network and operational requirements.

Data is frequently out of date due to the need for manual data entry. This has led to network engineers not trusting the data, hence not using it consistently for their work. Automated tools also rely on this data, so e.g. event management correlation and reporting is challenging due to the frequent need to double-check and fix data in the current database.
Who the users are and what they need to do
Full set of AGILE-style user stories will be sent to short-listed suppliers.

As a network operations engineer
I need to be able to trust the network and service information in our inventory management system to be able to plan and operate the network. I need some information to be learnt automatically from the Juniper / Infinera network equipment (serial numbers, customer service configuration etc.) and I need to be able to use an intuitive GUI to enter other information (operational dates, geographical locations etc.)

I also need various in-house tools to read and write data to this system.
Early market engagement
Any work that’s already been done
GÉANT has undertaken a competitive dialogue procurement seeking to purchase an off-the-shelf product and has decided not to purchase such a system due to strict budget limitations and need for a high level of customisation.

GÉANT has prepared :
-Functional requirements (AGILE user story cards)
-Expected records and fields to be stored
-Planned high-level modular system architecture
-Expected plan for implementing TM Forum guidelines (domains, entities, class hierachies)

GÉANT has created the following in-house systems which the new inventory system must interface with:
• Network event (outage) management correlation and display
• Enterprise Service Bus
• Data Warehouse (MySQL)
Existing team
Supplier will be working with in-house GEANT teams as follows:

Systems Development team who:
*write and maintain other in-house systems such as existing inventory system, reporting and event management correlation and display
*write and maintain the ESB plugin modules to interface with other in-house tools
*will write the BSS module
*maintain replacement inventory system post-release and act as 3rd line support

Users - mostly network operations engineers who plan, configure and fix the optical and IP network and liaise with suppliers. A user focus group has been specifically created to finalise detailed requirements during Sprint meetings.
Current phase

Work setup

Address where the work will take place
It is expected that the majority of the work will take place at the premises of the winner of the contract, with occasional visits to GEANT's office in Cambridge, Cambridgeshire, UK.

Details, logistics and feasibility to be discussed.
Working arrangements
It is expected that after the initial meetings, the supplier's key individuals would work in the GEANT Cambridge office for 1-2 weeks to kick off the project and perform the first sprint planning meetings.

During the majority of the project the developers are expected to work remotely, due to space limitations in the Cambridge office and our limited expenses budget. This limit is €10,000 for the whole project.

Sprint planning and retrospective meetings may happen via VC (H.323 or Skype) or face-to-face, as agreed between project managers of both organisations.
Security clearance
None required.

Additional information

Additional terms and conditions
GEANT requires to retain full intellectual property rights of all software created as part of this project, and be able to offer a software license to other organisations in the GEANT community.

For more information about the GEANT partners and the organisation model, please see

Skills and experience

Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.

Essential skills and experience
  • Have a track record of successfully delivering projects on time, and to budget and specification.
  • Have experience in delivering user provided designs and requirements
  • Have experience in creating web-based GUIs to interact with databases including comprehensive searching facilities
  • Be able to design solutions to connect multiple system applications
  • Have experience in creating systems that are successfully maintained by in-house client teams after production release
  • Have experience in creating systems that can be configured by users
  • Have experience in creating databases that are populated using 3rd party hardware configuration
  • Have experience in co-operating with user teams throughout the development process such that the users can submit revised requirements, review prototypes and ensure the finished product reflects latest business needs.
  • Have experience in creating RESTful APIs using JSON
  • Have experience in creating applications using Object-Oriented Design (OOD) Methodologies
Nice-to-have skills and experience
  • Demonstrate experience importing network hardware inventory and configuration into a database
  • Commence work within one month of the expected start date
  • Demonstrate experience of developing web-based applications using Java or PHP frameworks
  • Demonstrate experience of developing web-based applications using MySQL
  • Demonstrate experience of creating systems that interact with network management systems
  • Demonstrate experience in creating relational databases
  • Demonstrate experience in creating MySQL databases
  • Demonstrate experience in creating databases to store information about modular network hardware
  • Have experience creating a software product using AGILE-based methodologies
  • Demonstrate experience using appropriate areas of the TM Forum Information Framework Shared Information Datamodel

How suppliers will be evaluated

How many suppliers to evaluate
Proposal criteria
  • Initial technical design for GEANT inventory system that meets stated requirements
  • Suggested project team structure
  • Proposed approach and methodology including expected customer engagement
  • Risk identification, analysis & mitigation
  • Software Quality Assurance methodology
  • Development plan and release schedule
  • Documentation and training package
  • Value for money
Cultural fit criteria
  • Work as a team with our organisation
  • Transparent and collaborative when making decisions
Payment approach
Fixed price
Assessment methods
  • Written proposal
  • Case study
  • Reference
  • Presentation
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. Are Java and PHP the only platforms permissible, or is GÉANT open to consider others based on open source technologies as well?
GÉANT is certainly open to considering other platforms. Java and PHP are listed as 'nice to have' criteria because our in-house development team, that will maintain the system post-production release, currently have greater experience in these platforms than other platforms.
2. How many people are to be trained?
GÉANT Systems team - code walk-through so they can support code, product and system in the future - 4 people

Operations team - users inc. advanced users and UAT team - 6 people who will train rest of team after final UAT phase.
3. Is the €10,000 budget for expenses in addition to the total €400,000 budget for the total spend?
The €400,000 total spend is for the entire project which includes expenses.
4. Are you a public sector organisation as we can't find your URN number?
We do have a URN number and you can contact the Crown Commercial Service to obtain it. GEANT Limited receives funding from the European Commission and National Research and Education Networks (NRENs) across Europe and beyond, such as JISC ( in the UK. GEANT Limited is obligated by the conditions of its funding and governance to conduct itself as a Contracting Authority (as defined in The Public Contracts Regulations 2015). We are structured as a not for profit organisation and are eligible to use the CCS frameworks.
More information can also be found at and funding information at
5. What is the approximate number of users of the systems anticipated to be?
The key user group is expected to be ~20 people in the GÉANT Operations team. Secondary users will be members in other departments, such as finance and customer liaison teams, however they are also likely to retrieve reports from the inventory system via our separate reporting tool.

In addition, one of our partner organisations in Greece is expected to install a separate instance of this inventory system to document their network. We will also likely offer the software license to other partner organisations in our consortium.
6. What is the number of database tables in the existing system and what is the size of the database?
The existing MySQL database holds 83 tables of which approx. 25 are now obsolete as we no longer use the system as the authoritative source for that data or we have changed the data model so they're no longer relevant. We've created 6 views to ease queries. The entire database size including data that is over 10 years old is ~48 Mb.
7. Should the supplier migrate any data from the old system to the new?
The data in the MySQL DB will be handled as follows: 1) Old data will not be transferred and will be kept as a read-only archive, accessible via the old GUI or SQL CLI. 2) Most of the useful data about the current network will be learnt via the live network equipment using new import modules. 3) Some data such as site addresses will be imported via CSV or direct SQL transfer 4) Some data such as patch panel cabling will be freshly learnt via new audits and loaded via CSV initially and with changes made via GUI after production.
8. How many user stories have you produced so far?
We have 72 short user stories prepared, some with initial acceptance criteria. The list is currently on a private JIRA site and will be shown during the Q & A and an export shared subsequently on Box. It is expected that more detail will be added to these before development, such as exact data models and GUI layouts expected. Ideally the developers would collaborate with the assigned user representatives to finalise these details to ensure suitable depth of requirements.
9. Are there any third-party modules that must be integrated into the system, and if so do they use a common interface?
We do not need to incorporate third party modules *into* the new inventory system but we do need to exchange data between them. See the diagram that will be shared during the Q & A on Tuesday 21st June and subsequently made available on Box. The interfaces are a mixture of commercial APIs and and links to an in-house Enterprise Service Bus, using a combination of SSH, SNMP, csv file imports, RESTful APIs using JSON etc.
10. Further Information
Further requirements and design information can be found at
11. [Question asked during Q & A meeting on 21st June]
Is the GÉANT ESB in production now or is it a work in progress?
Yes, the GÉANT Enterprise Service Bus (ESB) is a production service and uses activeMQ and Camel.
12. [Question asked during Q & A meeting on 21st June]
How do you foresee the 2 development teams (GÉANT and contracted supplier) working together?
The two teams would collaborate during the contract, each creating different modules that must interface with each other. The GÉANT team will also act as technical specialists for the interfaces to the existing systems. After the production release of the inventory system, the GÉANT team will be responsible for its ongoing support and maintenance. Should we wish to engage the supplier for further development support, a separate scope of work and contract will be negotiated.
13. [Question asked during Q & A meeting on 21st June]
Will the inventory system write configuration to the network equipment in addition to reading configuration?
No, the inventory system is currently expected to only learn information, not write information to the network. However it would be useful if the APIs are designed such that this is a possible system enhancement in the future.