Inactive

Amendment 1: The purpose of this amendment is to extend the due date for responses to the RFI until Wednesday, May 24, 2023 at 5:00 PM. ** REQUIREMENTS TOOL - Full SOW provided in Attachment THIS IS A... Amendment 1: The purpose of this amendment is to extend the due date for responses to the RFI until Wednesday, May 24, 2023 at 5:00 PM. ** REQUIREMENTS TOOL - Full SOW provided in Attachment THIS IS A REQUEST FOR INFORMATION (RFI) ONLY This RFI is issued solely for information and planning purposes and does not constitute a solicitation. Nonetheless, submitters should properly mark their responses if the information is confidential or proprietary. Furthermore, those who respond to this RFI should not anticipate feedback with regards to its submission other than acknowledgment of receipt, should the submitter request an acknowledgement. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. All submissions become the property of the Federal Government and will not be returned. Responders are solely responsible for all expense associated with responding to this RFI. INTRODUCTION The Office of Biometric Identity Management (OBIM) provides biometric match, store, share, and analyze services to DHS and mission partners. The need for biometrics continues to grow among DHS Components; interagency stakeholders (e.g., the Departments of State, Justice, and Defense); State, local, tribal, and territorial entities; the Intelligence Community; and international mission partners. Biometrics support critical national security priorities, including counterterrorism and immigration. OBIM is focused on delivering accurate, timely, and high assurance biometric identity information and analysis. OBIM’s overall goals and priorities include continuing to improve biometric services and access to expanded biometric data to enable DHS operational missions. PURPOSE OF RFI The purpose of this RFI is to gather information on requirements development and management tools available that can capture, develop, store, and assess requirements. The capability will also provide a means to obtain organizational and stakeholder approval of requirements and associated artifacts (e.g., supporting documentation). The tool will also enable the automated generation of use cases, user stories, and test cases. SUBMISSION REQUIREMENTS This acquisition is in line with on-going efforts tied to a new OBIM-wide process for managing the requirements (acquisition-based, missional, operational, functional, non-functional, etc.) for OBIM systems and operations referred to as the Requirements Development and Management Process (RDMP), currently on-track for implementation at the start of Q1FY2024, with an eye towards mitigating and resolving identified issues in the current usage of multiple uncoordinated tools for managing requirements. This tool shall meet the following technical criteria: Functional Criteria The tool must be able to define, manage, and engineer requirements processes. The tool shall serve as a centralized collaboration of the in-house Requirements Development and Management Process platform between multiple and distributed stakeholders. The tool shall be able to score requirements to determine requirements quality, maturity, time to generate, traceability, changes, and validation (among other potential metrics), and provides the data (for a separate analytic environment) and/or a dashboard with the status of the metrics. The tool shall have the capability to know the difference between an operational, non-functional/functional/system/technical requirement based on a maturity of the requirement. The tool shall be able to allow for a review and approval process, requirement reuse, and the support of bug tracking. The tool shall have Full/Read-Write, Read/Only product as such to review requirements, develop, test or design documents that will allow teams to collaborate. The tool shall have documentation and project baselines can be sent out to users for electronic signature and feedback collected in a centralized way, making sure that approved documents are available to everybody in the project. The tool shall have change management: ability to manage the approval of and changes to requirements artifacts within the tool. The tool shall manage Artifact Repository: Artifacts are stored in version-controlled repository that supports check out, update, check-in, and collaboration across multiple types and workspaces. Agile work management: The tool will allow for the automated generation of use cases, user stories, test cases/plans and prioritization. The tool shall facilitate the decomposition of high-level capability requirements into epics, user stories, and features. The tool shall provide the status of requirements, to include but not limited to draft, proposed, approved, scheduled for release, partially implemented, completely implemented, obsolete, cancelled/deleted, etc. The tool shall have ease to interoperate or integrate effectively with any type of process template such as the current suite of Microsoft products and exportable as a .pdf, such as the Microsoft Office 365 versions of Word, Excel, PowerPoint, Visio, and Outlook. This includes compatibility with the Cameo MagicDraw application (or similar architecture and data management tool). The tool shall have ease to integrate effectively and easily with issue tracking and collaboration tools such as the current suite of OBIM agile-supporting requirements tools: JIRA v8.20.1, and Maestro Confluence 7.13.2. The tool shall offer a full array of reporting, cross-referencing, searching, and traceability capabilities for the managed requirements. Technical Criteria The tool shall support/reside on Amazon Web Services without a bridge product. The tool shall be customizable for flexibility in building reports and/or adding additional features. The tool shall have traceability to the source code with a collaborative role-based sign-off approach for requirements. Technical support for Data base transfer within the tool Vendor availability, support, and quality training: ability to receive timely and support, additional training material required for end users, including videos, user manuals or interactive tutorials. Software maintenance agreements must be compatible with software purchased. The software license use and maintenance support agreements come with the purchase of a license. Total of 30 licenses with read-write access. In addition to the requested information above, confirm if the solution described is commercially available or is a commercially available solution that can be modified to meet the Government’s needs. Finally, provide any pricing considerations of which the Government should be aware. For example, does this solution require an initial investment followed by reduced operations and maintenance costs, or is license pricing tier-based with additional discounts available for a higher number of users, etc. Please note that specific pricing for the product IS NOT being requested. SUBMISSION INSTRUCTIONS The information obtained may be utilized in the preparation of a Request for Quote (RFQ) provided DHS finds it in its best interest. Vendors are encouraged to review this RFI and determine if their competency meet the DHS requirements. Finally, RFI submissions should include a cover letter no longer than two (2) pages in length with the following information: 1. Vendor official name, address and phone number. 2. Point of Contact information, including name, phone number and email address. 3. The vendor’s country of origin. 4. If applicable, one URL for the organization’s official web site. 5. The socio-economic category under which the vendor is currently certified to perform under NAICS code [541512 – Computer Systems Design Services]. 6. If applicable, your company’s GSA Schedule contract number; and 7. If applicable, any relevant DHS strategic sourcing vehicle your company currently holds a contract under and the associated contract number. Responses are limited to 10 pages (including cover letter), must be in 12pt Calibri font with .75 inch margins and submitted via e-mail only to Contracting Officer Amy Driver at Amy.Driver@hq.dhs.gov, and Contract Specialist Robert Farrell at Robert.Farrell@hq.dhs.gov no later than May 19, 2023 at 5:00 PM ET. The subject line of the email should contain the RFI number 70RDAD23RFI000014. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate and mark proprietary information. Please be advised that all submissions become Government property and will not be returned. (End of Request for Information) ** See Attachment for Statement of Work**