FEMA capability index
Find the DART workflow for each of the 61 capabilities in FEMA’s survey.
How to use the capability index
A long requirements list is easier to review when each entry leads to an explanation. This index maps the 61 capabilities in FEMA’s survey to DART. Each entry links to the page that explains the related work.
The short labels summarize the survey. They do not replace its full text. The index describes application behavior, not an agency acceptance decision.
The survey workbook is available directly from SAM.gov. FEMA’s public notice includes the attachments and amendments. The RFI overview explains the request and how vendors were asked to respond.
Capability-by-capability coverage
The entries are grouped in the same order as the survey, so readers can move between the two. Open an entry to learn how the workflow works. The federal deployment pages explain the agency services and reviews it needs.
1.1 Professional development
Assign task books and inspect their requirements. Record evidence and review each task.
Pair a person with a mentor. Keep meetings and reviews with the dated relationship.
Set development goals and track progress. Link courses and supporting evidence.
Review a responder’s deployment performance. Keep the original review when a correction is made.
1.2 Training administration
Check eligibility before enrollment. Manage funding decisions and waitlists.
Check instructor credentials against class dates. Review outside instructor requests.
Keep versions of shared course materials. Review the impact before applying an update.
Accept student and instructor files through scan and release checks.
Collect course feedback and learning results. Keep them available for review.
Notify people when a course they need becomes available.
Schedule classes and record attendance. Support field and classroom work as well as online delivery.
Update course information and active status. Keep earlier versions.
1.3 Learning delivery
Deliver online lessons and save progress. Review imported course packages before publishing.
Score quizzes and assignments. Use test-out options and assign extra practice where needed.
Track lesson work and course completion. Review results in the gradebook.
1.4 Training records
Award course credit when completion rules are met. Keep verification and correction history.
Let people read their own training records. Apply scoped access for supervisors and specialists.
Bring training and certificates together in a transcript. Preserve their history and evidence.
Record revoked or expired credentials. Let readiness reflect the current evidence.
2.1 Equipment
Track issued equipment and its holder. Review returns and retain custody history.
2.2 Availability
Record available and unavailable dates. Review changes that need supervisor approval.
2.3 Deployments and travel
Record daily replies and approved exceptions. Follow up on unresolved checks.
Review an order before sending it. Record the responder’s acceptance or decline.
Record station arrival and departure. Retain earlier times after a correction.
Use team templates with defined positions. Keep accepted membership history.
Check deployment types and overlapping work against incident rules.
Plan the deployment end. Complete required checks and resolve equipment holds before finishing.
Keep dated work and leave history. Use it to review duration and rest.
Store permanent and temporary locations under scoped access.
Add time across visits without double counting. Keep remote and physical work separate.
3.1 Incident data
Show incident needs beside the people assigned. Preserve the dates of the demand.
Create and review incident setup. Track the incident through its lifecycle.
3.2 Incident coordination
Record duties and supervision dates. Use them to determine review obligations.
Request people or team packages. Review other resource requests in the incident context.
Compare responders against the need. Save the evidence and selection reason.
4.1 Analytics and reporting
Keep historical records for past-time reports and comparisons.
Choose dashboard reports and filters. Save a layout within the user’s access.
Build reports with chosen fields and groups. Inspect current status or save a fixed result.
5.1 Access
Provide scoped offline responder work when enabled. Test speed on the agency network.
Adapt work screens to smaller displays. Test the supported devices and browsers.
Keep the local time zone for scheduling and availability.
Configure approved network access. Test the route inside and outside the agency network.
5.2 Compliance and exercises
Apply the application controls. Complete the agency’s security and accessibility review.
Run exercises in a separate workspace. Record results and follow-up work.
Apply CUI handling labels. Restrict exports and configured data combinations.
5.3 Interoperability
Map and review outside data. Connect agency interfaces through checked exchanges.
5.4 Support and adaptability
Provide help and support requests. Let users report bugs and suggest improvements.
Use shared navigation and record controls. Guide users through the real work screens.
Review performance and failures. Test and approve changes before recording a release.
Extend connected record types and pages. Apply the same permissions and history rules.
Search records the user may read. Open the result in its work context.
Keep English available. Offer reviewed translations of interface text.
5.5 Data quality
Correct a single record or preview a batch. Retain the saved changes and undo history.
Check source data before application. Review conflicting records and compare results.
5.6 Profiles and permissions
Assign permissions with dates and scope. Keep the history when access changes.
Keep stable person IDs and source links. Review duplicates and retain position history.
Separate self-service actions from staff permissions. Apply the right scope to each task.
5.7 Communications
Let users manage notices and preferences. Keep acknowledgments and replies.
Queue urgent notices and keep delivery attempts. Test live capacity for the expected surge.
Create groups for the right teams. Use configured audio and video providers.
Send messages with replies and attachments. Apply file and record access checks.
Evaluation questions beyond the capability list
A working feature is only one part of choosing and delivering a government system. The survey also asks about architecture and delivery. It asks how costs and risks will be managed. Those answers depend on the actual program.
An engagement-specific response supplies verified company facts. It names the staff and partners. It also sets prices and delivery dates. Contract terms and security commitments must be agreed for that engagement.