Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out
Get this document free

CIMS Fire Protection Enhancements Business Requirements.doc

VIEWS: 16 PAGES: 46

									.




    CIMS FIRE PROTECTION ENHANCEMENTS
    Business Requirements




    Client:          Ministry of Forests and Range
                     Compliance and Enforcement Branch
                            - on behalf of the -
                     Forest Protection Branch
    Date:            Jan. 4, 2006
    Revision:        1




                                                                   Vivid Solutions Inc.
                                                     Suite #1A, 2328 Government St.
                                                                 Victoria, BC V8T 5G5
                                                             Phone: (250) 385-6040
                                                                Fax: (250) 385-6046
                                                   Website: www.vividsolutions.com
Ministry of Forests and Range                                           CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                                   Business Requirements




                                    Document Change Control


Revision Number     Revision Date     Revised By      Description
1                   Jan. 4, 2006      Graham Parker   Original Draft
2                   Jan. 8, 2006      Graham Parker   Split into separate documents for CIMS and ERA




                                                                                             Page 2 of 46
 Ministry of Forests and Range                                                                  CIMS Fire Protection Enhancements
 Compliance and Enforcement Branch                                                                          Business Requirements



                                                      Table of Contents


1. INTRODUCTION ..................................................................................................................... 6

     1.1           PROJECT VISION...................................................................................................... 6
     1.2           MOTIVATING FACTORS .............................................................................................. 6
     1.3           PROJECT SCOPE ...................................................................................................... 6
     1.4           DELIVERABLES ........................................................................................................ 7

2. BACKGROUND ...................................................................................................................... 8

     2.1           PROCESS OVERVIEW ................................................................................................. 8
     2.2           GEOGRAPHICAL ORGANIZATION.................................................................................... 8
     2.3           FOREST PROTECTION BRANCH APPLICATIONS.................................................................... 9

3. DOCUMENT APPROACH ............................................................................................................ 10

     3.1           OVERVIEW............................................................................................................. 10
     3.2           REQUIREMENT NUMBERING ......................................................................................... 10

4. USER CLASSES ...................................................................................................................... 12


5. CONCEPTUAL MODEL .............................................................................................................. 13

     5.1           CONTEXT DIAGRAM .................................................................................................. 13
     5.2           RESTRICTIONS AND CONSTRAINTS ................................................................................. 13

6. COMMON REQUIREMENTS ......................................................................................................... ERROR! BOOKMAR

     6.1           DATA REQUIREMENTS ................................................................................................ ERROR! BOOKMAR
           6.1.1         GENERAL ........................................................................................................ 21

           6.1.2         SITES ............................................................................................................ 21

           6.1.3         CLIENTS ......................................................................................................... 23

     6.2           PERFORMANCE REQUIREMENTS .................................................................................... 15
     6.3           DATA CONVERSION................................................................................................... 16
     6.4           QUALITY ASSURANCE ................................................................................................ 17
     6.5           NON-FUNCTIONAL REQUIREMENTS................................................................................. 18

7. CIMS REQUIREMENTS .............................................................................................................. ERROR! BOOKMAR

     7.1           BUSINESS PROCESSES ................................................................................................ 19
           7.1.1         HOME MODULE ................................................................................................. 19

           7.1.2         INSPECTION & RISK ............................................................................................ 19

           7.1.3         CLIENT .......................................................................................................... 20


                                                                                                                           Page 3 of 46
 Ministry of Forests and Range                                                                   CIMS Fire Protection Enhancements
 Compliance and Enforcement Branch                                                                           Business Requirements

            7.1.4         SITE ............................................................................................................. 20

            7.1.5         EXCLUSIONS .................................................................................................... 20

     7.2            DATA REQUIREMENTS ................................................................................................ 21
            7.2.1         INSPECTION & RISK ............................................................................................ 21

            7.2.2         CLIENT .......................................................................................................... 24

            7.2.3         SITE ............................................................................................................. 24

            7.2.4         EXCLUSIONS .................................................................................................... 25

     7.3            USER REQUIREMENTS ................................................................................................ 26
     7.4            FUNCTIONAL REQUIREMENTS ....................................................................................... 27
            7.4.1         ALL MODULES AND MENUS.................................................................................... 27

            7.4.2         HOME MODULE ................................................................................................. 27

            7.4.3         INSPECTION .................................................................................................... 28

            7.4.4         CLIENT .......................................................................................................... 33

            7.4.5         SITE ............................................................................................................. 33

            7.4.6         EXCLUSIONS .................................................................................................... 33

     7.5            REPORTING REQUIREMENTS ........................................................................................ 34
            7.5.1         REPORT INVOCATION SCREENS .............................................................................. 34

            7.5.2         CORE REPORTS................................................................................................. 35

            7.5.3         NEW REPORTS.................................................................................................. 36

     7.6            SECURITY REQUIREMENTS........................................................................................... 37
            7.6.1         ALL MODULES .................................................................................................. 37

            7.6.2         HOME MODULE ................................................................................................. 37

            7.6.3         INSPECTION .................................................................................................... 37

            7.6.4         REPORTS ........................................................................................................ 37

            7.6.5         EXCLUSIONS .................................................................................................... 37


8. RISK SUMMARY ..................................................................................................................... 38


9. OUTSTANDING ISSUES ............................................................................................................. 39


10. APPENDIX A – REFERENCES ...................................................................................................... 41

     10.1           APPLICABLE LEGISLATION........................................................................................... 41
     10.2           INSPECTION REASONS ............................................................................................... 41
     10.3           CIMS WELCOME SCREEN HYPERLINKS .............................................................................. 41
     10.4           GENERAL REQUIREMENTS ........................................................................................... 41
     10.5           FIELD NOTICES ....................................................................................................... 41


                                                                                                                            Page 4 of 46
 Ministry of Forests and Range                                                                CIMS Fire Protection Enhancements
 Compliance and Enforcement Branch                                                                        Business Requirements

     10.6        INSPECTION RISKS .................................................................................................... 41
     10.7        REHABILITATION ASSESSMENT ...................................................................................... 41
     10.8        FIRE HAZARD ASSESSMENT .......................................................................................... 41
     10.9        FIRE ZONE CODES .................................................................................................... 42

11. APPENDIX B – SCREEN PROTOTYPES ............................................................................................ 43

            11.1.1     CIMS-000 ........................................................................................................ 43

            11.1.2     CIMS-101 ........................................................................................................ 44

            11.1.3     CIMS-157 ........................................................................................................ 45


12. DOCUMENT SIGN-OFF ............................................................................................................ 46




                                                                                                                        Page 5 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements



1. INTRODUCTION


1.1 PROJECT VISION
The Compliance and Enforcement branch has been directed to adapt both the Compliance
Information Management System (CIMS) and Enforcement Review and Appeals (ERA)
applications to include information that is relevant to the locating and prosecution of fire
abatements and resulting fires, as managed by the Forest Protection Branch of the Ministry
of Forests and Range (MOFR).

This document will describe the modifications and enhancements as they were approved, as
well as identify any issues that may affect their behaviour, prior to actual implementation.


1.2 MOTIVATING FACTORS
The changes proposed herein are intended to consolidate the Forest Protection Branch‟s
inspection data with existing CIMS inspections and track prosecution of Wildfire Act-related
offences within ERA. As the C&E Branch‟s existing systems already perform a multitude of
compliance and enforcement activities, adding new features to the applications (as opposed
to creating a new system) represents a significant cost and timesavings for the Forest
Protection Branch, which would otherwise need to pay to create similar systems for their
own use.

The modifications will benefit the Ministry of Forests and Range as a whole as inspection,
compliance and enforcement information from the branches become more uniform and
centrally reportable. Existing inspection and prosecution information housed by the Forest
Protection Branch‟s in-house applications may eventually be migrated to the CIMS and ERA
database repositories. During the course of development, any features that must be
implemented for the Forest Protection Branch that may also benefit the current users of
CIMS and ERA will be made available, increasing the general value of both applications.

As the C&E Branch has been advised that all core features described herein must be in place
(and in Production) in time for the upcoming fire season (generally stated to start on April
15, 2006), the implementation of many of these features are considered a high priority.


1.3 PROJECT SCOPE
Where details have not been included in the document, no implementation of a particular
feature can be assumed. Any such feature must be considered to be out of scope, unless it
is identified herein.

No external databases or files will be imported or converted as part of the project. The
application will however utilize existing CIMS code and data structures that are currently
present (as of the date of this document‟s release) in each respective application‟s
implementation.

No transition of the existing Forest Protection Branch application data (Fire Chart, etc) will
be required from the vendor.


                                                                                     Page 6 of 46
Ministry of Forests and Range                                      CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                              Business Requirements



Deliverables will not include updated help files and Crystal reports, but possibly will be
addressed at a later date. These will not be included in the initial production-ready
deliverable.

While it would be desirable to modify both CIMS to use and store geo-spatial information,
due to development time constraints, integration with Oracle Spatial, SDE or any other
spatial engines are currently out of scope.

All existing CIMS processes, coding conventions and standards will be respected by
modifications described within this document. Unless otherwise specified, all modifications
will utilize and adhere to the existing implementations of these systems.

It is the developer‟s obligation to provide an alternate working implementation, should any
described implementation be infeasible within technical, time and budget limitations. Should
such a situation arise, the Ministry will be immediately notified of all options that are
available, including scope reduction.


1.4 DELIVERABLES
At the conclusion of this project, the Ministry will expect the delivery of the following items:

   o   All source required files required to build and run the application on Ministry-defined
       infrastructure
   o   All source code and related files required to rebuild the application. This includes, but
       is not limited to Java, PL/SQL, Crystal Reports and static files.
   o   All technical documentation that is relevant to the design and implementation of the
       application, which was created for, or as a by-product of development. This includes
       requirements, design, installation scripts, test scripts, CRUD Matrices, help and
       support documentation.
   o   Any standards documentation or critical technical articles used during development,
       which are not easily identifiable through examination of the source code.




                                                                                       Page 7 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements



2. BACKGROUND


2.1 PROCESS OVERVIEW
The Forest Protection Branch performs Fire Hazard and Rehabilitation inspections, similar to
C&E inspections.

Following these inspections, should hazards be present, the branch will issue warnings to
the landowner (private or tenured), which indicates that they need to remove the hazard. At
this point, a re-inspection may occur, particularly if the site has a higher than average risk
associated with it. Usually however hazard inspections do not result in rehabilitation
inspections.

When a hazard that was identified has not been abated within a prescribed time, the
landowner will be issued a penalty or violation ticket.

After a fire has been discovered, it is tracked and dealt with using the branch‟s internal fire
tracking and Fire Chart applications. Fires are assigned a fire number, which includes the
Fire Centre, which is a designated region of British Columbia that is responsible for fighting
fires within its boundaries.

There two types of fires: ones for which a permit has been obtained (permitted fires) and
wild fires. Open fires are generally permitted fires. Permitted fires include prescribed burns
and other open (area) burning.

Once a fire has been identified, an investigation will take place on the site. If the
responsible party had a reasonable measure of control over the cause of the fire, the branch
has the authority to issue an invoice to the responsible party to recover the cost of fighting
the fire they were ultimately responsible for. This occurs after an OTBH has been held and a
contravention has been upheld. Policy 9.1 needs to be considered in response to these
investigations.


2.2 GEOGRAPHICAL ORGANIZ ATION
The Forest Protection Branch is administrated using a geographic break down of Fire
Centres, which contain Fire Zones. These are roughly analogous to C&E districts and zones.

 Coastal                            North West              Prince George
    Chilliwack                        Bulkley                Dawson Creek
    Mid-Coast                         Cassiar                Fort Nelson
    Port McNeil                       Nadina                 Fort St. James
    Squamish                          Skeena                 Fort St. John
    Sunshine Coast                                            Mackenzie
    Campbell River                                            Prince George
    South Island                                              Robson Valley
                                                               Vanderhoof


 South East                         Kamloops                Cariboo
    Arrow                             Clearwater             100 Mile House
    Boundary                          Kamloops               Chilcotin
    Columbia                          Lillooet               Horsefly


                                                                                     Page 8 of 46
Ministry of Forests and Range                                     CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                             Business Requirements

    Cranbrook                         Merritt                 Quesnel
    Invermere                         Penticton               Williams Lake
    Kootenay Lake                     Salmon Arm
                                       Vernon



There is currently no discrete mapping between Fire Centres/Zones and C&E
Region/Districts. As such, Protection cases and inspections can only be identified within the
Fire Zones and can not be broken out to Districts or rolled up into Regions for reporting and
data analysis purposes.


2.3 FOREST PROTEC TION BR ANCH APPLICATIONS
The Forest Protection Branch has indicated that it currently utilizes several other
applications during the course of daily operations. While no integration has been planned at
this time, the following systems have been identified for reference purposes:

Application Name           Purpose
Fire Chart                 Online geo-spatial mapping tool for viewing the status of fires.
                           Commonly referred to as the “Whiteboard”
Fire Tracking
FC Reports
FP_CAS                     Fire costing, prevention and suppression financials application
BC IMIS                    Inventory control




                                                                                      Page 9 of 46
Ministry of Forests and Range                                   CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                           Business Requirements



3. DOCUMENT APPROACH


3.1 OVERVIEW
The following approach will be taken to define the requirements, particularly in the
integration section of each application that is to be modified to meet the requirements
identified in this document.

  Business Processes
  In this section, we will list all business processes of the solution, describing the
  precedence of business activities within each process.

  Data Requirements
  This section describes the data to be collected, stored or processed in as much detail as
  possible.

  User Requirements
  This section describes the requirements from the user‟s point of view. Use cases are
  provided for some of the more critical processes.

  Functional Requirements
  This section deals with interaction of the users with the system and how it will how the
  system will enable users to accomplish tasks. This section lists the functions that the
  system must provide and the components that will be necessary.

  Reporting Requirements
  This section identifies reports and other output from the system.

  Performance Requirements
  In this section, we will state any performance requirements for specific use case and
  describe their rationale.

  Security Requirements
  In this section, we will describe any specific security infrastructure necessary to support
  the system.

  Non-Functional Requirements
  This section describes standards, regulations, etc. to which the system must conform.


3.2 REQUIREMENT NUMBERIN G
In order to ensure that all business requirements are succinctly identifiable and will be
addressed during implementation, where each requirement has been assigned a number
when identified as a unique requirement.

Requirement numbers can be identified by the use of greyed, square brackets (“[]”) with a
number in them. For example: [0019] indicates requirement number nineteen, of this
document only.



                                                                                   Page 10 of 46
Ministry of Forests and Range                                 CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                         Business Requirements

Generally all requirements will be preceded by their number. Any numbers that appear
amongst text are either a direct indication that the surrounding text is a requirement, or
may be related to the requirement number stated. In the latter case, the requirement will
be stated elsewhere in the document, in a more explicit manner.

Please note that requirements may be exclusionary, specifically noting that an activity or
feature must not be present in the resulting implementation.




                                                                                 Page 11 of 46
Ministry of Forests and Range                                 CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                         Business Requirements



4. USER CLASSES

The following existing roles will need to be “cloned” for Protection, to provide access to
protection-only related features. No existing permissions will be changed unless otherwise
stated.

      [?]Inspector (no planning, no scheduling access)
      [?]Viewer
      [?]Delegated Decision Makers

These roles will be renamed internally for use by Forest Protection Branch users; this
renaming will not be apparent to users however.

Additionally, Delegated Decision Makers (DDM) will be “pooled” from a common list for both
Fire Protection & C&E branches. No other users or roles have been defined at this time.

All permissions for the above roles will be defined in the following standard documents,
included in the CIMS application:

      CRUD Matrix.xls (generalized permissions)
      Security Matrix.xls (physical database grants)
      WebADE Matrix.xls (physical WebADE action associations)

The above documents are defined as part of the core CIMS application detailed design. For
the purposes of quality assurance, the security for each role has been identified as a
separate requirement.

While approximately 120 employees have been identified as candidate users for the
modifications, there is currently no breakdown for their assignment to the above roles[?].




                                                                                 Page 12 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements



5. CONCEPTUAL MODEL


5.1 CONTEXT DIAGRAM
       The following diagram depicts the new usage of Forest Protection Branch personnel,
       with respect to CIMS and ERA. It should be noted that while other external systems
       do interact with CIMS and ERA, they are not involved in enhancements that are
       defined in this document.




                                              C&E User


                              CIMS                                   ERA


                          C&E Inspection                           C&E Case



                           FP Inspection                           FP Case




                                              FP User


       C&E users will continue to have their current CIMS and ERA access and will have
       complete access to all new Forest Protection Branch inspections and cases.

       Forest Protection Branch users will have access to all Fire Abatement and
       Rehabilitation inspections only within CIMS, limited to their Fire Zones. They will
       have full access to ERA, for all cases that have been specified within their Fire Zones.


5.2 RESTRICTIONS A ND CON STRAINTS
       The following constraints and restrictions will be present during implementation and
       deployment of the enhancements.

       The application is currently dependant upon the following application and database
       software:

       Server
           Windows 2000 – Operating System
           JRun 4.1 - Java Servlet container


                                                                                    Page 13 of 46
Ministry of Forests and Range                                     CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                             Business Requirements

                 IIS 5.0 - Web Application Server
                 Oracle 10g – RDBMS

       Client
            Internet Explorer 5.5

       As such, both CIMS is limited by any restrictions imposed by the software in which
       they run, including any patches and drivers that have been applied to keep the
       primary software up to date.

       MOFR currently utilizes a custom migration utility to move applications into their
       Test, Train and Production environments. In tandem with its use, the application‟s
       source, compiled code and database are not normally directly accessible during
       development. Vivid Solutions currently provides a comparable environment to allow
       development to proceed in lieu of access to MOFR‟s environments.

       CIMS currently uses the Struts framework to provide a structured approach to the
       application and is therefore constrained by any limitations it may contain.

       The web component of each application is dependant on software libraries and
       components, as detailed below:

               webade-mof-custom-04_01_03.jar          ESFBaseAgent-02_00_00.jar
               webade-reporting-04_01_00.jar           esfbaseagent-02_01_01.jar
               webade-taglib-04_01_07.jar              jaxb-api-01_00_00.jar
               webade-taskmanager-04_01_00.jar         jaxb-libs-01_00_00.jar
               wsdl4j-01_05_01.jar                     jaxb-ri-01_00_00.jar
               activation-01_00_02.jar                 jaxrpc-01_01_00.jar
               aqapi-09_00_03.jar                      jts-01_07_02.jar
               axis-01_02_01.jar                       jtsio-01_07_02.jar
               castor-0.9.3.9.jar                      mail-01_03_03.jar
               classes12-09_02_00_04.jar               mx4j-02_00_00.jar
               commons-beanutils-01_07_00.jar          mx4j-remote-02_00_00.jar
               commons-collections-03_01_00.jar        mx4j-rimpl-02_00_00.jar
               commons-digester-01_07_00.jar           mx4j-tools-02_00_00.jar
               commons-discovery-00_00_02.jar          saaj-01_02_00.jar
               commons-fileupload-01_00_00.jar         spatialUtil-02_00_00.jar
               commons-httpclient-1.0.jar              struts-01_02_08.jar
               commons-lang-02_01_00.jar               webade-04_01_10.jar

       CIMS has been developed as a web based application and as such is dependant on
       the TCP/IP protocols. The application is therefore subject to all speed, security and
       guarantee of delivery issues inherent in the protocols.




                                                                                     Page 14 of 46
Ministry of Forests and Range                                CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                        Business Requirements



6. PERFORMANCE REQUIREMENTS

There are no new performance requirements involved in the implementation of these
requirements for CIMS. At this time, there are approximately 120 new users that will need
access to both applications. While this does represent a modest increase in the number of
users, as no processor-intensive tasks are to be implemented during development, there is
no significant performance degradation expected.




                                                                                Page 15 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements



7. DATA CONVERSION

The Forest Protection Branch has identified that it has at least two data repositories that
store some information both similar and useful for Fire Abatement and Rehabilitation
inspections:
       o Forest Protection Branch database (which initiates inspections)
       o Electronic (word) documents: including fire reports and inspection reports

While it is currently out of scope to perform any data conversion or application integration,
it has been noted that such activities are desirable to the branch, in order to streamline data
entry and consolidate existing data to increase their usability and value.




                                                                                    Page 16 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements



8. QUALITY ASSURANCE

All new and modified components of both CIMS will need to be both regression tested from
both a C&E and Forest Protection Branch perspective.

The following measures will be applied during development and testing to ensure both CIMS
and ERA are developed to the highest level of quality possible:

    1. All forms[?] and reports[?] will be spell checked via MS Word (or other utility) to
       ensure spelling is correct. The Canadian-English dictionary will be used.
    2. A formal test plan for the application will be developed[?], with respect to the
       development timelines and budget.
    3. A series of test scripts for the application will be developed[?], with respect to the
       development timelines and budget.
    4. The application will be periodically tested using JUnit[?] to ensure all Unit tests are
       functioning as expected.
    5. The application will be periodically integration-tested to ensure that all separately-
       developed modules function correctly together. As well, it will be tested to ensure
       that all interactions with external systems[?] will work as expected.

The application will be regression tested prior to release of all milestone builds[?] to ensure
that any new features added have not impacted previous coding.




                                                                                    Page 17 of 46
Ministry of Forests and Range                                 CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                         Business Requirements



9. NON-FUNCTIONAL REQUIREMENTS

Application documentation will be amended to reflect changes made to the application, as a
result of this item. This includes:
    Security documents:
        o CRUD Matrix.xls (generalized permissions)
        o Security Matrix.xls (physical database grants)
        o WebADE Matrix.xls (physical WebADE action associations)
    Detailed Design documents
    Use Cases
    Data Models and database structure reports
    Test Scripts

Additionally, new documentation may need to be created and amended to completely
represent the implementation of the application, to create a complete documentation set.

No modifications to the existing CIMS Web Help or online training have been identified at
this time.

There are no other new non-functional requirements known to be involved in the
implementation.




                                                                                 Page 18 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements



10. BUSINESS PROCESSE S

       The Forest Protection Branch has requested the ability to enter inspections that
       related to Fire Abatement and Rehabilitation into CIMS. Data entry will follow the
       current methods that are present within CIMS for Harvest type Inspections.

       Except for the following modifications, all existing CIMS business processes are to be
       remain unaltered for both existing C&E personnel [?] and new Fire Protection
       users[?].

       Forest Protection Branch roles will perform the same functions as existing C&E roles
       with corresponding names (and therefore duties) [?].

       Fire Zones will be useable where Districts are currently used in the application, for
       Fire Protection Inspections only [?].


10.1 HOME MODULE


10.1.1     CIMS-000
              Forest Protection Branch users will not need access to all sections currently
               shown on the welcome screen.
              A new section called “Reinspection Required” and links will need to be added.
               Required re-inspections are defined as having a start date and a 30 day
               (inclusive) window. After 30 days, the reinspection reminder will no longer be
               shown for a given inspection.
              Default district will need to be modified to use Fire Zones instead, for Forest
               Protection Branch users only [?].
              All Forest Protection Branch users will have the same view on this screen;
               there will be no variation by role.


10.2 INSPEC TION & RISK
              Two distinct inspections have been defined for CIMS entry at this time:
                Fire Abatement
                Fire Rehabilitation

               These inspections will be enterable and editable by both Forest Protection
               Branch and C&E Personnel. These inspections are modelled after the Harvest
               Inspection.
              These inspections can only be created within a Fire Zone and therefore can
               only be searched for within a Fire Zone.
              Forest Protection Branch users will not need access to all sections currently
               shown on the inspection screen. As such, some sections will be hidden.
              Users will enter how the Hazard was abated, via the general comments box of
               Fire Abatement and Rehabilitation inspections.
              Inspectors will be able to create relationships between two individual
               inspections, for auditing and research.


                                                                                    Page 19 of 46
Ministry of Forests and Range                                   CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                           Business Requirements

              Some limited Risk Assessment information will be enterable .directly from the
               CIMS inspection, without having to access the Risk module


10.3 CLIENT
              Please see Section 7.2.3 for new business processes relating to CIMS Clients.


10.4 SITE
              Sites will have additional data and will be modelled after the General
               Inspection‟s site information
              Tenures will not be the primary identifier for a site, in terms of a Fire
               Abatement or Fire Rehabilitation inspection.
              Please see Section 7.2.4 for new business processes relating to CIMS Sites.


10.5 EXCLUSIONS
       The following modules will not have new business processes, or changes to existing
       business processes:
           Admin
           Commencement
           Schedule
           Plan
           Risk




                                                                                   Page 20 of 46
Ministry of Forests and Range                                      CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                              Business Requirements



11. DATA REQUIREMENTS

The following section defines data and changes to how that will be collected as a result of
the proposed modifications. Unless stated elsewhere in this document, this section defines
how particular data items are to be stored and entered, throughout both CIMS and ERA.


11.1 GENERAL
In general the implementation will suppress data that has been marked for removal, rather
than actually removing the code, data, database columns. That is to say that a piece of data
may still be retrieved from the database, but the user will not be aware of its existence, as
it will not be displayed in the web application or reports.


11.2 SITES
Sites are identified at the Fire Zone level and roll up to the Fire Centre. Investigations and
inspections are performed provincially however.

Risks associated with a site include, but are not limited to:
       o Urban interface zones (parts of communities near the edge of forest or fields)
       o Red and Dead standing forests

During data entry, sites optionally have a fire number [?] and a latitude/longitude pair [?].
When latitude is specified, longitude must be available as well (and vice versa) [?].

During read-only display, sites will have additional logic determining what is shown:
       o When a Fire Number is available, it is to be shown [?]
       o When no Fire Number is available, the Site‟s Lat/Long values are to be shown [?]
       o When no Fire Number or Lat/Long is available and a tenure is available, it will be
          shown as per current CIMS functionality [?]


11.2.1     F IRE N UMBERS
   Fires are named for the fire center they are initially located in. They restart every year
   and include the year.

       o   Entered as a single field with a mask [?]
       o   Displayed generically as:
                Z#####/YYYY
                Where „Z‟ represents a single letter code for the Fire Zone
       o   Example:
                G10485/2006 or K10485/2007
       o   In the database, a Fire Number will be stored as follows[?]:

           Type         Length      Input/Display Mask
           Character    11          A#####/YYYY


   Please see Appendix A for a list of codes for all Fire Zones.




                                                                                      Page 21 of 46
Ministry of Forests and Range                                       CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                               Business Requirements

11.2.2     L ATITUDES /L ONGITUDES
  Protection sites are not generally identified by tenures as they are for C&E inspections.
  Instead, they are usually identified by latitude and longitude, shown down to the tenths
  of a minute (“Tenths” format):

       o   Displayed generically as:
               ##o ##.####N
               ###o ##.####W
       o   Example (lat/long designation is not shown):
               48o 25.0115N (lat)
               148o 25.0115W (long)
       o   Entered as a single text field [?]
               The Ministry has expressed the desire use javascript to translate from the
                  following formats, into the “Tenths” format (please note that spaces are
                  top be respected in the formats below):
                      - Latitudes:
                              o ##/##/## [?]
                              o ## ## ## [?]
                              o ## ##.#### [?]
                      - Longitudes:
                              o ###/##/## [?]
                              o ### ## ## [?]
                              o ### ##.#### [?]
               Note: Integers may be entered as positive or negative [?]
               Note: The degrees symbol (o) is overly difficult to implement using
                  standard HTML text boxes present in CIMS. As such, this implementation
                  is out of scope.
               Note: No validation will be performed on the lat/long information itself, to
                  ensure the point is present within the boundaries of the Province of British
                  Columbia. As long as the user attempts to enter a number in one of the
                  above formats, it will be accepted [?].
       o   The data will not however be stored in the “Tenths” format [?]

  The FTA application has been identified as the defacto standard for lat/long input and
  usage within the Ministry. FTA in turn uses the ESF standard for storage, while not
  actually providing a user interface per say, for entry of this information.

  FTA currently stores lats/longs in dual formats: WGS84-Geographics and NAT83-
  Geographics. Internally, this is stored using an SDO geometry, in BC Albers format.

  As integration of SDO geometries is beyond the scope of development, CIMS and ERA
  will instead store the most common representation of point-coordinate information,
  which is represented by three integer fields, described as follows:

       Datum                        Type               Length
       Latitude Hours               Signed   Integer            2
       Latitude Minutes             Signed   Integer            2
       Latitude Seconds             Signed   Integer            2
       Longitude Hours              Signed   Integer            3
       Longitude Minutes            Signed   Integer            2
       Longitude Seconds            Signed   Integer            2


                                                                                       Page 22 of 46
Ministry of Forests and Range                                           CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                                   Business Requirements



    Entry of fire numbers [?] and lat/long [?] values in both CIMS and ERA will be performed
    in a uniform manner across both applications.


11.3 CLIENTS
   Clients are referred to as Responsibly Parties by the Forest Protection Branch.
   While the Forest Protection Branch has a different definition of what a “Client”
    constitutes, it is functionally the same as C&E Branch‟s usage. A new type of client called
    “Investigation Person/Organizations” have been defined for CIMS, in the CIMS Data
    Requirements section of this document. Please see Section 7.2.3 for further details. ERA
    will continue to exclusively use the CMS definition and implementation of clients.


11.4 INSPEC TION & RISK
        New Fire Abatement and Rehabilitation inspections will be modelled after the existing
        CIMS Harvest Inspection type.

              An owning agency code will be added to the inspection [?], to allow straight
               forward identification of inspections that were created by a particular branch
               (specifically without having to determine the agency by reverse-looking up
               the agency from the owner/lead investigator). This field will be automatically
               populated, based on the role of the user who is entering the inspection[?].
               When a user has been assigned both a Forest Protection Branch role and a
               C&E role, the C&E branch will be specified as the owning agency[?].

              The existing File # fields, “ARCs File #”[?] and “ORCs File #”[?] fields will be
               made optional, as these are not always present for Fire Abatement and
               Rehabilitation inspections.

              The Forest Protection Branch does not currently perform Risk Assessments in
               standard C&E manner. Instead, Forest Protection Branch users will have a
               simplified list of critical items that may be indicated directly on the inspection.
               These are currently defined as follows:

                Datum                                     Control
                Within 2km Wildland/Urban Interface[?]`
                Red & Dead Forest[?]
                                                           Check Boxes
                Seismic Lines[?]
                Land Clearing[?]
                Other[?]                                    Text Area


               With the exception of the “Other” text area, these values are to be
               implemented as a dynamic list of checkboxes, drawn from the database, as
               opposed to fixed data items stored in similarly-named columns[?]. While the
               design will be likely require more columns than the data to be stored, it will
               allow Fire Abatement and Rehabilitation inspections to accommodate more
               items in the future.

              Fire Abatement and Rehabilitation inspections may have inspection reasons
               additional to those that C&E currently uses. Specifically, the text of the first
               item “To achieve a district/region inspection objective” does not make sense


                                                                                           Page 23 of 46
Ministry of Forests and Range                                         CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                                 Business Requirements

               to Forest Protection Branch users and should read “To achieve a Fire
               Centre/Zone inspection objective”. To accommodate inspection-type or
               agency specific reasons for inspection, the Inspection Reason needs to take
               the current inspection type[?] or agency[?] into consideration for display.

              All Fire Abatement and Rehabilitation inspections will be listed using the
               standard inspection id from CIMS, followed by the site identifier as available.
               For example, inspection id 31854 would display as follows, depending on how
               the site has been defined:

                   o   If the site is a fire number [?]:31954-K0001/2007
                   o   If the site has a lat/long [?]: 31954-48o 25.0115N 148o 25.0115W
                   o   If the site has a tenure [?]: 31954-A02/TFL25

               Please see section 6.1.2 for details on precedence rules for display of site
               identification information.


11.5 CLIENT
       o   Inspections do not always have a client and therefore must continue to allow
           entry of inspections without clients [?]
       o   Instead of requiring the frequent entry of anonymous or weakly-defined clients
           into the CLIENT system (CMS), CIMS will be augmented to also allow entry of
           clients directly into a new CIMS Inspection Person/Organization (table) [?]. The
           table will contain the following information:

           Attribute        Type        Length   Optionality
           First Name       Character   40       Optional
           Middle Name      Character   40       Optional
           Last Name        Character   40       Required for a Person
           Company Name     Character   50       Required for a Company



       o   Person OR company name must be entered [?]
       o   Only the last name portion of person name must be entered`
       o   Only a person name OR a company name can be entered at a time. If text is
           entered into both person and company name fields, it is considered an error on
           save [?]
       o   During entry, the all name fields should be initial-capped automatically via
           JavaScript [?]
       o   The existing CIMS functionality that allows a CMS-Client to be assigned as a
           Licensee will also be maintained for the new Fire Abatement and Rehabilitation
           inspections [?]


11.6 SITE
       Fire Abatement and Rehabilitation inspections will have additional data stored for
       sites, further to that which is currently available when creating a General Inspection
       site. The table will contain the following information (as defined in Section 6.1.2):
           o Latitude [?]
           o Longitude [?]
           o Fire Number [?]


                                                                                         Page 24 of 46
Ministry of Forests and Range                                CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                        Business Requirements


11.7 EXCLUSIONS
       The following modules will not have new data requirements, or changes to existing
       data requirements:
          o Admin
          o Commencement
          o Schedule
          o Plan
          o Home Module




                                                                                Page 25 of 46
Ministry of Forests and Range                                     CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                             Business Requirements



12. USER REQUIREMENTS

Due to time constraints, there are currently no use cases defined for implementation. The
following use cases are however suggested for future inclusion as part of the requirements:
        1. Welcome to CIMS
        2. Search For Inspection by Type
        3. Create/Edit Fire Abatement Inspection
        4. Create/Edit Fire Rehabilitation Inspection
        5. View Existing Fire Abatement Inspection
        6. View Existing Fire Rehabilitation Inspection
        7. Print Report of Fire Abatement Inspection
        8. Print Report of Fire Rehabilitation Inspection

Additional use cases will likely be required to further define all logical scenarios that may be
encountered during regular use of CIMS, with respect to Fire Abatement and Rehabilitation
inspections.




                                                                                     Page 26 of 46
Ministry of Forests and Range                                             CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                                     Business Requirements



13. FUNCTIONAL REQUIREME NTS


13.1 ALL MODULES AND MENUS


           o   [?] All screens that will be accessible to any Fire Protection role that currently
               have a drop down (or other such control) to identify a District and/or Region
               will need to be modified to instead show a Fire Zone, for Fire Protection roles
               only.

           o   [?] All references in the application to “Forest Officer” and/or “Forest Official”
               must be altered to read “Official”. This terminology is outdated and will
               confuse new users.

           o   All drop down lists for data creation and search criteria that currently indicate
               either an Inspector will be modified to include users in corresponding
               protection roles [?].

           o   The following CIMS main menu items and associated modules will be made to
               be inaccessible to Forest Protection Branch users:

                Menu & Sub Items                                          Accessible   Requirement
                                                                           to FPB?          #
                Inspections         Add Inspection                            Y           [?]
                                    Search Inspections By                     Y           [?]
                                                  Inspection Id               Y           [?]
                                                  Tenure                      Y           [?]
                                                  Inspection Type             Y           [?]
                                                  Inspector                   Y           [?]
                                    Search Govt. Statutory Obligations       N            [?]
                                    Create Inspection Plan                   N            [?]
                                    Search Inspection Plans                  N            [?]
                Scheduling                                                    N            [?]
                Evaluations                                                   N            [?]
                Reports             Only those reports defined in this         Y           [?]
                                    section will be displayed.
                Commencement                                                   N            [?]
                Admin                                                          N            [?]


               Please see exclusions for CIMS-000 to identify additional sections of CIMS
               that are to be made inaccessible to Forest Protection Branch users, via both
               menus and regular navigation.


13.2 HOME MODULE


           CIMS-000

                  Default District will need to be modified to instead use Fire Zones [?]. The
                   label on the screen will need to be changed to match [?].
                  For all Forest Protection Branch users only, the following sections will be
                   suppressed from display:

                                                                                             Page 27 of 46
Ministry of Forests and Range                                      CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                              Business Requirements

                          Recently Updated Evaluations[?]
                          Reconcile Required[?]
                          Follow Up Closure Required[?]
                          Govt. Stat. Obligations Closure Reqd[?]
                          Workflow Management:
                                Reconcile Required[?]
                                Follow Up Closure Required[?]
                                Govt. Stat. Obligations Closure Reqd[?]
                                Commencement Sites Without Risk Evaluations[?]
                        Add:
                                Add Risk Assessment[?]
                                Add Risk Estimate[?]
                        Services:
                                Search Evaluations By [?] (all entries shown)
                  All of the preceding sections that are to be suppressed on the welcome
                   screen should also be made inaccessible through menus [?] and regular
                   system navigation means [?].
                  New links are to be added, using the following labels:
                        Fire View[?]
                        Forest Protection Internal website[?]
                  Search by Inspection Type is to be updated with new search criteria.
                   Please see notes below on CIMS-157 for further details
                  A new dynamic list is to be added, titled “Reinspection Required” [?]. This
                   is to display all Fire Protection-only inspections that have been marked as
                   requiring reinspection. An inspection needs to be re-inspected if the Re-
                   inspection Reminder date is set (see CIMS-131) and the date given is
                   equal to the current system date, or up to and including 30 days
                   afterwards (that is, a 30 day inclusive window)[?].
                  Please see Appendix B – Section 12.1.1 for screen prototype


13.3 INSPEC TION
                  To accommodate the new inspection types, a new series of view/edit
                   screens and underlying code will need to be implemented. As the
                   information to be collected for both the Fire Abatement and Rehabilitation
                   are close to that which is collected for the existing Harvest Inspection, the
                   Harvest Inspection will be used as a basis for development [?]. All
                   information and functionality that is currently associated with an existing
                   Harvest Inspection will be made available for use in Fire Abatement and
                   Rehabilitation inspections, except where otherwise noted in this
                   document, technically infeasible or defined as out of scope [?].

                  Fire Abatement and Rehabilitation inspections can only be created within a
                   Fire Zone [?] and specifically can not be created within a District [?].
                   Methods that cause the creation or modification of an inspection such that
                   it is placed logically within a District, is in error.

                  For all screens involved in inspections, the Risk Evaluation Id field is to be
                   suppressed for all Fire Abatement and Rehabilitation inspections. The code
                   is not to be modified to an extent where the id field is unavailable for later
                   inclusion [?]. The following screens (only) will be modified:
                        101/100 [?]

                                                                                      Page 28 of 46
Ministry of Forests and Range                                      CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                              Business Requirements

                          131 [?]
                          132/133 [?]
                          134/135 [?]
                          143/142 [?]

                  Wherever a Licensee field is shown (all inspection types and screens), it is
                   to be re-labelled to read “Responsible Party” [?]
                  When editing an Inspection, the Follow up and Follow up closure tabs are
                   not to be shown for Fire Abatement [?] and Rehabilitation inspections [?].

           CIMS-101/100 (INSPECTION TAB)

                  Latitude [?] and Longitude [?] fields are to be added to the “site section”
                   of the screen, above the existing Tenure field.
                  Fire Number is to be added as a new field [?], in its own section below the
                   “Contact” area [?].
                  The following sections are to be suppressed for Fire Abatement and
                   Rehabilitation inspections only:
                        Activity Status [?]
                        Comments about status [?]
                        Attachment Description [?]
                        Delivery Method [?]

                  The following section is to be suppressed for All inspection types [?]:
                       Attachment Description [?]

                  The “Forest Officer/Official” section is to be relabelled to read “Inspecting
                   Official” [?] for All Inspection types [?].
                  The “Licensee” section is to be relabelled to “Responsible Party” [?]
                  The “Browse” button in the Licensee section will redirect to the new CIMS-
                   016 screen, allowing entry of Inspection Person/Organizations [?] (CIMS-
                   101 only)
                  The “Received By” section is to be given a wrapping, header block with
                   the title “Delivered to Responsible Party” [?]
                  The dual “File #” sections of the screen are to be relabelled to read “ARCs
                   File #” [?] and “ORCs File #”[?] (left, right respectively), for all inspection
                   types [?].
                   “ARCs File #” [?] and “ORCs File #”[?] fields will be made optional
                  A new section called “Risk Assessment” is to be added before the “Area
                   Inspected” section [?]. This section will contain the following information:
                        Within 2km Wildland/Urban Interface (check box) [?]
                        Red & Dead Forest (check box)[?]
                        Seismic Lines (check box)[?]
                        Land Clearing (check box)[?]
                        Other (text area)[?]

                  A new section called “Related Inspections” is to be added after the “Risk
                   Assessment” section [?]. This section will contain the following:
                       A list of inspections that have been related to the current
                         inspection [?].




                                                                                      Page 29 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements

                          Each inspection will have a button labelled “Detach” to dis-
                           associate inspections from the current inspection [?] (CIMS-101
                           only)
                          Each inspection will be displayed as a hyperlink, allowing the user
                           to navigate to the details of the inspection [?].
                          A button labelled “Browse” at the bottom [?] (CIMS-101 only)

                  The existing Print button will need to be modified to run the new Fire
                   Abatement and Rehabilitation inspections report, once it has been
                   implemented[?].
                  Please see Appendix B – Section 12.1.2 for screen prototype

           CIMS-143/142 (REQUIREMENTS TAB)

                  New general requirements are to be defined for Fire Abatement and
                   Rehabilitation inspections and are to be shown on the General
                   Requirements screen (Requirements Tab) [?]. The following have been
                   suggested for use:
                       Debris Piles[?]
                       Tons Per Hectare of Slash[?]
                       Windrows[?]

           CIMS-131 (ADDENDUM TAB)

                  The Inspection Reason section will need to be modified to allow
                   specification of different inspection reasons for the Forest Protection
                   Branch. This may require either updating of codes[?] in the
                   INSPECTION_REASON_CODE table, or also include addition of a new code
                   table to separate the agency[?] or inspection type-specific[?] reasons.
                  As CIMS currently displays remediation orders from ERA, it should also be
                   modified so as to display applicable Cost Recovery enforcement actions[?].
                   Additionally Remediation orders from ERA should still be shown, but
                   relabelled as Rehabilitation orders[?].

           CIMS-132/133 (ATTACHMENTS TAB)

                  The description field needs to be expanded to allow entry[?] & storage[?]
                   of 2000 characters, up from its current limit of 255 characters. This is to
                   be applied to all Inspection types [?].

           CIMS-134/135 (NON-COMPLIANCE TAB)

                  A new item called “Instructions Issued” is to be added to the Compliance
                   Action Taken drop down [?]
                  A second drop down to be shown (to the left) when “Instructions Issued”
                   has been selected, to be called “Field Notice” [?]
                  The Field Notice drop down will contain the following items:
                        Order to Extinguish [?]
                        Order to Abate [?]
                  As CIMS does not currently attempt to create any particular type of
                   Enforcement Action in ERA (only a case if none exists), there will be no
                   modifications required in this regard.


                                                                                    Page 30 of 46
Ministry of Forests and Range                                          CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                                  Business Requirements

           CIMS-150 (ADD INSPECTION)

                  The Inspection Type drop down will include two new Inspection Types:
                       Fire Abatement [?]
                       Fire Rehabilitation [?]

                  A new drop down will be added for the Fire Zone [?].
                  The District drop down will be suppressed for these inspection types only
                   [?].

           CIMS-157 (SEARCH BY INSPECTION TYPE)

               The existing Search by Inspection Type is to be updated to include additional
               search criteria applicable to the Forest Protection Branch.

                  The Inspection Type drop down will include two new Inspection Types:
                       Fire Abatement [?]
                       Fire Rehabilitation [?]

                   These types will be implemented in a single new database table [?]
                   however, as there is currently no difference in the information that is
                   being captured by each type.

                  When Fire Abatement or Rehabilitation has been selected as the inspection
                   type, only the Fire Zone drop down will be shown [?]. Alternately, when
                   any other inspection type is shown, only the District drop down will be
                   available; the Fire Zone drop down will be suppressed [?].

                  The screen will include the following new criteria:

                        Criteria          Controls    Rules
                        Fire Zone [?]     Drop Down   This will only be shown when Fire Abatement or
                                                      Rehabilitation has been selected as the inspection
                                                      type.
                        Latitude [?]      Text Box    To be entered[?]/displayed[?] as per the Data
                                                      Requirements section.
                        Longitude [?]     Text Box    To be entered[?]/displayed[?] as per the Data
                                                      Requirements section.
                        Fire Number [?]   Text Box    To be entered[?]/displayed[?] as per the Data
                                                      Requirements section.


                  The new criteria will only become available when an inspection of type
                   “Fire Abatement” or “Fire Rehabilitation” has been selected [?].
                  The new criteria will be available to all CIMS users that can access the
                   screen [?]. It will not normally, automatically be shown however [?].
                  The new criteria will automatically default and be shown for Forest
                   Protection Branch users [?].
                  Search results will be modified as follows for Fire Protection Inspections:
                        Reconcile? Column is to be removed [?]
                        Follow-Up Column is to be removed, in following with its
                          corresponding tab‟s removal from CIMS-100/101 [?]
                        See CIMS-155/156/157/158 details
                  Please see Appendix B – Section 12.1.3 for screen prototype



                                                                                            Page 31 of 46
Ministry of Forests and Range                                        CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                                Business Requirements

           CIMS-158 (SEARCH BY INSPECTOR)

                  The screen will include the following new criteria:

                        Criteria        Controls    Rules
                        Fire Zone [?]   Drop Down   Forest Protection Branch users will only see a Fire
                                                    Zone drop down; the District drop down will be
                                                    suppressed [?].

                                                    For C&E users, when selected, the existing District
                                                    drop down will be automatically cleared as a
                                                    search result [?]. Conversely, when District is
                                                    selected for this type of search, Fire Zone will be
                                                    cleared [?].


                  Search results will be modified as follows for Fire Protection Inspections:
                       Reconcile? Column is to be removed [?]
                       See CIMS-155/156/157/158 details

           CIMS-155/156/157/158

                  On execution of a search, if only one inspection is returned as a result, the
                   application should automatically redirect to that inspection. This is to be
                   applied to all inspection types and inspection search screens[?][?][?][?].
                  Search results will be modified as follows for Fire Protection Inspections:
                       Site Column is to be shown in the following manner:
                               When a Fire Number is available, it is to be shown [?]
                               When no Fire Number is available, the Site‟s Lat/Long
                                   values are to be shown [?]
                               When no Fire Number or Lat/Long is available and a tenure
                                   is available, it will be shown as per current CIMS
                                   functionality [?]

           NEW CIMS-155A (SEARCH FOR RELATED INSPECTIONS)

           A new screen will be created to allow an existing incomplete inspection to be
           related to other inspections (any state) [?].

                  The screen will be presented as a search screen with two sections:
                      o The top section will show all inspections currently associated to the
                          current “base” inspection [?].
                               This section will also have controls to allow the removal of
                                 specific inspections from the list [?]
                               This section will have a Close button, which will redirect the
                                 user to CIMS-016 (as per below), to continue adding/editing
                                 the inspection [?]
                      o The bottom section will allow searching for inspections & display of
                          search results [?]
                      o On each result returned, an “Add” button will be shown in the
                          right-most column [?] When clicked, the inspection will be related
                          to the current inspection [?]. Visually, the inspection will appear in
                          to the top section of the screen [?] and the search results will be
                          cleared [?]



                                                                                          Page 32 of 46
Ministry of Forests and Range                                   CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                           Business Requirements

                  As the user is intentionally relating two known inspections, the search
                   screen will be modelled after CIMS-155, which allows searching for an
                   inspection by Id only [?]
                  This feature will be available to all inspection types [?]
                  This screen will also implement common search updates, as described by
                   the CIMS-155/156/157/158 details above [?]


13.4 CLIENT


           CIMS-016 (CLIENT SEARCH)

               The client search screen will need to be modified for Fire Abatement and
               Rehabilitation inspections so that non-tenure holding clients can be easily
               entered without having to create new entries in CMS (CLIENT). The following
               modifications will be made to CIMS-016, for Fire Abatement and
               Rehabilitation inspections only [?]:

                  The current search will be modified to search the new fields defined for
                   storage of Inspection Person/Organizations[?]
                  A new button called “Add Responsible Party” will be added to the top
                   button bar of the screen[?]. This will only be present for Fire Abatement
                   and Rehabilitation inspections. On click of the button, the user will
                   navigate to CIMS-155A [?]


13.5 SITE


           CIMS-013 (FIRE ABATEMENT/REHABILITATION SITE SEARCH)

               The Identify Site screen will need to be modified to include new fields
               application to Fire Abatement and Rehabilitation inspections. Please see
               Section 7.2.4 for details of the fields to be added to CIMS-013 [?], for Fire
               Abatement and Rehabilitation inspections only [?].


13.6 EXCLUSIONS
       The following modules will not have new functional requirements, or changes to
       existing functional requirements:
       o Admin
       o Commencement
       o Schedule
       o Plan
       o Risk




                                                                                   Page 33 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements



14. REPORTING REQUIREMEN TS

   All changes to the screens will be reflected in the corresponding reports, when
   implemented. In particular, all data items, positions and formatting modifications made
   to CIMS 100/101 will also be reflected in the new Fire Abatement[?] and
   Rehabilitation[?] inspection reports.

   Due to development timelines, only existing reports that require few modifications will
   be enabled for Forest Protection Branch users [?].

   Only the following reports will be made accessible to Forest Protection Branch users,
   with the described modifications:
           For all reports below:
                     o Should display Fire Zones [?], rolling up to Fire Centres [?] and
                        Provinces [?]
                     o Site Ids should display as per Data Requirements section [?]
                     o To include information from new Fire Abatement and Rehabilitation
                        inspections for display [?] and in totals [?]
           Incident Report Summary
           District Inspector Activity Report
                     o To be relabelled “Zone Inspector Activity Report” [?]
                     o “Licensee” to be relabelled to “Responsible Party”
           Inspection Reason Summary by District
                     o To be relabelled “Zone Inspector Activity Report” [?]
                     o To include new Fire Abatement and Rehabilitation inspection
                        reasons for inspections
           C&E History[?]
                     o Please see CIMS-623/624 below


14.1 REPORT INVOCATION SC REENS


   On the report execution screens of the above reports, the following modifications will be
   made:


14.1.1     CIMS-616 D ISTRICT I NSPECTOR A CTIVITY R EPORT
           o   Addition of Fire Abatement and Rehabilitation inspections types to the
               Inspection Type drop down.
           o   Please see CIMS-607/613/616 for further details


14.1.2     CIMS-613 I NCIDENT R EPORT S UMMARY R EPORT
           o   Forest Officer/Official re-labelling [?]
           o   Addition of Forest Protection Branch roles to Forest Officer/Official drop down
               [?]


14.1.3     CIMS-607/613/616
           o   Addition of Fire Zones as a new drop down [?]

                                                                                    Page 34 of 46
Ministry of Forests and Range                                   CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                           Business Requirements

           o   Selection of a Fire Zone or District causes the other drop down to be cleared
               [?]
           o   For Forest Protection Branch users only the District drop down will be
               suppressed [?]


14.1.4     CIMS-623/624
               The C&E History client search and History report screens will need to be
               modified for Fire Abatement and Rehabilitation inspections so that non-tenure
               holding clients (Inspection Person/Organizations) can be easily found. The
               following modifications will be made for all inspections [?]:

                  The current searches and results for both screens will be modified to
                   search   the   new     fields defined  for   storage   of  Inspection
                   Person/Organizations [?] [?].


14.2 CORE REPORTS


   The following reports will not be modified or made accessible to Forest Protection Branch
   employees:
            Inspections
              o Recreation Patrol Inspection Report
              o Road Inspection Report
              o Silviculture Inspection Report
              o General Inspection Report
              o Harvest Inspection Report
              o Incident Inspection Report
              o Range Inspection Report
              o Recreation Inspection Report

              Estimates
               o Harvest Estimate Report
               o Road Estimate Report
               o Silviculture Estimate Report
               o General Estimate Report
               o Harvest Estimate - Site Priority Report

              Assessments
               o Harvest Assessment - Site Priority Report
               o Harvest Assessment Report
               o Road Assessment Report

              Reports from the Reports Menu
               o Active Harvest Sites Without Risk Evaluations Report
               o CIMS Contravention Conclusion Method Summary Report
               o Client Compliance and Enforcement History Report
               o Completed Inspections Summary Report
               o Compliance Action Summary by Forest Officer_Official Report
               o Compliance Summary by Forest Officer_Official Report
               o Compliance to 02_03 CPM Standards Report
               o Compliance to 04_05 CPM Standards Report

                                                                                   Page 35 of 46
Ministry of Forests and Range                                   CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                           Business Requirements

               o   FTA Cut Block Status Update Report
               o   Government Non-Compliance Ledger Report
               o   High or Very High Priority Sites Inspected Report
               o   High or Very High Revenue Risk Sites Inspected Report
               o   Inspection Compliance by Priority Report
               o   Inspection Site Assignment Summary Report
               o   Inspection Time to Completion Report
               o   Inspections on Active Sites Report
               o   Inspections Requiring Follow Up or Investigation Report
               o   Reconcilable Inspections Report
               o   Reinspection Priority Report
               o   Risk Evaluations by Forest Officers_Officials Report
               o   Sites Inspected Based on Inspection Priority Report

   No other CIMS reports will be available for use by Forest Protection Branch users[?]. All
   new reports will be made available for use by C&E personnel however[?].

   Other than what has been specified above, no other reports have been defined as being
   in scope for development or modification.


14.3 NEW REPORTS


   The following new reports will need to be created to accommodate new Fire Abatement
   and Rehabilitation inspection types:
           Fire Abatement Inspection Report[?] (to be based on the Harvest Inspection
              Report)
           Fire Rehabilitation Inspection Report[?](to be based on the Harvest Inspection
              Report)
           Risk Assessment (report subsection): This will be based on the existing Risk
              Assessment report, but will pull from the smaller list of risk assessment items
              presented to Forest Protection Branch users from CIMS-100/101 [?]. The
              report will be shown as a new section in the Fire Abatement and
              Rehabilitation inspection reports[?].

   Please note that these reports are not accessible via the CIMS Reports menu, but are
   PDF reports that can be generated from relevant CIMS screens.

   These reports require further definition that can not be described due to time
   constraints. All updated summary reports should roll details from the Fire Zone [?] up to
   the Fire Center [?] and Provincial [?] levels, once report implementation becomes in
   scope.




                                                                                   Page 36 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements



15. SECURITY REQUIREMENT S


15.1 ALL MODULES
       o   Protection roles work across the entire province and should not be restricted from
           data entry or reporting across Fire Zone/Centre boundaries. As such, all users will
           be created with access to all Fire Zones defined by the ADAM security manager
           [?].
       o   Protection Roles will be allowed to view Fire Abatement and Rehabilitation
           Inspections only [?] and will not be able to access C&E inspections in any manner
           [?].
       o   C&E Roles will have security permissions on Protection inspections, equivalent to
           that which they currently have on C&E inspections [?]. There will be no additional
           security constraints for C&E roles, on Fire Protection inspections.


15.2 HOME MODULE
       Please see section 7.4.2 for Security Requirements of the Home Module. The security
       of this module has been implemented by excluding features from users.


15.3 INSPEC TION
       Please see section 7.4.3 for Security Requirements of the Inspection Module. The
       security of this module has been implemented by excluding features from users.


15.4 REPORTS
       Please see section 7.5 for Security Requirements of the Reports Module. The security
       of this module has been implemented by excluding features from users.


15.5 EXCLUSIONS
       The following modules will not have new security requirements, or changes to
       existing security requirements:
           o Admin
           o Client
           o Commencement
           o Schedule
           o Plan
           o Risk
           o Site




                                                                                    Page 37 of 46
Ministry of Forests and Range                                     CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                             Business Requirements



16. RISK SUMMARY

   1. Creation of storage for Clients, which is functionality that is technically already
      handled by the CLIENT (CMS) application & data structures.

        Risks              Potential of parallel data entry and duplication
                           Increase in erroneous data
                           Data model approval and subsequent project hold up
        Mitigations        User training to have users first search CLIENT will reduce some
                            dual entry
                           There is no mitigation for erroneous data entry
                           Advance notice to the DAs and DBAs will help preserve the project
                            timelines

   2. Outstanding Data from the Forest Protection Branch

        Risks              While there is no critical data identified at this time, any data that
                            the branch would like to see used upon Production delivery that is
                            not in the hands of the development team prior to Test delivery will
                            not likely reach Production in a timely manner
        Mitigations        Data requested should be provided to the development team as
                            soon as feasible.

   3. Communication

        Risks              As there is only a short period in which to commence & complete
                            development, any delayed communication represents a significant
                            risk.
        Mitigations        All parties involved in development should meet regularly to assess
                            status of the project and resolve issues that come up.
                           Where possible, critical personnel should have a back up in place
                            who is both capable and authorized to make decisions and to
                            provide information to the development team.
                           Where no back up personnel is available, any additional business
                            process and system documentation that can be delivered to the
                            development team, should be presented prior to commencement.
                           Any critical personnel that will be unavailable for any part of the
                            duration of the project must provide the development team with a
                            timeline of their availability, so to as reduce time between
                            communications.

All Outstanding issues identified in this document represent some degree of effort, time
and/or quality risk.




                                                                                     Page 38 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements



17. OUTSTANDING ISSUES

   1. Fire Abatement and Rehabilitation inspections may have inspection reasons
      additional to those that C&E currently uses. Specifically, the text of the first item “To
      achieve a district/region inspection objective” does not make sense to Forest
      Protection Branch uses and should read “To achieve a Fire Centre/Zone inspection
      objective”.
           A list of new Inspection Reasons applicable to Fire Abatement and
             Rehabilitation inspections needs to be obtained from the Forest Protection
             Branch.
           C&E needs to determine if it would like to modify the code entry (faster) or
             alter the database to accommodate different inspection-type or agency
             specific reasons.

   2. Forest Protection Branch needs to determine which users will need what new roles.
      This can be determined in parallel to development.

   3. Forest Protection Branch needs to provide new hyperlinks to be shown on CIMS-000
      (welcome page).

   4. A list of general requirements applicable to Fire Abatement and Rehabilitation
      inspections needs to be obtained from the Forest Protection Branch. Currently, only
      the following have been suggested:
           Debris Piles
           Tons Per Hectare of Slash
           Windrows

   5. A list of Field Notices applicable to Instructions Issued for Fire Abatement and
      Rehabilitation inspections needs to be obtained from the Forest Protection Branch.
      Currently, only the following have been defined:
           Order to Extinguish
           Order to Abate

   6. A list of additional inspection risks applicable to Fire Abatement and Rehabilitation
      inspections needs to be obtained from the Forest Protection Branch. Currently, only
      the following have been defined:
           Within 2km Wildland/Urban Interface
           Red & Dead Forest
           Seismic Lines
           Land Clearing

   7. No use cases for CIMS or ERA have been defined due to time constraints.

   8. Modifications to reports and new reports for CIMS and ERA have not been fully
      defined due to time constraints. As such, the Forest Protection Branch will be limited
      to using a subset of the current CIMS and ERA reports, with only the modifications
      described. It is not expected that these changes alone will be sufficient. Additional
      data will likely be needed for the current reports (eg. Fire Numbers), as well as full
      mockups of the reports should be created, for detail reports (such as the Fire
      Inspection Report).


                                                                                    Page 39 of 46
Ministry of Forests and Range                                    CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                            Business Requirements

   9. The current definition for display of a Fire inspection in CIMS that only has lat/longs,
      is overly long. When placed in the CIMS user interface, there will generally only be
      sufficient space for two columns of inspection titles on any given list of inspections.
      The current definition defines the following as a valid display value:

       o   31954-48o 25.0115N 148o 25.0115W

       It is recommended that for lat/long identifiers, the following alternate displays could
       be used:

       o   31954-48o 25N 148o 25W (no decimal tenths)
       o   31954-48/25/00 148/25/00 (alternate UTM format)
       o   KLM-31954 (Fire Zone-inspection number, similar to ERA)
       o   K31954/2007 (Fire Zone and inspection number/year)

   10. CIMS currently has a list of single character codes for fire Zones, while ERA has a
       three-character list. If possible, these should probably both be three characters in
       order to have consistency between the applications.




                                                                                    Page 40 of 46
Ministry of Forests and Range                                   CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                           Business Requirements



18. APPENDIX A – REFERENCES

The following have been referenced by this document and are included as part of the
business requirements.


18.1 APPLICABLE LEG ISLATI ON
The BC Wildfire Act and Wildfire Regulation are legislation that are particularly relevant to
the Forest Protection Branch‟s activities.


18.2 INSPEC TION REASON S
To be obtained from the Forest Protection Branch.

The following have been suggested:
    Closure Order
    Fire Patrol
    Abatement
    Public Complaint


18.3 CIMS WELCOME SCREEN HYPERLINKS
To be obtained from the Forest Protection Branch.


18.4 GENERAL REQUIREMENTS
To be obtained from the Forest Protection Branch.


18.5 FIELD NOTICES
To be obtained from the Forest Protection Branch.


18.6 INSPEC TION RISKS
To be obtained from the Forest Protection Branch.


18.7 REHABILITATION ASSES SMENT
To be obtained from the Forest Protection Branch.


18.8 FIRE HAZARD ASSESSMENT
To be obtained from the Forest Protection Branch.




                                                                                   Page 41 of 46
Ministry of Forests and Range                                                CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                                        Business Requirements


18.9 FIRE ZONE CODES
The following list of codes is to be used during representation of a zone, in the CIMS
inspection identifiers:

ORG_UNIT_NO      ORG_UNIT_CODE      ORG_UNIT_NAME
1531             FCAMH              100 Mile House Fire Zone, 100 Mile
                                    House
1560             FNOCA              Cassiar Fire Zone, Dease Lake
1542             FSOAR              Castlegar Fire Zone, Castlegar
1532             FCACH              Chilcotin Fire Zone, Alexis Creek
1571             FCOCK              Chilliwack Fire Zone, Clearbrook
1545             FSOCB              Cranbrook Fire Zone, Cranbrook
1551             FPGDC              Dawson Creek Fire Zone, Dawson Creek
1552             FPGFN              Fort Nelson Fire Zone, Fort Nelson
1553             FPGJA              Fort St. James Fire Zone, Fort St. James
1554             FPGJO              Fort St. John Fire Zone, Fort St. John
1549             FSOGO              Golden Fire Zone, Golden
1546             FSOIN              Invermere Fire Zone, Invermere
1536             FKAKA              Kamloops Fire Zone, Kamloops
1544             FSOBO              Kettle Valley Fire Zone, Rock Creek
1547             FSOKL              Kootenay Lake Fire Zone, Nelson
1562             FNOLA              Lakes Fire Zone, Burns Lake
1537             FKALI              Lillooet Fire Zone, Lillooet
1555             FPGMK              Mackenzie Fire Zone, Mackenzie
1557             FPGRV              McBride Fire Zone, McBride
1538             FKAME              Merritt Fire Zone, Merritt
1539             FKAPE              Penticton Fire Zone, Penticton
1568             FCOPA              Port Alberni Fire Zone, Port Alberni
1556             FPGPG              Prince George Fire Zone, Prince George
1533             FCAQU              Quesnel Fire Zone, Quesnel
1548             FSORE              Revelstoke Fire Zone, Revelstoke
1540             FKASA              Salmon Arm Fire Zone, Salmon Arm
1561             FNOSK              Skeena Fire Zone, Terrace
1567             FCOSI              South Island Fire Zone, Cobble Hill
1570             FCOSQ              Squamish Fire Zone, Squamish
1569             FCOSC              Sunshine Coast Fire Zone, Powell River
1783             FNOTE              Telkwa Fire Zone, Telkwa
1558             FPGVA              Vanderhoof Fire Zone, Vanderhoof
1541             FKAVE              Vernon Fire Zone, Vernon
1534             FCAWL              Williams Lake Fire Zone, Williams Lake




                                                                                                Page 42 of 46
Ministry of Forests and Range        CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                Business Requirements



19. APPENDIX B – SCREEN PROTOTYPES


19.1 CIMS-000




                                                        Page 43 of 46
Ministry of Forests and Range       CIMS Fire Protection Enhancements
Compliance and Enforcement Branch               Business Requirements


19.2 CIMS-101




                                                       Page 44 of 46
Ministry of Forests and Range       CIMS Fire Protection Enhancements
Compliance and Enforcement Branch               Business Requirements


19.3 CIMS-157




                                                       Page 45 of 46
Ministry of Forests and Range                                CIMS Fire Protection Enhancements
Compliance and Enforcement Branch                                        Business Requirements



20. DOCUMENT SIGN-OFF

The undersigned have read and agree with the content of this document.




Susan Prosser                                             Date
Senior Business Analyst,
Information Management Group,
Ministry of Forests and Range




Yvonne Roslin-White                                       Date
Systems and Training Coordinator
Compliance and Enforcement Branch
Ministry of Forests and Range




                                                                                Page 46 of 46

								
To top