FBODaily.com | FedBizOpps: MOD | D | RFI EXCHANGE for PEO EIS Information Exchange Day, ****30 July 2013****, to support DoD Biometrics. See update of data requested for JPIv2 and BEC Increment 1.

FBO DAILY - FEDBIZOPPS ISSUE OF JULY 21, 2013 FBO #4257
MODIFICATION

D -- RFI EXCHANGE for PEO EIS Information Exchange Day, 30 July 2013, to support DoD Biometrics. See update of data requested for JPIv2 and BEC Increment 1.

Notice Date: 7/19/2013
Notice Type: Modification/Amendment
NAICS: 541512 — Computer Systems Design Services
Contracting Office: ACC - New Jersey, Center for Contracting and Commerce, Building 10 Phipps RD, Picatinny Arsenal, NJ 07806-5000
ZIP Code: 07806-5000
Solicitation Number: W15QKN13R0191
Response Due: 7/25/2013
Archive Date: 9/17/2013
Point of Contact: Carmel Costa, 609/562-7041
E-Mail Address: ACC - New Jersey
(carmel.m.costa.civ@mail.mil)
Small Business Set-Aside: N/A
Description: You are invited to a Department of Defense (DoD) Biometrics Information Exchange hosted by Program Executive Office Enterprise Information Systems (PEO EIS) to facilitate Army and industry collaboration and information exchange of Biometric strategies. This event is intended to advance collaboration between DoD Biometric programs and industry partners in the areas of: Joint Personnel Identification Version 2 (JPIv2), Biometrics Enabling Capability (BEC) Increment (Inc) 1, and Program Management Operational Support (PMOS). The JPIv2 capability will provide the operator the ability to collect, match, store, reference, and transmit a biometric modality and/or modalities of face, iris, fingerprints, and collect voice. The system will support a myriad of operational mission sets, ranging from a tactical austere environment to a mature, established Forward Operating Base. To support this range of mission sets, the biometric capability proposes the need for a man portable variant and a mobile variant. The BEC Inc 1 effort provides the DoD with an authoritative biometric enterprise database repository. This specific Information Exchange is focused on the acquisition to support the development and deployment of BEC Inc 1 to provide enhanced capability to the current DoD Biometrics repository. The PMOS effort(s) will provide DoD Biometrics and its subordinate PMs with support in program management and engineering. Specific areas of program management include: project operations, business management, strategic planning and analysis, administration, acquisition management, logistics management, budget, cost, and scheduling. Specific areas of engineering include systems engineering and risk management. ***LOCATION*** The Information Exchange will take place on Tuesday, 30 July 2013, 0900-1600, at the Wood Theater, 6050 Abbott Road, Fort Belvoir, VA. There are no registration fees and there is no hosted luncheon or beverage service; however, attendees MUST pre-register. Seating capacity is limited and we request no more than two representatives from each company attend. ***AGENDA*** 0900 - 0930 - Welcome Remarks (Mr. Douglas K. Wiltsie, PEO EIS) 0930 - 1045 - JPI Briefing 1045 - 1055 - Break 1055 - 1125 - BEC Inc 1 Briefing 1125 - 1130 - (Breakdown/Set-up Break) 1130 - 1200 - PMOS Briefing 1200 - 1310 - Lunch Break 1310 - 1400 - JPI Panel Discussion 1400 - 1410 - Break 1410 - 1450 - BEC Inc 1 Panel Discussion 1450 - 1500 - Break 1500 - 1530 - PMOS Panel Discussion 1530 - 1600 - Closing Remarks To register for the event, please use the site below: http://www.cvent.com/d/4cqhsj/ Points of Contact: For registration questions, please contact Ms. Jo Manson by e-mail at jo.w.manson2.ctr@mail.mil or phone: 703-806-3980. For event-specific questions, please contact Ms. Erin Buechel Wieczorek by e-mail at erin.b.wieczorek.civ@mail.mil or phone: 703-806-2195. In order to get the most robust dialog related to INFO EXCHANGE, scheduled ****30 July 2013****, the original Notice, posted on 03 July 2013, under reference number W15QKN13R0191 is hereby modified. 1. The purpose of this modified notice is the following: a. Provide clarification on the classification codes and NAICS codes for the DOD Biometric Programs that will be discussed; b.Update the data contained in Joint Personnel Identification, version 2 (JPIv2); (and) c.Update the data contained in Biometrics Enabling Capability (BEC) Increment 1. 2. The Government intends on utilizing the below classification codes and NAICS codes: a. Joint Personnel Identification, version 2 (JPIv2) classification code: D-Information Technology services, including telecommunications services. NAICS CODE: 334118- Computer Terminal and other Computer Peripheral Equipment Manufacturing b. BEC classification code: D-Information Technology services, including telecommunications services. NAICS CODE: 541512 -Computer System Design Services c. Program Management Operation Support (PMOS) classification code: D-Information Technology services, including telecommunications services. NAICS CODE: 541519- Other Computer Related Services 3.The following changes were made to JPIv2: a. Provide clarification on the description section pertaining to industry feedback on the feasibility of a Commercial -off-the-Shelf (COTS) and Non-Developmental Item (NDI) acquisition approach; b. Removal of Engineering and Manufacturing Development information contained in submission instructions section; c. Increase the page limitation in the submission instructions section; (and) d.Provide file type instructions to submit white paper. 4. The BEC Increment 1 document is hereby removed in its entirety and replaced. 5. No changes were made to the PMOS. 6. Please utilize the following version to prepare response to the Government for either JPIv2 or BEC Increment-1. This NEW version supersedes the previous version for participating potential offerors to follow. REQUEST FOR INFORMATION (RFI) FOR JOINT PERSONNEL IDENTIFICATION, VERSION 2 (JPIV2) 12 July 2013 1.DESCRIPTION. This Request for Information (RFI) is to conduct market research on industry's product capabilities to meet the Joint Personnel Identification, version 2 (JPIv2) top-level requirements and to seek industry's feedback on the feasibility of a Commercial-off-the-Shelf (COTS) and Nondevelopmental Item (NDI) acquisition approach. The Government does not intend to award a contract based on this Request for Information (RFI). Any response will be treated as information only and not a proposal. Responses will be separated from, and have no bearing on proposals submitted to any future formal Request for Proposal (RFP). Eligibility to participate in a future acquisition does not depend upon your white paper submission to this notice. Participation in response to this announcement is voluntary, and participants shall not be compensated. If you submit proprietary information, you must clearly mark quote mark PROPRIETARY quote mark on every sheet containing such information and segregate the Proprietary information to the maximum extent practical from other portions of your response (e.g. use an attachment or exhibit). Respondents are responsible for adequately marking Proprietary information in their response. The Government intends to use non-Government (contractor) support personnel as Subject Matter Experts (SMEs) to help the Program Management Office (PMO) review the RFI responses, including review of any marked or unmarked proprietary information. The non-Government (contractor) support personnel include CACI Enterprise Solutions Inc., MITRE Corporation, LMI, and SciTech Services. All contractor support personnel have executed Non-Disclosure Agreements (NDAs) with the Government and are on file with the Government. Response to this RFI constitutes acknowledgement and agreement that the information you provide, including any marked or unmarked proprietary information, may be disclosed to these non-Government (contractor) support personnel. 2.PROGRAM OVERVIEW. The purpose of JPIv2 is to provide the Department of Defense (DoD) with a tactical biometrics collect, match, store, and share capability, exploiting identity information; providing a combat multiplier referred to as identity dominance. The JPIv2 capability will consist of two variants, a man portable (hand-held) version for use in the field and a mobile version for forward garrison use. The mobile system will be optimized for enrollments, analysis, referencing, and producing/verifying credentials at fixed site locations. The man portable system will be ruggedized, lightweight, and support dismounted operations. The Government intends to procure approximately 823 mobile and 4,841 man portable variants during the full deployment phase. The JPIv2 capability may replace selected biometric collection systems within the DoD and provide an enduring DoD tactical biometrics collection capability. JPIv2 is currently designated as Acquisition Category (ACAT) Information Assurance (IA) Major Automated Information System (MAIS) program. 3.SUBMISSION INSTRUCTIONS. The Government is conducting on-going market research and analysis to develop and support the JPIv2 acquisition strategy. To achieve a more affordable solution, the Government is seeking information to support the feasibility of a COTS and NDI acquisition approach. Therefore, the JPIv2 PMO is soliciting industry inputs through this RFI. The Government requests interested parties submit white papers that cover the following technical and business areas of interest: a)Based on the draft JPIv2 top-level requirements identified in APPENDIX A, identify the DoD unique requirements that are not consistent with your commercial products or nondevelopmental items. b)What are the key cost drivers in your COTS or NDI products? What are the potential opportunities to lower production costs and achieve a more affordable solution? c)What are your plans to evolve your hardware product lines in the next 12 to 18 months? What new features or capabilities do you plan to include? d)What are your plans to evolve your software product lines in the next 12 to 18 months? What new features or capabilities do you plan to include? e)What current and/or emerging biometric capabilities do you see trending in the current biometric market place? Do you see DoD's anticipated biometric procurement quantity large enough to influence the overall trend in the market? f)What are the top challenges in evaluating, integrating and testing COTS in Tactical Biometrics Systems (e.g. Government networks, hardware and software integration)? g)The JPI Program Management Team is contemplating participation in the Army-sponsored Network Integration Evaluation (NIE) event in the future. What is your experience in NIE? Would your company consider investing your resources to participate in an NIE event? What sort of cash flow/return on investment would be required to justify your participation in a JPIv2 NIE event? What potential benefits and/or impacts do you see resulting from the JPIv2 System participation in NIE? h)What are the risks associated with a COTS and/or NDI acquisition approach? What barriers would your company encounter? What cash flow/return on investment would be required to overcome such barriers? Provide recommendations to minimize the risk. i)JPIv2 will require Information Assurance (IA) Certification and Accreditation (C&A) for multiple networks. What recommendations can you provide regarding cost-effective and timely development of DoD IA Certification and Accreditation Process (DIACAP) artifact packages? j)If a COTS and/or NDI acquisition approach is chosen, what is your anticipated role in the JPIv2 effort (e.g., prime, sub, team member, etc.)? k)What is your Intellectual Property (IP) business model, to include usage rights and any restrictions for this type of effort (e.g., enterprise license, node-lock, etc.)? Include Technical Data Package (TDP) availability associated with your commercial products or NDI. l)What are your standard warranty practices and limitations for this type of product? How does your company handle non-warranty repairs? m)What is your sustainment model (e.g., % of purchase price, per device cost, etc.) for this type of product? What type of sustainment package (including repair parts availability and lead times, surge capability, documentation, and pricing) do you offer for your commercial or NDI products? n)What is your business base for tactical biometrics devices? How much of your business base is commercial versus Government? o)The Government contemplates procuring approximately 823 mobile and 4,841 man portable variants. What is your strategy in satisfying the capability for the portable (handheld) and mobile requirements? p)What is your open system approach to architecture for inserting new or modified algorithms in JPIv2? q)Do your commercial products or nondevelopmental items have the ability to interoperate with the DoD authoritative database currently known as the Automated Biometric Identification System (ABIS)? r)What are your overall concerns? Submit a white paper limited to a maximum of 25 pages, excluding the cover page and appendices. The cover page must show: company name and address; primary point of contact and one alternate; telephone number and e-mail address; DUNS number; Commercial And Government Entity (CAGE) code; North American Industry Classification System (NAICS) code and secondary NAICS code; small business category and size standard for this NAICS code, if applicable; and Facility clearance, and to what level. All information submitted to ACC-NJ POC must reference W15QKN-13-R-0191/JPIv2. Submit your white paper in electronic format (i.e. Microsoft Word or Adobe Acrobat compatible) to Ms. Carmel Costa, Contract Specialist, at carmel.m.costa.civ@mail.mil, no later than 25 July 2013. The Government will not accept classified information. Questions relative to this JPIv2 RFI shall be addressed via email to Ms. Carmel Costa, Contract Specialist, at carmel.m.costa.civ@mail.mil, no later than 19 July 2013. To assist with these RFI questions, the following appendices are included: APPENDIX A: Draft JPIv2 Top-Level Requirement (TLR) list APPENDIX B: Network Integration Evaluation (NIE) Information Sheet 4.BIOMETRICS INFORMATION EXCHANGE. As part of the Government's on-going market research efforts, the Government is hosting a Biometrics Information Exchange event with an opportunity for industry to participate in a JPIv2 Question and Answer Panel Session. Active participation and questions during this event will help to refine the JPIv2 acquisition strategy. APPENDIX A. DRAFT JPIV2 TOP-LEVEL REQUIREMENT (TLR) LIST TLR #Requirement TitleDescription 1StandardsThe system shall comply with protocols and standards IAW the DoD Information Technology Standard Registry (DISR). 2Flat Fingerprint Match RateThe [mobile] system shall match 10 flat fingerprint images against a database of 450,000 identities in less than or equal to 5 minutes. 3Flat Fingerprint Match RateThe [portable] system shall match 10 flat fingerprint images against a database of 100,000 identities in less than or equal to 120 seconds. 4Iris Match Rate The [mobile] system shall match 2 iris images against a database of 450,000 identities in less than or equal to 35 seconds. 5Iris Match Rate The [portable] system shall match 2 iris images against a database of 100,000 identities in less than or equal to 30 seconds. 6Match Alerts/NotificationsThe system shall provide match alerts/notifications for biometric matches. 7Match Biometrics - Authoritative SourceThe system shall match collected biometrics data with an Authoritative Source via a LAN or WAN connection. 8Prioritize Match SequenceThe system shall allow the operator to prioritize the modalities for a local match. 9Rolled Fingerprint Match RateThe [mobile] system shall match 10 rolled fingerprint images against a database of 450,000 identities in less than or equal to 5 minutes. 10Rolled Fingerprint Match Rate The [portable] system shall match 10 rolled fingerprint images against a database of 100,000 identities in less than or equal to 120 seconds. 11Iris Images - Store Single ImagesThe system shall store collected iris images from the right and left eyes as two separate digital images. 12Storage - Remove DataThe system shall allow stored data to be removed/discarded, including biometric and mission data. 13Store Biometric Files The [mobile] system shall locally store 450,000 identities. 14Store DataThe system shall locally store biometric data and associated biographical and contextual data. 15Associate DataThe system shall associate collected biographical and contextual data with the appropriate biometric subject. 16Emerging Biometric ModalitiesThe system shall be capable of upgrading the collection capabilities and integrating new emerging biometric modalities as required. 17Facial Images - AutofocusThe system shall automatically focus on the face of a biometric subject for facial image collection. 18Facial Images - Collect DistanceThe system shall collect facial images at a standoff distance of less than or equal to 2 meters. 19Facial Images - Collect Distance The system shall collect facial images at a standoff distance of greater than 2 meters. 20Facial Images - Collect FrontalThe system shall electronically capture facial images in accordance with DoD EBTS. 21Fingerprint Images - Collect FlatThe system shall electronically collect, by direct physical contact with a subject, single-finger flat fingerprint images. 22Fingerprint Images - Collect RolledThe system shall electronically collect, by direct physical contact with a subject, single-finger rolled fingerprint images. 23Fingerprint Images - Sequence CheckThe system shall provide sequence checking capability for fingerprint images. 24Fingerprint Images - Collect SlapThe system shall electronically collect, by direct physical contact with a subject, multiple-finger slap fingerprint images. 25Fingerprint Images - Collect StandardsThe system shall electronically capture and transmit images in accordance with the FBI EBTS version 9.3. 26Iris Images - Bifurcate DualThe system shall bifurcate dual iris images if a single image of both the left and right eye is captured. 27Iris Images - CollectThe system shall electronically collect single, dual and/ or simultaneous dual iris images. 28Iris Images - Collect LightingThe system shall collect iris images in lit and unlit conditions. 29Iris Images - Collect Single The system shall collect single iris images at a standoff distance of greater than 2 meters. 30Palm print Images - CollectThe [mobile] system shall collect palm print images. 31Quality Check OverrideThe system shall allow the quality check to be overridden by the collector/operator on a case-by-case basis. 32Quality IndicatorThe system shall provide an indicator with quality check results. 33Sustainment Operational AvailabilityThe system shall have an Operational Availability (AO) greater than or equal to 95 percent. 34Sustainment Material AvailabilityThe system shall have a Materiel Availability (AM) greater than or equal to 80%. 35Security - Hardware TokensThe system shall use National Security System (NSS) PKI hardware tokens to access SIPRNet. 36Security Classification DisplayThe system shall appropriately display the security classification of the information being viewed. 37JPIv2 to JPIv2 SynchronizationThe system shall synchronize with other biometric collection systems. 38Removable Storage For All Local DataThe system shall have the capability to transfer all locally stored data to removable media. 39SynchronizationThe system shall provide Watchlist synchronization with the biometrics enterprise via a LAN or WAN. 40Synchronization NotificationThe system shall notify the operator, upon initial boot up and a network connection, of any newly loaded records or watchlist updates. 41Synchronization Update CustomizationThe system shall allow the operator to customize the time increment for watchlist synchronization. 42Watchlist ExportThe system shall export watchlists. 43Watchlist ImportThe system shall import watchlists. 44Watchlist ManagementThe system shall manage multiple watchlists. 45Embedded TrainingThe system shall include embedded training for all functions and for component and system level operational set-up and recovery procedures. 46Modes - TrainingThe system shall provide a dedicated training mode. 47Training - Reach BackThe system shall reach-back to a help desk for training assistance. 48Materiel ReliabilityThe system shall have a Materiel Reliability (MR) greater than 95% for completing a 72 hour mission. 49Mean Corrective Maintenance TimeThe system shall have a Mean Corrective Maintenance Time (MCMT) of less than 4 hours. 50Mean Time Between Operational Mission FailuresThe system shall have a Mean Time Between Operational Mission Failures (MTBOMF) greater than 1,440 hours. 51Physical Characteristics - DimensionsThe [mobile] system shall have dimensions of less than or equal to 14 inches by 14 inches by 1 inch. 52Physical Characteristics - Dimensions The [portable] system shall have dimensions of less than or equal to 5 inches by 4 inches by 4 inches. 53Physical Characteristics - Weight The [mobile] system shall weigh less than or equal to 10 lbs. 54Physical Characteristics - Weight The [portable] system shall weigh less than or equal to 2 lbs. 55Material Exposure to Extreme Sand - Blowing DustThe system shall withstand exposure to extremely dusty/windswept environments without operational or materiel degradation in accordance with MIL-STD 810G. 56Ruggedness The system shall meet environmental and ruggedization standards in accordance with MIL-STD-810G. 57NetworkThe system shall receive and maintain an Authority To Operate/Authority To Connect for DoD NIPRNET and SIPRNET. 58Latent Print Match ResponseThe system shall receive latent fingerprint match report via automated method from the biometrics enterprise. 59IdentificationThe system shall perform local identification (1:n). 60Identification FARThe system shall provide a False Acceptance Rate (FAR) of 0.5% for identification. 61Identification FRRThe system shall provide a False Rejection Rate (FRR) of 0.1% for identification. 62VerificationThe system shall perform local verification (1:1). 63Verification FARThe system shall provide a False Acceptance Rate (FAR) of 0.1% for verification. 64Verification FRRThe system shall provide a False Rejection Rate (FRR) of 0.5% for verification. 65Failure to Acquire - Fingerprint ImagesThe system shall provide a Failure to Acquire Rate (FTAR) of less than or equal to 1% for fingerprint images. 66Failure to Acquire - Iris ImagesThe system shall provide a Failure to Acquire Rate (FTAR) of less than or equal to 1% for iris images. 67Failure to EnrollThe system shall provide a Failure to Enroll Rate (FTER) of less than or equal to 5%. 68Associate Biometric SamplesThe system shall show relationship linkage between identities from multiple biometric subjects. 69Report GenerationThe system shall provide tailorable/configurable electronic reports. 70Data De-Confliction - Human-In-The-Loop - UpdatesThe system shall provide Human-in-the-Loop (HITL) data de-confliction of locally stored files and new/updated biometric identities. 71Collect CitizenshipThe system shall have a field to identify the appropriate citizenship of all persons enrolled through the device. 72Geo-Location - Coordinate System - GPSThe system shall provide Geospatial Positioning System (GPS) geo-location coordinates. 73Voice Sample - Collect The [mobile] system shall collect voice samples when operating in controlled environmental conditions. 74Match Threat Analysis - RequestThe system shall be capable of submitting a request for ad hoc threat analysis and recommended action. 75Forensic Data - Case File Change - DocumentationThe system shall provide permanent documentation of all access and record modifications to a case file, or maintain an audit trail to support legal chain of custody requirements. 76Digital Media Collection - PDAThe system shall collect digital media from personal digital assistant (PDA) devices. 77Digital Media Collection - PDA - File FormatThe system shall collect digital media in a file format compatible with linking, attaching, and/or embedding the files into the overall event After Action Report submission into the authoritative source. 78Digital Media Collection - PhonesThe system shall collect digital media from satellite/cell phones. 79Database Compatibility - SeaportThe system shall collect data and information compatible with the U.S. Navy's SeaPort database. 80Time to Set UpThe system shall have a demonstrated set-up time of less than 5 minutes. 81Biometric Collection Quality MetricsThe system shall incorporate quality metrics on each biometric modality collected using approved metrics in accordance with INCITS M1 quality standards. 82EnvironmentalThe system shall be positively buoyant in its case/transport packaging. 83Communications - WirelessThe system shall transmit and receive data via secure and encrypted wireless communications systems. 84Components - Device SupportThe system shall support plug and play of multiple vendor collection peripherals per modality. 85Security - Data-at-RestThe system shall support DoD approved data at rest solutions sufficient to protect Personally Identifiable Information. 86Security - Level 4 AuthenticationThe system shall provide Level 4 authentication for accessing the Authoritative Source as defined in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-63. 87Security - NIAPThe system shall have components that are National Information Assurance Partnership (NIAP) certified. 88Security - PKIThe system shall use certificates from the DoD Public Key Infrastructure (PKI). 89EBTS - ConformanceThe system shall conform to the mandatory features for EBTS transactions, as defined by the Type of Transaction (TOT) in the DoD EBTS Application Profile. 90EBTS - ShareThe system shall electronically transmit data IAW DoD EBTS (current standard v2.0, emerging v3.0) 91CertificationThe system shall have its EBTS compliance certified by Joint Interoperability Test Command. 92NetworkThe system shall have its interoperability certified by Joint Interoperability Test Command, as per DoDI 4630.8, section 5.8.12.1. 93Store DataThe system shall locally store biometric data and associated biographical and contextual data. APPENDIX B. NETWORK INTEGRATION EVALUATION (NIE) INFORMATION SHEET The Network Integration Evaluation is a series of semiannual Army sponsored events in which soldiers perform simulated field environment evaluations of network, hardware/software, communications and command controls of emerging Army programs and technologies. During the evaluations, the NIE TRIAD comprised of the Brigade Modernization Command (BMC), the Army Test and Evaluation command (ATEC), and the System of Systems Integration (SoSI) Directorate conducts parallel Limited User Tests of several select Army programs of record (PORs). In addition to the POR testing, the evaluation exercise will also assess participants' potential developmental and emerging networked capabilities to fill identified Army technology Gaps, to include possible integration with POR equipment. The intent of NIE is to involve industry participation, resources, knowledge, and solutions to fill these identified Capability Gaps. Extensive radio/signal communications testing will be held at laboratories at Aberdeen Proving Ground (APG), MD, while NIE field exercises will be primarily conducted at Ft. Bliss, TX and White Sands Missile Range (WSMR), NM. REQUEST FOR INFORMATION (RFI) FOR BIOMETRICS ENABLING CAPABILITY (BEC) INCREMENT 1 12 July 2013 1. DESCRIPTION: This Request for Information (RFI) is to conduct market research on industry's capabilities to meet Biometrics Enabling Capability (BEC) Increment 1 and seek industry's feedback on top level requirements. The potential top level system requirements are found in Appendix A. The Government does not intend to award a contract based on this Request for Information (RFI). Any response will be treated as information only and not a proposal. Responses (questions) will be separated from, and have no bearing on proposals submitted to any future formal Request for Proposal (RFP). Eligibility to participate in a future acquisition does not depend upon your submission to this notice. Participation in response to this announcement is voluntary, and participants shall not be compensated. If you submit proprietary information, you must clearly mark quote mark proprietary quote mark on every sheet containing such information and segregate the Proprietary information to the maximum extent practical from other portions of your response (e.g. use an attachment or exhibit). Respondents are responsible for adequately marking Proprietary information in their response. The Government intends to use non-Government (contractor) support personnel as Subject Matter Experts (SMEs) to help the Program Management Office (PMO) review the RFI responses(questions), including review of any marked or unmarked proprietary information. The non-Government (contractor) support personnel include CACI Enterprise Solutions Inc., MITRE Corporation, and LMI. All contractor support personnel have executed Non-Disclosure Agreements (NDAs) with the Government and are on file with the Government. Response to this RFI constitutes acknowledgement and agreement that the information you provide, including any marked or unmarked proprietary information, may be disclosed to these non-Government (contractor) support personnel. 2.PROGRAM OVERVIEW: BEC Increment 1 will process fingerprint, iris, facial, palm print, and latent data in a system that functions to support the full spectrum of DoD missions and ensure interoperability and full interface capabilities with DHS, Federal Bureau of Investigation (FBI) and other potential agencies. BEC Increment 1 will provide matching, storing, reference and sharing capabilities for these modalities to support DoD forces. The fundamental functions of BEC Inc 1 are to process, match, store, share, reference, and manage standardized biometrics and related contextual data, in the authoritative database. BEC Inc 1 will facilitate on-demand access to Watchlist data. These fundamental functions provide critical information that directly supports user decide and/or act requirements. BEC Increment 1 is currently designated as Acquisition Category (ACAT) Information Assurance (IA) Major Automated Information System (MAIS) program. The Government is moving toward a preferred Engineering Alternative that incorporates the following: Platform as a Service (PaaS) Service Model; Two approaches for implementing BEC Inc 1 are being considered: Army Data Center and Private Cloud. PaaS provides the underlying infrastructure, including network, servers, operating systems, and storage; (and) A System/Software Integrator will be responsible for creating and deploying biometric software applications/services to the PaaS environment. PM BEC will fine tune the assessment of each approach through collaboration with industry and the stakeholder/user community. The expectation is that implementation approaches provided herein are viable and will be included in ensuing RFPs. 3.POTENTIAL AREAS OF INTEREST: During the Information Exchange event the Government contemplates providing clarification to the following areas of interest and Top Level Requirements (Appendix A). The Areas of Interest are provided below: a)Single and Multi Biometric Fusion to increase identification confidence of individuals to reduce human verification workloads. b)Biographic or Contextual Fusion to combine with biometric match results identification of individuals. c)Solutions in the market place to provide for easy implementation of multi vendor matching algorithms? d)Solutions for commercial off the shelf biometric workflow management. e)Cost effective alternatives to provide continuity of operation capabilities across multiple data centers. f)Impacts of biometric matching in a virtualized environment. g)Options for application profile builder that takes EBTS 3.0 and lets stakeholders build a customizable version of EBTS, for their operational use. h)Cross Domain Solutions (CDS) that enables sharing of unclassified biometrics data across security domains (SECRET to Unclassified and Unclassified to SECRET). i)With interoperability mandates going beyond Department of Justice (DoJ) and Department of Homeland Security (DHS) what type of mechanism can be put into place to limit the responses to outside organizations and international partners. The solution should be flexible, scalable, easily configured, and cost effective. j)Big data use cases for biometric systems, and other positive benefits. 4.SUBMISSION REQUIREMENTS: The Government is not requesting a white paper at this time. However, the Government is requesting questions pertaining to clarification, risks, cost drivers, scheduling/methodology, and affordability for the Areas of Interest and top level requirements identified in #3 and Appendix A within this attached document. All information submitted to ACC-NJ POC must reference W15QKN-13-R-0191/BEC. Submit your questions in electronic format (i.e. Microsoft Word or Adobe Reader compatible) to Ms. Carmel Costa, Contract Specialist, at carmel.m.costa.civ@mail.mil, no later than 4:00PM EST on 25 July 2013. The Government will not accept classified information. APPENDIX A. DRAFT BEC TOP-LEVEL REQUIREMENT (TLR) LIST TLR #Requirement TitleDescription 1Modalities2D Face, Finger, Iris, Palm, and Latent Print Examination 2Storage50 Million biometrics DoD EBTS enrollments, scalable to 100 Million biometrics DoD EBTS enrollment 3Submissions 45,000 transactions per day, scalable to 160,000 transactions per day 4Match Response Automatic High Priority match/no match less than 5 Min (Up to 9,000/day) 5Match Processing Query database using contextual or biographic data fields 6Match Processing Fusion matching for combination scores of multiple modalities 7Bulk EnrollmentsProcess 10K a day Bulk Enrollments/Fingerprint Cards from non-network submissions 8WatchlistMulti-modal watchlist that contains template biometrics records and is customizable by users including choice of templates or images 9Data RecoveryCOOP - MAC 2 Sensitive Certification (Mission / Business Essential functions less than 24 hrs, Receive/Store submissions less than 4hrs) 10StandardsSupport DISR and DoD EBTS standards and backwards compatibility 11Privacy/Information AssuranceComply with privacy and identity protection policies Comply with applicable Federal, DoD and Army information assurance policies 12AccessSupport NIPR/SIPR Web Access 13Operational Availability greater than 98% THIS UPDATED NOTICE IS TO CORRECT PEO EIS/BIOMETRICS INFORMATION EXCHANGE DATE. EVENT IS 30 JULY 2013. THERE WAS A TYPO IN THE PREVIOUS AMENDMENT.
Web Link: FBO.gov Permalink
(https://www.fbo.gov/notices/a23a20dd5cff1e41048021be8921dbca)
Place of Performance: Address: PEO - EIS (Wood Theater) 6050 Abbott Road Fort Belvoir VA; Zip Code: 22060
Record: SN03122640-W 20130721/130719235223-a23a20dd5cff1e41048021be8921dbca (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 |

Loren Data's SAM Daily™

D -- RFI EXCHANGE for PEO EIS Information Exchange Day, ****30 July 2013****, to support DoD Biometrics. See update of data requested for JPIv2 and BEC Increment 1.

D -- RFI EXCHANGE for PEO EIS Information Exchange Day, 30 July 2013, to support DoD Biometrics. See update of data requested for JPIv2 and BEC Increment 1.