Changes between Version 3 and Version 4 of SIS/UI/Tutorial-v1.0/StationSummary


Ignore:
Timestamp:
06/19/12 15:47:14 (5 years ago)
Author:
skientz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SIS/UI/Tutorial-v1.0/StationSummary

    v3 v4  
    3535  [#UpdateStationInstruments Update Station Instruments] 
    3636 
    37       1. Install a new logger and its sensor(s) 
    38       1. Add a Sensor to an existing Logger 
    39       1. !Sensor/Logger swap 
    40       1. !Sensor/Logger temporary removal 
    41       1. !Sensor/Logger reinstall 
    42       1. Sensor removal to end channels 
     37      1. Install a New Logger and its Sensor(s) 
     38      1. Add a Sensor to an Existing Logger 
     39      1. !Sensor/Logger Swap 
     40      1. !Sensor/Logger Temporary Removal 
     41      1. !Sensor/Logger Reinstall 
     42      1. Sensor Removal to End Channels 
    4343      1. Terminate Station 
    4444 
     
    4747  [#UpdatePowerDevices Update Power Devices] 
    4848 
    49       1. Install a new device 
     49      1. Install a New Device 
     50      1. Swap a Device 
     51      1. Remove a Device 
     52 
     53  [#UpdateTelemetryDevices Update Telemetry Devices] 
     54 
     55      1. Install a New Device 
    5056      1. Swap a device 
    5157      1. Remove a device 
    5258 
    53   [#UpdateTelemetryDevices Update Telemetry Devices] 
    54  
    55       1. Install a new device 
    56       1. Swap a device 
    57       1. Remove a device 
    58  
    5959[#PowerInstallations Power Installations] 
    6060 
     
    8080 
    8181The date format YYYY-MM-DD is used in this form and other forms in the UI. 
    82 The date 3000/01/01 is used in SIS to indicate an ‘active’ epoch for stations/channels/etc.  
     82The date 3000-01-01 is used in SIS to indicate an ‘active’ epoch for stations/channels/etc.  
    8383 
    8484Form Tip: If you do not want to submit the form, then click the Back button on your browser to return to the page you were at previously.  You can do this for virtually all forms in the SIS UI. Exceptions will be noted as needed. 
     
    9898#!html 
    9999<p style="text-align: center"> 
    100 Figure 1: Jump to Station form 
     100Figure 1: Jump to Station Form 
    101101</p> 
    102102}}} 
     
    138138#!html 
    139139<p style="text-align: center"> 
    140 Figure 3. Station Header module in the Summary page (example for station CI.XX1) 
     140Figure 3. Station Header Module in the Summary page (example for station CI.XX1) 
    141141</p> 
    142142}}} 
     
    201201===== !Channel/Response ===== 
    202202 
    203 1. Instrument history by date: report of the logger and sensor installation history at this station. 
    204 2. Channel configuration epochs: report of select fields of the station’s channel configuration epochs. 
    205 3. Instrument history by channel: report of the logger and sensor installation history by channel. (The instrument-history-by-fate report is an aggregate view that collapses the channel information.) 
    206 4. Channel Manager: This section allows the user to view and modify the metadata of individual channels.  (See the Channel Manager section for more details.) 
     203  * Instrument history by date: report of the logger and sensor installation history at this station. 
     204  * Channel configuration epochs: report of select fields of the station’s channel configuration epochs. 
     205  * Instrument history by channel: report of the logger and sensor installation history by channel. (The instrument-history-by-fate report is an aggregate view that collapses the channel information.) 
     206  * Channel Manager: This section allows the user to view and modify the metadata of individual channels.  (See the Channel Manager section for more details.) 
    207207 
    208208 
    209209===== !Installations/Logs ===== 
    210210 
    211 1. Station Logs: shows all the log entries for the station. Click on the subject to see the full entry. For authenticated users, there is a link to create a new log entry. (See User Actions for instructions). 
    212 2. Power installations: shows all the Power device installations at the station (historical epochs and current). 
    213 3. Telemetry installations: shows all the Telemetry device installations at the station (historical epochs and current). 
     211  * Station Logs: shows all the log entries for the station. Click on the subject to see the full entry. For authenticated users, there is a link to create a new log entry. (See User Actions for instructions). 
     212  * Power installations: shows all the Power device installations at the station (historical epochs and current). 
     213  * Telemetry installations: shows all the Telemetry device installations at the station (historical epochs and current). 
    214214 
    215215 
    216216===== External Links ===== 
    217217 
    218 1. SCSN Operators list email archive for the station 
    219 2. SCSN Operators Contact information for the station 
     218  * SCSN Operators list email archive for the station 
     219  * SCSN Operators Contact information for the station 
    220220 
    221221 
     
    260260The form fields are: 
    261261 
    262 {{{ 
    263 Check the numbering here and fix 
    264 }}} 
    265  
    266  1. From: initialized with the user’s email address. 
    267  2. Recipient: 
    268  
    269  1. Production site: the field is initialized with the SCSN Operators list email address. 
    270  2. Test site: the field is initialized with the user’s email address. 
    271  3. You may enter a comma-separated list of valid email addresses. 
    272  
    273  1. Subject:  initialized with the station code 
    274  2. Message: initialized with a template commonly used by SCSN operators to report field work.  It includes a short description of any user actions recorded via the UI. 
    275  
    276  1. Note: the station contact URL is an SCSN-specific link 
    277  1. Log email: Check this box to automatically create a station log entry in the database from the subject and message fields of the email form. 
     262  * From: initialized with the user’s email address. 
     263  * Recipient: 
     264     - Production site: the field is initialized with the SCSN Operators list email address. 
     265     - Test site: the field is initialized with the user’s email address. 
     266     - You may enter a comma-separated list of valid email addresses. 
     267 
     268  * Subject:  initialized with the station code 
     269  * Message: initialized with a template commonly used by SCSN operators to report field work.  It includes a short description of any user actions recorded via the UI. 
     270     - Note: the station contact URL is an SCSN-specific link 
     271 
     272  * Log email: Check this box to automatically create a station log entry in the database from the subject and message fields of the email form. 
    278273 
    279274 
     
    292287First, the user must select the field action to be done, and specify the GMT datetime of the action. 
    293288 
    294  1. Install a new logger and its sensor(s) 
     289==== 1. Install a New Logger and its Sensor(s) ==== 
     290 
    295291This action is used for: 
    296   a. A new station with no instruments 
    297   b. Adding an additional datalogger at a station with its own sensor(s). 
     292   1. A new station with no instruments 
     293   1. Adding an additional datalogger at a station with its own sensor(s). 
    298294 
    299295 
     
    305301#!html 
    306302<p style="text-align: center"> 
    307 Figure 5. Update Station Instruments Form: select Station action 
     303Figure 5. Update Station Instruments Form: Select Station action 
    308304</p> 
    309305}}} 
     
    311307Note the Tips section below the form on the page. It describes the station-actions which are: 
    312308 * Add a new logger and its sensor(s) 
    313  * Select this action to install a new logger and one or more sensors at a locationcode. 
     309     - Select this action to install a new logger and one or more sensors at a locationcode. 
    314310 * Terminate Station 
    315  * This removes all online instruments, end all online channels, and set the station offdate. 
     311     - This removes all online instruments, end all online channels, and set the station offdate. 
    316312 
    317313 
     
    328324#!html 
    329325<p style="text-align: center"> 
    330 Figure 6. Install new logger and sensor(s) form 
     326Figure 6. Install New Logger and Sensor(s) Form 
    331327</p> 
    332328}}} 
     
    337333 
    338334 1. Loggertype: Select the logger model of the logger to be installed from the loggertype dropdown. 
    339  2. Logger !S/N: The !S/N dropdown is then populated with the available loggers of the selected loggertype. 
    340  
    341  1. ONLY loggers having inventory status=INVENTORY are displayed in the dropdown. 
    342  2. Select the serialnumber of the logger to be installed. 
    343  
     335 1. Logger !S/N: The !S/N dropdown is then populated with the available loggers of the selected loggertype. 
     336     a. ONLY loggers having inventory status=INVENTORY are displayed in the dropdown. 
     337     a. Select the serialnumber of the logger to be installed. 
    344338 1. Configuration: The Channel configuration dropdown is populated with the available channelset(s) for the selected loggertype.  The default selection is the most common use for SCSN stations. 
    345  2. Sensortype: select the sensor model of the first sensor from the sensortype dropdown. 
    346  3. Sensor !S/N: The !S/N dropdown is then populated with the available sensors of the selected sensortype. 
    347  
    348  1. ONLY sensors have inventory status=INVENTORY are displayed in the dropdown. 
    349  2. Select the serialnumber of the sensor to be installed. 
    350  
     339 1. Sensortype: select the sensor model of the first sensor from the sensortype dropdown. 
     340 1. Sensor !S/N: The !S/N dropdown is then populated with the available sensors of the selected sensortype. 
     341     a. ONLY sensors have inventory status=INVENTORY are displayed in the dropdown. 
     342     a. Select the serialnumber of the sensor to be installed. 
    351343 1. Depth: the sensor emplacement depth (units of meters) in the Depth textbox (default=0). 
    352  2. Channels: The Channel configuration dropdown is populated with the available channelset(s) for the selected sensortype.  The default selection is the most common for SCSN stations. 
    353  3. Locationcode: The default locationcode for SCSN stations is 2 blank characters: ‘  ‘.  The convention is to accept 2 dashes ‘--’ as equivalent to the default locationcode. If the sensor is using another locationcode (e.g. 00, 01, etc), then edit the value in the Loc textbox. 
    354  4. If the logger has another sensor, click the ‘Add another Sensor’ button which updates the form with a new set of dropdowns for a next sensor. Repeat Items #4-8 for the next sensor. 
     344 1. Channels: The Channel configuration dropdown is populated with the available channelset(s) for the selected sensortype.  The default selection is the most common for SCSN stations. 
     345 1. Locationcode: The default locationcode for SCSN stations is 2 blank characters: ‘  ‘.  The convention is to accept 2 dashes ‘--’ as equivalent to the default locationcode. If the sensor is using another locationcode (e.g. 00, 01, etc), then edit the value in the Loc textbox. 
     346 1. If the logger has another sensor, click the ‘Add another Sensor’ button which updates the form with a new set of dropdowns for a next sensor. Repeat Items #4-8 for the next sensor. 
    355347 
    356348 
    357349Below the form is a ‘preview’ of the expected channels that will be produced once the form has been submitted. It displays: 
    358350 
    359  1. A diagram of the logger’s boards and modules and shows how its sensitivity response is assigned to which channels. 
    360  2. A diagram of each sensor’s components and shows how its sensitivity response is assigned to which channels.  Within the sensor’s diagram are textboxes for the azimuth and dip of each sensor component. The textboxes are initialized with the most commonly used defaults.  You may edit them here, or use the Channel Manager (see the Channel Manager  document for more information). 
     351 * A diagram of the logger’s boards and modules and shows how its sensitivity response is assigned to which channels. 
     352 * A diagram of each sensor’s components and shows how its sensitivity response is assigned to which channels.  Within the sensor’s diagram are textboxes for the azimuth and dip of each sensor component. The textboxes are initialized with the most commonly used defaults.  You may edit them here, or use the Channel Manager (see the Channel Manager  document for more information). 
    361353 
    362354 
    363355Finally, click Submit to update the database.  At this time, the following database updates are done: 
    364356 
    365  1. A set of active channel epochs will be created whose epoch ondate is the GMT datetime specified earlier, and whose epoch offdate is active (3000/01/01 is the SIS convention for active offdate).  The set of channels created is determined from the submitted logger Configuration entry and the sensor Channels entry. 
    366  2. The channel epochs will be linked to the instrument response of the selected logger and sensor(s), and their simpleresponse is calculated. 
    367  3. The inventory status of the selected logger and sensor(s) is changed to INSTALLED. 
     357 * A set of active channel epochs will be created whose epoch ondate is the GMT datetime specified earlier, and whose epoch offdate is active (3000/01/01 is the SIS convention for active offdate).  The set of channels created is determined from the submitted logger Configuration entry and the sensor Channels entry. 
     358 * The channel epochs will be linked to the instrument response of the selected logger and sensor(s), and their simpleresponse is calculated. 
     359 * The inventory status of the selected logger and sensor(s) is changed to INSTALLED. 
    368360 
    369361 
     
    375367Note: To correct or delete the update you just made, you need to use the Channel Manager (see the Channel Manager  document for more information). 
    376368 
    377  2. Add a Sensor to an existing Logger 
     369==== 2. Add a Sensor to an Existing Logger ==== 
     370 
    378371This action is used for the case of: 
    379   a. A sensor was installed at a later time to an existing logger, 
    380   b. You only installed one sensor in the ‘Install a logger and its sensor(s)’ action and you wish to install another. 
     372   * A sensor was installed at a later time to an existing logger, 
     373   * You only installed one sensor in the ‘Install a logger and its sensor(s)’ action and you wish to install another. 
    381374 
    382375 
     
    410403 
    411404The install date submitted from the previous form is displayed in the page. (If it is incorrect, return to the previous page to re-submit the form).  The fields for this form are: 
    412 1. Locationcode: The default is 2 blank characters (displayed as 2 dashes in the form).  
    413 1. If the channels of this sensor are not using the default loccode, then edit the textbox. 
    414 1. Sensortype: Select the sensor model of the sensor to be installed from the dropdown. 
    415 2. Serialnumber: Select the serialnumber of the sensor to be installed from the dropdown.  
    416 1. Only sensors having inventory status=INVENTORY appear in the dropdown. 
    417 1. Channels: The channelset to use for the sensor. The default selection is the most common. 
    418 2. Logger configuration: The channelset to use for the logger. The default selection is the most common for SCSN stations. 
    419 3. Latitude, Longitude, Elevation:  The textboxes are initialized with the station’s coordinates.  
    420 1. If the sensor has different coordinates, then edit the textboxes with the values to use for the channels belonging to that sensor. 
    421 1. Emplacement depth: Positive downward value in meters. Defaults to 0. 
     405 1. Locationcode: The default is 2 blank characters (displayed as 2 dashes in the form).  
     406     a. If the channels of this sensor are not using the default loccode, then edit the textbox. 
     407 1. Sensortype: Select the sensor model of the sensor to be installed from the dropdown. 
     408     a. Serialnumber: Select the serialnumber of the sensor to be installed from the dropdown.  
     409 1. Only sensors having inventory status=INVENTORY appear in the dropdown. 
     410 1. Channels: The channelset to use for the sensor. The default selection is the most common. 
     411 1. Logger configuration: The channelset to use for the logger. The default selection is the most common for SCSN stations. 
     412 1. Latitude, Longitude, Elevation:  The textboxes are initialized with the station’s coordinates.  
     413     a. If the sensor has different coordinates, then edit the textboxes with the values to use for the channels belonging to that sensor. 
     414 1. Emplacement depth: Positive downward value in meters. Defaults to 0. 
    422415 
    423416 
     
    425418 
    426419 
    427 3. !Sensor/Logger swap 
    428  
     420==== 3. !Sensor/Logger Swap ==== 
     421  
    429422 
    430423This action is used when: 
    431 1. A sensor currently installed at the station is swapped out with another sensor that is currently in the inventory.  The new sensor may be of a different model than the old one.  
    432 2. A logger currently installed at the station is swapped out with another sensor that is currently in the inventory. The new logger may be of a different model than the old one. 
    433 Limitation: You cannot use the Swap action to replace an accelerometer with a velocity-transducer or barometer (or vice versa). The new sensor must be of the same category (i.e. an Accelerometer is swapped for another, a Velocity-Transducer is swapped for another).  
     424 * A sensor currently installed at the station is swapped out with another sensor that is currently in the inventory.  The new sensor may be of a different model than the old one.  
     425 * A logger currently installed at the station is swapped out with another sensor that is currently in the inventory. The new logger may be of a different model than the old one. 
     426Limitation: You cannot use the Swap action to replace an accelerometer with a velocity-transducer or barometer (or vice versa). The new sensor must be of the same category (i.e., an Accelerometer is swapped for another, a Velocity-Transducer is swapped for another).  
    434427 
    435428 
    436429From the Station Summary page, Click on the ‘Update Station Instruments’ link in the User links module. 
    437430 
    438 1. From the Action menu of the instrument to be replaced, select the ‘Swap’ option.  Enter the GMT datetime of the swap action and click Continue. 
    439 2. The next step is to select the new instrument from the inventory.  Select the model and serialnumber of the new instrument and submit the form to update the database.   
    440 1. Only instruments having inventory status=INVENTORY appear in the dropdown. 
    441 1. At this time, the following database changes are made: 
    442 1. The channel epochs belonging to the old instrument are ended (their offdate is set to the swap date). 
    443 2. New active channel epochs are created whose ondate is equal to the swap date. Their response stages use the new instrument’s response. 
    444 1. The old instrument’s inventory status is set to INVENTORY. 
    445 2. The new instrument’s inventory status is set to INSTALLED. 
     431 1. From the Action menu of the instrument to be replaced, select the ‘Swap’ option.  Enter the GMT datetime of the swap action and click Continue. 
     432 1. The next step is to select the new instrument from the inventory.  Select the model and serialnumber of the new instrument and submit the form to update the database.   
     433    a. Only instruments having inventory status=INVENTORY appear in the dropdown. 
     434 1. At this time, the following database changes are made: 
     435    a. The channel epochs belonging to the old instrument are ended (their offdate is set to the swap date). 
     436    a. New active channel epochs are created whose ondate is equal to the swap date. Their response stages use the new instrument’s response. 
     437 1. The old instrument’s inventory status is set to INVENTORY. 
     438 1. The new instrument’s inventory status is set to INSTALLED. 
    446439 
    447440 
     
    449442 
    450443 
    451 4. !Sensor/Logger temporary removal 
     444==== 4. !Sensor/Logger Temporary Removal ==== 
    452445 
    453446 
     
    458451Enter the GMT datetime of the removal and submit the form. At this time, the following database changes are made: 
    459452 
    460 1. The current active channel epochs belonging to the removed instrument are ended (their offdate is set to the removal date). 
    461 2. New active channel epochs are created whose ondate is the removal date, with a flag indicating that they have no instrument gain for this epoch. 
    462 3. The removed instrument’s inventory status is set to REPAIR. 
     453 1. The current active channel epochs belonging to the removed instrument are ended (their offdate is set to the removal date). 
     454 1. New active channel epochs are created whose ondate is the removal date, with a flag indicating that they have no instrument gain for this epoch. 
     455 1. The removed instrument’s inventory status is set to REPAIR. 
    463456 
    464457 
     
    468461The channels belonging to the removed instrument appear in the Current Channels module, but with no gain for their current epoch.   
    469462 
    470 5. !Sensor/Logger reinstall 
     463==== 5. !Sensor/Logger Reinstall ==== 
    471464 
    472465 
     
    484477#!html 
    485478<p style="text-align: center"> 
    486 Figure 9. Update Station Instruments - select reinstall option 
     479Figure 9. Update Station Instruments - Select Reinstall option 
    487480</p> 
    488481}}} 
     
    491484Enter the GMT datetime of the re-install and submit the form. At this time, the following database changes are made: 
    492485 
    493 1. The current active channel epochs belonging to the instrument are ended (their offdate is set to the reinstall date).  Reminder: these channel epochs have no instrument gain. 
    494 2. New active channel epochs are created whose ondate is the reinstall date and their simplereponse is calculated. 
    495 3. The instrument’s inventory status is set to INSTALLED. 
     486 1. The current active channel epochs belonging to the instrument are ended (their offdate is set to the reinstall date).  Reminder: these channel epochs have no instrument gain. 
     487 1. New active channel epochs are created whose ondate is the reinstall date and their simplereponse is calculated. 
     488 1. The instrument’s inventory status is set to INSTALLED. 
    496489 
    497490 
     
    500493 
    501494 
    502 6. Sensor removal to end channels 
     495==== 6. Sensor Removal to End Channels ==== 
    503496 
    504497This action is used to permanently remove a sensor and set the offdate of the channels belonging to the sensor. 
     
    508501Enter the GMT datetime of the action and submit the form. At this time, the following database changes are made: 
    509502 
    510 1. The current active channel epochs belonging to the offlined sensor are ended (their offdate is set to the remove date). 
    511 2. The channel header offdate for each of those channels is ended (their offdate is set to the remove date) to indicate there will be no further epochs for this channel. 
     503 1. The current active channel epochs belonging to the offlined sensor are ended (their offdate is set to the remove date). 
     504 1. The channel header offdate for each of those channels is ended (their offdate is set to the remove date) to indicate there will be no further epochs for this channel. 
    512505 
    513506 
     
    515508The Current Channels module should no longer display the ended channels of the offlined sensor. However, the channel headers and their epochs still exist in the database, and can be modified via the Channel Manager. 
    516509 
    517 7. Terminate Station 
     510==== 7. Terminate Station ==== 
     511 
    518512From the Station Summary page, Click on the ‘Update Station Instruments’ link. 
    519513From the Station action dropdown menu: select the ‘Terminate Station’ option. 
    520514Enter the GMT datetime to use for the station offdate and submit the form. At this time, the following database changes are made: 
    521 1. Remove all instruments from the station and return them to the inventory 
    522 2. Set the offdate of all currently active channel epochs at the station to the submitted offdate 
    523 3. Set the channel header offdate of all currently active channels at the station to the submitted offdate. 
    524 4. Set the station header offdate to the submitted offdate. 
     515 
     516 * Remove all instruments from the station and return them to the inventory 
     517 * Set the offdate of all currently active channel epochs at the station to the submitted offdate 
     518 * Set the channel header offdate of all currently active channels at the station to the submitted offdate. 
     519 * Set the station header offdate to the submitted offdate. 
    525520 
    526521 
     
    540535#!html 
    541536<p style="text-align: center"> 
    542 Figure 10. !Station/Location  Log entry form 
     537Figure 10. !Station/Location  Log Entry Form 
    543538</p> 
    544539}}} 
     
    546541 
    547542Fill out the form and submit it to create a new log entry. If there are no errors, you are re-directed to the detail page of the entry.  For authenticated users, the detail page contains links to: 
    548 1. Edit the entry (return to the log entry form to edit the fields) 
    549 2. Delete the entry (it asks for confirmation before deleting the record) 
     543 * Edit the entry (return to the log entry form to edit the fields) 
     544 * Delete the entry (it asks for confirmation before deleting the record) 
    550545 
    551546 
     
    560555 
    561556Note the Tips section below the form on the page: 
    562 1. Location actions: 
    563 1. Install New: Install a new device. Select the devicetype and devicemodel to continue. 
    564 1. Device actions: 
    565 1. Swap: Swap the selected device with another of the same devicetype. 
    566 2. Uninstall: End the active installation epoch of the device on the specified offdate. The device will no longer be installed at this location. 
     557 * Location actions: 
     558    - Install New: Install a new device. Select the devicetype and devicemodel to continue. 
     559 * Device actions: 
     560    - Swap: Swap the selected device with another of the same devicetype. 
     561    - Uninstall: End the active installation epoch of the device on the specified offdate. The device will no longer be installed at this location. 
    567562 
    568563 
    569564Note: Devicetypes can be inventoriable (its devices are tracked by unique serialnumber) or non-inventoriable (its devices are not tracked by a unique serialnumber).  Since most POWER devicetypes are non-inventoriable, the examples shown here are for non-inventoriable power devices. 
    570565 
    571 1. Install a new device 
     566==== 1. Install a New Device ==== 
    572567 
    573568 
     
    583578#!html 
    584579<p style="text-align: center"> 
    585 Figure 11. Update current Power Devices: select action 
     580Figure 11. Update Current Power Devices: Select action 
    586581</p> 
    587582}}} 
     
    598593#!html 
    599594<p style="text-align: center"> 
    600 Figure 12. Update current Power Devices: install new device (charger) 
     595Figure 12. Update Current Power Devices: Install new device (charger) 
    601596</p> 
    602597}}} 
     
    605600Enter the values and submit the form. At this time, the following database changes are made: 
    606601 1. If the selected devicetype is: 
    607   a.  inventoriable (devices tracked by unique serialnumber): 
    608     * The device serialnumber selected by the user is identified in the inventory pool and its inventory status is set to INSTALLED. 
    609   b. non-inventoriable (devices are not tracked by unique serialnumber): 
    610    * A new device is automatically created in the database 
    611    * A new active installation epoch is created that links the device to the location.  The epoch’s ondate is the submitted install date.  
     602    a.  inventoriable (devices tracked by unique serialnumber): 
     603      i. The device serialnumber selected by the user is identified in the inventory pool and its inventory status is set to INSTALLED. 
     604    b. non-inventoriable (devices are not tracked by unique serialnumber): 
     605      i. A new device is automatically created in the database 
     606 1. A new active installation epoch is created that links the device to the location.  The epoch’s ondate is the submitted install date.  
    612607 
    613608 
     
    615610 
    616611 
    617 2. Swap a device 
    618  
    619  
    620 This is to swap a current power device with another of the same devicetype (e.g. one Charger for another). 
     612==== 2. Swap a Device ==== 
     613 
     614 
     615This is to swap a current power device with another of the same devicetype (e.g., one charger for another). 
    621616From the action menu of the device to be swapped, select the ‘Swap’ action. In this example, we select swap on the Charger installed in Part 1 above: 
    622617 
     
    626621#!html 
    627622<p style="text-align: center"> 
    628 Figure 13. Update current Power Devices: select Swap action 
     623Figure 13. Update Current Power Devices: Select Swap action 
    629624</p> 
    630625}}} 
     
    635630Note: the Swap action preserves the devicetype across the swap, but you can select another devicemodel for the new device. 
    636631Enter the values for the new device and submit the form. At this time, the following database changes are made: 
    637 1. The installation epoch belonging to the old device is ended (its offdate is set to the swap date). 
    638 2. If the devicetype is: 
    639 1. inventoriable:  
    640 1. The inventory status of the old device is set to INVENTORY. 
    641 2. The new device serialnumber is selected by the user and its inventory status is set to INSTALLED. 
    642 1. Non-inventoriable: 
    643 1. A new device is automatically created 
    644 1. A new active installation epoch is created that links the device to the location. The epoch’s ondate is the submitted swap date. 
     632 1. The installation epoch belonging to the old device is ended (its offdate is set to the swap date). 
     633 1. If the devicetype is: 
     634    a. inventoriable:  
     635      i. The inventory status of the old device is set to INVENTORY. 
     636      i. The new device serialnumber is selected by the user and its inventory status is set to INSTALLED. 
     637    a. Non-inventoriable: 
     638      i. A new device is automatically created 
     639 1. A new active installation epoch is created that links the device to the location. The epoch’s ondate is the submitted swap date. 
     640 
    645641If there are no errors in the above steps, you are re-directed back to the Summary page where you should see the new device in the Power devices module.  To swap another device, click the Update Power devices link and repeat the procedure. To view and correct the power installation epochs, refer to the [#PowerInstallations Power Installations] section in this document. 
    646642 
    647643 
    648 3. Remove a device 
     644==== 3. Remove a Device ==== 
    649645 
    650646 
     
    656652 
    657653 1. The installation epoch belonging to the device is ended (its offdate is set to the remove date). 
    658  2. If the devicetype is inventoriable: the removed device’s inventory status is set to INVENTORY. 
     654 1. If the devicetype is inventoriable: the removed device’s inventory status is set to INVENTORY. 
    659655 
    660656If there are no errors in the above steps, you are re-directed back to the Summary page. 
     
    671667Note: Devicetypes can be inventoriable (its devices are tracked by unique serialnumber) or non-inventoriable (its devices are not tracked by a unique serialnumber).  Since most Telemetry devicetypes are inventoriable, the examples shown here are for inventoriable telemetry devices. 
    672668 
    673 1. Install a new device 
     669==== 1. Install a New Device ==== 
    674670 
    675671 
     
    684680#!html 
    685681<p style="text-align: center"> 
    686 Figure 14. Update current Telemetry Devices: Select Install new 
     682Figure 14. Update Current Telemetry Devices: Select Install new 
    687683</p> 
    688684}}} 
     
    702698 
    703699Since the DIGITAL-RECORDER devicetype is inventoriable: 
    704 1. The available devices whose inventory status=INVENTORY of the selected devicemodel are displayed in the Serialnumber dropdown menu.   
    705 2. Select the serialnumber of the device to install from the Serialnumber dropdown menu 
     700 
     701 * The available devices whose inventory status=INVENTORY of the selected devicemodel are displayed in the Serialnumber dropdown menu.   
     702 * Select the serialnumber of the device to install from the Serialnumber dropdown menu 
    706703Submit the form. At this time the database is updated (refer to the database changes outlined in the section ‘Update Power Devices: Install new device’).  
     704 
    707705If there are no errors in the above steps, you are re-directed back to the Summary page where you should see the new device in the Telemetry devices module. To install another telemetry device, click the ‘Update Telemetry devices’ link and repeat the procedure. To view and correct the telemetry installation epochs, refer to the ‘Telemetry Installations’ section in this document. 
    708706 
    709707 
    710 2. Swap a device 
     708==== 2. Swap a Device ==== 
    711709 
    712710 
     
    726724Enter the GMT datetime of the swap (the swap date must be posterior to the device’s install date), and click Continue. The next step is to select the new device to be installed.  
    727725Note: the Swap action preserves the devicetype across the swap, but you can select another devicemodel for the new device. 
     726 
    728727Since the DIGITAL-RECORDER devicetype is inventoriable: 
    729 1. The available devices whose inventory status=INVENTORY of the selected devicemodel are displayed in the Serialnumber dropdown menu.   
    730 2. Select the serialnumber of the device to install from the Serialnumber dropdown menu 
     728 * The available devices whose inventory status=INVENTORY of the selected devicemodel are displayed in the Serialnumber dropdown menu.   
     729 * Select the serialnumber of the device to install from the Serialnumber dropdown menu 
    731730Submit the form. At this time the database is updated (refer to the database changes outlined in the section ‘Update Power Devices: Swap a device’).  
     731 
    732732If there are no errors in the above steps, you are re-directed back to the Summary page where you should see the new device in the Telemetry devices module. To swap another telemetry device, click the ‘Update Telemetry devices’ link and repeat the procedure. To view and correct the telemetry installation epochs, refer to the ‘Telemetry Installations’ section in this document. 
    733733 
    734 3. Remove a device 
     734==== 3. Remove a Device ==== 
    735735 
    736736 
     
    738738From the action menu of the device to be swapped, select the ‘Uninstall’ action. 
    739739Enter the GMT datetime of the removal (the removal date must be posterior to the device’s install date), and submit the form.  At this time, the following database changes are made: 
    740 1. The installation epoch belonging to the device is ended (its offdate is set to the remove date). 
    741 2. If the devicetype is inventoriable: the removed device’s inventory status is set to INVENTORY. 
     740 
     741 1. The installation epoch belonging to the device is ended (its offdate is set to the remove date). 
     742 1. If the devicetype is inventoriable: the removed device’s inventory status is set to INVENTORY. 
     743 
    742744If there are no errors in the above steps, you are re-directed back to the Summary page. 
    743745 
     
    768770Note: If you enter an offdate of 3000-01-01 (i.e. an active installation epoch), then this form is equivalent to using the Update Power Devices form to install a new power device. 
    769771Select the devicetype from the first dropdown menu, and then the devicemodel from the second dropdown menu.  (In this example, we select the Battery devicetype). 
     772 
    770773Enter the epoch ondatetime, and offdatetime in the accepted format, and click Continue. 
    771774 
     
    785788Since the Battery devicetype is non-inventoriable in SIS, the device serialnumber is optional. 
    786789Enter the values for the device and submit the form.  
     790 
    787791At this time, a new installation epoch is created that links the device to the location for the given ondate and offdate. 
    788792If there are no errors in the above steps, you are re-directed to the detail page of the newly created epoch. 
     
    808812 
    809813 
    810  
    811814Authenticated users see an ‘Edit’ link next to the fields of the installation epoch, and a link to delete the epoch.  Clicking on the Edit link of a field takes you to a form where you can edit the value, submit the form and be re-directed back to the detail page of the installation epoch. 
    812815