Attachment_3_PWS_-_DLA_Troop_Support.pdf

Attachment 3 – Page 1

Attachment 3

PERFORMANCE WORK STATEMENT – DLA TROOP SUPPORT

DLA Enterprise Online Databases Subscription Service

INFORMATION SERVICES

INTRODUCTION

The following information and document retrieval services are to be provided to the Medical Directorate; the Hardware Directorate; and the Construction & Equipment (C&E) Supply Chain at the DLA Philadelphia Troop Support. The Commodities at DLA Philadelphia Troop Support is responsible for providing logistics support to the Military Services for a wide range of components and spare parts used for weapon systems, aircraft and naval ships. To carry out this mission, the Commodities need various research tools including an on-line information retrieval system that provides instantaneous access to specifications, standards, parts catalogs, various Government databases and regulations.

The system must contain expeditious and sophisticated research capabilities as well as a Comprehensive index that allows various types of searching and management reports, with the ability to identify specific documents then view the actual document pages. The documents must be viewable online in electronic- based PDF or HTML format, must be fully printable, and must be provided in a licensing arrangement which will permit authorized downloading to hard or floppy disc. The specific requirements for this on- line system are detailed below. Product must be commercially available "off the shelf ' and immediately deployable according to the start date of the period of performance. This COTS application shall be immediately deployable, operational, in conformance with and compatible with existing SOR requirements.

ACCESS THROUGH THE WWW TO GOVERNMENT AND COMMERCIAL

DOCUMENTS

The system shall provide as a minimum access to the following documents along with access to an index for these documents and complete and unlimited access to full-text images in PDF and/or ASCII Text:

Core Service (includes index and actual document images):

• Military Specs and Standards

• Military Performance and Detail Specifications

• Navy Technical Publications

• Federal Specs and Standards

• Commercial Item Descriptions (CIDs)

• Joint/Army-Navy Specs and Standards

• Military/Federal Qualified Products Lists (QPLs)

• Qualified Manufacturers Lists (QMLs)

• Military Handbook/

• Military Bulletins

• MS Drawings, AND, ANA, AN Drawings

Attachment 3 – Page 2

• DESC/SMD Drawings

• Data Item Descriptions (DIDs)

• Federal Information Processing Standards (FIPS)

• DoD Adopted Industry Standards

• Historical (cancelled and superseded) documents

• Army Documents

The system must also provide direct on-line access to the DoD Adopted documents from the following Standards- Developing Organizations:

AA

AASHTO

AATCC

ABMA

ACI AGA

AGMA

AMT

AIAA

AIA/NAS

3D AIA/NAS

ANSI API

ARI

ASA

ASCE

ASHRAE

ASME

ASSE-Safety ASSE-Sanit

ASQ

ASTM

AWS

AWWA

BHMA

BMI

BOCA

CEA

CGSB

CSA

CTI

ECA

EIA

GEIA

ICC

Attachment 3 – Page 3

ICEA I

EC

IEEE

IPC

ISA

ISO

ITU J

EDEC

MSS

NACE

NEMA

NFPA-Fire

NISO

NSF PFI

PIA

RWMA

SAE

SMACNA

SSPC

TIA

UL

In addition, the system must provide direct on-line access to the Commercial Standards (not just DoD Adopted) from the following Societies:

AIA/NAS

3D AIA/NAS

ANSI

ASME

ASTM

BSI

DIN SAE SBAC

ORGANIZATION # OF USERS

CORE SERVICES 10

LOGISTICS DATABASE 10

ANSI 5

(See Note below)

AIA/NAS 10

(See Note below)

ASTM 12

(See Note below) ASME Standards 7

Attachment 3 – Page 4

(See Note below)

SAE 10

(See Note below) DIN English 1

(See Note below)

BSI 1

(See Note below) Vendor Catalog Service 3 SBAC Standards 1 Catalog/Express Basic 2 ASQ Standards 2 ISO Standards 2

Medical/Consumer Goods Section Historical Mil Specs 2 Mil Specs and Standards Essential 2 UL Standards 2

*Note: The total number of users for the marked items listed above must encompass both direct on-line access to the DoD Adopted as well as Commercial Standards as specified in the Statement of Requirements.

Index and Reports:

The System must provide a single index to the documents listed above with access to full text images in PDF Format. The Index must be able to provide the following reports:

1. Summary that provides Scope and Intended use information.

2. Keywords assigned by the preparing activity.

3. Additional management information such as applicable QPLs, DIDs, etc.

4. An applicable Documents report that lists all documents referenced within the document.

5. Links to applicable documents including links to referenced standards, slash sheets, QPL and FLIS data when applicable for DODISS documents.

6. Responsible Activities report that includes addresses, phone/fax numbers, and email addresses for the Preparing Activity, Custodians, Reviewers and the Society/Organization.

7. A history of the document to include the date of the base document as well as any revisions or amendments, with links to those documents.

8. A complete document outline that allows the user to go from the index directly to the paragraph, sub-paragraph or section level rather than simply the first page of the document.

9. The Report information must be printable.

Product Functionality:

The system must provide the following research capabilities or methods.

Attachment 3 – Page 5

1. All Military/DoD, Government, and Non-Government (Commercial) documents listed above must be included in the same product using the same search engine. The index must include the Military/Government documents and the DoD adopted industry standards.

2. Searching by document number or portion of a document number, including alpha prefixes and decimal points.

3. Keywords must be searchable from the index in the title of the document, scope, intended use, keyword paragraphs or summaries, and from the document outline for all documents that include this information.

4. The system must be capable of performing characteristic searches

5. Searching by Federal Supply Classification (FSC).

6. Searching by Preparing Organization.

7. The system must have the capability to conduct a search by specific document type. For example, search by Mil Specs, Fed Specs, etc.

8. The system must be capable of limiting a search to active or historical

(canceled/superseded) document references.

9. Combination or Boolean searching must be possible.

10. Each search query should provide the user with a Results List. The Results List must identify the document number, active or historical status, publication date, if it is newly revised, and the document title. Each document in the Results List should be directly linkable to value-added Summary/Detail Report information.

11. Additional Document Management Features

Favorites List:

1. Ability to place documents on a "Favorites" List with a single keystroke.

1. Users automatically receive email notification when a document on their "Favorites" List is revised, cancelled, withdrawn or superseded.

2. Includes ability to add personal notes to a document on the Favorites Lists, i.e., specific pages you use in the standard, project/product the standard was used on, etc.

3. Document Watch Lists

4. Ability to create "named" Watch List(s) to easily track documents associated with a particular project or compliance program.

5. Includes ability to add documents to a Watch List with a single click.

6. Includes ability to "freeze" documents on a Watch List at a specific revision level, or specify "current version" to ensure documents on Watch List are always kept up-to-date.

7. Include ability to specify other uses that can view/modify a "named" Watch List.

8. Includes ability for specified users to receive email Alerts when all (or selected) documents on a Watch List are revised, cancelled, withdrawn or superseded.

9. Alerts for Favorites and Watch Lists should be displayed online in one centralized place for easy viewing and management.

10. User must be able to define the time period they want Alerts to cover, i.e. 1 week, 30

Attachment 3 – Page 6 days, 60 days, etc.

11. Save Search

12. Ability to save a search for future re-creation.

Document Images/Text:

1. All non-government commercial standards must be licensed by the issuing .standards developing organization to allow image viewing and printing of the desired actual standard in hardcopy format.

2. Document images must include full English translation.

3. Documents must be updated a minimum of every 7 days.

4. System must identify recently updated documents.

5. Documents must be provided via electronic media. Hardcopy delivery of documents will not be considered.

6. When a contract with the Standards Developing Organization (SDO) requires DRM

(Digital Rights Management) restrictions, the File Open Plug-In will be made available at no charge to allow viewing of the PDF documents. DRM is currently required for AWS and IPC.

Attachment 3 – Page 7

LOGISTICS DATABASE APPLICATION REQUIREMENTS

This is a Product Description of Required Information Service Regulations for logistics data services to be provided via Vendor's on-line server or internet technology format. These services will be accessed through the DLA Troop Support local area network (LAN); compatibility with the DLA Troop Support LAN is essential. The logistics data service product shall allow for advanced and flexible querying capabilities and the ability to identify and provide detailed data elements for specific National Stock Numbers (NSN)/National Item Identification Numbers (NIIN) and manufacturers' part numbers.

Product must be capable of being distributed to multiple users through the DLA Troop Support

LAN.

°The product must be commercially available "off the shelf ' at the time of award. The system must provide on-line WWW access to the following databases:

1. FLIS

• Historical NATO NSN records

• Product Item Description (PID)

2. PID Specification

• Standards Drawing references

• The complete Military specification and standards index

• D043/D043 X-File

• D049

• SNUD

• Complete historical Procurement History (including Army, Navy, Air Force, and

Marine Corp, Coast

• Guard, DLA Inventory Control Points

3. Subscription Service Support

• GSA and local government agencies)

• LIRSH

• DODAAF

• QPL Parts Index

• Navy CRF

• MRIL

• AMDF

• SB700-20

• P2300/P23 l O/P2330, P2002

• CHAIN

• MIAPL

• NICN/NIIN

Attachment 3 – Page 8

• APL/AEL

• Work Unit Code (WUC)

• FAA Parts Manufacturing Authority (PMA)

• United Kingdom NSN

• Canadian MCRL and Procurement History databases

• Visibility to spare parts and forged parts tooling data

Product Functionality Features & Requirements:

The system must have the following features and research capabilities:

1. The FLIS database must be searched by any combination of the following fields:

Manufacturer's part number (which must be found by specifying ANY portion of the part number), FSC, NIIN, NSN, Item Name (both approved and unapproved item names), CAGE Code, Company Name, Source of Supply, Acquisition Advice Code, Item Name Code, End Item Codes from the Army, Navy and Air Force, Navy COG code, PID Keyword, PID Spec, and technical characteristics.

2. The FLIS database must reference PID information for any NIINs that report such information. This is a mandatory requirement since PID data often has technical data, which is not referenced in the V-segment (technical characteristics) and references specification, standards and drawing number data.

3. The FLIS database must search obsolete NIINs found in the Section K or E of the FLIS database and instantly reference the correct replacing NIIN.

4. Company Name searches must allow the user to select multiple CAGE's that represent the company name searched (since the user may not know which manufacturer's facility pertains to their search.). Selecting only one CAGE from a Company Name pick list will be considered unacceptable by DLA Troop Support since searching by only one CAGE code would result in multiple searches that would negatively impact research time.

5. Keyword searches must select all the records that match the keyword values.

6. Applicable fields or a combination of fields must independently search each database.

The AMDF must be searched by any combination of the following search keys: NIIN and LIN; Procurement Histories must be searched by NIIN, FSC, CAGE Code, DUNS Number, Source of Supply, Contract Number and Government Fiscal Year. The MIAPL must be searched by APL/RIC, Nomenclature, Drawing Number, Specification Number, NIIN, CAGE, Manual Number; DODAAF database must be searched by City, Country, Agency Name, State, Zip Code or DODAAC Code. The CAGE database must be searched by any combination of the following search keys: CAGE, Company Name, City, State, Zip, SIC, Telephone Number.

7. Technical Characteristics must be searched by specifying any search in the FLIS, and then, narrowing the search by any applicable technical characteristics, regardless of INC (Item Name Code) or Item Names. Users must be able to research parts by entering one or more of its technical characteristics. Users must also have the ability to select one or

Attachment 3 – Page 9 more answers from a pick list of valid replies. Selecting only one value from the pick list will be considered unacceptable by DLA Troop Support since this will not fulfill the purpose of searching by technical characteristics. Users must then be able to cross-reference the FLIS data for each technical characteristic record retrieved and instantly view all relevant data to the computer screen.

8. A flexible Batch feature must be available to query each database independently by any single search key. The FLIS database must also be searched by a Part/CAGE combination in order to retrieve just those specific FLIS records. Batch data must be input via keyboard or a file and downloaded to either the printer or a file. Output to a batch must be available in the following formats: Standard formatted reports, user customized formatted reports, ASCII reports or user customized ASCII reports. Users must be able to save their search values entered manually to a

9. file for later use. Batch values resulting in no hits must be recorded in an error log. Users must not be limited to the number of batch values searched when entering batch values by file.

10. The batch processing must take place on the server so that the user's workstation is not tied up during the batch process.

11. The system must provide an instant, clearly visible cross-reference to additional databases that have more information regarding the part searched.

12. To accommodate DLA Troop Support users, the system must allow users to search by a NICN (Navy Item Control Number) in the FLIS search screen. If the NICN has been assigned a FLIS record, the system must report back the FLIS record and show the NIIN/NSN cross referenced.

13. To accommodate DSCP Navy database users, the APL and AEL databases must have the ability to search by NOMENCLATURE, and HULL #. Nomenclature searches must search all words (regardless of order) and numeric values. This is a key factor for accurately researching APLS. Also, the APL and AEL databases must support batch searching, where users are able to customize their output to a field level. Also, to accommodate DSCP Navy database users, the service must allow output to the Navy's ICAPS and ROMIS software programs. This is needed since output to these programs saves labor time and ensures accuracy.

14. The National Forging and Tooling Database (NFTD) should provide Federal Supply Code, National Item Identification Number, Part Number, Forging/DIE Number, Forge Shop and Commercial and Government Entity Code.

15. The databases must be updated promptly, i.e. within days of receiving the published data to ensure up-to-date, accurate information.

Attachment 3 – Page 10

VENDOR CATALOG REQUIREMENTS

1. Industrial & Electronic Parts and Equipment Catalogs & Data Sheets (Manufacturers'

Catalogs) provide the ability to reduce procurement costs and make better buying decisions by providing multiple sources for industrial & electronic parts and equipment.

This is critical in meeting the DoD wide requirement to implement the use of more Commercial Off-The-Shelf (COTS) and EBS initiatives.

2. Engineers and purchasing agents at DLA Troop Support must be parts catalog mavens, adept at quickly finding the part with the right specifications from the right company at the right price. Paper-based catalogs make this a difficult and time-consuming task.

Different companies Use different terms, part numbers, and organizational schemes to display their wares. Therefore, DLA Troop Support requires an on-line information system for viewing manufacturers' catalogs via the WWW. The system must provide expeditious and flexible search Capabilities. Product must be commercially available "off the shelf ' at the time of award.

Product Functionality for Vendor Catalogs:

1. The database must be searched by any combination of the following fields: Keyword, Part Number (which can include any numeric searches; e.g., part number, referenced Document number, NIIN, NSN, etc.), Manufacturer Name, (includes old names, alternate Names or GSA contractor number. Both PDF and non-PDF documents are searchable and accessible in this database.

2. The database must allow searching for manufacturer's catalogs by any of the following:

Street Address, City, State, Zip/Postal Code, Country, Telephone #, Fax #, SIC Code, NAICS Code, CAGE Code with a result of the actual vendor's catalog or data sheet.

3. The results list from any search must produce a single list of results with the ability to View manufactures information and/or full-text catalogs from that results page.

4. The service must include full-text database to both commercial vendor and GSA Information. It must contain full-text document pages of supplier catalogs, data sheets, and related documents, and contains GSA supply schedules, contractor information, and related publications. All COTS or government-approved sources for items and information can be searched, viewed, and printed using the same product and the same search engine.

5. It must use the Internet, standard Web browsers, and the Adobe Acrobat image viewer to deliver the data, so no customized software installation or configuration is necessary to use the product.

6. The user must be able to find manufacturer or distributor information for the item searched.

7. The user must be able to automatically cross-reference other applicable databases for more information about the item searched.

8. The database must be updated promptly to insure the availability of current, accurate

Attachment 3 – Page 11 information.

Document Images/Text:

1. All scanned images must be scanned at 300X300 dpi.

2. Images must be viewable in the PDF (Adobe Acrobat) Viewer.

3. All documents must be viewable/searchable.

4. Must be able to print individual pages, range of pages, or the complete document.

Fasteners Database:

1. The database must identify, specify and source fastener hardware including bolts, bushings, fasteners, grommets, studs, insets, nuts, nut plates, pins, pins-springs, key & seat, posts, rivets, screws, spacers, washers, snap, and wire. The database must be searched by part number, document number, text fields and parametrically by fastener category attributes (materials, finish, head style, head recess, type, nominal size, thread type, grip, length and strength). The database should also have the ability to link to the related Industry Fastener Standard (AIA/NAS, ASME, BSI, and MIL) in the Industry/Military Standards database. The results should be able to be displayed in a side-by-side comparison.