N6426726Q5034 Draft PD.pdf

1 | 4

PURCHASE DESCRIPTION

1. INTRODUCTION

NAVSEA HQ (SEA10D2) requires YELLO software licenses for their Enterprise Recruiting Program

2. BACKGROUND

NAVSEA YELLO software licenses for their Enterprise Recruiting Program

3. REQUIREMENTS

To support NAVSEA recruiting efforts to include:

Yello Application Management Solution for up to 2000 Hires.

Solution Includes the following:

• 5 Admin Seats

• 1 Application Workflows with up to 32 customer defined statuses

• Up to 5 Workflow Communications

• 1 Application Form with up to 25 Application Fields

• 1 NEXT Job Board

• Up to 30 custom Requisition fields

• Up to 15 custom Candidate Profile fields

• Up to 5 Custom Staff/User Fields

• Up to 15 Candidate Tags and/or Candidate Folders

• USAjobs Integration

Yello Event Recruiting Solution for up to 600 Events (Virtual and In Person). Solution Includes the following:

• 5 Admin Seats

• Mobile Recruiting Application

• Event Management

• Pre Event Registration

• Evaluation Forms

• Candidate Administration (Searching/Filtering)

• Custom Branding

• Single Sign On

• Campus Profiles

• Virtual Event Video Conferencing

• Event Scheduling

2 | 4

• Event Expenses

• Event Performance Reporting

• Event Central

• CRM (Campaigns, Talent Community (1))

Additional Feature to include but not be limited to the following:

• Event Add Ons

• Tiny URLs

• Site Add Ons

• Enable Chat In Video Sessions

• Walk Me Tool

• Staff Calendar/1 on 1 Scheduling

• Send Campaigns Emails from Separate IP Address

• NCC Integration and Instance

ADDITIONAL INFORMATION

A. PERIOD OF PERFORMANCE / REQUIRED DELIVERY DATES

B. PLACE OF PERFORMANCE

C. SHIPPING ADDRESS

D. INSPECTION AND ACCEPTANCE

E. TECHNICAL POINT OF CONTACT

The period of performance for this order is 26 September 2026 – 25 September 2027

1333 Isaac Hull Ave Washington, DC 20376

1333 Isaac Hull Ave Washington, DC 20376 DoDAAC N00024

TBD

TBD

3 | 4

PURCHASE DESCRIPTION

INSTRUCTIONS

HEADER

Replace “HEADER” and provide a short title that best identifies the task requirements to be performed. Keep it simple – a one-liner is adequate. Make this a short phrase by which the job is generally known. Procurement actions are generally referenced by this title until a contract number is assigned by the Contracts Department; therefore ensure the title is representative of the requirements.

1. INTRODUCTION

Provide just enough information for the reader to understand what is being procured and by whom (i.e. department name and code). This section should not be lengthy or include any information that is contained in other sections of the description.

2. BACKGROUND

This section shall help the reader get a good understanding of what is being procured and why.

When writing this section, assume that the reader does not have any knowledge or experience with the requirements of the procurement. Therefore provide historical information necessary to understand how the requirements were derived and why the requirements are needed. In addition, identify the current state of the requirements. If the requirement is part of a larger program, identify the program and the relationship of the requirement to the overall program.

Also, identify research, studies, or other efforts that contribute to the reader’s understanding of the requirement. Make sure only facts and relevant information is included. The length of this section should not exceed four paragraphs; however, it is more important to fully discuss the background than it is to try to stay within length constraints. Do not include any information that is contained in other sections of the description.

3. REQUIREMENTS

This section should include the following characteristic to adequately describe the Government’s minimum need:

Common nomenclature (commercial description);

Kind of material (i.e., type, grade, alternatives, etc.);

Electrical data, if any;

Dimensions, size, capacity;

Principles of operation;

4 | 4

Restrictive environmental conditions;

Intended use (i.e., location within assembly, essential operating conditions, etc.);

Equipment with which the item is to be used;

End item application;

Original Equipment Manufacturers (OEM) part number, if applicable; and

Other pertinent information that further describes the item, material or service required (including salient characteristics and other products that are equal in form, fit and function to the product/model number identified for Brand Name or Equal descriptions.

5 | 4

THIS PAGE CONTAINS NECESSARY INFORMATION FOR THE PROCUREMENT

ACTION THAT IS PLACED IN OTHER SECTIONS OF THE CONTRACT

PERIOD OF PERFORMANCE / REQUIRED DELIVERY DATES

For a Service Procurement: Provide the desired POP. For a Supply Procurement: Provide a RDD for each item in the form of number of days, months, etc. (e.g. 30 days after award). If not applicable, enter “N/A”.

PLACE OF PERFORMANCE

Required for a Service Procurement – State the location(s) of where the work will be performed.

If not applicable, enter “N/A”.

SHIPPING ADDRESS

Required for a Supply Procurement - State the activity name, DODAAC, address, city and state of the location where the material/equipment is to be delivered. If not applicable, enter “N/A”.

INSPECTION AND ACCEPTANCE

Required for both Supply and Service Procurements – State who will be conducting the inspection and acceptance and when and where the inspection and acceptance will be conducted.

TECHNICAL POINT OF CONTACT

Required for contracts that do not require a COR appointment. Provide the contact information (name, code, phone number, email address) of the requestor(s) that have cognizance over the procurement. If not applicable, enter “N/A”.