DRAFT_GeoMapping_PWS__20170711.pdf

PDF 98 KB Posted

Attached to
AFICA - AFRS Geo-Mapping Application
Solicitation number
Not on record
Issued by

About this file

DRAFT PWS for the Air Force Recruiting Service (AFRS) Geo-Mapping Application and maintenance services.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

AIR FORCE RECRUITING SERVICE (AFRS)

[DRAFT] PERFORMANCE WORK STATEMENT (PWS)

FOR

GEO-MAPPING APPLICATION & MAINTENANCE

11 Jul 17

1. DESCRIPTION OF SERVICES.

AFRS has a requirement for continued access to and support of the AFRS Geo-Mapping Application. The web-based mapping application identifies and delineates the four (4) major AFRS recruiting programs: Enlisted Accessions (EA), Health Professions (HP), Line Officers (LO), and Chaplain recruiting programs.

The maps intuitive and interactive graphic user interface will allow users to browse through geographic layers such as states, counties, cities, groups, squadrons, and zip codes. The map will expand current capabilities by allowing recruiters to effectively manage newly assigned areas of responsibility, and view pertinent demographic information such as youth population, household income, and school and college locations in each of the assigned recruiting zones.

2. SCOPE.

The contractor shall provide all equipment and labor to include the AFRS Geo-Mapping Application, program updates, system sustainment, data integration, hosting facilities, web maintenance, and helpdesk support. The application shall display recruiting zones (using five-digit U.S. Postal Zip Codes as a baseline) for 3 groups, 27-30 squadrons, 180-250 flights, and approximately 900 offices manned with 2000+ EAs, HPs, LOs, and Chaplain recruiters and staff.

The webserver(s) must be fast, secure, and capable of supporting multiple AFRS users at one time. The application should be accessible to users on a 24/7 basis, with the exception of notified downtime for scheduled maintenance.

3. SYSTEM REQUIREMENTS.

3.1. Required Functional Capabilities.

• The mapping application should not require the need for any proprietary hardware or software.

• The mapping application shall be hosted on the contractor’s web server and should be accessible on both desktop and mobile platforms.

• The mapping application shall include, or be able to perform, the following:

a. The application shall allow users to display and navigate AFRS-identified recruiting zones defined by boundaries based on States, Counties, Zip Codes, Groups, Squadrons, Flights, and Recruiter Offices. Boundary-defined zones shall be selectable, allowing the user to highlight and fill zones using various color, pattern, and transparency tools. Pertinent information regarding the zone (including hyperlinks to additional data) shall be displayed when the user selects or rolls over the zone with their mouse pointer. Zones shall be capable of displaying layered information to the user and allow the user to turn on/off layers through a menu - or table of content - type selection capability.

b. The application shall allow the user to search and display information available in the database of information relating to zones through a free text function with auto complete or a series of drop-down menus. The application shall allow the user to perform advanced ad-hoc queries based on available recruiting information (e.g., production and demographic data). The results of the query shall be made available to the user immediately on their monitor and have the capability to export the results into an Excel spreadsheet or PDF file.

c. The application shall allow the user to bookmark various locations (and other identifiable entities within zones), and display pertinent information with respect to the bookmark.

d. The application shall allow the user to display background “themes” of their choosing through a menu or swiping function. At a minimum, the application shall be able to display background “themes” using a satellite view, road map view, or a plainly colored background view.

e. The application shall provide the user with capabilities to measure distances between points, zoom in/out, identify various identities within a specified distance from a point, and dynamically display location coordinates using latitude and longitude.

f. The application shall allow the user to select and mark-up an area of the map using various drawing objects and export the area as an image file.

g. The application shall allow the inclusion of no-cost commercial or government sourced mapping service links (e.g., Dept. of Education, Dept. of Defense, Census Bureau, etc.) to select and display pertinent mapping and demographic information.

h. The application shall provide prospective users the ability to request a secure account through the creation of a UserID and password interface. The application shall notify the user when their account has been created. The application shall provide a mechanism to reset a user’s password should they forget their account information.

i. The application shall give the AFRS application administrators the ability to approve/disapprove new account requests and review or amend existing account information through an administrator user interface. The application shall provide administrators the ability to delete and reset existing accounts.

j. The contractor shall integrate a variety of AFRS-provided recruiting data (e.g., office locations, DoD facilities, production data, recruiting statistics, educational institutions, etc.) and display the information in a logical, human-factored design (e.g., point locations, heat maps, zones, icons, spreadsheets, etc.). AFRS data updates will be provided to the contractor every month at a minimum.

k. The contractor shall integrate and update on an annual basis non-AFRS supplied demographic and location data to include at a minimum the following:

• High school and college locations with hyperlinks to their respective Dept. of Education data sources

• Military facilities for the US Air Force, Navy, Army, Marines, and Coast Guard

3.2. Systems Evolution.

The contractor shall conduct lifecycle management software enhancements.

4. CONTRACTUAL REQUIREMENTS.

4.1. Customer Support.

The contractor shall provide Level 1 and Level 2 technical support via internet, telephone, and email seven (7) days a week, twenty-four (24) hours a day.

Level 1 – The system is down or a problem exists that prevents access to the application. The contractor shall respond within one (1) hour of notification during normal work hours, and three

(3) hours outside normal hours. A fix shall be implemented within 3 calendar days.

Level 2 – A problem exists that impacts application accessibility, data recovery, or data content.

The contractor shall respond within one (1) hour of notification during normal work hours, and three (3) hours outside normal hours. A fix shall be implemented within 5 business days.

4.2. Security Requirements.

The contractor’s hosting facilities must be secure at all times. Primary server hardware must have limited access and should be placed in a physical and virtually secure environment. A secondary or backup server must also be maintained and secured.

4.3. Records Management.

The Contractor shall manage all data created for Government use or legally controlled by the Government, in support of the functional activity or required by AF publication, IAW with the AF records management procedures in Air Force Instruction (AFI) 33 - 322, Records Management Program, paragraph 10, Air Force Manual (AFMAN) 37-123, paragraph 7.4, Air Force Manual (AFMAN) 37-138, paragraph 2.13, and the Air Force Records Disposition Schedule (AF RDS) located at https://afrims.amc.af.mil/rds_series.cfm or http://www.amc.af.mil/shared/media/document/AFD-060803-003.pdf

5. QUALITY ASSURANCE.

The contractor shall be responsible for quality control for all work accomplished during the performance of the task. The contractor shall provide and maintain a Quality Control Plan (QCP) which ensures the requirements in this PWS are met. The QCP shall be included in the technical proposal for evaluation and acceptance, and shall be considered acceptable and approved unless the contractor is notified by the Contracting Officer (CO) prior to award. As a minimum, the contractor shall develop quality control procedures that address the areas identified in Section 6 Service Delivery Summary.

The government will periodically evaluate the contractor’s performance by appointing a Contracting Officer Representative (COR) to monitor performance to ensure services are received. The COR will evaluate the contractor’s performance in accordance with the Quality Assurance Surveillance Plan (QASP) for this requirement.

6. SERVICE DELIVERY SUMMARY.

Performance Objective

PWS

Paragraph

Performance Threshold

1. Level 1 technical support 3.4 The contractor shall respond within one (1) hour of notification M-F 7:30 AM-4:30 PM CST, and three (3) hours outside those hours. A fix shall be implemented within 3 calendar days.

2. Level 2 technical support 3.4 The contractor shall respond within one (1) hour of notification M-F 7:30 AM-4:30 PM CST, and three (3) hours outside those hours. A fix shall be implemented within 5 business days.

https://afrims.amc.af.mil/rds_series.cfm http://www.amc.af.mil/shared/media/document/AFD-060803-003.pdf

Performance Objective

PWS

Paragraph

Performance Threshold

3. Provide uninterrupted application availability to users

3.4 The contractor shall maintain

application availability at a 99% rate based on a 24/7 period with the exception of notified downtime for scheduled maintenance.

4. Update monthly AFRS provided zip code-to-recruiter billet ID data

The contractor shall update the data within five (5) business days of receipt from AFRS.

5. Integrate a variety of AFRS-provided recruiting data

3.1(j) The contractor shall update the data within five (5) business days of receipt from AFRS.

6. Integrate and update on an annual basis non-AFRS supplied demographics

3.1(k) The contractor shall update the data within five (5) business days of receipt from AFRS.

File details come from the government source that posted it. Updated .