Attachment 1 - Requirements Checklist.xlsx

SaaS video streaming platform USCA26Q0172 - Software as a service (SaaS) video streaming platform requirenment.

RFQ - Volume I: Technical Approach Attachment 1 Requirements Checklist

4. The platform shall maintain availability of no less than 99.9%, 24x7x365 (not including scheduled downtime)

1. Upload Media (2.10)

2. Search for assets

i. By all asset fields metadata fields including title, ID, description, keywords.

ii. Support Boolean, fuzzy, and exact match functions.

3. Sort and organize assets

i. Via metadata tagging and/or folder system into groups of media sometimes called projects, channels, and or playlists.

4. Manage and modify all media assets and their accompanying metadata including but not limited to

i. the ability to replace, update, or modify all metadata fields;

ii. the ability to download library assets for offline play;

iii. the ability to automatically assign and manually override thumbnails via integrated thumbnail generator or via still image file upload;

iv. the ability to seamlessly replace media or swap underlying media files that retains embed player; functionality, and associated metadata and viewer analytics consistency; and

v. the ability to delete and remove content at the discretion of the government.

1. stage projects for review;

2. collaborate with other authenticated court staff;

3. modify assets;

4. publish; and

5. generate embedded codes for display on both internet and intranet websites.

1. The CMS shall support browser-based single or multiple media file uploads.

2. The platform shall support simultaneous multi-file (batch) uploads via file exchange protocol:

i. FTP/SFTP and/or

ii. HTTP/HTTPS

1. Built-in play/pause.

2. Display video title and description.

3. Volume control button.

4. Mute button.

5. Togglable Full screen mode

6. Scrubber bar (to jump to specific point in playback).

7. Display time of asset playback and total run time.

8. Control of accessibility features, such as enabling/disabling closed captioning.

9. Support permanent links and dynamic embed code that works on modern browsers and devices.

10. Support fallback features for older browsers.

11. Support responsive web design players that scale up or down to fit screen sizes of any device, including personal computers, mobile phones, and tablets.

12. Players function as expected with supported versions of modern desktop and mobile browsers, including but not limited to Microsoft Edge, Chrome, Firefox, and Safari.

13. Players support mobile devices in full-screen mode, with playback controls.

14. Closed Captions: integrated synchronized captions from industry standard caption sidecar files (.vtt, .srt, etc.)

1. At a minimum, the automation tools must allow developers to script:

i. Access and modify metadata, title, description, and custom fields.

ii. Access and modify asset thumbnails.

iii. Access on demand assets for video and audio programming.

iv. Access lists of video/audio assets.

2. Generate data feeds for groups of video/audio assets (such as JSON or XML), which will be used to dynamically import and display content and associated metadata on third-party systems.

3. Ability to modify player embed codes to customize player features.

C C. The Contractor shall provide detailed documentation/instructions for all developer and automation tools.

1. Number of views/plays.

2. Number of unique viewers.

3. Watch time as either duration or percentage watched.

4. The following are not mandatory requirements but are preferred:

i. referral tracking and/or embed tracking

ii. Quality rendition watched out

iii. Full screen or not

iv. Player impressions

v. Playback device and/or browser version

i. in standard file format(s), such as CSV, JSON, XLSX, TSV.

1. The platform should have Single-sign-on support with the ability to integrate with the AOUSC and FJC separate Single Sign On (SSO) systems.

2.9 content management F. The following are not a mandatory, functional requirement but are preferred:

1. The CMS should support content trimming and editing features after media is uploaded.

i. The CMS Should support automation to collect episodes into a series projects, channels, and or playlists. An example of this would be the ability to set rules for media inclusion in a series project based on media metadata.

1. The platform should support custom transcoding profiles.

2.12 Integrated Players D. The following are not mandatory functional requirements but are preferred:

1. The platform should generate automatic closed captions.

i. Accessible Player Controls: Players must be navigable via keyboard and clearly labeled for screen readers, with no mandatory autoplay. All controls, including play, pause, volume, and seeking, must be operable via a keyboard, with a clear visible focus indicator.

ii. Readable Text & Contrast: Display high-contrast, legible text for on-screen information.

2.13 Metadata Capability C. The following are not mandatory functional requirements but are preferred:

1. The CMS should support speech recognition of English spoken in the media to conduct searches against.

2.14 Website Integration and developer tools D. The following are not mandatory functional requirements but are preferred:

1. Flexibility to customize platform players, use our own player, or use third-party players with assets on the platform.

2.15 Analytics D. The following are not mandatory functional requirements but are preferred

1. The platform should have the ability to integrate platform analytics with Google Analytics.