SOO Appendix C_FS_OSOH_WC_IntegratedProjectRequirements 3May2021 v3.xlsx
XLSX spreadsheet 64 KB Posted
- Attached to
- 2021 eSafety Recompete Federal contract opportunity
- Solicitation number
- 12760421Q0122
- Issued by
- Department of Agriculture Forest Service
About this file
This document outlines requirements for an integrated Workers' Compensation and Safety and Occupational Health case management, recording, and reporting software as a service solution. Key requirements include a web-based application compliant with Section 508 and various data security standards, functionality for incident reporting, case management, metrics dashboards, forms, templates, and interfaces to payroll, personnel, and other systems. The solution must provide role-based access, analytics, notifications, and support over 28,000 employees across multiple agencies. The SaaS licensing and maintenance will be provided under a recompete contract awarded by the Department of Agriculture Forest Service solicitation number 12760421Q0122.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Questions_Matrix_RFQ 12760421Q0122 - eSafety - 4 - Final.xlsx | XLSX spreadsheet | |
| RFP 12760421Q0122_ V2- Final 092621.pdf | ||
| RFP 12760421Q0142_ V2- Final 092621.pdf | ||
| QUESTIONS - 3 - Final.pdf | ||
| Questions_Matrix_RFQ 12760421Q0122 - eSafety - 4 - Final.xlsx | XLSX spreadsheet | |
| QUESTIONS - 5 FINAL.pdf | ||
| QUESTIONS - 6 - Final.pdf | ||
| RFQ 12760421Q0122 Questions - 1_update_092021 - FINAL.xlsx | XLSX spreadsheet | |
| USDA eSafety Questions - 2_update - FINAL.xlsx | XLSX spreadsheet | |
| SOHWC_RFP_Attachment_X_SOO_v6.1_092021 - Final.pdf | ||
| SOO Appendix C_FS_OSOH_WC_IntegratedProjectRequirements 31August2021 v4.xlsx | XLSX spreadsheet | |
| SOHWC RFP Attachment X SOO_v4_05202021.pdf | ||
| SOO Appendix E_Current Database Field Descriptions_2182021v1.docx | DOCX document | |
| ATTACHMENT 2.pdf | ||
| ATTACHMENT 1.pdf | ||
| SOO Appendix F_Commonly Used Forms_2182021v1.zip | ZIP file | |
| 12760421Q0122 - RFP Final.pdf |
Show all 17
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Safety
| Number | Step | Impact on Role/Data | Requirement | Acceptance Criteria | Priority | Fit-Gap Status | Comments |
| OSOH-1 | The system must be a Web based application. | Mandatory | |||||
| OSOH-2 | The system must support single sign-on. | Mandatory | |||||
| OSOH-3 | The system must be in compliance with laws and regulations. | Mandatory | |||||
| OSOH-3.1 | The system must be in compliance with OSHA laws and regulations, including 29 CFR 1904, Recordkeeping (e.g., generation of OSHA 300, 301, and 300A). | Mandatory | |||||
| OSOH-4 | The system must provide warning messages prior to automatically logging a user out, due to inactivity. | Mandatory | |||||
| OSOH-5 | The system must not exit users from the system due to capacity/load constraints. | Mandatory | |||||
| OSOH-6 | The system must provide standard out of the box capabilities for enterprise integration with document management, workflow management, case management and customer relationship management systems. | Mandatory | |||||
| OSOH-7 | The system shall adhere to current United States Department of Agriculture (USDA) Web standards (e.g., color, format, etc.) for each Agency. | Mandatory | |||||
| OSOH-8 | The system must be Section 508 compliant. | Mandatory | |||||
| OSOH-9 | The system must operate using a standard database (e.g. Oracle®). | Mandatory | |||||
| OSOH-10 | The system must back-up all records and associated files. | Mandatory | |||||
| OSOH-11 | The system must store data in compliance with Federal Data Retention Standards. | Mandatory | |||||
| OSOH-12 | The system must perform archiving without impacting system performance. | Mandatory | |||||
| OSOH-13 | The system must accommodate multiple records in support of 28,000 permanent and 12,000 seasonal employees at nine Regions, seven Research Stations, 158 National Forests and Grasslands, and 24 Job Centers, currently comprised of 821 OSHA establishments (locations). | Mandatory | |||||
| OSOH-14 | The system must accommodate an increase in volumes at any time, suddenly or gradually. | Mandatory | |||||
| OSOH-15 | The system must accommodate peak volumes. | Mandatory | |||||
| OSOH-16 | The system must monitor critical batch cycles between systems to completion. | Mandatory | |||||
| OSOH-17 | The system must automatically alert the Systems Administrator when utilization on application server or database server is exceeded (e.g., 85 percent). | Mandatory | |||||
| OSOH-18 | The system must automatically alert users when Web pages are unavailable. | Mandatory | |||||
| OSOH-19 | The system must be available for use via the Internet 24 hours a day and 7 days a week, except for negotiated periods of scheduled maintenance. | Mandatory | |||||
| OSOH-20 | The system must be available for a “specified percentage” of time (e.g., 98 percent). | Mandatory | |||||
| OSOH-21 | The system must not be down for more than a “specified number” of minutes during a peak period (e.g., 15 minutes). | Mandatory | |||||
| OSOH-22 | The system must not be down for more than a “specified number” of hours during non-peak (e.g., two hours). | Mandatory | |||||
| OSOH-23 | The system must be available based upon predetermined service level agreements (e.g., 24 hours a day, seven days a week, with a yearly availability of 99.9 percent). | Mandatory | |||||
| OSOH-24 | The system must keep a log of all maintenance activities, including scheduled preventive maintenance. | Mandatory | |||||
| OSOH-25 | The system must log documentation of all suspected faults in accordance with the USDA Incident Management Policy. | Mandatory | |||||
| OSOH-26 | The system must log all associated suspected fault remediation in accordance with the USDA Incident Management Policy. | Mandatory | |||||
| OSOH-27 | The system must log documentation of all actual faults in accordance with the USDA Incident Management Policy. | Mandatory | |||||
| OSOH-28 | The system must provide scheduled system maintenance which takes into account users in various time zones. | Mandatory | |||||
| OSOH-29 | The system must employ monitoring tools to monitor condition of the entire system. | Mandatory | |||||
| OSOH-30 | The system must employ monitoring tools to monitor usage of system resources. | Mandatory | |||||
| OSOH-31 | The system must notify affected users of a system outage when a user tries to access the system. | Mandatory | |||||
| OSOH-32 | The system must provide a complete copy of system records, including audit log records, for purpose of system restore. | Mandatory | |||||
| OSOH-33 | The system must notify a user with appropriate user roles via a system outage report. | Mandatory | |||||
| OSOH-34 | The system must notify a user with appropriate user roles of remediation procedures to solve system outage. | Mandatory | |||||
| OSOH-35 | The system must maintain a completely separate, duplicate instance of the application and all records for purposes of disaster recovery. | Mandatory | |||||
| OSOH-36 | The system must be able to load backup media. | Mandatory | |||||
| OSOH-37 | The system must be able to restore system data. | Mandatory | |||||
| OSOH-38 | The system must allow a user with appropriate user roles the ability to test system functionality, including security controls. | Mandatory | |||||
| OSOH-39 | The system must support Security Services (e.g., Federal Information Processing Standard (FIPS)). | Mandatory | |||||
| OSOH-40 | The system must be compliant with the National Institute of Standards and Technology 800-53 (NIST 800-53) standards. | Mandatory | |||||
| OSOH-41 | The system must authenticate users through USDA security and access controls. | Mandatory | |||||
| OSOH-42 | The system must deny access to the system for non-authenticated users. | Mandatory | |||||
| OSOH-43 | The system must enable functionality by a user's role within organizational level. | Mandatory | |||||
| OSOH-44 | The system must provide filtering capabilities on data. | Mandatory | |||||
| OSOH-45 | The system must display an error message when filtered data cannot be returned. | Mandatory | |||||
| OSOH-46 | The system must mask Personally Identifiable Information (PII) in data that is viewed in or exported from the system (where applicable) | Mandatory | |||||
| OSOH-46.1 | The system must mask Personally Identifiable Information (PII) in data that is viewed in or exported from the system (where applicable) and comply with Privacy Act, Americans with Disabilities Act (ADA), and Health Insurance Portability and Accountability Act (HIPAA) requirements for data storage, protection, and transmission. | Mandatory | |||||
| Dashboard | |||||||
| OSOH-47 | The system must provide a dashboard. | Mandatory | |||||
| OSOH-47.1 | The system must have the ability to provide a dashboard, per user, based on role. | Mandatory | |||||
| OSOH-47.2 | The system must have the ability to provide a dashboard, per user, based on organizational level, physical location, and OSHA establishment code. | Mandatory | |||||
| OSOH-48 | The system must have the ability to provide a dashboard, by Region/Station (R/S). | Mandatory | |||||
| OSOH-49 | The system must have the ability to provide a user-customizable dashboard. | Useful | |||||
| OSOH-50 | The system must provide a dashboard with a visual graphical display. | Critical | |||||
| OSOH-51 | The system must provide the ability to save user-defined formulas for metrics onto the user's personal dashboard. | Useful | |||||
| OSOH-52 | The system must provide a dashboard of near real-time indicators of selected metrics. | Critical | |||||
| OSOH-52.1 | The system must provide a dashboard of near real-time Leading Indicators. | Critical | |||||
| OSOH-52.2.1 | The system must provide a dashboard of near real-time indicators of Safety Program Evaluations (SPEs) due this fiscal year. | Critical | |||||
| OSOH-52.2.2 | The system must provide a dashboard of near real-time indicators of SPEs completed. | Critical | |||||
| OSOH-52.2.3 | The system must provide a dashboard of near real-time indicators of Safety Stories submitted. | Critical | |||||
| OSOH-52.2.4 | The system must provide a dashboard of near real-time indicators of Employee-Submitted Hazard Reports. | Mandatory | |||||
| OSOH-52.2 | The system must provide a dashboard of near real-time Trailing Indicators. | Critical | |||||
| OSOH-52.2.1 | The system must provide a dashboard of near real-time indicators of Total Cases Reported (e.g., fiscal/calendar year to date). | Mandatory | |||||
| OSOH-52.2.2 | The system must provide a dashboard of near real-time indicators of Total Case Rate (e.g., fiscal/calendar year to date). | Mandatory | |||||
| OSOH-52.2.3 | The system must provide a dashboard of near real-time indicators of total Occupational Safety and Health Administration (OSHA) Recordable Cases (e.g., fiscal/calendar year to date) and track metrics across time (current year and previous years) in support of reducing total injury and illness case rates for the PEER Initiative. | Mandatory | Dashboard applies to current year and previous year once data has been collected in the system. The goal is to capture data in the system from implementation forward for trending purposes. | ||||
| OSOH-52.2.4 | The system must provide a dashboard of near real-time indicators of OSHA Recordable Case Rate (e.g., fiscal/calendar year to date) and track metrics across time (current year and previous years) in support of reducing total injury and illness case rates for the PEER Initiative. | Mandatory | |||||
| OSOH-52.2.5 | The system must provide a dashboard of near real-time indicators of total Time Away (LTA) Cases (e.g., fiscal/calendar year to date) and track metrics across time (current year and previous years) in support of reducing lost-time injury and illness case rates for the PEER Initiative. | Mandatory | |||||
| OSOH-52.2.6 | The system must provide a dashboard of near real-time indicators of Lost Time Case Rate (LTAR) (e.g., fiscal/calendar year to date) and track metrics across time (current year and previous years) in support of reducing lost-time injury and illness case rates for the PEER Initiative. | Mandatory | |||||
| OSOH-52.2.7 | The system must provide a dashboard of near real-time indicators of Total Lost Work Days (e.g., fiscal/calendar year to date) and track metrics across time (current year and previous years) in support of reducing total injury and illness case rates for the PEER Initiative. | Mandatory | |||||
| OSOH-52.2.8 | The system must provide a dashboard of near real-time indicators of Lost Work Day Rate (e.g., fiscal/calendar year to date) and track metrics across time (current year and previous years) in support of reducing total injury and illness case rates for the PEER Initiative. | Mandatory | |||||
| OSOH-52.2.9 | The system must provide a dashboard of near real-time indicators of Restricted Duty Cases Total and track metrics across time (current year and previous years) in support of reducing total injury and illness case rates for the PEER Initiative. | Mandatory | |||||
| OSOH-52.2.10 | The system must provide a dashboard of near real-time indicators of Restricted Duty Case Rate and track metrics across time (current year and previous years) in support of reducing total injury and illness case rates for the PEER Initiative. | Mandatory | |||||
| OSOH-52.2.11 | The system must provide a dashboard of near real-time indicators of total Motor Vehicle Accident (MVA) Cases (e.g., fiscal/calendar year to date). | Mandatory | |||||
| OSOH-52.2.12 | The system must provide a dashboard of near real-time indicators of Chargeable MVA Cases (>$1,500). | Mandatory | |||||
| OSOH-52.2.13 | The system must provide a dashboard of near real-time indicators of Chargeable Motor Vehicle Accident Cases Frequency Rate. | Mandatory | |||||
| OSOH-52.2.14 | The system must provide a dashboard of near real-time indicators of Motorarized Vehicle Accidents Resulting in Personal Injury (e.g., fiscal/calendar year to date). | Mandatory | |||||
| OSOH-52.2.15 | The system must provide a dashboard of near real-time indicators of Number of FS Employee Fatalities (e.g., fiscal/calendar year to date) and provide trending data across time. | Mandatory | |||||
| OSOH-53 | The system must provide a user friendly interface. | Mandatory | |||||
| OSOH-53.1 | The system must provide tabs on the main page. | Mandatory | |||||
| OSOH-53.2 | The system must provide drop-down choices in user fields, where possible. | Mandatory | |||||
| OSOH-53.3 | The system must provide search functionality for large groupings. | Mandatory | |||||
| OSOH-53.4 | The system must provide the ability to use previously answered questions to populate forms and data. | Mandatory | |||||
| OSOH-54 | The system must provide the ability for users to answer questions in an interview style (e.g., text fields, drop-down fields, radio buttons, etc.). | Critical | |||||
| OSOH-55 | The system must provide the ability to interface with a portal (e.g., SharePoint®). | Mandatory | |||||
| OSOH-56 | The system must support a managerial view for dashboards. | Critical | |||||
| OSOH-57 | The system must provide the ability to generate updates/notifications for the users on the main page. | Critical | |||||
| OSOH-58 | The system must provide search capabilities for active cases, including but not limited to: | Mandatory | |||||
| OSOH-58.1 | The system must provide search capabilities for active cases by incident number. | Mandatory | |||||
| OSOH-58.2 | The system must provide search capabilities for active cases by Social Security Number (SSN). | Mandatory | |||||
| OSOH-58.3 | The system must provide search capabilities for active cases by last name. | Mandatory | |||||
| OSOH-58.4 | The system must provide search capabilities for active cases by Date of Birth (DOB). | Mandatory | |||||
| OSOH-58.5 | The system must provide search capabilities for active cases by Wildcard Search (*). | Mandatory | |||||
| OSOH-58.6 | The system must provide search capabilities for active cases by Multiple criteria (e.g., DOB and last name). | Mandatory | |||||
| OSOH-59 | The system must provide search capabilities for archived cases, including but not limited to: | Mandatory | |||||
| OSOH-59.1 | The system must provide search capabilities for archived cases by incident number. | Mandatory | |||||
| OSOH-59.2 | The system must provide search capabilities for archived cases by SSN. | Mandatory | |||||
| OSOH-59.3 | The system must provide search capabilities for archived cases by last name. | Mandatory | |||||
| OSOH-59.4 | The system must provide search capabilities for archived cases by DOB. | Mandatory | |||||
| OSOH-59.5 | The system must provide search capabilities for archived cases by Wildcard Search (*). | Mandatory | |||||
| OSOH-59.6 | The system must provide search capabilities for archived cases by multiple criteria (e.g., DOB and last name). | Mandatory | |||||
| OSOH-60 | The system must provide multiple search return formats, including but not limited to: | Critical | |||||
| OSOH-60.1 | The system must provide a list search return format. | Critical | |||||
| OSOH-60.2 | The system must provide an Employee history search return format. | Critical | |||||
| OSOH-61 | The system must provide the ability to sort returned (i.e., search) information. | Critical | |||||
| OSOH-62 | The system must provide the ability to delegate authority, based on user roles (access). | Mandatory | |||||
| OSOH-62.1 | The system must accommodate a change in available Supervisors. | Mandatory | |||||
| Analytics and Metrics | |||||||
| OSOH-63 | The system must provide the ability for pre-defined (standard) metrics to be accessed by the user. | Critical | |||||
| OSOH-64 | The system must provide for the ability for ad-hoc metrics to be accessed by the user. | Critical | |||||
| OSOH-65 | The system must provide the ability to save personalized metrics within a user's view. | Critical | |||||
| OSOH-66 | The system must provide the ability to display the source of data for metric calculations. | Useful | |||||
| OSOH-67 | The system must provide the ability to show the definition of metrics. | Critical | |||||
| OSOH-68 | The system must provide the ability to show the formula for the calculation(s) of the metric. | Critical | |||||
| OSOH-69 | The system must provide the ability to create trends for user defined data sets based on user defined periods of time. | Critical | |||||
| OSOH-70 | The system must provide the ability to view trends for user defined data sets based on user defined periods of time. | Critical | |||||
| OSOH-71 | The system must provide the ability to roll up/drill down on the available data by organization structure level 8. | Critical | |||||
| OSOH-72 | The system must provide the ability for the user to export a metric including all of the additional descriptive information related to that metric. | Useful | |||||
| OSOH-73 | The system must provide the ability to show the definition (including calculations) of a metric on an exported document. | Critical | |||||
| OSOH-74 | The system must provide the ability for a user to see a snapshot of accident records and to customize as needed within the vendor solutions capabilities. | Critical | |||||
| OSOH-75 | The system must provide the ability to view a snapshot (data at a specific point of time) of a user-defined data set based on user-defined time frame. | Critical | |||||
| OSOH-76 | The system must provide the ability for users to conduct forecasting (using historical information to determine trends) as needed within the vendor solutions capabilities. | Critical | |||||
| OSOH-77 | The system must provide the ability to conduct benchmarks against external organizations, given that the data is provided in the tool. | Useful | |||||
| System Rules | |||||||
| OSOH-78 | The system must achieve Authority to Operate (ATO). | Mandatory | |||||
| OSOH-79 | The system must support Web based access capabilities. | Mandatory | |||||
| OSOH-80 | The system must provide the ability to create business rules against the data (e.g., auto-calculations that trigger events, etc.). | Mandatory | |||||
| OSOH-81 | The system must be able to pre-populate data fields. | Mandatory | |||||
| OSOH-82 | The system must allow user to edit pre-populated data. | Mandatory | |||||
| OSOH-83 | The system must provide the ability to display choices via drop-down, where possible. | Mandatory | |||||
| OSOH-84 | The system must not require users to re-enter any data that is already contained in existing databases. | Critical | |||||
| OSOH-84.1 | The system must not require users to re-enter any data that is already contained in existing databases, including personal data made available from the Employee database of record (e.g., National Finance Center (NFC) Bi-Weekly Examination and Analytical Reporting (BEAR) file). | Critical | |||||
| OSOH-85 | The system must provide the ability to prohibit users from advancing under certain scenarios. | Critical | |||||
| OSOH-85.1 | The system must provide the ability to prohibit users from advancing if there is a change of date without justification. | Useful | |||||
| OSOH-85.2 | The system must provide the ability to prohibit users from advancing if there are blank fields (where mandatory or designated input is requested). | Mandatory | |||||
| OSOH-85.3 | The system must provide the ability to prohibit users from advancing if there is incomplete documentation. | Mandatory | |||||
| OSOH-86 | The system must support electronic signature. | Useful | |||||
| OSOH-87 | The system must provide an ability for free text and notes with audit capability. | Mandatory | |||||
| OSOH-88 | The system must provide the ability to save multiple comments. | Mandatory | |||||
| OSOH-88.1 | The system must provide the ability to save multiple comments in chronological order. | Mandatory | |||||
| OSOH-88.2 | The system must provide the ability to filter/sort multiple comments. | Critical | |||||
| OSOH-89 | The system must provide the ability to process analytics. | Critical | |||||
| OSOH-90 | The system must have email capabilities. | Mandatory | |||||
| OSOH-91 | The system must have fax capabilities. | Critical | |||||
| OSOH-92 | The system must provide save capabilities. | Mandatory | |||||
| OSOH-93 | The system must support auto save functionality. | Critical | |||||
| OSOH-94 | The system must provide the ability to notify a user prior to timing-out. | Mandatory | |||||
| OSOH-95 | The system must provide the ability to convert specific formats (e.g., date). | Mandatory | |||||
| OSOH-96 | The system must provide the ability to conduct auto calculations (where possible). | Mandatory | |||||
| OSOH-97 | The system must provide the ability to load all historical cases. | Mandatory | |||||
| OSOH-98 | The system must have the capability to associate Safety related forms with an IN. | Mandatory | |||||
| OSOH-98.1 | The system must have the capability to associate SF-91 forms with an IN. | Mandatory | |||||
| OSOH-98.2 | The system must have the capability to associate AD-112 forms with an IN. | Mandatory | |||||
| OSOH-99 | The system must allow users to determine a IN association based on data. | Critical | |||||
| OSOH-100 | The system must have the capability to associate corrective actions numbers to an IN. | Critical | |||||
| OSOH-100.1 | The system must have the capability to associate corrective actions to an audit number. | Critical | |||||
| OSOH-101 | The system must automate e-mail messaging to perform actions. | Mandatory | |||||
| OSOH-101.1 | The system must automate e-mail messaging to route documents. | Mandatory | |||||
| OSOH-101.2 | The system must automate e-mail messaging to advise users of the next steps. | Mandatory | |||||
| OSOH-102 | The system must provide provisions for alerts when a process action has not been completed within designated time frames. | Critical | |||||
| Alerts/ Notifications | |||||||
| OSOH-103 | The system must provide alerts. | Mandatory | |||||
| OSOH-103.1 | The system must alert users of mandatory printing requirements. | Mandatory | |||||
| OSOH-104 | The system must provide auto generated notifications upon entry of any incident. | Mandatory | |||||
| OSOH-105 | The system must default notifications to individuals. | Mandatory | |||||
| OSOH-105.1 | The system must provide the ability to add/delete recipients for notifications. | Mandatory | |||||
| OSOH-105.2 | The system must default notifications to User's Supervisor. | Mandatory | |||||
| OSOH-105.3 | The system must default notifications to the Designated Safety Manager. | Mandatory | |||||
| OSOH-106 | The system must provide notification when additional action is required (e.g., when completing fields/forms/etc., prior to allowing the user to progress within the solution). | Mandatory | |||||
| OSOH-107 | The system must provide the ability to notify a user when he/she accesses a record that someone is currently accessing. | Critical | |||||
| OSOH-107.1 | The system must provide the ability to identify initial user when he/she accesses a record that someone is currently accessing. | Critical | |||||
| OSOH-107.2 | The system must provide the ability to limit secondary access to “read-only” when two users are accessing the same record. | Critical | |||||
| OSOH-108 | The system must provide the ability to provide receipt notification. | Useful | |||||
| OSOH-109 | The system must provide the ability to display error notification. | Critical | |||||
| OSOH-110 | The system must allow users to over-write fields of any provided Supervisor or Safety Manager. | Mandatory | |||||
| OSOH-110.1 | The system must allow users to over-write Name fields of any provided Supervisor or Safety Manager. | Mandatory | |||||
| OSOH-111 | The system must default notifications when a Supervisor record is overwritten. | Mandatory | |||||
| OSOH-112 | The system must notify the appropriate party when a field is overwritten. | Useful | |||||
| OSOH-113 | The system must generate incident e-mail notifications. | Mandatory | |||||
| OSOH-113.1 | The system must generate incident e-mail notifications to contain Date of the incident. | Mandatory | |||||
| OSOH-113.2 | The system must generate incident e-mail notifications to contain Time of the incident. | Mandatory | |||||
| OSOH-113.3 | The system must generate incident e-mail notifications to contain Subject of the incident. | Mandatory | |||||
| OSOH-114 | The system must provide provisions for alerts when a process action has not been completed within designated time frames. | Critical | |||||
| OSOH-115 | The system must provide a calendar functionality based on user notifications/due dates/future notifications. | Useful | |||||
| OSOH-116 | The system must provide a drop-down functionality for a user to select the month, date and year of a data field (separate drop-down for each element). | Critical | |||||
| User Roles/ Access | |||||||
| OSOH-117 | The system must provide the ability for the user to log multiple case statuses, including but not limited to: | Mandatory | |||||
| OSOH-117.1 | The system must provide the ability for the user to log open case statuses. | Mandatory | |||||
| OSOH-117.2 | The system must provide the ability for the user to log action needed case statuses. | Mandatory | |||||
| OSOH-117.3 | The system must provide the ability for the user to log pending case statuses. | Mandatory | |||||
| OSOH-117.4 | The system must provide the ability for the user to log incomplete case statuses. | Mandatory | |||||
| OSOH-117.5 | The system must provide the ability for the user to log completed case statuses. | Mandatory | |||||
| OSOH-117.6 | The system must provide the ability for the user to log medical only case statuses. | Mandatory | |||||
| OSOH-117.7 | The system must provide the ability for the user to log first-aid case statuses. | Mandatory | |||||
| OSOH-118 | The system must provide role-based security. | Mandatory | |||||
| OSOH-119 | The system must provide user/administrator roles, including but not limited to: | Mandatory | |||||
| OSOH-119.1 | The system must provide a read only role. | Mandatory | |||||
| OSOH-119.2 | The system must provide a create role. | Mandatory | |||||
| OSOH-119.3 | The system must provide an administer role. | Mandatory | |||||
| OSOH-120 | The system must provide user/administrator roles to allow minor system configuration. | Mandatory | |||||
| OSOH-120.1 | The system must provide user/administrator roles to make status updates. | Mandatory | |||||
| OSOH-121 | The system must provide access to a shared reporting library for all users. | Mandatory | |||||
| OSOH-122 | The system must be accessible to all users upon request. | Mandatory | |||||
| OSOH-122.1 | The system must be accessible to all FS Employees. | Mandatory | |||||
| OSOH-122.2 | The system must provide alternative access (e.g., new hires, 1039-seasonal employees, non-Employees, Administratively Determined (AD) Employees, Volunteers, etc.). | Mandatory | |||||
| OSOH-122.2.1 | The system must capture basic personal information about non-Employees who access the system. | Mandatory | |||||
| Archive/ Print/Export | |||||||
| OSOH-123 | The system must provide the ability to archive. | Mandatory | |||||
| OSOH-124 | The system must be able to print, including but not limited to: | Mandatory | |||||
| OSOH-124.1 | The system must be able to print/Portable Data Format (PDF) functionality. | Mandatory | |||||
| OSOH-124.2 | The system must be able to print/PDF case details. | Mandatory | |||||
| OSOH-124.3 | The system must be able to print/PDF case summary. | Mandatory | |||||
| OSOH-124.4 | The system must be able to print/PDF forms. | Mandatory | |||||
| OSOH-125 | The system must be able to print reports, including but not limited to: | Mandatory | |||||
| OSOH-125.1 | The system must be able to print Incident reports. | Mandatory | |||||
| OSOH-125.2 | The system must be able to print near-miss/Safety Story reports. | Mandatory | |||||
| OSOH-125.3 | The system must be able to print work-related illness reports. | Mandatory | |||||
| OSOH-125.4 | The system must be able to print work-related injury reports. | Mandatory | |||||
| OSOH-125.5 | The system must be able to print OSHA Logs. | Mandatory | |||||
| OSOH-125.6 | The system must be able to print OSHA Summary Reports. | Mandatory | |||||
| OSOH-126 | The system must provide export capabilities, including but not limited to: | Mandatory | |||||
| OSOH-126.1 | The system must provide PDF export capabilities. | Mandatory | |||||
| OSOH-126.2 | The system must provide Microsoft® Products export capabilities (e.g., Word, Excel®, etc..) | Mandatory | |||||
| OSOH-126.3 | The system must provide Email export capabilities. | Mandatory | |||||
| OSOH-126.4 | The system must provide Visual (graphics) export capabilities. | Mandatory | |||||
| OSOH-127 | The system must have the ability to create PDF files. | Mandatory | |||||
| OSOH-128 | The system must provide audit trail capabilities. | Mandatory | |||||
| OSOH-128.1 | The system must provide a log of changes (e.g., audit trail) to any record. | Mandatory | |||||
| OSOH-128.2 | The system must provide a touch record log (any time a user has viewed a record). | Critical | |||||
| OSOH-128.3 | The system must provide a log of changes (e.g., audit trail) to any record after its initial review/approval by the Safety Manager. | Critical | |||||
| OSOH-128.4 | The system must provide an audit trail of the Date of changes. | Mandatory | |||||
| OSOH-128.5 | The system must provide an audit trail of the Time of changes. | Mandatory | |||||
| OSOH-128.6 | The system must provide an audit trail of the User(s) who performed changes. | Mandatory | |||||
| OSOH-128.7 | The system must provide an audit trail of the Field(s) that were changed. | Critical | |||||
| OSOH-128.8 | The system must provide an audit trail of the action performed (changed from/to). | Mandatory | |||||
| OSOH-128.9 | The system must provide an audit trail of the changes made by third parties (e.g., NFC, Paycheck8, etc.). | Mandatory | |||||
| OSOH-128.10 | The system must provide an audit trail of the creation date. | Mandatory | |||||
| OSOH-129 | The system must provide the ability to directly access changes captured in audit history, as well as associated documents. | Useful | |||||
| OSOH-130 | The system must provide the ability to add attachments. | Mandatory | |||||
| OSOH-131 | The system must support a resume library by attaching the PDF versions. | Critical | |||||
| Interfaces | |||||||
| OSOH-132 | The system must provide inbound interfaces. | Mandatory | |||||
| OSOH-133 | The system must provide outbound interfaces. | Mandatory | |||||
| OSOH-133.1 | The system must provide for inbound EDI capabilities for standard HR data and fields (e.g., NFC EmpowHR) | Mandatory | |||||
| OSOH-133.2 | The system must provide for an inbound EDI with a standard Time and Attendance (T&A) System | Mandatory | |||||
| OSOH-133.3 | The system must provide bi-directional EDI capabilities with CRM. | Mandatory | |||||
| OSOH-133.4 | The system must provide bi-directional EDI capabilities with the NFC Equipment Management Information System (EMIS). | Useful | |||||
| OSOH-133.5 | The system must provide bi-directional EDI capabilities with the General Services Administration (GSA) system. | Useful | |||||
| OSOH-133.6 | The system must provide inbound EDI capabilities with GovTrip. | Useful | |||||
| OSOH-134 | The system must interface with Self-Service Dashboard (SSD) to implement role based accesses and receipt of Human Resources data from the existing Human Resources management System (HRIS). | Mandatory | |||||
| Miscellaneous | |||||||
| OSOH-135 | The system must support a help feature. | Mandatory | |||||
| OSOH-135.1 | The system must support a reference library. | Mandatory | |||||
| OSOH-135.2 | The system must support a Frequently Asked Questions (FAQ) guide. | Mandatory | |||||
| OSOH-135.3 | The system must support definitions. | Mandatory | |||||
| OSOH-135.4 | The system must support an acronym list. | Mandatory | |||||
| OSOH-135.5 | The system must support a DOL directory. | Mandatory | |||||
| OSOH-135.6 | The system must support a USDA directory. | Critical | |||||
| OSOH-135.7 | The system must support mouse over functionality. | Critical | |||||
| OSOH-135.8 | The system must support an Office of Personnel Management (OPM) Library (e.g., series, pay plan, grade, title, etc.) for a dictionary of terms. | Critical | |||||
| OSOH-135.9 | The system must support paybanding dictionary. | Critical | |||||
| OSOH-136 | The system must support a resume library via a staff acquisition solution (e.g., eRecruit). | Useful | |||||
| OSOH-137 | The system must support spell/grammar check. | Critical | |||||
| OSOH-137.1 | The system must support spell/grammar check with edit/add functionality (role-based). | Critical | |||||
| OSOH-137.2 | The system must support spell/grammar check with auto capitals. | Critical | |||||
| OSOH-138 | The system must provide the ability to support social media. | Useful | |||||
| OSOH-138.1 | The system must provide the ability to support communicator. | Useful | |||||
| OSOH-139 | The system must provide the ability to identify records based on telecommunications. | Useful | |||||
| OSOH-139.1 | The system must provide the ability to identify incident number based on telecommunications. | Mandatory | |||||
| OSOH-140 | The system must provide the ability to direct reply to outgoing emails back to the appropriate Safety Manager. | Mandatory | |||||
| OSOH-141 | The system must provide the ability to add/edit/delete Points of Contact (POCs), addresses, etc., to provide to the Safety Manager. | Critical | |||||
| OSOH-142 | The system must provide ability to identify region based on Employee organization code (Level 8). | Mandatory | |||||
| Reporting | |||||||
| OSOH-143 | The system must provide the ability to produce standard reports. | Mandatory | |||||
| OSOH-143.1 | The system must produce the OSHA Logs. | Mandatory | |||||
| OSOH-143.2 | The system must produce OSHA Summary Reports. | Mandatory | |||||
| OSOH-143.3 | The system must produce the USDA Annual Report DOL/OSHA. | Critical | |||||
| OSOH-143.4 | The system must produce Days Away/Restricted Time reporting as a report for Safety Managers at each level to Organization level 5 of the organization. | Mandatory | |||||
| OSOH-143.5 | The system must produce Motor Vehicle Accident (MVA) Frequency Rates based on vehicle data. | Mandatory | |||||
| OSOH-143.6 | The system must produce a Personal Injury rate report. | Mandatory | |||||
| OSOH-143.6.1 | The system must produce a Personal Injury rate report by Organization Code. | Mandatory | |||||
| OSOH-143.6.2 | The system must produce a Personal Injury rate report by OSHA Recordables. | Mandatory | |||||
| OSOH-143.6.3 | The system must produce a Personal Injury rate report by Hours Worked. | Mandatory | |||||
| OSOH-143.6.4 | The system must produce a Personal Injury rate report by Number of Employees. | Mandatory | |||||
| OSOH-144 | The system must support mandated reporting for injured employees to support compliance with the Dingell Act, S 47 Section 1114 – Section G, Firefighter Injuries Database, Section 9 (a) of the Federal Fire Prevention and Control Act of 1974 (15 U.S.C. 2208) including data entry, search, and reporting. | Mandatory | |||||
| OSOH-144.1 | The system must support mandated reporting to identify if the injured employee is a firefighter. | Mandatory | |||||
| OSOH-144.2 | The system must support mandated reporting to identify if the injured firefighter sought treatment for the injuries from a licensed practitioner (i.e., Medical Professional) | Mandatory | |||||
| OSOH-144.3 | The system must support mandated reporting to identify if the injury resulted in the firefighters death. | Mandatory | |||||
| OSOH-144.4 | The system must support mandated reporting to identify if the injury/death was a result of participation in a "pack test" or "Work Capacity Test" (WCT) or while preparing for a pack test/WCT. | Mandatory | |||||
| OSOH-144.5 | The system must support mandated reporting to identify if the injury/death was a result of a Motorized Vehicle Accident (MVA). | Mandatory | |||||
| OSOH-144.6 | The system must support mandated reporting to identify if the injury/death resulted from an aircraft crash. | Mandatory | |||||
| OSOH-144 | The system must provide the ability to report on archived data. | Mandatory | |||||
| OSOH-145 | The system must be able to report on data in all tables and fields. | Mandatory | |||||
| OSOH-146 | The system must provide access to all data within forms, templates, tables, etc. | Mandatory | |||||
| OSOH-147 | The system must provide query capabilities. | Mandatory | |||||
| OSOH-148 | The system must provide the ability to automate reports. | Mandatory | |||||
| OSOH-149 | The system must provide the ability to email reports. | Critical | |||||
| OSOH-150 | The system must provide the ability to attach comments to the report. | Critical | |||||
| OSOH-151 | The system must support audit-trail functionality with reports. | Critical | |||||
| OSOH-151.1 | The system must support an audit-trail functionality of the Report Name. | Critical | |||||
| OSOH-151.2 | The system must support an audit-trail functionality of the Date/Time. | Critical | |||||
| OSOH-151.3 | The system must support an audit-trail functionality of payment made. | Critical | |||||
| OSOH-152 | The system must provide the ability to produce ad-hoc reports. | Mandatory | |||||
| OSOH-153 | The system must generate ad-hoc reports and graphical charts. | Critical | |||||
| OSOH-154 | The system must provide version control. | Mandatory | |||||
| OSOH-155 | The system must provide role-based functionality to edit reports. | Mandatory | |||||
| OSOH-155.1 | The system must provide role-based functionality to sort reports. | Mandatory | |||||
| OSOH-156 | The system must provide functionality to filter reports. | Mandatory | |||||
| OSOH-157 | The system must provide calculation functionality (where possible). | Mandatory | |||||
| OSOH-158 | The system must provide the ability to select a random sample of data (fields as pre-defined by the user) to generate a report (e.g., internal user audit for accuracy (Quality Control)) | Mandatory | |||||
| OSOH-159 | The system must support the ability to produce trend reports. | Mandatory | |||||
| OSOH-160 | The system must provide the ability to convert query to report. | Mandatory | |||||
| OSOH-161 | The system must provide the ability to generate reports on standard templates, forms, etc. | Critical | |||||
| OSOH-162 | The system must provide the ability to generate reports based on audit-trail functionality. | Mandatory | |||||
| OSOH-163 | The system must provide capabilities for EDI of summary data and reports. | Critical | |||||
| Templates and Forms | |||||||
| OSOH-164 | The system must provide the ability to produce templates on Department letterhead. | Critical | |||||
| OSOH-165 | The system must allow users to edit selected fields in standard templates. | Mandatory | |||||
| OSOH-166 | The system must support role-based functionality to edit standard templates. | Mandatory | |||||
| OSOH-167 | The system must support role-based functionality to delete standard templates. | Mandatory | |||||
| OSOH-168 | The system must support role-based functionality to add standard templates. | Mandatory | |||||
| OSOH-169 | The system must provide an Agency configurable standard template library. | Mandatory | |||||
| OSOH-170 | The system must support links to standard templates. | Mandatory | |||||
| OSOH-171 | The system must provide the ability to record sent templates/forms. | Mandatory | |||||
| OSOH-171.1 | The system must provide the ability to record sent templates/forms within the tool. | Critical | |||||
| OSOH-171.2 | The system must provide the ability to record sent templates/forms via Carbon Copy (cc)/Blind Carbon Copy (bcc) email. | Useful | |||||
| OSOH-172 | The system must provide a cross-match with the Organization code versus charge back code and alert the user. | Critical | |||||
| OSOH-173 | The system must allow a user to edit content of the template, based on user-role. | Mandatory | |||||
| OSOH-174 | The system must allow manual entry of forms for Casual Employees or non-Employees. | Mandatory | |||||
| OSOH-175 | The system must auto-generate Standard Forms. | Mandatory | |||||
| OSOH-176 | The system must support auto population of forms. | Mandatory | |||||
| OSOH-176.1 | The system must auto-populate SF91 (i.e., Motor Vehicle Accident Report). | Mandatory | |||||
| OSOH-176.2 | The system must auto-populate AD112 (i.e., Report of Unserviceable, Lost, Stolen, Damaged, or Destroyed Property). | Mandatory | |||||
| OSOH-176.3 | The system must auto-populate AD872 (i.e., Property Damage Incident). | Mandatory | |||||
| OSOH-176.4 | The system must auto-populate SF-91A (i.e., Investigation Report of Motor Vehicle Accident). | Mandatory | |||||
| OSOH-176.5 | The system must auto-populate SF-94 (i.e., Statement of Witness). | Mandatory | |||||
| OSOH-177 | The system must provide the capability to capture and populate Safety Program Evaluation checklists. | Critical | |||||
| OSOH-178 | The system must support standard forms (e.g., DOL). | Mandatory | |||||
| OSOH-179 | The system must provide the ability to prohibit a user from saving a form when certain fields are not completed. | Mandatory | |||||
| OSOH-180 | The system must support role-based functionality to perform actions on standard forms. | Mandatory | |||||
| OSOH-180.1 | The system must support role-based functionality to add standard forms. | Mandatory | |||||
| OSOH-180.2 | The system must support role-based functionality to edit standard forms. | Mandatory | |||||
| OSOH-180.3 | The system must support role-based functionality to delete standard forms. | Mandatory | |||||
| OSOH-180.4 | The system must support role-based functionality to approve standard forms. | Mandatory | |||||
| OSOH-180.5 | The system must prohibit the user from making changes to forms after they have been submitted. | Mandatory | |||||
| OSOH-181 | The system must be able to record other costs not paid by the DOL. | Mandatory | |||||
| Links | |||||||
| OSOH-182 | The system must provide ability to link to external Web sites. | Useful | |||||
| OSOH-182.1 | The system must provide ability to link to Social Security Index. | Useful | |||||
| OSOH-183 | The system must provide links to specific documentation including, but not limited to: | Critical | |||||
| OSOH-183.1 | The system must provide links to Standard Operating Procedure (SOP) (stored in application behind firewall). | Critical | |||||
| OSOH-183.2 | The system must provide links to Code of Federal Regulations (CFR). | Critical | |||||
| OSOH-184 | The system must provide ability to hyperlink to documentation (if you were working on a case and there was documentation attached, being able to click the link and read it). | Critical | |||||
| Investigation Management | |||||||
| OSOH-185 | The system must associate Safety and Health investigation information with the associated Coordinated Response Protocol (CRP) process. | Critical | |||||
| OSOH-186 | The system must trigger safety investigations. | Useful | |||||
| OSOH-186.1 | The system must allow a user to trigger an investigation based upon the risk indicator. | Useful | |||||
| OSOH-186.1.1 | The system must calculate a risk indicator score based on pre-defined information. | Useful | |||||
| OSOH-187 | The system must provide a module to record and track Agency incident investigations. | Critical | |||||
| OSOH-187.1 | The system must provide a module to record and track Agency investigations into MVA incidents. | Critical | |||||
| OSOH-187.2 | The system must provide a module to record and track Agency investigations into injury incidents. | Critical | |||||
| OSOH-188 | The system must generate letters. | Critical | |||||
| OSOH-188.1 | The system must generate 24 hour notification letters. | Useful | |||||
| OSOH-188.2 | The system must generate 72 hour notification letters. | Useful | |||||
| OSOH-189 | The system must generate investigation reports. | Critical | |||||
| OSOH-189.1 | The system must generate incident investigation reports. | Critical | |||||
| OSOH-189.2 | The system must generate claim investigation reports. | Critical | |||||
| OSOH-189.3 | The system must generate factual investigation reports. | Critical | |||||
| OSOH-189.4 | The system must generate management review reports. | Critical | |||||
| OSOH-190 | The system must allow users to upload artifacts related to investigations. | Critical | |||||
| OSOH-190.1 | The system must allow users to upload evidentiary documents. | Critical | |||||
| OSOH-190.2 | The system must allow users to upload witness statements. | Critical | |||||
| OSOH-190.3 | The system must allow users to upload photos. | Critical | |||||
| OSOH-190.4 | The system must allow users to upload video. | Useful | |||||
| OSOH-190.5 | The system must allow users to upload audio. | Useful | |||||
| OSOH-191 | The system must link all supporting investigation documentation to the associated incident. | Critical | |||||
| OSOH-192 | The system must generate timelines (e.g., incident, case). | Critical | |||||
| OSOH-193 | The system must generate chronologies (e.g., incident, case). | Critical | |||||
| OSOH-194 | The system must automatically generate one or more e-mail notifications to an investigator upon appointment. | Useful | |||||
| OSOH-195 | The system must capture investigation findings. | Mandatory | |||||
| OSOH-195.1 | The system must capture third party investigation findings. | Critical | |||||
| OSOH-196 | The system must allow users to generate, print and/or electronically transfer investigation reports. | Critical | |||||
| OSOH-197 | The system must provide role-based functionality to perform investigative actions. | Critical | |||||
| OSOH-197.1 | The system must provide role-based functionality to recommend corrective actions. | Critical | |||||
| OSOH-197.2 | The system must provide role-based functionality to authorize corrective actions. | Critical | |||||
| OSOH-197.3 | The system must provide role-based functionality to implement corrective actions. | Critical | |||||
| OSOH-197.4 | The system must provide role-based functionality to monitor corrective actions. | Critical | |||||
| OSOH-198 | The system must track Lessons Learned and Continuous Improvement from investigations. | Critical | |||||
| OSOH-198 | The system must capture anonymous reports of questionable behavior (e.g., associated with incident, MVA, etc.). | Useful | |||||
| OSOH Module | |||||||
| Incident | |||||||
| OSOH-199 | The system must allow users to enter initial details of an incident (e.g., accident, near-miss or work-related illness). | Mandatory | |||||
| OSOH-199.1 | The system must allow each user to update data as information changes, with the date and time of the change reflected in system information. For example, the accident employee, supervisor, and Safety Manager must be able to update the Days Away, Restricted, or Transferred (DART) information continuously, without locking them out of the system (i.e., no restriction that the incident cannot be edited after 24 hours). | Mandatory | |||||
| OSOH-200 | The system must allow users to identify incident or accident witnesses. | Mandatory | |||||
| OSOH-201 | The system must automatically generate one or more e-mail notifications to a witness(es) upon identification of witnesses. | Critical | |||||
| OSOH-202 | The system must allow the user to perform incident report actions prior to submission. | Mandatory | |||||
| OSOH-202.1 | The system must allow the user to review incident report prior to submission. | Mandatory | |||||
| OSOH-202.2 | The system must allow the user to update incident report prior to submission. | Mandatory | |||||
| OSOH-203 | The system must maintain data libraries. | Mandatory | |||||
| OSOH-203.1 | The system must maintain an Incident Folder. | Mandatory | |||||
| OSOH-203.2 | The system must maintain an Employee Folder. | Mandatory | |||||
| OSOH-203.3 | The system must maintain an Audit library. | Mandatory | |||||
| OSOH-203.4 | The system must maintain a Facility library. | Mandatory | |||||
| OSOH-203.5 | The system must maintain an MVA Incidents library. | Mandatory | |||||
| OSOH-203.6 | The system must maintain a Liability Claims library. | Mandatory | |||||
| OSOH-204 | The system must index records of incident by certain data fields. | Mandatory | |||||
| OSOH-204.1 | The system must index records of incident by User's name. | Mandatory | |||||
| OSOH-204.2 | The system must index records of incident by SSN. | Mandatory | |||||
| OSOH-204.3 | The system must index records of incident by Date of accident. | Mandatory | |||||
| OSOH-204.4 | The system must index records of incident by Organization Code. | Mandatory | |||||
| OSOH-204.5 | The system must index records by Zip code of the incident location, where applicable. | Mandatory | |||||
| OSOH-204.6 | The system must index records by fire name, where applicable. | Mandatory | |||||
| OSOH-205 | The system must categorize incident reports into the various and specific activities of fire management. | Mandatory | |||||
| OSOH-206 | The system must allow users to download blank incident reporting forms. | Useful | |||||
| OSOH-207 | The system must allow users to print blank incident reporting forms. | Useful | |||||
| OSOH-208 | The system must allow users to capture incidents. | Mandatory | |||||
| OSOH-208.1 | The system must allow users to capture Near Miss, Safety Hazards and Safety Stories incidents | Mandatory | |||||
| OSOH-208.2 | The system must allow users to capture incidents of Work-related illnesses. | Mandatory | |||||
| OSOH-208.3 | The system must allow users to capture incidents of Work-related injuries. | Mandatory | |||||
| OSOH-208.4 | The system must support role-based functionality to capture law enforcement reports. | Mandatory | |||||
| OSOH-208.5 | The system must support role-based functionality to capture coroner reports. | Mandatory | |||||
| OSOH-209 | The system must allow users to report potential safety issues. | Mandatory | |||||
| OSOH-210 | The system must allow users to report anonymous Near Miss, Safety Hazards and Safety Stories incidents. | Mandatory | |||||
| OSOH-211 | The system must allow users to report motorized vehicle accidents. | Mandatory | |||||
| OSOH-211.1 | The system must allow users to capture drive time immediately prior to incident. | Mandatory | |||||
| OSOH-212 | The system must maintain a database of all reported incidents. | Mandatory | |||||
| OSOH-213 | The system must support role-based functionality (e.g., Supervisors or Safety Managers) to perform actions related to incident reports. | Mandatory | |||||
| OSOH-213.1 | The system must support role-based functionality (e.g., Supervisors or Safety Managers) to edit incident reports. | Mandatory | |||||
| OSOH-213.2 | The system must support role-based functionality (e.g., Supervisors or Safety Managers) to approve incident reports. | Mandatory | |||||
| OSOH-213.3 | The system must support role-based functionality (e.g., Supervisors or Safety Managers) to disapprove incident reports. | Mandatory | |||||
| OSOH-213.4 | The system must support role-based functionality (e.g., Supervisors or Safety Managers) to route incident reports back to Employee for additional information. | Mandatory | |||||
| OSOH-213.5 | The system must support role-based functionality (e.g., Supervisors or Safety Managers) to delete incident reports. | Mandatory | |||||
| OSOH-213.6 | The system must support role-based functionality (e.g., Supervisors or Safety Managers) to attach comments to incident reports. | Mandatory | |||||
| OSOH-214 | The system must allow categorization by individual of Incident reports. | Mandatory | |||||
| OSOH-214.1 | The system must allow categorization by Employee of another government Agency of Incident reports. | Mandatory | |||||
| OSOH-214.2 | The system must allow categorization by Volunteer of Incident reports. | Mandatory | |||||
| OSOH-214.3 | The system must allow categorization by Job Corp worker of Incident reports. | Mandatory | |||||
| OSOH-214.4 | The system must allow categorization by Contractor of Incident reports. | Mandatory | |||||
| OSOH-214.5 | The system must allow categorization by Concessionaire of Incident reports. | Mandatory | |||||
| OSOH-214.6 | The system must allow categorization by Emergency worker of Incident reports. | Mandatory | |||||
| OSOH-214.7 | The system must allow categorization by Fire Fighter of Incident reports. | Mandatory | |||||
| OSOH-214.8 | The system must allow categorization by General Public of Incident reports. | Mandatory | |||||
| OSOH-215 | The system must store each incident report entered into the system in a temporary file. | Mandatory | |||||
| OSOH-216 | The system must support role-based functionality to move each incident report to the permanent database after it has been marked as reviewed. | Mandatory | |||||
| OSOH-217 | The system must allow the user to capture data in a Corrective Actions Folder. | Mandatory | |||||
| OSOH-217.1 | The system must allow the user to capture the Corrective Action Number. | Mandatory | |||||
| OSOH-217.2 | The system must allow the user to capture Facility Name. | Mandatory | |||||
| OSOH-217.3 | The system must allow the user to capture the Responsible Party. | Mandatory | |||||
| OSOH-217.4 | The system must allow the user to capture the Short Description of Corrective Actions. | Mandatory | |||||
| OSOH-217.5 | The system must allow the user to capture Follow-up Actions. | Mandatory | |||||
| OSOH-217.6 | The system must allow the user to capture Lessons Learned information. | Mandatory | |||||
| Motorized Vehicle Accidents (MVA) |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .