ICMS Requirements Appendix B.xlsx
XLSX spreadsheet 30 KB Posted
- Attached to
- Investigation Case Management System
- Solicitation number
- Not on record
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI Industry Questions Response Final.xlsx | XLSX spreadsheet | |
| RFI_for_ICMS_Final_Post-May 14.docx | DOCX document | |
| RFI_for_ICMS_Final_Post.docx | DOCX document |
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
Sheet1
| Functional Requirements | ||||||
| REQ ID | Requirements | Source | Verification Method | Priority | Yes | No |
| (1-3) | ||||||
| REQ100 | Persons Module - Ability to enter and manage Persons associated with Cases, including Subjects, Complainants, Witnesses, and other Person types. Ability to create relationships among persons (i.e., spouse, mother, father, son, daughter, etc.). The associations (or cross indexes) should appear when conducting a person search. | Derived | Demo | P-1 | ||
| ICMS101 | Ability to track multiple Person Aliases | Derived | Test | P-1 | ||
| ICMS102 | Ability to merge multiple Person records | Derived | Test | P-1 | ||
| ICMS103 | Ability to track Persons | Derived | Test | P-1 | ||
| ICMS104 | Ability to associate Persons with Cases (via a designated role such as subject, victim, complainant, associated person, witness) | Derived | Test | P-1 | ||
| ICMS105 | Ability to track unidentified Persons (associated to the case) | Derived | Test | P-1 | ||
| ICMS106 | For all modules, ability to toggle back and forth between multiple search results without starting a new search each time. | Derived | Test | P-1 | ||
| REQ200 | Complaints Module - Ability to enter and manage Complaints from intake through conversion into an Investigation, including associated records, workflows, and notifications. | Derived | Demo | P-1 | ||
| ICMS201 | Ability to manually enter a new Complaint | Derived | Test | P-1 | ||
| ICMS202 | Ability to import, enter, or upload BOP and USMS allegations (Complaints) received in batch files | Derived | Test | P-1 | ||
| ICMS203 | Special Agent (SA) - Ability to review Complaints and recommend a disposition | Derived | Test | P-2 | ||
| ICMS204 | SA-In-Charge (SAC) - Ability to concur or return a Complaint based on the recommended disposition | Derived | Test | P-1 | ||
| ICMS205 | Ability to refer a Complaint to an external agency with the ability to designate the type of referral code | Derived | Test | P-1 | ||
| ICMS206 | Ability to convert a Complaint into an Investigation | Derived | Test | P-1 | ||
| ICMS207 | Ability to associate Documents to a Case | Derived | Test | P-1 | ||
| ICMS208 | Ability to import hotline email data or use email data to create a new complaint. This includes having complaint forms filled out on the OIG’s website automatically populate into the case management system for review and subsequent disposition. The dispositions available should include various abilities to close and/or associate the complaint with a prior investigation/complaint, mark as a duplicate entry, and close or code that the complaint is not within the OIG’s jurisdiction. | Derived | Test | P-1 | ||
| ICMS209 | Ability to generate a unique identification number for complaints that will also be utilized if complaint is converted to a case | Derived | Test | P-1 | ||
| ICMS210 | Ability to associate new Complaints/Cases with existing Complaints/Cases | Derived | Test | P-1 | ||
| ICMS211 | Ability to track Violation Codes (Offenses) | Derived | Test | P-1 | ||
| ICMS212 | Ability to view Complaints in Progress (Views) | Derived | Test | P-1 | ||
| ICMS213 | Ability to view, print, and transmit via email all complaint intake material and letters. For example, when a complaint is ready for final disposition the employee will click a referral button that will automatically initiate an email to the appropriate agency and automatically attach the case documents that have been saved in the ICMS. The email shall be configured to automatically change the intended recipient dependent upon the receiving agency/component. Field elements should also have the ability to enter/process and transmit/dispose of complaints. Contractor to work with the government to create workflows for headquarters vs. field elements. | Derived | Test | P-2 | ||
| ICMS214 | Ability to auto-generate and email letters specific to complaints. If no email address is entered into the “persons” record, an option to manually generate and print a formal letter to be mailed shall be included. The date the complaint letter was emailed should be captured. | Derived | Test | P-2 | ||
| ICMS215 | Ability to associate each person that has been entered in the database to all complaints and cases associated to that person. | Derived | Test | P-1 | ||
| REQ300 | Investigations Module - Ability to manage the Investigation from assignment through case closure, including case special security handling for high profile cases. An option to print or save (via .PDF) a summary of the investigation that captures all of the case information on the investigation module. | Derived | Analysis/Demo | P-1 | ||
| ICMS301 | Ability to create a “Restricted Folder” with customizable permissions (e.g., Grand Jury, HIPPA, Privacy Act). The ability to customize who has access to the folder should be able to be specified by the user and supervisors. | Derived | Test | P-1 | ||
| ICMS302 | Ability to enter various data elements relative to an investigation. Elements to be provided by the government during the development phase, and should include, but not be limited to, all capabilities and data elements currently available in IDMS, such as: investigation type, field office responsibility, status, case agent, days open, work hours attributed to the case, joint investigation marker and identity of other agency involved, case complexity, date closed, etc. Should also have the ability to cross reference cases to other relevant modules, such as Persons, Judicial Actions, Administrative Actions, etc. | Derived | Test | P-1 | ||
| ICMS303 | Ability to certify a case for closure by requiring managers to verify that specific actions have been taken and certain documents have been uploaded to the case file before the file can be closed. Elements needed to certify a case for closure to be provided by the government. | Derived | Test | P-2 | ||
| ICMS304 | Ability to designate an investigation as either an Investigation, Preliminary Inquiry, or an Auxiliary. | Derived | Test | P-1 | ||
| ICMS305 | Ability to assign investigation complexity levels to new investigations (high, medium, low). | Derived | Test | P-1 | ||
| ICMS306 | Ability to generate investigation opening notification memoranda to be transmitted to DOJ components. | Derived | Test | P-2 | ||
| ICMS307 | Inclusion of a case sensitivity field that allows sensitive items to be captured such as: Inspector General interest, priority investigation, media interest, Joint Investigation with other agencies and an option to select appropriate agency. | Derived | Test | P-1 | ||
| ICMS308 | Each investigation will contain an electronic chronological case log (CCL) that will capture the date of the event, a description of the activity (e.g., Memorandum of Investigation of XYZ, Case Review), and an automatically applied name of who made the entry. These entries will be made by manual entry of the user. The CCL shall be maintained in a chronological order. A reminder to conduct case reviews every 60 days shall be emailed to the assigned special agent’s supervisor if a case review is not documented by day 55. All entries into the CCL will be locked by the originator and should not have the ability to be edited by other users, except Power Users. The CCL will also have the ability to enter an investigative work plan for supervisory approval, as appropriate. There shall be a list of typical activities to be outlined by the government in a type of activity field (e.g., MOI, Case Review). When a type of activity corresponds to an OIG form, the ability for the user to create a pre-populated form with system-generated information (e.g., name of agent, personal identifying information of interview) shall be automatically imported into the template. | Derived | Test | P-1 | ||
| ICMS309 | Ability to see how many days the investigation has been open and how many hours have been charged to the investigation. | Derived | Test | P-1 | ||
| ICMS310 | Ability to input time entry against an investigation and complaint which would automatically apply the matter to the employee’s WebTA timecard. | Derived | Test | P-1 | ||
| ICMS311 | Data fields for investigations shall be consistent with the requirements of NIBRS. The crosswalk for these requirements is highlighted on the FBI’s website. All NIBRS codes shall be initially entered, and the flexibility built into the system to allow for future changes or modifications by system administrators | Derived | Test | P-1 | ||
| ICMS312 | Ability to associate documents to a case. | Derived | Test | P-1 | ||
| REQ400 | Referral Module – Ability to refer a case to another DOJ component’s Internal Affairs division or other DOJ components. Contractor to work with the government to determine the best path to capture criminal, civil, and administrative referrals and the method of recording each action in the system. This may require the expansion of various types of dispositions which may be different for criminal, civil, and administrative matters. | Derived | Test | P-1 | ||
| ICMS401 | Ability to refer a Case to another DOJ component's Internal Affairs division | Derived | Test | P-1 | ||
| ICMS402 | Ability to track result of the internal referral | Derived | Test | P-1 | ||
| REQ500 | Judicial (Criminal) Module – Ability to track arrests, case presentation for prosecution, and sentencing information and outcomes. Federal sentencing statutes shall be initially entered, and the flexibility built into the system to allow for future changes or modifications by system administrators. | Derived | Demo | P-1 | ||
| ICMS501 | Ability to track Judicial Referrals, including the initial referral to a federal and/or state prosecutorial authority and the prosecutorial decision. | Derived | Test | P-1 | ||
| ICMS502 | Ability to track the Judicial (Criminal) charging type (indictment, information, etc.) and Outcome (Sentencing Info) | Derived | Test | P-1 | ||
| ICMS503 | Ability to enter and track Arrests to ensure that each arrest is associated with a judicial disposition. Ability to require a certification (via checkboxes or other method) that fingerprints, photographs, and a personal history sheet were collected and fingerprints were submitted to the FBI, before a newly-created arrest record can be saved. Ability to require a certification (via checkboxes or other method) that a final RAP sheet showing OIG credit for the arrest has been obtained and an R-84 form was submitted to the FBI, before a case can be closed. | Derived | Test | P-1 | ||
| REQ600 | Evidence Module – Ability to track physical and digital evidence records, including chain of custody and digital signatures. Ability for supervisors to have access to see what item(s) are held in evidence for their field office and for headquarters staff ability for a view capability to allow unilateral view access to items in evidence at all offices nationwide. | Derived | Analysis/Demo | P-1 | ||
| ICMS601 | Ability to track (enter) Evidence into custody and generate an Evidence tag to be printed and attached to the piece of evidence with a unique identifier number associated to the investigation | Derived | Test | P-1 | ||
| ICMS602 | Ability to track chain of custody events for the evidence, and to document the transfer of evidence (temporary or permanent) to other field offices or an external entity. | Derived | Test | P-1 | ||
| ICMS603 | Ability to track redacted digital evidence and status | Derived | Test | P-1 | ||
| ICMS604 | Ability to conduct an annual inventory | Derived | Test | P-2 | ||
| ICMS605 | Ability to digitally sign the outgoing evidence as last receiver | Derived | Test | P-1 | ||
| ICMS606 | Ability to generate and send a report for component review | Derived | Test | P-1 | ||
| ICMS607 | Ability to request and document approval authority to dispose of evidence. | Derived | Test | P-1 | ||
| ICMS608 | Ability to request and document approval authority to dispose of abandoned currency seized as evidence. | Derived | Test | P-1 | ||
| REQ700 | Enforcement Request Module – Ability to request and track enforcement assistance. The system shall utilize configurable workflow processes to define all level of activities to submit/approve requests. | Derived | Demo | P-1 | ||
| ICMS701 | Ability to request and track Enforcement Request - Consensual Intercept | Derived | Test | P-1 | ||
| ICMS702 | Ability to request and track Enforcement Request - Telephone Consensual | Derived | Test | P-1 | ||
| ICMS703 | Ability to request and track Enforcement Request - Consensual for BOP | Derived | Test | P-1 | ||
| ICMS704 | Ability to request and track Enforcement Request – Subpoenas. The user shall specify the signatory authority for such subpoenas and allow the user to select the type of subpoena (SAC, Inspector General, or Grand Jury). Appropriate approval/review layers shall be automated to route to and track the status of requests | Derived | Test | P-1 | ||
| ICMS705 | Ability to request and track Enforcement Request - Polygraph Examinations | Derived | Test | P-1 | ||
| ICMS706 | Ability to track request and Enforcement Request - FedPris Requests | Derived | Test | P-1 | ||
| ICMS707 | Ability to request and track Enforcement Request – Approval of the use of undercover buy money over the field office threshold. | Derived | Test | P-2 | ||
| ICMS708 | Ability to request and track Enforcement Request – Foreign travel for investigative activities. | Derived | Test | P-2 | ||
| ICMS709 | Ability to request and track Enforcement Request – Approval of the use of flash money rolls. | Derived | Test | P-2 | ||
| ICMS710 | Ability to request and track Enforcement Request – consensual non-telephone intercepts. | Derived | Test | P-1 | ||
| REQ800 | ROI (Reports of Investigation) Module – Ability to track Reports of Investigations, including report generation, approvals, and digital signature. | Derived | Analysis/Demo | P-1 | ||
| ICMS801 | Ability to digitally sign utilizing PIV credentials | Derived | Test | P-1 | ||
| ICMS802 | Ability to create a Report of Investigation (ROI) activity / record | Derived | Test | P-1 | ||
| ICMS803 | Ability to generate a Report of Investigation electronically which will include an ROI coversheet, exhibit list, and the ability to attach selected documents or other items in the case file as exhibits. The system should allow the option for selected case file documents to be generated into a .PDF portfolio file. | Derived | Test | P-1 | ||
| ICMS804 | Ability to submit, approve, and return a Report of Investigation | Derived | Test | P-1 | ||
| ICMS805 | Ability to track customer satisfaction survey data | Derived | Test | P-1 | ||
| ICMS806 | Ability to run reports to provide status, revolving number of days since referred, etc. | Derived | Test | P-1 | ||
| ICMS807 | Ability to capture / generate number of days in custody | Derived | Test | P-1 | ||
| REQ900 | Admin Actions Module – Ability to track Admin Actions, including disciplinary actions and appeals. | Derived | Demo | P-1 | ||
| ICMS901 | Ability to track the initial (interim) admin action | Derived | Test | P-1 | ||
| ICMS902 | Ability to track the final admin action | Derived | Test | P-1 | ||
| ICMS903 | Ability to track admin action appeals | Derived | Test | P-1 | ||
| REQ1000 | Civil Actions Module – Ability to track Civil Actions, including the judicial referral and related outcomes (Civil Monetary Penalties). | Derived | Demo | P-1 | ||
| ICMS1001 | Ability to track Civil Actions | Derived | Test | P-1 | ||
| ICMS1002 | Ability to track Civil Action Outcomes (CMP) | Derived | Test | P-1 | ||
| REQ1100 | Investigative Activity Module – Ability to track Investigative Activities | Derived | Demo | P-1 | ||
| ICMS1101 | Ability to track Investigative Activity - Forensic Activity Requested | Derived | Test | P-1 | ||
| ICMS1102 | Ability to track Investigative Activity - INV DIV Briefing Program | Derived | Test | P-1 | ||
| ICMS1103 | Ability to track Investigative Activity - OEO Request Approved | Derived | Test | P-1 | ||
| ICMS1104 | Ability to track Investigative Activity - Polygraph Administered | Derived | Test | P-1 | ||
| ICMS1105 | Ability to track Investigative Activity - PRR | Derived | Test | P-1 | ||
| ICMS1106 | Ability to track Investigative Activity - Recovery Act | Derived | Test | P-1 | ||
| ICMS1107 | Ability to track Investigative Activity - Search Warrant Executed | Derived | Test | P-1 | ||
| ICMS1108 | Ability to track Investigative Activity - Seizure | Derived | Test | P-1 | ||
| ICMS1109 | Ability to track Investigative Activity - Subpoena Served | Derived | Test | P-1 | ||
| ICMS1010 | Ability to track Investigative Activity - Surveillance | Derived | Test | P-1 | ||
| ICMS1111 | Ability to track Investigative Activity - Undercover Operation | Derived | Test | P-1 | ||
| ICMS1112 | Ability to track an Auxiliary Investigation (For assistance, as an Investigation Activity) | Derived | Test | P-1 | ||
| ICMS1113 | Ability to track Investigative Activity - Generic Activity (shared fields) | Derived | Test | P-1 | ||
| ICMS1114 | Ability to automatically add a record retention thru date that the system will automatically calculate based on the date of final case closure. For investigations meeting the permanent retention requirement, ability to indicate when the investigation has been transferred to the NARA, with associated tracking information (e.g., date transferred, NARA reference number, media serial number). | Derived | Test | P-1 | ||
| For investigations to be deleted, the system shall automatically email the SAC ISB and the INV computer programmers of the deletion. They shall have the ability to delete investigative SharePoint folders; however, the investigative entry screen shall remain. | ||||||
| REQ1200 | Time Entry Module – Ability to track and approve time with pay periods, including time entered against cases and other admin time per employee. The option to require the completion of a timesheet. | Derived | Demo | P-1 | ||
| ICMS1201 | Ability to track hours spent on a case | Derived | Test | P-1 | ||
| ICMS1202 | Ability to view total hours spent on a case | Derived | Test | P-1 | ||
| ICMS1203 | Ability to interact with the OIG time and attendance system WebTA | Derived | Test | P-2 | ||
| ICMS1204 | Ability to track by fiscal year and by Pay Periods | Derived | Test | P-2 | ||
| ICMS1205 | Ability to submit Time Entries | Derived | Test | P-2 | ||
| ICMS1206 | Ability to Approve and Reject Time Entries | Derived | Test | P-2 | ||
| ICMS1207 | Ability to auto-create time summaries at the beginning of a new pay period | Derived | Test | P-2 | ||
| REQ1300 | Reports – Ability to run and print reports, including ad-hoc reports and formatted reports. Ability to run automated reports that are automatically distributed to authorized recipients. Reports shall be able to be drilled down from INV globally to office and group levels. Managers shall be able to run all reports for their chain of command. INV HQ SACs and executives shall be able to see all data collectively or separately broken down. | Derived | Demo | P-1 | ||
| ICMS1301 | Ability to run OIG report - Investigation Statistics, which includes statistics for investigative caseloads, prosecutive/administrative actions, BOP case timeliness, ROI timeliness, and cases opened by offense category. | Derived | Test | P-1 | ||
| ICMS1302 | Ability to product Ad-Hoc Reports | Derived | Test | P-1 | ||
| ICMS1303 | Ability to run monthly report - Monthly Productivity Report | Derived | Test | P-1 | ||
| ICMS1304 | Ability to run monthly report - Monthly Investigation by Component | Derived | Test | P-1 | ||
| ICMS1305 | Ability to run monthly report - Monthly Investigation Closed by Component | Derived | Test | P-1 | ||
| ICMS1306 | Ability to run semiannual report - Semiannual Report to Congress | Derived | Test | P-1 | ||
| ICMS1307 | Ability to run semiannual report - Agent Summary Statistics Report | Derived | Test | P-1 | ||
| ICMS1308 | Ability to run semiannual report - Agent Caseload Report | Derived | Test | P-1 | ||
| ICMS1309 | Ability to run semiannual report - Whistleblower Statistics Report | Derived | Test | P-1 | ||
| ICMS1310 | Ability to run annual report - IAR Surveillance Activities Report | Derived | Test | P-1 | ||
| ICMS1311 | Ability to run OIG report - Open Cases Report by Agent | Derived | Test | P-1 | ||
| ICMS1312 | Ability to run OIG report - Open Priority Investigations | Derived | Test | P-1 | ||
| ICMS1313 | Ability to run OIG report - Open Priority Investigations with Complaint Narrative | Derived | Test | P-1 | ||
| ICMS1314 | Ability to run OIG report - Investigative Activities Briefings | Derived | Test | P-1 | ||
| ICMS1315 | Ability to run OIG report - New Investigations | Derived | Test | P-1 | ||
| ICMS1316 | Ability to run OIG report - Open Criminal Cases with Victim and Witness | Derived | Test | P-1 | ||
| ICMS1301 | Ability to run OIG report - SACs Call Report | Derived | Test | P-1 | ||
| ICMS1317 | Ability to run semiannual report to Congress - Investigations Type Missing | Derived | Test | P-1 | ||
| ICMS1318 | Ability to run semiannual report to Congress - INV OPJP No Prosecution Date | Derived | Test | P-1 | ||
| ICMS1319 | Ability to run semiannual report to Congress – Arrests | Derived | Test | P-1 | ||
| ICMS1320 | Ability to run semiannual report to Congress - Criminal Indictments / Information | Derived | Test | P-1 | ||
| ICMS1321 | Ability to run semiannual report to Congress - Convictions and Pleas | Derived | Test | P-1 | ||
| ICMS1322 | Ability to run semiannual report to Congress - Administrative Actions | Derived | Test | P-1 | ||
| ICMS1323 | Ability to run semiannual report to Congress - Civil Rights Complaints | Derived | Test | P-1 | ||
| ICMS1324 | Ability to run semiannual report to Congress - Civil Proceedings | Derived | Test | P-1 | ||
| ICMS1325 | Ability to run semiannual report to Congress - Criminal Fines, Restitutions, and Recoveries | Derived | Test | P-1 | ||
| ICMS1326 | Ability to run semiannual report to Congress - Non-Judicial Monetary | Derived | Test | P-1 | ||
| ICMS1327 | Ability to run semiannual preview report - Allegations with "U" Disposition ATF, DEA, and FBI Only | Derived | Test | P-1 | ||
| ICMS1328 | Ability to run semiannual preview report - Allegations with "U" Disposition Excludes ATF, DEA, and FBI | Derived | Test | P-1 | ||
| ICMS1329 | Ability to run semiannual preview report - Referrals 90 Day Excluding ATF, FBI, and DEA | Derived | Test | P-1 | ||
| ICMS1330 | Ability to run semiannual preview report - Referrals 90 Days Patriot Act, ATF, FBI, DEA Only | Derived | Test | P-1 | ||
| ICMS1331 | Ability to run semiannual preview report - Referral Complaints with Missing Referral Records | Derived | Test | P-1 | ||
| ICMS1326 | Ability to run cyclical report – Investigative Activities Report | Derived | Test | P-1 | ||
| ICMS1332 | Ability to run automated report - HQ Weekly Complaint Intake | Derived | Test | P-1 | ||
| ICMS1333 | Ability to run automated report - ATF Weekly Complaint Report | Derived | Test | P-1 | ||
| ICMS1334 | Ability to run automated report - BOP Weekly Complaint Report | Derived | Test | P-1 | ||
| ICMS1326 | Ability to run automated report - DEA Weekly Complaint Report | Derived | Test | P-1 | ||
| ICMS1335 | Ability to run automated report - FBI Weekly Complaint Report | Derived | Test | P-1 | ||
| ICMS1336 | Ability to run automated report - OBD Weekly Complaint Report | Derived | Test | P-1 | ||
| ICMS1337 | Ability to run automated report – USMS Weekly Complaint Report | Derived | Test | P-1 | ||
| ICMS1338 | Ability to run automated report - Daily OPSII Undesignated Complaints | Derived | Test | P-1 | ||
| ICMS1339 | Ability to run automated report - Daily USMS Undesignated | Derived | Test | P-1 | ||
| ICMS1340 | Ability to run automated report - Monthly FBI Extract | Derived | Test | P-1 | ||
| ICMS1341 | Ability to run automated report - Monthly Grassley Report | Derived | Test | P-1 | ||
| ICMS1342 | Ability to run automated report - Monthly High Case Complex Scheduler | Derived | Test | P-1 | ||
| ICMS1343 | Ability to run automated report - Monthly Open Grassley Report | Derived | Test | P-1 | ||
| ICMS1344 | Ability to run automated report - Patriot Act Cases | Derived | Test | P-1 | ||
| ICMS1345 | Ability to run automated report - Weekly Case Complexity Report | Derived | Test | P-1 | ||
| ICMS1346 | Ability to run automated report - Weekly Contract Grant Fraud Complaint Report | Derived | Test | P-1 | ||
| ICMS1347 | Ability to run automated report - Weekly COVID-19 Report | Derived | Test | P-1 | ||
| ICMS1348 | Ability to run automated report - Weekly DICAM Cases Report | Derived | Test | P-1 | ||
| ICMS1349 | Ability to run automated report - Weekly FBI New Criminal Investigations List | Derived | Test | P-1 | ||
| ICMS1350 | Ability to run automated report - Weekly NDAA Report | Derived | Test | P-1 | ||
| ICMS1351 | Ability to run automated report - Weekly New Investigations | Derived | Test | P-1 | ||
| ICMS1352 | Ability to run automated report - Weekly New Investigations OBD_cc | Derived | Test | P-1 | ||
| ICMS1353 | Ability to run automated report - Weekly New Investigations_cc | Derived | Test | P-1 | ||
| ICMS1354 | Ability to run automated report - Weekly New Investigations with Victims_cc | Derived | Test | P-1 | ||
| ICMS1355 | Ability to run automated report - Weekly New Preliminary Investigations_cc | Derived | Test | P-1 | ||
| ICMS1356 | Ability to run automated report - Weekly O&R Report | Derived | Test | P-1 | ||
| ICMS1357 | Ability to run automated report - Weekly Potential COVID-19 Report | Derived | Test | P-1 | ||
| ICMS1358 | Ability to run automated report - Weekly Potential NDAA Report | Derived | Test | P-1 | ||
| ICMS1359 | Ability to run automated report - Weekly T Complaints Report | Derived | Test | P-1 | ||
| ICMS1360 | Ability to run automated report - Weekly Undesignated Complaints | Derived | Test | P-1 | ||
| ICMS1361 | Ability to run automated report - Weekly USERRA Report | Derived | Test | P-1 | ||
| ICMS1362 | Ability to run automated report - Weekly M & R Complaint Draft Report | Derived | Test | P-1 | ||
| ICMS1363 | Ability to run automated report - Whistleblower Closed Cases | Derived | Test | P-1 | ||
| ICMS1364 | Ability to run automated report - Whistleblower Defined Report | Derived | Test | P-1 | ||
| ICMS1365 | Ability to run automated report - Whistleblower Ombudsperson Tracking Report | Derived | Test | P-1 | ||
| ICMS1366 | Ability to run internal case-related report - Complaint Form | Derived | Test | P-1 | ||
| ICMS1367 | Ability to run internal case-related report - Complaint Form except Confidential | Derived | Test | P-1 | ||
| ICMS1368 | Ability to run internal case-related report - Investigations Report | Derived | Test | P-1 | ||
| ICMS1369 | Ability to run internal case-related report - Closing Certification with Narrative | Derived | Test | P-1 | ||
| ICMS1370 | Ability to run internal case-related report - Closing Certification without Narrative | Derived | Test | P-1 | ||
| ICMS1371 | Ability to run external/ad hoc report – SAC’s Call Report | Derived | Test | P-1 | ||
| ICMS1372 | Ability to run former Crystal report - BOP Referral Memo | Derived | Test | P-1 | ||
| ICMS1373 | Ability to run former Crystal report - Overall Component Rating | Derived | Test | P-1 | ||
| ICMS1374 | Ability to run former Crystal report - ROI Tracking Report - Semiannual | Derived | Test | P-1 | ||
| ICMS1375 | Ability to run former Crystal report - BOP Closed or Referred within 6 Months | Derived | Test | P-1 | ||
| ICMS1376 | Ability to run former Crystal report - Cases Closed with Subject Outcomes | Derived | Test | P-1 | ||
| ICMS1377 | Ability to export reports/case documents into a structured PDF format | Derived | Test | P-1 | ||
| ICMS1378 | The system must have mandatory form field indicator that clearly shows a user which fields must be completed. | Derived | Test | P-1 | ||
| REQ1400 | The system shall have extensive search capabilities. | Derived | Demo | P-1 | ||
| ICMS1401 | Ability to conduct extensive searches capabilities. Search/query results should not be limited and include results of the universe.in the number of records returned. | Derived | Test | P-1 | ||
| ICSM1402 | Entered data elements shall be searchable | Derived | Test | P-1 | ||
| ICSM1403 | Documents imported shall be searchable | Derived | Test | P-1 | ||
| ICSM1404 | Searches shall support multiple data formats | Derived | Test | P-1 | ||
| REQ1600 | Security I. (Role-Based Access): The system shall have role-based access to a case/files/documents. | Derived | Demo | P-1 | ||
| ICMS1601 | Ability to allow the system administrator to assign role attributes | Derived | Test | P-1 | ||
| ICMS1602 | Ability to track changes to records via an audit trail (Read and Write). | Derived | Test | P-1 | ||
| ICMS1603 | Ability to track view auditing (record opened / viewed) | Derived | Test | P-1 | ||
| ICMS1604 | Ability to have permission levels that can be set by the System Administrator | Derived | Test | P-1 | ||
| ICMS1605 | Data shall be accessible by authenticated users | Derived | Test | P-1 | ||
| ICMS1606 | Data shall be accessible by authorized users | Derived | Test | P-1 | ||
| ICMS1607 | Data fields shall be viewable based on assigned user roles | Derived | Test | P-1 | ||
| ICMS1608 | Data fields shall be editable based on assigned user roles | Derived | Test | P-1 | ||
| ICMS1609 | Supervisors shall have the ability to electronically review agent cases (ex. Review workload queue) | Derived | Test | P-1 | ||
| ICMS1610 | Supervisors shall have the ability to electronically manage agent cases (ex. Reassign case) | Derived | Test | P-1 | ||
| ICMS1611 | Supervisors shall have the ability to electronically comment on agent cases | Derived | Test | P-1 | ||
| ICMS1612 | Ability to allow for Group access to a case. Groups consist of specific individuals representing multiple roles | Derived | Test | P-1 | ||
| ICMS1613 | Ability to develop various user roles and assign role-based permissions | Derived | Test | P-1 | ||
| ICMS1614 | Ability to designate an “Acting Supervisor” to perform the next higher-level functions within the system. When an “Acting Supervisor” is selected, the permissions from the actual supervisor shall not be removed. | Derived | Test | P-1 | ||
| REQ1700 | Security II. The system should request for credentials to access the application | Derived | Demo | P-1 | ||
| ICMS1701 | The system shall allow single sign on (SSO) via the Personal Identity Verification (PIV) card. | Derived | Test | P-1 | ||
| ICMS1702 | The system shall be PIV-enabled by accepting HSPD-12 PIV credentials as a method of identity verification and authentication. | DOJ | Test | P-1 | ||
| ICMS1703 | The system must demonstrate the ability to correctly work with PIV credentials by responding to the cryptographic challenge in the authentication protocol before granting access. | DOJ | Test | P-1 | ||
| REQ1800 | User Dashboard: The system should have a dynamic, customizable, real-time dashboard. | Derived | Demo | P-1 | ||
| ICMS1801 | The dashboard shall display the status of a user’s cases (approvals, denials, pending, completed) | Derived | Test | P-1 | ||
| ICMS1802 | The dashboard shall display the user’s specific reports | Derived | Test | P-2 | ||
| REQ1900 | The system shall support data analytics of case records | Derived | Demo | P-1 | ||
| Non-Functional (Technical) Requirements | ||||||
| REQ ID | Requirements | Source | Verification Method | Priority | Yes | No |
| (1-3) | ||||||
| T-REQ100 | System Availability (SA): The system shall have 99.999% availability time/Uptime. | Derived | Analysis | P-1 | ||
| T-REQ200 | Web Browser: Ability to utilize a web browser-based interface. | Derived | Test | P-1 | ||
| ICMS201 | The system shall be compatible with Microsoft Web browser | Derived | Test | P-2 | ||
| ICMS202 | The system shall be compatible with Google Web browsers | Derived | Test | P-2 | ||
| ICMS203 | The system shall be compatible with Mozilla browsers | Derived | Test | P-2 | ||
| T-REQ500 | System Integrations – Ability to import flat (text-based) data files from external organizations. | Derived | Test/Inspection | P-1 | ||
| ICMS501 | Ability to import large data files from the NFC (National Finance Center) | Derived | Test/Demo | P-1 | ||
| ICMS502 | Subsequent fields should be included to capture to transfer of these records to the National Archives and Records Administration. Associated records disposal fields/activities should also be captured. | Derived | Test/Inspection | P-1 | ||
| ICMS503 | Ability to generate and transmit a National Incident-Based Reporting System (NIBRS) report to FBI CJIS. The exported report shall be able to be electronically transmitted to CJIS in their required format, capturing the required data fields in their required format. A query-able record of transmission to the CJIS shall remain documented in the system. | Derived | Test/Inspection | P-1 | ||
| ICMS504 | Ability to export select investigative files to NARA through one of their approved electronic media methods. The physical transfer will be handled by the government; however, the system shall have a way to document the date a permanent investigation was transferred to NARA for safekeeping and have customizable data elements (e.g., date transferred, NARA reference number). Similarly, the system shall have a way to automatically calculate a destruction date for investigations and complaints entered into the system. There shall also be a date field to capture when the aforementioned matters are destroyed/deleted. Deleted files shall include the associated SharePoint folders, not the data entry portions that shall be retained for historical and reporting purposes. | Derived- | Test/Inspection | P-1 | ||
| T-REQ600 | Data Migration – Ability to migrate data from the current IDMS Case Management system into the Power Platform ICM Case Management system. | Derived | Inspection | P-1 | ||
| ICMS601 | Ability to import / view all data from legacy IDMS | Derived | Inspection | P-1 | ||
| ICMS602 | Ability to migrate iManage documents of various file types into the case management system (e.g., SharePoint 2019) (See Attachment 1 for file types). | Derived | Inspection | P-1 | ||
| T-REQ700 | The system shall utilize configurable workflows processes to define all level of activities to manage a case. | Derived | Analysis/Demo | P-1 | ||
| T-REQ800 | File/Document Management. | Derived | Analysis | P-1 | ||
| ICMS801 | Ability to integrate with SharePoint 2019 On-Premises | Derived | Test | P-1 | ||
| ICMS802 | Ability to automatically create a folder when a new case is created | Derived | Test | P-1 | ||
| ICMS803 | Ability to export all documents, evidence listing, and activities associated to a case for court proceedings/discovery requirements. | Derived | Test | P-1 | ||
| ICMS804 | Ability to import and store various electronic evidence types. | Derived | Test | P-1 | ||
| ICMS805 | Ability to store copies of original documentation | Derived | Test | P-1 | ||
| ICMS806 | Ability to store various media files. | Derived | Test | P-1 | ||
| ICMS807 | Ability to store data fields related to case actions | Derived | Test | P-1 | ||
| ICMS808 | Ability to store data fields related to case results | Derived | Test | P-1 | ||
| ICMS809 | Ability to store narrative files/documents | Derived | Test | P-1 | ||
| ICMS810 | Each case file shall have a total file attachment capacity of at least 4 gigabytes | Derived | Test | P-1 | ||
| ICMS811 | Ability to allow total file attachment capacity to be configurable per case file | Derived | Test | P-2 | ||
| ICMS812 | The system shall not automatically modify the title of a file | Derived | Test | P-1 | ||
| ICMS813 | Users shall have the option to modify the title of a file | Derived | Test | P-1 | ||
| IDMS814 | Ability to upload entire document folder at one time. | Derived | Test | P-1 | ||
| IDMS815 | The system shall support drag & drop of documents for uploading | Derived | Test | P-1 | ||
| T-REQ900 | The software must allow a user to navigate by mouse, touch, and keyboard. | Derived | Test | P-1 | ||
| T-REQ1000 | The system shall support a tracking component for ITD/INV (ISB) administration. | Derived | Test | P-1 | ||
| T-REQ1100 | A built-in helpdesk shall be created to track user requests for assistance, the status of the request, and the disposition. These requests shall be able to be tracked numerically, by fiscal year. The ability for users to request assistance within the case management system shall be made available. | Derived | Test/Inspection | P-1 | ||
| T-REQ1200 | Ability to integrate with the DOJ OIG Active Directory in order to pull user information ex: Name, Office Location, etc. (Application shall be able to support 150 concurrent users, with the capability to expand as necessary) | Derived | Test | P-2 | ||
| T-REQ1300 | A built-in tracker to monitor bugs or requests for future development shall be added. This tracker shall be jointly monitored by ITD and INV ISB’s system administrators. The requirement to numerically track the status of requests, by fiscal year, and a status/disposition. | Derived | Test/Inspection | P-2 |
File details come from the government source that posted it. Updated .