These notes are the outcome of the 2005 CTSP Conference that was held in
Reno, NV from March 15^th^ to the 17^th^. These notes are a
consolidation of the issues and possible solutions to situations that
CTSPs deal with while on incidents.

Items in RED below will reference Action Items that were taken or will
be taken to resolve an issue.

# Review of Draft CTSP Work Group Charter

A copy of the draft charter dated 17-Mar-2005 can be found on the
FireFYI website. The posted version reflects some changes talked about
in the following notes during the initial discussion. What follows is a
section by section discussion.

## Section I. Background {#section-i.-background .Style-Heading-2-+-Bold}

### Nothing of note was discussed.

## Section II. Name {#section-ii.-name .Style-Heading-2-+-Bold}

### Nothing of note was discussed.

## Section III. Authority {#section-iii.-authority .Style-Heading-2-+-Bold}

### Nothing of note was discussed.

## Section IV. Comments on Mission Statement {#section-iv.-comments-on-mission-statement .Style-Heading-2-+-Bold}

### Mission Statement should concur with the IRMWT.

### Include the words "operational" and "all-risk". Words added in appropriate places.

## Section V. Comments on Objective {#section-v.-comments-on-objective .Style-Heading-2-+-Bold}

### Does not use the word "training". Words added in appropriate places.

### Develop training/certification process bullet statement. Outside scope of Charter. This is one of the topics that was discussed at length and will fall under the Group responsibilities.

### Use wording from existing sources.

### Reference to FSH 5109.17 -- Fire and Aviation Management Qualifications Handbook, Chapter 20-Qualifications and Certification usually mirrors the NWCG 310-1. Even though the CTSP position exists, it is a technical specialist and currently does not have a Fire Qualification Guide (310-1). That would be the outcome of establishing a formal task book once the CTSP Work Group is sanctioned.

### Discussion on where does a CTSP live. Plans, Finance, Logistics or Staff. Will have a hard time selling this, but a unit position may be easier to sell. 

### Organizational chart for NWCG IRM Working Team can be found on their page: <http://www.nwcg.gov/teams/irmwt/irm.htm>

### Combine Mission statement and Objective into a Purpose statement. An example follows: This is not implemented in the current version of the Charter. Further discussion is needed to evaluate the pros & cons. 

> **PURPOSE**
>
> The purpose of the CTSPWG is to serve as an Advisory Group to the
> IRMWT to coordinate issues, analyze problems, and recommend solutions
> that affect the IT Specialist providing information technology support
> on wildland fire and all-risk incidents. The Group's goals will be (1)
> to align information technology with the operational and support needs
> on wildland fire and all-risk incidents, (2) efficiently and
> effectively standardize the roles and responsibilities that CTSPs use
> in wildland fire and all-risk incidents, and (3) develop
> recommendations that will be submitted to the IRMWT as priority issues
> that will have the greatest impact on the roles and responsibilities
> of the CTSP.
>
> To fully and effectively execute its assignment, the CTSPWG will:
>
> A. Develop recommended standard hardware infrastructure
>
> B. Collect and provide repository for common set of tools utilized by
> CTSPs
>
> C. Establish industry recommended security protocols that are accepted
> by both the IT industry as well as participating agencies
>
> D. Identify and document CTSP knowledge, skills and abilities
>
> E. Develop recommended guidelines for an acceptable level of CTSP
> proficiency
>
> F. Research and recommend new and emerging technologies
>
> G. Operate and maintain CTSP discussion board
>
> H Identify and recommend training requirements

## Section VI. Comments on Organization {#section-vi.-comments-on-organization .Style-Heading-2-+-Bold}

### We desire to represent ourselves and our recommendations to the IRMWT. We do not necessarily want the IRMWT representative assigned in an overview capacity to carry our business back to the IRMWT. Louis Leezer to do further research.

## Section VII. Comments on Membership {#section-vii.-comments-on-membership .Style-Heading-2-+-Bold}

### This section needed the most rework and contained the most discussion. The final solution was to bump voting members to 9 such that all agencies that were listed could be represented (but may or may not choose to participate). The addition of state agencies necessitated the bump to 9.

### Clarify "regional State representatives." 

### Hold team member at a maximum of 7.....i.e. use an odd number. See text in point number 1.

### Discussion about composition of group and what agencies to include. There needs to be some way of appointing and re-appointing so that the charter continuity is not affected. Use staggered appointment/re-appointment. Not specifically addressed in current version, but understood that staggering is required to allow for continuity. If needed in the future, Charter can be amended.

### Term limits not inherent. Term limits added.

### Individuals may attend the meetings but may not have voting privileges.

### Reword VII D. Section D pertained to members having influence within their respective agencies. After much discussion, D was removed.

### Need a direct path to talk to Barrowcliff, and other agency specific personnel. Members need to be able to by-pass chain of command to discuss Group business

## Section VIII. Comments on Team Chair Authorities and Responsibilities {#section-viii.-comments-on-team-chair-authorities-and-responsibilities .Style-Heading-2-+-Bold}

### Change "Chairman" to "Chair" Done.

### Put wording in to specify membership composition. If NWCG IRMWT doesn't want us to nominate our board, they will take it away. Method of obtaining Group membership still needs some discussion. Consensus is that many of the Group members will be drafted from active CTSPs who are interested in these proceedings.

### Goal of membership is to keep it small, but to also give broadest representation.

## Section IX. Comments on Meeting and Reports {#section-ix.-comments-on-meeting-and-reports .Style-Heading-2-+-Bold}

### Quorum would be a fixed number rather than 2/3. Quorum remains at 2/3 of membership list.

### Virtual participation is an option. We are computer wizards, we can do this virtually. Right?

### Don't tighten the quorum requirement so that you can't conduct business.

# Task Book Discussion

A task book will be a natural outcome of the chartering process. This
may require a second task group to handle the training and certification
process.

# CTSP Manual Discussion

## Review {#review .Style-Heading-2-+-Bold}

### Reviewed TOC of CTSP Manual dated March 2001 

### Manual will be available on the FireFYI site. 

## Brainstorming of CTSP Knowledge {#brainstorming-of-ctsp-knowledge .Style-Heading-2-+-Bold}

The following list is the result of some brainstorming that occurred as
to the scope and nature of the duties a CTSP performs. The basis of the
exercise is to begin documenting the areas that may need to be looked at
for possible knowledge, skills, and abilities.

### Fire / Incident

#### Knowledge of Fire/Incident Business Practices

#### ICS System (I-100; I-200) (<http://www.nwcg.gov/pms/forms/ics_cours/ics_courses.htm>) 

#### Mobilization

#### Transitioning incident to another team

#### Incident procurement practices

#### Demobiliztion of equipment

### Windows 2000/XP

#### Creating and using an incident/team computer image (See Section X. Part F for further details)

#### Installing software

#### Installing, configuring, maintaining Norton/Symantec/McAfee antivirus

#### Firewall administration

### I-Suite (Incident Automation Database)

#### Setup of Admin Tools

#### Adding an Incident

#### Attaching a database

#### Importing data from ROSS (See Section VII)

#### Maintaining current backups of incident data, including I-Suite

#### Database repository

#### Merge/Split

#### Contacting Helpdesk/Support

#### Access database knowledge

#### Report writing/SQL

### Networking

#### Setup ID, subnet mask, gateway, DNS

#### Using switches and hubs and wiring

#### Configuration and use of router

#### Using DHCP or static IP addresses

#### Security

#### WAN/LAN Issues

#### VPN Client

#### Wireless networking

#### Network cable building

### Printers

#### Network IP or shared workstation

#### Maintenance

### Miscellaneous

#### Posting IAP's

#### Website creation and maintenance

#### FTP use

#### Internet connectivity

#### 209 submission

#### Physical hardware security

#### Software support

#### MS Office

#### Adobe Acrobat

#### Dreamweaver

#### GPS

#### Support of other electronic devices

### New and Emerging Technologies

#### Voice over IP

# ISO Group, CTSPs, and Fire Assignments

## Mike Fields and Angela Chavez attended as representatives from the Information Solutions Organization (ISO) Group. 

## Mike summarized history of A-76 and application to IT. FS won competition. ISO and CGA (Continued Government Activities) are the "new" Forest Service IRM group.

## Mike outlined the current organization chart for the ISO and its sister branch, the CGA.

## In 2005, the ISO is committed to supporting Fire/All-Risk incidents

## A desire was expressed to develop a set of basic skills so that the ISO can be available for Fire/All-Risk support.

## A shift of IRM thinking to Fire.

## They will support fire with a structured organization while providing continued support on the home front. 

## **Q**: Team position CTSP works with hardware and software. Is the ISO planning to provide adequate training in the software used by Incidents? **A**: Yes. We want to do it on an economic basis. Must have a contingency plan to cover home base when one is sent out.

## There was much discussion and education that occurred in both directions. As the CTSP effort grows and develops, it will need to work with the ISO to make sure that needs are met in both directions.

# Incident Business Automation - Phase 1 (I-Suite Stabilization)

## 2004 Accomplishments {#accomplishments .Style-Heading-2-+-Bold}

### Establishment & implementation of data repository

#### To be posted at transition

#### To be posted at the end of an incident

### Implementation of a new Website

#### More intuitive

#### Reorganized

### Standardization of training sessions and materials

#### Based on NWCG format

#### 4 sessions in 2004

#### 5 sessions planned in 2005

### Incorporation of interagency subject matter experts (SMEs)

#### BIA

#### 2 State people

#### BLM

#### Coast Guard (All-Risk)

### Three national business requirements training sessions.

### Data import capability from ROSS (Discussed later)

### ROSS Request Numbering system incorporated

### Changed save method to improve stability and data integrity

### Added mandatory fields

### Eliminated R & R data and added mobilization date and length of assignment field

## 2004 Accomplishments -- ITS {#accomplishments-its .Style-Heading-2-+-Bold}

### Ability to create partial pay OF-286 documents

### Unique invoice numbers system generated

### Printing improved

## 2004 Accomplishments -- IAP {#accomplishments-iap .Style-Heading-2-+-Bold}

### Spell check added

### Worked at improving print methods (not one of the prouder accomplishments)

### Added enhancements to the 204 to improve the appearance

### Worked with 209 committee to make improvements to the 209 report

## 2004 Accomplishments -- ICARS {#accomplishments-icars .Style-Heading-2-+-Bold}

### Allow editing of per unit costs

### Fix issues

## 2005 Limited Release {#limited-release .Style-Heading-2-+-Bold}

### A limited release version is currently being tested and will be released before Fire Season.

### 288 partial pay

### Bug fixes

### Minor 288 form changes

### Data entry enhancements in ITS

### Fax 288 from application

### Print 209 properly

### Have an "override" accounting code for obligations

### 204 will show trainees as such

### IAP consistency related items

## 2006 Release {#release .Style-Heading-2-+-Bold}

> We were given a glimpse of a beta version of the 2006 I-Suite release

### Bar Code/Smart Code Technology

### Supply Module

### Enhanced Demob functionality

### Redesign database structure 

### Application look more seamless; the 4 individual applications have been merged into one application, more user friendly

### Enhanced Admin Tool 

### User level security. Individual user accounts in I-Suite which will restrict access to specified modules 

### Import tools for IQCS, Radio Frequencies, AD Rates

### User Help Module

### Establish Data Warehouse

### Establish O & M process

## Questions on I-Suite? {#questions-on-i-suite .Style-Heading-2-+-Bold}

### Q: Will data in the repository be sufficient information for legal actions? A: SSN and EIN are removed from the database. Official data, resides at the agency in charge of the incident.

### Adding Fax capability has the advantages of only needing a person's phone number

### Q: Release date for I-Suite 2005? A: Beta test in April and release by the end of May.

# Incident Based Automation - Phase 2

## Review of accomplishments in 2004 {#review-of-accomplishments-in-2004 .Style-Heading-2-+-Bold}

### NWCG approved scope of Incident Business areas to be analyzed

### Advertised and hired sunset project manager Dorothy Albright

### Awarded contract to SAIC

## Overview {#overview .Style-Heading-2-+-Bold}

### Evaluate all incident support processes

#### What's working great

#### What processes should be changed

#### What automated tools should be changed/integrated

### Goal is to identify areas of efficiency, encourage consistency, and ensure ease of use

### Deliver final, validated report by early CY06

### Coordinate with FS IBP long term strategic project

## Near Term {#near-term .Style-Heading-2-+-Bold}

### Contractor to deliver proposal of interview question, process

### Currently developing the "as is" infrastructure, automation and documented processes

### Meeting with the FS IBP contractor next week to begin coordination/collaboration.

### Establishing a Website for info sharing/contact us

### Developing communication process

### Anticipate beginning interviews within next several weeks -- payment centers, other static locations.

# ROSS Import to I-Suite

Donna Tate went through a sample import form ROSS using the instructions
found at: <http://isuite.nwcg.gov/Documentation/ROSS_Import_Guide.pdf>.
It is straightforward.

# National Data Repository

## There exists an I-Suite database repository. Access it through the I-Suite Website ([http://isuite.nwcg.gov](http://isuite.nwcg.gov/)) 

## Username/Password protected site using DMS account and password credentials

## Databases will be posted at team transitions and at end of incident

# InciWeb

## Addresses {#addresses .Style-Heading-2-+-Bold}

### <http://www.fs.fed.us/fire/incidents/>

### [http://www.inciweb.org](http://www.inciweb.org/)

## Objectives: {#objectives .Style-Heading-2-+-Bold}

### A comprehensive form based incident template that entails minimal production

### An efficient way to post pertinent incident information -- Internet based

### Information based on most current ICS 209 to provide consistency

### Website in place quickly and cleanly

### Hosting unit can maintain the site or delegate this task

### Searching and archiving capabilities

### Ftp site for storing and sharing of incident information within the fire community.

### Forest level delegates the authority and is keeper of the keys.

### Delegation of Authority manages whether or not this is used by team or unit

### Manages public information.

### In beta for FS Regions 1, 4, and 5 for 2005 Fire Season

### Place for IAP's and 209s to be downloaded.

## Issues  {#issues .Style-Heading-2-+-Bold}

### There is already an interagency incident ftp site setup for both GIS information as well as other incident data: <ftp://ftp.fire.blm.gov/> 

### Duplication of effort with <http://wildfires.nifc.gov/>

### InciWeb needs new home to further develop in some areas

### If the main parties involved in these issues could pool their resources, a solid national interagency tool could be successfully developed and used.

## Contact  {#contact .Style-Heading-2-+-Bold}

### Carolyn Higgins (<chiggins@fs.fed.us>) for more information

### Jon Holden (<jholden@fs.fed.us>) for access to a training profile 

# Database Tools, Tips, Tricks

The topics outlined below are tools that have been developed or utilized
by individuals. In several cases, the functionality utilizes the data
found in the I-Suite databases, but is neither specifically endorsed nor
supported by I-Suite. They do provide expanded capability and you will
need to contact the responsible party or post directly to
http:/www.firefyi.com questions that you may have concerning an item.

## [I-Tools]{.underline} -- Runs in Microsoft Access (Carl Beyerhelm) {#i-tools-runs-in-microsoft-access-carl-beyerhelm .Style-Heading-2-+-Bold}

### MS Access application that runs against the I-Suite database

### Demob Planner

### Reports from I-Suite

### Ties into I-Supply during checkout process

### Can be found at [http://www.firefyi.com](http://www.firefyi.com/)

## [I-Supply]{.underline} - A Supply Module (Carl Beyerhelm) {#i-supply---a-supply-module-carl-beyerhelm .Style-Heading-2-+-Bold}

### MS Access application that runs against the I-Suite database

### Issues and Returns

### Receiving, Returns To Service and Adjustments -- Inventory

### Reports

### Will be posted to [http://www.firefyi.com](http://www.firefyi.com/) after some further testing

## [Visual CE]{.underline} -- by syware.com {#visual-ce-by-syware.com .Style-Heading-2-+-Bold}

### <http://www.syware.com/prodlib/win_ce/vce/vce.htm>

### Pocket PC Controller -- skins for displaying what's on the iPAQ 

### I-Supply module for a portable handheld, 

### Synchronize data with laptop or workstation

## Incident Performance Evaluation Application (Brian Lamb) {#incident-performance-evaluation-application-brian-lamb .Style-Heading-2-+-Bold}

### MS Access application that runs against the I-Suite database

### For Teams that require an evaluation, this will automate the process to a series of clicks and a print.

### Can be customized to have unique duties for different positions

## Schedule Backups {#schedule-backups .Style-Heading-2-+-Bold}

### Application: System Scheduler

### Can be used to make unattended, automated I-Suite backups

### Negated by 2005 release of I-Suite, but application is useful for other system steps

### Information can be found on [http://www.firefyi.com](http://www.firefyi.com/) 

## Process to Re-Image Team Computers {#process-to-re-image-team-computers .Style-Heading-2-+-Bold}

> Some teams are using Norton Ghost (or similar product) to create disk
> images of like systems to be able to rapidly rebuild & or restore a
> computer to a known condition. It can be preloaded with all the
> applications that a user might need to use while on an assignment.
> What follows is a general synopsis of the Norton Ghost process. These
> directions may vary from version to version, but the overall steps are
> fairly similar.

### Ghost Imaging Upload Process

#### Setup and configure a computer with the image you want to duplicate (client)

#### Run Ghost Server application on a second computer (server) and configure for an upload

#### The client and server are connected via a network switch. It is best if this is performed in a stand alone network to avoid impacting your office network.

#### Optional: Run Microsoft's SysPrep ([http://www.microsoft.com](http://www.microsoft.com/) -- search for SysPrep for the correct platform). This utility will reset the image such that upon reboot you can change the hostname. SysPrep will shutdown the computer automatically upon completion.

#### Reboot client with a Ghost floppy. Client will then upload a disk image to the server as a file much like a zip archive.

#### Image size will vary, but expect about 1.5 GB depending on software you have installed (I-Suite; MS Office; Norton Anti-Virus)

### Ghost Imaging Download Process

#### Connect multiple laptops to standalone network. 

#### Boot from Ghost floppy

#### Each client locates Ghost server to receive image.

#### Once all clients are connected, commence simultaneous image download

#### Repeat this process until all computers are re-imaged.

### Doug Wagner reports issues trying to re-image more than 4 machines at a time. Brian Lamb has done as many as 12 with no problems. May be dependent on the version of the software.

### Requires a licensed copy of Norton Ghost for each machine. Check EULA.

### Can use static IP addresses or DHCP

### Takes about 15 minutes to re-image a machine.

## Anti-Virus Update Tip for machines on local network {#anti-virus-update-tip-for-machines-on-local-network .Style-Heading-2-+-Bold}

### Put the update file on a CD or laptop server

### Point all other machines on the network to the laptop server to update; this will save bandwidth on incident

## Fire ISP {#fire-isp .Style-Heading-2-+-Bold}

There is tentative work being done to establish a Fire ISP. NIFC has
agreed to look and see if this is a viable project.

###  {#section .unnumbered}