Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF JULY 05, 2014 FBO #4606
MODIFICATION

R -- Requestf for Information - Post Tracking System

Notice Date
7/3/2014
 
Notice Type
Modification/Amendment
 
NAICS
541519 — Other Computer Related Services
 
Contracting Office
Department of Homeland Security, Office of the Chief Procurement Officer, Office of Procurement Operations, Federal Protective Service, 701 Market Street, Philadelphia, Pennsylvania, 19106, United States
 
ZIP Code
19106
 
Solicitation Number
RFIPTS-14-0001
 
Point of Contact
Peter J Andrews, Phone: 215-521-2261
 
E-Mail Address
peter.j.andrews@hq.dhs.gov
(peter.j.andrews@hq.dhs.gov)
 
Small Business Set-Aside
N/A
 
Description
Request for Information Federal Protective Service Post Tracking Solution This is a Request for Information (RFI) issued solely for information-gathering and planning purposes. It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. The U.S. Department of Homeland Security (DHS), Federal Protective Service (FPS) is seeking to identify vendors capable of supporting FPS programs by providing a complete solution to track guard posts or parts of a solution that can satisfy some of the capabilities identified here. Responses to this RFI will not affect a potential vendor's ability to respond to any RFP that may or may not follow, nor will not responding limit participation in any future RFP. Please ensure that any sensitive or protected information is marked as such. By submitting a response, each respondent agrees that any and all costs incurred in generating the RFI response or in support of activities associated with it shall be the sole responsibility of the respondent. The Government shall incur no obligations or liabilities to anyone for any costs or expenses incurred by the respondents in preparing the RFI response. Responses to this RFI are solicited to identify technologies and vendor specific operations and management concepts that would define the vendor's market offering and capabilities, and to determine the commercial market pricing structure for these services. Section 1: Introduction FPS is responsible for providing protection services in more than 9,500 Federal facilities owned or leased by the General Services Administration (GSA) or other Federal Agencies. The primary mission of FPS is the protection of buildings, grounds, and properties, as well as the people who work within and visit them. In approximately 2,500 of the 9,500 buildings, this is done in part through deployment and management of trained and certified Protective Security Officers (PSO). These individuals staff posts, guard buildings, screen visitors, and operate security countermeasures (e.g., magnetometers) throughout the day with FPS employees providing contract oversight. Currently, FPS manually reviews post and certification records to ensure that contract PSO vendors are performing in accordance with the contract. FPS intends to automate this process to continue to improve management and oversight of the PSO program and enable an effective and efficient process to determine, in real time, that PSO posts in facilities are properly staffed by qualified individuals. FPS is looking for a solution that will provide automated information on the identity and qualifications of PSO performing security service's at federal facilities. To do this, it is envisioned that a solution will need to deliver the functional capabilites below: • Confirm the identity of an individual attempting to staff a post • Confirm that the individual is authorized and qualified to staff a post by validating that their credentials (training, certifications, and suitability) meet the specific requirements of that post. This includes approximately 30 credentials (e.g., baton training, firearm training, CPR certification, etc.). • Capture the time that an individual begins to staff a post, transitions to another post, and leaves a post • Generate a notice to a designated individual within FPS management to alert them if a post is unstaffed • Gather data needed to validate contractor invoices in order to ensure that the services that have been provided meet the contracted level of service. Section 2: Scope 2.1 Capabilities Required Below are important capabilities that FPS believes are needed in order to provide oversight of individuals who staff FPS posts. These capabilities are the basis for the questions used in the Post Tracking System RFI Response Form regarding how the proposed solution would address FPS needs. • Capability for an individual to check in and check out when attempting to staff a post • Capability to authenticate the identity of an individual attempting to staff a post • Capability to ensure that a post is properly staffed with authorized and qualified personnel. This means validating that an individual meets all requirements before starting work at a Federal facility, including the following: o An individual is assigned to the specific facility or contract for the post he/she is about to staff o An individual has completed the required training to staff the post o An individual has obtained the required certifications to staff the post o An individual has the required suitability to staff the post • Capability to notify an individual who is checking in at a post that they are not authorized or qualified to staff that post, and handling situations that arise where an individual is wrongly denied authorization to check in and staff a post • Capability to record the time when an individual goes on or off a post • Capability to identify that a post is not staffed or is improperly staffed, and to notify a designated FPS individual • Ability to maintain the solution after implementatration (this includes customer and technical support) • Capability to provide reporting to FPS on post staffing levels for a given time period to ensure that the hours FPS is billed for services matches the time that individuals actually worked • Capability to enter, manage, and maintain data for each individual regarding their training and certifications • Capability to enter, manage, and maintain data for the requirements needed to staff each post. 2.2 Other Considerations Beyond the primary functionality, the items below will be considered to determine whether a solution proposed may be a viable alternative for the FPS post tracking capability. When providing a description of and details about the solution, the following considerations should be addressed when applicable. • Ease of deployment • Ease of use for guards • Ease of report generation • Ease of management and maintenance of the solution • Amount of new development the solution requires • Effectiveness of data protection, including the Personal Identification Information (PII) of guards • Accuracy of performing a specific capability • Speed of performing a specific capability • Scalability of the solution. Section 3: RFI Responses and Instructions The details provided by responses to this RFI will assist FPS in refining the necessary scope of work. Information offered will also help define the procurement strategy selected that represents the best interest of the Government. In submitting responses, please include the full company name and address, applicable POC e-mail address, and the DUNS (Data Universal Numbering System) and other information requested on the FPS Post Tracking System RFI Response Form. Please ensure that the responses only address the questions provided in this RFI. 3.1 RFI Schedule The key dates are provided below. • Respondent clarification questions on the RFI due by: July 14, 2014; 11:59 PM ET • RFI Responses due by July 28, 2014: 11:59 PM ET. 3.2 Questions about the RFI If any clarification is needed regarding the content of the RFI, please submit questions in writing to Peter J. Andrews, peter.j.andrews@hq.dhs.gov no later than 11:59 ET PM on July 14, 2014. These should be in an MS Word document, formatted in Arial font 10 and single spaced. Questions should be sequentially numbered, and the total of all questions should not exceed 2 pages in length. Responses to questions should be available within 5 business days after receipt and made available to all potential respondents. 3.3 RFI Response RFI Responses should be submitted using the attached PTS RFI Response Form. Responses must be submitted no later than 11:59 PM ET on July 28, 2014 to Peter J. Andrews, peter.j.andrews@hq.dhs.gov. Detailed information and explanations about each specific question/topic must be provided in the appropriate cell in the "Response Detail" column on the PTS RFI Response Form. Each cell will expand to allow as much space as needed to address the question/topic posed; however, the total number of pages for the overall RFI response should not exceed 15 pages. All response details must be provided in Arial font 10 and single spaced.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/notices/ddab500a717eb098e1581ca0dd13f1ea)
 
Place of Performance
Address: Nationwide, United States
 
Record
SN03414783-W 20140705/140703235918-ddab500a717eb098e1581ca0dd13f1ea (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  © 1994-2020, Loren Data Corp.