STATEMENT OF WORK.docx

The salient characteristics of the services required are as follows:

1.0 A web service shall be supplied for access to part information with the following characteristics:

1.1 Accessible by Government (Navy) systems.

1.2 The ability to store information at a minimum 300,000 parts, with an expected normal growth rate of 10% per year.

1.3 An Application Programming Interface (API) to access the web service with the following characteristics.

1.3.1 API documentation sufficient to describe how to connect to, query, and retrieve part information from the service, as well as send part information to a list of parts stored on the vendor’s system which will be used to get weekly status.

1.3.2 The ability to retrieve part information and status for a list of parts stored on the vendor’s system (subscription list).

1.3.3 The ability to query for part information for individual parts.

1.3.4 Be able to provide specific change notifications for parts on the subscription list by date, such as, but not limited to: product change notifications, product discontinuation notifications, counterfeit notifications, and transfer notifications.

1.3.5 Can be used to query the Vendor's system database on part type, technology type, and other factors.

1.3.6 The ability to retrieve alert information when a part status changes for a list of parts stored on the vendor’s system (subscription list).

1.4 The ability to provide information listed in 1.4.1 through 1.4.9 about parts of interest (single part queries or subscription list)

1.4.1 Manufacturer’s part number for the part.

1.4.2 Commercial and Government Entity names and manufacturer ID for the part.

1.4.3 A description of the part (Nomenclature).

1.4.4 REACH, RoHS and Lead-Free information for a part.

1.4.5 The manufacturer name for the part.

1.4.6 Lifecycle information for the part.

1.4.6.1 Predicted years to End of Life (YTEOL) provided via Lifecycle Availability projection in years for Active part types

1.4.6.2 Estimated lifecycle stage provided via Lifecycle Availability projection in years for Active part types - Preliminary production status reported for not-yet-released parts, updated production status to Active when production confirmed, and End-Of-Life date for parts with last time buy.

1.4.6.3 Estimated Production Start and End Date

1.4.7 The following part characteristics

1.4.7.1 Package

1.4.7.2 Pin Out

1.4.7.3 Technology type or technology sector

1.4.7.4 Maximum and minimum operating temperature

1.4.8 Data sheets for the part, if available.

1.4.9 Market information for the part

1.4.9.1 Current production status and lifecycle availability projection

1.4.9.2 Obsolescence date

1.5 No service caps on queries against loaded OMIS master of 300,000 parts plus 10% per year in API

1.6 All query information shall be provided in an industry standard Extensible Markup Language (XML) format.

1.6.1 The query return format shall be clearly identified and described in the API documentation.

1.7 Industry standard methods of connecting and communicating.

1.7.1 The interface shall be either Restful or SOAP format, with Restful being preferred.

1.8 The ability to initially load and re-baseline the subscription list as needed by the government.

1.9 The web service shall provide better than 95% uptime.

2.0 The web service shall have a User Interface (UI) that can do the following:

2.1 Allow for a minimum of five (5) users to be logged in simultaneously. Unlimited simultaneous user access will be granted.

2.2 Allow for individual parts to be searched and the following part information returned.

2.2.1 Part information listed under requirement 1.3

2.3 The ability to search batches of parts.

2.3.1 The UI’s batch search function shall be usable with only a part number and manufacturer name.

2.3.2 Provide all of the same information listed under requirement 1.3

2.4 Allow for part alternates to be searched.

2.4.1 Alternates shall be identified as being form, fit, function replacements where applicable.

2.4.2 Alternates shall indicate if they are from the same manufacturer cage as the original searched part.

2.4.3 Allow for parts to be searched based on part attribute data such as: technology, family, group, capacity, category, class, type, Org, program, function, pin count, and package.

2.5 Provide alert information when a part status changes.

2.5.1 Provide alert histories when requested.

2.5.2 Provide End of Life notices for parts when available.

2.5.3 Provide Life of Type buy notices when available.

2.6 Provide the ability to load and store lists of parts (Bill of Materials (BOM)) into locations to enable the user to assess those parts.

2.6.1 Identify which parts in the BOM are recognized by the application and provide assistance in correcting unrecognized parts.

2.6.2 Allow the BOM to be structured in a hierarchical fashion based on a field that provides where used data. In addition to flat BOM format, three levels of structure (System/Box/Board) and where-used function available.

2.6.3 Provide a mechanism to edit the BOMs by adding or subtracting parts and to edit the items in the list

2.6.4 The ability to generate risk status reports for loaded BOMs

2.6.5 Provide all of the same information listed under 1.3 for the BOMs

2.6.6 Provide instantaneous obsolescence notification (alerts) with all new obsolescence issues referenced against a loaded BOM