| Q. 1 |
Is it true that MIOS support the existing meters in field?
|
| Ans |
Yes. MIOS supports the existing meters which are deployed in the field.
It is the only interoperability solution which takes care of both existing as well as futuristic requirements in the metering space. |
|
| Q. 2 |
What is CFW?
|
| Ans |
CFW stands for Common Frame Work. This is the main application which acts as the user interface for providing interoperability and invoking the manufacturer specific APIs. |
|
| Q. 3 |
What is CFW and APIs?
|
| Ans |
CFW is the third party software and manufacturers provide the API’s or Application Program Interfaces.
There are 3 API’s. a) API 1 – For Meter readings b) API2 – For MRI downloading c) API3 for converting to Common data format (CDF). Pease refer section 3 of interoperability document for more clarity. |
|
| Q. 4 |
Will the utilities/ system integrators be able to use a single software to collect data from multiple makes of meters?
|
| Ans |
Yes. Single software, CFW, can be used to download data from multiple make of meters. |
|
| Q. 5 |
Can one software be used to view data of the existing meters and the meters which will be installed in future ie. After the implementation of MIOS?
|
| Ans |
Yes. Same software can be used to view the data of existing meters as well as future meters. MIOS is the only interoperability solution in the world which provides this advantage. The API concept makes it simple and convenient and thus useful to the end user. |
|
| Q. 6 |
Does MIOS require all meters to give same data?
|
| Ans |
MIOS work irrespective of the data send by the meter. The different makes of meters can send data in their proprietary format. APIs. |
|
| Q. 7 |
Will MIOS support both remote collection of data and MRI collection of data?
|
| Ans |
Yes. MIOS supports both MRI based data collection as well as remote collection of data. |
|
| Q. 8 |
Can the existing MRI or modem be used even after the implementation of MIOS?
|
| Ans |
Yes. The existing MRI and modem can be used.
|
|
| Q. 9 |
Will CFW/MII enable MRI to collect data from multiple makes of metes?
|
| Ans |
The collection of data using MRI will continue the same way as it is now. The CFW/MII will come into picture once data is being collected from the MRI to the PC.
|
|
| Q. 10 |
Which all MRI makes will this CFW support?
|
| Ans |
The make of MRI is irrelevant as far as CFW is concerned, as long as it downloads data from the meter and dumps it to the PC.
|
|
| Q. 11 |
Will the data collected and stored in the manufacturer specific folder be used at any time?
|
| Ans |
The data collected and stored in the manufacture specific folder may be used. The manufacture specific analysis software should be able to open this file. This method may be used to verify the authenticity of the data displayed by CFW.
|
|
| Q. 12 |
When does MII use TCP/IP and when does it use Configuration file?
|
| Ans |
Meter Interprocess protocol is an effective means of communication between the two systems. Smaller message will be transferred via TCP/ IP link while bigger message will still be transferred via configuration file. |
|
| Q. 13 |
Is it possible to collect selective data from the meter?
|
| Ans |
Yes. Selective data collection is possible such as billing parameters, instantaneous parameters etc. |
|
| Q. 14 |
How will the API verify that it has been invoke by an authenticate program?
|
| Ans |
API can be invoked by a program which follows MII protocol. If it follows MII protocol, then it can be called CFW. |
|
| Q. 15 |
What will the API do if the Baud rate is not 1200?
|
| Ans |
1200 has been accepted as the default baud rate for the modem. The API can change the baud rate to its desired value, but when it terminates its operation it should switch the baud rate to 1200. |
|
| Q. 16 |
Should all the CDF files be in XML?
|
| Ans |
Yes. The CDF files should be in XML. |
|
| Q. 17 |
Where will the read result file be stored?
|
| Ans |
The read result file will be stored in the ‘READRESULT’ folder that is inside the manufacturer specific folder. |
|
| Q. 18 |
What does result with deviation mean (Status 2 in result code)?
|
| Ans |
Status code 2 means result with deviation. If all the parameters mentioned in ‘WHATTOREAD’ is not read but collection of other parameters were successes, then it is indicated by ‘2’. The parameters which were not read are mention in the result file under the tag ‘DEVIATION’. |
|
| Q. 19 |
What is the need of the module (API) for checking integrity of the data?
|
| Ans |
The integrity of the data is being checked to ensure that the data has not been altered in the process of data transfer. This is being ensured using authenticators for which the seed is available with the sender and the receiver. |
|
| Q. 20 |
CFW should ensure "Scalability of the software", what does it mean by scalability?
|
| Ans |
If there are any changes/additions in features, new codes will have to be added to accommodate these. The provision of upward scalability has to be built-into the software. |
|
| Q. 21 |
Why is SCADA and Online data collection application referred for?
|
| Ans |
Supervisory Control And Data Acquisition has been mentioned to clarify that such applications are not envisaged in this document. |
|
| Q. 22 |
Why are log files required?
|
| Ans |
Log files are used to capture communication which takes place between CFW and APIs. |
|
| Q. 23 |
As per document "Multiple meter reading option is applicable only when more than one meter is connected on the same network (or on the same telephone line). When multiple meters reading option is chosen each meter is read sequentially. Next meter reading is started once first meter reading is completed." Does it mean there can not be parallel communication i.e parallel data collection?
|
| Ans |
Parallel data collection is possible. In single instance only one port will be used and so the collection of data will be sequential. In case of multiple instances we have several ports dedicated for collection and data can be collected simultaneously. |
|
| Q. 24 |
"For verification purpose of the data given by Read API, a suitable tool will have to be supplied by the respective manufacturer." What is the actual expectation?
|
| Ans |
Any software tool which displays the data and helps manually verifying the data collected by the READAPI will do. Manufacturer specific software for data collection and viewing may also be used. |
|
| Q. 25 |
The output of the Read API is in Manufacturer format, how can it to be verified?
|
| Ans |
Any software tool which displays the data and helps manually verifying the data collected by the READAPI will do. Manufacturer specific software for data collection and viewing may also be used. |
|
| Q. 26 |
What is the use of instance id and instance number?
|
| Ans |
Instance ID and Instance number are the same. They are generated by CFW and used to link the instance of meter reading with the messages. This number will also be passed in the configuration file prepared by CFW. It shall be the responsibility of CFW to link the messages between API and itself with the instance number. It will be the responsibility of CFW to maintain unique instance Id. Maximum length Instance Id will be of 4 characters. |
|
| Q. 27 |
Authenticator=fn(Data+Seed).What do you mean by seed?
|
| Ans |
The Authenticator is used to verify the integrity of the data. The authenticator is a function of seed and data. The seed is a particular code, which both receiver and sender are aware of. At the sender side the authenticator will generate a value using the seed and the data and append this value to the message. At the receiver side also this action is performed and the value generated is compared. If it is the same then the data is assumed to be correct. |
|
| Q. 28 |
What is instantaneous parameter?
|
| Ans |
Instantaneous parameters are the values which the meter record at a particular instant. |
|
| Q. 29 |
Is it necessary for meter to have a TCP/IP port for CFW and API to work?
|
| Ans |
The TCP/IP is defined for communication between the CFW and API. Meter is not required to have a TCP/IP port. |
|
| Q. 30 |
Can you tell us the communication link between the third party software, CFW and Manufacturers API?
|
| Ans |
Meter Interoperability Interprocess protocol is the means of communication between the two systems. The two systems will communicate with each other through sockets by establishing a TCP/IP connection and passing messages on this channel. Smaller message will be transferred via TCP/ IP link while bigger message will still be transferred via configuration file. |
|
| Q. 31 |
Who generates the configuration file that needs to be transferred to the API?
|
| Ans |
CFW will generate configuration files and pass it to API via MII protocol. |
|
| Q. 32 |
What is the format for specifying the different parameters in the CDF file?
|
| Ans |
Some common parameter code definitions are provided in the section 14 of interoperability document. Eg. R-Phase phase to neutral instantaneous voltage
P1-1-1-1-0 |
|
| Q. 33 |
Where id the CDF file stored? How is it transferred to the CFW?
|
| Ans |
API converts the manufacturer specific format files to CDF and stores in the CDF done folder. The responsibility of picking the CDF files lies with CFW. |
|
| Q. 34 |
In which programming language should the CFW be developed?
|
| Ans |
Any programming language can be used for developing CFW. |
|
| Q. 35 |
Will Read API exe launch itself on its own? How will it exchange license information with CFW?
|
| Ans |
Read API will not launch by itself. It has to be launched by CFW. Exchange of license information with CFW is not required. API will manage its own license information. |
|
| Q. 36 |
"On launching of API, its icon can be seen in system tray". How will multiple instances of API be launched?
|
| Ans |
CFW will launch API. One API, by itself will handle multiple requests. Each request will have unique instance ID. |
|
| Q. 37 |
How will the API get terminated?
|
| Ans |
CFW will terminate the API in the way similar to the way it invokes the API. |
|
| Q. 38 |
How does the CFW invoke the API?
|
| Ans |
The CFW should pass IP address and port number as two command line parameters. IP address is first parameter and port number is second parameter.
Example of passing parameter
172.16.1.123 3333 |
|
| Q. 39 |
Is server port no. = 12345 for all instances of Read API client?
|
| Ans |
Port 12345 is for API’s of all manufacturers. All communication between API’s and CFW will happen from this port only. Each manufacturer will have only one instance of API. |
|
| Q. 40 |
How can a system integrator get the APIs?
|
| Ans |
The APIs will be supplied to the utilities. System integrators can procure APIs from utilities or directly from IEEMA-MIOS. To procure from MIOS the system integrator will have to furnish a letter from the utility that authorizes supply of API to the integrator. |
|
| Q. 41 |
How MIOS support inbound dialing?
|
| Ans |
e-APIs are under development. Once e-API are developed inbound dialing will be available. |
|
| Q. 42 |
Is there a way I can find version number of API?
|
| Ans |
G30 & G31 tag provides version number of API3. API1 version can be found by ReadAPI / v. |
|
| Q. 43 |
Who will certify the API ?
|
| Ans |
Independent Testing agency will certify API based on the test case document. |
|
| Q. 44 |
How to test the APIs? Is there tool available to test APIs?
|
| Ans |
APIs testing s/w will be available to test the APIs. |
|
| Q. 45 |
What will be the APIs testing procedure?
|
| Ans |
API testing will focus on interface testing which is specified in the test case document. |
|
| Q. 46 |
Is it possible to get the APIs from MIOS web site?
|
| Ans |
Application can be given through web site subsequent to which respective meter manufacturer will supply API within a given time frame |
|
| Q. 47 |
Is it possible to get the information about the APIs released by the different manufacturer?
|
| Ans |
Yes the information will be available on web site & respective version number which that API supports |
|
