TOS_RFI Survey DTS 2.0_Finalized.xlsx
XLSX spreadsheet 133 KB Posted
- Attached to
- FEMA's Deployment Management Solution
- Solicitation number
- 70FA3126I00000008
- Issued by
-
Federal Emergency Management Agency
About this file
This is a Request for Information (RFI) survey in Microsoft Excel format designed to gather vendor responses regarding solutions to replace the Federal Emergency Management Agency's legacy Deployment Tracking System (DTS). The RFI is issued by FEMA under National Classification Code 541511 (Custom Computer Programming Services) and seeks Commercial Off-The-Shelf (COTS), Configurable COTS (CCOTS), custom, or hybrid cloud-based solutions that improve incident workforce management capabilities. Vendors must submit completed survey responses within two weeks of posting, with an additional two weeks allocated for feedback and follow-up discussions, for a total evaluation period of four weeks. Responses should be emailed to the FEMA contracting officer in the provided Excel document format.
The RFI covers four main sections: participant company profile; functional task capabilities across 17 subtasks organized under five key mission areas (workforce qualification, deployment management, event/incident management, data analytics and reporting, and system administration); system attributes including compatibility, vendor support, scalability, usability, customization, feedback mechanisms, and architecture; and cost, schedule, and risk considerations. Vendors must address whether they can meet each requirement with COTS, configuration, or customization; estimate required staffing effort using person-days; and provide detailed comments on their capabilities. Critical operational requirements include FedRAMP High Impact level cloud hosting, Technology Readiness Level 6 or higher, compliance with FEMA and DHS security standards, government cloud environment operation, and integration with existing FEMA/DHS systems. The underlying federal opportunity is estimated at $50 million to $100 million over five to ten years and seeks solutions supporting workforce readiness, personnel availability, deployment tracking, force package management, equipment assignment, analytics, and interoperability across the full deployment lifecycle.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI-Sources Sought Vendor Responses Profile Summary Template.xlsx | XLSX spreadsheet | |
| TOS_DTS 2.0 RFI Overview_9.23.2026.pdf |
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
Cover Sheet
Federal Emergency Management Agency (FEMA) Department of Homeland Security
North Atlantic Classification Code: Classification Code: 541511 - Custom Computer Programming Services
Deployment Management System Cloud Based Solution Request for Information (RFI)
Please complete information below:
Vendor: Address:
Primary Point of Contact
| Name: |
| Email: |
| Phone Number: |
Secondary Point of Contact
| Name: |
| Email: |
| Phone Number: |
Deadline: 2 weeks to complete the survey - 2 weeks for back and forth discussion
Navigation: Background and instructions sheet outlines in detail the entire survey please complete each sheet in its entirety.
Background & Instructions
| Background and Instructions |
| Instructions: Please fill out the form electronically within this Excel document and email the file to the FEMA contracting officer. |
| Deadline: The RFI should be submitted within 2 weeks of posting and allow for 2 weeks of feedback and follow-up for a total period of 4 weeks |
| Questions: If you have any questions about this questionnaire, please contact provide them to the CO in a word document that can be shared with the independent project team working this effort. |
| Purpose: FEMA is conducting market research to identify a COTS, configurable COTS, custom, or hybrid solutions capable of replacing the legacy Deployment Tracking System (DTS) and materially improving FEMA’s incident workforce management capabilities. The replacement solution should support workforce readiness, personnel availability, qualifications, certifications, training, deployment tracking, incident and event staffing, force package management, equipment assignment, reporting, analytics, secure cloud hosting, and interoperability with existing FEMA/DHS systems. FEMA is seeking information on solutions that improve readiness visibility, accelerate staffing, reduce manual work, strengthen data quality, support surge operations, improve reporting and analytics, and reduce long-term sustainment burden. |
FEMA has identified five key mission tasks:
| 1. | Ensure a qualified workforce | |
| 2. | Manage and track deployments | |
| 3. | Manage events and incidents | |
| 4. | Provide data analytics and reporting | |
| 5. | Enable system administration and support | |
| Desired Future State |
FEMA seeks a modern, scalable solution that enables improved management of the incident workforce across the full deployment lifecycle. The desired future state includes:
| • | Improved visibility into workforce availability, qualifications, skills, training dependencies, and deployment status. | |
| • | Faster identification, selection, notification, assignment, deployment, and demobilization of qualified personnel. | |
| • | Reduced manual data entry, spreadsheet-based tracking, duplicative workflows, and offline coordination. | |
| • | Better integration and interoperability across other critical government systems | |
| • | Improved analytics, and reporting to support operational decisions, leadership reporting, and surge planning. | |
| • | Scalable support for major disasters, Stafford Act and non-Stafford Act incidents, exercises, and DHS events | |
| • | Improved user adoption, workflow continuity, cybersecurity, auditability, and long-term sustainment. | |
| Questionnaire Content and Structure: This questionnaire covers a broad mix of functional tasks and system attributes. There are four sections of questions with each section having its own worksheet. The four sections include: | ||
| Section 1 - Participant profile questions | ||
| Section 2 - Questions regarding functional tasks | ||
| Section 3 - Questions regarding system attributes | ||
| Section 4 - Questions regarding cost, schedule, and risk |
Section 1 - Participant Profile includes several questions regarding your company and any teaming arrangements you may leverage as part of a Deployment Management System.
| Section 2 - Functional Tasks includes three questions for each of the 17 subtasks. The first two are standardized questions with drop down lists for responses. The third question provides the ability to expound or elaborate on the responses to the first two questions. The questions are as follows: |
| Question 1: Can your organization fulfill each requirement TODAY? If yes, is some level of configuration, customization? |
| Question 2: How much staff time would be required to fulfill each requirement (consider mid-level engineer for average person days)? Include time required to configure the system, create custom components, and any increase in testing beyond what would normally be required. |
| Question 3: Do you have any comments about your responses for each subtask? If YES, please use this column to expound on your responses. |
Section 3 - System Attributes includes a set of questions arranged by several system attributes applicable to any software system (e.g. compatibility, scalability, useability, etc…). The responses are free form.
Section 4 - Cost, Schedule (Sked), and Risk includes a set of questions in each of these programmatic areas. The responses are free form.
The "Necessary Capabilities" worksheet is provided for reference. It provides the necessary capabilities mapped to each subtask. This provides more detail when responding to Section 2.
Conditions & Assumptions:
· The solution will need to operate on a FedRAMP High Impact level cloud
· The number of simultaneous users, number, frequency, and size of deployments—will continue to grow
· The technology should be of sufficiently high maturity (greater than or equal to Technology Readiness Level (TRM) 6 such that it can be fielded by FEMA in timely manner
· Solution concepts should be compliant with FEMA and DHS security and IT standards, including cyber security and supply chain risk management. In addition, the solution must operate within the government owned cloud environment.
Section 1 - Solution Profile
| Information Domain: Solution Profile | |
| Question | Response |
| Company name, address, and the authorized POC responding to this RFI. | |
| Business size (i.e. Large, small, number of employee, market capitalization) | |
| Socioeconomic Designation (Small Disadvantaged, 8(a), Women-Owned, HUBZone, Veteran Owned and/or Service Disabled Veteran-Owned Business). | |
| Existing FEMA, DHS, GSA, or other Government contract(s) (Multiple Award IDIQs) If applicable |
Please provide Contract #, Period of Performance, and total value
| List the major partners that you would leverage in your solution. |
| Describe your market position and/or unique capabilities relative to the scope of this RFI. |
| Describe if you are the primary developer, reseller and/or integrator of the solution(s) you are recommending, providing overview of reseller and/or integrator relationships/dynamics. |
Section 2 - Functional Tasks
| Information Domain: Functional Tasks | ||||
| Task | Subtask (hyperlinks are provided to relevant necessary capabilities under each subtask) | Question 1: Can your organization meet this subtask? Please select from dropdown list. | Question 2: How much staff time would be required to meet this subtask (consider mid-level engineer for average person days)? Please select from dropdown list. | Question 3: Do you have any comments about your responses for each subtask? If YES, please use this column to expound on your responses (e.g. any assumptions associated with your response). |
| 1. Ensure a qualified workforce | 1.1. Facilitate professional development | |||
| 1.2. Manage training programs and curriculum | ||||
| 1.3. Deliver training and education content | ||||
| 1.4. Manage training records and certifications | ||||
| 2. Manage and track deployments | 2.1. Manage assigned equipment | |||
| 2.2. Update, maintain, and track personnel availability | ||||
| 2.3. Update, maintain, and track personnel deployment and travel | ||||
| 3. Manage events and incidents | 3.1. Create events and manage associated data | |||
| 3.2. Manage event and incident | ||||
| 4. Provide data analytics and reporting | 4.1. Enable standard and ad-hoc reporting | |||
| 5. Enable system administration and support | 5.1. Allow ubiquitous access | |||
| 5.2. Enable system compliance with applicable policies and regulations | ||||
| 5.3. Ensure integration and interoperability with other systems, as appropriate | ||||
| 5.4. Ensure system performance and useability | ||||
| 5.5. Manage system data and information | ||||
| 5.6. Manage user profiles and privileges | ||||
| 5.7. Provide communication and notification pathways | ||||
| Definitions for Question 1: | ||||
| Commerical Off the Shelf (COTS) | The released version of a COTS solution that includes those functions or capabilities are available to any authorized user upon initial hardware setup and software installation. | Custom - Full Custom | Customization of a COTS solution includes software development work to change or extend functionality of an existing COTS product, without resulting in changes to the core code of the COTS product.* Customization is any software change intended to address specific requirements that are not configuration as defined above. Software customization may be used to create reports, interfaces, conversion objects, extensions, forms, or other capability to satisfy requirements that could not otherwise be implemented by the configuration process. | |
| Configurable Commercial off the Shelf (CCOTS) | Configuration of a COTS solution includes any change within the defined set of COTS product parameters where a Government user with proper permissions can set, with no engineering services necessary, and does not result in customization of the COTS product (i.e., the configuration is compatible with future versions of the software). | Note: | * Core code is that which belongs to a module (or set of modules) that is commercially available, and changes to it would not be isolated to a single customer. |
Section 3 - System Attributes
| Informantion Domain: System Attributes | ||
| System Attribute | Question | Response |
| Compatibility | Can the solution seamlessly interconnect with other governement systems to pull data foundational to the tasks it will be executing? Do you have examples of this that you could provide? | |
| How does the software handle version updates, and what measures are in place to prevent integration issues? | ||
| Can the software seamlessly integrate with both cloud-based and on-premise solutions? | ||
| Vendor Support | How do you handle the integration of software with other existing systems, and what expertise do you have with similar integrations? | |
| Can you provide ongoing support after the initial implementation, and what is the structure of post-implementation support services? | ||
| Scalability | Can the software handle fluctuations in user load without compromising performance or user experience? Describe how it handles spikes in utilization. | |
| Usability | How much training is required to become proficient at using the software? | |
| Customization | Are there limitations on third-party integrations when extensive customizations are applied? | |
| Feedback Mechanism | In what ways does the software actively seek feedback, and how is feedback incorporated into future updates? | |
| Are there channels for direct communications between users and the development team for more nuanced feature requests? | ||
| Architecture | Is your solution built on a commercial platform? If so please provide. What is the hosting model, FedRAMP/ATO status or readiness, security boundary, identity and access management, Zero Trust alignment, logging, encryption, monitoring, resilience, continuity, and disaster recovery approach. |
Section 4 - Cost, Sked, Risk
| Information Domain: Cost, Schedule, Risk | ||
| Programmatic Area | Question | Response |
| Cost | What is your software pricing model (if COTS) and what are the cost drivers? Do you have a SaaS fee per user or do customers pay an initial SW cost with a recurring fee? | |
| If number of users is primary driver, what is the annual subscription or licensing cost per user? | ||
| How does the software accommodate changes in user count, and what is the pricing impact as the organization scales? | ||
| What are ROM labor costs for implementation, customization, training, testing, and integration given the relative size of the program? Breakout costs by O&M, Development, and subscription costs (Based on 1y/5y/10y). |
Elaborate on cost model and key drivers, including licensing, hosting, configuration, customization, migration, integrations, reporting, cybersecurity, training, support, surge usage, and recurring operations and maintenance.
| What are the cost drivers for data migration and do you have any heuristics for estimating the cost of data migration from legacy and internal DHS systems? | |
| Designate what costs are recurring vs non-recurring? | |
| Schedule | What pre-implementation steps are necessary to ensure a smooth transition to the new software? Describe the approach for integrating with Government systems, migrating legacy DTS data, cleansing and validating data, transitioning workflows and reports, supporting coexistence, conducting phased rollout and cutover, and decommissioning legacy capabilities. |
| Given a program of this size and scope, what is an expected range in months to reach Minimum Viable Prodcut and Full Deployment milestones? Recommended timeline, major phases, assumptions, dependencies, Government responsibilities, user training, change management, ATO activities, and continuity during implementation. | |
| Risk | In your experience, what risks and opportunities have you noted with similar implementations? Known risks or constraints related to migration, integrations, ATO, reporting, user adoption, customization, scalability, data quality, workflow change, surge usage, legacy coexistence, and sustainment. |
Necessary Capabilities
| Task | Subtask | Necessary Capability |
| 1. Ensure a qualified workforce | 1.1. Facilitate professional development | 1.1.1. Provide ability to manage Position Task Book assignment and completion. This includes: |
· the ability for defined users to complete Position Task Books (PTBs)
· the ability to assign one or more PTB to a user
· the ability for defined users to track progress towards an individual’s completion of position task book requirements. This includes tracking of all tasks and associated evaluations, as well as training.
· the ability for defined users to request one or more qualifications/positions, which align to PTBs
· the ability for defined users to explore available positions/qualifications and the requirements to achieve those positions/qualifications (these requirements are those outlined in PTBs)
| 1.1.2. Provide ability to manage mentorship programs. Such programs require pairing of an individual with a mentor, who is expected to provide coaching and subsequent evaluation of that individual. | |
| 1.1.3. Enable creation and tracking of independent development plan. The system allows users to create plans documenting training and education goals and progress in attaining them. | |
| 1.1.4. Provide ability to evaluate responders. The system allows supervisors to evaluate responders on their performance during deployment. This includes the ability to supervise responders and create, edit, and submit evaluations, which become part of that responder’s permanent record. | |
| 1.2. Manage training programs and curriculum | 1.2.1. Provide ability to manage course registration and wait lists. This includes the ability to: |
· enable defined users to register for courses and ensuring those users meet course eligibility requirements
· allow users to be added to wait lists for courses that are full
· allow for automatic enrollment for new hires and prerequisites
· configure automated processes aligned with position training requirements
· process multiple training application, authorization, and funding forms as required for course registration
| 1.2.2. Provide ability to manage instructors, including both contract and government employee instructors. The system needs to store instructor credentials and compare to appropriate standards required to teach their respective courses. |
| 1.2.3. Provide ability to manage training curriculum and content. This includes the following: |
· allowing for updates/changes to specific content
· allowing for cascading changes (changes that can be automatically implemented across courses, units, modules, etc.)
· ability to remove specific content
· ability to store course-related materials
· ability to store administrative material
· require administrative or supervisory permission to access course and course materials
· ability to serve as a training material repository that meets IT library best practices
| 1.2.4. Allow defined users to upload content, enabling students and instructors to be able to upload materials (e.g., completed assignments, lecture materials) to the system | |
| 1.2.5. Allow for surveys and polls to collect feedback from students, to enable the assessment of student satisfaction with courses and the evaluation of student learning according to Kirkpatrick levels I-IV. | |
| 1.2.6. Provide ability to notify defined users of available training courses. The system allows users who need a particular training course (e.g., to complete a requirement of their PTB) to be automatically notified if that course becomes available. | |
| 1.2.7. Provide ability to manage the scheduling of training courses. This includes the ability to manage the scheduling and rostering of mandatory and optional formal (schoolhouse) training, field delivered training, online training, and virtual training. It also includes management of instructor and student scheduling management within an organization and across the FEMA enterprise. | |
| 1.2.8. Provide ability to update course listings, including status (active/inactive), instructor information, and course information. | |
| 1.3. Deliver training and education content | 1.3.1. Provide ability to deliver online training content. Users need the ability to view and complete available online training courses. Training content may be delivered through various means, such as independent computer-based training, instructor-led online training, web-based training modules, asynchronous training, hybrid courses, and synchronous online training. The system also needs to provide the ability to adapt to support innovative instruction formats. |
| 1.3.2. Provide ability to evaluate and test learning. This includes the following: |
· ability to create a tailored module with specific knowledge student did not test well for
· allow for test-out opportunities when appropriate
· inform student on what specific aspects of learning they missed
· provide gradebook with rubrics
· allow for pre- and post-testing
· allow for standard and non-standard testing
| 1.3.3. Provide ability to track student progress, both through a course and through modules within a course. | ||
| 1.4. Manage training records and certifications | 1.4.1. Provide ability to award credit for courses, such as FQS training courses and other courses an individual takes in support of their duties. This includes the ability to automatically award credit to a person who successfully completes a course. | |
| 1.4.2. Provide ability for defined users to access training records. This includes the ability for responders to access their own training records and for supervisors or other authorized personnel to access others’ training records (e.g., to validate that PTB requirements are met). | ||
| 1.4.3. Provide ability to manage, store, and track current and historical position qualifications, specialties, certifications, and training. Included in this are the abilities to import and export certificates from external training and education courses/activities and generate unified transcripts. | ||
| 1.4.4. Provide the ability to manage decertification when a user no longer meets the requirements for any of the certifications they hold. | ||
| 2. Manage and track deployments | 2.1. Manage assigned equipment | 2.1.1. Provide ability to assign and track equipment status and readiness. This is limited to personal equipment issued to responders. |
| 2.2. Update, maintain, and track personnel availability | 2.2.1. Provide ability to manage and track workforce availability, including non-deployable status. This includes the ability for defined users to manage and self-report their availability, as well as the ability for supervisors to manage requests for availability and unavailability. | |
| 2.3. Update, maintain, and track personnel deployment and travel | 2.3.1. Provide ability to manage accountability. The system enables deployed personnel to provide daily accountability checks to support the monitoring of personnel safety and security. It also allows responders to provide accountability information throughout all phases of the deployment; this includes the ability to designate a reason that a responder may not be able to respond to accountability check-in requests (e.g., due to travel, hospitalization, or time zone alignment). | |
| 2.3.2. Provide ability to manage the deployment process. This includes the ability for defined users to issue, manage, track, and accept or decline deployment orders and requests, view associated information, and manage deployment status. | ||
| 2.3.3. Provide ability for responders to check-in and check-out at duty stations, which are the location to which an individual is deployed. | ||
| 2.3.4. Provide ability to manage different units such as teams, force packages, and force modules as well as individual responders. | ||
| 2.3.5. Provide ability to manage multiple deployments and multiple deployment types. This includes the ability to manage successive deployments; manage concurrent deployments; and manage multiple types of deployments (e.g., standard, virtual, training). | ||
| 2.3.6. Provide ability to schedule and prepare for responder demobilization. The system allows users to specify when the deployment of individual responders will end and identifies steps responders need to take in this process. | ||
| 2.3.7. Provide ability to track personnel status (e.g., deployment, leave, enhanced demobilization, medical leave, training, rotation, detail, etc.) and associated dates. The system allows users to track how long a responder has been deployed to an event and whether they have taken leave during or between deployments. This enables supervisors to ensure employees are provided with time to rest and recuperate between deployments to avoid burnout. | ||
| 2.3.8. Provide ability to record and update permanent and temporary duty stations, as well as the residence of record. The system allows users to document permanent or temporary location to which they are deployed and their permanent residences. Information needs to be accessible to users who need it (e.g., to ensure compliance with the 50-week rule). | ||
| 2.3.9. Provide ability to record how long a responder has been in a location across deployments. The system allows users to track the cumulative duration of time that they have been deployed to a specific location. System distinguishes between physical (geographical location) and virtual (remote) deployments. | ||
| 3. Manage events and incidents | 3.1. Create events and manage associated data | 3.1.1. Provide ability for defined users to aggregate and monitor relevant deployment and time-phasing information pertaining to an event/incident. This allows select users to view certain deployment data in the aggregate, as opposed to solely individual records. |
| 3.1.2. Provide ability for defined users to manage the event/incident lifecycle, including creating the event, assigning a unique identifier to the event, and deploying different force packages/force modules over time. | ||
| 3.2. Manage event and incident | 3.2.1. Provide ability to coordinate event/incident management activities such as assignments and evaluations. The system provides the ability to coordinate event/incident management activities such as assignments and evaluations. For example, the system allows the assignment of a responder to a supervisor at an event and requires that supervisor to evaluate the responder after they have been supervised for a certain period of time. | |
| 3.2.2. Provide ability to request specific types of responders, force packages, and force modules. Defined users can request specific types of responders, force packages, and force modules. | ||
| 3.2.3. Provide ability to identify responders eligible for deployment. The system provides the ability to review workforce availability, qualifications, and specialties in accordance with force package or module requirements. The system also enables the identification of available and suitable responders fairly and equitably. | ||
| 4. Provide data analytics and reporting | 4.1. Enable standard and ad-hoc reporting | 4.1.1. Provide ability to store historic data. Data can be used to enable analysis and reporting. |
| 4.1.2. Provide customizable/configurable dashboard capabilities. The system allows users to modify reporting dashboards. | ||
| 4.1.3. Provide flexible and customizable reports based on user-defined criteria. Reporting capabilities cover the following: |
· ability to analyze data related to the qualification process
· ability to analyze emerging incident workforce issues
· ability to assess and report on mission capability against standard metrics, pursuant to readiness requirements
· ability to assess deployment data
· ability to assess overall staffing and forecast staffing needs
· ability to generate and edit organizational structure reports (both during disaster and steady state operations)
· ability to provide standardized time-sensitive (real-time or near-real-time) status reports in support of disaster operations
· ability to assess training needs
· ability to analyze emerging incident workforce issues specific to an event or incident
· ability to assess event staffing and forecast staffing needs
· ability to compile and review data associated with events and incidents
| 5. Enable system administration and support | 5.1. Allow ubiquitous access | 5.1.1. Provide ability to access system under low bandwidth conditions. The system allows users to access it when internet transmission is slow. |
| 5.1.2. Provide ability to support user access from multiple types of devices and browsers. The system ensures that content is accessible on different types of devices, such as such as desktops, laptops, mobile phones, and tablets; and browsers. | ||
| 5.1.3. Provide ability to accommodate and adjust requirements for users across multiple time zones. The system can capture time zone differences. | ||
| 5.1.4. Allow access from both outside of and behind the FEMA firewall, enabling users to access the full functionality of the system whether or not they are connected to the FEMA network. | ||
| 5.2. Enable system compliance with applicable policies and regulations | 5.2.1. Provide ability to ensure compliance with all applicable policies and regulations regarding accessibility (508), records management, cybersecurity, and privacy. | |
| 5.2.2. Provide ability to support planned contingencies and conduct contingency planning and exercises. This includes the capability to test contingency plans and support exercises (which may replicate events) without impacting or interrupting current users or operations. | ||
| 5.2.3. Provide ability to handle controlled unclassified information (CUI) and mitigate issues associated with data aggregation. The system can identify, label, protect, and restrict access as appropriate the full range of CUI, and helps users avoid combining information that together might warrant higher levels of classification | ||
| 5.3. Ensure integration and interoperability with other systems, as appropriate | 5.3.1. Provide ability to integrate or interface with other systems, including both systems internal to FEMA and external to FEMA. | |
| 5.4. Ensure system performance and useability | 5.4.1. Enable customer support. This includes providing a customer support functionality (e.g., help desk); storage and access to training and guidance on how to use the system; the ability for all users to report bugs; and the ability for all users to recommend improvements. | |
| 5.4.2. Provide a standardized, intuitive user interface. The system has a standard, easy-to-use interface. | ||
| 5.4.3. Provide ability to manage system performance and testing new capabilities and features. This includes reporting on system performance; tracking needed and planned system improvements, upgrades, and patches; and allowing for all infrastructure hosting and maintenance. | ||
| 5.4.4. Provide flexible system architecture and solution adaptability. The system needs to be easily adaptable to meet changing needs, enable the addition of new capabilities with minimal impact to existing capabilities, and include interfaces that integrate with both current and future components. | ||
| 5.4.5. Provide search functionality. The system allows for searches across DTS. | ||
| 5.4.6. Provide language options. The system will employ English as the main language and will enable use of secondary languages. | ||
| 5.5. Manage system data and information | 5.5.1. Allow for manual and bulk updating of information within the system. The system allows users to update information with the system individually and in the aggregate. | |
| 5.5.2. Provide ability to manage data validation, quality assurance, and quality control. Personnel managing the system need to be able to validate that data are correct and ensure quality assurance and quality control, especially when, for example, system upgrades are implemented. | ||
| 5.6. Manage user profiles and privileges | 5.6.1. Provide ability to assign and update user role(s) and permissions, using a flexible user role and permissions structure. | |
| 5.6.2. Provide ability to create, modify, and store user profiles for all users. This includes management of associated information, including: |
· providing a unique identifier for each user
· ensuring that user profiles are unique (i.e., no user has more than one profile)
· providing the ability to manage and store an employee's past experience and assign equivalency for initial position assignments
· providing the ability to define, assign, update, and store multiple titles and roles across multiple events/incidents
· and providing the ability to for defined users to add and update contact information.
| 5.6.3. Provide ability for defined users to access and manage profiles, review qualifications, and designate position assignment. The system allows users to access and manage aspects of their own profiles, and authorized personnel (e.g., supervisors) can manage profiles, review qualifications, and designate position assignments. | |
| 5.7. Provide communication and notification pathways | 5.7.1. Provide ability for defined users to receive, manage, customize and respond to notifications as required. In addition to receiving notifications, users need to be able to manage and customize the types of notifications they receive. |
| 5.7.2. Provide ability to send high volume, high speed, and automated, interactive notifications, such as urgent announcements to deployed responders related to their deployment. | |
| 5.7.3. Provide ability to define and communicate with customized groups via multiple means. The system needs to enable messaging via text, as well as via video/audio. Different communication needs exist across the deployment workforce enterprise, ranging from deployment-related communications to course-related communications. For example, the system needs to enable written messaging between leadership/supervisors and responders. It also needs to enable both messaging and synchronous (e.g., audio/video) interactions between students and instructors. Customization of messaging groups is important to ensure the appropriate people receive communications and to account for the many nuances in disaster operations. | |
| 5.7.4. Provide ability to send a variety of message formats (e.g., questions, responses) and contents (e.g., pictures, links). |
Validation Lists
| Question 1 Response Options |
| YES: COTS no configuration or customization required |
| YES: CCOTS Solution available; configuration required |
| YES: Custom Solution available; customization required |
| No Capability Today: Enhancement needed and possible |
| No Capability Today: Enhancement not possible |
| Question 2 Response Options |
| Less than one person week |
| More than one person week, but less than one person month |
| 1-2 person months |
| 3-5 person months |
| More than 5 person-months |
| Solution Type |
| COTS |
| C-COTS |
| Custom |
image1.png
File details come from the government source that posted it. Updated .