Draft_solicitation_questions_answers.doc

DOC document 292 KB Posted

Attached to
Computer Aided Dispatch Information System FINAL RFP
Solicitation number
HSCETC-10-R-00010
Issued by

About this file

Draft solicitation questions and answers.

View the file

Other files

File Type Posted
HSCETC-10-R-00010 Amendment 000004 - Cancellation.pdf PDF
SF33amd2.pdf PDF
SF33amd3.pdf PDF
CADIS_Sol_04192010amd3.doc DOC document
CADIS Questions amd2.doc DOC document
CADIS FRD 040810.doc DOC document
CADIS_Sol_04082010.doc DOC document
Preproposal conference briefing 0312 oaq full v3.ppt PPT presentation
sf33.pdf PDF
CADIS_Sol_QA 0317-oaq.doc DOC document
CAD Solic PPC QA 031610.xlsx XLSX spreadsheet
PPC_attendee_sign-in.pdf PDF
SF33.pdf PDF
OMB Circular A-11 Part 7.pdf PDF
NIBRS Standards.pdf PDF
Technical Reference Model 2010.pdf PDF
Labor Categories 03092010.doc DOC document
Baseline Security Requirements.doc DOC document
SLM Gate Review Document Delivery Expectations.pdf PDF
ICE_SLM_Handbook_1.2.pdf PDF
MCD CF19 Toughbook Specs.xls XLS spreadsheet
CADIS FRD 03092010.doc DOC document
Technical Architecture Guidebook.pdf PDF
Enterprise Systems Assurance Plan.pdf PDF
Architecture Test Evaluation Plan 2.0.pdf PDF
SLM Work Patterns.pdf PDF
Project Tailoring Plan Template.doc DOC document
CADIS Sol 03092010.doc DOC document
CF19 Toughbook Specs.xls XLS spreadsheet
14. FRD_2009_11 03a.doc DOC document
Section A.pdf PDF
CADIS Solicitation draft.doc DOC document
Show all 32

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Draft Solicitation Questions from Industry

Computer Aided Dispatch Information System (CADIS) – HSCETC-10-R-00010

Answers provided by the CADIS IPT 1/20/2010

Document (Attachment or Exhibit)
Paragraph
Page No.
Question
Answer
1.
General
Will there be an industry day prior to the release of the final RFP?
There will be a pre-proposal conference about mid-March in Washington, DC.
2.
General
Will the contractor be required to prepare a Privacy Threat Assessment and PIA as formal deliverables in section 7 of the RFP?
The Contractor prepares the PTA, PIA and other documents and provides an ISSO per the section 5.8 Certification and Accreditation and deliverables as required by section 7.8 by the prepared C&A plan.
3.
General
Is ICE acting on behalf of NPPD as the responsible DHS component?
ICE is procuring this effort, which will be transferred to DHS/OPO & NPPD immediately after award for administration.
4.
General
Will CADIS Solutions conform to ICE Infrastructure or NPPD Infrastructure?
The project will be managed by ICE and follow all ICE Policies and Procedures.
5.
General
Will CADIS Include NAICS Code 541519 to include FirstSource Small Business Size Standards?
The chosen NAICS code is 541512 but codes 541511 and 541519 could also be utilized.
6.
General
What is the expected online retention for CADIS data?
The answer is in FRD section 2.21, the expected online retention for CADIS data is indefinitely.
7.
General
Will Contractor have remote access during implementation?
Yes. The Contractor will have access to the Functional Quality Test Environment where the application will be tested.
8.
General
Is it the intent of the FPS to provide GIS data that contains floor plan and alarm location data? If so, how many floor plans will be provided and are alarm points and floor plans geospatially referenced? What format will the floor plans be in?
Language added to 2.2, 2.2.5

The system shall have the capability to integrate alarm location, floor plans and building data, using the ESRI standard; however this capability will be delayed from the initial deployment, in Phase 2 or later of CADIS implementation.

Comment:

It the intent of the FPS to provide GIS data that contains floor plan and alarm location data. There are approximately 9,000 buildings with multiple floors. The exact number of floor plans that will be provided has not been determined. The alarm points and floor plans are not geospatially referenced. The floor plans are in ESRI format.

9.
General
Please clarify that the Product/Service Description: COMPUTER AIDED DESIGN/MANUFACTURE (CAD/CAM) is for a Configurable COT Computer Aided Dispatch System, not Design?
Language change to B.5.

PSC Code: D307 Automated Information System Design and Integration Services

Comment:

This is not CAD/CAM project. The Product Service Code has been changed from D313 to D307. This is not a Computer Aided Design project.

10.
Section B
Item No. 0001 through 6019
2
Reference to “Computer Aided Design/Manufacture (CAD/CAM)” rather than Computer Aided Dispatch.
The referenced language included in the items description is the default language for the previously selected Product Service Code, which has been changed from D313 to D307.
11.
Section B
B.3 Para 1
15
Per Section B.3, paragraph 1, “The Department of Homeland Security (DHS), Immigration and Customs Enforcement is the sole authority to request services under this contract.” With the transfer of the Federal Protective Service to DHS NPPD in Oct 2009, what role, if any, will NPPD have related to system design and deployment and overall decision making with respect to awarding the contract?
Language change to B.3.

The Department of Homeland Security, ICE and NPPD, will have the sole authority to request services under this contract.

Comment:

ICE will manage this project. NPPD will be involved as a stakeholder. We do not know when or if NPPD will take over this project.

12.
Section B
B.5
15
PSC Code: D313, Computer Aided Design/Mfg Services” does not reflect Computer Aided Dispatch and refers to another type of application.
See language change in B.5. The PSC has been changed. This procurement is for Computer Aided Dispatch and Information System.
13.
Section B
B.5
15
Please clarify PSC – this procurement is for a Computer Aided Dispatch System, not Computer Aided Design system.
See language change in B.5. The PSC has been changed. This procurement is for a Computer Aided Dispatch and Information System.
14.
SOW
2.1
17
FPS is seeking the ability for users to "work offline in the event of connectivity failures, and the capability to continue to work off-line in the event the failure occurs in the middle of a session without any data loss". This requirement would typically be best supported with a distributed architecture which appears to be implicitly prohibited by DHS policy prohibiting Peer to Peer (P2P) architectures. Please elaborate.
See additional language in section 2.1 paragraph 4.

All solutions must meet DHS regulation 4300A.

15.
SOW
2.1 Para 1
17
Do FPS vehicles already contain GPS tracking devices? If so, is the expectation that the new GIS capability will integrate with these systems or will existing Mobile Computing Devices (MCDs) be used as the tracking devices?
Additional language in 2.1 para 1.

FPS envisions future capability to integrate with GPS Vehicle Location devices.

Comment:

The vehicles do not currently have GPS tracking devices.

16.
SOW
2.1 Para 3
17
Per Section 2.1, paragraph 3, “CADIS is expected to integrate with existing Intrusion Detection Systems and Access Control Systems.” What systems are currently used for intrusion detection and access control?
Additional language in 2.1 para 3 and Section 5.9 Interface E.

CADIS will interface with Security Information System (SIS) for processing of all electronic security systems being monitored, including Intrusion Detection System (IDS) and Access Control System (ACS) alarms, and fire alarms.

17.
SOW
Section 2.1
17
Is 911 call taking part of the expected solution or a future enhancement? If part of the initial solution, who will provide the E911 ANI/ALI interface and associated equipment (telephone switch, computer telephony interface, digital voice recorder, TTY modem, etc)? To what extent is the contractor expected to interface to the E911 solution?
No, 911 call taking is not required. There is no interface to E911 in this solicitation.
18.
SOW
Section 2.1 Envisioned Capabilities
17
It is clear that the solution must be a seamless integration of CAD, RMS

and GIS.

The level of functionality expected of the GIS is not as well defined as the functionality of the CAD. Is ICE/FPS interested in a robust GIS that includes 2 and 3D views of building exteriors and interiors, routing of response vehicles , tracking of response vehicles, establishment of cordons, blast and plume modeling and building evacuation modeling? Or are the requirements primarily the establishment of the ESRI database and geocoding?

Language added to section 2.1, second to the last bullet.

CADIS will integrate with an ESRI database and use data provided by that system.

Comment:

The level of functionality expected of the GIS is not well defined and this area needs to be developed.

The requirements are probably the establishment of the ESRI database and geocoding.

19.
SOW
Section 2.1
18
Unlike CAD, RMS is typically not considered a mission critical component of a public safety offering. Does the requirement of Section 2.1 for 99.999% system availability apply to the RMS system?
Language added to 2.1, 2nd bullet.

This availability requirement applies to both dispatch capabilities and record management components.

20.
SOW
Section 2.1
18
If the System is configured for 99.999% availability, what offline capability is required by which users?
Language added to 2.1, 2nd bullet.

There is no requirement for offline capability for dispatch functions. Dispatch functions must be available online in the primary location or the backup location.

21.
SOW
2.1 Paragraph 4
18
What specific functions need to be provided when COOP is engaged at a remote station?

Will local alarm processing be enough to satisfy this requirement with a means to forward the local data to CAD and RMS later, once the servers are back on-line?

Language changed, removed reference to coop in 2.1 para 4

22.
SOW
18
Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) utilizing Big Fix.”

Q: It would be helpful to have information on the types of MCD’s deployed in the field?

Attachment added to the solicitation. MCD specs are an additional document to the solicitation.

23.

Section 2.2 and Section 5.3
19, 24
Section 2.2 suggests that MegaCenters should be considered for primary and backup sites. However, section 5.3 suggests that the design of the application, including development and test environments such that the system can be hosted at the DHS Data Center (or the MegaCenters). To confirm, can either the DHS Data Center OR the MegaCenter be considered for a hosting solution?
Language changes to section 2.2.1 & section 5.3 last bullet.

CADIS will initially be hosted in the FPS MegaCenters and eventually move to the DHS datacenter.

24.
SOW
2.2.1
19
Will the location of the CADIS server be provided with the final RFP or post-award?
Language change to 2.2.1.

CADIS will initially be hosted in the FPS MegaCenters and eventually move to the DHS datacenter.

25.
SOW
2.2.2
19
Will dispatch workstations be provided by FPS as GFE or should they be included in the proposal? If provided by FPS, please provide a hardware and software specification breakdown in the final RFP.
Language added to 2.2.2 (b).

Dispatch workstations are provided and are GFE.

Comment:

Workstation specifications are provided by the vendor and approved by the Government.

26.
SOW
2.2.2
19
With the final RFP, would FPS be able to provide a hardware specification breakdown of the 950 FPS-provided mobile clients to be connected to CADIS, including the primary location of each mobile and how each is connected to the DHS network (RF, Cellular, etc)?
Language change to 2.2.2 (a).

MCD specifications are provided as an attachment.

Comment:

Primary location of each mobile is throughout the United States and its territories.

Language added to 2.2.4

MCD’s will connect to the DHS network via AirCard or LAN.

27.
SOW
2.2.3 Para 1
19
Previous sections mentioned software to mobile clients will be done using existing DHS network and ICE-owned Big Fix utilities. It is clear in the SOW that the contractor will have the responsibility to ensure the application can be pushed to mobile clients. Will the contractor be responsible for direct follow up with each user for errors or will that be accomplished by FPS tech support?
Language added in 2.2.3.

Follow up with individual users for completion of installation will be accomplished by FPS personnel.

28.
SOW
Section 2.2.2.c)
19
What is the expected quantity of concurrent reporting clients?
Section 5.3 paragraph 3 indicates 600 concurrent users.
29.
SOW
Section 2.2.4
19
RFP states “…….software and shall be installed and configured on existing mobile computing devices….” Please provide hardware specifications for current MDT units and to include GPS availability.
See #22.
30.
SOW
3
20
Will a suggested list of COTS/GOTS apps be available as GFI
The Government doesn’t have a suggested list.
31.
SOW
Section 5.2
23
Is it the intent of FPS that the Disaster Recovery Site and the Backup site to be one in the same; if not is the intent that these systems will be co-located at the same facility?
See 5.3 1st bullet

Comments:

Is it the intent of FPS that the Disaster Recovery Site and the Backup site to be one in the same? Not necessarily.

If not is the intent that these systems will be co-located at the same facility? Yes and no.

32.

Section 5.2
23
The draft SOW indicates that the contractor shall provide a “development, test, and documentation” infrastructure to support the CADIS effort. Please clarify the requirements for the documentation infrastructure and where the government intends it to be hosted.
Language chance to 5.2, the last bullet.

Provide a development and testing environment. Documentation will be delivered to the government provided Electronic Library Management System (ELMS).

33.
SOW
Section 5.3
24
Does FPS anticipate that training will be conducted at each of the mega centers with dispatcher, sys admin and LEO training being conducted equally at each location? What is the anticipated maximum student count per training course?
Language added to 5.7.

The Contractor shall propose a blended training approach that provides overall best value and the best approach to training based on the contractor’s experience in providing training for their product.

Language added in 5.7.

Provide dispatch and system administrator training at each of the four MegaCenters. We are looking to the vendor to provide recommendations for training through the use of various training methodologies for the MegaCenters and LEOs dispersed across the nation. We anticipate the need to train approximately 950 LEOs on the use of MCDs. We anticipate the need to train approximately 120 dispatchers and systems administrators at the FPS MegaCenters.

Integrate software that will provide interactive training sessions for users at MegaCenter sites. The training should be accessed directly from CADIS, as opposed to a separate website. A yearly refresher course will also be required.

34.
SOW
Section 5.5
25
In the event of on-site support requirements what is the expected on-site response time.
Language added to 5.5, first bullet.

If vendor support is required on-site, this must be accomplished within 72 hours during normal business hours.

35.
SOW
5.4 Para 1
25
Does the 800,000 records figure encompass records from all four MegaCenters or are there 800,000 records per MegaCenter (i.e. 3,200,000 in total)?
Language change in 5.4 para 1.

The Contractor shall plan and execute a successful data migration and transition effort, migrating a total of 800,000 records from the current legacy DOL and a total of 33,000 records from WebRMS systems to CADIS.

36.
SOW
Section 5.4 Data Migration and Transition
25
a. More information on the file format(s) of the data to be migrated from the legacy system to CADIS would be helpful.

b. Likewise having a description of the legacy system will better enable us to prepare a migration plan.

Language added to 5.4 para 1.

A data dictionary of the WebRMS system file formats will be included as an attachment to this solicitation. File formats for DOL will be defined during the post-award requirements development.

37.

Section 5.6.1
27
The table in SOW Section 5.6.1 Page 27 indicating the number of anticipated SCRs per contract year is incomplete. Will the Government provide a completed table in the final RFP?
Language added to 5.6.1 after para 1. All SCRs will be Cost Plus Fixed Fee. Each SCR will be developed and bid on an as needed basis.
38.
SOW
Section 5.7
27
Can the Govt explain if 'Training Coordination' includes training logistics (selection of locations, timeframes, tech prep of training locations etc) as well?
Language change from the word “coordinate” to “conduct” in 5.7
39.
SOW
5.7 and 7.9
27 and 37
In the SOW paragraph 5.7 there is no mention of web-based training; in paragraph 7.9 in the table on deliverables, web- based training support data in listed.

Please clarify.

Language added to section 5.7 para 2. The Contractor shall propose a blended training approach that provides overall best value and the best approach to training based on the contractor’s experience in providing training for their product.

40.
SOW
5.9 Para 1
29
Technical specifications of proposed interfaces are needed to appropriately estimate costs for the third-party systems identified, especially interfaces A, B and E, as they are FPS or ICE owned systems. When will this information be available? Are these proposals expected with the response to this SOW or at a later date? If so, what date?
Language added to 5.9, last para.

Detailed functional specification for these interfaces will be developed during the functional requirements process.

41.
SOW
Interface A Paragraph 1
29
In the final RFP, please provide interface information for the RAMP system including published interface options and specifications.
Detailed functional specification for these interfaces will be developed during the functional requirements process.
42.
SOW
Interface A
29
Request additional interface and workflow information concerning RAMP.

What is the expected change rate of the current RAMP data; daily, weekly, monthly?

Detailed functional specification for these interfaces will be developed during the functional requirements process.

43.
SOW
Interface B
30
Is it the intent of FPS that the PTS system sends an alarm to the CADIS system when a guard misses a scheduled security check? Or, will the CADIS system be expected to ingest beat and roster information for planning purposes? What is the expected integration?
Detailed functional specification for these interfaces will be developed during the functional requirements process.
44.
SOW
Interface B
30
Request additional interface and workflow information concerning PTS.
Language added to 5.9, last sentence.

Detailed functional specification for these interfaces will be developed during the functional requirements process.

45.
SOW
1
30
PTS Timeline - When will this application be available in production?
Language added to interface B, last sentence.

PTS will be available for PTS integration during the development phase of CADIS.

46.
SOW
Interface E Paragraph 1
31
Are all FPS alarms nationwide funneled into a single SIS central station system? If not, how many SIS systems are currently in use and do all remote stations have an SIS workstation?

Where are the SIS systems physically located, including all SIS alarm monitoring workstations?

Language added in Interface E.

There are four independent SIS systems that will provide alarm data to the CADIS system operating in the four MegaCenters.

The SIS systems, including all SIS alarm monitoring workstations are physically located at the MegaCenters.

47.
SOW
Interface E
31
Is it the intent of FPS to provide a list of geo-located alarm points, or is this information readily available? Will the contractor be expected to gather this information if it’s not readily available?
Language added to Interface E para 1.

The geo-located alarm points are available through the SIS alarm monitoring system.

48.
SOW
Interface G
31
In reference to DHS/ICE geospatial database (optional) – What is the expected integration for this data and how will it be used within the system? Is there a workflow associated with this data, if so can it be provided? How often is it updated and how often would FPS expect it to be updated in the CADIS system?
Language added to Interface G.

The geospatial data will be used by CADIS to display facility and officer locations, traffic maps, street maps, and any other geographic information required by FPS. The interface specifications will be defined during requirements definition phase.

49.
SOW
Interface H
31
Request additional interface and workflow information concerning ICEPIC.
Language added to Interface H.

The interface specifications will be defined during requirements definition phase.

50.
SOW
Interface H Paragraph 1
31
Please provide further detail on the current ICEPIC system, including published interface options and specifications to allow for accurate integration estimates.
Same answer as question 49.
51.
SOW
Section 5.10
32
Can the Government further clarify the purpose and requirements of the COTS tracking system that is required by the contractor?
Language removed in 5.10, bullet & 2 sub bullets.
52.
SOW
Section 6 Key Personnel

While much of the draft solicitation is a requirements/performance based approach, the key personnel section leans toward government direction on “how to” approach the work.

The minimum requirements for the Program Manager and Project Leads limit

Contractors’ capability to provide the best qualified personnel. For example, a contractor may have an excellent candidate for a program manager that has 7 years of experience or has subject matter expertise in everything but radio controlled systems.

Our preference would be for ICE to identify the key personnel positions and let vendors put forward their best candidates.

Language changed in 6.0.

Program Manager – Candidate must have a minimum of 10 years of IT-related program management experience and have experience managing law enforcement dispatch systems, call center databases, and experience managing similar system implementations. PMP Certification preferred.

Project Leads – Candidate must have a minimum of 5 years of IT-related management experience and have experience with law enforcement dispatch systems, call center databases, and experience with similar system implementation.

53.
SOW
7.5 Para 1
35
Is the Project Tailoring Plan simply referencing the standard template within the SLM or will there be one provided by the Government (GFI)? If the latter, when would the Project Tailoring Plan be provided?
Language added to 7.5, para 1.

The Contractor shall review the Project Tailoring Plan (PTP), which will be developed by ICE Systems Architecture after contract award, for the CADIS effort.

The PTP will provide recommendations for any additional tailoring based upon the maturity of their product, with supporting rationale.

54.
SOW
8.0 Paragraph 1
37
What is the purpose of the ten Government issued laptops identified here? Is the intent to use them as MCDs within CADIS? If so, please provide specifications for these units.
Language added to 8.0.

The Government will provide laptops and tokens for Contractor use in developing and testing the system.

MCD specs are an additional document to the solicitation.

55.
SOW
8.0 Paragraph 2
38
Please define the required security clearance for access to the DHS Enterprise Library.
See comment section H.2 of the solicitation for all security clearance requirements
56.
Section L
Section L,

Volume 1, Tab 2

76
“The Offer shall submit a draft Project Management Plan outlining resources, implementation strategies, activities, and milestones necessary to accomplish work specified in the SOW.”

Is the Project Management Plan excluded from the technical proposal 40 page limit?

Yes

57.
Section L
Section L.2
76
Will the government exclude the Past Performance / Corporate Experience write-up from the 40 page limit of the Technical Proposal?
Yes
58.
Section L
L.2 Instructions/ Notice to Offerors; Tab 3 Past Performance
76-77
Of the three similar efforts, two examples should be in proximate relation to each other

such that Offerors can clearly demonstrate how they brought forth improvement and innovation through the use of technology, tools, or work processes from one effort to the other and how that is applicable to the FPS environment and the CADIS effort.

We don’t understand how the phrase “two examples should be in proximate relation to each other” should be interpreted. It appears the intent is to have two examples that resulted in improvements similar to the kind of improvements ICE/FPS expects to achieve in the CADIS effort.

Yes, that is the intent.

59.
Section L
Tab 2 Management Approach / Staffing
76
“The Offer shall submit a draft Project Management Plan outlining resources, implementation strategies, activities, and milestones necessary to accomplish work specified in the SOW.” Will the draft project management plan count toward the 40-page limit?
Yes
60.
Section L
Proposal Due Date, Time, and Location
78
Is February 19, 2010 the planned due date for the Final RFP response assuming release of the Final RFP January 25, 2010?
These dates are going to change.
61.
Section L
Proposal Due Date, Time, and Location

NOTE:

78
“CRDS screening delays deliveries by one to five days.” Assuming release of the Final RFP is January 25. 2010 and due date is February 19, 2010 is only 25 days with 5 days for screening, this will not be sufficient time to provide a quality, comprehensive proposal. We would request an additional 30 days.
The 30 day request is noted. The CRDS date stamps the proposals when they receive them, which verifies that the proposals were received on time. It may take 1-5 days before they get delivered to the Contracting Office.
62.
FRD
2.2.1
5
Request additional interface and workflow information concerning SIS.

Additionally does the current SIS system have the ability to provide information with regard to alarm types to categorize response requirements?

Yes, the answer from question 46 may help.

63.
FRD
2.2.1
5
Approximately how many alarm panels, or alarm aggregation points are included? In addition, approximately how many devices is the system expected to support?
Language added to 2.2.1.

There will be an interface to SIS from each of the CADIS systems in the four MegaCenters. The number of alarm aggregation points is one per CADIS system. SIS provides the capability to automatically detect and export all alarm points to CADIS.

64.

2.2.1
5
Is there sample data available?
Language added to 2.2.1.

SIS interface record formats will be defined in the functional requirements phase.

65.
FRD
2.2.1
5
What existing alarm filtering is currently in place?
Language added to 2.2.1 .

No alarm filtering exists in SIS, all alarm filtering will be done in CADIS.

66.
FRD
2.2
5
Are the alarm systems and associated interfaces at each Megacenter the same?
Yes
67.
FRD
2.2.2
5
Is there sample data available?
No. Sample data is not available.
68.
FRD
2.2.3
5
Is there sample data available?
No. Sample data is not available.
69.
FRD
2.2.3
5
Does the SIS system support the capability to automatically detect and export all of the alarm points for use in the CADIS system?
Language added to 2.2.1.

WAN connectivity and bandwidth between the MegaCenters will be sufficient to support the alarm monitoring capabilities of the COTS product.

Comment:

The “automatically detect and export all of the alarm points” question is unknown.

70.
FRD
2.2.3
5
In reference to Alarm Monitoring, can FPS provide the average daily alarm rates? Does FPS have historical data for peak and seasonal alarm rates and if so, can those be provided?
The rates are not available.
71.
FRD
2.2.4
5
How many of the 7,400,000 annual alarms from SIS resulted in an incident that required a dispatch response?
Language added to 2.2.4.

The number of incidents generated from these alarm signals varies substantially based on the type of alarm, and the number of incidents cannot be predicted.

72.
FRD
2.2.5
5
How many levels are needed?
Language added to 2.2.5.

There are ten alert levels, as defined by SIS.

73.
FRD
2.3.1
6
Can you identify the additional sources that need to be interfaced?
Language added to 2.3.1.

The additional sources to be interfaced will be defined during requirements definition, if interface C (NCIC) is awarded.

74.
FRD
2.4.1
7
Do these areas exist now or will they need to be created? How many ESN’s exist? Are current response assignments available or do they need to be created?
Language added to 2.4.1.

There are approximately 900 LEOs covering approximately 9,000 government facilities. Response assignments will be defined during system configuration.

75.
FRD
2.5.2
8
In addition to caller questions for response is EMD required? Do you have an EMD program currently? What one?
Language added to 2.5.2.

Emergency Medical Dispatch is not required.

76.
FRD
2.5.3
8
What AVL are you currently using?
Language added to 2.5.3.

The AVL system has not been defined as yet, however, whichever AVL solution is selected will meet requirements of the selected COTS product.

77.
FRD
2.5.7
8
Is this for dispatchers immediate playback, administrative look up or both? For instant recall at the position how far back would be required? The system shall provide playback capability to recreate fleet movements

Please clarify what is meant by "playback capability" to recreate fleet movements Language added to 2.5.7.

The system shall provide playback capability to recreate fleet movements for dispatchers, administrative and supervisory review. Playback retention shall be provided within the limits of the COTS product.

78.
FRD
2.5.8
8
Is the infrastructure in place currently? What will be the connection point?
Language added to 2.5.8.

This requirement is necessary for planned future capability. The interface between the existing P25 wireless radio system and CADIS will be defined during system requirements.

79.
FRD
2.5.8
8
What in-use and/or planned P25 wireless radio system(s) will need to be interfaced to CADIS (by provider and version/type)?
Same answer as 78.
80.
FRD
2.5.9
9
Will this be via the APCO-25 Interface? The system shall show real time tracking, the exact

location visited by a vehicle, how long it was there, speeds en route and the time the vehicle left each location

Please describe how this information is anticipated to be captured by and displayed to the user. Is this on a map or is it data that as been tracked through a transaction record for movements as recorded by the dispatcher or through the

LEO using the MDC unit?

Language added to 2.5.9.

The tracking shall be performed as part of the GPS/AVL system that will be deployed at a future date.

81.
FRD
INCIDENT TRACKING

2.6.1

10
The system shall provide the ability to enter information, including LEO initiated “police reports" directly into the RMS from remote sites (field reporting) using desk top computers, laptop computers and Mobile Computing Devices (MCDs)

QUESTION: What wireless infrastructure and bandwidth is available to the Mobile Computing Devices?

Language added to 2.6.1.

Electronic copies of paper forms will not be required. Data entry fields will provide direct input into the RMS component of CADIS. Reports generated from that RMS component will comply with FPS requirements, which will be defined in the requirements definition phase.

82.
FRD
2.6.1
10
For MDC’s, what type of network connection and protocol will these computers have for access/input to CADIS (such as commercial broadband, Wireless LAN hotspots, private radio network)?
Please see the language added to 2.2.4.

MCD’s will connect to the DHS network via AirCard or LAN.

83.
FRD
2.6.1
10
“The System shall provide the ability to enter information, including LEO initiated ‘police reports’ directly into the RMS from remote sites…”

Does DHS require a field reporting solution that provides electronic forms similar to current paper forms or for data entry screens with RMS entry fields?

Language added to 2.6.1.

Electronic copies of paper forms will not be required. Data entry fields will provide direct input into the RMS component of CADIS. Reports generated from that RMS component will comply with FPS requirements, which will be defined in the requirements definition phase.

84.
FRD
2.13
15
Can you clarify what workflows and transactions are being referred to in this section? For example are transactions database transactions and workflows the various business rules that are within an application?
Language added text to 2.13.1.

The system shall provide the user the ability to query CADIS incident status.

85.
FRD
2.13.3
15
At what level? Is this for processing or call handling? Does this refer to making a priority 3 call a priority 1?
Language added to 2.13.3.

The system shall allow users to escalate transaction priority, which will be defined during the requirements definition phase.

86.
FRD
2.13.5
15
How many and what type of definitions need to be provided?
Language added to 2.13.5.

The system shall be configurable to support end-user defined workflows that are available within the COTS product.

87.
FRD
2.15.2
15
What type and capacity is available or dedicated to transport this data?
Language added to 2.15.2.

The network will provide sufficient capability to transfer this data in real time.

88.
FRD
2.16.1
16
2.16.4 requires similar look will these screens be preset or is user definable on login required?
Language added to 2.16.1.

The GUI look and feel will be determined by the capabilities of the COTS product. All screens should be existant in the product being proposed.

89.
FRD
2.16.8
16
How will these calls arrive? Is this system required to provide CPE phone equipment? Is this required to interface to a phone system other than for ANI/ALI? What phone system will be used?
Language added to 2.16.8.

Each facility utilizes its own phone system. Interface requirements will be defined during requirements definition phase. Some existing phone systems are Meridian and Avaya.

90.
FRD
2.16.10
16
What CCTV devices and or systems are expected to be interfaced to the CADIS system? What is the expected workflow as it relates to alarms?
Language added to 2.16.10.

This is considered a future capability, not to be bid on at this time.

91.
FRD
2.16.10
16
How many screens will be needed to support this system per position? Will this be required in the Mega centers, remote offices and mobiles?
Same answer as 90.
92.
FRD
2.17.1
16
Will UTC also be needed to be displayed?
Language added to 2.17.1.

The system shall provide the ability to create reports linked to the specific time zone in which the incident occurred and display UTC.

Please see 2.14.1.

The system shall provide the ability to work with and display a standard, system wide clock, for establishing baseline times (e.g., Coordinated Universal Time (UTC)

93.
FRD
2.17.3
16
Requirement states “The system shall provide the ability to create and send situation reports for a specific incident”

Please provide a sample of a current situation report.

Language added to 2.17.3.

The report will be based on the requirements definition phase.

94.
FRD
INTERFACES
17
QUESTION: Will detailed specifications be provided for all interfaces including data elements, protocol, connectivity to external systems? Will a Use Case be provided to define user expectations?
Added text to Interfaces:

The interface specifications will be defined during requirements definition phase.

95.
FRD
2.18.2.6
18
Requirement mentions the DHS/ICE Geospatial Database containing data in ESRI format

What are the current ESRI toolsets in use and/or current ArcSDE version?

Language added to 2.18.2.6.

Dispatchers will require access to all maps, and LEOs will require access to regional and local maps.

The ESRI toolsets in use will be defined during requirements definition phase.

96.
FRD
2.18.2.6
18
Will the geodatabase be provided as a single nationwide map, or will it be split into subsections, such as by state or region?
Language added to 2.18.2.6.

The Geodatabase will be split into subsections.

97.
FRD
2.2.1,

2.2.2 Geographic locations of clients

18
What WAN connectivity and bandwidth is available between the Mega-Centers, the Rockville Data Center, Dispatch Clients, and Regional / Reporting Clients?
Language added to 2.2.1.

WAN connectivity and bandwidth between the MegaCenters will be sufficient to support the alarm monitoring capabilities of the COTS product.

98.
FRD
2.2.4 Mobile Computing Devices (MCDs):
18
What are the specifications of the existing mobile computing devices?
Attachment added to the solicitation. MCD specs are an additional document to the solicitation.
99.
FRD
4.1 TECHNICAL DOCUMENTS
20
Will the documents listed in this section be made available at the time of the release of the RFP?
Yes.
100.
FRD
3.4.2
22
What will the defined reports be and for what time frame? Will this include Video and Audio files?
Language added to 3.4.2.

The system shall process 90% of defined report transactions in less than 60 seconds based on current canned reports provided in the COTS product.

Comment:

What the defined reports are and video and audio file inclusion are unknown.

101.
FRD
4.0
22
The FRD provides specific counts of various users classes such as system administrators and dispatchers. However, there is not mention of the quantity of RMS clients. What is the expected number of RMS thick clients at the Megacenters? What is the expected number of RMS web-based/ reporting clients at the regional centers?
Language added to 4.0.

All RMS access should be web based. Access to the RMS will be defined through user roles during requirements definition.

102.
FRD
COMMERCIAL OFF-THE-SHELF (COTS) CAD SYSTEM

(4th bullet)

23
This system shall: Provide a means to optimize network traffic.

COMMENT: Specifically the system will optimize network traffic related to data within the system components and to the interface endpoints of the system. Cannot assume responsibility for network traffic provided by outside systems.

Noted.

103.
FRD
4.3
25
Table 4.3 mentions providing “weather information”.

Is this a requirement to provide an interface to an existing weather system? If so, please provide vendor information for weather system.

Language removed, #6

104.
FRD
4.5
26
Does an MSAG exist? Is a SALI needed?
These acronyms do not fit this solicitation.

File details come from the government source that posted it. Updated .