CAL FIRE could benefit from the NIFC EGP portal approach and/or use of the EGP portal itself

"Although inherently regional in activities, a department-wide approach to data management will benefit all"

"Program areas have opportunity to correlate/analyze data in new, informative ways (e.g. how do DSpace efforts impact DINS outcomes)"

CAL FIRE has opportunities to improve fire protection through partnerships with modelers

Opportunity to increase use of modeling and automation tools to improve data management/analysis processes

CAL FIRE can use public-facing maps to show the public how it is performing its mission

"CAL FIRE is involved in several innovative multi-sensor, near real-time model / prediction applications (e.g., WiFire)"

"CAL FIRE activities (training, community engagement, urban forestry, GHG changes, etc.) would be very useful to see in map form"

Non-GIS staff want to be autonomous users of GIS to answer common questions

The transition from PAPER / SIMPLE DIGITAL to GIS offers new ways to work

"CAL FIRE ""public customers"" (e.g., grant applicants) could use a GIS interface to determine programs for which they may be eligible"

Geospatial interface(s) can enable pre-field screening and investigation in many business areas

Predictive modeling would be enormously valuable

Opportunity to improve consistency/amount of natural resource data and benefit biologists and foresters down the road.

No resistance once adopted - �starving� for more gis integration

CAL FIRE has program areas with strong visions for a geospatially integrated work environment

Opportunity to use web mapping tools as platform for improved collaboration/information sharing with local governments

"Many important uses for desktop GIS applications (e.g., inspection pre-planning)"

"Many important uses for field-mobile applications (e.g., inspection)"

Risk modeling would be of great value

Well-designed and implemented geospatial tools can assist field staff in meeting workload rather than adding more work

"CAL FIRE could pre-build worst-case models for fire response throughout state, saving time when there are fire starts (cf. FDOP)"

"Some program areas have clear vision of geospatial information needs, though they may not be meeting those needs yet"

"GIS is the ""killer application"" for CAL FIRE if deployed well"

CAL FIRE has pockets of strong local collaboration (e.g. SLO) to serve as models for other regions

CAL FIRE has strong vision for using real-time data in incident response for true situational awareness

Tremendous amount of GIS usage/skill in Forest Practice

Long history of GIS usage within FRAP; Integrated with many program workflows

CalMAPPER serving as useful tool for tracking fuel and fire hazard reduction information.

CAL FIRE PIMS application works well and has a geospatial component to it

Long history of GIS usage; Strong awareness of GIS capabilities

"Units are taking advantage of GIS for pre-creating response plans (pre-attack), work planning, and focus areas for fuel and hazard reduction"

Risk of information saturation if data is not curated and presented with context to those in field

Inefficient workflows create a backlog of field work and deter full distribution of grant money

"If GIS is not deployed, validated and supported properly, puts lives at risk"

Lack of validation workflows for near-real time information impacts public safety

"Perceived risk of ""hacking"" public information (e.g. altering evacuation routes) causing additional risk, confusion, loss of trust"

No plan in place for leveraging emerging technologies (e.g. on site remote sensing data capture/processing)

"Uncertain access to real-time, validated geospatial information from jurisdictions. Unable to answer all questions from public, Governor's office."

Lack of access to current parcel data

"Current geospatial information relies on addresses not x-y locations (40k state properties, 40k other buildings)"

Program lacks a comprehensive geospatial dataset for properties it inspects

GIS users are lack confidence in enterprise data back-up procedures. Fearful of losing data.

Base reference data used in fire response is typically a year old (distributed via hard drive)

"Data is being collected/stored in proprietary platform, reducing interoperability with non-Esri plaforms"

Hard to work with sensitive / confidential data in a shared enterprise library structure

Challenged by connectivity and management of hard drives. Need more frequently updated data to be shared with everyone.

Current workflows for incorporating field-collected data and distributing data via hard-drive are too slow.

Geospatial information standards are not well-defined (at least in some program areas)

"Lack of an integrated, enterprise, up-to-date, geospatial library hinders task performance (e.g., burn planning needs several current datasets)"

CAL FIRE needs a Common Operating Picture platform but does not have one

CAL FIRE is losing important mission-critical learning by not being able to do pre and post-fire analyses routinely.

"CAL FIRE accomplishments (grants) are not easy to track geographically, useful for many reasons"

Business needs of program areas may not be expressed in a way that GIS users can operationalize

Program areas are sometimes not aware that they have (or could have) GIS data of use to others

CAL FIRE does not require grantees to submit standardized GIS data as part of grant application or reporting

"New grant application and tracking software does not incorporate GIS in submittal, reporting, or data management"

"No process in place for rapidly collecting, collating, disseminating information to meet both public and internal information needs"

Data collection loop is left open as excavator does not record/report back findings

Lack of policies on data sharing inhibit workflows

No case management system in place

"GIS management (users, application requests, etc.) is largely a PAPER process"

"Lack of workflow and standards that generate high-quality GIS data essential to general mission of CAL FIRE (e.g., perimters, ignition points)"

CAL FIRE lacks an infrastructure plan for separating data editing from data publishing

"Antiquated process for integrating weather data with CAD and ICC, slowing appropriate response actions"

Lack of standardized data management practices among local ECCs

Paper methods are still being used where electronic tools are already available

Pertinent data is tracked/collected in various systems inside and outside of CAL FIRE; No agency has a true statewide view of resources/conditions

Lack of field-mobile mapping technology creates redundant mapping efforts

Many actions that create geospatial data have no workflow for the actor to verify the geospatial data (it is left to the GIS person)

Data entry in stand-alone application makes it necessary to enter data two times or more

Data has to be created two or three times in current work processes

Inspection Assistant (federal system) is isolated from CAL FIRE systems and use of its data is problematic

Pipeline spatial data come from external sources and is of variable or unknown quality

"Time-critical geospatial data (CAD data, radio traffic on fire locations, etc.) are handled through manual processes"

CAL FIRE does not have an NSDI-like list of framework layers for the entire department (foundational spatial datasets)

GIS datasets are stored may not be part of enterprise backup or discovery because they are stored on local drives

"Information sources, services sources, are difficult to identify or find"

Users find it difficult to tell whether datasets are up to date or most authoritative

Lack of guidance for collecting/developing standardized geospatial data within program

Authoritative data from partners varies over time and partner personnel

Difficult to evaluate quality and suitability of data from external sources

"Lack of protocol for archiving project data sources along with project outcomes (for future reference, legal challenge, etc.)"

CAL FIRE has no standardized tool(s) for cataloguing GIS datasets within program areas

"""Enterprise data"" lacks a formal definition as a concept within CAL FIRE"

"Incident mapping methods and standards are standardized by informal, ad hoc, group"

Lack of access to CAD data

Greater adoption of Portal for ArcGIS will alleviate some demand for AGOL licenses

USFS has implemented major enterprise that can serve as model for CAL FIRE.

The proliferation of non-standard devices and applications will potentially cause confusion or misinformation during incident

Reliance on large number of AGOL licenses from NIFC could be a weakpoint if federal license lending policy changes

Lack of 24/7 support for tools (CAL FIRE and vendor support)

GIS in remote areas hindered by lack of connectivity

Infrastructure and worflows are not in place to support real-time information sharing during events

The current model of using AGOL for quick online maps will require ever-increasing number of licenses to meet demand; Lack of scalability

Units responding to incidents have no means to get data updates when en route or during initial attack.

"Connectivity limits use of geospatial information when one cannot plan ahead and pack ""data to go"""

On-call GIS/IT support is lacking outside of standard work hours

Esri platform constrains integration with external systems

CAL FIRE does not have sufficient infrastructure to fully support Portal for ArcGIS implementation

"CAL FIRE has no clear strategy on mobile applications and platforms (e.g., Avenza and Collector and Drozen's ""all in one"")"

"Software version changes break custom tools, locking CAL FIRE in to old versions of software OR forcing abandonment of custom tools"

"Currently no access to ""test"" environment; Must rely on IT for testing of applications"

Data maintenance process requires Forest Practices to work outside of the Enterprise

"Forest Practices downloads FRAP data to own, local server in order to organize, store, manipulate for own purposes"

Remote Desktop use of GIS is not working well for some programs that are fairly heavy GIS users due to insufficient network connectivity

Hardware and storage for intensive data analysis and modeling is not available

Lack of currency with GIS software version creates issues

Potential for improved communication and info sharing with the public

The process of Enterprise GIS implementation should be well-publicized within CAL FIRE

An enterprise GIS will bring together resource management and fire protection data to the benefit of both

"Federal requirements can be a ""driver"" for enterprise GIS integration"

Formal governance can build policies and accountability for geospatial data and applications

"Domains of information that would be very useful in geospatial form have not been part of GIS thinking or planning (e.g., surveys)"

"CAL FIRE should look to practices in other states for good ideas on implementation and access (e.g., Texas, Maine, Nevada, Alaska)"

GIS could be very important to achieve many parts of the program's mission

"CAL FIRE and the Resources Agency share a common interest in managing GIS at an enterprise level through agency support (GIO, Data Scientist)"

CAL FIRE could be statewide leader in emergency response data management

CAL FIRE is looked upon as a statewide data manager by other agencies

"CAL FIRE could collaborate with key partners (e.g., USFS) on defining new, useful, geospatial datasets and tools (e.g., seed collection)"

On-line GIS applications are very useful and require little training

"Collaborators can be a key to successful information management, especially at the local level"

Expertise should be portable not isolated to single unit

"""Enterprise"" and ""Authoritative Data"" are somewhat new concepts in the department, so are opportunities to educate agency staff"

CAL FIRE is interested in practical innovation and willing to try new approaches

"Enterprise information management, including GIS, has high-level executive support"

Using other programs as GIS service centers and sources rather than starting from scratch within program

CAL FIRE GIS staff are adept at finding ways to implement and use GIS without much formal support from IT

Other program staff (DINS) have been helpful in supporting Fire & Life Safety

FRAP provides valuable GIS support to other programs

CAL FIRE is often not compliant with State IT rules and processes

Pockets of excellence in GIS create idiosyncratic applications that are not supportable by IT

"Executive awareness/support for standards is lacking, preventing their creation/enforcement"

"Lack of field-mobile mapping technology is a safety issue (e.g., dozer operations)"

CAL FIRE is far out of compliance with state standards concerning database and application development

Solutions that ignore or fail security standards will hurt enterprise use of GIS

"Resource Management and Fire Protection are seen as ""competing"" for GIS development focus"

Decisions about GIS or related data systems have been made without any input from people on the ground

Forest Practices staff spend a lot of time producing data (digitizing) across various permitting types (inefficient use of skilled staff)

"Inclusion of ""GIS"" in job description triggers costly reclassifications"

"Expanding GIS use at field level (e.g., in units) will put a huge load on PFEs"

"Fire response mission may pull staff away from routine, but essential, data management activities"

"In some programs, GIS workflows that support regular business needs are not yet established"

CAL FIRE has no GPS standards or equipment for programs that use field GPS

Confidentiality standards for sensitive data are not part of the GIS planning process

"GIS adoption, use, and activities at the unit level depend on unit leader preferences rather than CAL FIRE enterprise needs or goals"

GIS management and governance is currently a volunteer activity from program areas

The department may not have standards for data security (public vs. sensitive vs. confidential / legal requirements vs. right to know)

"""Can-do"" attitude creates solutin pockets but not long-term, supportable, solutions"

IT does not have GIS expertise allowing them to provide techical support to program areas

Lack of application development standards guide or structured review process before app goes public

"Proliferation of applications on different mobile devices creates confusion, inefficiencies"

"Battalion data collection efforts have no centralized storage location (e.g., for staging areas, water sources, helisports, ICP, etc.)"

CAD centerline data are variable in quality and completeness

CAL FIRE does not have a policy (including legal considerations) for managing/maintaining response data

CAL FIRE does not have a policy for establishing map standards for Units and Contract Counties

"CAL FIRE lacks a strategy for mobile GIS implementation, integration, data management"

"No current enterprise template for creating wildland pre-plans; often created ""on the fly"" in response to event"

External data collected multiple time by various CAL FIRE program areas for different purposes

GIS was not included in scope for Cal Trees; Missed opportunity

"Information sharing needs and workflows are not well-identified, causing duplication of effort"

Lack of plan/guidance on where to store large data sets of potential interest to entire enterprise (e.g. LiDAR data)

Requests for information are not documented as well as they should be making it difficult for staff to recreate process in future

"CAL FIRE lacks a comprehensive list of geospatial data reporting required by federal, state, local partners"

Enterprise applications have been developed without considering their geospatial data components

"Lack of clear direction from Department on incident mapping protocols leads to inefficient ""decision by committee"""

Lack of standardized SLA for GIS vendor services

Shared data drive update on annual basis is not sufficiently frequent (suggestion is to update from a centralized server throughout year)

IT does not screen enterprise application development proposals for geospatial components

The geospatial elements of standard CAL FIRE reports are not clearly defined in a single comprehensive list

CAL FIRE has no list of geospatial data products that must pass legal (as in lawsuit) scrutiny

"New technologies (e.g., Tablet Command) are implemented at the program level, not at the enterprise level"

"Progressive uses of GIS and geospatial at the unit level are ""one-offs"" with no solid plan to evaluate and propogate (if useful) to other units"

"State Forests lack a defined set of spatial reporting goals, data collection methods, and priorities"

"CAL FIRE does not use GIS for facility management, though this is a well-established benefit of GIS"

Users have difficulty determining how to get support including who to contact.

IT support and management for GIS is perceived to be lacking

"The department does not have a clearly defined ""ulitmate goal"" for GIS"

Personnel qualifications statements and duties don't align with actual day to day task requirements (i.e. GIS tasks not mentioned explicitly)

"SMEs with GIS skills end up supporting other SMEs without GIS skills, taking the GIS-skilled SME away from primary duties"

"Prefire engineers are used differently within the 21 units so that ""standard"" guidance or training for them is difficult or impossible"

"Lack consistent, local GIS expertise/support at the 21 Emergency Command Centers"

Staff has no time to innovate because of burdensome data maintenance processes

The S-341 training lacks a cadre leader within CAL FIRE

Growth and expansion in GIS use is limited by the current unit model of having a PFE be the expert

Program staff think they do not have enough programmer support

Risk modeling would require more training

"GIS skills used for job tasks are acquired ad hoc or brought individually to job, rather than either hiring criteria or outcome of actual training"

CAL FIRE foresters are not taking full advantage of tools to collect data more efficiently and maintain standards

"Lack of GIS technical expertise in program, have to rely on other programs"

Staff does not have time / job duties to become GIS experts

CAL FIRE misses opportunities to use geospatial data effectively by not having well-trained staff or pre-built products

Programs relying on staff with very little GIS training to perform critical GIS tasks.

Lack of consistent GIS support

Lack of GIS support