SATPC0042337 Tab 04 4 SOW.pdf
PDF 248 KB Posted
- Attached to
- Software Development Federal contract opportunity
- Solicitation number
- 80NSSC26940387Q
About this file
This is a Statement of Work (SOW) for NASA defining functional requirements for the custom development and upgrade of a scheduling module within the ReadyOp tool.
The SOW encompasses five primary functional categories. Resource & Availability Management requires the module to support flexible individual schedules for people, rooms, and equipment with configurable availability windows, blackout periods, advance notice requirements, and administrator override capabilities. Administrators must specify standard time blocks (such as 30 minutes) that users can extend through consecutive bookings. Schedule Groups & Classifications functionality must enable grouping of individual schedules by building or service, support direct resource booking or "first available" selection within groups, and allow administrators to reassign existing appointments between resources within the same group. User Experience & Automation requirements include mandatory ReadyOp Form submission before booking completion, support for additional participants, automatic ICS calendar invite distribution upon confirmation, recurring booking capability, and duplicate prevention by email address. Administrative Oversight & Reporting mandates centralized dashboards displaying bookings by schedule/classification/group, cancellation controls with role-based permissions, and permanent exportable audit trails recording who performed actions, timestamps, specific actions taken (created/modified/deleted), and before-and-after data values. Access Control requirements specify role-based access controls for event creation and editing, with location-based security permitting permissions assignment to individual schedules or groups to enable local management without global system access.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| SATPC0042337 Tab 07 Capability Statement.pdf |
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
NASA - Scheduling Module - SOW
ReadyOp Scheduling Module: Functional Requirements
The Statement of Work defines the parameters for the custom development of upgrading the scheduling capability inside the ReadyOp tool.
Resource & Availability Management
• Flexible Schedules: The module must support the creation of individual schedules for people, rooms, and equipment, allowing tailored management for each resource.
• Availability Rules: The system needs to accommodate specific availability windows, such as Monday through Friday, 8 AM to 5 PM. Additionally, it should permit the definition of blackout periods, including holidays and recurring breaks.
• Advance Notice: The scheduling module should enforce a minimum lead time for bookings, preventing last-minute or same-day registrations.
• Admin Overrides: Administrators must have the ability to override blackout dates and lead-time rules, enabling manual creation or rescheduling of appointments when necessary.
• Duration Controls: Administrators should be able to specify a standard time block (such as 30 minutes) and allow users to book consecutive blocks for extended sessions.
Schedule Groups & Classifications
• Group Logic: The module should provide functionality for grouping individual schedules, such as those for a specific building or service (e.g., "Building 25 Badging").
• Smart Booking: Users must be able to either book a specific resource directly or select a "first available" option within a group.
• Resource Reassignment: Administrators should have the ability to transfer an existing appointment from one resource to another within the same group. For example, moving a booking from Terminal 1 to
Terminal 2 at a specific time.
User Experience & Automation
• Form Integration: The module should allow for the requirement of a ReadyOp Form submission before a booking can be completed.
• Participant Support: Users must be able to add additional attendees when making a booking.
• Calendar Sync: Upon booking confirmation, the system should automatically send ICS calendar invites to all participants.
• Recurring Bookings: The module must support the scheduling of repeating events.
• Duplicate Prevention: The system should check for existing entries, such as by email address, to ensure that an individual cannot register multiple times within a specified period.
Administrative Oversight & Reporting
• Centralized Viewing: Administrators should have access to dashboards that display all bookings by individual schedule, classification, or group.
• Full Cancellation Control: Both users and administrators must be able to cancel appointments to release time slots, with permissions based on user role.
• Audit Trails: The system should maintain a permanent, exportable log of all activity. This log must record:
o Who performed the action and when.
o The specific action taken (created, modified, or deleted).
o The "before and after" values for any changed data.
Access Control
• Granular Permissions: The module should implement role-based access controls, determining who can create or edit events.
• Location-Based Security: Permissions should be assignable to individual schedules or groups, enabling local management of specific buildings or rooms without granting global access to the entire system.
File details come from the government source that posted it. Updated .