BIDS AND AWARDS COMMITTEE FOR THE INTEGRATED GOVERNMENT

PHILIPPINES PROJECT (BAC4IGOV)

Supplemental Bid Bulletin No. 1

 

Supply, Delivery, Installation and Configuration of Software Components and Perpetual Licenses to Implement the Government Operations Management Interoperability Platform and Profiling System

 

Bid Reference No:  BAC4IGOV-2016-05-006

 

After considering the clarifications, recommendations and suggestions of the end-user, the BAC4IGOV hereby decides to include, revise, amend, delete and/or adapt the following provisions:

 

ORIGINAL PROVISION AMENDED PROVISION
INVITATION TO BID
Item No. 4:  Delivery Place and Delivery Period
Delivery Period
For Technical Deliverables – Within sixty (60) calendar days from receipt of Notice to Proceed

For the Support – Twelve (12) months from receipt of Notice to Proceed

Delivery Period
For Technical Deliverables – Within three (3) months from receipt of Notice to Proceed and Twelve (12) months for the on-boarding support
Item No. 5
For this project, “similar in nature” shall mean Software Development For this project, “similar in nature” shall mean Software Product and Services
SECTION VI.  SCHEDULE OF REQUIREMENTS
The delivery schedule shall be completed within sixteen (16) months from receipt of Notice to Proceed.

 

Description Qty Delivered, Weeks/Months
Supply, Delivery, Installation and Configuration of Software Components and Perpetual Licenses to Implement the Government Operations Management Interoperability Platform and Profiling System 1 lot For Technical Deliverables – Within sixty (60) calendar days from receipt of Notice to Proceed

For the Support – Twelve (12) months from receipt of Notice to Proceed

The delivery schedule shall be completed within fifteen (15) months from receipt of Notice to Proceed.

 

Description Qty Delivered, Weeks/Months
Supply, Delivery, Installation and Configuration of Software Components and Perpetual Licenses to Implement the Government Operations Management Interoperability Platform and Profiling System 1 lot For Technical Deliverables – Within three (3) months from receipt of Notice to Proceed and Twelve (12) months for the on-boarding support
Please refer to Revised Schedule of Requirements as of 20 May 2016.
SECTION VII.  TECHNICAL SPECIFICATIONS
1.4.     Compatibility Requirement
1.4.1  Open source Enterprise Microservices Java-based Development and Runtime Platform 1.4.1    Enterprise Microservices Java-based Development and Runtime Platform
1.4.2  Open source Enterprise Java-based Business Process Management Tool 1.4.2    Embedded BPMN 2.0 compliant Business Process Management Tool
1.4.3  Open source Enterprise RDBMS 1.4.3    Enterprise RDBMS
1.4.4  Open source No SQL Database (Storage Only) 1.4.4    NoSQL XML Document Database (Storage Only)
1.4.7  Mobility Platform: Android OS (API 19 and later versions) 1.4.7    Development and Runtime Engine: Java
1.4.8  Open source Embedded Data Visualization and BI Engine 1.4.8    Application Deployment Model: Microservices
1.4.9  Development and Runtime Engine: Java 1.4.9    External Integration: Web Services (SOAP/REST)
1.4.10   Application Deployment Model: Microservices 1.4.10  Enterprise IP Geolocation Service
1.4.11   External Integration: Web Services (SOAP/REST) Deleted
1.4.12   Enterprise IP Geolocation Service Deleted
5.1.3.1 User Profile Management
5.1.3.1.1 Provides authenticated user administrators the ability to add user accounts and trigger alternative user-verification identity protocols, update or delete user accounts and permissions; create, update, add members to, set permissions to or delete groups; Deleted
5.1.3.1.2 Provides authenticated users the ability to update individual profiles, personal photo, contact information and address. The system must be able to send a confirmation email to a registered email address and log the IP and geo-location where the profile was created; Deleted
5.1.3.1.3 Provides authenticated users the ability to manage contact address books, create a company profile (if the authenticated user is a company), URL, and email addresses; Deleted
5.4.1.  Runtime and Customization Development Technical Specifications
5.4.1.1 The system must be built on the following technology stack. It is recommended that the solutions provider will subscribe to existing components of the stack of ICT Office. The solutions provider should provide mechanisms for integration should there be a need to deviate from these components. The system must be built on the following technology stack. It is recommended that the solutions provider will subscribe to existing components of the stack of ICT Office. The solutions provider should provide mechanisms for integration should there be a need to deviate from these components.
5.4.1.1.7   Mobility Platform: Android OS (API 19 and later versions) 5.4.1.7  Development and Runtime Engine: Java
5.4.1.1.8   Enterprise Embedded Data Visualization and BI Engine 5.4.1.8  Application Deployment Model: Microservices
5.4.1.1.9   Development and Runtime Engine: Java 5.4.1.9  External Integration: Web Services (SOAP/REST)
5.4.1.1.10 Application Deployment Model: Microservices 5.4.1.10Enterprise IP Geolocation Service
5.4.1.1.11 External Integration: Web Services (SOAP/REST) Deleted
5.4.1.1.12 IP Geolocation Service Deleted
5.3.1.   On-Site Technical Staffing Support for Functional Onboarding Deployment of On-Site BPM Technical Staff to Support Agency Onboarding Activities (8×6):
5.3.1.2  Deployment of On-Site Technical/Developers to Support technology requirements and integration with iGov Services (8×6): 5.3.2.   Deployment of On-Site Technical/Developers to Support technology requirements and integration with iGov Services (8×6):
5.3.1.3  Two (2) Multi-disciplinary Developer Resources for select Agency 5.3.2.1 Two (2) Multi-disciplinary Developer Resources for select Agency
5.3.1.4  Integration with iGov Services 5.3.3.   Integration with iGov Services
5.3.1.5  The system must be able to integrate with or use iGov services such as, but not limited to, PNPKI, SSO, PhPay and ProgResibo. 5.3.3.1.          The system must be able to integrate with or use iGov services such as, but not limited to, PNPKI, SSO, PhPay and ProgResibo.
5.4.1.   Runtime and Customization Development Technical Specifications
5.4.1.1 The system must be built on the following technology stack. It is recommended that the solutions provider will subscribe to existing components of the stack of ICT Office. The solutions provider should provide mechanisms for integration should there be a need to deviate from these components. The system must be built on the following technology stack. It is recommended that the solutions provider will subscribe to existing components of the stack of ICT Office. The solutions provider should provide mechanisms for integration should there be a need to deviate from these components.
5.4.1.1.1Enterprise Microservices Development and Runtime Platform 5.4.1.1.          Enterprise Microservices Development and Runtime Platform
5.4.1.1.2          Embedded BPMN 2.0-compliant Business Process Management Tool 5.4.1.2.          Embedded BPMN 2.0-compliant Business Process Management Tool
5.4.1.1.3          Enterprise RDBMS 5.4.1.3.          Enterprise RDBMS
5.4.1.1.4          NoSQL XML Document Database (Storage Only) 5.4.1.4.          NoSQL XML Document Database (Storage Only)
5.4.1.1.5          Open source Enterprise Server Operating System 5.4.1.5.          Open source Enterprise Server Operating System
5.4.1.1.6          Cloud Infrastructure: IaaS (e.g. Amazon Web Services, Azure) 5.4.1.6.          Cloud Infrastructure: IaaS (e.g. Amazon Web Services, Azure)
5.4.1.1.7          Mobility Platform: Android OS (API 19 and later versions) 5.4.1.7.          Mobility Platform: Android OS (API 19 and later versions)
5.4.1.1.8          Enterprise Embedded Data Visualization and BI Engine 5.4.1.8.          Enterprise Embedded Data Visualization and BI Engine
5.4.1.1.9          Development and Runtime Engine: Java 5.4.1.9.          Development and Runtime Engine: Java
5.4.1.1.10        Application Deployment Model: Microservices 5.4.1.10.        Application Deployment Model: Microservices
5.4.1.11.          External Integration: Web Services (SOAP/REST) 5.4.1.11.        External Integration: Web Services (SOAP/REST)
5.4.1.1.12        IP Geolocation Service 5.4.1.12.        IP Geolocation Service
5.4.1.2  Core Services 5.4.2.      Core Services
5.4.1.2.1          The system will be a cloud-based IaaS platform that integrates a microservice-based application system with the an enterprise process flow management and administration portal functionality, a market-facing portal functionality, enterprise management portal functionality, profiling portal, user authentication and authorization, semantic search, value calculator, reporting and analytics. 5.4.2.1.   The system will be a cloud-based IaaS platform that integrates a microservice-based application system with the an enterprise process flow management and administration portal functionality, a market-facing portal functionality, enterprise management portal functionality, profiling portal, user authentication and authorization, semantic search, value calculator, reporting and analytics.
5.4.1.2.2          Core services will be implemented as microservices. Microservice intercommunication will be routed either through an enterprise service bus or via an API-management gateway with the option to limit microservice intercommunication to preset IP addresses. 5.4.2.2.   Core services will be implemented as microservices. Microservice intercommunication will be routed either through an enterprise service bus or via an API-management gateway with the option to limit microservice intercommunication to preset IP addresses.
5.4.1.2.3          Interface or integration with external systems must be through a web service using standard SOAP/REST protocols. 5.4.2.3.   Interface or integration with external systems must be through a web service using standard SOAP/REST protocols.
5.4.1.2.4          Microservices and web services must support, at the minimum, XML 1.0, SOAP 1.1, HTTP 1.1 with SSL3.0/TLS 1.0+ with the capability to easily adapt to the latest standard recommendations upon release, and must be compliant with the latest WS standards; 5.4.2.4.   Microservices and web services must support, at the minimum, XML 1.0, SOAP 1.1, HTTP 1.1 with SSL3.0/TLS 1.0+ with the capability to easily adapt to the latest standard recommendations upon release, and must be compliant with the latest WS standards;
5.4.1.2.5    The system must support single-sign on (OAuth 2.0 and SAML) and security certification protocols using the latest standards (i.e. X.509, SSL/TLS, OCSP/CRL, and PKCS12). 5.4.2.5.    The system must support single-sign on (OAuth 2.0 and SAML) and security certification protocols using the latest standards (i.e. X.509, SSL/TLS, OCSP/CRL, and PKCS12).
5.4.1.2.6    Form data elements must utilize the latest XForms/XSLT standards. Form data elements must be made available to and/or retrievable from external systems via a web service and/or exportable/importable in XML format. 5.4.2.6.    Form data elements must utilize the latest XForms/XSLT standards. Form data elements must be made available to and/or retrievable from external systems via a web service and/or exportable/importable in XML format.
5.4.1.2.7    The system must provide micro- and web service facility to manage service instances, usage, and others including the capability to horizontally scale up to maintain performance specifications. 5.4.2.7.    The system must provide micro- and web service facility to manage service instances, usage, and others including the capability to horizontally scale up to maintain performance specifications.
5.4.1.2.8    The system must be compatible with IP geolocation libraries and/or able to access IP geolocation web services. 5.4.2.8.    The system must be compatible with IP geolocation libraries and/or able to access IP geolocation web services.
5.4.1.2.9    The system must provide the capability to create a backup instance in a different cloud zone with built-in automatic synchronization whilst optimizing operational and maintenance costs. 5.4.2.9.    The system must provide the capability to create a backup instance in a different cloud zone with built-in automatic synchronization whilst optimizing operational and maintenance costs.
5.4.1.2.10  The system must provide backwards compatibility with global data interchange standards. 5.4.2.10.  The system must provide backwards compatibility with global data interchange standards.
5.4.1.3       Management Portal Functionality 5.4.3.      Management Portal Functionality
5.4.1.3.1    The portals must provide a UI-based integrated functionality to provide standard administrative tools including management of users, user profiles and permissions, report generation and analytics, performance dashboards, etc. 5.4.3.1.   The portals must provide a UI-based integrated functionality to provide standard administrative tools including management of users, user profiles and permissions, report generation and analytics, performance dashboards, etc.
5.4.1.4       Enterprise Process Flow Management and Administrative Functionality 5.4.4.      Enterprise Process Flow Management and Administrative Functionality
5.4.1.4.1    The process flow management microservice must allow multi-tenancy with the capability to independently and securely define process flows and process flow data. 5.4.4.1.   The process flow management microservice must allow multi-tenancy with the capability to independently and securely define process flows and process flow data.
5.4.1.4.2    The portal must provide UI-based integrated functionality to define process flows, assign users and user permissions, and other process management functions, as well as an administrative component to manage users, databases, reports, etc. 5.4.4.2    The portal must provide UI-based integrated functionality to define process flows, assign users and user permissions, and other process management functions, as well as an administrative component to manage users, databases, reports, etc.
5.4.1.5       Database 5.4.5.      Database
5.4.1.5.1    The system must use a horizontally scalable NoSQL data store (capable of using JSON data format) and a scalable RDBMS with the option to provide encrypted storage. 5.4.5.1.   The system must use a horizontally scalable NoSQL data store (capable of using JSON data format) and a scalable RDBMS with the option to provide encrypted storage.
5.4.1.5.2    The system utilizes a centralized database service to ensure data consistency across micro- and web services and their instances. 5.4.5.2.   The system utilizes a centralized database service to ensure data consistency across micro- and web services and their instances.
5.4.1.6       Reporting and Analytics 5.4.6.      Reporting and Analytics
5.4.1.6.1    The reporting and analytics tool must have the capability to access and process data from the database. 5.4.6.1.    The reporting and analytics tool must have the capability to access and process data from the database.
5.4.1.6.2    There must be a capability to integrate graphical reporting capabilities via ETL. 5.4.6.2.    There must be a capability to integrate graphical reporting capabilities via ETL.
5.4.1.7       Application Development and Delivery Framework 5.4.7.        Application Development and Delivery Framework
5.4.1.7.1    System applications must use a machine-independent and cross-platform development environment. 5.4.7.1.    System applications must use a machine-independent and cross-platform development environment.
5.4.1.7.2    The enterprise PaaS must allow for continuous delivery and continuous integration of cloud-based microservices or component applications with near zero overhead for deploying, configuring, updating and maintaining high availability whilst minimizing costs, time and other risks in delivering changes or updates. 5.4.7.2.    The enterprise PaaS must allow for continuous delivery and continuous integration of cloud-based microservices or component applications with near zero overhead for deploying, configuring, updating and maintaining high availability whilst minimizing costs, time and other risks in delivering changes or updates.
7.1.1.  Integrated regression testing through each delivery cycle. 7.1.    Integrated regression testing through each delivery cycle.
7.1.2.  Performance and functional testing for each component, module, web service, or database (where applicable). 7.2.    Performance and functional testing for each component, module, web service, or database (where applicable).
7.1.3.  Usability test 7.3.    Usability test
7.1.4.  Security tests 7.4.    Security tests
Please refer to Revised Terms of Reference as of 20 May 2016.

 

 

 

 

 

All terms, conditions and instructions to bidders specified in the Bidding Documents inconsistent with this Bid Bulletin are hereby superseded and modified accordingly.

Please use the following forms attached in this Supplemental Bid Bulletin:

  • Revised Schedule of Requirements as of 20 May 2016
  • Revised Technical Specifications as of 20 My 2016

For information and guidance of all concerned. For a complete set of documents, kindly click on the link below:
Supplemental Bid Bulletin No. 1 – Supply, Delivery, Installation and Configuration of Software Components and Perpetual Licenses to Implement the Government Operations Management Interoperability Platform and Profiling System

 

Issued this 20th day of May 2016.

 

(SGD) DENIS F. VILLORENTE