Quick Start
From MIP Wiki
This is a Quick Start Guide for Data Collectors & System Operators. The MIP Test Management Tool (MTMT) is designed to conduct both SLT and OLT type test events.
Perhaps the most important concept to understand is that every test event (or test case) can only have one source (sender) but could have muliple targets (receivers). This design will allow the test organisation to quickly assess the results of a test because they can track any problem down to a single source.
The value of the test results depends on the quality of the input that the data collectors provide. For this reason, comments are always mandatory for every answer.
Contents |
[edit] Create Account or Login
Create an account or login with an existing username / password. Use the 'Sign-Up' link on the left menu bar to create a new account or use the login form to sign-in with an existing account.
Note: If you've just created an account, you must wait for a Test Controller to verify your information and upgrade your privledges to "Data Collector - System Operator" before you proceed.
[edit] Select a Test
Select the Test you are conducting. From the left menu bar click "Select Test" -- select a published test from the test list. If your test is not available, notify your test director.
[edit] Create or Join Open Test Iteration
You must either create a test iteration or join an existing test iteration. For OLT type tests, the test controller will normally create test iterations. For bi-lateral SLT type tests, only one of the two data collectors needs to create a test iteration. Please be aware that Data Collectors may only close test iterations which they created themselves. For bi-lateral tests, we suggest that the "source" system will do this.
[edit] Create Test Iteration
To create a test iteration, select 'Create Test Iteration' from the left menu bar. You must provide a name and description for the iteration (to allow the test controllers to find your iteration later), then select which systems and organisations will participate in the test. At least two organisations must be active for any test iteration. 'Iteration Name' must include an a start date or period (and the systems under test for SLT); 'Description' must include the systems under test and the roles they play.
Examples:
'Iteration Name': OLT CV 28 March 2007
'Description': OLT CV 28 March 2007. DEU=DIV N, USA1=DIV S, NOR1=BDE A, BEL=BDE B, SWE=BDE C.
'Iteration Name': SLT1 09 Sept 2007 DEU-USA1
'Description': SLT1 09 Sept 2007 DEU-USA1. DEU=Node A, USA1=Node B.
[edit] Join Existing Test Iteration
To join an existing test iteration select 'Show Open Iterations' from the left menu bar. Select an open iteration from the open iteration list.
[edit] Select System and Roles
Once you have created or selected an open iteration, you must then select your system and role. Available roles are 'System Operator', 'Data Collector', or 'View Answer'.
[edit] System Operator
Select 'System Operator' if you are manageing the event list (i.e. running the "injects") on your national C2 Information System (C2IS). You will be able to update the iteration when your events are complete but you will not be able to input any data collector answers.
[edit] Data Collector
Select 'Data Collector' if you are answering questions for the C2 system you are responsible for. Normally for OLT type tests, data collectors will not conduct self evaluations of their national C2IS. The test organisation will 'assign' data collectors to a different C2IS.
[edit] View Answers
This puts you into a 'read-only' mode to allow you to view answers submitted for any particular organisation / system.
[edit] Conduct Test
The first test event is displayed once you select a role.
[edit] System Operator
You will be able to select the "Click Complete" or "Click Skipped" link when your selected organisation / system is the Source. Select "Click Complete" if you are ready with the inject. The target systems will see the event is complete (green dot) and can collect data. Select "Click Skipped" if your system doesn't have the capability to do the inject. The target systems will see the event is skipped (yellow dot) and will not search for data on the system (they will have to answer the data collection question with SKIP).
[edit] Data Collector
You will be able to answer questions when your selected organisation / system is the Target. Please be aware you are collecting data for other people: your comment should be complete and understandable for someone that was not participating in the test! The status of event could be: (e.g. of comment)
GO : "OK" Skip: "Div N Recce (WHO!!) does not have MEM capability"; N.I.: "The system does not implement holdings"; K.O.: "Mapping to (WHO!!) C2IS didn't work.
If an event asks to attach a file (a .jpg to display the "operational situation"), follow these operations:
A) Click the "attach file" command; B) Go to the folder where you have saved the file and select it (remember the naming conventions); C) Click the "Upload" command; D) Click the "Submit answer".
If you want remove an attached file, click the (X) near it. IMPORTANT: Save .jpg for screenshots of the "operational situation" only!
[edit] Filter
To display only 'your' events (in the ones your system is the source or the ones you have to collect data on), select the "Click for Filter On" link.
[edit] Close Test Iteration
Data Collectors may close test iterations which they created. All other test iterations must be closed by a Test Controller or Test Director.
[edit] View Test Report
Only test data from closed iterations is used in test reports. Data Collectors can run an 'Iteration Report' to view the test results from their iteration.
