The file's text, extracted by GovTribe without its formatting.
RFC Response table
Instructions: In the experience column indicate if your company has experience for the specified requirement. If Yes, then indicate the name of the past customer and the period of performance.
If the Narrative column is “Yes”, then your response to this RFC should include a narrative description demonstrating your experience and understanding of the required capability.
| Req# |
| Requirement |
| Narrative (Yes/No/NA) |
| Experience (Yes/No/NA) |
| Past Customer |
| Period of Performance (Dates) |
0. Enhancement #1: Merge Rapid DNA Prototype functionality with the current CODIS release.
| 1. |
| The Contractor shall have experience with the latest version of MS Visual Studio (C#, VB.Net, and C++) and the .Net Framework. |
| No |
| 1. |
| The Contractor shall have experience with the latest version of MS SQL Server including the Enterprise and Express editions. |
| No |
| 1. |
| The Contractor shall have experience with MS Windows Communication Foundation (WCF). |
| No |
| 1. |
| The Contractor shall have experience with creating automated unit tests (i.e. NUnit, CSUnit, etc.) for .Net solutions that are invoked as part of a continuous integration (CI) strategy as new builds are created. Experience with automated user graphical user interface (GUI) testing is highly desirable. |
| Yes |
| 1. |
| The Contractor shall have experience with using automated tools to perform load testing to simulate a large number of users simultaneously using an application based on a service oriented architecture (SOA). |
| No |
| 1. |
| The Contractor shall have experience in both concurrency testing and performance testing. |
| No |
| 1. |
| The Contractor shall be able to create realistic test datasets with synthetic DNA profiles using allelic population database frequencies. |
| No |
| NA |
| 1. |
| The Contractor shall be able to create test scenarios reflecting typical CODIS operations that occur in parallel in order to meet concurrency requirements. |
| No |
| NA |
| 1. |
| The Contractor shall have MS TFS experience. |
| No |
| 1. |
| The Contractor shall have experience in managing and merging code branches with no disruption and/or degradation of existing code. |
| No |
| 1. |
| The Contractor shall have experience in continuous integration in order to detect defects early in the software development life cycle (SDLC). |
| No |
| 1. |
| The Contractor shall demonstrate they have experience creating screen mockups, interactive prototypes, and conducting usability reviews. |
| Yes |
| 1. |
| The Contractor shall have existing human factors engineering experience to guide the design of the CODIS application so that user productivity is efficient while minimizing the need for CODIS application training. |
| No |
| 1. |
| The Contractor shall have installation packaging experience using Windows Installer (MSI) technology and experience releasing application updates (patches, hotfixes, etc.). |
| No |
| 1. |
| The Contractor shall be able to describe a technical approach to maintaining the CRW at booking agencies not connected to the CJIS SEN with minimal assistance from the Operations helpdesk. |
| Yes |
| NA |
| 1. |
| The Contractor shall be able to create realistic test environments for each CODIS release being developed reflecting the types of environments that will be used in the production environment for CODIS operations. |
| No |
| NA |
| 1. |
| The Contractor shall demonstrate the capability to create realistic system (end-to-end) test cases that exercise the CODIS functionality when sending SERs/RSRs from a booking agency to SDIS and NDIS. |
| No |
| NA |
| 1. |
| The Contractor shall have experience using virtualization and supporting large SQL Server databases in order to adequately test rapid DNA functionality to meet the FBI rapid DNA mission objectives. |
| No |
| 1. |
| The Contractor shall be able to describe how the capabilities to process SERs and RSRs could be used in the future to improve the existing CODIS incremental upload process and the incremental Autosearch process. |
| No |
| NA |
| 1. |
| The Contractor shall have experience implementing scalable messaging solutions that are reliable and secure. |
| No |
| 1. |
| The Contractor shall have experience in developing XML schema (XSDs) used to define interface specifications. |
| No |
| 1. |
| The Contractor shall have experience with secure messaging using industry standard web services. |
| No |
| 1. |
| The Contractor shall have experience with HTTPS and Public Key Infrastructure (PKI) using X.509 certificates. |
| No |
| 1. |
| The Contractor shall have experience in security testing to verify the security posture of the CODIS application is constantly maintained as the CODIS application is enhanced. |
| No |
| 1. |
| The Contractor shall be able to describe a technical approach for merging Rapid DNA Prototype functionality with the CODIS main code base while verifying that software quality is not compromised. |
| Yes |
| NA |
| 1. |
| The Contractor shall be able to describe a technical approach to incrementally delivering business value using an Agile SDLC. |
| Yes |
| NA |
0. Enhancement #2: Develop Match Rarity Enhancement (MRE).
| 1. |
| The Contractor shall have expertise with DNA forensic statistical calculations used to determine human identity. |
| No |
| 1. |
| The Contractor shall be knowledgeable of how population database frequencies impact random match probability and how the number of expected matches is calculated when searching at different stringencies and when allowing a specified number of STR loci to miss. |
| Yes |
| NA |
| 1. |
| The Contractor shall be able to independently validate MRE calculation results for scientific and statistical accuracy. |
| Yes |
| NA |
| 1. |
| The Contractor shall be able to describe a testing strategy for MRE functionality. |
| No |
| NA |
| 1. |
| The Contractor shall be able to update relevant CODIS design documentation to explain how the MRE value is calculated and how CODIS business rules are impacted by the MRE capability. |
| No |
| NA |
0. Enhancement #3: Allelic dropout search capability.
| 1. |
| The Contractor shall possess bioinformatics expertise (recent within the last year) to understand how stringency and missed STR loci search configuration settings impact search results and the CODIS search engine (Next Generation Indexing Search Service (NGISS)) performance. |
| Yes |
| 1. |
| The Contractor shall be knowledgeable in multi-dimensional and tree structured indexing methods to support future optimizations to the CODIS search engine. |
| No |
| 1. |
| The Contractor must have an understanding of naturally occurring patterns in DNA genotypes and haplotypes in order to support efficient, high performance search and retrieval strategies of DNA profiles. |
| Yes |
0. Enhancement #4: Interoperability Service Enhancements.
| 1. |
| The Contractor shall have experience creating interface specifications and interface control documents to facilitate the adoption of industry standard services. |
| No |
| 1. |
| The Contractor shall have experience creating secure services that authenticate users, protect confidentiality, and maintain integrity of law enforcement sensitive data. |
| No |
| 1. |
| The Contractor shall have experience testing services accessed over both protected and unprotected networks. |
| No |
| 1. |
| The Contractor shall have experience creating automated unit tests that validates service layer business functionality. |
| No |
0. Enhancement #5: Pedigree Autosearch Performance Improvement.
| 1. |
| The Contractor shall possess bioinformatics expertise (recent within the last year) to understand how the number of typed and untyped pedigree nodes impact pedigree search results and the CODIS search engine (Next Generation Indexing Search Service (NGISS)) performance. |
| Yes |
| 1. |
| The Contractor shall have recent (within the last year) experience in multi-threaded programming using multi-core processors. |
| No |
| 1. |
| The Contractor shall have an understanding of creating pedigree search algorithms for missing person identification that are logarithmically scalable. |
| Yes |
| NA |
| 1. |
| The Contractor shall have an understanding of how different genetic technologies (STR, mtDNA, and Y-STR) impact missing person identification. |
| No |
| NA |
| 1. |
| The Contractor shall have general experience with application performance monitoring and tuning when using large in-memory databases. |
| No |
| 1. |
| The Contractor shall be able to describe a technical approach to reducing pedigree Autosearch time. The technical approach shall consider implications to pedigree consistency checks needed to initialize the pedigree for evaluation during searching. |
| No |
| NA |
| 1. |
| The Contractor shall be able to create valid test data using synthetic pedigrees with a user specified number of typed nodes that are genetically consistent across all genetic technologies. |
| No |
| NA |
0. Enhancement #6: Popstats Pedigree Calculation
| 1. |
| Even though the Government is providing the pedigree likelihood calculation algorithm as GFI, the Contractor shall be knowledgeable of kinship statistics in order to support the implementation and validation of the pedigree likelihood calculation. |
| Yes |
| NA |
| 1. |
| The Contractor shall have the expertise to implement and validate these new Popstats pedigree LR calculations. |
| No |
| NA |
| 1. |
| The Contractor shall be knowledgeable of mutation models and the impact of mutations (STR, mtDNA, and Y-STR) to pedigree likelihood calculations. |
| No |
| NA |
| 1. |
| The Contractor shall be knowledgeable of the impact of genetically linked loci (not independent) on kinship calculation results. |
| No |
| NA |
| 1. |
| The Contractor shall be knowledgeable of approaches to determining identity by descent (IBD) for both genotypes and haplotypes. |
| No |
| NA |
| 1. |
| The Contractor shall be knowledgeable of the current SWGDAM guidelines for both mtDNA and Y-STR interpretation. For more information on statistical calculations for haplotypes refer to Scientific Working Group on DNA Analysis Methods (SWGDAM) Interpretation Guidelines for Mitochondrial DNA Analysis by Forensic DNA Testing Laboratories and Scientific Working Group on DNA Analysis Methods (SWGDAM) Interpretation Guidelines for Y-Chromosome STR Typing. |
0. Enhancement #7: Combined Data Entry.
| 1. |
| The Contractor shall have current experience developing feature rich GUI interface applications using MS Visual Studio and the .Net framework. Experience with MS Windows Presentation Foundation (WPF) is desirable. |
| Yes |
0. Enhancement #8: Specimen Import.
| 1. |
| The Contractor shall be knowledgeable of DNA information that can be exported from external DNA analysis applications such DNA sequencers, LIMS, and expert systems. |
| Yes |
| NA |
| 1. |
| The Contractor shall have current experience automating processes to improve user productivity and efficiency. |
| No |
0. Enhancement #9: Rank Audit Trail.
| 1. |
| The Contractor shall be knowledgeable of security best practices related protecting the integrity of application audit trails. |
| No |
| 1. |
| The Contractor shall demonstrate an understanding of the technical challenges in implementing a rank audit trail. |
| No |
| NA |
| 1. |
| The Contractor shall describe a technical approach to creating a rank audit trail. |
| Yes |
| NA |
0. Enhancement #10: Pedigree Audit Trail.
| 1. |
| The Contractor shall demonstrate an understanding of the technical challenges in implementing a pedigree audit trail. |
| No |
| NA |
| 1. |
| The Contractor shall describe a technical approach to creating a pedigree audit trail. |
| Yes |
| NA |
0. Enhancement #11: Usability Enhancements.
| 1. |
| The Contractor shall demonstrate an understanding of the technical challenges in improving the usability of the CODIS application. |
| No |
| NA |
| 1. |
| The Contractor shall describe a technical approach for improving the usability of the CODIS application. This technical approach shall describe how consistency in the user interface will be improved. |
| Yes |
| NA |
0. Enhancement #12: Maintainability Enhancements
| 1. |
| The Contractor shall have experience using industry leading installation packaging applications such as Flexara Software InstallShield. |
| No |
| 1. |
| The Contractor shall be able to recommend improvements to the design of CODIS in order to reduce deployment time and calls to the CODIS helpdesk related to installation. |
| Yes |
| 1. |
| The Contractor shall be able to recommend strategies for quickly deploying CODIS hotfixes and monitoring the hotfix deployment status by communicating CODIS version status for all client workstations and the CODIS server to the CODIS helpdesk. |
| Yes |
| 1. |
| The Contractor shall be knowledgeable of extract, transform, and load (ETL) operations used on very large relational databases. |
| No |
| 1. |
| The Contractor shall have experience in SQL Server performance tuning and optimization. |
| No |
| 1. |
| The Contractor shall have experience with developing 64 bit applications that are multithreaded. |
| No |
| 1. |
| The Contractor shall be familiar with the COTS development components used in the current version of CODIS. |
| No |
| 1. |
| The Contractor shall be able to recommend improvements to the CODIS architecture to accommodate operating CODIS in a virtualized or cloud environment. |
| No |
| 1. |
| The Contractor shall have current experience in object oriented (OO) design patterns. |
| No |
| 1. |
| The Contractor should be able to recommend opportunities to improve CODIS functionality and maintainability by leveraging advances in the .Net Framework. |
| No |
| 1. |
| The Contractor shall be able recommend possible improvements in the CODIS user interface by leveraging advances in the Windows Presentation Foundation (WPF). |
| No |
| 1. |
| The Contractor shall be familiar with the Windows Workflow Foundation (WWF) and be able to recommend CODIS operations that could be refactored to use WWF to improve CODIS maintainability. |
| No |
| 1. |
| The Contractor shall be familiar with the Microsoft Enterprise Library to provide logging and exception handling. |
| No |
| 1. |
| The Contractor shall be familiar with application monitoring techniques to identify performance bottlenecks such as memory leaks, excessive paging, disk i/o utilization, and processor utilization. |
| No |
| 1. |
| The Contractor shall have experience with creating automated tests that exercise functionality via the application graphical user interface (GUI). |
| Yes |
| 1. |
| The Contractor shall demonstrate they have current trained staff (testers) and posses the software/tools readily available to create an automated smoke test. |
| No |
| 1. |
| The Contractor shall have experience in providing disaster recovery/high availability solutions for mission critical applications. |
| Yes |
| 1. |
| The Contractor shall be familiar with the latest Microsoft SQL Server technologies used to create high availability solutions. |
| No |
| 1. |
| The Contractor shall be able to evaluate the use Windows Server Failover Clustering (WSFC), SQL Server AlwaysOn Availability Groups, Database Mirroring, and Log Shipping to meet CODIS high availability requirements. |
| No |
0. Training
| 1. |
| The Contractor shall have experience using the latest versions Adobe Captivate and Adobe RoboHelp. |
| No |
| 1. |
| The Contractor shall have experience creating SCORM 2004 CBTs. |
| Yes |
| 1. |
| The Contractor shall have experience creating curriculum to support learning objectives. |
| No |
| 1. |
| The Contractor shall describe a technical approach to creating and testing SCORM compliant CBTs. |
| No |
| NA |
0. Subject Matter Expertise (SME) Support
| 1. |
| The Contractor shall have current experience working with academic institutions to conduct research and collaborate on software development objectives. |
| No |
| 1. |
| The Contractor shall demonstrate they have SMEs capable of writing scientific white papers and scholarly articles suitable for publication in scientific/forensic journals. |
| No |
| 1. |
| The Contract shall demonstrate an understanding of each of the SME capabilities requested. |
| Yes |
| NA |
0. Maintenance Support
| 1. |
| The Contractor shall demonstrate they have experience working with other companies to develop software solutions. |
| No |
| 1. |
| The Contractor shall demonstrate the ability to create a liaison plan with the Maintenance Contractor. |
| No |
| NA |
| 1. |
| The Contractor shall demonstrate a CM approach to facilitate the integration of maintenance changes with the main CODIS development branch. |
| Yes |
| NA |