Tested Products: Version 4
Products submitted for testing to MultiSpeak Version 4 are tested for interoperability. The testing begins when two products (typically from different vendors) are submitted for a joint test. The vendors develop an assertions document that states the joint MultiSpeak functionality that they wish to claim and how those capabilities may be used to support utility business processes. The independent testing agency then verifies that the two products integrate in the manners described and that the integration is achieved using MultiSpeak. The verified assertions documents are available either from the vendors participating in the test or directly from the MultiSpeak Project Technical Coordinator.
Version 4 Interoperability Documents |
||
 |
SageQuest-Milsoft Version 4 Mobile Control Interoperability | Posted 2/19/10 |
|
Clevest-Milsoft Version 4 Mobile Field Force Interoperability | Posted 10/15/09 |
You may use these documents as a way to see, in detail, exactly what MultiSpeak-compatible integration is included in vendor product interfaces.
The Use and Importance of the Assertions Document
The purpose of the assertions document is to educate utility staff members on what level of MultiSpeak integration could be expected between two specific products that have completed Version 3.0 interoperability testing. Assertions documents are written with the utility audience in mind. They answer the following questions:
- What can I do with the software products that would not be possible without the MultiSpeak integration?
- Why is this shared functionality important to my business processes?
- How have the vendors used MultiSpeak to accomplish the integration described?
- How much of the MultiSpeak defined interface capability does this interface support?
Note that assertions documents do not necessarily describe all of the capabilities of an interface between two products, only those that are accomplished using MultiSpeak. It is certainly possible for two vendors to support other integration features that are not included in MultiSpeak; for a description of such features, contact the affected vendors directly.
Utilities can use assertions documents in two ways:
- You have MultiSpeak-compatible software and you want to know what it does, and does not, do.
- You are considering the purchase of software and want to compare the MultiSpeak integration supported by alternative vendor offerings.
This type of testing is performed by the NRECA-approved testing agent when pairs of vendors specifically request and pay for such testing. It should be noted that, in some cases, products may be interoperable, but the vendors have not chosen to pay for testing to document this fact. For some vendors, whose products are expected to integrate with a large number of software products offered by different vendors, the cost of testing all possible combinations of software can be burdensome. Alternatively, a utility may choose to require interoperability testing for a pair of products that have not yet been jointly tested as a software quality control step during software procurement. In such a case, the cost of the test may be borne by the utility or by the vendor(s) of the software in question.