PWS_Taxonomy_Tool_.pdf

Attachment 1 (PWS) Performance Work Statement (PWS)

For Defense Acquisition University (DAU)

Acquisition Technology & Logistics (AT&L) Taxonomy Management Auto Classification Tool

1. PURPOSE

The Defense Acquisition University (DAU) requires a taxonomy management system for better coordination of terminology and meaning across the enterprise; add-ons can help to classify content so that it can be retrieved more quickly. A thesaurus provides term definition, history, provenance, and relationships to other terms. All of this can enhance operations at DAU when used to tag content in SharePoint.

2. BACKGROUND

The Defense Acquisition University (DAU), located at Fort Belvoir (Virginia) and at regional campuses around the country, coordinates the Department of Defense (DoD) acquisition education and training program to meet the training and performance support requirements of more than 140,000 military and civilian personnel serving in acquisition positions worldwide, as required by the Defense Acquisition Workforce Improvement Act of 1991 and Public Law PL 1009-163 sec 1056.c.3. Through its dispersed campus and Acquisition Learning Model (ALM), DAU sponsors acquisition curriculum, instructor training, and knowledge sharing systems to provide a full range of basic, intermediate, and advanced learning assets to support the career goals, professional development, and job support needs of the acquisition workforce around the world. Further, its learning assets are used by the entire federal Government's workforce, defense industry partners, and foreign acquisition professionals.

3. GENERAL RQUIREMENTS

A taxonomy management system provides better coordination of terminology and meaning across the enterprise; add-ons can help to classify content so that it can be retrieved more quickly. A thesaurus provides term definition, history, provenance, and relationships to other terms. All of this can enhance operations at DAU when used to tag content in SharePoint, or elsewhere.

The Term Store in SharePoint 2013 is a vast improvement over previous versions of the software and DAU requires some enhanced capabilities.

1. Hierarchical relationships (i.e., broader and narrower terms), need to be specifically visible as BT or NT to content producers tagging material as content is created and/or uploaded.

2. The Ability to indicating other types of relationships (i.e., RT or “cousins”).

3. Robust “Scope Notes.”

4. Audit trail to track changes in language over time. If DAU intends to use this taxonomy for historical documents as well as current, it’s vital that changes in what we call/name things are noted as they evolve (History Notes).

5. Reporting capability for analysis of term usage (e.g., number of information objects using tag).

Analyzing term usage is important in determining the need to surface a term (and material associated with it), i.e., moving it from Level 4 or 5 to Level 1 or 2.

The contractor will be required to interface and work cooperatively with DAU personnel, Office of the Secretary of Defense (OSD), Service, Agency, Industry (including other contractors supporting DAU directly or indirectly), and Academic personnel in order to provide a variety of consulting, training, as well as technical and administrative support for operating, maintaining, and improving term store through automation.

4. PERFORMANCE REQUIREMENTS

This performance-based work statement defines the requirements and acceptable performance levels necessary to support the Government. The contractor shall provide support services to DAU in the following task areas.

DAU is looking for a tool that can be deployed rapidly and is easy-to-manage. Beyond taxonomy editing, DAU would benefit metadata tagging tools that assist with auto-classification and/or machine-aided indexing. This is particularly important as content producers (authors) will be tagging and uploading material to sites. Workflow can make a difference in terms of taxonomy editor functionality requirements (basic, midrange, or advanced). Any tool considered by DAU must:

• Maintain terms and relationships (equivalencies, hierarchical, and associative) as reciprocals and when renaming, merging, subsuming, or deleting terms o Customizable semantic relationships between terms, dependent on class o Disallow invalid relationships (according to standards) o Support candidate/approved terms, indicating term creation and update data

• Support multiple types of inter-category term relationships

• Support ease of use characteristics and drag-and-drop for relationship management

• Support simple and filtered results term searching (with spell-check capabilities turned on/off) o Supports the use of Term categories for advanced filtering

• Have multiple taxonomy display options, importing and exporting formats

• Customizable (user-defined) relationships, term notes, and attributes

• Manages the creation of terms to prevent the creation of duplicate terms through the use of relationship rules

• Support two levels of term Removal; deactivation and deletion o Provides warnings for term deletion

• Support the tracking and viewing of historical information on terms, preferred terms, and term relationships

• Generate reports in various display formats (hierarchical, alphabetical, rotating index, visualizations)

• Permit importing and exporting of taxonomies o Export data in interoperable formats for import to SharePoint 2013

• Support ANSI/NISO Z39.19-2005, ISO, OWL, RDF standards

• Provide REST Web Services APIs using strongly typed web methods and Extensible Markup

Language (XML)

• Provide a SharePoint Integration that supports the following functionality o Provide an out of the box connector that manages the updating of the SharePoint Term

Store with Terms and relationship information that is being maintained in the Taxonomy solution o Provide a REST Web Services API that allows the automated creation of Terms identified through a SharePoint form o Does not use the SharePoint Term Store as the core repository for the storage of Taxonomy Terms and their hierarchical or non-hierarchical relationships o Support a loosely coupled integration with SharePoint that is not be tied to the hierarchical relationship limitations of SharePoint

• Support deploying the solution on Windows Server 2008 R2 or newer using IIS, ASP, and .Net Framework

• Support the storage of Taxonomy managed data on Microsoft SQL 2008 or newer

5. DELIVERABLES

The vendor must provide support for the Installation and configuration of the product. They must guide DAU through the process of configuring the out of the box connectors and connections to support the configuration needed to meet performance requirements.

The vendor must assist with performance tuning and user acceptance testing to ensure the full interoperability between the Taxonomy Solution and SharePoint.

Vendor must provide usage and application configuration and management training applicable to the implementation scenario at the DAU campus.

Vendor must provide 5x8 product support for technical issues with direct support phone numbers and tracking of open issues.

6. SPECIAL REQUIREMENTS

None

7. PLACE OF PERFOMRANCE

Work will be performed at DAU’s Headquarters Fort Belvoir, Virginia.

8. PERIOD OF PERFORMANCE

The base period of performance for this order shall be 1 year from the date of award with 2 option years for annual maintenance.

9. DELIVERY INSTRUCTIONS

Ship to: Defense Acquisition University, 9820 Belvoir Road, Building 231, Fort Belvoir VA, 22060 ATTN: Bruce Wilcox

10. SECTION 508 COMPLIANCE

Section 508 Rehabilitation Act: Regarding DAU Purchasing of Accessible Electronic and Information Technology (EIT)

Background: Far 39.2 Code of Federal Regulations, Title 36: 36 CFR Ch. XI (7–1–11 Edition) (PART 1194— ELECTRONIC AND INFORMATION TECHNOLOGY ACCESSIBILITY STANDARDS); Subpart B—Technical Standards (1194-21 through1194-26)

The software tool deliverables to be acquired in this solicitation are primarily EIT, and, therefore subject to Section 508. Section 508 of the Rehabilitation Act, as amended in 1998 (PL 105-220), was signed into law on August 7, 1998, by President William J. Clinton as part of the Workforce Investment Act of 1998.

Section 508 of the Rehabilitation Act requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, they shall ensure that this technology allows:

• Federal employees with disabilities to have access to and use of information and data that is comparable to that by Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency, and

• Individuals with disabilities, who are members of the public seeking information or services from a Federal agency, to have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities.

36 CFR Ch. XI (7–1–11 Edition) PART 1194

Technical Standards:

1194.21 Software applications and operating systems.

(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.

(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.

(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes.

(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text.

(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance.

(f) Textual information shall be provided through operating system functions for displaying text.

The minimum information that shall be made available is text content, text input caret location, and text attributes.

(g) Applications shall not override user selected contrast and color selections and other individual display attributes.

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.

(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.

(l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

1194.22 Web-based intranet and internet information and applications.

(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

(e) Redundant text links shall be provided for each active region of a server-side image map.

(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

(g) Row and column headers shall be identified for data tables.

(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

(i) Frames shall be titled with text that facilitates frame identification and navigation.

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.

(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.

(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).

(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

(o) A method shall be provided that permits users to skip repetitive navigation links.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

1194.24 Video and multimedia products.

(a) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned.

Attachment 1 (PWS)

The Defense Acquisition University (DAU), located at Fort Belvoir (Virginia) and at regional campuses around the country, coordinates the Department of Defense (DoD) acquisition education and training program to meet the training and performance suppo...