Annex 1: Request for Fixed Price Task Order Proposal No.NPL-HQ-STO-001 A & B
Global Health Supply Chain – Procurement and Supply Management (GHSC-PSM) project
IQS No. NPL-HQ-001
Global Health Supply Chain – Procurement and Supply Management (GHSC-PSM) project in Nepal
is soliciting a proposal(s) under the above mentioned IQS for the following service(s), pursuant to
IQS clause C.3 Ordering:
TASK ORDER STATEMENT OF WORK:
1. Background: The Global Health Supply Chain Program – Procurement and Supply Management
(GHSC-PSM) project (alternately referred to herein as “Chemonics” or “GHSC-PSM” or “Buyer”) is
an official project of the United States Agency for International Development (USAID) implemented
by Chemonics International and its consortium members. The purpose of GHSC-PSM is to ensure
uninterrupted supplies of health commodities in support of USG-funded public health initiatives
around the world. The project provides direct procurement and supply chain management support to
the President’s Emergency Plan for AIDS Relief (PEPFAR), the President’s Malaria Initiative (PMI),
and Population and Reproductive Health (PRH). GHSC-PSM supports health programs through the
supply of a wide range of health commodities, including contraceptives and condoms, essential
drugs; and select commodities for HIV/AIDS, malaria, maternal and child health, and infectious
diseases. The software application will focus on logistics management of the health commodities for
Ministry of Health (MoH) in Nepal and will be implemented at Central, regional and district medical
stores and also includes the reporting from the last mile i.e. from Service Delivery Points (SDP). In
addition to the intervention approaches highlighted under Section I, part 1, this Sub-Task Order
(STO) will focus on the successful implementation of Phase I, as detailed below.
2. Sub-Task Order Phase 1:
I.A. Sub Task Order A-1 SOW (Phase I): Technical Description
Overview
The purpose of this procurement is to provide an off-the-shelf system for the Ministry of Health from
the software vendor who has proven experience in developing, implementing and customization of
Logistics Management Information Systems. The application will have a web-interface, android
application (for phone/tablet) and a desktop offline module for Inventory Management.
The successful offeror shall deliver to Chemonics the deliverables set forth in A and B below.
A. System’s Main Functionality:
 Track and report logistics (stock status) data:
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 2 of 35




Warehouse Management functionality:
Requisitions
Stock Data Import and Collation:
Data processing - Reports and dashboards
Detailed requirements are listed below:
Solution Technical Requirements
Requirements
Platform(s)
Mobile
Web
Description
Internet connectivity and electricity supply are scarce for
most health facilities. However, mobile connectivity is on
the rise and generally available in most of the country. Since
the current data collection does not require constant
connectivity, mobile computing platforms can be used for
data collection, especially for areas where wireless
connectivity is mostly available. Data collection volumes are
not significant which further makes the mobile computing
platform very attractive. The mobile computing component
of this application needs to provide all functionality required
for data collection even when connectivity is poor or totally
absent.
A web-based component should complement the mobile
computing component for facilities with reliable
connectivity. The web-based component should have
enhanced capabilities, including but not limited to, error
correction, data visualization, application administration and
configuration.
The mobile component of eLMIS is planned for
smartphones and/or tablets i.e. Android OS. Minimum
hardware requirements will need to be defined. As long as
the mobile component provides the required functionality,
the application solution is not tied to a specific solution. E.g.
the solution may use an Android app or an in-browser
solution with offline capability.
The web component of eLMIS will be used where internet
connectivity is reliable. The web component must be
compatible with web browsers such as Google Chrome
version 57 or later and Mozilla Firefox version 52 and later.
Minimum hardware and software requirements for the
workstation for the web-component will need to be defined.
The web-component must provide comprehensive
functionality including redundancy of the mobile
component.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 3 of 35
Role Based Access Control
Functional Requirements
User Self Service
The application's functionality will cater to many levels of
users with various needs. In order to ensure correct
compartmentalization of data and functionality, user roles
will be specified. Users may have one or more roles with
progressively higher levels of access and functionality. If a
user has more than one role, then the functionality and
access rights of the higher role apply. The roles list will be
specified at a later date, but the expected roles are listed
below. However, the system must be flexible enough to
ensure that new roles can be created and both access and
functionality for these new roles be configurable.
Expected Roles List
- Data Entry / Reporter
- Data Reviewer
- Health Manager
- Administrator
- Central Staff
- Public of Nepal
- Govt. of Nepal Partners
This is a sample list and will need to be confirmed during
requirements confirmation with the stakeholders.
Access to system
The user of the application is expected to get some services
from the application without the need for external support.
This is a self-service component of the application.
- The user must be able to access the system using a defined
access methodology. The methodology may be the same or
different between the web and mobile components.
- The user must be able to request access to the system by
creating a profile which would involve submitting necessary
details
Recover Access
The system must provide the user with the necessary
functionality to gain access in case user credentials are lost.
The system must ensure that a user trying to gain access is
the correct user.
Create/Update Profile
- The system must allow the user to manage a user profile
which would allow limited functionality such as: updating
user address, email, contact details, credential recovery
details etc.
Language selection
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 4 of 35
User Oversight
Inventory Management
- The system must allow the user to specify language of the
interface (English or Nepali)
The application must allow user management and oversight
to ensure that the access to data and functionality is provided
to the designated users. This part of the application is an
administrative component of the system.
User Access Request Notification
- The system must provide notification that a user has
requested access with relevant details of the user.
User Verification
- The system must allow verification of the user requesting
access by way of multi-level approval chain.
User Approval
- The system must allow the user to be granted or denied
access with notification of cause of denial (if denied).
User Enable/Disable
- The system must allow the disabling and enabling of any
user based on need. Disabling the user ensures that the user
will not be able to access the system through any component
(the user may not circumvent this requirement by resetting
access credentials).
User Role Management
- The system must allow the allocation of roles to the user.
User Facility/Admin Div. Assignment
- The system must allow the assignment of one or more
facilities or other administrative divisions to the user.
The system must support the following:
GRN (Goods Receipt Note)
- GRN detail capture on receipt of goods
FEFO (First Expiry First Out)
- FEFO - when stock needs to be issued / transferred
Receive - account for expiry
- Receiving - automatic updating of inventory data on
receipt of stock
Batch management
- Ability to manage stock by batches
Stock Adjustment
- Automatic adjustment of stock when stock is received or
issued
- Manual Stock Adjustment of stock with reason after stock
taking (theft, expiry, damage, physical count etc.)
Stock Location Management
- Stock location management - location of stock in a facility
Stock Quarantine
- Ability to quarantine stock received until approval is
received from quality verification process
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 5 of 35
Inventory Status Reporting
Requisitions
Data Review
- Ability to quarantine existing stock if adverse information
regarding quality is received
Note: Desktop-based offline module for IM with ability to
sync data with eLMIS
The system must support data gathering of inventory status
from facilities. Inventory status data gathering must have the
option of both manual and automatic submission/collection.
Hierarchical levels - by location
- The system must allow the user to gather inventory data by
all administrative division hierarchies and by product.
By product
- The system must allow the user to view inventory data by
admin levels and by product.
Interval
- The system must allow data gathering at specified
intervals.
The system must provide the following functionality for the
requisition process
- The system must allow the configuration of a requisition
template.
- The system must allow authorized users to create
requisitions.
- The system must provide requisition calculation (provide
automatic calculation and validation to reduce errors and
data burden)
- The system must provide functionality to print the
requisition in specified formats for offline review
- The system must allow the submission of requisition/s
- The system must allow relevant users to authorize the
requisition
- The system allow the aggregation of requisitions for a
geographic/administrative area
- The system must allow the rejection of requisition/s
- The system must allow the approval of requisitions
- The system must allow the viewing/updating of
requisitions
- The system must allow emergency requisitions to support
the process of emergency ordering
- The system must allow the conversion of requisitions into
orders
Data submitted may be reviewed and edited either by the
user or notification by a higher role.
- The system must allow review of submitted data for certain
administrative divisions as specified.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 6 of 35
Data Approval /Data
Rejection
Inventory/Stock Status Data
Editing
Data Retention Rules for
Editing
Data Import from Other
System
Data Collation of Reported
and Imported Data
Configurability
- The system must allow the user submitting the data the
option to update current and past data as required and data
consistency should be ensured.
- The system must notify the user that data submitted by the
user has been rejected and needs to be reviewed.
Data submitted needs to be reviewed and either approved or
rejected by a higher role.
- The system must allow a higher role user the ability to
review the data submitted by a lower role in administrative
divisions.
- The system must allow a higher role user to approve the
data submitted by a lower role.
- The system must allow a higher role user to edit the data
submitted by a lower role and submit/approve it without
rejecting the data submitted by a lower role.
- The system must allow the rejection of data being
reviewed so that the user who submitted the data may
review and edit.
- The system must provide a notification to the user that
submitted data needs to be reviewed.
There are specific requirements towards the editing of
inventory/stock status data.
- Data for the specific administrative divisions can only be
edited for specified time periods in the past.
- Rejected data can be edited
There are specific requirements towards the editing of data.
- Data for the specific administrative divisions can only be
edited for specified time periods.
There are specific requirements towards the retention and
editing of data on the mobile component.
- The mobile component may only allow editing of currently
submitted data and up to a specified time period.
- The mobile component may only retain data up to a
specified interval.
The system must allow interoperability with other systems
and ability to process data imported.
- The system must allow the import of data using industry
standard formats (XML, CSV) to import data.
- The system must allow various data import mechanisms
(uploading, web-services).
The system must provide functionality to collate all the data
in the system.
- The system must be able to collate/aggregate data collected
through submission via the web and mobile components of
the system with the data that is imported into the system.
The system must provide a high degree of configurability
which will allow the application to adapt to changing needs
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 7 of 35
Data fields, Data sets and
Data Types
Reference Data Management
Types of Reference Data
- Facilities
- Districts
- Regions/Provinces
- Geo Regions
- Relations between locations
- Facility - Product Mapping
- Product - Category
Mapping
Master Data Management
of the system owner which ensures sustainability of the
application. Configurability also ensures that for certain
functionality the system owner does not need the services of
a development team. This will lower cost of ownership.
The system must provide functionality that allows the user
to add, update and disable data fields and data sets. It is
understood that there may be a core set of data fields/data
sets that cannot be disabled or updated. However, the system
must allow the addition of data fields and data sets to the
core set of data if such data sets exist.
- The system must allow the creation, updating and disabling
of data fields/data sets per a list of data types.
- The system must allow the addition of data fields/data sets
to specific functional areas of the application.
- The system must allow the removal of specific data
fields/data sets from certain functional areas of the
application.
Reference data is an essential part of the application and is
required to ensure data integrity and consistency and prevent
user error.
- The system must allow the user to add, update or disable
existing reference data.
- The system must allow the user to create new sets of
reference data as a data set.
- The system must allow the reference data to be created in a
hierarchical relationship.
- The system must ensure that reference data can have
relationships between sets of reference data.
- The system must allow the creation, updating and disabling
of relationships between sets of data.
(E.g. The solution will need to cater to possible future
administrative division reorganization.)
For LMIS systems, master data is essential and is used in a
similar fashion as reference data.
Types of Master Data
- Product master
- Product categories
- The system must allow the user to import the product
master as required.
Disable products
- The system must allow the user to add, update or disable
products in the product master.
Links products and categories
- The system must allow the user to create hierarchical and
direct (One-one, One-many) relationships between sets of
master data.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 8 of 35
Custom Reports
Data Visualization
Configure general stock
parameters (Min Max levels
by location) per Nepal
standards
Ability to set warnings when
specified thresholds are
crossed
Data Import Formats
As the system is used, there will be a need to create reports
that have not yet been specified.
- The system must allow the user to generate custom reports.
- The system must allow the user to create a report template
from sets of data.
- The system must allow the user the ability to assign which
roles can access this report.
- Refer Sample Reports in Annex 8
Data visualization allows a user to view data in pictorial or
graph format. Data analysis is presented visually to key
users who can then make decisions/recommendations. This
also allows identification of trends and patterns. As the
system is better used, there will be a need to create data
visualizations that will be specified later.
- The system must allow the user the ability to generate
custom data visualization.
- The system must allow the user to create data visualization
templates from sets of data.
- The system must allow the user the ability to assign roles
for accessing these templates.
- Refer Sample data visualization in Annex 9
For any LMIS the ability to configure and set specific rules
assists the user by taking away the burden of having to
remember all of the rules. This ensures data integrity and
supply chain awareness.
- The system must allow the user to set Authorized Stock
levels (minimum/maximum) by admin levels and by
products.
- The system must allow the user to set the authorized stock
levels as both numeric and percentage values.
- The system must allow the user to set an Emergency
Ordering Point by administrative levels and by products.
- The system should allow the user to update or disable any
such rules.
The system must communicate with the user using short and
meaningful messages and warnings. These messages and
warnings allow the user to take corrective or preventive
action.
- The system must provide meaningful error messages.
- The system must provide warnings when important/critical
thresholds are crossed.
- Warnings may need user confirmation
The system must allow the user to define data import
formats using the existing data fields and data sets.
- The data import format defined must have the option of
being defined as XML or XLS/XSLX or CSV.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 9 of 35
Data Collection Intervals
Data Editing Intervals
General
Input Validation
Notifications
Reminders
Task List
Messages to User
Branding
Disclaimers / Notices
The system must allow the user to define the intervals for
data collection by administrative levels and provide the
ability to send reminders.
The data collection method can be specified as both manual
and automatic.
The system must allow the setting intervals/periods for
which past data submitted can be edited.
The system shall validate input to ensure data quality.
- The system shall display text to the user notifying what
input is allowed.
- The system shall display relevant error messages when
input is erroneous.
The system must be able to send notifications to the user.
- Critical event requiring manual interference
- Event on calendar that requires user attention
-NOTE: This is just for user assistance to perform their task
better. At this moment, there is no requirement to link this to
any action in the system.
The system must allow the user to set reminders with short
messages by date and time. The system may also provide
reminders when scheduled activity will take place.
- The user may elect to receive notifications from the system
for these reminders.
- The system may provide reminders to users to ensure
inventory data is correct before it is collected for reporting
purposes.
The system must display a task list for specific roles. This
allows the user to understand what input is required from the
user end.
- List of users requesting access
- List of data needing review (for approval/rejection)
- Issues/Errors in the application
Messages to the user must be specific, short, and meaningful
and allow the user to take a corrective or preventive action.
The system must display proper branding of all identified
partners as required.
- The branding must follow rules of USAID
(https://www.usaid.gov/branding).
- The branding must follow any other rules of a partner.
The system must display disclaimers and notices as required.
- The system must display notices to the effect that the data
produced by the system is not officially endorsed by the US
Government. Text will be confirmed.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 10 of 35
Application Metrics
Standard Reporting (Data
Processing - Reports)
List of reports
- The disclaimer/notice may need to be displayed on the data
produced by the system as well i.e. on reports generated by
the system.
The system must provide functionality that displays system
metrics (sample below).
- System Access - the details of the users, IP addresses,
browser / app used, logon time etc.
- Errors, notifications, warnings by category
- Data imports (reports, master data etc.)
The system is expected to produce a standard set of reports
expected from an LMIS system.
- The reports should be available in XML, XSL/X and PDF
formats.
- The reports should be downloadable/exportable from the
system.
Following tentative lists of reports provides the synopsis
about the type of reports required. However, the actual
number of reports, their formats and details will need to be
explored and agreed explicitly with LMD during
requirements gathering and confirmation:
- Summary Reports for Consumption, AMC, MOS, and SoH
by SDPs, Districts, Regions and national level
- Detail reports for Consumption, AMC, MOS, and SoH for
each commodity, commodity group and/or range of selected
commodities by SDPs, Districts, Regions and national level
-Comparative reports for Consumption by time (Month,
Quarter, Trimester, and Half Yearly, yearly based on both
Nepali and AD Calendar) for selected levels of supply
chains, SDPs, Districts, Regions and national level
-Performance Reports about their reporting status including
filters for level of supply chains, date ranges, and reporting
type filtering
-Annual Data reports for each level of supply chain to
summarize their annual stock levels
- Informative Reports based on current data for stock
availability, near expiry, shipment delayed, stock
registration delayed etc.
-PPMR reports for FP commodities
-Monthly Consumption reporting compilation
-Warehouse specific reports
-Pipeline Reports
-Forecast and Quantification assistance reports
-Quality Control specific reports by status, batches, purchase
order, contract, and manufacturer
-Procurement specific reports by purchase order, contract,
manufacturer
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 11 of 35
GIS Overlay of reports
Reporting and Aggregation
Intervals
Data Processing - Standard
Data
Visualization/Dashboards
Samples of visualizations
Pipeline
LMIS Software
Interoperability
Constraints
Mobile Platform
Application Load
The samples and format of the reports expected from the
system are detailed in Annex 8
The system must allow the GIS overlay of data.
- The system must provide the GIS overlay for standard data
visualization.
- The system must provide the GIS overlay for custom data
visualization.
With the introduction of the system, sites using this system
will be able to report monthly while for other sites the data
reporting will continue to be on a quarterly basis.
- The system should be able to aggregate and display
reported data for sites reporting on monthly basis.
- The system should be able to aggregate and display
reported data for sites reporting on a quarterly basis.
List of expected visualizations
The list of data visualizations expected from the system are
as follows:
- The system must provide visualization based on the
indicators based on the level of supply chain.
- MOS
- Stock outs by storage site
- Consumption
- Reporting rates
- AMC
- SoH
- Expiries
- Data visualization is expected to be both graph
representation and choropleth maps.
The samples and format of the data visualization expected
from the system are detailed in Annex 9.
The solution must have the ability to capture shipment
information and produce pipeline reports. Refer sample
Pipeline report in Annex 8
System will need to be retired
- All paper based data will be entered directly into eLMIS.
- All retrospective data will be migrated to eLMIS in Phase1.
The system will need to interoperate with other information
systems in use locally (e.g. DHIS2) or planned later.
The system will work under certain constraints which will
ensure the proper functioning of the system and take into
account the local context.
The system must be able to work on Android version 4.4
and greater.
The application is expected to be able to serve large sets of
users.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 12 of 35
Initial load
Nepali Language
Multi Calendar Support
Nepal e-Government
Interoperability Framework
(NeGIF) Compliance
Data designation by Govt. of
Nepal
- The initial load may be 100 users (concurrent users may be
fewer).
- The application must be able to scale up to support 5,000
users (concurrent will be fewer.
- The application must be able to handle sudden loads at
specified intervals of time.
The initial load of the application is planned at 80
concurrent users that fit various roles listed. However, the
user population will not be evenly divided between the
different roles. E.g. there will be far more Data
Entry/Reporters that there will be Central Policy staff. But
the Central Policy staff may be generating data
visualizations etc., which are resource intensive while the
Data Entry / Reporter only submit information which is not
resource intensive.
When recommending the H/W and S/W required for the
application, this must be taken into account.
The system must provide support for the use of the Nepali
language for all users.
It should have provision for multi-calendar support, BS and
AD both calendars to begin with.
Nepal uses a localized lunar calendar (known as Bikram
Sambat, BS) as its official calendar. It is 56.7 years ahead of
the solar Gregorian calendar.
a.) Calendar Year: The new year begins in mid-April and is
divided into 12 months ranging from 29-32 days in a month.
b.) Nepali Fiscal Year: Nepalese fiscal year ranges from
start of fourth month in BS till end of third month of next
year in BS. Generally, it falls from July 16 to July 15 of
corresponding years.
c.) Gregorian calendar: Support for the regular Gregorian
calendar
The system should support the Nepali calendar for data
collection and reporting considering both Calendar and
Fiscal year. It should have provision to report based on
Nepali months, quarters, semi-annually and yearly for both
Nepali calendar and fiscal year.
The system must comply with the requirements of the Nepal
e-Government Framework (NeGIF).
The system must support the Nepal Government Enterprise
Architecture (Nepal GEA).
The data collected by this application has been designated as
Confidential by default, having access to authorized users
only.
- Despite data designation by GoN, all data transmitted and
stored by the system must be protected from intentional and
unintentional access and manipulation.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 13 of 35
Data Processing and Storage
Standards
- Data visibility is per user role based on level and roles.
- Publicly available data - LMD / DoHS/MoH can decide a
limited sets of reports or data to be publicly available on
their portal, to be pushed on a regular interval.
The system must meet specific requirements for data
processing and storage:
- The system must ensure that all deletes are logical only.
- Any relationships for data being deleted/disabled must be
preserved.
- For specific data sets a history of changes must be stored.
- Data (Reference/Master Data, stock status data) for mobile
component should be able to synchronize with the data of
record.
The system must conform/support various international
standards:
GS1
-GS1 standards will be used for product identification.
INN
- International Non-Proprietary Names will be used for
medicines.
Non-Functional Requirements
Auditability
Availability
Documentation
Auditability is a key component of the system.
- The system must store a history of access to and
manipulation of data including user names.
- The system must log key parameters of the system (user
access, IPs, usernames, GPS location, etc.).
The solution is required to be highly available.
- The solution must be available during GoN working hours.
- The solution must also be available during other hours for
Data Entry / Reporters and other data submission and
processing needs.
Comprehensive documentation will be required for this
solution. (As much documentation as can be made available,
may be provided during RFP responses). Documentation
required, but not limited to, is:
- Solution Architecture
- Deployment Architecture
- Technical documentation (Admin manuals, deployment
guides, DB manuals, user guides, maintenance manuals,
developer guides etc.)
- Training documentation
- Requirements Documentation (Use Cases, Non-Functional,
Test Cases, other details)
- Test plans, test documents and results
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 14 of 35
- Some documentation such as user manuals and training
material will be required in both English and Nepali
language.
Extensible
Reliability
Interoperability
Logging
Maintainability
Modular
The solution must be extensible partly using ability to create
and expose services. Solution code and APIs must be well
documented...
The supporting documentation must be detailed enough that
qualified developers can work on extending the application
functionality if required, with little to no support.
Fault Tolerant
The solution is expected to be fault tolerant by design and
implementation.
- The application by design should have no single point-offailure
- The application should isolate and contain faults and not
allow other parts of the application to be adversely affected.
- Documentation (reference, design, architecture) should be
provided to demonstrate that the solution is fault tolerant.
Since the application will be part of a growing ecosystem of
applications and functionality, it is imperative that the
solution be able to interoperate between various other
systems. The objective is to allow the uninterrupted flow of
information between disparate systems.
The system can have defined or definable interfaces/service
end-points that will provide the ability for other systems to
connect and provide data. Similarly, the ability to connect to
other service end points to obtain data should be provided.
Interoperability as a function should not need to be built
from scratch, but should be mostly achievable through
configuration and mapping.
- Documentation and other evidence must be provided in
support of this requirement.
The solution must be able to maintain detail logs of various
application parameters including but not limited to user
activity, IP addresses, browser types, GPS locations, OS
type etc.
The solution must maintainable with local/regional support.
The system should have high Mean Time Between Failures
and low Mean Time To Recovery.
The system must be shown to have a stable codebase with
proven usage (deployed with multiple clients for at least 18
months).
The solution must be modular and it must be demonstrated
that the modules can work independently and together as
required. Adding or enabling modules to work with each
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 15 of 35
Multilanguage Support
Performant
Scalability
Security
Other Application
Parameters
other should require little effort and provide seamless access
and functionality to the user.
The solution must provide support for at least 2 languages as
specified.
- English (US or UK)
- Nepali language support
The solution deployment should ensure that the solution is
performant and provides a good user experience.
- Page load time in web-interfaces not to exceed 3 seconds
- The solution architecture must ensure that throughput is
sufficient to handle peak loads.
- The solution must use low resources for the mobile
component.
The solution is planned to start from a small set of users and
then grow to a large set of users.
- The solution must be able to scale and support a large set
of users form a smaller set.
- The solution must be able to scale operations and handle
surges in data transmission and processing loads.
The solution must ensure that data in storage and during
transmission is secure from intentional and unintentional
interference and access.
- Must use Transport Layer Security (HTTPS) for web and
mobile component
- Mobile data must be secure on mobile device.
- The system must provide unwanted intrusion protection
(e.g. SQL Injection, Brute Force).
- The system must allow password expiry and password
renewal.
- The system must be able to meet government/national
standards for data security.
H/W Specifications for deployment platform
The solution must provide specifications of the hardware
that will be used for a deployment platform.
- The solution may be hosted on dedicated servers.
- The solution may be hosted in the cloud or on a Virtual
Private Cloud.
- Details may be tiered for user sizes and details provided
regarding concurrent support.
- The deployment platform will be decided in consultation
with GHSC-PSM, MoH and LMD.
- The deployment platform will be provided and is outside
the scope of this RFP
S/W Specifications of deployment platform
The solution must provide the specifications of the software
used the comprehensive solution.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 16 of 35
- Software used for the application (Application server,
RDBMS)
- Software used for the deployment platform (Operating
System, Web servers, Mobile platform etc.)
- Software for the deployment will be provided and is
outside the scope of the RFP.
Offline/Intermittent Connectivity Support
System (Specific components) should be able to perform
functions specified during intermittent or no internet
connectivity.
Support Mechanism
The offeror must provide and support mechanism for the
solution during the production period.
- The offeror must provide an SLA with options that detail
technical support for the application.
- The SLA and options should be accompanied with cost
details.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 17 of 35
B. Implementation, data migration and User Trainings:
In addition to the software product implementation (this includes specific configurations and
customizations to the system and all necessary steps for a successful Go-live), the vendor will
also ensure legacy data is successfully migrated to the new the selected vendor, will be
responsible for developing user manuals, participant and facilitator guides, imparting trainings
and providing software support. Vendor will second/place staff at LMD premises and in
geographical region(s) to support Phase1 implementation process. The solution will be
implemented in phases and each of the phases has its own requirements as described below.
The application will be primarily implemented at Central, Regional and District medical stores,
and the mobile applications will be used at last mile sites- Service Delivery Points (SDP). In
addition to the intervention approaches highlighted under Section I, part 1, this Sub-Task Order
(STO) will focus on the successful implementation of Phase 1.
Scale: 02 central sites, 05 regional sites, 15 districts and 30 health facilities. There may be some
variation during actual implementation i.e. 10% more or less sites.
Training and Capacity Building
The eLMIS implementation plan includes a commitment towards long term sustainability
through training activities, capacity building and continuous monitoring. This will be ensured
through continuous dialogues and consultations with all stakeholders during consultative
meetings and development of training plans. The vendor should have considerable experience
and experienced staff in assessing training needs, developing training programs and an
experienced and skilled training team e.g. Master Trainers.
20-25 master trainers will be trained from the Department of Health Services (DoHS) to impart
training and orientation of eLMIS. A total of 90 individuals will be trained on eLMIS reporting
in Phase1 from 15 districts of Mid-Western Region and 43 health managers from national, central
& regional stores and district stores will be oriented to review and analyze data using the eLMIS
mobile application and web-portal.
There will be need of curriculum development/revision, approval from MoH/NHTC and training
implementation in close coordination with LMD/NHTC
The offeror only needs to provide trainers. Costs for equipment, venues etc. do not need to be
factored into the response.
Training Activities
Training Needs Assessment
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 18 of 35
The purpose is to perform an analysis of staff competency. It shall assess, analyze and define the
staff training needs in all the areas of the eLMIS Operation and Management. This will provide
the basis for the training design and planning.
Key Activities
● Define and analyze staff competencye requirements based on competence appraisal and
employee’s requests
● Review competence through interviews/questionnaires, observations, group discussions,
and inputs from stakeholders.
● Define and document the competence gaps
● Collaborate with DoHS and National Health Training Center (NHTC) to identify ideal
training solutions to close the competence gaps.
● Define the specification of the training needs including training plans, objectives,
expected output, monitoring approach, constraints, training methods and targeted
curriculum.
● Document the training needs and review with users, technical, administrators.
Methods
● Questionnaires
● Pre-Qualification Assessments Tests, paper based and/or online based on tool
● Discussions with key stakeholders
● Gap Analysis
Key Output
● Training Needs Assessment Document
Training Design and Planning
The purpose is to design and plan the actions required to address the identified competence gaps
at the potential trainees and define the criteria for evaluating the training outcomes and
monitoring the training process.
Key Activities
● Define & document the constraints (timing & schedule, availability, resources)
● Define and document the timing methods (on-site and off-site courses & workshops, selftraining based on training tool)
● Design the training (objectives & requirements, training needs, trainees, training method
and content, schedules, resource requirements, material, criteria & methods to evaluate
training outcomes to measure satisfaction, knowledge acquisition, on-the-job
performance, management’s satisfaction, organizational impact and process)
● Document the training design, training material and plans and review with concerning
key stakeholders of DoHS.
Methods
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 19 of 35
● Discussions with key stakeholders
● Training Development Approaches
Key Outputs
● Training Material
● Training Schedule
● Overall Training Design and Planning Document
Training Implementation
The purpose is to execute training to address identified competence gaps. To ensure that the
expected training outcomes are achieved, quality assurance will be built into each of the eLMIS
trainings.
At the end of the training, an assessment will be organized to evaluate the skillset as post-training
assessment.
Key Activities
● Provide pre-training support and briefings
● Provide training to the selected trainees for eLMIS operation and management
● Provide training support (relevant tools, documentation and feedback on task
performance)
● Provide the end of training support (receive feedback information from trainees and
trainers, and provide feedback information to managers and personnel involved in the
training process)
● Build a "competency profile" of the new knowledge, skills and abilities acquired from
training
● Identify gap/weaknesses between the acquired and desired level of competency, identify
and prioritize competency gaps and develop continuous training enhancement.
● Document the training, and review with trainees and concerned stakeholders
Methods
● Classroom/Group based Trainings
● Workshops
● Drills and Assessments
Key Outputs
● Staff Training and Reports
● Skill set Certifications
● Training report
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 20 of 35
● Training feedback
Training Evaluation
The purpose of training evaluation is to confirm that the training objectives have been met.
Evaluation will include short term and long-term analysis. In the short term, LMD and NHTC
with support of GHSC-PSM will obtain trainee feedback information on the training methods,
resources used, knowledge and skills gained as a result of the training. In the long term, the
trainees’ job performance and productivity improvements can be monitored and evaluated. It can
be used as a feedback for training program improvements for future trainings.
Key Activities
● Data Collection, Analysis and Interpretation of the results with consideration of
specification of training needs, evaluation criteria and description of sources and methods
● Observations and discussions with key stakeholders of DoHS
● Recommendations for improvement
● Procedures for corrective actions
● Staff skills improvements and abilities observations
Methods
●
●
●
●
Evaluation Questionnaires
Workshops
Assessments
Drills
Key Output
● Training Evaluation Report
Sub Task Order 1-A: Deliverables
Deliverables
The deliverables are:
Deliverable 1: Development of Project Plan and Tool-Kit
The offeror shall outline its plan for implementation for the roll-out of the LMIS system, providing a
detailed project tool-kit which will provide the project plan, tools, and templates necessary to complete
the subsequent activities in this subcontract. The project plan, tools, and templates shall include details on
the Subcontractor’s planned mobilization; benchmarks for completion of the scope of work; timeline for
completion; roles and responsibilities of partners, stakeholders, and other resources; and plans for
feedback and communication. The project plan shall be submitted electronically in Microsoft Project or
Microsoft Excel format.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 21 of 35
Additionally, the Subcontractor shall develop a project tool-kit, including but not limited to the following
documents:
Project charter. The Subcontractor shall support the Contractor to develop a project charter
which will clearly explain the purpose of the LMIS system, and will outline key benchmarks,
milestones, and processes, in alignment with the project timeline, described above. The charter
shall be submitted in Microsoft Word, and shall be reviewed and approved by the Contractor,
based on concurrence from the national LMIS multi-stakeholder steering committee.
Change control governance process. The Subcontractor shall also develop and define a change
control governance process, outlining who makes decisions on bugs, priorities, and changes to the
system moving forward. The change control governance process shall also include terms of
reference for the change control committee. The process shall be submitted in Microsoft Word.
Roles and responsibilities matrix. The Subcontractor shall jointly develop with the Contractor a
roles and responsibilities matrix that will outline the scope of the Subcontractor’s work in
alignment with the project plan and charter, described above. The matrix shall be submitted
electronically in Microsoft Word or Microsoft Excel.
Bi-weekly status updates template. The Subcontractor shall create a template to provide the
Contractor with bi-weekly status updates. The report shall include information regarding progress
measured against the detailed project plan, updates on newly identified risks and mitigation
strategy (which will feed into the risk log), challenges encountered, and solutions to overcoming
identified challenges. The template shall be submitted electronically in Microsoft Word or
Microsoft PowerPoint.
Communications plan. The Subcontractor shall develop a plan for its communications throughout
the implementation of the subcontract, detailing its plan for engaging GHSC-PSM Nepal field
office staff. The communications plan shall be submitted electronically in Microsoft Word.
Release Management and Test plans template. The Subcontractor shall develop a structured plan
for software releases, including testing all components of System administration, configuration,
profiles, and all other functionality. The template shall be submitted electronically in Microsoft
Word or Microsoft Excel.
Test results template. The Subcontractor shall develop a template to report on the results of the
test plan, including features and functionality tested, variances, recommendations, and
stakeholder concurrence. The Subcontractor shall also detail how the testing results will be
analyzed and shared with key stakeholders. The template shall be submitted electronically in
Microsoft Word or Microsoft Excel.
User requirements template. The Subcontractor shall, in coordination with the Contractor,
develop a template to capture System system requirements from a variety of different
stakeholders, including MOH and GHSC-PSM Malawi staff. The template shall be submitted
electronically in Microsoft Word or Microsoft Excel.
Process flow template. The Subcontractor shall, in coordination with the Contractor, develop a
template to capture the key business processes for System from a variety of different
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 22 of 35
stakeholders, including MOH staff. The template shall be submitted electronically in Microsoft
Visio or Microsoft Word.
Training reports. The Subcontractor shall submit a 3-5 page training report for each training held
describing the purpose of the training, topics covered, training materials utilized, challenges
encountered, and lessons learned for future trainings. The reports shall be submitted in Microsoft
Word.
System issue tracking software and report template. The Subcontractor shall share the detailed
specifications of the software and a report template that will be used to track and capture system
bugs, new specifications, and change requests for the system as shall be reported during the user
acceptance testing (UAT) and post-go-live. The details of the system and report template shall be
submitted electronically in Microsoft Word, Microsoft Excel, or Microsoft PowerPoint.
User acceptance template: The Subcontractor shall develop a template to document user sign-off
on key functionality and acceptance of the system. The template shall be submitted electronically
in Microsoft Word or Microsoft Excel.
Deliverable 2:
-
-
Legacy data collection and cleaning
Configure Solution
o All functionality detailed in the functions requirements section of the system
requirements document from Deliverable 1(e.g. user self-service, user management,
reference data management, master data management, reports, data visualizations,
data collection/entry, role-based access control, role based data flow etc.)
Migrate legacy data
Setup the data import mechanism
Application Testing – Unit testing and testing with relevant stakeholders
Bug Resolution – Resolve all bugs and issues
Deliverable 3:
-
Ensure that platform to conduct UAT is prepared
Kick off preparation of final deployment platform
Ensure preparation of rollout coordination
Service level agreement for support and processes to be finalized
Deliverable 4:
-
Finalize Training plan
Conduct User Acceptance Testing – in leadership of GoN (e.g. LMD and other relevant
stakeholders)
Bug resolution – Resolve all bugs and issues
Training documentation finalized and ready
User Acceptance Testing complete and signoff obtained
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 23 of 35
Deliverable 5:
-
Conduct trainings of users and of trainers
Structure to provide post Go-Live user support ready and tested
Post go-live support processes explained to users
Deployment platform ready
Deliverable 6:
-
Detailed application documentation ready (including but not limited to)
o System Design Document
o System Requirements Specification
o User manual
o Application Administration Manual
o Database Administration Manual
o Deployment Manual
▪ Deployment platform configuration
▪ Application
▪ Database
o Developer manual
o Troubleshooting guide
Deliverable 7:
-
Application deployed in production environment
Support team live
Cutover from any existing applications
Application Go-Live
Illustrative Deliverables Schedule: This schedule will be adjusted, as appropriate, based on
discussions with the selected vendor: (Note: Some activities and tasks are expected to run in parallel
across deliverables)
DELIVERABLES
Deliverable 1
Project Charter
Roles and Responsibilities
Reporting templates
Project plan
Cutover plan
Rollout plan
Support plan
Process mapping
Finalized requirements
TIMELINE
21-Jul-17
21-Jul-17
21-Jul-17
21-Jul-17
21-Jul-17
21-Jul-17
21-Jul-17
21-Jul-17
28-Jul-17
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 24 of 35
Deliverable 2
Legacy Data Collection and Cleaning
Configure solution
Application Testing
Bug resolution
Migrate legacy data
Setup and Test Data Import Mechanism
Deliverable 3
UAT Platform prep
Deployment Platform prep
Rollout Prep
Support Service Level Agreement and
Process
Deliverable 4
Training plan
User Acceptance Testing
Bug resolution
Training documents ready
UAT Signoff
Deliverable 5
Support Structure Ready
Conduct Training
Deployment Platform ready
Deliverable 6
Detailed Application documentation
submitted
Deliverable 7
Deployed in live environment
Cutover from existing system
Support Team Live
Project Reports
4-Aug-17
18-Aug-17
25-Aug-17
1-Sep-17
1-Sep-17
1-Sep-17
8-Sep-17
8-Sep-17
8-Sep-17
8-Sep-17
1-Sep-17
8-Sep-17
15-Sep-17
15-Sep-17
15-Sep-17
15-Sep-17
15-Sep-17
15-Sep-17
22-Sep-17
22-Sep-17
22-Sep-17
22-Sep-17
Weekly (Friday)
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 25 of 35
I.B Sub-Task Order 1-B: Operations Support and Maintenance—Online IMS
Background
In 2016, UNICEF developed an online Inventory Management System (IMS) to track Expanded
Programme on Immunization (EPI) vaccine stocks at central and regional medical stores in
coordination with the Child Health and Logistic Management Divisions of the Nepal Department of
Health Services (DoHS), and it is now in use at 65 of Nepal’s 75 districts. Additionally, the system
has been expanded to include health commodities beyond vaccines. The system is used by LMD to
track batch and expiry of health commodities at central, regional and district levels. Phase 1 scope
includes continued support of this system. Online IMS will remain operational until phase-2 of the
project. The system has the inventory data of health commodities of 2 central, 5 regional and 75
district stores. All data will be migrated to eLMIS periodically of all central, regional and district
medical stores until phase-2 go-live.
Scope of Work
This system will need to be supported to ensure that it continues to function smoothly. Application
and user issues will need to be collected and addressed per specified Service Level Agreement to
ensure minimum disruption. Support will be required during normal working hours as specified by
Government of Nepal. The number of facilities and users that need to be supported are 2 Central
facilities, 5 Regional Medical Stores and 75 Districts. A user base of approximately 110 users with
various roles will need to be supported.
The Operations and Support will continue as long as the system is in use – until it is replaced with
another system or retired.
Services to be provided
Services provided will ensure:
-
Continued smooth functioning at normal levels (Normal levels to be agreed upon)
Minimum disruption in functioning and restoration to normal levels of function
A ticketing system for reporting and tracking issues till closing
Support for users and issue resolution tracking
Adherence to Service Level Agreement
Support is available during user working hours as specified for GoN
Resolve/fixing systems bugs
Administrative support for configuration of system
Services provided do NOT include:
-
Making enhancements to the system
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 26 of 35
-
Defects caused by alterations, amendments or any other changes not agreed to by GHSC-PSM
and LMD MoH GoN
Service
Parameters
Change
Control
Description
-
Warranty
-
Response
Criteria
-
Prioritization
-
Escalation
Documentatio
n
Reporting
All requests for changes to the system and supporting services, by LMD or
GHSC-PSM, must be recorded in detail
Formal agreement is required to demonstrate acceptance and agreement or
rejection of any changes
Offeror may respond with a proposal in writing with suggestions for bug
resolution and system improvement, with details of cost and timelines. The
proposal will need agreement and approval with GHSC-PSM and LMD. If
GHSC-PSM and LMD do not respond to any proposal within 4 business
days, the proposal is considered rejected.
All bug fixes etc. must be properly tested and warrantied as free from
defects
Hours of Coverage
The hours of coverage are from 10: AM to 5:00PM Nepal Standard Time
(NST) Sunday to Friday. Weekends and national holidays are excluded.
Issue acknowledgement with ticket number is required
Issue acknowledgement response times and communication channel are
required
Time threshold for acknowledgement of issues during hours of coverage
Categorization of priorities for issues is required (e.g. Critical, Important,
Normal) to ensure impact and urgency are taken into consideration
Responses and resolution times are required according to category
-
Issue escalation process is required
Issue escalation may take place according to category
Issue escalation may be automated per the ticketing system according to
agreed-upon time intervals
For bug fixes and configuration changes, relevant documentation will need to
be updated
Weekly/Monthly report on number and categories of issues, time taken to
respond, status of issues, users affected
Application Environment Specification
NAME
PROCESSOR NAME
VENDOR ID
PROCESSOR SPEED (MHZ)
PROCESSOR NAME
VENDOR ID
PROCESSOR SPEED (MHZ)
VALUE
Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
Genuine Intel
1999.787
Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
Genuine Intel
1999.787
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 27 of 35
TOTAL MEMORY
FREE MEMORY
TOTAL SWAP MEMORY
FREE SWAP MEMORY
OPERATING SYSTEM
APACHE 2.4.25
DIRECTADMIN 1.51.3
EXIM 4.89
MARIADB 5.5.41
NAMED 9.9.4
SSHD
DOVECOT 2.2.27 (C0F36B0)
PURE-FTPD 1.0.43
PHP 5.6.30
8011076 kB
4778704 kB
4095996 kB
4074644 kB
CentOS 7.0 64-Bit
Running
Running
Running
Running
Running
Running
Running
Running
Installed
Sub Task Order 1-B: Deliverables
Since STO 1-B is for Operations Support and Maintenance, it will require monthly reports
summarizing both issues and requests for configuration etc.
Deliverables
-
Monthly report with details such as issues logged, issue category, response times, issues
statuses
Monthly report with details such as requests for configuration changes, administrative
interventions, request date, approval date (if required), time to resolve, current status.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 28 of 35
PROPOSAL REQUIREMENTS:
The offeror shall submit a proposal including the information below:
1. Technical approach: Technical Approach, Methodology and Detailed Work Plan. This part
shall be between 15 and 20 pages long, but may not exceed 20 pages. This section should include
offeror’s response to both section 2.I.A & 2.I.B.
2. Management and Key Personnel This part shall include the project management approach,
organization chart and project plan with brief summaries of key personnel. CVs for key
personnel may be included in an annex to the technical proposal and will not count against
the page limit. Preference shall be given to proposals with technically qualified personnel
with application area degrees and supporting certifications. Brief travel within Nepal may be
required for all personnel. At a minimum, offerors are expected to provide candidates for key
personnel as outlined below, and may include additional personnel if deemed necessary in
support of their technical implementation and management approach. This section can be
between 5-7 pages, and shall not exceed 7 pages.
Title
Core Responsibility
Qualifications and Experience
Sub Task Order 1-A
Project Manager
(Location :
Kathmandu)
- Overall ownership of the Project
and main channel of
communication between the
PSM/LMD and Vendor Team.
- Monitor and review project
progress and advise status to
stakeholders through the meetings
and reporting processes;
- In conjunction with the PSM
eLMIS team, develop and maintain
the goals and objectives of the
Project and Project Management
Plan
- Accountable for the adherence to
quality and standards guidelines;
- Assist in coordinating the user
acceptance testing processes;
- Supervise and monitor the project
progress and review the
effectiveness of project execution
performed by the Vendor resources;
- Monitors and ensures the quality of
project deliverables;
- Arrange all regular project status
- MCA / BE/B TECH/ MBA (IT)/other
relevant Post Graduation degree in
IT.
- Good communication and inter
personal skills
- Fluency in written and spoken
English
- Excellent IT Project Management
skills with 5+ years’ experience on
managing large IT projects,
preferably on Health and/or
Pharmaceutical Supply chain
management domains.
- Extensive experience on managing IT
projects for government clients
- System level and holistic
understanding of Technical concepts
- Experience of project management of
at least 3-5 IT turnkey projects on
COTS Software implementation for
web and mobile devices.
- Prior experience with project
implementation in variety of remote
and difficult geographical terrains.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 29 of 35
Supply chain
Business
Analyst
-
(Location :
Kathmandu)
-
-
-
-
-
Software
Developer
-
(Location :
Vendor offices
with travel to
Kathmandu as
needed)
-
-
meetings and change management
meetings;
Ensures client management
Signatory to various project
documents from Vendor side.
SME in the cross section of supply
chain management, warehouse
management and leveraging the
application to meet the needs.
Impart the ideas on the best
practices and lesson learnt
managing Logistics Information
Management and Supply Chain
operational automation across the
globe
Capture and manage business
requirements in collaboration with
project managers, developers and
other stakeholders.
Conduct system study & prepare
SRS for system change
management, configuration and
implementation.
Prepare system implementation
document aligned with the overall
milestones and objectives set by
PSM eLMIS team.
Lead software testing and
deployment management.
Assist Project Manager for the
change management and provide
necessary recommendation for the
process analysis.
Write code/configure application to
ensure software functionalities as
per the requirement specifications.
Research and examine existing
functionalities of the proposed
solution to ensure its aligned with
the requirement specification for
eLMIS
Refine and fine tune system
functionalities for optimal
performance for eLMIS
Setup and configure the system as
per the required specifications for
eLMIS.
- Preferable Certification in project
management skill i.e. PMP or
equivalent
- MCA / MIT/ Other relevant Post
Graduation degree in IT.
- Must have supply chain management
experience of public sector health
commodities preferably in Nepal
- Good communications and inter
personal skills and fluency in written
and spoken English
- At least 5+ years’ experience as
Business Analyst/ System Analyst or
Solution Architect on managing large
IT projects, preferably on Health
and/or Pharmaceutical Supply chain
management domains.
- Extensive experience on IT projects
for government clients
- System level and holistic
understanding of Technical concepts
- Experience of Business Analysis and
Change Management in at least 2 IT
turnkey projects on COTS Software
implementation for web and mobile
devices.
- Prior experience with project
implementation in variety of remote
and difficult geographical terrains.
- Preferred knowledge of Nepali
language
- Bachelors in IT related degree.
- Good communications and inter
personal skills and fluency in written
and spoken English
- 3 years of experience of writing codes
for IT projects preferably in COTS
software.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 30 of 35
- Liaise with documentation team for
software and operating manuals
Quality
Assurance
Specialist
(Location :
Vendor offices
with travel to
Kathmandu as
needed)
Documentation
(Location :
Vendor offices
with travel to
Kathmandu as
needed)
Trainer
(Location :
Kathmandu)
- Frequently a cross between
developers and SC business analyst.
- Duties are shared with other
functions such as support.
- Prepare Test Plan, Test Scenarios,
Test Cases
- Prepare Test Bed and Test Data
- Prepare and take sign-off on
Acceptance Criteria
- Execute UAT and take final signoff
- Execute OAT and take final signoff
- Publish test metrics to show
health/status
- Preserve Test Results
- Prepare and execute non-functional
tests
- Maintain Traceability Matrix
- Will also act as a trainer
- Determine the needs of end users of
technical documentation.
- Plan, develop, organize and write
user manuals.
- Prepare documents in explanatory
styles for multiple audiences
- Use photographs, drawings,
diagrams and charts that increase
users’ understanding.
- Develop the technical documents,
user manuals, trainer guide and
participants’ guides
- Carry out Training needs
assessments
- Design training modules on basic
training and specific trainings
Conduct training to all users as
- B.E./ B Tech./MCA or other IT
related degree
- Preferably have supply chain
management experience of public
sector health commodities in Nepal
- 3+ years of experience in IT software
testing required with an emphasis on
certifying web-based applications and
mobile applications.
- Strong understanding of the QA best
practices.
- Ability to coordinate review sessions,
investigate issues, research and
implement process and testing
methods
- Desirable Knowledge of Test
Automation Tool
- Bachelor Degree, preferably in IT or
communication background.
- Should have supply chain
management experience of public
sector health commodities in Nepal
- Basic knowledge of Software
Development Life Cycle.
- Strong written and verbal
communication skills.
- Worked in a similar capacity for
preferably 4+ years
- Extensive exposure to government
projects
- Proficiency in MS Office and
technical drawing tools like MS
Visio.
- Should have prior experience in
curriculum development and
imparting trainings
- Bachelor Degree, preferably in IT or
communication background.
- Should have supply chain
management experience of public
sector health commodities in Nepal
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 31 of 35
needed
Helpdesk
Support
(Location :
Kathmandu)
LMIS Officers
(Location :
Posted at
specific
locations in
Nepal)
- Provide first level contact and
convey resolutions to customer
issues
- Properly escalate unresolved
queries to the next level of support
as required
- Track, route and redirect problems
to correct resources
- Update support data and produce
activity reports
- Walk customers through problem
solving process
- Follow up with customers, provide
feedback and see problems through
to resolution
- Utilize excellent customer service
skills and exceed customers’
expectations
- Ensure proper recording,
documentation and closure
- Preserve and grow your knowledge
of help desk procedures, products
and services
- Duty station will be LMD,
Kathmandu
- Reviews data entered to ensure
completeness and accuracy
- Review reported data to ensure the
quality and liaise with concerned if
there is any anomaly in the
reporting and fix it
- Run reports after every reporting
period to verify results and review
data for deficiencies or errors,
correct any incompatibilities if
possible and check output
- Strong written and verbal
communication skills.
- Worked in a similar capacity for
preferably 4+ years
- Extensive exposure to government
projects
- Proficiency in MS Office and
technical drawing tools like MS
Visio.
- Should have prior experience in
conduction trainings
- Proven working experience in
providing help desk support
- Preferably have supply chain
management experience of public
sector health commodities in Nepal
- Proficiency in English and Nepali.
- Working experience as Helpdesk
Support for at least 1+ years.
- Working knowledge of help desk
software, databases and remote
control
- Strong client-facing and
communication skills
- Advanced troubleshooting and multitasking skills
- Customer service orientation
- Master’s degree in IT, MBA or
supply chain or related degree
- Minimum 3 years of practical
experience in Information systems,
logistics, warehouse management,
and health information systems
- Technical expertise regarding
information systems
- Strong knowledge of and experience
with reporting
- Strong analytical skills with the
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 32 of 35
- Identify and rectify issues in eLMIS
due to data import/entry over the
time
- Assist in communicating issues to
development team from users
- Prepare list HF’s for revision and
addition/deletion in eLMIS
- Follow up with RMS, districts and
SDPs for data entry in eLMIS.
Contact relevant trained
operator/storekeeper to ensure
logistics data reported timely.
- Provide support to eLMIS data
entry personnel for any issues
related to hardware and software
arises to report
- Perform consumption data quality
check at various levels
- Perform Data Validation at various
levels and work with M&E team
- Support eLMIS trainings and OJTs
- Duty station will be at locations to
be finalized in conjunction with
LMD.
Sub Task Order 1-B
Support
- Manage a helpdesk providing
technical support to end users
Manager
- Properly prioritize requests to
maintain support
Develop escalation processes to
(Location :
ensure complex issues are handled
Kathmandu)
correctly
- Remain responsible for tickets and
to close out tickets in a timely
manner
- Evaluate results and recommends
changes affecting short-term project
growth and success
Support
- Provide first level contact and
Personnel
convey resolutions to customer
issues
(Location
: - Properly escalate unresolved
Kathmandu)
queries to the next level of support
as required
- Track, route and redirect problems
to correct resources
- Update support data and produce
-
-
ability to collect, organize, analyze,
and disseminate significant amounts
of information with attention to detail
and accuracy
Willingness to travel to designated or
requested areas of the concerned
province;
Proficiency in English and Nepali
required;
Demonstrated written and verbal
communication skills;
Attention to detail, assertiveness, and
commitment to results,
Excellent computer skills with
Microsoft Office and Internet
- Bachelor's Degree or higher
- 3-5 years’ experience in IT Service
desk environment
- Excellent communication and
leadership skills
- Experience managing service desk
operations
- Proven working experience in
providing help desk support
- Preferably have supply chain
management experience of public
sector health commodities in Nepal
- Proficiency in English and Nepali.
- Working experience as Helpdesk
Support for at least 1+ years.
- Working knowledge of help desk
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 33 of 35
Software
Developer/s
(Location :
Vendor offices
with travel to
Kathmandu as
needed)
Documentation/
QA
(Location :
Vendor offices
with travel to
Kathmandu as
needed)
activity reports
- Walk end-user through problem
solving process
- Follow up with users, provide
feedback and see problems through
to resolution
- Ensure proper recording,
documentation and closure
- Write code/configure application to
ensure software functionalities as
per the requirement specifications.
- Fix bugs, refine, configuration
management and fine tune system
functionalities for optimal
performance of online IMS
- Liaise with documentation team for
software and operating manuals
Update documentation, if needed
and ensure bug free application
software, databases and remote
control
- Strong client-facing and
communication skills
- Advanced troubleshooting and multitasking skills
- Customer service orientation
- Bachelors in IT related degree.
- Good communications and inter
personal skills and fluency in written
and spoken English
- 3 years of experience of writing codes
for IT projects.
- Bachelor Degree, preferably in IT or
communication background.
- Should have supply chain
management experience of public
sector health commodities in Nepal
- Basic knowledge of Software
Development Life Cycle.
- Strong written and verbal
communication skills.
- Worked in a similar capacity for
preferably 4+ years
- Extensive exposure to government
projects
- Proficiency in MS Office and
technical drawing tools like MS
Visio.
Should have prior experience in
curriculum development and
imparting trainings
3. Corporate Capabilities, Experience, and Past Performance For the purposes of STO 1,
offerors do not need to list additional past performance reference that are different from the
IQS. Offerors must include a detailed narrative demonstrating their corporate capabilities,
past experiences, and specific technical experience in implementing the technical
approach/methodology and the detailed work plan in response to the technical SOW for both
STO 1-A & 1-B. Offerors will be scored on demonstrated ability as outlined in STO 1 A &
B.
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 34 of 35
4. Cost proposal and payment schedule: The cost proposal is used to determine which
proposals represent the best value and serves as a basis of negotiation before award of a
subcontract. The ancitipated total value for STO 1 A & B is not to exceed $700,000,
Chemonics ancipate offerors to provide competitive cost proposals, and reserves the right to
alter the ceiling of the STO.
The price of the subcontract to be awarded will be an all-inclusive fixed price. No profit,
fees, taxes, or additional costs can be added after award. Nevertheless, for the purpose of the
proposal, offerors must provide a detailed budget showing major line items, e.g. salaries,
allowances, travel costs, other direct costs, indirect rates, etc., as well as individual line items,
e.g. salaries or rates for individuals, different types of allowances, rent, utilities, insurance,
etc. Offers must show unit prices, quantities, and total price. All items and services must be
clearly labeled and included in the total offered price. All cost information must be expressed
in United States Dollars (USD). See Annex 4 for a sample cost structure.
Because GHSC-PSM project in Nepal is a USAID funded project and is implemented under a
bilateral agreement between the Nepal and the U.S. Government, offerors must not include
VAT and customs duties in their cost proposal.
The cost proposal shall also include a budget narrative that explains the basis for the estimate
of every cost element or line item. Supporting information must be provided in sufficient
detail to allow for a complete analysis of each cost element or line item. Chemonics reserves
the right to request additional cost information if the evaluation committee has concerns of
the reasonableness, realism, or completeness of an offeror’s proposed cost.
If it is an offeror’s regular practice to budget indirect rates, e.g. overhead, fringe, G&A,
administrative, or other rate, Offerors must explain the rates and the rates’ base of application
in the budget narrative. Chemonics reserves the right to request additional information to
substantiate an Offeror’s indirect rates.
Under no circumstances may cost information be included in the technical proposal. No cost
information or any prices, whether for deliverables or line items, may be included in the
technical proposal. Cost information must only be shown in the cost proposal.
5. Evaluation and Basis for Award
This RFP will use the tradeoff process to determine best value. That means that each proposal
will be evaluated and scored against the evaluation criteria and evaluation sub-criteria, which
are stated in the IQS solicication evaluation table. Cost proposals are not assigned points, but
for overall evaluation purposes of this RFP, technical evaluation factors other than cost, when
combined, will outweigh cost. The cost volume will be considered for reasonability and
PART.FT.038, Rev.002, 5/7/2014
Request for Sub-Task Order Proposal No 001
IQS No. 001
Page 35 of 35
allowability. If technical scores are determined to be equal or nearly equal, only then cost
will become the determining factor
The proposal shall be dully signed by an authorized representative of the company and 1 printed
copy should be delivered at [email protected] no later than 9:00 AM EST, May
29th, 2017.
Global Health Supply Chain – Procurement and Supply Management (GHSC-PSM) project reserves
the right to reject task order proposals and this does not constitute a guarantee of a TO being issued.
Offeror(s) further understand that all costs associated with the preparation of the application are at
the expense of the applicant.
PART.FT.038, Rev.002, 5/7/2014