Questions_and_Answers_0001.pdf

1. PWS II.A Task 1 (page 7): Please confirm the expected total number of ShakeAlert Ready Branding Guide derivative resources (e.g., template types, icon sets) that must be delivered so we can scope graphic design labor accurately.

Answer: Undetermined. Use of existing resources (e.g. graphics, logos, etc.) will be emphasized to maintain the ShakeAlert brand. The need for new brand-aligned graphics might arise during the planning phase with the contractor.

2. PWS II.A Task 2 (page 8): For each of the six new park Fact Sheets, what finished page count or layout specification (e.g., tri fold brochure vs. single page PDF) should we assume?

Answer: On the order of 1-2 pages double-sided for each fact sheet.

3. PWS II.A Task 3 (page 8): Should the annual ShakeAlert Ready Schools curriculum assessment include original empirical research (e.g., educator surveys/focus groups) or rely solely on USGS supplied feedback?

Answer: Please see the PWS under task 3.

4. PWS II.A Task 3 (page 8): Are Learning Management System integrations required when updating ShakeAlert Ready Schools resources, and if so, does the government have a preferred LMS?

Answer: No LMS is required or needed for this project.

5. PWS II.A Task 4 (page 8): Please specify acceptable file formats and the required Section 508/WCAG conformance level for new ShakeAlert Ready CERT multimedia deliverables, if any.

Answer: This will be discussed but all resources (fact sheets, etc.) will be publicly available via .pdf and other formats that allow themselves to be distributed broadly via ShakeAlert.org. All source files for all of the deliverables must be provided to

USGS.

6. PWS III.A (page 9): Because in person gatherings are “desired but not required,” please indicate locations of on-site meetings so that travel can be priced accurately.

Answer: At most there could be one on-site planning meeting with the contractor, however, this will likely not be needed given the versatility of on-line meeting tools.

The single in-person meeting would be a project “kickoff” but again it likely will not be necessary.

7. FAR 52.212 1 (b)(4) Instructions (page 10): Is there a maximum page limit or individual file size limit for the Technical and Past Performance submission?

Answer: No preference.

8. PWS Task 3 (page 8): How many existing ShakeAlert Ready Schools lessons/pages/minutes must be reviewed so we can estimate instructional design hours and editing timelines?

Answer: There are lesson plans for grades: K-1, 2-3, 4-5, 6-8, and 9-12.

9. PWS Task 4 (page 8): What are the page or slide counts for the current CERT Participant Guide, Instructor Guides, and Presentations to quantify layout, multimedia conversion, and QC effort?

Answer: About 30.

10. PWS Tasks 1 2 (pages 7 8): Will USGS provide editable source design/video files, or must we rebuild assets from PDFs to determine graphic design LOE and software licensing costs?

Answer: USGS will provide these resources where available, however, contractor may need to create new graphics, etc. All new resources must have the same look and feel as other graphics, etc. in our collection. Use of the ShakeAlert trademark must conform with our guidelines. See: https://www.shakealert.org/system-information/shakealert-trademark-guidelines/

11. PWS Tasks 1 4 (pages 7 8): Are any additional languages or localizations required so we can budget translation, subtitling, and bilingual SME review?

Answer: All resources will be English-only. English subtitles will be required for any videos and alt text for graphics.

12. PWS II.A “Deliverable Review and Feedback Process” (page 7): What Government review turnaround time and maximum revision cycles should we assume to build a realistic schedule and reserve labor for edits?

Answer: This is dependent on the type of deliverable and the issues to be addressed. Every effort will be made to be as efficient as possible. In the beginning, while the contractor is learning about ShakeAlert core messaging, trademark guidelines, etc. there may be the need for additional review and revision cycles.

13. PWS II.A “CEO\&TE Focus Team” (pages 6 7): What average frequency and duration of Focus Team meetings are expected so we can price facilitation hours beyond weekly PM calls?

Answer: Focus team meetings are held monthly during the performance period with the possibility of having one or two additional meetings to address more complex project issues.

14. PWS II.A shared drive reference (page 7): Which collaboration platform will USGS host, or what security specs apply if we host it so we can plan IT provisioning, ATO compliance, and ODC licensing?

Answer: USGS utilizes Office365 resources so using OneDrive is an option. Other options can be explored with the contractor.

15. PWS Task 2 & Task 4 multimedia bullets (page 8): What preferred resolution/encode settings and distribution platforms apply to new videos/animations so we can scope editing hours, storage, and delivery specs?

Answer: All videos produced for this project should be available in 480p, 720p, and 1080p in order to maximize the ways that the resources can be used (in social media, on web pages, in slide decks, museum displays, and potentially on tv).

16. PWS Task 3 (page 8): How many ShakeAlert powered schools or districts will participate in surveys/focus groups to estimate survey admin hours, incentives, and data analysis effort?

Answer: Undetermined. This depends on the number of schools participating during the PoP.

17. Is there an incumbent contractor? If so, what is its name and contract number?

Answer: No incumbent contractor is exercising the implementation phase of ShakeAlert Ready since it is a new project.

18. If there is an incumbent contractor, has the scope or size of the contract changed in any nontrivial way between the incumbent contract and the present solicitation?

Answer: There is no incumbent contractor that is working on the implementation phase of ShakeAlert Ready since it is a new project

19. If there is no incumbent contractor, then are there existing contractor(s) that are doing some of the work of this PWS? If so, what are their name(s) and contract number(s)?

Answer: No incumbent contractor is exercising the implementation phase of ShakeAlert Ready.

20. If there are no contractors doing any of the work currently, then how is the work of the PWS being done? Or is it not being done at all?

Answer: Current work being done on ShakeAlert Ready is only in the areas of program and materials development. The implementation phase (e.g. rollouts, evaluation, development of branding guide, expansion planning) are new.

21. If the work of the PWS is not being done at all right now, then is there a backlog that the incoming contractor will have to handle? If so, please explain and describe how much of a backlog there is.

Answer: No backlog. The ShakeAlert Ready Implementation Project is a new project.

22. If there is an incumbent contract, is the scope and estimated workload for the present solicitation approximately the same as for the incumbent contract?

Answer: There was/is no incumbent contract for ShakeAlert Ready Implementation.

This is a new project. However, previous contracts have focused on ShakeAlert Ready feasibility, needs assessment, and materials development. This solicitation is fundamentally different in scope and workload so a comparison would not be accurate.