BIDS AND AWARDS COMMITTEE FOR GOODS AND SERVICES

(BAC4G&S)

 

Supplemental Bid Bulletin No. 2

 

PROCUREMENT OF THE DEPARTMENT OF INFORMATION AND COMMUNICATIONS TECHNOLOGY MOBILE OPERATIONS VEHICLE FOR EMERGENCY (MOVE) HUB AND MOVE DISPATCH OF THE GOVERNMENT EMERGENCY COMMUNICATIONS SYSTEM (GECS) PROJECT

 

Bid Reference No.:  BAC4G&S-2018-003

 

Please be advised of the changes in the schedule of the Submission and Opening of Bids for this project:

ACTIVITY PREVIOUS SCHEDULE REVISED SCHEDULE
Submission of Bids 18 October 2018

12 Noon

19 October 2018

9AM

Opening of Bids 18 October 2018

1:30PM

19 October 2018

10AM

 

After considering the queries, clarifications, recommendations and suggestions, the BAC4G&S hereby decides to include, revise, amend, delete and/or adapt the following provisions:

NO. QUERY BAC4G&S RESPONSE
1 Invitation to bid (under description of ABC) Procurement of the Department of Information and Communications Technology Mobile Operations vehicle for Emergency (MOVE) Hub and Move Dispatch of the Government Emergency Communications System (GECS) Project.:

 

The Description of the bid with an ABC of PhP 192,150,000.00 is for MOVE Dispatch only in Page 4. However, on page 65, it says the project is composed of 3 major components: (1) MOVE Hub and MOVE Dispatch, (2) DRMIS, (3) Capacity Development and Information Campaign. Can you please clarify what is the scope of the GECS project for the appropriate budget (ABC as there seems to be a misalignment of the requirements mentioned in the bid documents.

This bid is only for the MOVE Hub and MOVE Dispatch.
2 Do you have an overall solution architecture envisioning all the connectivities between the sub systems, network elements , etc.? No.
3 5.15., page 72

 

At least two (2) pairs of IP Radio:

 

Please clarify why 24.05-24.25GHz is specified for the IP Radio. This frequency band is defined for use by automobile radar rather than communications systems and usage of this band is planned to be phased out by 2022 in both Europe and US.

(http://e2e.ti.com/blogs_/b/behind_the_wheel/archive/2017/10/25/why-are-automotive-radar-systems-moving-from-24ghz-to-77ghz).

 

This frequency range is NOT normally used for backhaul transmission. it would be more relevant to refer to ITU-R F.748-4 Annex 1/CEPT ERC 13-02 E which defines 24.5-26.5 for the IP Radio

 

(http://www.etsi.org/deliver/etsi_en/302200_302299/3022170202/01.03.01_40/en_3022170202v010301o.pdf)

Frequencies shall be provided by the end user.
4 5.15., page 72

 

Where does DICT plan to deploy and terminate these IP Radio and why 2 pairs? can you please provide the network topology for these 2 pairs of IP Radio?

Point-to-point topology
5 5.15., page 72

 

AT least two (2) pairs of IP Radio:

 

Considering the operating frequency stated in the ToR is NOT typically used for transmission backhaul but rather for automotive radar, can we request for the new dimensioning parameters (i.e. frequency band, maximum distance, channel bandwidth, throughput, site coordinates, etc.) in order to come up with the required BoQ?

– Frequency shall be provided by the end user.

– 10km minimum distance.

– 1Gbps minimum throughput.

 

This is a deployable system. site coordinates are variable.

6 5.1.5., page 72

 

Data Collection and Analytics System:

 

Will this form part if the DRMIS platform? if yes, is this part of the GECS or a separate tender?

DRMIS is part of GECS Project but is on a different bid from GECS MOVE.
7 5.1.5., page 72

 

Integrated Communications System One (1) unit of mobile Very Small Aperture Terminal (VSAT) See attached Annex 1 below for details

 

Where does DICT plan to deploy and terminate this VSAT?

One (1) mounted on top of the MOVE Hub.
8 5.1.5.

 

10 Radio units of Ad Hoc Network (Mobile, Flying and Wireless)

 

Can you please elaborate more on how the Ad Hoc network will be used in the context of emergency communications systems? What are the use cases?

 

Based on IEEE, an Ad Hoc Network is commonly referred to as IEEE 802.11 standard or wireless LAN.

 

In a typical emergency situation, every second counts. It’s critical that emergency services can respond quickly an have the right information to rapidly assess the situation and take action. Using wireless LAN for this purpose may not be as efficient, reliable and robust compared to a rapidly deployable LTE network. LTE networks enables real time video and broadband data services that greatly enhance the situational awareness for first responders. LTE opens up a new vista of communications possibilities for rescue missions and disaster recovery situations. It can also enhance the day-to-day operational efficiency of public safety agencies with new applications for surveillance, real time database access and remote medical assistance. Below are the applications and services that can be provided by a rapidly deployable LTE network

1.) Group communication (MC PTT) including push to video.

2.) Real-time video

3.) Database lookup and reporting

4.) Remote monitoring

5.) Location and Mapping

6.) Control room applications

Ad hoc may be commonly referred to as wireless LAN. but there are other technologies that can be used as ad hoc. it is indicated in the TOR that several technologies can be used. such as Radio over IP, MANET, or LTE. these are based on the proofs of concept provided by other companies. one of which is the deployable LTE. i would recommend provision of “relay/repeater” stations that work as “ad hoc” if you will be using deployable LTE.
9 5.1.5., page 72

 

Must have dynamic and Adaptive routing protocols (position-based, mesh network, self-healing, and self-forming):

 

Are all these 10 radio units of Ad Hoc network to be configured as a mesh network? What technology are you trying to envision with self-healing solution? If point to point transmission is used, self-healing is not supported.

Yes. all units must be capable of mesh network.
10 5.1.5., page 73

 

Adaptable to frequency adjustment within (frequency allocation to be determined):

5.1.5.3.3.2.1 VHF 30- 300MHz

5.1.5.3.3.2.2 UHF 300-3000MHz

5.1.5.3.3.2.3 SHF 3-30GHz

5.1.5.3.3.2.5 Wi-Fi ISM 2.4GHz, 5.8GHz

 

These frequency bands mentioned herein are provided by specific radio technologies and are used for different applications. What are the applications and services planned to be used by these frequencies? what are the use cases? Can you please specify the use case fort EHF 30-300GHz?

Frequency allocations is determined by what kind of network you’re going to propose as ad hoc.
we require adaptable frequency adjustment in reference to whatever the frequency assignment shall be provided by NTC based on the proposed ad hoc technology.
11 5.1.5, page 73

 

Transmission: Either any of the following: (1) Radio over IP, (2) MANET or (3) LTE (Data, IP-based, web-based applications):

 

Does this pertain to the connectivity to be used by the Ad Hoc network? Transmission or connectivity to where?

 

What is the radio technology for (1) RoIP and (2) MANET? IEEE 802.11 (Multi-hop)?

 

For LTE deployable solution, the frequency spectrum band for PPDR (Public Protection and Disaster Relief) is the country specific. Typically, below are the LTE bands that used PPDR

-FDD B1, B3, B4, B7, B25, B14, B28-R3

-TDD B38, B40, B41

Yes, ad hoc shall be used as primary connectivity between the operations hub to and from the dispatch unit.
12 5.1.5., page 73

 

Must have at least 12 independent voice channels separated from data channels

 

What is the use case for this requirement on the context of an Ad Hoc network or LTE network? Can we interpret this as the requirement of MC PTT on top of LTE network?

The independent voice channels must be separately configured in case data channels fail.

MCPTT is part of the LTE technology as of 2016.

13 5.1.5., page 73

 

Minimum Number of Hops/Nodes :8 (+2 for Hub & Dispatch nodes)

 

Can you please elaborate more on this requirement?

Nodes/hops play a relay/repeater role in the ad hoc network. At 1km effective distance, the network is expected to have extended coverage of at least 10km. lesser on a mesh topology.
14 5.1.5., page 73

 

Built-in Position Location Information system

 

What is the use case for this requirement on the context of an Ad Hoc network or LTE network? Can we interpret this as the requirement of MC PTT on top of LTE network?

Use case is for communications. MCPTT is part of the LTE technology as of 2016.
15 5.1.5., page 73

 

Built-in video management software

 

What is the use case for this requirement on the context of an Ad Hoc network or LTE network? Can we interpret this as the requirement of VMS (Video Management System) on top of LTE network? Is it  intended to provide visual coverage within the nearby area where the MOVE Hub is located or disaster hit area for situation awareness?

Yes, MOVE Dispatch location and visual coverage included.
16 5.1.5., page 73

 

Built-in H.264 video encoder

 

What is the use case for this requirement on the context of an Ad Hoc network or LTE network? Can we interpret this as the requirement of VMS (Video Management System) on top of LTE network? Is it  intended to provide visual coverage within the nearby area where the MOVE Hub is located or disaster hit area for situation awareness?

yes. MOVE Dispatch location and visual coverage included.
17 5.1.5., page 73

 

Able to connect to UAV as one of the hops/nodes

 

What is the use case for this requirement on the context of an Ad Hoc network?

To extend network coverage in case of inaccessible terrain.
18 5.1.5., page 73

 

Protection at IP68 standard:

 

IP68 means the unit can be dropped into a body of water and guarantees protection of up to 1.5m deep for half an hour. Is this the intention of this requirement?

Yes.
19 5.1.5., page 73

 

One (1) unit of fiber optic infrastructure interface

 

Can you please elaborate more on this requirement? What is the use case for this requirement.

This pertains to the optical distribution unit (ODU), that will interconnect with the DICT GovNet fiber-optic infrastructure when present.
20  

 

One (1) unit of Network Integrator 5.1.5.3.6.1 to 5.1.5.3.6.5

 

Can you please elaborate more on this requirement? what is the use case for this requirement.

This integrates the whole communications system on a single network management system. can be the link between the gateway and the application server. some systems however, already include this within their NMS.
21 One (1) Unit of Application and System Server.

 

5.1.5.3.8.5 integrate  different communication systems such as DMR, Tetra, MPT, LTE, VHF PSTN/PLMN/IP PBX/Satellite through appropriate gateway

Is this for your network management system? can you please elaborate more on the use case for this requirement.

This integrates the whole communications system on a single network management system. some systems however, already include the Gateway or Network Integrator in this system.
22 5.1.5., page 76

 

At least ten (10) handheld integrated communications devices, each capable of the following or similar:

 

Does it require separate radio communications systems supporting these different communications systems (i.e. VHF and UHF, 2g, 3g/4g, etc..)?

No. bidders can propose singular units with all the connectivity requirements, when applicable.
23 For dimensioning purpose, can you please specify the parameters required for each of the communications system. for example:

1.) VSAT- how many users and bandwidth

2.) 2g- how many simultaneous users, etc.

3.) 4g- how many connected users, what are the features/functionalities (i.e. EPC, PCRF, etc.)

4.) etc.

1. VSAT – 5Mbps downlink, minimum of 6 simultaneous users.

2. 2G – minimum of 15 simultaneous users

3. 4G – minimum of 300 simultaneous users, for video streaming, MMS, SMS (PCRF can be excluded. we do NOT charge for access.)

4. et al.

24 5.2., page 79

 

Procurement of six (6) MOVE Dispatch

 

Our initial impression for MOVE Dispatch is to ferry the first responders to the disaster hit areas equipped with deployable solution (i.e. backpack network, etc.) to provide situation awareness on the ground. are all the required subsystem mentioned in this section expected to be fitted out in the MOVE Dispatch?

Yes.
25 5.2.1., page 81

 

Lightweight, must not exceed 10kg; Rugged Backpack

 

Is the ruggedized backpack weight negotiable?

No.
26 5.2.1., page 82

 

One (1) unit of Multicarrier emergency communications system

 

It seems the minimum technical specifications are a mix features and functionalities of different communications systems (i.e. 2g, 3g, 4g VHF/UHF, etc.) See below questions for each items:

Not applicable
27 5.2.2.6.1.1., page 82

 

Wireless Technologies supported: 2g,3g,4g

 

For 2g, since most of the mobile handsets (i.e. feature phone smartphone, etc.) supports 2g network, SMS and voice are very much supported. This can be used to reach out to the people who needs to be rescued. Hence, the 2g network is a must. However, not all mobile handsets support 3g and 4g (LTE). But why require 3G if there is 4G if the intention is to provide data connections to the first responders? the spectral efficiency of 4g is way better than 3G. 4G is the right technology for mission critical communications.

3g is no longer a requirement.
28 5.2.2.6.1.2., page 82

 

At least 120/20 kbps download/upload rates

 

As per above, 3g may not be relevant for mission critical communications.

3g is no longer a requirement.
29 5.2.2.6.1.3., page 82

 

At least fifteen (15) simultaneous users (2 carriers)

 

Any significance why 15 simultaneous users only for 2 carriers? as per 2G GSM standard, it should 30 simultaneous users using half rate vocoders for 2 carriers. This results to more people requiring help can call the first responders.

“at least” means minimum of 15 simultaneous users per carrier for 2G
30 5.2.2.6.1.4, page 82

 

Base station rated output power 24dBm

 

This rated output 25mW is typically for indoor coverage and has low power radio. Why settle for a low power radio if you need as much coverage during disaster? Recommended for 2G is 10W, for LTE is 5w

For indoor coverage, minimum is 1watt. for outdoor coverage, minimum output power is 5W
31 5.2.2.6.1.5., page 82

 

Connectivity RF Connectors: Single RF antenna connector (2x) UE antenna connectors (2x)

 

What is the antenna gain? you need to specify the antenna gain or the expected EIRP/ERP. Expective radiated Power (ERP) is the power emitted by the radio transmitter with the considerations of the gains and losses of the cables. So even if you indicate the power of the radio, vendors can put low gain antenna and high loss cables that is cheaper. What is the specifications of the antenna? Omni or directional?

OMNI
32 5.2.2.6.1.6., page 82

 

Wi-Fi IEEE802.11a/b/g/n 2.4GHz-5GHz

 

Is this intended for Ad Hoc network?

Yes.
33 5.2.2.6.1.7., page 82

 

Bluetooth 4.0, 2.4GHz

 

What is this for? Wi-Fi has better coverage than Bluetooth.

Provision of connectivity when needed.
34 5.2.2.6.1.8., page 82

 

Ethernet 4.0, 2.4 GHz

 

What is this for? Wi-Fi has better coverage than Bluetooth

Provision of connectivity when needed.
35 5.2.2.6.1.9., page 82

 

USB Port USB 2.0 Type A, mini USB Type B

 

What is this for?

Provision of interface when needed.
36 5.2.2.6.1.10., page 82

 

GPS 1xSMA (with 28dB antenna)

 

What is this for? What are the location based services required?

The GPS provides critical positioning capabilities
37 5.2.2.6.11., page 82

 

Battery power source up to 2h, with Dual power input connector for two swappable external batteries (with at least 2x spare batteries)

 

Any significance why only 2 hours? There are battery technology that can last for 5 hours and can still be compact.

These are minimum requirements. bidders can propose higher.
38 5.2.2.6.1.12., page 82

 

Power Supply 9V-30V DC

 

We assume this is 9V to 30V DC range?

Yes.
39 5.1.2., page 67

 

Cargo Closed Van Interior Specification

 

Do you have an draft layout (i.e. floor plan, etc.) showing how the interior features (i.e. sleeping cabin, lavatory, ops room, power supply room, space provision for motorcycle, etc.) will fit out into the cargo van. Note that the main components of the project is the emergency communications systems which should be prioritized  in terms of dimensioning and space allocation.

Yes.
40 Is incident management part of the MOVE HUB system’s function? Yes.
41 Would there be public access (like hotline) to the telephony component of the MOVE HUB? Yes.
42 Is the dispatch system referred to on the TOR refers to the dispatch of resource components of the MOVE
system or would it also manage other/adhoc resources that may be used by the emergency team on emergency site?
Yes.
43 Would the deployed resources be tracked by GPS devices? Yes.
44 Why there’s a need for a Firewall with 30Gbps throughput? (Please refer to 5.1.5.2.1.7.1 scope of work) throughput is 10Gbps minimum, 30Gbps maximum
45 Is there already an existing “Data Collection and Analytics System” If none, what Data will be collected and analyzed?

 

i. Please Define Scope. (Please refer to 5.1.5.2.1.1.0)

 

ii. It mentions about Database Server, but Database Software is out scope?

No system in existent. database software comes with the database server, but MUST be compatible with DRRMIS (open source).

 

(to be inserted in the requirements)

46 Please clarify scope of “Application and System (Please refer to 5.1.5.3.8.1.0) Please refer to item no. 21.
47 Can DICT expand the number of years from 3 years to 5 years or allow bidders submit several completed projects to a maximum of 5 projects? The MOVE project is quite substantial in amount and not many prospective bidders can meet this requirement. This is already the case.
48 Schedule of Requirements, page 63 (Delivery Period)

 

Please allow extension of to October 26 to give time for bidders to provide proper proposal since the scope of the requirements entails complexity.

 

Please allow extension of delivery period to 150 calendar days upon NTP for Phase 1.

 

Please allow extension of delivery period to 180 calendar days upon NTP for Phase 2

 

 

Bid opening will proceed as scheduled.

 

1. delivery period is 90 Calendar Days upon NTP

 

2. delivery for phase 2 is 60 calendar days upon acceptance of phase 1

49 Bid Datasheet, page 37 (Certificate of Distributorship/Dealership/Resellership)

 

Please identify which main equipment should have a Certificate from the Manufacturer.

All communications equipment, including UAV and Generator Set
50 Bid Datasheet, 37, (ISO 9001)

 

• For the ISO 9001, please allow Quality Management System TL 9000 as alternative for ISO 9001. TL 9000 specializes the generic ISO 9001 to meet the needs of one industrial sector, which for TL 9000 is the information and communications technology (ICT)—extending from service providers through ICT equipment manufacturers through the suppliers and contractors and subcontractors that provide electronic components and software components to those ICT equipment manufacturers.

 

• Please allow one (1) ISO or alternative Quality Management System Certificate for this bid.

Request is granted since TL9000 focuses on telecommunications quality systems requirements
51 Sec. VII, page 71 (Database Server)

 

• Please confirm that the bidder shall provide for hardware only (not including softwares).

 

• Please identify the Storage requirement.

 

• Please confirm if the Firewall throughput of 30Gbps can be lowered.

 

·        please refer to item no. 45

·        For maximum network efficiency, the minimum of 10Gbpbs firewall throughput will be adopted.

52 Sec. VII, page 72 (IP Radio)

 

• Please verify the correct operating frequency.

 

• Please confirm that the licensing shall be under the responsibility of DICT.

please refer to Item 172.
53 Sec. VII, page 72 and page 80 (Radio Units of Ad Hoc Network)

 

• Please confirm that the VHF, UHF, SHF, EHF, WiFi requirements may be excluded as the transmission can be via LTE only.

 

• Since this is basically used for transmission of data, please clarify why we need to have a “Built-in video management software and Built-in H.264 video encoder”.

 

• Please elaborate on “Able to connect to UAV as one of the hops/nodes”

– Adaptability to these frequencies is to open the bid to any type of technology available for ad hoc. bidders can choose only one technology, and focus on the frequency range within that chosen platform.

 

– Built-in management software and video encoder is to be able to access the sent information (in this case, video) at the terminal as needed.

 

– UAV can be equipped with a radio relay/repeater that can act as one of the nodes to extend the network coverage.

54 Sec. VII., page 73 (Network Integrator)

 

Please confirm that the Network Integrator may be excluded since it has the same purpose of the Gateway/Communications Integration/Radio Interface Unit.

Network integrator is a separate unit, and CANNOT be excluded. this serves as a redundancy unit in case one of the modules drop or fail.
55 Sec. VII, page 74-75 (Application and System Server)

 

• Please confirm that the bidder will have to provide for hardware only (not including software).

 

• Please confirm if the video management software shall be installed in this server and not in the Radio Units of Ad Hoc Network

 

• Please confirm if the Firewall throughput of 30Gbps can be lowered.

– Software is included in this server. such as the network management system, dispatch system, video, image, audio management software, integrated communications platform/dashboard, drone mapping software, even the electrical and cooling system management (when applicable), etc. DO TAKE NOTE: ALL SYSTEMS MUST BE COMPATIBLE AND WORKING TOGETHER. software is not defined one-by-one, to provide flexibility of systematization. but it is expected that the whole network is INTEGRATED.

 

– minimum throughput for the firewall is 10Gbps

56 Sec. VII, page 75 (HF, VHF, and UHF Base and Mobile Radio)

 

• Please confirm that HF radio shall be omitted from the requirements.

 

• Please confirm that if the HF radio will not be included in the requirement, the Automatic Link Establishment (ALE) will also be omitted.

 

• Please confirm that the quantity for this requirement is as follows:

– 1 unit VHF base radio

– 1 unit UHF base radio

– 1 unit VHF mobile radio

– 1 unit UHF mobile radio

– HF is not omitted.

 

– ALE is not omitted as well

 

– no, but will be amended

57 Sec. VII, page 76 and 82 (Pneumatic Telescope Mast)

 

Please confirm that the bidder can offer other radio standard such as but not limited to P25 or NXDN

Ok.
58 Sec VII, page 78 (Pneumatic Telescopic Mast)

 

Please allow approximate mast weight of at most 60kg.

Approximate mast weight 55 kg
59 Sec. VII, page 79 (4×4 pick-up truck with power winch)

 

Please provide the height of pole for the MOVE Dispatch.

To be included/added to the technical specifications within the MOVE Dispatch
60 Sec. VII, page 80 (PTZ IP Camera)

 

• Please allow Image Sensor 1/2.8” Progressive Scan CMOS

 

• Please allow to have the “Connectivity to Wi-Fi” as optional only.

These are minimum requirements. bidders can propose higher.
61 Sec. VII, page 82 (UHF/VHF Repeater)

 

Please clarify why the UHF/VHF Repeater is in the dispatch vehicle and not in the six-wheeler truck

VHF/UHF repeater is in the dispatch vehicle for expanded network coverage.
62 Sec. VII, page 82 (Multi-Carrier Emergency Communications Systems)

 

Please double check the Base station rated output power. Recommended output power is greater than + 24dBm.

Please refer to item no. 30
63 Sec. VII, page 86 (Azimuth Deploy Speed)

 

The antenna specifications (azimuth) is particular only to iNETVu.

 

Please allow 2°/sec type for Azimuth Deploy Speed.

Azimuth deploy speed for Drive-away VSAT antenna must be fast enough. 2°/sec or 5°/sec azimuth deploy speed allowable only to fly-away VSAT Antenna.
64 Sec. VII, page 89 (Ku-Band BUC IF input)

 

Please allow IF input within the range of 950-1750 MHz

Ok.
65 Sec VII, page 89 (C-Band BUC IF input)

 

Please allow IF input within the range of 950-1750 MHz

Ok.
66 Sec VII, page 90 (Ku-Band BUC LO Frequency conversion)

 

Please allow other value for LO Frequency Conversion since it is only conversion.

 

12800MHz is a typical LO’s for satellite communications. This has no negative effect on the performance. It is just too specific.

Ok.
67 Sec. VII, pate 89 (C-Band BUC LO Frequency conversion)

 

Please allow other value for LO Frequency Conversion.

 

4900 or 7375 MHz is a typical LO’s for satellite communications.

Ok.
68 Sec. VII, page 89 (C-Band BUC Connector)

 

Please kindly allow Connector type: CPR-137G.

Ok.
69 Sec. VII, page 89 (C-Band LNB Input frequency range)

 

Please double check the values and term.

 

• Output frequency range: 13.75 to 14.5 GHz – This is the TX frequency and specs of the BUC

 

• This should be Input frequency range: 12.25-12.75 GHz

Ok.
70 Sec. VII, (C-Band LNB Input frequency range)

 

Please double check the term.

 

• Input frequency range: 950 to 1700 MHz

• This should be Output frequency range: We request to allow Output frequency range within the range of 950-1750 MHz

Ok.
71 Sec VII., page 89 (C-Band LNB Output frequency range)

 

Please double check the values and term.

 

• Output frequency range: 5.85 to 6.425 GHz – This is the TX frequency and specs of the BUC

 

• This should be Input frequency range: 3.4 to 4.2 GHz

Ok.
72 Sec VII., page 89 (C-Band LNB Input frequency range)

 

Please double check the term.

• Input frequency range: 950 to 1525 MHz

• This should be Output frequency range:

• We request to allow Output frequency range within the range of 950-1750 MHz

Ok.
73 Sec. VII, page 89 (Ku- and C- Band LNB Output power)

 

Please double check the Output power as this is too high for LNB. Typical Output power is 0 to 10dBm.

Ok.
74 Invitation to Bid, page 4, item 1

 

Please confirm that the ABC for this bid is for equipment only and the subscription is not included.

Yes, subscription not included.
75 We request for the end user to share with the bidders the used cases presented during the pre-bid. Use-cases shall be provided upon purchase of bid documents
76 We request for the end user to share with the bidders the pictures of sample layout. Sample lay out shall be provided upon purchase of the bid documents
77 5.1.2 Cargo Closed Van Interior Specification One (1) unit of Enclosed Lavatory with Basin

5.1.2.6.1 With water features: fresh water for lavatory flush and bidet; potable water for basin

5.1.2.6.2 Separate pipes from fresh water, and potable water storage

5.1.2.6.3 Separate pipes going to used water storage, and septic tank

 

Comment:

The MOVE Hub from its specifications and the amount and nature of equipment that will be installed inside it, would presumably be a Command Center for emergency situations. The inclusion of a sanitary facility within the Command Center in our opinion is inappropriate and based on our past projects this will hasten degradation of the vehicle and the facility as a whole. Sanitation and maintenance will be a bigger task as compared to a set up where in toilets, lavatory, septic tanks and shower facilities are separated from the Command Center.

 

Inquiry:

Can the DICT consider use of portable toilets or other similar equipment that can be hauled or trailered to the MOVE Hub deployment site when situations would call for operations that would last several days and there is no sanitary facility available? If yes, can the enclosed lavatory and sanitary component be taken out from the MOVE Hub specifications and be replaced by a trailered portable toilet (Portalet).

Almost all of the equipment in the vehicle has IP67 or higher rating. we require effective use of the all the equipment in whatever type of environment is present. including lavatory facilities.
78 5.2.1. Unified Communications System and Data Collection

One (1) unit of portable transceiver radio set as one of the nodes of the Ad Hoc Communications Network

 

Must have dynamic and adaptive routing protocols (position-based, mesh network, self-healing, and self-forming)

 

Automatic Link Establishment (ALE) for adaptable frequency adjustment within (frequency allocation to be determined)

 

5.2.2.1.2.1. VHF 30-300MHz

5.2.2.1.2.2. UHF 300-3000MHz

5.2.2.1.2.3. SHF 3-30GHz

5.2.2.1.2.4. EHF 30-300GHz

5.2.2.1.2.5. Wi-Fi ISM 2.4 GHz, 5.8GHz

 

Transmission: Either any of the following: (1) Radio over IP, (2) MANET or (3) LTE

(Data, IP-Based, web-based applications)

 

Throughput of at least 5Mbps

 

Comment: The above specification is confusing. At the topmost it is asking for a portable transceiver radio set as one of the nodes of the Ad Hoc Communications Network. Must have dynamic and adaptive routing protocols (position-based, mesh network, self-healing, and self-forming). These are consistent and is correct. However, also asking for Automatic Link Establishment (ALE) for adaptable frequency adjustment within (frequency allocation to be determined) introduces the confusion. ALE is a link establishment technic that is only being used in HF SSB communication and not in Mobile Adhoc Network radios as the rest of the specifications are suggesting. Also, HF is only a narrowband form of radio communication while the requirement is likewise asking for a throughput of at least 5MBps which is a wideband communication specification.

 

Inquiry: May we request that the ALE part be removed and the table of frequencies be revised to include only those that will allow the throughput requirement of 5Mbps?

– Adaptability to these frequencies is to open the bid to any type of technology/platform available for ad hoc. bidders can choose only one technology, and may focus on the frequency range within the chosen platform, including the protocols needed to provide “self-healing”, or other functions required of the network

– ALE (or another protocol with similar function) MUST be provided with the proposed platform for the ad hoc

79 Comment

The ABC for the Mobile Operations Vehicle for Emergency (MOVE) Hub and MOVE Dispatch of the Government Emergency Communications System (GECS) Project of the DICT requires delivery of a total of Six (6) sets of MOVE and GECS. After a thorough review and evaluation of the finance and pricing we find the total value of the number of sets required for the whole lot containing the various system components that can qualify to minimum technical requirements of the DICT exceeds that of the ABC or Approved Budget for Contract for the project.

 

Inquiry:

May we request that the number of sets of MOVE and GECS required be reduced from 6 to 4? In our opinion this will ensure that all the equipment to be supplied for the project will be of high quality and not simply based on which has the lowest price. And since the mode of procurement is still Public Bidding the spirit of competition is still preserved for the advantaged of the government

 
80 Can we request for an overall solution architecture
envisioning all the connectivity between the sub

systems, network elements, etc.?

No.
81 Can we request for use case description of each component required as part of the ToR. i.e. One (1) Unit of Multi-Carrier Emergency Communications System apart from the requirements specification. Upon purchase of bid docs.
82 5.1.5., page 72

At least two (2) pairs of IP Radio

 

Please clarify why 24.05-24.25GHz is specified for IP Radio. This frequency band is defined for use by automobile radar rather than communications systems and usage of this band is planned to be phased out by 2022 in both Europe and US. (http://e2e.ti.com/blogs_/b/behind_the_wheel/archive/2017/10/25/why-are-automotive-radarsystems-moving-from-24ghz-to-77ghz).

 

This frequency range is NOT normally used for backhaul transmission. It would be more relevant to refer to ITU-R F.748-4 Annex 1/CEPT ERC 13-02 E which defines 24.5-26.5 for IP Radio. (http://www.etsi.org/deliver/etsi_en/302200_302299/3022170202/01.03.01_40/en_3022170202v010301o.pdf)

Please refer to Item 129.
83 5.1.5., page 72

Must have dynamic and adaptive routing protocols (position based mesh network, self-healing, and self-forming)

 

Are all these 10 radio units of Ad Hoc network to be configured as a mesh network? If point to point network topology is used, then self-healing is not supported.

 

Where does DICT plans to tap in for power required
by the ad hoc network?

Yes, mesh topology is NOT point-to-point.

 

These ad hoc nodes must have their own power supply.

84 5.1.5., page 73

Must have at least 12 independent voice channels separated from data channels

 

What is the use case for this requirement on the context of an Ad Hoc network or LTE network? Can we interpret this as the requirement of MC PTT on top of LTE network?

Recommended layout of equipment and use-case scenarios will be provided upon purchase of bid docs.
85 5.1.5., page 73

Minimum number of Hops/Nodes: 8 (+2 for Hub & Dispatch nodes)

 

Based on the above clarifications, we recommend for DICT to revisit this requirement and assess the practically of deploying an ad hoc network with either bus, mesh or even star network topology. Setting up these network topologies will require a fair bit of time to test and make the solution work. We strongly recommend DICT to revisit this requirement as it does not provide any practical sense in the context of an emergency or disaster event. Besides, these multi hops ad hoc network are typically low power wireless network and provides minimal coverage with multiple point of failures. Whereas the GSM network-in-a-box and LTE deployable compact network can provide efficient and wider coverage.

LTE solution is one of the choices.
86 5.1.5., page 73

Built-in Position Location Information System

 

What is the use case for this requirement on the context of an Ad Hoc network or LTE network? Can we interpret this as the requirement of MC PTT on top of LTE network?

Prior to deployment of the nodes, area mapping for “drop-off locations” shall be determined. nodes shall be deployed based on these locations. thus, accurate position must be known.
87 5.1.5., page 73

Build-in video management software

 

What is the use case for this requirement on the context of an Ad Hoc network or LTE network? Can we interpret this as the requirement of VMS (Video Management System) on top of LTE network? Is it intended to provide visual coverage within the nearby area where the MOVE Hub is located or disaster hit area for situation awareness?

If VMS is not part of the ad hoc management system, then yes.

 

transmitted information, including video, is expected to be managed at the terminal of your ad hoc network.

88 5.1.5., page 73

Build-in H.264 video encoder

 

What is the use case for this requirement on the context of an Ad Hoc network or LTE network? Can we interpret this as the requirement of VMS (Video Management System) on top of LTE network? Is it intended to provide visual coverage within the nearby area where the MOVE Hub is located or disaster hit area for situation awareness?

If VMS is not part of the ad hoc management system, then yes.

 

transmitted information, including video, is expected to be encoded/decoded at the terminal of your ad hoc network.

89 5.2.2.6.1.8., page 82

10/100/1000 Base-T

 

This is OK for wired connectivity to the network.

Not applicable.
90 5.1.5., page 75

Frequency Hopping with at least 30 user programmable hop plans (with hop name, rate, bandwidth, and encryption key)

 

Can you please elaborate more on this requirement? What is the use case for this requirement.

This requirement lowers interferences, (co-channelling, adjacent channel, inter modulation, etc.)
91 Is DICT, being a government agency looking at communications solutions that are compliant to the standards like 3GPP mission critical, ETSI, etc.? 2g and 4g
92 5.1.

Ad Hoc Network

 

Need to further define the Ad Hoc Network requirement that is ‘mobile, flying, and wireless’ and adapts to ‘VHF, UHF, SHF frequencies’ with ’12 independent voice channels’.

 

o Is the drone capable of repeating VHF, UHF, and SHF voice communications?

 

o Will there be 12 independent voice channels per listed band?

When applicable with the proposed platform.

 

No.

93 5.1.

Gateway/Com Integration/ Radio Interface Unit

 

o The eight radio interfaces need to be defined – exact frequency bands have to be defined as there are sub-bands; analog or digital; conventional or trunking; digital protocols – P25, TETRA, DMR, NEXEDGE, etc.

 

o The PNP and AFP, normally, will not allow access to their encrypted radios.

 

o (HF, VHF, and UHF Base and Mobile Radio) These are interface radios to the gateway. The given specs are for tactical HF radios. Hop plans, ALE, and antenna tuners are terms normally associated with HF-SSB communications but not VHF and UHF.

the gateway must be able to accept different radio systems, including legacy equipment still being used in remote areas.
94 5.2.

VHF/UHF Repeater

 

We cannot provide a single repeater unit that can support Low Band/VHF/UHF operation. We assume that this repeater will be used by the responders at the MOVE pickup. Their multimode radio can be made to operate in DMR 2 conventional mode and will just need a single repeater, preferably at 350 MHz (a UHF sub-band

Ok.
95 5.1.1., page 67

Six-Wheeler Truck with cutaway chassis

 

Will DICT accept China brands? For quality assurance purposes, would DICT consider Japanese or European brand?

No preferences.
96 5.1.1.1., page 67

Engine Type: Shall no exceed 7.6L In-Line 6, 4-stroke cycle, water-cooled direct injection turbocharged diesel engine

 

Anything below this specs?

All specifications are minimum. EXCEPT the 7.5L requirement.
97 5.1.1.1.8, page 67

Payload: ~11,000kg

 

Anything below this specs?

No.
98 5.1.2., page 67

Cargo Closed Van Interior Specification: One (1) unit of Ceiling Mount Cooling System

 

Can we suggest a wall mount? As experience tell us that ceiling type might cause flooding of the ceiling and might affect the cables inside wall mounted remote control w/ temperature control.

No.
99 5.1.2.5.1., page 67

Sleeping cabin: Two (2) units of fixed bed frames, at least 2.0 x 1.0m (LxW)

 

Does it have to be fixed bed?

Yes.
100 5.1.2.5.3., page 67

Sleeping cabin: Mounted on the wall

 

Does DICT mean secure and installed beside the wall, fixed, with pull out extra beds?

No.
101 5.1.2.5.5., page 67

Sleeping cabin: With two (2) beddings storage underneath the beds, accessible thru the sleeping cabin wall

 

What’s the purpose of bedding storage?

To store beddings.
102 5.1.2.7.2.4., page 68

At least two (2) safe storage, for drone, laptops, and accessories

 

What is the size of the drone?

Depends on the size of the proposed drones of the bidders.
103 5.1.2.7.2.4., page 68

At least two (2) universal charging station (atop drawers & storage) for mobile devices (i.e. laptops, tablets two-way, radio, etc.)

 

What particular charging stations? AC Only or USB port, with DC charging , what port?

charging stations are supplied from the power supply system of the MOVE Hub
104 5.1.2.8.1., page 68

Wall in-between power supply room and OPS room must be sound proofed

 

Can we submit our own engineering design to ascertain this feature?

Yes.
105 5.1.2.8.1., page 68

Wall in-between power supply room and OPS room must be sound proofed

 

Generally, underneath chassis. Is this OK with DICT?

No.
106 5.1.2.7.2.4., page 68

 

Can ramp be provided instead to avoid power loss and provide easy maintenance for the MOVE?

Hydraulic ramp
107 5.1.2., page 68

Doorway from the right-side of the trailer into the OPS room with retractable steps

 

Manually deployed and retracted?

As proposed.
108 5.1.2., page 68

Penned/fenced rooftop approximately 0.3m (height) for safety and discretion of equipment

 

Collapsible fence or fixed?

As proposed.
109 5.1.3., page 69

At least (2) units of storage with locks for self-sustainability tools (e.g.: pickaxe, axe, portable chainsaw, shovels, outside cabin dirty kitchen kit, cooking kits and utensils, foldable table and chairs; with at least two (2) 20L containers for diesel refueling)

 

Is this for disaster equipment storage rack?

Locked storage.
110 5.1.4., page 69

One (1) unit of built-in power generator system

 

Power Gen with pull out rack easy access?

as proposed.
111 5.1.3., page 69

With exterior trailer access for electrical taps and charging station

 

This can be done but is NOT recommended as this is dangerous and might cause short circuit.

Safety is our concern, thus, all the necessary precautions must be considered.
112 Bid Data Sheet, -page 37

 

Please identify which main equipment should have a Manufacturer’s Certificate.

For all communications, IT, cooling systems, including the power generator
113 Sec VII, page 71 (Database Server)

 

• Please confirm that the bidder shall provide for hardware only (not including software).

 

• Please allow 1TB of storage for the server.

 

• Please allow Firewall throughput of 1Gbps.

·        No system in existent. database software comes with the database server, but MUST be compatible with DRRMIS (open source).

(to be inserted in the requirements)

·        Still 8TB

·        Amended

114 Sec VII, page 72 (IP Radio)

 

• Please verify the correct operating frequency.

 

• Please confirm that the licensing shall be under the responsibility of DICT.

Amended.
115 Sec. VII, page 72 and page 80 (Radio Units of Ad Hoc Network)

 

• Please remove VHF, UHF, SHF, EHF, Wi-Fi requirements as it is not applicable.

 

• Please remove the item ‘Must have at least 12 independent voice channel separated from data channels’ as this requirement shall be used for data transmission.

 

• Please remove ‘Built-in video management software and Built-in H.264 video encoder’ as this requirement shall be used for data transmission.

– adaptability to these frequencies is to open the bid to any type of technology available for ad hoc. bidders can choose only one technology, and focus on the frequency range within that chosen platform.

 

– built-in management software and video encoder is to be able to access the sent information (in this case, video) at the terminal as needed.

 

– UAV can be equipped with a radio relay/repeater that can act as one of the nodes to extend the network coverage.

116 Sec. VII, page 73 and 81

(UAV)

 

Please confirm that the CAAP compliance shall be done after awarding of the project since the bidder will have to register the UAV to CAAP for it to be certified.

Yes, this is possible. all requirements must be submitted before the final acceptance.
117 Sec. VII, page 73 (Network Integrator)

 

Please remove the Network Integrator as it already a duplicate / has the same purpose as the Gateway/Communications Integration/Radio Interface Unit.

network integrator is a separate unit, and CANNOT be excluded. this serves as a redundancy unit in case one of the modules drop or fail.
118 Sec. VII, page 73 (Network Integrator)

 

Please remove the integration of ‘LTE transmission’ in the Network Integrator as it is not applicable.

This serves as a redundancy unit in case one of the modules drop or fail.
119 Sec VII, page 73, (Gateway/Communications Integration/Radio Interface Unit)

 

Please remove the integration of ‘LTE transmission’ in the Gateway as it is not applicable.

the gateway must be able to accept different radio systems, including legacy equipment still being used in remote areas.
120 Sec VII, page 78 (Pneumatic Telescopic Mast)

 

Please allow approximate mast weight of 57kilos

Approximate mast weight 55 kg
121 Sec VII, page 79 (4×4 Pick-up Truck with Power Winch)

 

Please accept the pole height of 4m for the 4×4 pick-up truck.

Ok.
122 Sec VII, page 82 (Multi-Carrier Emergency Communications Systems)

 

Please double check the Base station rated output power. Output power is greater than + 24dBm.

Ok.
123 Sec. VII, page 86 (Satellite Router/Modem)

 

As reviewed, the D-TDMA is iDirect’s patented access technology. Please see link below:
http://www.idirect.net/Company/Resource-Center/Satellite-Basics/Glossary-of-Terms.aspx

 

With this, please allow bidder to propose other brand for the Satellite Router/Modem

Okay.
124 Please allow Connector type: CPR-137G. Ok.
125 Sec. VII, page 89 (Ku- and C- Band LNB Output power)

 

For the VSAT part, please confirm that the ABC for this bid is for VSAT equipment but the subscription to the satellite provider is not included.

subscription is not included
126 We request for the end user to share with the bidders the used cases presented during the pre-bid. Use-cases shall be provided upon purchase of bid documents
127 We request for the end user to share with the bidders the pictures of sample layout. sample lay out shall be provided upon purchase of the bid documents
128 Additional Requirement for Pneumatic Telescopic Mast to add as another item under the minimum technical specifications (5.1.5.3.13.1.10)
129 Additional Role for the End User to add as another role for the end user

 

ORIGINAL PROVISION AMENDED PROVISION
Section I. Invitation to Bid
3. Delivery Period

Within thirty (30) calendar days from receipt of Notice to Proceed

3. Delivery Period

Phase I – within ninety (90) calendar days upon receipt of NTP

Phase II – within sixty (60) calendar days upon acceptance of Phase I

Section III. Bid Data Sheet
12(x) Valid and current ISO 9001 Quality Management System  Certificate issued to the manufacturer by an Independent Certifying body 12(x) Valid and current ISO 9001 or TL9000 Quality Management System Certificate issued to the manufacturer by an Independent Certifying body
Section VI. Schedule of Requirements
Within thirty (30) calendar days upon receipt of Notice to Proceed

Project Site: Central Office, Valenzuela City

Within ninety (90) calendar days upon receipt of Notice to Proceed

Project Site: DICT Velenzuela Campus, Brgy., Karuhatan, Valenzuela City

Section VII. Technical Specifications
5.1.5.2.1.7.1. 30Gbps Firewall throughput 5.1.5.2.1.7.1. Minimum of 10GbpsFirewall throughput
Page 71, Data Collection and Analytics System

Scalable, Stackable, Rack-Mountable

Page 71, Data Collection and Analytics System

At least 8TB storage, Scalable, Stackable, Rack-Mountable

Page 75

One (1) unit of the following: HF, VHF, and UHF BASE AND MOBILE RADIO

Page 75

One (1) unit of the HF Base Radio and one (1) unit of VHF/UHF dual band Base Radio

5.2.2.6.1.1. Wireless Technologies supported:

2G, 3G, 4G

5.2.2.6.1.1. Wireless Technologies supported:

2G, 4G

5.2.2.6.1.2. At least 120/20 Kbps Download/Upload Rates 5.2.2.6.1.2. At least 120/20 Kbps Download/Upload Rates for 2G; At least 5/5 Mbps Download/Upload Rates for 4G (CIR)
5.7. xxx

 

For Phase 1:

(a) Central Office, Valenzuela City, 30 calendar days after NTP

5.7. xxx

 

For Phase 1:

(a) DICT Valenzuela Campus, Brgy. Karuhatan, Valenzuela City, 90 calendar days after NTP

5.1.5.3.2.1.9. Minimum Range: 20km 5.1.5.3.2.1.9. Minimum Range: 10km
Page 73, 10 radio units of Ad Hoc Network (Mobile, Flying, Wireless)

Protection at IP68 standard

Page 73, 10 radio units of Ad Hoc Network (Mobile, Flying, Wireless)

Protection at IP67 standard

Page 73, One (1) unit of Fiber Optic Infrastructure Interface Page 73, One (1) unit of Fiber Optic Infrastructure Interface (ODU)
5.2.2.6.1.3. At least fifteen (15) simultaneous users (2 carriers) 5.2.2.6.1.3. At least fifteen (15) simultaneous users for each carrier for 2G: at least 300 simultaneous users for 4G
5.2.2.6.1.4. Base station rated output power ≤+24dBm Base Station rated power: minimum of 1W for indoor coverage: minimum of 5W for outdoor coverage
5.2.2.6.1.5. Connectivity RF Connectors: Single RF antenna connector (2x); UE antenna connectors (2x) 5.2.2.6.1.5. Connectivity RF Connectors: Single RF antenna connector (2x); UE antenna connectors (2x); Antenna Gain = 3 to 6dBi
No original stipulation. Page 71, Database server

 

Must come with the Database Software that is compatible with DRRMIS (open source), including archives of the captured spatial data, information gathered (video, image, audio, logs, etc.)

5.1.5.3.8.14.1. 30Gbps Firewall throughput 5.1.5.3.8.14.1. 10Gbps Firewall throughput
Page 76, At least ten (10) handheld integrated communications devices, each capable of the following or similar:

 

Compatibility with DMR, Tetra standards

Page 76, At least ten (10) handheld integrated communications devices, each capable of the following or similar:

 

Compatibility with DMR, Tetra, IP25 standards

No original stipulation. Page 81, One (1) unit of portable transceiver radio set as one of the nodes of the Ad Hoc Communications Network

 

Xxx

 

To include portable mast/pole, extended height up to approximately 4 meters, minimum top load 25kg, including internal cable

4.2.5.1.1.1. IF input: 950-1450 MHz 4.2.5.1.1.1. IF input: 950-1750 MHz
4.2.5.1.2.1. IF input: 950-1525 MHz 4.2.5.1.2.1. IF input: 950-1750 MHz
4.2.5.1.1.7 LO Frequency conversion: 15450 MHz 4.2.5.1.1.7 LO Frequency conversion: 12.8 GHz, 15.45 GHz
4.2.5.1.2.6. LO Frequency conversion: 7300,7375 MHz (user selectable) 4.2.5.1.2.6. LO Frequency conversion: 4900, 7375 MHz (user selectable)
4.2.5.1.2.4. Connector: WR229 (Rx) and WR137 / Type N (Tx) 4.2.5.1.2.4. Connector: WR229 (Rx) and WR137 / Type N (Tx) and CPR-137G
4.2.5.2.1. Output frequency range: 13.75 to 14.5 GHz 4.2.5.2.1. Output frequency range: 10.7 to 12.75 GHz
4.2.5.2.1.2. Input frequency range: 950 to 1700 MHz 4.2.5.2.1.2. Output frequency range: 950 to 1750 MHz
4.2.5.2.2.1. Output frequency range: 5.850 to 6.425 GHz 4.2.5.2.2.1. Output frequency range: 3.625 to 4.2  GHz
4.2.5.2.2.2. Input frequency range: 950 to 1525 MHz 4.2.5.2.2.2. Input frequency range: 950 to 1750 MHz
4.2.5.2.1.3. Output power @ 1dB GCP: 31.5 dBm min. @ 25 deg. C 4.2.5.2.1.3. Output power @ 10dB GCP: 31.5 dBm min. @ 25 deg. C
4.2.4.1.2. Multiple Access: TDM Downstream, D-TDMA (Deterministic TDMA) Upstream 4.2.4.1.2. Multiple Access: TDM Downstream, TDMA (Deterministic TDMA) Upstream
No original stipulation. 5.1.5.3.13.1.10. Lightning Arrester to withstand 30KV, with grounding not greater than zero impedance.
  8.4. Provision of assigned frequencies from National Telecommunications Commission (NTC).

 

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

 

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

  • Revised Schedule of Requirements as of 12 October 2018
  • Revised Technical Specifications as of 12 October 2018
  • Revised Technical Bid Form as of 12 October 2018

 

For information and guidance of all concerned.For a full copy of the document, Click the link below:

Supplemental Bid Bulletin No. 2 -PROCUREMENT OF THE DEPARTMENT OF INFORMATION AND COMMUNICATIONS TECHNOLOGY MOBILE OPERATIONS VEHICLE FOR EMERGENCY (MOVE) HUB AND MOVE DISPATCH OF THE GOVERNMENT EMERGENCY COMMUNICATIONS SYSTEM (GECS) PROJECT

Issued this 11th day of September 2018.

 

 

 

(SGD) JIEZL GABRIELLE G. REOTUTAR

Vice Chairperson, BAC4G&S