Section VII – Purchaser’s Requirements 1
R I S
EQUIREMENTS OF THE NFORMATION YSTEM
( T R , I S ,
INCLUDING ECHNICAL EQUIREMENTS MPLEMENTATION CHEDULE
S I T , B I
YSTEM NVENTORY ABLES ACKGROUND AND NFORMATIONAL
M )
ATERIALS
Notes on preparing the Requirements of the Information System
The Requirements of the Information System comprise four significant and closely related
subsections:
▪ Technical Requirements
▪ Implementation Schedule
▪ System Inventory Tables
▪ Background and Informational Materials
Each subsection is presented and discussed separately
Section VII – Purchaser’s Requirements 2
Technical Requirements
Notes on preparing the Technical Requirements
The Technical Requirements – in combination with the Implementation Schedule and the
supporting System Inventory Tables – state the Supplier’s obligations to design, supply and install
the Information System and, as such, should be “voiced” to the Supplier (i.e., “The System MUST
…” “The Supplier MUST …”). They form the contractual basis for the Purchaser-Supplier
interactions on technical matters (in combination with refinements introduced through the
Supplier’s bid, the Project Plan, and any Change Orders).
The Technical Requirements also must include all the technical details that Bidders will need to
prepare realistic, responsive, and competitive bids (i.e., covering all their obligations under the
Contract if so awarded). However, matters addressed to the Bidder’s (i.e., before contract award)
generally belong in the Format of the Technical Bid Section 8 of Part 1.
Often Technical Requirements are based on either consultant’s project proposals (voiced to the
Purchaser’s management) or bids from previous procurements (voiced to the Purchaser). In both
instances, care needs to be taken in converting these materials into Technical Requirements (voiced
to the Supplier). Otherwise, substantial ambiguity will be introduced into the Technical
Requirements from, among other things, “aspirational” text suggesting the benefits (to the
Purchaser) which are often not obligations that the Supplier can deliver on or be held to deliver
upon. Bid based language will often include “sales pitches”, such as “expandability up to sixteen
processors”, whereas the Technical Requirements need to be stated as threshold values to be
cleared by the Supplier (e.g., “expandability to at least sixteen processors”).
To the greatest extent possible, the Technical Requirements should be expressed in terms of the
Purchaser’s business activities, rather than a technological design. This leaves it up to the market
to determine what specific Information Technologies can best satisfy these business needs. This is
particularly relevant where the Information System will embody complex business logic in the form
of application software.
Even in the case of a relatively straight-forward Information System, where the business needs can
be clearly linked to technological and methodological requirements known in advance of any
bidding, the requirements must still be vendor-neutral and admit the widest possible range of
technical responses.
Accordingly, references to brand names, catalog numbers, or other details that limit the source of
any item or component to a specific manufacturer should be avoided. Where such references are
unavoidable, the words “or substantially equivalent” should be added to permit Bidders to bid
equivalent or superior technologies. (The Purchaser will need to be ready to indicate how this
equivalence will be assessed.) Only in the most exceptional circumstances may Bidders be required
to offer brand-name items and the equivalency clause be omitted. The IsDB’s consideration for
exception requires that:
(a) a brand-name component appears to have no equivalent or superior alternative,
because: of its unique ability to reliably interoperate with a relatively large base
of existing technologies; to conform with the Purchaser’s adopted technological
standards; and to offer overwhelming savings in terms of avoided costs for
retraining, data conversion, macro / business template redevelopment, etc.;
(b) the IsDB has agreed in advance, during project preparation, that such brand-name
restrictions are warranted; and
Section VII – Purchaser’s Requirements 3
(c) such brand-name components are the absolute fewest possible and each
component has been explicitly identified in the Bid Data Sheet for ITB 16.3 .
Similarly, where national standards or codes of practice are specified, the Purchaser should
include a statement that other national or international standards “that are substantially
equivalent” will also be acceptable.
To help ensure comparable bids and ease Contract execution, the Purchaser’s requirements must
be stated as clearly as possible, with minimum room for differing interpretations. Thus, wherever
possible, technical requirements should include definitive characteristics and quantifiable
measures. If technical characteristics in a specific range, or above or below specific thresholds,
are required, then these should be clearly specified. For example, the expandability of a server
should be stated as “no less than four processors.” Technical specifications that state only “four
processors” create unnecessary uncertainty for Bidders regarding whether or not, for example, a
server that could be expanded up to six processor boards would be technically responsive.
Quantitative technical specifications must, however, be employed with care. They can dictate
technical architectures and, thus, be unnecessarily restrictive. For example, a quantitative
requirement for the minimum width of the data path in a processor may be unnecessarily restrictive.
Instead, a specification of a required level of standard performance benchmark test is more
appropriate, allowing different technical approaches to achieving the Purchaser’s functional and
performance objectives. In general, the Purchaser should try to use widely accepted direct
measures of performance and functionality whenever possible and carefully review specifications
for those that might dictate technical architectures.
It is important that the Technical Requirements clearly identify which are mandatory features (for
which a bid’s nonconformance might require rejection for non-responsiveness) and which are
preferable features that can be included or excluded from a bid at the Bidder’s option. To enhance
the clarity of the specifications, Purchasers are advised to use the word “MUST” (in bold capitals)
in sentences describing mandatory requirements. A clear requirements numbering scheme is also
essential.
The following presents a sample outline format for the Technical Requirements Section. This can
and should be adapted to meet the Purchaser’s needs for the specific Information System to be
procured.
Any applicable sustainable procurement/environmental and social sustainability requirements
shall be added to the technical requirements.
3.0.4 below indicates noise levels and emission standard. Additional requirements as applicable
may include, but not limited to, aspects related to the protection of the environment including
management and safety of hazardous materials, resource efficiency and pollution prevention and
management measures.
Section VII – Purchaser’s Requirements 4
Technical Requirements
Table of Contents: Technical Requirements
A. Acronyms Used in The Technical Requirements 128
0.1 127128
B. Functional, Architectural and Performance Requirements 130
1.1 129
1.2 129130
1.3 130131
1.4 131
1.5 132
C. Service Specifications – Supply & Install Items 134
2.1 133
2.2 134
2.3 134
2.4 134
2.5 134
2.6 135136
2.7 135
D. Technology Specifications – Supply & Install Items 137
3.0 136137
3.1 136
3.2 137
3.3 138
3.4 138
3.5 140
3.6 140
E. Testing and Quality Assurance Requirements 140
4.1 140
4.2 140
4.3 141
F. Service Specifications – Recurrent Cost Items 1141
5.1 141
5.2 142
5.3 1434
Section VII – Purchaser’s Requirements 5
A. A U T T R
CRONYMS SED IN HE ECHNICAL EQUIREMENTS
0.1 Acronym Table
Note: Compile a table of organizational and technical acronyms used in the Requirements.
This can be done, for example, by extending the following table.
Term Explanation
bps bits per second
cps characters per second
DBMS Database Management System
DOS Disk Operating System
dpi dots per inch
Ethernet IEEE 802.3 Standard LAN protocol
GB gigabyte
Hz Hertz (cycles per second)
IEEE Institute of Electrical and Electronics Engineers
ISO International Standards Organization
KB kilobyte
kVA Kilovolt ampere
LAN Local area network
lpi lines per inch
lpm lines per minute
MB megabyte
MTBF Mean time between failures
NIC Network interface card
NOS Network operating system
ODBC Open Database Connectivity
OLE Object Linking and Embedding
OS Operating system
PCL Printer Command Language
Section VII – Purchaser’s Requirements 6
Term Explanation
ppm pages per minute
PS PostScript -- Adobe page description language
RAID Redundant array of inexpensive disks
RAM Random access memory
RISC Reduced instruction-set computer
SCSI Small Computer System Interface
SNMP Simple Network Management Protocol
SQL Structured Query Language
TCP/IP Transmission Control Protocol / Internet Protocol
V Volt
WLAN Wireless LAN
Section VII – Purchaser’s Requirements 7
B. F , A P
UNCTIONAL RCHITECTURAL AND ERFORMANCE
R
EQUIREMENTS
1.1 Legal and Regulatory Requirements to be met by the Information
System
1.1.1 The Information System MUST comply with the following laws and
regulations:
1.1.1.1 Presidential Regulation 16/2018 on Public Procurement (Peraturan
Presiden 16/2018 tentang Pengadaan Barang dan Jasa Pemerintah)
1.1.1.2 Ministry of Health Regulation 24/2022 on Electronic Medical
Records (Peraturan Kementerian kesehatan 24/2022 tentang Rekam
Medis Elektronik)
1.2 Business Function Requirements to be met by the Information
System
1.2.1 The developed IT Infrastructure MUST support the following business
functions
1.2.1.1 The general business requirement is to have a robust, secure and
resilient IT Infrastructure in six (6) Vertical hospitals.
1.2.1.2 This project aims to optimize the seamless integration of EMR and
Hospital Apps into SATUSEHAT through the establishment of
private data center technology in six (6) Vertical Hospitals.
1.2.1.3 The IT Infrastructure must securely store and manage critical
medical data, including EMRs; ensure data accessibility and
reliability; support the integration of healthcare systems; and
maintain a high level of security and resilience to provide efficient
and quality patient care.
1.2.1.4 The six referral and vertical hospitals (Dharmais Cancer Hospital,
Persahabatan Hospital, dr. Hasan Sadikin Hospital, dr. Sardjito
Hospital, Prof Dr IGNG Ngoerah Hospital and dr. Wahidin
Sudirohusodo Hospital will be the business users.
Section VII – Purchaser’s Requirements 8
1.2.1.5
1.3 Architectural Requirements to be met by the Information System
1.3.1 The Information System MUST be supplied and configured to implement
the following architecture.
Section VII – Purchaser’s Requirements 9
1.3.1.2 Applications and databases hosted in the private data center
1.3.1.3 Business users able to securely allow outbound connections to
SATUSEHAT endpoint and inbound connections to allow Local
connections (Health Facilities Environment)
1.3.1.4 Business users can access and work with reliable data without
interruptions during power outages.
1.4 Systems Administration and Management Functions Required to
be met by the Information System
1.4.1 The Information System MUST provide for the following management,
administration, and security features at the overall System level in an
integrated fashion.
1.4.1.2 Installation, Configuration and Change Management: The Supplier
MUST provide assistance during installation and managed services
support. Supplier MUST deployed and configured by certified
engineers in the dedicated space provided by the hospitals. Supplier
MUST provide managed support services which include unlimited
managed service support 24 hours x 7 days during the valid contract
period.
The Successful Bidder MUST provide the required services. This
would include:
• Requirement Analysis
Section VII – Purchaser’s Requirements 10
• Design
• Implementation
• Operation
• Maintenance
1.4.1.3 Operational Monitoring, Diagnostics, and Troubleshooting:
The Supplier will be responsible for operational monitoring, diagnostics,
and troubleshooting of the installed systems/equipment. Under the scope,
the supplier shall undertake monitoring, administration, and management of
the infrastructure supplied, installed and commissioned by them under this
tender. Purchaser and the successful bidder should agree upon the
contractual period and service levels for providing the necessary services.
All systems, equipment, software, and required licenses should be procured,
installed, configured, implemented, and maintained by the successful bidder
during the period of the contract.
1.4.1.4 User Administration and Access Control; User and Usage
Monitoring and Audit Trails:
● The purchaser wants to ensure that user and usage monitoring and audit
trails features are available for all systems and/or equipments that will
be installed under this tender.
1.4.1.5 System and Information Security and Security Policies: The
successful bidder must follow the recommendations/
guidelines/procedures stipulated under ISO 27001:2013 family of
standards.
1.4.1.6 Back-up and Disaster-Recovery:
The successful bidder must provide detailed procedure and
guidelines for back-up and disaster recovery for all
systems/equipments that will be installed under this tender.
1.5 Performance Requirements of the Information System
1.5.1 The Information System MUST reach the following performance levels.
1.5.1.1 The Bidder will provide the six hospitals the ICT Infrastructure in
order to enhance the quality of medical services, as well as human
resources in medical education and research
1.5.1.2 The improvement of ICT and effective use of ICT in collaboration,
treatment and improving the referral system as an important pillar
that will help not only increase the sustainability of the Project but
it will also help realizing long term structural gains in terms of health
system strengthening.
1.5.1.3 The requirement of the SLA provide are as follows:
Section VII – Purchaser’s Requirements 11
1. Priority 1 (Critical)
● Response time @ 15 min
● Resolution Time @ 1 hr
● Update Frequency @ 15 min
2. Priority 2 (High):
● Response time @ 30 min
● Resolution Time @ 4 hr
● Update Frequency @ 1 hr
3. Priority 3 (Moderate):
● Response time @ 30 min
● Resolution Time @ 4 hr
● Update Frequency @ 1 hr
4. Priority 4 (Low): Service or information request
● Response time @ 60 min
● Resolution Time @ 72 hr
● Update Frequency @ 24 hr
C. S S – S & I I
ERVICE PECIFICATIONS UPPLY NSTALL TEMS
1.1 System Analysis, Design and Customization/Development
1.1.1 The Supplier MUST perform the following Analysis and Design activities
using a formal system analysis/development methodology with the following key
activities and design deliverables.
1.1.1.1 Detailed Analysis: An in-depth study of IT Infrastructure
requirements is required to be performed by the selected vendor. At
the end of the detailed analysis stage the selected vendor must
submit a detailed analysis report. This report, if agreed by the
purchaser will be the basis of functional requirements and in the
light of this report the design of the proposed - will be made.
1.1.1.2 Physical Design: The requirement specifications from the detailed
analysis phase must be studied in this phase and then the final logical
and physical/cloud system design will be prepared. At the end of this
phase the selected vendor will submit the final design of the
proposed IT Infrastructure. The final design document must include
Section VII – Purchaser’s Requirements 12
detailed hardware architectures and supported software of the
proposed development of IT Infrastructure with Private Data Center
Platform. The design document must be approved by the purchaser.
1.2 Software Customization / Development
2.1.1 The Supplier MUST perform Software Customization / Development using
a formal software development methodology with the following characteristics
and/or with the following technologies and/or tools.
2.1.1.1 Not Applicable
1.3 System Integration (to other existing systems)
1.3.1 The Supplier MUST perform the following Integration Services, describe:
The Supplier should be able to integrate the Micro private data center with
the existing infrastructure in each hospital.
1.4 Training and Training Materials
1.4.1 The Supplier MUST provide the following Training Services and Materials.
1.4.1.1 User: The Supplier MUST prepare provide feasibility study or
benchmarking trip, to evaluate a well-equipped referral systems and
IT Infrastructure with detailed activities as follows:
● Prepare benchmarking trip
● Carry out the coordination process to the hospital for benchmarking
purposes
● Prepare work visit plans, budgets and process reports on the
implementation of benchmarking;
● Coordinate with PMU regarding the number and administrative
requirements of benchmarking participant;
● Provide Benchmark Report to PMU.
1.4.1.2 Technical: To be provided by the contracted bidder
1.4.1.3 Management: To be provided by the contracted bidder
1.5 Data Conversion and Migration
1.5.1 The Supplier MUST provide services and tools to perform the following
Data Conversion and Migration Services: Facilitate the data conversion and
migration processes, data mapping and data validation testing. Tools that
able to automate, streamline, and ensure the accuracy of the data transfer.
Section VII – Purchaser’s Requirements 13
1.6 Documentation Requirements
1.6.1 The Supplier MUST prepare and provide the following Documentation.
1.6.1.1 End-User Documents: Not Applicable
1.6.1.2 Technical Documents:
▪ Letter of Support/Letter of Authorization
▪ Business Requirements Document
▪ Technical Specifications Document
▪ Handover Report (BAST)
▪ User Manual
▪ Operation Manual for Security Incident
1.7 Requirements of the Supplier’s Technical Team
1.7.1 The Supplier MUST maintain a technical team of the following roles and
skill levels during the Supply and Installation Activities under the Contract:
1.7.1.1 Project Team Leader (1 person): At least 10 years proven work
experience as a team leader or supervisor with PMP Certificate. In-
depth knowledge of software development project management and
performance metrics. Excellent communication and leadership
skills. Direct experience in working with Public Sector/Private
Sector is a plus. Master Degree in IT, Information System,
Management, Computer Science, or equivalent.
1.7.1.2 Health Information Technology Specialist (1 person):
At least 10 years proven work experience in Health Informatics. In-
depth knowledge of Health technology, health information system and
the implementation of HIS within Healthcare Facilities in Indonesia
with Electronic Health Record Certification. Direct experience in
working with Ministry of Health and Hospital in Indonesia is a plus.
Master Degree in Health Informatics, Healthcare Information
Management, Public Health, Biomedical Sciences, or equivalent.
1.7.1.3 Cloud Architect (1 Person):
At least 3 years experience in designing and deploying cloud
architecture, experience in migration, and has in-depth knowledge of
network-level security, backup and recovery. Must have Professional
Cloud Architect Certification. Bachelor's degree in Computer Science
or Information Technology, or equivalent.
1.7.1.4 Cloud Engineer (3 person):
At least 1 year experience in infrastructure management and public
and/or private cloud operations or equivalent. Proficient in advising as
Section VII – Purchaser’s Requirements 14
well as coordinating and communicating customer requirements with
internal specifically on cloud deployment or migration. Have Associate
Cloud Engineer Certification. Bachelor's degree in Computer Science
or Information Technology, or equivalent.
2.7.1.4 Project Admin (1 person):
At least 1 (one) year experience and a portfolio as content writer or
technical report related. Have experience writing in English and Bahasa.
Bachelor's degree in Computer Science or Information Technology, or
equivalent.
D. T S – S & I I
ECHNOLOGY PECIFICATIONS UPPLY NSTALL TEMS
3.0 General Technical Requirements
3.0.1 Language Support: All information technologies must provide support for
the English and Bahasa Indonesia.
3.0.2 Electrical Power: All active equipment must include power plugs standard
in Indonesia.
3.0.3 Environmental: Not Applicable
3.0.4 Safety: Not Applicable
3.1 Computing Hardware Specifications
3.1.1 Processing Unit Type 1: Server Management
3.1.1.1 Processing unit performance: As configured for the bid, the
processing unit MUST, at a minimum,
(a) Achieve SPEC CPU2017 rating or equivalent
3.1.1.2 Processor expandability:
(a) Minimum acceptable number of core: 16 core
(b) Minimum acceptable Processor Base Frequency 2.00 GHz
3.1.1.3 Processor memory and other storage:
(a) Main memory: 32GB
(b) Disk storage; 960GB SSD
3.1.1.4 Processing unit fault tolerance: Bidder MUST provide hot-
swappable modules; redundant power supplies and other modules;
error checking; and failure detection.
3.1.1.5 Processing unit management features: Bidder MUST provide local
and remote management;
Section VII – Purchaser’s Requirements 15
3.1.1.6 Processing unit input and output devices: Bidder MUST provide
network interfaces with minimum 4x10Gb; controllers interface;
VGA Port; and USB Port;
3.1.2 Processing Unit Type 2: Server Node
3.1.2.1 Processing unit performance: As configured for the bid, the
processing unit MUST, at a minimum,
(a) Achieve SPEC CPU2017 rating or equivalent
3.1.2.2 Processor expandability:
(c) Minimum acceptable number of core: 24 core
(d) Minimum acceptable Processor Base Frequency 2.00 GHz
3.1.2.3 Processor memory and other storage:
(c) Main memory: 256GB
(d) Disk storage; 6720GB SSD
3.1.2.4 Processing unit fault tolerance: Bidder MUST provide hot-
swappable modules; redundant power supplies and other modules;
error checking; and failure detection.
3.1.2.5 Processing unit management features: Bidder MUST provide local
and remote management;
3.1.2.6 Processing unit input and output devices: Bidder MUST provide
network interfaces with minimum 4x10Gb; controllers interface;
VGA Port; and USB Port;
3.2 Network and Communications Specifications
3.2.1 Local Area Network:
3.2.1.1 Equipment and software:
● Internet Protocol (IP),
● Simple Network Management Protocol (SNMP),
● Link Aggregation Control Protocol (LACP),
● Frame sizes up to 9K bytes
● Dynamic Host Configuration Protocol (DHCP);
● Features: Stacking Switch or Virtual Port Channel (vPC) or other
3.2.1.2 Cabling: Not Applicable
3.2.1.3 Minimum acceptable number and speed of ports: 16 ports with 10G
speed
3.2.2 Wide-Area Network:
3.2.2.1 Equipment and software:
Section VII – Purchaser’s Requirements 16
● Provide High Availability Configurations such as Active-Active,
Active-Passive, Clustering;
● Provide Security features including SD-WAN, App Control Service,
IPS Service, Malware Protection, Web and Video Filtering Service,
and Antispam Service
3.2.2.2 Telecommunications Services: Not Applicable
3.2.3 Other Communications Equipment: Not Applicable
3.3 Ancillary Hardware Specifications
3.3.1 Shared Data Storage Devices: Not Applicable
3.3.2 Shared Output and Input Devices: Not Applicable
3.3.3 Power Conditioning Devices: Not Applicable
3.3.4 Specialized Furnishing/Equipment:
3.3.4.1 Equipment Cabinets/Racks: SUPPLIER must provide MicroDC that
contained 42U Rack with Rack Power Distribution, Local & Remote
Management, Interior Lighting, Cable Manager, Local Touch-screen
Display Interface; 3.5kW split system Outdoor unit, Pre-charged
refrigerant; 3.5kW split system Indoor unit, Gravity Drain; UPS 6000VA
230V ,with RailKit, External Battery Pack; PDU Metered ZeroU 16A
230V; Black Modular Toolless Blanking Panel; Temperature and Humidity
Sensors; Door Contact Sensors; Water Leakage Sensor; Smoke Sensor; and
Alarm Beacon;
3.3.4.2 Environment Control Equipment:
Air conditioning units; humidity control equipment;
3.3.4.3 Physical Access Control Equipment:
Door entry controls; intrusion detection;
3.3.4.3 Logical Access Control Equipment: Not Applicable
3.4 Standard Software Specifications
3.4.1 System Software and System-Management Utilities:
3.4.1.1 Early Detection Response: The supplier MUST deliver an Endpoint
Detection and Response (EDR) solution, complemented by a 24x7
Security Operations Center (SOC). The expected EDR solution
must offer capabilities for Remote Containment and Remediation,
Endpoint Detection and Response, and continuous monitoring of all
endpoints. It should analyze data in real-time, automatically
Section VII – Purchaser’s Requirements 17
identifying threats. Additionally, the EDR system should provide
continuous high-fidelity telemetry with forensic-level detail across
endpoints and workloads distributed throughout the network edge
and hybrid cloud infrastructure. Throughout the service provision,
the supplier must deliver EDR services that are acknowledged as a
Leader on Magic Quadrant for Endpoint Protection Platform 2022
or substantially equivalent.
3.4.1.2 Privileged Access Management (PAM): Supplier MUST provide
Privileged Access Management (PAM) solution for monitoring,
recording, and overseeing privileged user sessions in real-time. The
supplied PAM must have capabilities such as credential vaulting,
safeguarding critical assets, and incorporating machine learning for
threat detection and analytics.
3.4.1.3 Infrastructure and Application Performance Monitoring: Supplier
MUST provide Infrastructure and Application Performance
Monitoring services recognized as a leader on the 2023 Magic
Quadrant for Application Performance Monitoring and
Observability or equivalent.. The Infrastructure and Application
Performance Monitoring will be utilized to monitor, troubleshoot,
and enhance the performance of both applications and infrastructure.
The provided Infrastructure and Application Performance
Monitoring should possess features such as application tracing,
logging, observation of both infrastructure and applications, and AI-
powered anomaly detection or substantially equivalent.
3.4.2 Networking and Communications Software: Not Applicable
3.4.3 General-Purpose Software: Not Applicable
3.4.4 Database Software and Development Tools:
3.4.4.1 Data Server Management Platform: Bidder should provider
Management Platform that will controls the dedicated data
infrastructure for each Hospital, providing resource allocation,
security, automation, and scalability while ensuring efficient
management.
3.4.5 Business Application Software:
Supplier MUST Develop project monitoring dashboard to evaluate and
monitor the progress of MoH x IsDB project. The provided dashboard will
directly evaluate by IsDB team and auditor. Hence, the project monitoring
dashboard expected to monitor the following key objective:
● Project Implementation progress: Provide dashboard that present the
progress of project
● Spend Management Modules: Provide dashboard that capture,
analyze and share project spending
Section VII – Purchaser’s Requirements 18
3.5 Consumables
3.5.1 Printer Ink / Toner – Printer Type 1: Not Applicable
3.6 Other Non-IT Goods
3.6.1 Workstation Desks: Not Applicable
3.6.2 Photocopiers: Not Applicable
3.6.3 Specialized Mechanical Systems – Datacenter : Not Applicable
E. T Q A R
ESTING AND UALITY SSURANCE EQUIREMENTS
4.1 Inspections
4.1.1 No factory inspection from the Purchaser is necessary
4.1.2 Inspections following delivery shall be arranged in a designated location as
per the instruction of the the PMU. The inspection activities will include
checks whether the hardware and software supplied under this tender
comply with the minimum requirements set forth in the technical
requirements section of this bidding document. It will also check the
physical condition of the items as well as ingenuity of their source and other
obligations mentioned in this bidding document and the agreement signed
between the purchaser and the selected vendor.
4.2 Pre-commissioning Tests
4.2.0 In addition to the Supplier’s standard check-out and set-up tests, the Supplier
(with the assistance of the Purchaser) must perform the following tests on the
System and its Subsystems before Installation will be deemed to have occurred
and the Purchaser will issue the Installation Certificate(s) (pursuant to GCC
Clause 26 and related SCC clauses).
4.2.1 Test of all individual software systems must be performed and desired
performance indicators and technical specifications mentioned in this tender
must be met by each and every software component / system included in this
tender.
4.2.2 Test of all individual hardware/ components must be performed and desired
performance indicators and technical specifications mentioned in this tender
must be met by each and every hardware component / system included in this
tender.
Section VII – Purchaser’s Requirements 19
4.3 Operational Acceptance Tests
4.3.0 Pursuant to GCC Clause 27 and related SCC clauses, the Purchaser (with
the assistance of the Supplier) will perform the following tests on the
System and its Subsystems following Installation to determine whether the
System and the Subsystems meet all the requirements mandated for
Operational Acceptance.
4.3.1 The Purchaser (with the assistance of the Supplier) shall perform Operational
Acceptance Tests to ascertain whether the System, or a specified Subsystem, is
able to attain the functional and performance requirements specified in the
Technical Requirements and Agreed and Finalized Project Plan, in accordance
with the provisions of GCC Clause 27.2 (Operational Acceptance Test).
The Supplier shall use all reasonable endeavors to promptly remedy any defect
and/or deficiencies and/or other reasons for the failure of the Operational
Acceptance Test that the Project Manager has notified the Supplier of. Once
such remedies have been made by the Supplier, the Supplier shall notify the
Purchaser, and the Purchaser, with the full cooperation of the Supplier, shall use
all reasonable endeavors to promptly carry out retesting of the System or
Subsystem. Upon the successful conclusion of the Operational Acceptance
Tests, the Supplier shall notify the Purchaser of its request for Operational
Acceptance Certification, in accordance with GCC Clause 27.3.3. The
Purchaser shall then issue to the Supplier the Operational Acceptance
Certification in accordance with GCC Clause 27.3.3 (a), or shall notify the
Supplier of further defects, deficiencies, or other reasons for the failure of the
Operational Acceptance Test. The procedure set out in this GCC Clause 27.3.4
shall be repeated, as necessary, until an Operational Acceptance Certificate is
issued.
F. S S – R C I
ERVICE PECIFICATIONS ECURRENT OST TEMS
5.1 Warranty Defect Repair
5.1.1 The Supplier MUST provide the following services under the Contract or,
as appropriate under separate contracts (as specified in the bidding
documents).
5.1.1.1 Warranty Defect Repair Service: Three (3) year warranty should be
provided to all equipment, systems, and hardware and software
items (Defects of the total IT Infrastructure (IS) will be addressed at
on-site in accordance with the assigned priority level as mentioned
in 1.4.1.2 Operational Monitoring, Diagnostics, and
Section VII – Purchaser’s Requirements 20
Troubleshooting) including on-site defects remedy service, as
applicable.
5.2 Technical Support
5.2.1 The Supplier MUST provide the following services under the Contract or,
as appropriate under separate contracts (as specified in the bidding
documents).
5.2.1.1 User support / hot line:
Supplier MUST provide a ticketing tools and support which includes unlimited
management service support 24 hours x 7 days during the valid contract
period.
The requirement of the Level of Support provide are as follows:
Level 1 (DCO/Help Desk )
● Responsibilities:
○ Answer support calls/ticket
○ Work on problem using specified documentation
○ Document ticket and escalate to Level 2 support
● Support Hour: 24 hours x 7 days
Level 2 (Technology Support Team)
● Responsibilities:
○ Handle problem that cannot be resolved by Level 1
○ Perform all items specified in managed service SoW
○ Create problem resolution documentation for future reference
○ Escalate to Level 3 or appropriate party
● Support Hour: Monday - Friday (09.00 – 17.00)
Level 3 (Technology Expert Team)
● Responsibilities:
○ Handle complex problem that can not be resolved by Level 2
○ Collaborate with 3rd party vendor to resolve complex and
challenging issues
● Support Hour: Monday - Friday (09.00 – 17.00)
5.2.1.2 Technical Assistance:
Section VII – Purchaser’s Requirements 21
1. Priority 1 (Critical):
● Response time @ 15 min
● Resolution Time @ 1 hr
● Update Frequency @15 min
2. Priority 2 (High):.
● Response time @ 30 min
● Resolution Time @ 4 hr
● Update Frequency @ 1 hr
3. Priority 3 (Moderate):
● Response time @ 30 min
● Resolution Time @ 4 hr
● Update Frequency @ 1 hr
4. Priority 4 (Low): Service or information request
● Response time @ 60 min
● Resolution Time @ 72 hr
● Update Frequency @ 24 hr
5.2.1.3 Post-Warranty Maintenance Services: Supplier MUST provide 1
(one) year post warranty maintenance service. Cost of Maintenance
Service must be bid in the Recurrent Cost Items
5.3 Requirements of the Supplier’s Technical Team
5.3.1.1 Project Manager (1 person):
At least 10 years proven work experience as a team leader or supervisor
with PMP Certificate. In-depth knowledge of software development
project management and performance metrics. Excellent
communication and leadership skills. Direct experience in working with
Public Sector/Private Sector is a plus. Master Degree in IT, Information
System, Management, Computer Science, or equivalent.
5.3.1.2 Health Information Technology Specialist (1 person):
At least 10 years proven work experience in Health Informatics. In-
depth knowledge of Health technology, health information system and
the implementation of HIS within Healthcare Facilities in Indonesia
Section VII – Purchaser’s Requirements 22
with Electronic Health Record Certification. Direct experience in
working with Ministry of Health and Hospital in Indonesia is a plus.
Doctoral Degree in Health Informatics, Healthcare Information
Management, Public Health, Biomedical Sciences, or equivalent.
5.3.1.3 Cloud Architect (1 Person):
At least 3 years experience in designing and deploying cloud
architecture, experience in migration, and has in-depth knowledge of
network-level security, backup and recovery. Must have Professional
Cloud Architect Certification. Bachelor's degree in Computer Science
or Information Technology, or equivalent.
5.3.1.4 Cloud Engineer (3 person):
At least 1 year experience in infrastructure management and public
and/or private cloud operationsor equivalent. Proficient in advising as
well as coordinating and communicating customer requirements with
internal specifically on cloud deployment or migration. Have Associate
Cloud Engineer Certification. Bachelor's degree in Computer Science
or Information Technology, or equivalent.
5.3.1.5 Technical Writer (1 person):
At least 1 (one) year experience and a portfolio as content writer or
technical report related. Have experience writing in English and Bahasa.
Bachelor's degree in Computer Science or Information Technology, or
equivalent.
Section VII – Purchaser’s Requirements 23
Implementation Schedule
Notes on preparing the Implementation Schedule
The Implementation Schedule summarize when and where Installation, and
Operational Acceptance should take place for all Subsystems and/or major components of the
System, and for the overall System itself – as well as any other major Contract milestones.
Note: The delivery date is not presented in the Implementation Schedule. Under Incoterms
2010 for CIP, Delivery refers to the date when the Supplier delivers the goods to the
first carrier at the port of embarkation, not to the arrival of the goods at the destination
site. Delivery (shipment) date therefore varies according to the country of origin of the
goods and the Supplier's chosen method of transport.
The target dates need to be realistic and achievable in light of the capacity of both the
average Supplier and the Purchaser to carry out their respective contract obligations. Also,
the Purchaser must take care to ensure that the dates specified in the Schedule are consistent
with any specified elsewhere in the bidding document, especially in the GCC/SCC (e.g., and/or
times specified for the submission and acceptance of the Agreed Project Plan).
The work breakdown structure (deliverables) in the Implementation Schedule should
be sufficiently detailed to facilitate careful management of the Contract – but not so detailed
that it unnecessarily constrains bidders from organizing the proposed work in the most efficient
and effective manner.
To facilitate the bidding and the contract management processes, the Implementation
Schedule, the System Inventory Tables and Price Schedules should be closely linked. In
particular, the Implementation Schedule defines the major deliverable Subsystems. For each
Subsystem there should be a corresponding System Inventory Table or Tables. These System
Inventory Tables catalog the specific items (inputs) comprising the Subsystem, as well as the
quantities of each item required (for the supply and install cost items as well as the recurrent
cost items). For each System Inventory Table there should be a corresponding Price Schedule
that closely mirrors the System Inventory Table. Careful development of these materials will
greatly improve the changes of obtaining complete and comparable bids (and ease the bid
evaluation process) as well as improving the likelihood that the Purchaser’s and Supplier’s
interactions during contract execution are closely orchestrated (thus easing the burden of
contract management and improving the likelihood of successful implementation of the
Information System).
The sample tables comprise:
(a) An Implementation Schedule Table;
(b) A Site Table(s); and
(c) A Table of Holidays and other Non-Working Days.
Section VII – Purchaser’s Requirements 24
The Purchaser should modify these tables, as required, to suit the particulars of the
System (and Subsystems) to be supplied and installed. The sample text in the tables is
illustrative only and should be modified or deleted as appropriate.
The timings stated in the Implementation Schedule should be specified in weeks from
Contract Effectiveness. This will ease the maintenance of the bidding documents during the
preparation and bidding processes.
Where appropriate, the Implementation Schedule should indicate the deliverables
against which Liquidated Damages may be applied in the event of implementation delays
arising from the actions of the Supplier (as governed by the SCC and GCC clause 28). These
milestones should be kept to the essential minimum needed by the Purchaser to ensure contract
discipline by the Supplier – but not so many that they unnecessarily strain the Purchaser-
Supplier relationship upon which the successful implementation of the Information System will
invariably depend.
The Site Table(s) catalog the physical location of the site(s) where the System is to be
supplied, installed, and operated. The site(s) may consist of a number of branch offices in
remote regions, different departments or offices in the same city, or a combination of these.
The Purchaser must specify this information in sufficient detail so that Bidders can
accurately estimate costs related to:
(a) Delivery and insurance;
(b) Installation, including cabling and inter-building communications, etc.
(c) Perform support services, such as warranty defect repair, maintenance, and
other technical support services; and
(d) Other related Service obligations the successful Bidder will have to perform
under the Contract, including related travel and subsistence costs.
This information will also help Bidders identify which site(s) may warrant a site visit
during the period they are preparing their bids. If the System presents complex installation
challenges, site layout drawings should be included in the Background and Informational
Materials Section.
Section VII – Purchaser’s Requirements 25
Table of Contents: Implementation Schedule
A. 147
B. 150
C. 150
A.
I S T
MPLEMENTATION CHEDULE ABLE
Note: Refer to the System Inventory Table(s) for the specific items and components that
constitute the Subsystems or item. Refer to the Site Table(s) below for details regarding
the site and the site code.
Section VII – Purchaser’s Requirements 26
Line Delivery
Item Configurat Site / Site (Bidder to specify Installation Acceptance Liquid
No. Subsystem / Item ion Table Code in the Preliminary (weeks from (weeks from ated
No. Project Plan) Effective Date) Effective Date) Dama
ges
Milest
one
0 Project Plan - - - - W2 - - W3 no
all sites
1 Initiation Phase
Business
all sites
Requirement
1.1 Document
all sites
1.2 System Design
Purchasing
all sites
1.3 Hardware
- -
2
all sites
Design Phase
2.1 Design Private
all sites
Data Center
all sites
3 Execution Phase
MicroDC
- - all sites - - yes
3.1 Installation
Device and
all sites
Software
3.2 Installation
Private Data
all sites
Center
3.3 Implementation
all sites
3.4 Testing
Section VII – Purchaser’s Requirements 27
Line Delivery
Item Configurat Site / Site (Bidder to specify Installation Acceptance Liquid
No. Subsystem / Item ion Table Code in the Preliminary (weeks from (weeks from ated
No. Project Plan) Effective Date) Effective Date) Dama
ges
Milest
one
all sites
4 Closing Phase
all sites
4.1 Documentation
all sites
4.2 Training
Operational W40
Acceptance of
the System as an
integrated whole
y
- - indicates not applicable. “Indicates repetition of table entry above.
Section VII – Purchaser’s Requirements 28
B.
S T ( )
ITE ABLE S
Drawing
Site Reference No. (if
Code Site City / Town / Region Primary Street Address any)
1 Dharmais Cancer Hospital Jakarta Jl. S Parman Kav.84-86,
Slipi. West Jakarta ,
DKI Jakarta, 11420,
Indonesia
2 Persahabatan Hospital Jakarta Jl. Persahabatan Raya
No.1, East Jakarta, DKI
Jakarta, 13230,
Indonesia
3 dr. Hasan Sadikin Hospital Bandung Jl. Pasteur No. 38,
Bandung, West Java,
40161, Indonesia
4 dr. Sardjito Hospital Prof Yogyakarta Jl. Kesehatan No. 1
Sekip Sinduadi,
Yogyakarta, Special
Region of Yogyakarta,
55281, Indonesia
5 Prof Dr IGNG Ngoerah Hospital Denpasar Jl. Diponegoro,
Denpasar, Bali, 80113,
Indonesia
6 dr. Wahidin Sudirohusodo Hospital Makassar Jl.Perintis Kemerdekaan
Km.11, Makassar,
South Sulawesi, 90245
Section VII – Purchaser’s Requirements 29
C.
T H O N -W D
ABLE OF OLIDAYS AND THER ON ORKING AYS
Month 2024 2025 2026 2027
1
2
3
4
5
6
7
8
9
10
11
Section VII – Purchaser’s Requirements 30
System Inventory Tables
Notes on preparing the System Inventory Tables
The System Inventory Tables detail:
(a) for each Subsystem (Deliverable) indicated in the Implementation Schedule,
the Information Technologies, Materials, and other Goods and Services that
comprise the System to be supplied and/or performed by the Supplier;
(b) the quantities of such Information Technologies, Materials, and other Goods
and Services;
(c) the sites and the location of each on a specific site (e.g., building, floor, room,
department, etc.)
(d) the cross references to the relevant section of the Technical Requirements
where that item is described in greater detail
The Purchaser should modify these tables, as required, to suit the particulars of the
System (and Subsystems) to be supplied and installed. The sample text provided for
various sections of the tables is illustrative only and should be modified or deleted as
appropriate.
There are two sample formats given for the System Inventory Tables: one for the
Supply and Installation cost items and the second for Recurrent Cost Items needed (if any).
The second version of the table permits the Purchaser to obtain price information about
items that are needed during the Warranty Period.
Section VII – Purchaser’s Requirements 31
S I T (S I C I ) [ :
YSTEM NVENTORY ABLE UPPLY AND NSTALLATION OST TEMS INSERT IDENTIFYING
]
NUMBER
Line item number: [ specify: relevant line item number from the Implementation Schedule (e.g., 1.1) ]
[ as necessary for the supply and installation of the System, specify: the detailed components and quantities in the System Inventory
Table below for the line item specified above, modifying the sample components and sample table entries as needed. Repeat the
System Inventory Table as needed to cover each and every line item in the Implementation Schedule that requires elaboration. ]
Relevant Technical Additional Site Information
Component Specifications (e.g., building, floor,
No. Component No. department, etc.) Quantity
1. Hardware - - - -
1.1 Micro Data Center 4 1-6 6
1.2 Server 4 1-6 24
1.3 Firewall 4 1-6 12
1.4 Switch 4 1-6 12
:
Note: - - indicates not applicable. “ indicates repetition of table entry above.
Section VII – Purchaser’s Requirements 32
S I T (R C I ) [ : ] –
YSTEM NVENTORY ABLE ECURRENT OST TEMS INSERT IDENTIFYING NUMBER
Line item number: [ specify: relevant line item number from the Implementation Schedule (e.g., y.1) ]
Component Relevant
No. Component Technical Y1 Y2 Y3
Specifications No.
all items, all sites, all items, all sites, all items, all sites,
1. Warranty Defect Repair included in the included in the included in the
Supply and Install Supply and Install Supply and Install
Price Price Price
2. Software/Firmware Licenses and 4-6 all items, all sites, all items, all sites, all items, all sites,
Updates: included in the included in the included in the
Supply and Install Supply and Install Supply and Install
- Firewall Licenses
Price Price Price
- Cloud Management Platform
Licenses
- Infrastructure and Application
Monitoring
- SIEM
- PAM
- EDR
3. Technical Services
3.1 Project Manager 3
3.2 Health Information Technology 3
Specialist
3.3 Cloud Architect 3
Section VII – Purchaser’s Requirements 33
Component Relevant
No. Component Technical Y1 Y2 Y3
Specifications No.
Cloud Engineer
3
Technical Writer
3
Note: - - indicates not applicable. “ indicates repetition of table entry above.
Section VII – Purchaser’s Requirements 34
Background and Informational Materials
A. B
ACKGROUND
0.1 The Purchaser
0.1.1 The Directorate General of Health Services of the Ministry of Health
which has the responsibility and functions to providing health services
to officials, employees within the Ministry of Health and the
surrounding community at the national level. The function of the Health
Service Unit is to organize the implementation of medical services,
emergency services, laboratory services, radiology services,
physiotherapy services and the human resources and general
administration affairs.
0.1.2 The SATUSEHAT (SATSET) platform is a digital health ecosystem
platform that provides data connectivity, analysis, and services to
support and integrate various health applications in Indonesia. In
developing this platform, the Ministry of Health adopted the Platform-
as-a-service (PAAS) infrastructure model that connects the entire
ecosystem of health industry players to create one reliable national
health data. Later this platform will become a liaison between various
application platforms for various health industry players. For this
reason, all applications and health service facilities such as vertical
hospitals, government hospitals, private hospitals, health centers,
posyandu, laboratories, clinics and pharmacies must follow the
standards set by the Ministry of Health on the SATSET platform.
0.1.3 The Directorate General of Health Services of the Ministry of Health
has received financing from the Islamic Development Bank toward the
cost of the Strengthening of National Referral Hospital and Vertical
Technical Units Projectt. The goal is to provide a robust, secure, and
resilient environment for the Health IT Infrastructure data from the
Sixth Referral and Vertical Hospital to support the integration process
into SATUSEHAT.
0.2 The Purchaser’s Business Objectives for the Information System
0.2.1 Strengthening of the hospital infrastructure of the selected locations it
can improve the response time for treatment of patients, provide high
quality care with better medical equipment and a well-trained health
workforce, provide more evidence-based clinical solutions through
assessing and analyzing more data based on better integrated ICT
infrastructure
0.2.2 IT Infrastructure is required to securely store and manage critical
medical data, including Electronic Medical Records (EMRs); ensure
Section VII – Purchaser’s Requirements 35
data accessibility and reliability; support the integration of healthcare
systems; and maintaining a high level of security and resilience to
provide efficient and quality patient care. In current situation, the
presence of low-quality servers within the hospital, compromised by
viruses and ransomware, presents a significant obstacle, impeding the
seamless integration of hospital applications and Electronic Medical
Records (EMR) into SATUSEHAT.
0.2.3 The subject project to provide IT Infrastucture to support the data
collection from each Hospital Information System and/or Application to
increase the effectiveness in integrating data into SATUSEHAT and to
support the development of the Maternal and Child referral system
0.2.4 One of the project's components is the procurement of goods and
services that will strengthen health IT Infrastructures through private
data center technology. The developed infrastructure aims to provide a
robust, secure, and resilient environment for data storage and to support
the integration of medical data into SATUSEHAT.
B. I M
NFORMATIONAL ATERIALS
0.3 The Legal, Regulatory, and Normative Context for the Information System
0.3.1 Presidential Regulation 16/2018 on Public Procurement (Peraturan
Presiden 16/2018 tentang Pengadaan Barang dan Jasa Pemerintah)
0.3.2 Ministry of Health Regulation 24/2022 on Electronic Medical Records (Peraturan
Menteri Kesehatan 24/2022 tentang Rekam Medis Elektronik
0.3.3 Ministry of Health Regulation 75/2019 on Health Crisis Management (Peraturan
Menteri Kesehatan 75/2019 tentang Penanggulangan Krisis Kesehatan)
0.3.4 ISO 27001:2013 on Information Security Management
0.4 Existing Information Systems / Information Technologies Relevant to the
Information System
0.4.1 SATUSEHAT
0.5 Available Training Facilities to Support the Implementation of the
Information System
0.5.1 Not Applicable
0.6 Site Drawings and Site Survey Information Relevant to the Information
System
0.6.1 Not Applicable