B08_Solicitation_140P6024Q0070_(Attachment_01_SOW).pdf

Scope of Work

Lewis and Clark National Historic Trail Georeferenced Recreation Content

Article I – Definitions and Background

The Lewis and Clark National Historic Trail In 1978 Congress established the trail as part of the national trail system (NTS) as one of four original national historic trails. Today, the trail is approximately 4,900 miles in length connecting Pittsburgh, Pennsylvania to near present-day Astoria, Oregon. Following the historic outbound and inbound routes of the Lewis and Clark Expedition, including the preparatory section from Pittsburgh, the trail connections 16 states:

Pennsylvania, Ohio, West Virginia, Kentucky, Indiana, Illinois, Missouri, Kansas, Nebraska, Iowa, South Dakota, North Dakota, Montana, Idaho, Washington, and Oregon.

The Trail is headquartered in Omaha, Nebraska and administered by the National Park Service.

One of the ways the National Park Service commemorates and protects the Trail is through interpretation. “Interpretation is a catalyst in creating opportunities for audience members to make their own intellectual and emotional connections to the meanings of park resources. Our goal is to help visitors using our digital media to make those connections via this new interpretive content.” (NPS Essentials)

“Interpretation and Education provide dynamic, vibrant, and essential support in fulfilling the NPS mission. The stewardship of park resources is highly dependent upon an engaged and supportive public.’ (NPS Essentials)

By facilitating meaningful and enriching park experiences, Interpretation and Education services provide a mission-critical role — helping visitors discover why they care about park resources so that they will want to help care for those resources.” (NPS Essentials)

Article II – Project Description

The purpose of this contract is to conduct research and provide interpretively written content on recreation sites that will be used for our NPS website, mobile app and other interpretive products.

This contract, and the content produced from it, will serve several purposes:

• Be written interpretively- in order to help give digital visitors an opportunity to discover why they care about Trail resources.

• Be engaging- the content will be a catalyst in creating opportunities for the audience to make their own intellectual and emotional connections with the meanings of Trail resources. It will help inspire future travels on the trail.

• Follow the format laid out in the SOW (and discussed in the initial meeting) to be used on the NPS systems and for public use. This includes writing formatted as place assets or as articles.

• Have quality, vetted content that is available to third party app and website developers.

https://mylearning.nps.gov/library-resources/nps-essentials-interpretation-education/ https://mylearning.nps.gov/library-resources/nps-essentials-interpretation-education/ https://mylearning.nps.gov/library-resources/nps-essentials-interpretation-education/

Next is some background information taken from the NPS Digital Community Site on Place Assets. The content management system and Place Assets described below are the system used by National Park Service employees to creative webpages and content for nps.gov. For some examples of existing webpages from the Lewis and Clark NHT, go to https://www.nps.gov/lecl/planyourvisit/places-to-visit-montana.htm

What Are "Places"?

Throughout this guide, the capitalized word Place asset? refers to a specific type of web-page in the NPS.gov content management system (CMS) to describe a location. The lowercase word "place" is used in the more general sense of a physical location.

A Place is a specific physical location (e.g., a notable farm, a particular bridge, a specific wayside next to a visitor center, etc). Ideally, these areas do not change quickly and require visual orientation to and on the landscape.

Why Create a Place?

Like other types of shared content, a Place asset embodies the Create Once, Publish Everywhere model. Various sites within the NPS.gov umbrella can then reuse Place assets without having to recreate or duplicate content that another park or program already published.

For example, Burnside Bridge is a notable location in Antietam, but the stories related to Burnside Bridge, and the ramifications of the battle there, extend beyond Antietam's physical borders. A single Place with details of Burnside Bridge would certainly be useful on ANTI's site, as well as the Civil War subject site and other sites that currently exist or that might exist in the future (e.g., military history, historic preservation, etc.).

Places can also be reused by third-parties via the NPS Application Programming Interface (API) and will be used in the NPS servicewide mobile app.

• {LECL note- having the Places for the NPS app and available for third-parties are goals of this project}

Places and the NPS Mobile App As mentioned above, Places aren't just published on NPS.gov. They will be used in the NPS servicewide mobile app in a couple of different ways.

• Categories The app will allow a park to group any number of Places by a variety of categories.

For example, Yellowstone might make an individual Place for each mud pot in the park, and then group them up into a category called "Mud Pots in Yellowstone." Then, a mud pot enthusiast who is traveling to Yellowstone can read about each of them in the app.

There isn't necessarily a set order or any directions connecting Places within a category;

it's just a list of locations that share a common theme / geology / etc.

{ LECL examples- Partner Visitor Centers, Historical Sites, Recreation} https://www.nps.gov/lecl/planyourvisit/places-to-visit-montana.htm https://www.annertech.com/blog/cope-create-once-publish-everywhere-introduction https://www.annertech.com/blog/cope-create-once-publish-everywhere-introduction https://www.nps.gov/subjects/civilwar https://www.nps.gov/subjects/historicpreservation/index.htm https://www.nps.gov/subjects/developer/guides.htm https://doimspp.sharepoint.com/sites/nps-web-community/SitePages/Apps.aspx https://doimspp.sharepoint.com/sites/nps-web-community/SitePages/Apps.aspx https://doimspp.sharepoint.com/sites/nps-web-community/SitePages/Apps.aspx https://doimspp.sharepoint.com/sites/nps-web-community/SitePages/app-categories.aspx

• Self-Guided Tours The app will let a park string together a sequence of Places (and other types of content, like campgrounds and visitor centers) into a self-guided tour. When thinking about what stops would work well on a self-guided tour, keep your thinking flexible on what constitutes a Place. Any location that you wish to direct people to visit would work well, no matter how large or small.

For example, any of the following might make a good Place to create and include in a self-guided tour:

• Historic structures

• Water trail

• Grave sites

• Historical markers

• Lewis and Clark Trail sites

For this project, LECL is asking the contractor to develop interpretive content on recreation for 80-100 sites along the Trail. All of these write up will be place assets (see above for explanation)

Article III- Scope of Work

This contract will provide a set of content that provides visitors a set of places they can visit along the trail to experience various recreation activities.

Lewis and Clark National Historic Trail will provide:

• Specific format of how the final content should be prepared for us to review and the final version.

• Links to our current website and shared content for reference.

Final project will include:

• Research recreation sites along the trail. Develop a criteria for selecting sites for content development.

• Contractor will devise strategy for researching, organizing, and writing recreation content for each site selected.

• Each place will be written up using a specific format provided by LECL. The contractor will also find and provide graphics in the public domain to be used with each place researched. GIS coordinates will be provided for each place.

• Citations for all information gathered will be provided with each entry.

Deliverables:

Research and develop place asset for recreation sites that come up during research.

https://doimspp.sharepoint.com/sites/nps-web-community/SitePages/Tours.aspx

Site selection should include sites in each of the 16 states of the trail with at least three sites per state. Site selection should break down approximately as 20% hiking trails, 20% biking opportunities, 20% water sports and water trails, 20% fishing, 20% wildlife observation and photography opportunities. Sites selected must be open to the public. A minimum of 80 pieces of content will be developed.

Deliverables should be provided in Word document as well as a PDF format.

• Place assets will o Minimum 100 words in length o Include a photo, public domain with citation o Follow an interpretive writing style o Include list of amenities o Geolocation data o List of all sources and citations used to write the text o With each Place, provide a short, 1-2 sentence teaser for use in social media posts

Deliverables-

A. Attend post-award conference call.

B. Submit electronic notes from post award conference call.

C. Submit preliminary research and update on site selection.

D. Submit draft report with citations, graphics, geolocation data as word document.

E. Submit second draft with citations, graphics, geolocation data as word document.

F. Final report—submit the original files in word and a pdf file on removable media.

Schedule:

Deliverable Description Completion Time Review Time A Attend a post award conference call.

Within 30 days from award

B Submit electronic notes from post award conference call.

10 Days from call 10 days

C Submit preliminary bibliography, research, and update site research.

60 Days from acceptance of previous deliverable

10 days

D Submit draft with citations, graphics, geolocation data as word document.

Within 120 days of acceptance of previous deliverable.

30 days

E Submit second draft with citations, graphics, geolocation data as word document.

Within 90 days of acceptance of previous deliverable.

20 days

F Submit final report within 60 days of acceptance of previous deliverable

20 days