GIS R2 Development - DOC by vpo20543

VIEWS: 60 PAGES: 47

									                                                                    RFP #H-048-08 WisFIRS
                                                       Technical Guidance and Specifications Appendices
                                                                For R2 Phase GIS Development,
                                                                  Public Lands Management

1.0 Appendix A - TECHNICAL SPECIFICATIONS AND PRODUCTS ........................................................................................ 3
  1.1 Detailed Summary of the WisFIRS Project .......................................................................................................................... 3
     1.1.1 WisFIRS Release details ............................................................................................................................................... 4
     1.1.2 Current GIS Integration ................................................................................................................................................. 8
     1.1.3 Hardware / Software Environment ................................................................................................................................. 9
     1.1.4 Hardware / COTS Software Specifications .................................................................................................................... 9
     1.1.5 Performance ................................................................................................................................................................ 11
     1.1.6 Programming Specifications ........................................................................................................................................ 11
     1.1.7 Development Model ..................................................................................................................................................... 12
     1.1.8 User Interface .............................................................................................................................................................. 13
     1.1.9 Database Design ......................................................................................................................................................... 14
     1.1.10 Database Design Methodology.................................................................................................................................. 14
2.0 IMPORTANT NOTES ON DATA......................................................................................................................................... 16
  2.1 DNR Responsibilities.......................................................................................................................................................... 17
     2.1.1 Symbology / Cartography ............................................................................................................................................ 17
     2.1.2 Business Objects ......................................................................................................................................................... 17
     2.1.3 Unique Keys ................................................................................................................................................................ 18
     2.1.4 Ancillary Features List ................................................................................................................................................. 18
     2.1.5 Display Fields / Attributes / Report Formats ................................................................................................................ 18
  2.2 Anticipated Users ............................................................................................................................................................... 18
  2.3 Current GIS Technology Use ............................................................................................................................................. 18
  2.4 Security .............................................................................................................................................................................. 18
  2.5 Connectivity ........................................................................................................................................................................ 18
3.0 APPLICATION FUNCTIONALITY ......................................................................................................................................... 19
  3.1 WisFIRS R1 Integration Functionality ................................................................................................................................ 19
     3.1.1 Function Description - Launch to Map Portal from R1 (Individual Record) ................................................................. 19
     3.1.2 Function Description - Launch to Map Portal from R1 (Multiple Records) .................................................................. 20
     3.1.3 Function Description - Launch to R1 ........................................................................................................................... 21
     3.1.4 Function Description - Orphans List ............................................................................................................................ 21
     3.1.5 Function Description - Entitlement............................................................................................................................... 21
     3.1.6 Function Description - Minimum Resolution ................................................................................................................ 21
4.0 MAP DISPLAY....................................................................................................................................................................... 22
  4.1 Function Description - Layers List ...................................................................................................................................... 22
  4.2 Function Description - Viewing Historical Polygon Data .................................................................................................... 22
  4.3 Function Description - Dynamic labels for GIS features .................................................................................................... 22
  4.4 Function Description - Legend ........................................................................................................................................... 22
  4.5 Function Description - North Arrow .................................................................................................................................... 22
  4.6 Function Description - Scale Bar ........................................................................................................................................ 23
  4.7 Function Description - Attribute-based symbology / thematic mapping ............................................................................. 23
  4.8 Function Description - Upload of local layers ..................................................................................................................... 23
  4.9 Function Description - Measure Area ................................................................................................................................. 23
  4.10 Function Description - Measure Distance ........................................................................................................................ 24
  4.11 Function Description - Map Templates ............................................................................................................................ 24
  4.12 Function Description - Display latitude / longitude Coordinates ....................................................................................... 24
  4.13 Function Description - Map Bookmarks ........................................................................................................................... 24
5.0 MAP NAVIGATION................................................................................................................................................................ 24
  5.1 Function Description - Reset Map ...................................................................................................................................... 24
  5.2 Function Description - Zoom In .......................................................................................................................................... 24
  5.3 Function Description - Zoom Out ....................................................................................................................................... 25
  5.4 Function Description - Pan / Re-center Map ...................................................................................................................... 25
  5.5 Function Description - Pre-defined Zoom To Features (Termed Quick Searches within this document) .......................... 25
  5.6 Function Description - Zoom Bar / Zoom to Fixed Scale or Extent .................................................................................... 25
  5.7 Function Description - Zoom to Previous Map ................................................................................................................... 26


WisFIRS RFP R2 GIS Development                                    Page 1 of 47                                                        07/21/2010
                                                                     RFP #H-048-08 WisFIRS
                                                        Technical Guidance and Specifications Appendices
                                                                 For R2 Phase GIS Development,
                                                                   Public Lands Management

6.0 MAP SELECTION ................................................................................................................................................................. 26
  6.1 Function Description - Active Layer(s) Designation ........................................................................................................... 26
  6.2 Function Description - Select By Box ................................................................................................................................. 26
  6.3 Function Description - Select By Poly ................................................................................................................................ 26
  6.4 Function Description - Select By Point / Identify................................................................................................................. 27
  6.5 Function Description - Select By Buffer using Existing Features ....................................................................................... 27
  6.6 Function Description - Clear Selection ............................................................................................................................... 27
  6.7 Function Description - Show Results ................................................................................................................................. 27
7.0 MAP EDITING ....................................................................................................................................................................... 27
  7.1 Function Description - Working Property Selection............................................................................................................ 27
  7.2 Function Description - “Topology” Rules ............................................................................................................................ 28
    7.2.1 Features belonging inside a Property: ......................................................................................................................... 28
  7.3 Function Description - Create Polygon Boundaries ........................................................................................................... 28
  7.4 Function Description - Split Poly By Line............................................................................................................................ 29
  7.5 Function Description - Merge Polygons ............................................................................................................................. 29
  7.6 Function Description - Create Neighbor Polygon ............................................................................................................... 29
  7.7 Function Description - Split Poly by Poly ............................................................................................................................ 30
  7.8 Function Description - Polygon Boundary Edits ................................................................................................................. 30
  7.9 Function Description - Navigate Map while digitizing ......................................................................................................... 30
  7.10 Function Description - Polygon Delete ............................................................................................................................. 30
  7.11 Function Description - Tracking Historical Polygon Geometry ......................................................................................... 30
  7.12 Function Description - Explode function (Separate Singlepart into Mulipart polygons) .................................................... 31
  7.13 Function Description - Copy Polygon ............................................................................................................................... 31
  7.14 Function Description - Assignment of “Property, Compartment, Stand” (PCS) Triplet .................................................... 32
  7.15 Function Description - COGO Editing .............................................................................................................................. 32
  7.16 Function Description - Create Cruise Points .................................................................................................................... 32
  7.17 Function Description - Cruise Layer Download ................................................................................................................ 32
  7.18 Function Description - Create Ancillary Point Feature ..................................................................................................... 32
  7.19 Function Description - Create Ancillary Line Feature ....................................................................................................... 33
  7.20 Function Description - Create Ancillary Polygon Feature ................................................................................................. 34
  7.21 Function Description - Create Text-based Annotation ..................................................................................................... 35
  7.22 Function Description - Desktop Editing Support .............................................................................................................. 35
  7.23 Function Description - GPS Upload ................................................................................................................................. 35
8.0 GIS OUTPUT ......................................................................................................................................................................... 35
  8.1 Function Description - GIS Export ...................................................................................................................................... 35
  8.2 Function Description - Template Report Maps................................................................................................................... 36
  8.3 Function Description - Orphans Report .............................................................................................................................. 36
  8.4 Function Description - Masking for Report Output ............................................................................................................. 36
  8.5 Function Description - GIS Acres Summary reporting ....................................................................................................... 36
9.0 GIS ADMINISTRATION......................................................................................................................................................... 36
  9.1 Function Description - Uploaded Local Layers................................................................................................................... 36
Appendix B – Core Navigation Workflows: ............................................................................................................................. 37
  Zoom In .................................................................................................................................................................................... 37
  Zoom Out ................................................................................................................................................................................. 38
  Pan ........................................................................................................................................................................................... 39
  Start Over ................................................................................................................................................................................. 40
  Measure ................................................................................................................................................................................... 41
  Select by Polygon ..................................................................................................................................................................... 42
  Select by Rectangle ................................................................................................................................................................. 43
Appendix C –Business Workflows ........................................................................................................................................... 44
  Completed Treatment Attribution ............................................................................................................................................. 44
  Archival of Completed Treatment............................................................................................................................................. 45
  Pushing of Local Shapes to Staging WisFIRS Area ................................................................................................................ 46


WisFIRS RFP R2 GIS Development                                     Page 2 of 47                                                          07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management



        The vendor must review point by point the information in Appendix A, B and C in order to respond
        to the proposal.

        1.0 Appendix A - TECHNICAL SPECIFICATIONS AND PRODUCTS

        1.1 Detailed Summary of the WisFIRS Project
             A few applications that the Wisconsin DNR Division of Forestry uses to conduct business needed to be re-
             developed to improve efficiencies and make changes that came about from legislation. We were redesigning the
             Recon6i (RAVE/RAVEN) application(s) for public land management due to the obsolete technology on which it is
             running. Two of our other applications on the private side of Forestry for the WDNR also needed to be re-
             designed, Plan Trac (which is used to create and track management plans) and the Tax Law system(aka
             Managed Forest Law or MFL, which is used to administer the Tax Law programs). After evaluating the potential
             for merging functionality where it makes sense between these applications, we decided to re-design all three of
             them under the Wisconsin Forest Inventory & Reporting System (WisFIRS) project. WisFIRS is a system that
             will enable foresters to store data collected in the field, plan for and track completed practices (e.g. timber sales),
             report accomplishments, calculate the financial aspects of the programs (e.g. millions of dollars collected and
             dispersed to towns and counties), and tracking open MFL lands to hunting and recreation to name a few. This
             application manages core business functions for public and private forest management in Wisconsin, serving
             hundreds of DNR staff as well as our partners (county forests and cooperating (consulting) foresters). Due to the
             importance of knowing where on the landscape practices are being done, geographical information systems (GIS)
             is being integrated throughout the system. WisFIRS is being developed to encompass the business functions of
             3 existing applications, which are running on old technology, which is now at risk of failing. These applications
             were different enough that field staff had to learn how to use each application individually, making it incredibly
             cumbersome and in some cases staff have to re-enter the same information up to 4 times, increasing errors in
             the data. The WisFIRS project is taking the time to not only re-write existing applications into new, current
             technology, but also re-design workflows to gain efficiencies in the field, allow for easier reporting, and increase
             access to the data.




WisFIRS RFP R2 GIS Development               Page 3 of 47                                   07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management




             1.1.1 WisFIRS Release details
                The releases are organized to contain functionality that “fits” together, staff we are releasing the application to,
                and technology that needs to stay together, otherwise we might end up accidentally breaking other parts of the
                system. A brief definition of what is included in each release, as well as staff impacted (e.g. the number of
                forestry staff this portion will be released to upon completion), the current technology the existing application is
                running under and application integration (e.g. the other applications that this piece fits with).

                Release 1:
                Recon (Planning, Public Land Management, Stands & Treatments) (June 4, 2007)
                         Planning - Harvest constraints to help plan the work needed to be accomplished on public lands.

                         Stands and Treatments - Stands along with their treatments to be tracked and managed. Currently
                         both RECON and PlanTrac provide this capability. The new system will provide one integrated
                         solution.

                         Public Land Management- Properties, compartments, county offices, and DNR offices, the public land
                         search page is the primary component of this sub-system.
                                    Staff Impacted: 120 DNR, 70 County = 190 total
                                    Current Technology: ArcView 3.3 or ArcGIS 9.2, fGIS, not all properties or counties are
                                     using GIS.
                                    Application Integration: Public Financials, Public Timber Harvest, GIS (Public), Finance

                Release 2:
                GIS Public Lands Management




WisFIRS RFP R2 GIS Development               Page 4 of 47                                   07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

                         Definition: GIS Solution – Identifying the “chunk of dirt” you are managing on State and County lands.
                         This includes: creating and editing layers such as stands; map display such as queries, navigation;
                         and selection; as well as GIS output.
                                    Staff Impacted: 120 DNR, 70 County = 190 total
                                    Current Technology: ArcView 3.3 or ArcGIS 9.2, not all properties or counties are using
                                     GIS.
                                    Application Integration: WisFIRS R1, Public Financials, Public Timber Harvest, GIS
                                     (Private), Finance

                Release 3:
                MFL/FCL Admin. & Packet (Petition + Plan) Writer, Letter generation, Private Stumpage and Forestry:
                   PlanTrac:
                       Land Owner - This sub-system primarily manages information about private land owners who are
                       involved in the MFL or FCL programs. It also includes some private land owners who are not involved
                       in the tax programs. (i.e. Stewardship plans).
                         Letters – Supports the creation of templates and the generation of form letters that will be sent to
                         private land owners.

                         Private Land Management - Although the stand and treatment information can be standardized across
                         public and private boundaries, other land management information can not. This sub-system primarily
                         deals with land descriptions. The private land search page is the primary component of this sub-
                         system.

                    MFL/FCL Administration:
                       MFL Management – Supports the administration of the MFL program to include the issuance of orders
                       of entry, denial, transfer, and withdrawal as well as the issuance of correction, amendment, and
                       rescinding orders. Additionally, this sub-system supports the administration of the MFL Certified
                       Group.
                         FCL Management* – Supports the administration of the FCL program to include the issuance of
                         transfer, withdrawal, correction, amendment, and rescinding orders.
                    Private Forestry
                        CF/CPW Management – This new component would help track the Cooperating Foresters and
                        Certified Plan Writers participation, registration, and publication.
                         MFL Plan Referral - Currently the MFL referral process is a semi-automated activity that relies upon
                         spreadsheets. This sub-system deals with the referral list, notifications of offers, notifications of
                         accepted offers, assignment of forester, and a workload matrix.

                         Stumpage* – Private stumpage data entry and calculations; done by the Cooperating Forester Firm
                         Rep. and DNR Forester. Currently this information is submitted on paper and entered by DNR staff
                         into Recon6i. The data entry through Recon6i will be replaced in WisFIRS; Issues surround the
                         aspect of letting Firm reps enter the data rather than having DNR staff do it.

                         Timbersale referral list – Requests from private landowners to get professional forestry assistance in
                         establishing a timber sale go through a referral process similar to the referral process for creating
                         management plans. This has potential to be linked to the mandatory practice list as well. This
                         includes timbersales for all private lands. Currently the mandatory practice list (report) other non-tax
                         practices and Coop Forester “offer” notification.

                         Forestry Assistance Locator - changes required to be made to the Forestry Assistance Locator (FAL)
                         and DNR FR listing by county to read the oracle database, rather than doing the extract.


WisFIRS RFP R2 GIS Development               Page 5 of 47                                  07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

                                Staff Impacted: MFL Admin. DNR/CO (10), Packet Writer (110 DNR, 150 CF) = 270 Total
                                Current Technology:
                                     o MFL: Power Builder 8 (unsupported in April 2004), SAS, SQR (server and desktop),
                                         Unix, Cobol.
                                     o PlanTrac: VB6, MS Access 97, and an InfoTech component
                                Application Integration: Private Financials, Stewardship Plans, Private Timber Harvest,
                                 Forestry Assistance Locator, GIS, Finance

                Release 4:
                Public Financials, County Forest Law, Timbersales, Stumpage Rates
                         Public Financials - Supports the invoicing of counties for severance due. It maintains the loan
                         balances and applies the severance paid from county forest timber sales to the loan balances.
                         Additionally, this sub-system will support the issuance of invoices to logging contractors for timber
                         harvested on a specific sale. It will create a web-based ledger for each sale. This does not exist in the
                         current system. Interaction with Finance’s accounts receivable system will also be involved in this
                         sub-system.

                         County Forest Law – Maintains the official acreage listing, in total and by township, and loan balance
                         for each County Forest. Acreage payments (see private financials) and severance payments to
                         towns (from counties) are dependent on this data.

                         Public Timber Harvest – Supports public timber sales. It primarily tracks the status of timber sales (A-
                         notice, B-notice, and final cutting reports). It would convert the cutting timber sale approval process
                         from a paper chase, to electronic, improving efficiency. It records stand information, value and
                         volume of timber products involved in a harvest. The real time data would improve accuracy of timber
                         sale reporting. Logging contractor information would also be maintained. A number of timber sale
                         reports would be associated with this sub-system. It is anticipated that the accuracy of these reports
                         would improve due to the real time data entry and electronic approvals.

                         Stumpage - Deals with the generation and historical retention of stumpage rates for various
                         species/product combinations. The rates generated form the basis for the rates ultimately published in
                         Chapter NR 46 (private) and the Timber Sale Handbook (public). Currently, both public and private
                         data is included in the rate calculations.
                                    Staff Impacted: 120 DNR, 70 County = 190 Total
                                    Current Technology: In recon 6i; made up of: Oracle forms 6i, SAS, and UNIX.
                                    Application Integration: GIS, Recon, Finance.
                                    Application Integration: GIS, Recon, Finance.

                Release 5:
                GIS Private Lands Management and misc. GIS functions.
                        GIS integration: Identifying the “chunk of dirt” you are managing on MFL and Stewardship lands. This
                        includes: creating and editing layers such as stands; map display such as queries, navigation, and
                        selection; as well as GIS output.
                         NHI, soils Automation – Automating the integration of the NHI portal if the program allows for CPWs to
                         have access to the information, as well as digital soils information

                         Monitoring of Plans:
                         Legacy – DNR private foresters have monitoring responsibilities for legacy projects (easements)
                         yearly. This involves stewardship plan comparisons, MFL plan comparisons, comparing baseline
                         documentation, photos, conservation easements, plans. Each property needs to report annually, and
                         we need to show the FS how these are monitored during our 5 year review.

WisFIRS RFP R2 GIS Development              Page 6 of 47                                   07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management


                         Stewardship- Generating random plans that are in need or monitoring, create a map and report out
                         which plans by region and county the random sample occurred.

                         SAP reporting – Export a report out how many acres of MFL/Stewardship plans occur in the high
                         priority SAP areas for a given year.
                              Staff Impacted: 111 DNR, 78 CPW = 188 Total
                              Application Integration: WisFIRS R3, Private Financials, Stewardship Plans, Private Timber
                                   Harvest, GIS (Public), Finance, Forestry Assistance Locator.

                Release 6:
                Private financials, Private (Tax Law) timber harvest, cost share programs
                        Private Financials - Supports the processing of payments to municipalities for MFL yield and
                        withdrawal taxes; FCL severance, withdrawal and termination taxes; the annual aid payment; and the
                        annual resource aid payment to qualifying counties. Additionally, supports the invoicing for MFL yield,
                        withdrawal, and closed acreage fee as well as FCL severance, withdrawal and termination taxes.
                        Interaction with the WISMART and Finance’s accounts receivable systems are also involved in this
                        sub-system. Plan prep fee for DNR prepared MFL plans.
                         Private Timber Harvest - Supports the private timber sale process. This will primarily track timber
                         cutting notices/reports associated with MFL and FCL orders. Private cutting notices, foresters’
                         approvals, proposed and actual volume, species to be cut, invoices issues (yield and severance tax
                         columns filled out).
                         Cost share programs – tracking WFLGP, WHIP, EQUIP, FLEP, etc. this needs to be easily updated.
                         Landowners, application, application tracking, letters to landowners, expense tracking, treatment
                         extension, routing and approvals, grant payments and cancellations, and transfers. Need to expand
                         this section to include other cost share programs such as, EQUIP, WHIP, SIP Health, CRP, FLEP.
                         These programs continually change, so this section will need to be easily updated.
                               Staff Impacted: 110 DNR, 10 DNR/CO, 78 CPWs = 198 Total
                               Current Technology: Power Builder 8 (unsupported in April 2004), SAS, SQR (server and
                                  desktop), Unix, Cobol, spreadsheets for cost share.
                               Application Integration: GIS for cutting notice map, Stewardship Plans, MFL, Finance.

                Release 7:
                Stewardship plans, FTS enforcement tracking, field data collection, plan monitoring

                         Stewardship Plans - Similar to MFL plans but without the mandatory practices, and can be created by
                         Cooperating Foresters in addition to CPWs and DNR Foresters.

                         School & community forest law - applications reviewed by DNR Foresters, recon completed by DNR
                         Foresters, management plans (either developer or reviewed by DNR Foresters), periodic follow-up.
                         Education plans, timbersales.

                         FTS Enforcement tracking - Tracking various violations (plan violations, cutting violations, failure to file
                         forms, posting violations, etc.), potentially including the sequence of actions, letter generation (some
                         of which is handled by PlanTrac now, information about the violations (types, fines, etc.). The primary
                         advantage to including this (beyond what’s in PlanTrac) would be centralized location of the data. It
                         would also be a potential opportunity to enforce standardized processes, however, this can be a
                         negative as well, since sometimes there’s value in flexibility.

                         Field Data Collection: Supports collection of plot-level data and tools for summarizing the data at the
                         stand-level for entry in to the Recon system. Data management tools will link to GPS coordinates


WisFIRS RFP R2 GIS Development               Page 7 of 47                                    07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

                         captured in the field. The system will allow for review of the data from the field before automatically
                         being uploaded into the WisFIRS application.
                                       Current Technology: Stew plans: PlanTrac, word, enforcement tracking: excel, Field
                                          data collection: paper, or excel.
                                       Staff Impacted: 111 DNR, 78 CPW = 188 Total
                                       Application Integration: GIS, WFLGP, MFL (landowners), Finance

                         Here is a description of the overall project timeline.




             1.1.2 Current GIS Integration
             Currently, R1 of WisFIRS includes Oracle (9i) database, ASP.NET 2005 and MS SQL Reporting Services. There
             is a stand alone GIS option in Release 1, using ESRI’s ArcGIS / ArcView (3.x and 9.x) that interfaces with the
             WisFIRS web system to update all tabular information, passing up a unique ID, as well as the acreage data for
             the stands that have a GIS representation. You can download information from the Oracle database to use for


WisFIRS RFP R2 GIS Development               Page 8 of 47                                 07/21/2010
                                                 RFP #H-048-08 WisFIRS
                                    Technical Guidance and Specifications Appendices
                                             For R2 Phase GIS Development,
                                               Public Lands Management

             mapping and GIS analysis. The goal is to better integrate the GIS data with the tabular data, and storing the GIS
             data in a centralized repository, rather than individual desktops throughout the state. In addition to the R1
             requirements, Release 3 which focus on the private forestry business (functionality represented by the current
             Managed Forest Tax Law and PlanTrac applications), will require GIS to be fully integrated into the business
             practices. This development effort will be proceeding at the same time as the Release 2 GIS integration, and the
             GIS integration will occur in a future release of WisFIRS (Release 5).


             1.1.3 Hardware / Software Environment
             The DNR GIS server architecture is currently represented in three application environments:
                 Development
                 User Acceptance (UAT)
                 Production

             Each environment contains its own GIS web servers, ArcIMS Servers, ArcGIS Servers, ArcSDE and Oracle
             databases. Other than database links, connections from one environment to another are not currently allowed.

             In the current DNR environment, all GIS web applications use the GIS web servers rather than the general-
             purpose web servers. The ArcIMS connector libraries and ArcGIS Server ADFs are installed on the GIS web
             servers.

             The following sections detail the exact programming specifications, hardware and Commercial off-the-shelf
             (COTS) constraints under which the application must be built. The provided solution must ultimately adhere to
             the DNR’s software development methodology (called the System Development Framework (SDF)) and other
             constraints listed in this section of the document.



             1.1.4 Hardware / COTS Software Specifications
             This section describes the existing DNR production environment. This section describes the production
             configuration against which the recommended solution must operate. The Production DNR GIS environment will
             be at the described minimum hardware and software release for WisFIRS R2 deployment.

             The provided solution must be an ESRI-based and compatible solution. It must be forward-looking and take into
             account, to the extent possible, future releases of WisFIRS including field data collection and mobile deployment
             of mapping functionality (R7).


        HARDWARE – MASS STORAGE HARDWARE
        Production GIS Windows Servers. All disk space on Windows servers come from a mirrored SAN, which will continue
        to change over the next year as the new solutions require increased capacity, security and new availability
        requirements.

         Public Web Server               Configuration Element       Description
                                         Server Mfg                  Proliant BL35pG1
                                         OS Version                  Windows 2003
                                         Service Pack                Service Pack 2
                                                                     Two Dual Core 2.2 GHz AMD Opteron
                                         CPU                         Processor 275
                                         Memory                      4856 MB
                                         NIC                         HP NC370i gigabit adapters

WisFIRS RFP R2 GIS Development             Page 9 of 47                                  07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management


                                     Network Speed           2 GB/s


         Intranet Web Server
                                     Server Mfg              IBM eServer BladeCenter LS20
                                     OS Version              Windows 2003
                                     Service Pack            Service Pack 2
                                                             Two Dual Core 2.2 GHz AMD Opteron
                                     CPU                     Processor 275
                                     Memory                  4096 MB
                                     NIC                     Broadcom NetXtreme Gigabit adapters
                                     Network Speed           1 GB/s

         ArcIMS Application Server
                                     Server Mfg              IBM eServer BladeCenter LS20
                                     OS Version              Windows 2003
                                     Service Pack            Service Pack 2
                                                             Two Dual Core 2.2 GHz AMD Opteron
                                     CPU                     Processor 275
                                     Memory                  4096 MB
                                     NIC                     Broadcom NetXtreme Gigabit adapters
                                     Network Speed           1 GB/s


         ArcIMS Spatial Server
                                     Server Mfg              IBM eServer BladeCenter LS20
                                     OS Version              Windows 2003
                                     Service Pack            Service Pack 2
                                                             Two Dual Core 2.2 GHz AMD Opteron
                                     CPU                     Processor 275
                                     Memory                  8192 MB
                                     NIC                     Broadcom NetXtreme Gigabit adapters
                                     Network Speed           1 GB/s


         ArcGIS Server
                                     Server Mfg              IBM eServer BladeCenter LS20
                                     OS Version              Windows 2003
                                     Service Pack            Service Pack 2
                                                             Two Dual Core 2.2 GHz AMD Opteron
                                     CPU                     Processor 275
                                     Memory                  4096 MB
                                     NIC                     Broadcom NetXtreme Gigabit adapters
                                     Network Speed           1 GB/s


         ArcSDE Service Server

WisFIRS RFP R2 GIS Development         Page 10 of 47                          07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

                                           Server Mfg                   IBM eServer BladeCenter LS20
                                           OS Version                   Windows 2003
                                           Service Pack                 Service Pack 2
                                                                        Two Dual Core 2.2 GHz AMD Opteron
                                           CPU                          Processor 275
                                           Memory                       4096 MB
                                           NIC                          Broadcom NetXtreme Gigabit adapters
                                           Network Speed                1 GB/s


         Oracle Database
                                           Oracle Dev
                                                              version   Oracle9i (9.2.0.8.0)
            part of Enterprise database
                                   farm                           OS    HP-UX
                                           Oracle UAT
                                                              version   Oracle9i, updating to 10g in 2008
                                                                  OS    HP-UX
                                           Oracle Prod
                                                              version   Oracle9i
                                                                  OS    HP-UX



             1.1.5 Performance
             It will be important for the DNR to simplify their mapping content to the extent possible (i.e., thin data that creates
             performance impacts) and have all imagery loaded into ArcSDE. Based on other’s experience ArcIMS renders
             maps faster than ArcGIS Server. Within the DNR’s architecture it’s unclear whether that will be the case due to
             the capacity of ArcIMS. Early deployments for testing in the DNR’s environment is required to make a final
             decision on which rendering software to use. If the application is written in ArcIMS, it must be written to easily
             migration to ArcGIS Server for display when that product improves.


             1.1.6 Programming Specifications
             Application development in the DNR also needs to follow the DNR’s software development lifecycle methodology,
             known as the System Development Framework (SDF). The SDF is based on other application development
             frameworks, such as RUP.
              The application should be written for Microsoft Internet Explorer 6.0 and above.
              All code for web services and the web-based solution should be written in Microsoft VB.NET or C#.NET
                 technologies and ArcGIS Server 9.2 (at a minimum) or ArcGIS Server 9.3 (if it is determined that use of this
                 version will fit into agency plans) within the Microsoft .NET Framework 2.0.
              The user interface should be written using HTML, Cascading Style Sheets (CSS), and JavaScript.
                 This interface should utilize standard technologies, specifically Adobe Flash Versions 8 or 9 and AJAX
                 preferably Control Toolkit for .NET 2.0, to consume any required web service methods and present results to
                                                                                              rd
                 the user. Other implementation of AJAX with the exception of any locked 3 party plug-ins would also be
                 acceptable.
              The use of standard ESRI “out-of-the-box” capabilities should be leveraged throughout the project where
                 possible. These can include, but are not limited to, ESRI standard controls and Server and SOAP APIs.
                 o The ADF provides a COM-based interface into the core ArcObjects.


WisFIRS RFP R2 GIS Development              Page 11 of 47                                    07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

                 o    The SOAP API provides an XML-based interface into the core ArcObjects
                 o    Custom .NET web services interface directly against the core ArcObjects
                 o    Ultimately, all above scenarios operate against the core ArcObjects and are sanctioned approaches by
                      ESRI
                 o    The ESRI bundled controls are part of the ADF and “bundle” functionality found in the ADF.
                 o    Use of the ADF may require additional licensing (i.e., any server that has the ADF installed will require an
                      ArcGIS Server license).
                 o    As the ADF requires the use of COM and COM-ports, issues may be experienced when trying to
                      configure the firewall and communicate using COM across the firewall. The use of the SOAP API or
                      custom .NET web services may eliminate these port requirements as they communicate through more
                      standard ports.
                 o    At 9.2, the ESRI controls contain some degree of extensibility and are AJAX-enabled. For this reason,
                      they may warrant consideration in a solution.
                       The extent of “extensibility” should be understood to limit risk in choosing this scenario
                 o    The performance overhead associated with using the ADF, or derived controls, should be known and
                      considered as part of the software architecture / design.
                       Source code should be delivered to DNR as a Visual Studio 2005 Solution. All code should be
                          documented using in-line comments where necessary. Source code should be neat and well-
                          organized to facilitate review by DNR staff as necessary.
                       Application Programming Interface (API) documentation on all the source code should be delivered
                          in form of CHM, HxS-format, MSDN-style documentation or another approved format.
                       Any automated build scripts used should be included. Detailed instructions on how to build and
                          deploy the system should be provided.
                       DNR should receive the source code and have rights to use derived products within other DNR-
                          specific projects.
                       Reporting should be done through the use of Microsoft SQL Server Reporting Services components
                          or leveraging the DET SQL Server Reporting Services server.
                       All internal standards defined in the SDF documentation must be adhered to in addition to leveraging
                          the above stated technologies.
                       The solution must meet DNR database and application standards (such as security, branding,
                          coding)


             1.1.7 Development Model
             It is expected that the R2 interface can be developed primarily off-site. This is possible based on the scoped
             approach and preexisting R1 interface. It is not expected that GIS capabilities will be directly built into the R1
             interface – beyond a quick map and link to the mapping portal. The quick map and linking to R2 will not require
             that installation of GIS or ESRI technologies into the R1 solution.

             This model for development should work well. Other development models such as VPN and collocated Visual
             Source Safe (VSS) solutions may be problematic from a performance and productivity perspective.

             The vendor is responsible for all hardware and software required to “replicate” the DNR’s Development, User
             Acceptance Testing and Production environment to the extent possible on their servers if the vendor will not be
             physically located at the DNR office in Madison, Wisconsin. This is to minimize deployment risks and issues
             related to inconsistencies in the source and target environments. This “replication” would include ESRI versions
                                                                     rd
             and products, Microsoft technologies and associated 3 party tools.

             A “work-able” solution for both the supplying vendor and the DNR should be negotiated as related to deployment
             intervals and approach. An initial deployment should occur early on in the project to minimize risk and highlight
             inconsistencies in the Vendor and DNR Development environments. As major milestones are reached (e.g.,
             module completion) deployments to the DNR’s environment should occur.


WisFIRS RFP R2 GIS Development              Page 12 of 47                                  07/21/2010
                                                 RFP #H-048-08 WisFIRS
                                    Technical Guidance and Specifications Appendices
                                             For R2 Phase GIS Development,
                                               Public Lands Management

             It is recommended that deployments be directed to the DNR’s Development Environment. Deployment to the
             Development Environment will allow both parties to refine deployment guides, scripts and associated issues.
             Once a release is stabilized in the Development Environment, the DNR will be responsible for “promoting” the
             release to the Testing Environment. User Acceptance Testing (UAT) will be leveraged for formal testing. Once
             accepted in UAT, the DNR will “promote” the release to the Production Environment. No active development
             changes will occur either in UAT or the Production Environments. The DNR will work will make the required
             ArcSDE data layers available in the Development, UAT and Production Environments as well as the required
                                     rd
             ESRI, Microsoft and 3 party supporting technologies. To minimize risk, it is imperative that DNR staff perform
             this “promotion” activity early in the project.

             The DNR is able to supply laptop computers, Virtual Private Network (VPN) access and accounts to facilitate
             network access, code deployments to development and staging environments.

              The DNR will additionally be able to facilitate ready access to data, databases, existing source code for any data
             structures and records, database schemas, application code or other objects. All DNR-provided content should
             be treated with confidence and contractors will exercise secure control over the original materials and media and
             over any and all copies of received content.

             The DNR will provide a technical lead contact person to serve as the Single Point-of-Contact for all
             deployments and technical issues. This would be in addition to the DNR’s project manager, who will continue to
             be the contact for the overall project details.


             1.1.8 User Interface
             A graphic designer will need to work with a subset of users to develop a user interface that works well with the
             existing application and is intuitive to the end users. As part of the development process, sample screen
             interfaces should be developed to articulate the placement of various required elements. User Interface
             requirements include:
              The interface design will be designed for a minimum screen resolution of 1024 x 768
              Navigation between the current WisFIRS application and the mapping UI to be developed must be
                  straightforward and feel “integrated” even if the two systems are largely independent
              The mapping UI must be designed to “match” the current WisFIRS look and feel.
              UI design must facilitate logical workflow, to the extent possible.




WisFIRS RFP R2 GIS Development             Page 13 of 47                                  07/21/2010
                                                 RFP #H-048-08 WisFIRS
                                    Technical Guidance and Specifications Appendices
                                             For R2 Phase GIS Development,
                                               Public Lands Management




             1.1.9 Database Design
             Most application developers rely heavily on database tables for many management functions including user
             access to data layers, fields of information, report content, application behavior (e.g., zoom scales) and other
             generic configurations. This is true with the WisFIRS application as its content is database driven. All future
             design and development work should be driven against a normalized database schema complete with data
             integrity rules, domains and constraints.


             1.1.10 Database Design Methodology
             The Design of the database to support an application is one of the most important aspects of any project. The
             success and on-time completion of the project is highly dependant on a normalized and properly developed
             database. Mid-stream database schema changes can have substantial impacts on any application. The


WisFIRS RFP R2 GIS Development              Page 14 of 47                                  07/21/2010
                                                 RFP #H-048-08 WisFIRS
                                    Technical Guidance and Specifications Appendices
                                             For R2 Phase GIS Development,
                                               Public Lands Management

             application developed will need a well-defined database structure to support the detailed functional requirements
             provided by DNR.

             All databases should be modeled, initially, in Visio using data modeling extensions. This provides a visual
             representation and tool for creating the necessary database referential integrity and domain constraints that are
             so important for data integrity and application consistency.

                    1.1.10.1 Spatial Table Dictionary

                    A Data Dictionary has been provided showing the core spatial layers to be managed:
                               Properties
                               Stands (RECON)
                               Completed Treatments
                               Ancillary Layers
                               Staging Layers
                               Historic Layers

             Also included are staging versions of the core properties and ancillary GIS layers for the custom creation of
             features (points, lines and polygons).




WisFIRS RFP R2 GIS Development             Page 15 of 47                                  07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management




        2.0 IMPORTANT NOTES ON DATA
        These sections are provided for information purposes only and apply if ArcIMS will be the image-rendering engine in
        the design. Currently, using ArcIMS for the presentation tier may be more efficient than using ArcGIS Server. ESRI
        ArcGIS Server, while great for many applications (e.g., True Clipping) that ArcIMS does not support, is slower to
        render images. As stated in the performance section, if the application is written in ArcIMS, it must be written to easily
        migration to ArcGIS Server for display when that product improves.

        We see no impact to WisFIRS R2 from the below items; however, they are documented for informational purposes.
        Coded Domains - ArcIMS is not geodatabase “aware” meaning geodatabase subtypes, domains and ranges are not
        recognized by ArcIMS in the same manner as they are in ArcMap or ArcCatalog. Utilities exist to make domain data
        available through ArcIMS and can be implement as required. The DNR desires to see the “real” value of a given
        attribute (e.g., Upland, Industrial, 10” Main, etc.) as opposed to the coded values (e.g., 1, 2, 3) which will make no
        sense to end users, this solution will need to be implemented.



WisFIRS RFP R2 GIS Development              Page 16 of 47                                  07/21/2010
                                                 RFP #H-048-08 WisFIRS
                                    Technical Guidance and Specifications Appendices
                                             For R2 Phase GIS Development,
                                               Public Lands Management

        Annotation - ArcIMS also does not support ESRI annotation features. Solutions exist for displaying annotation
        features and can be used to accommodate the DNR’s needs. If the DNR desires to show annotation layers, this
        solution will need to be implemented. This option may require additional maintenance and will need to be discussed
        further with the DNR.
        Raster Data - Using ArcIMS to serve file-based (e.g., TIFs, SIDs) raster data can have severe performance limitations.
        Image formats (to be accepted by the WDNR), locations, and file-sizes all play a part in the responsiveness of ArcIMS.
        For this reason, we anticipate having all orthophotography / raster data loaded into ArcSDE. ArcSDE will store the
        raster data much more efficiently. Through pyramiding and indexing, retrieving the raster data will speed up
        exponentially.


        2.1 DNR Responsibilities
        During the implementation of the WisFIRS R2 project, the DNR and their constituents will have various technical
        responsibilities to insure successful delivery.

        These have been listed at a high-level in the section included below.


             2.1.1 Symbology / Cartography
             DNR and their constituents will be responsible for supplying the cartographic representation for their GIS data.
             An MXD or ArcIMS AXL file should be delivered with the GIS data supporting the AXL or MXD. This MXD / AXL
             will include:
                    GIS layers to display
                    Scale thresholds for provided layers display
                    Initial layer display (on / off)
                    Primary display field for identify / select operations
                    Primary and other candidate label fields
                    Label fonts / colors / sizes / scale thresholds for display
                    Colors (normal state and highlight / selected state)
                    Symbology
                    Thematic Group (e.g., Environmental, Transportation)
                    Map north arrow styles
                    Map scale bar specification
                    Thematic rendering symbology (e.g. colors for displaying stand types thematically)
                    Short and long report fields (i.e., which attributes should come back initially and which should only be
                       shown when the user want to see a long report)



             2.1.2 Business Objects
             The DNR technical members responsible for the development of WisFIRS R1 have developed a tiered
             architecture which includes a Data Access Layer, Business Logic and Presentation Layer. Use of these existing
             business objects will be important to the success of the project from several perspectives. They will insure data
             records are accessed and edited in a consistent manner. They will also reduce change / configuration
             management efforts to the overall system if used consistently. If all developers accessing common business
             content are using the same core code – much risk and overhead will be minimized. DNR technical staff should
             make available all core business objects.




WisFIRS RFP R2 GIS Development             Page 17 of 47                                 07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

             2.1.3 Unique Keys
             The generation of unique values in the system may be important for new GIS / Business content originating from
             the R2 mapping interface. It is expected that the DNR technical staff will provide the necessary business objects
             / stored procedures / logic to create and manage unique key values.



             2.1.4 Ancillary Features List
             A requirement in this document includes the ability to create ancillary GIS features, i.e. those kinds of features
             whose display enhances the users cartographic expression but for which no business attribution (data) are
             collected, such as fence rows, streams and rights-of-way. DNR and their constituents will be responsible for
             providing a list of these features to be captured and data type (e.g., polygon).



             2.1.5 Display Fields / Attributes / Report Formats
             The display of data both from the mapping interface and through generated reports will need to be defined by
             DNR staff and constituents. The specific attributes to display for on-screen display as well printed material will
             need to be defined.


        2.2 Anticipated Users
        The user community for this system is diverse, but primarily foresters.
            230 DNR foresters (internal to DNR network)
            70 county foresters (external to DNR network)
            Future users: 150 independent consulting foresters (external to DNR network)


        2.3 Current GIS Technology Use
               10% ~ power users using ESRI products (ArcView 3.x or 8-9.x) into their work and look for opportunities to
                exploit GIS technology
               40% use the basic GIS features of ESRI products for some of their work
               30% rely on fGIS – a free GIS solution build by the Division of Forestry and the University of Wisconsin based
                on TatukGIS technology.
               ~ 20% do not use GIS technology.


        2.4 Security
        The county and independent foresters would be considered external users and need to access the systems from the
        internet.


        2.5 Connectivity
        Monday – Friday, 7 am – 5 pm. Downtime 1-2 days is OK during one instance, more than that might become
        problematic. If this is repeated more than once a month, reconfiguration of application and or architecture might be
        required.

        Network bandwidth varies between 256K – T1 connections. Some DNR offices may be able to be bumped up to 512K
        connections if application requires more bandwidth.



WisFIRS RFP R2 GIS Development              Page 18 of 47                                   07/21/2010
                                                 RFP #H-048-08 WisFIRS
                                    Technical Guidance and Specifications Appendices
                                             For R2 Phase GIS Development,
                                               Public Lands Management

        3.0 APPLICATION FUNCTIONALITY

        3.1 WisFIRS R1 Integration Functionality


             3.1.1 Function Description - Launch to Map Portal from R1 (Individual Record)




            Users will be presented with a Globe Icon Graphic for each record (e.g., Property, Stand). If a GIS shape exists,
            this Icon will be Green. If no GIS shape exists, this icon will be red.

            When the user places their mouse over the globe icon, they will be presented with 2 options:
               Quick Map
               Full Map

            Quick Map: Users will get to preview selected GIS features from within R1 interface through a “Call-out” map.
            This map will be termed a Quick Map throughout this document. The Quick Map will be a simplified small map
            window with minimal capabilities.

            Full Map: Users will use a button on the WisFIRS R1 user interface to open and move users from WisFIRS R1 to
            the Map Portal. This interface will be a fully functional GIS portal with advanced editing tools.

            Various levels of information may exist in R1 at the point of this Launch request including the Property,
            Compartment, Stand and / or Completed Treatment. The R1 interface will send along the most information
            possible at the time. In response, the Map Portal should zoom to the extent of the information provided.



WisFIRS RFP R2 GIS Development             Page 19 of 47                                 07/21/2010
                                                 RFP #H-048-08 WisFIRS
                                    Technical Guidance and Specifications Appendices
                                             For R2 Phase GIS Development,
                                               Public Lands Management

            If a Property is included in the R1 Map Portal launch request, this Property should be set as the Working Property
            in the Map Portal.

            Those “launch” points are described as follows:
                      Properties Tab                                             Recon Tab
                      Properties sub-menu                                        Compartments sub-menu
                      Core Property Group sub-menu                               Stands sub-menu
                      Custom Property Group sub-menu
                      Treatments Tab                                             Planning Tab
                      Scheduled treatments sub-menu                              Harvest Schedule sub-menu
                      Completed Treatments sub-menu                              Cultural Treatments sub-menu
                                                                                 Tuning Schedule sub-menu

            * DNR Staff will work with the vendor to construct the calling launch request formats and develop the launch points
            within the R1 interface.




             3.1.2 Function Description - Launch to Map Portal from R1 (Multiple Records)
             Users will use a button on the bottom of the WisFIRS R1 user interface to open and move users from WisFIRS
             R1 to the Map Portal. Various levels of information may exist in R1 at the point of this Launch request including
             Property, Compartment, Stand and / or Completed Treatment identifiers. The R1 interface will send along the
             most information possible at the time. In response, the Map Portal should zoom to the extent of the information
             provided.

             If a Property is included in the R1 Map Portal launch request, this Property should be set as the Working Property
             in the Map Portal.

             Those “launch” points are described as follows:
                       Header                                                     Properties Tab
                       Launch to Map Icon (zoom to state)                         Properties sub-menu (zoom to property)
                                                                                  Core Property Group sub-menu
                                                                                  Custom Property Group sub-menu
                        Recon Tab                                                 Treatments Tab
                        Compartments sub-menu                                     Scheduled treatments sub-menu
                        Stands sub-menu                                           Completed Treatments sub-menu
                        Planning Tab
                        Harvest Schedule sub-menu
                        Cultural Treatments sub-menu

             * DNR Staff will work with the vendor to construct the calling launch request formats and develop the launch
             points within the R1 interface.




WisFIRS RFP R2 GIS Development             Page 20 of 47                                 07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management




             3.1.3 Function Description - Launch to R1
            Users will be able to link back to the R1 interface from the Map Portal to display business records of interest.

            Users will be able to generate a single or list of Properties, Stands or Completed treatments through the map
            selection tools identified in this document.

            Using this list, users will be able to “launch” back to the R1 interface detailing business content for selected GIS
            features.

            * DNR staff will build and expose web services that will accept a feature type (e.g., stands) and single, or list of,
            properties. R1 will display business content for all feature IDs sent in the request.


             3.1.4 Function Description - Orphans List
             Users will get feedback for which records are missing shapes or shapes that are missing complete data. This will
             be termed the Orphans List throughout this document.

             Users will need a mechanism to resolve “orphans”. These orphans can exist under two conditions:
                Business record attribution (e.g., stand) exists with no GIS feature (e.g., stand boundary).
                A GIS feature exists with no business record attribution.

             The exact location for the interface that will provide the functionality to resolve these issues has not been
             determined, but it is recommended that it be displayed in a dashboard-like interface window.

             At a minimum, the mapping component of WisFIRS will be responsible for providing, through a .NET web
             service, a list of shapes in GIS based on Property, Compartment, Stand and Completed Treatments. It is
             expected that this will be married up with business records on the R1 interface to identify spatial and business
             record anomalies.

             Users will be able to launch to the business attribution details or mapping interface of a given record displayed in
             the Orphans list. A hardcopy report of the Orphans list will be available for users to print.


             3.1.5 Function Description - Entitlement
             The WisFIRS R1 component tracks users and their ability to edit properties. A property must exist in the R1
             application prior to digitizing a property boundary and the given user must be granted permission to edit that
             property. The R2 GIS component of WisFIRS must limit users from creating Stands and Completed Treatments
             by consulting core R1 entitlement database tables or exposed business logic.

             The current entitlement scheme should support a role-based framework that will allow selected functionality to be
             available to selected users (e.g. Orphans lists for administrators vs. authorized editors, etc. or Local data upload
             authority)


             3.1.6 Function Description - Minimum Resolution
             The user interface should be developed to support a minimum resolution of 1024X768. The interface can
             support higher resolutions but will not be required to support lower resolutions.




WisFIRS RFP R2 GIS Development              Page 21 of 47                                    07/21/2010
                                                   RFP #H-048-08 WisFIRS
                                      Technical Guidance and Specifications Appendices
                                               For R2 Phase GIS Development,
                                                 Public Lands Management




        4.0 MAP DISPLAY
        4.1 Function Description - Layers List
          WisFIRS Map Portal will have a thematically organized layers library used for reference, editing, and map-making

          All layers to be included in the mapping portal will be displayed in a layers list.

          Control over layer groupings will be managed centrally through database tables allowing for easy management and
          reassignment of a given layer to a thematic group.

          Thematic groups should be expandable and collapsible using a graphics symbol (e.g., plus / minus).

          Users will have a My Layers tab on the interface. This tab will contain any Staged Stands or Completed Treatments
          pushed from Desktop R2. This tab will additionally contain any locally uploaded data.

          * DNR Staff will provide all thematic categories and layer assignments

        4.2 Function Description - Viewing Historical Polygon Data
          Users will need to view the changes in geographic extent through time of specific layers whose historical changes
          are deemed business critical. The features of value within these layers will be archived (stored in the database) for
          future reference. The features will only be viewable once a user request has determined which features to display,
          because showing all “Historic” features that have accumulated over time would result in a cluttered map.

          PUBLIC (R1): Users will need to view Historic feature geometry based on date range for completed treatments on
          Public Lands.

          Each shape must store date/time created, date/time archived.
              User selects Historic layer they want to query/view
              User selects active date range: start date; end date defaults to match start date; user optionally enters
                 different end date;
              User runs query that initiates a definition query where all features in selected layer that were “active” in time
                 range defined;
              Results displayed on screen
              User clears display when finished

        4.3 Function Description - Dynamic labels for GIS features
          For each GIS layer to be included in the Map Portal, a default label should be provided for each feature.

          For defined GIS layers in the Map Portal, secondary label fields should be supported allowing for the dynamic
          alteration of feature labeling. For example, a user could choose to have a stand labeled by Stand Number or
          Acreage or Stand Number and Acreage.

          * DNR staff will provide default and candidate label fields and display / symbology characteristics

        4.4 Function Description - Legend
          A label will be available on the Map Portal and will display all active layers for the map.

        4.5 Function Description - North Arrow
          A north arrow will be provided on the Map generated by the Map Portal.


WisFIRS RFP R2 GIS Development               Page 22 of 47                                      07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

          * DNR staff will provided the arrow design style from the list of candidate styles from ESRI.

        4.6 Function Description - Scale Bar
          The Map generated by the Map Portal will include a scale bar.

          * DNR staff will provide scale bar specifications based on candidate styles available through ESRI technologies.

        4.7 Function Description - Attribute-based symbology / thematic mapping
          Users should have the ability to create thematic maps dynamically. For example, a user may wish to thematically
          render a map based on Stand Condition or Stand Type.

          * DNR staff will provide layers, attributes and symbology for thematic mapping.
          * DNR would provide colors for each unique value

        4.8 Function Description - Upload of local layers
          Users need to upload their own local vector datasets for use as reference and map display.
          Users will be able to upload shapefile content. Uploads will only be supported that contain all required shapefile
          components, valid geometry and projection specifications. Any raster (air photo) data that needs to be displayed will
          need to be loaded into the database by an administrator.

          Users will provide a user-friendly name for uploaded data.
          Users will have the ability to delete, from the server, uploaded data.
          Users will be able to turn on/off uploaded data layers limiting display.
          Users will have minimal control over the display of uploaded content beyond setting the default color.
          Users will manage uploaded content through a lightweight administration panel allowing for:
              Content deletion
              Color changes
              Display name changes

        4.9 Function Description - Measure Area
          Users will be provided a button on the Map Portal that will allow for area measurements.

          As the user creates inflection points, the map display will reflect the last segment length, total perimeter and area
          dynamically.

          The map must not be regenerated for each inflection point.

          The users will complete the area measurement by double-clicking the map.

          The user will clear the measurement area from the screen by selecting the Clear Button from the user interface.

          * DNR staff will provide the units (e.g., feet, acres) to be included for line and area measurements.




WisFIRS RFP R2 GIS Development              Page 23 of 47                                   07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

        4.10 Function Description - Measure Distance
          Users will be provided a button on the Map Portal that will allow for linear measurements.

          As the user creates inflection points, the map display will reflect the last segment length and total line length
          dynamically.

          The map must not be regenerated for each inflection point.

          The users will complete the linear measurement by double-clicking the map.

          The user will clear the line from the screen by selecting the Clear Button from the user interface.

          * DNR staff will provide the units (e.g., feet, meters) to be included for line measurements.

        4.11 Function Description - Map Templates
          The user will be provided a series of pre-defined templates. Each template will include a name (e.g., Working Map,
          Timber Sale, and MFL). Once selected, the template will drive the formatting of the map including which layers are
          turned on / off. These will be used to define a standard set of layers for various cartographic, viewing or reporting
          options.

          * DNR will provide a defined set of templates. For each template, the required layers to be turned on will be
          provided. All other layers will be assumed to be turned off.

        4.12 Function Description - Display latitude / longitude Coordinates
          The application must display the Latitude and Longitude coordinates on the screen interface. The exact location of
          this display is up to the contractor but should be in the lower left section of the interface.

          The latitude / longitude should update dynamically on mouse movement within the map interface.

        4.13 Function Description - Map Bookmarks
          Users will be able to save and retrieve Map Bookmarks. Bookmarks, when created will save current extent and
          layer visibility. User will give the bookmark a name before saving. Users will be able to delete Bookmarks from their
          list.


        5.0 MAP NAVIGATION
        5.1 Function Description - Reset Map
          Users will be provided a button on the user interface to allow for Resetting map content.

          This button, when pressed, will zoom the user back out to the full, original, extent of the map. This function will reset
          the map to its original state. All selections and results will be cleared and the layer list will be set back to default.

        5.2 Function Description - Zoom In
          Users will be provided a button on the user interface to allow for zooming in on the map.

          Users will be able to Zoom In using one of 2 methods. The user can either perform a single left-mouse-click
          operation on the map which will re-center the map at the location of the user’s click and zoom in by a factor of 2 or
          left-drag a box to define the new map extent. Upon releasing the mouse, the map will refresh to the defined box
          extent.

          For the “left-drag” option defined above, a shaded polygon showing the users desired zoom extent must be
          displayed dynamically.

WisFIRS RFP R2 GIS Development              Page 24 of 47                                   07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management


          For the “left-drag” option defined above, a dashed line showing the actual extent of the map that will be created must
          be displayed.

        5.3 Function Description - Zoom Out
          The user can either perform a single left-mouse-click operation on the map which will re-center the map at the
          location of the user’s click and zoom out by a factor of 2 or left-drag a box to define the new map extent. The new
          map extent will be calculated as a proportion of the user-defined box and the current map extent. The larger the
          rectangle drawn, the less zoomed out the new map will be.

          For the “left-drag” option defined above, a shaded polygon showing the users desired zoom extent must be
          displayed dynamically.

        5.4 Function Description - Pan / Re-center Map
          Users will be provided a button on the user interface to allow for panning the map.

          The Pan Button, once selected, will allow the user to either single-left-click on the map to re-center the map to that
          point or left-mouse-drag to move the entire map a certain direction. The map will be refreshed to the new extent
          once the left mouse button is released.

        5.5 Function Description - Pre-defined Zoom To Features (Termed Quick Searches within this
        document)
          Users will be provided with a drop-down list of pre-defined Quick Searches on the main Map Portal Interface screen.

          Selections from the primary drop-down will include:
          Zoom to PLSS
          Zoom to County
          Zoom to Lat/Long
          Zoom to Absolute Scale (1: N)
          Zoom to Relative Scale (1” = N)

          Upon selecting a primary drop-down, users will be presented with either a text entry box (e.g., scale) or defined set
          of options in a secondary drop-down list (e.g., county list). Additional drop-down or text boxes may be required to
          support zooming to features (e.g., lat/long as distinct data entry text fields).

          Zoom to Property – will require entry of a property value only
          Zoom to Compartment – will require entry of a property and compartment value
          Zoom to Stand – will require entry of a property, compartment and stand value
          Users will be presented with the valid values in a cascading manner (e.g., user selects a Property and presented
          with a list of valid compartments, etc.).
          If a user provides only a property value, they are zoomed to the property boundary.
          If a user provides a Property and Compartment, they are zoomed to the Compartment extent.

          * DNR will provide tables of information to support quick searching of defined sets (e.g., county lists).

        5.6 Function Description - Zoom Bar / Zoom to Fixed Scale or Extent
          The main interface of the Map Portal will contain a tick-based zoom bar with zoom in / out buttons on each end.
          Clicking the tick marks will zoom the user to the corresponding scale at the center of the current map extent.
          The accompanying zoom in/out buttons on the Zoom Bar will allow the user to adjust the selected tick mark (i.e.,
          selecting the Zoom Out will take the user to the next tick mark to the right).




WisFIRS RFP R2 GIS Development              Page 25 of 47                                   07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management




          * DNR will provide a list of scales and corresponding descriptions (e.g. 1:24000, 1 mile, County).

        5.7 Function Description - Zoom to Previous Map
          Users will have a button on the main Map Portal that will allow them to zoom to the previous map made. This will
          only allow them to zoom to the last map rendered.


        6.0 MAP SELECTION

        6.1 Function Description - Active Layer(s) Designation
          Users must choose the Active layer(s) to ensure all Identification and Selection options operate against the correct
          layers (e.g., properties, stands, streams, roads, etc.).

          This will be built as a list box with checkbox options. Layers presented must be dynamically pulled from the
          application framework.

          Users will be trained on the impacts associated with selecting large extents against multiple layers of data. This is a
          known and stated performance risk.

        6.2 Function Description - Select By Box
          Users will be presented with a button on the user interface that allows for the drawing of a “box” or “rectangle” that
          “touches” the features they want to select.

          This tool will operate only against the Active Layers defined.

          This tool will allow for feature selection by either clicking a single point or left-dragging the mouse to create a
          rectangle / box.

          Selected features will be highlighted on the map.

          If the user chooses to drag a box, this tool will dynamically show a preview of the selection area as the user drags
          moves the mouse.

        6.3 Function Description - Select By Poly
          Users will be provided a button on the Map Portal that will allow for polygon-based selections.

          As the user creates inflection points, the map will display the polygon dynamically.

          The map must not be regenerated for each inflection point created.

          The users will complete the polygon selection by double-clicking the map.

          This tool will operate only against the Active Layers defined.


WisFIRS RFP R2 GIS Development               Page 26 of 47                                   07/21/2010
                                                   RFP #H-048-08 WisFIRS
                                      Technical Guidance and Specifications Appendices
                                               For R2 Phase GIS Development,
                                                 Public Lands Management



        6.4 Function Description - Select By Point / Identify
          Users will be provided a button on the Map Portal that will allow for point selections.

          Users will click once to select a feature against the Active Layer

          This tool will operate only against the Active Layers defined. It will not function against layers such as Imagery.

          A method will be developed to “deselect” previously selected features.

        6.5 Function Description - Select By Buffer using Existing Features
          The buffer option will be presented after the initial features have been selected using one of the previously described
          tools (e.g., select by box).

          Upon selecting the buffer tool, the user will have the ability to buffer out a set distance and units (e.g., 1 mile, 10
          feet).

          Optionally, users will be able to select features from the same or a different layer. If the users desires to perform the
          buffer select, the original feature will be buffered and all features in the intersect layer that are touched by the buffer
          extent will be returned.

          * DNR to provide units to be supported (e.g., ft / miles / acres etc).

        6.6 Function Description - Clear Selection
          Users will be provided a button on the Map Portal that allows for the “clearing” of selected features.

          This tool will be valid after a selection has been made through one of the previously described tools (e.g., select by
          polygon).

          When this button is pressed, it will clear all highlighting and results screen. The map will refresh.

        6.7 Function Description - Show Results
          The Map Portal interface must present selected features, and a limited amount of attribute information, to users.

          Results will be presented with a Short Report list of attributes.

          From this results “panel”, users must be able to link back to the WisFIRS R1 interface for Properties, Stands and
          Completed Treatments. See WisFIRS integration section.

          Users must also have ability to de-select by shape in the event of exactly or nearly exact overlapping shapes (where
          on-screen de-selection is difficult or impossible)

          * DNR staff will provide the short report attributes list per layer.


        7.0 MAP EDITING

        7.1 Function Description - Working Property Selection
          Users must choose a “Working” Property to ensure all edits to business layers get properly affiliated with the correct
          Property designation.



WisFIRS RFP R2 GIS Development                Page 27 of 47                                   07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

          From the Map Portal, users must be able to select a property from their list of granted properties. This selected
          property will persist until changed and will be a prerequisite to all subsequent editing operations.

          The Working Property will additionally be set when the Map Portal is called from the WisFIRS R1 interface.
          Example: User is in the R1 interface, searches for stands within a property, then chooses to launch to the Map
          Portal. This launch request must carry with it the Property designator and set that as the Working Property in the
          Map Portal.

          Users will be permitted to perform other generic operations such as view, select, identification without having set a
          working Property

          Only features that are affiliated with the “working” property should be editable (i.e. can’t edit a neighboring property’s
          stands by accident).

        7.2 Function Description - “Topology” Rules

             7.2.1 Features belonging inside a Property:
             If a Property Boundary is NOT mapped, then no topological enforcement of keeping Stands and Completed
             Treatments shapes within these boundaries will take place.

             However, when a Property Boundary exists, the system will check to see that all edited Stand and Completed
             Treatment polygons fall within the Property polygon boundary(ies). Users will be warned when they do not, and
             will be given a choice to clip to the Property boundary or abort the operation. If the Stand or Completed treatment
             is not contained wholly or in part within the Working Property (i.e., it’s totally outside the Property boundary), the
             user is informed and the operation is aborted.

            7.2.2 Property Boundary Overlaps:
             Newly added property boundary polygons cannot overlap pre-existing property boundary polygons. If the pre-
             existing boundary is thought to be in error, and the user does not have rights to edit this feature, then the user
             with the appropriate rights will have to be contacted about editing.

        7.3 Function Description - Create Polygon Boundaries
          Users must be able to create polygon shapes by selecting a tool from the Map Portal interface. A drop-down list of
          all “editable” layers will be presented to the user. All edits will occur against this “edit layer”.

          This tool will allow the user to digitize points of inflection and display a preview shape of what will be created in the
          ArcSDE geodatabase.
               Users must be able to drag inflection points to new locations once created
               Users must be able to insert new inflection points in between existing inflection points
               Users must be able to delete inflection points
               Users must be able to pan while zooming even if facilitated through a right-click context menu

          The user must have the ability to abort the operation after digitization has occurred.

          Polygons must be able to be created in these layers:
               Property boundaries
               Stands
               Completed Treatments
               Ancillary polygon layers

          A working property business record must be chosen by the user prior to creating Stand, Completed Treatment,
          and/or Ancillary GIS features (although a Property shape is not required).

WisFIRS RFP R2 GIS Development               Page 28 of 47                                   07/21/2010
                                                   RFP #H-048-08 WisFIRS
                                      Technical Guidance and Specifications Appendices
                                               For R2 Phase GIS Development,
                                                 Public Lands Management


          A business record for Properties must exist in WisFIRS R1 prior to creating a Property boundary.

          Stand polygons can be created before a Stand business record exists.
          Completed treatments polygons can be created before a Completed Treatment business record exists.

          * DNR staff will provide an interface, or mechanism, for the assignment of unique ids (e.g., Recon ID / SEQ_NO)
          and “Stubbing out” business records with minimal required content.
          * DNR will provide a discreet list of ancillary polygon layers for editing

        7.4 Function Description - Split Poly By Line
          Users must be able to create linear shapes, to be used to split existing polygons, by selecting a tool from the Map
          Portal interface. A drop-down list of all “editable” layers will be presented to the user. All edits will occur against this
          “edit layer”.

          The newly drawn line will split the selected polygon. Only one selection will be allowed at a time and a selected
          shape must be present

          Users must be presented with 2 dialog text boxes to enter in the Left and Right split polygon labels.
          It will be assumed that the orientation of left/right will be determined by “walking the line” being digitized.

          For Stands and Completed Treatments, the user will assign the Property/Compartment/Stand triplet to the
          component parts (the Property ID will default to the working property and be un-editable).

          The parent shape will be copied into the Historic layer if the layer is designated as archive-worthy, and there is
          business data affiliated with the shape.

        7.5 Function Description - Merge Polygons
          Users must be able to merge polygon shapes by selecting a tool from the Map Portal interface. A drop-down list of
          all “editable” layers will be presented to the user. All edits will occur against this “edit layer”.

          This tool combines selected shapes into one polygon. If shapes have coincident boundaries, they will be dissolved
          together. If shapes do not touch one another, they will become a multi-part polygon.

          The user will be forced to assign the Property/Compartment/Stand triplet to the merged shape. The Recon_ID
          records that were affiliated with the “parent” shapes are deleted for all EXCEPT the one chosen by the user to
          persist on the merged “child” shape (as per Public Lands Handbook pg 130-11: “When combining stands, the new
          stand can retain one of the original stand numbers, but must be updated to reflect new stand conditions. Leftover
          stand numbers must be deleted”).

          Parent shapes will be copied into the Historic layer if the layer is designated as archive-worthy, and there is business
          data affiliated with the shapes.

        7.6 Function Description - Create Neighbor Polygon
          Users must be able to create neighbor polygon shapes by selecting a tool from the Map Portal interface. A drop-
          down list of all “editable” layers will be presented to the user. All edits will occur against this “edit layer”.

          Users will use this tool to create a new polygon that shares boundaries wherever it overlaps with pre-selected
          polygon(s) within same layer.




WisFIRS RFP R2 GIS Development               Page 29 of 47                                    07/21/2010
                                                   RFP #H-048-08 WisFIRS
                                      Technical Guidance and Specifications Appendices
                                               For R2 Phase GIS Development,
                                                 Public Lands Management

        7.7 Function Description - Split Poly by Poly
          Users must be able to split polygon shapes with another, user-defined, polygon shape by selecting a tool from the
          Map Portal interface. A drop-down list of all “editable” layers will be presented to the user. All edits will occur
          against this “edit layer”.

          The newly drawn polygon will cut a new polygon into the selected polygons. The original geometry will be modified.
          The new geometry will be created and given a RECON_ID.

          The parent shape will be copied into the Historic layer if the layer is designated as archive-worthy, and there is
          business data affiliated with the shape.

        7.8 Function Description - Polygon Boundary Edits
          Users must be able to perform boundary edits against existing polygon shapes by selecting a tool from the Map
          Portal interface. A drop-down list of all “editable” layers will be presented to the user. All edits will occur against this
          “edit layer”.

          Cut – a newly drawn polygon subtracts area of overlap from selected polygon
          Append – a newly drawn polygon adds to selected polygon (either contiguous or non-contiguous)

          The parent shape will be copied into the Historic layer if the layer is designated as archive-worthy, and there is
          business data affiliated with the shape.

          No unique IDs will be assigned during these editing operations

        7.9 Function Description - Navigate Map while digitizing
          Users must be able to pan and zoom in / out while digitizing shapes. This will be available by right-clicking the
          mouse and using a context menu system. The menu system will include the ability to zoom in (2x), zoom out (2x),
          and re-center the map. The re-center operation will occur at the current mouse location thus accomplishing the
          effect of panning.

        7.10 Function Description - Polygon Delete
          Users must be able to delete existing polygons by selecting a tool from the Map Portal interface. A drop-down list of
          all “editable” layers will be presented to the user. All edits will occur against this “edit layer”.

          User must have the ability to select and delete polygon features (Properties / Order of Designation / Stands /
          Completed Treatments).

          The shape to be “deleted” will actually be copied into the Historic layer if the layer is designated as archive-worthy,
          and there is business data affiliated with the shape.

        7.11 Function Description - Tracking Historical Polygon Geometry
          Changes in geographic extent through time must be preserved for specific layers whose historical changes are
          deemed business critical. The features of value within these layers will be archived (stored in the database) for
          future reference.

          It is guaranteed that most users will not perform archiving procedures unless forced to do so, and therefore a
          manual archiving process would surely mean loss of business critical data. An automated process is required to
          ensure that data is archived consistently, or at least as consistently as possible given workflows must be allowed
          where users enter business attributes into WisFIRS prior to, or without, mapping.

          The automated archival system must not keep interim shape edits (as user refines final polygon extent) but rather it
          must only snapshot the geometry of the final geographic footprint of the shape of interest. The system assumes that
          if a user is making changes to a shape with valuable business data associated, that it must preserve a copy of the

WisFIRS RFP R2 GIS Development               Page 30 of 47                                    07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

          “parent” polygon because these polygons need to be preserved in tact for future use, and because the new footprint
          is not valid for the previously associated business data (i.e. completed treatment).

          Archival will be triggered whenever two conditions are met: 1) a user makes an edit that changes an existing polygon
          (split, merge, cut, append, delete) AND 2) the edited polygon has business data associated with it.

          To support editing of polygons that does not trigger archival, the system must facilitate a workflow whereby the
          association of business data to shapes is done after creation and refinement editing of shapes is complete. Note
          that business data can exist in the WisFIRS system prior to mapping, but users that “launch” from a business record
          to the mapping will by default map using the PCS triplet it launched from, but then will manually choose which of the
          completed treatment records to associate the shape(s) to. (Otherwise, if the business data were affiliated with the
          first shape created, no refinement editing could occur without triggering an auto archive.)

          A warning will be given to users when a shape is about to be copied into the Historical layer, and an opportunity to
          disassociate Completed Treatment business data will be available if an error was made by the user and they want to
          make additional edits to geometry before adding the CT data.

          The Historic data will be stored in separate layers from the “current” data, thus facilitating definition-query driven
          viewing of the Historic data with/without the current features displayed.

          PUBLIC: Users need archival of feature geometry for Completed Treatments on Public Lands

          PRIVATE (R3): For Private Lands with MFL Properties and Stewardship Plans with WFLGP cost share, users need
          archival of feature geometry for “Orders of Designation” (or contiguous tax parcels under same ownership within a
          single municipality), stands/planned treatments, and completed treatments. The full requirements of the R3
          components are not yet known; therefore discussion above focuses largely on Completed Treatments.

          Functional requirements related to the Retrieval / Viewing of the Historic data is covered in 0 – Viewing Historical
          Polygon Data.

        7.12 Function Description - Explode function (Separate Singlepart into Mulipart polygons)
          User must be able to perform the fission of multi-part polygon resulting in multiple unique polygon records by
          selecting a tool from the Map Portal interface. A drop-down list of all “editable” layers will be presented to the user.
          All edits will occur against this “edit layer”.

          The original multi-part shape is destroyed.

          The newly created records both retain the exact attribution as the parent record.

          Combining Multipart back into Singlepart is covered in the Merge Polygons section above.

        7.13 Function Description - Copy Polygon
          Users need the ability to copy shapes from one layer to another. A defined set of copy operations to be supported
          are listed. For all operations, if the shape has been attributed with Property, Compartment and Stand Values –
          those values will carry across to the new stand.

          Stands to Completed Treatment:
          Users must be able to copy a Stand polygon from the Stands layer to the Completed Treatments Layer by selecting
          a tool from the Map Portal interface.

          Public: Completed Treatments to Stand:
          Users must be able to copy a Completed Treatments polygon into the Stands Layer by selecting a tool from the Map
          Portal interface.


WisFIRS RFP R2 GIS Development               Page 31 of 47                                   07/21/2010
                                                   RFP #H-048-08 WisFIRS
                                      Technical Guidance and Specifications Appendices
                                               For R2 Phase GIS Development,
                                                 Public Lands Management


          Property / Order of Designation (R3) to Stand:
          User must be able to copy a Property boundary polygon to the Stands layer.

          Staging Stands to Production Stands:
          Users must be able to promote a shape in the Staging Stands layer to the production layer.

          Staging Completed Treatments to Production Completed Treatments:
          Users must be able to promote a shape in the Staging Completed Treatments layer to the production layer.

          My Layers (local data upload) to Property/Order, Stand, and Completed Treatment:
          User must be able to copy a feature from their “My Data” local data upload layers into the WisFIRS stands and
          completed treatments layers.

        7.14 Function Description - Assignment of “Property, Compartment, Stand” (PCS) Triplet
          For each stand or completed treatment polygon that is newly mapped, users need to enter either 1) a property,
          compartment and stand id (PCS Triplet) that already exists in the database, or 2) indicate that there is no such
          record in the database and that a new business record is required.

          The PCS Triplet allows for association of shapes back to Recon records and Completed Treatment business
          attribution data.

        7.15 Function Description - COGO Editing
          Users must be able to, using bearing, distance and direction for setting vertices of a polygon shape, create polygon
          shapes by selecting a tool from the Map Portal interface. A drop-down list of all “editable” layers will be presented to
          the user. All edits will occur against this “edit layer”.

        7.16 Function Description - Create Cruise Points
          Users will be able to select existing cruise areas (e.g., Stands) and generate either systematic cruise points or
          randomly-generated cruise points.

          The cruise points will be created on a Cruise Point layer and automatically stamped with the Cruise Name from the
          Cruise Area used for point generation. An additional, and optional, Cruise Point layer name and description will be
          available.

          * DNR will provide the exact parameters for the generation of these cruise points

        7.17 Function Description - Cruise Layer Download
          Users will have the ability to download data from the Cruise Layer into a standard shapefile format and standard
          projection.

          DNR will provide the projection standards.

        7.18 Function Description - Create Ancillary Point Feature
          DNR will provide the entire list of required ancillary layers
              Required Point Editing Functions

                Create/Move/Delete Point:

                         Users must be able to create point shapes by selecting a tool from the Map Portal interface. A drop-
                         down list of all "editable" layers will be presented to the user. All edits will occur against this "edit
                         layer".


WisFIRS RFP R2 GIS Development               Page 32 of 47                                  07/21/2010
                                                   RFP #H-048-08 WisFIRS
                                      Technical Guidance and Specifications Appendices
                                               For R2 Phase GIS Development,
                                                 Public Lands Management

                         Users must be able to drag and move points to new locations once created.
                         Users must be able to delete points once created.
                         The user must have the ability to abort the operation after digitization has occurred.

                Copy Point to Other Ancillary Point Layer:

                         Users need the ability to copy shapes from one layer to another.

        7.19 Function Description - Create Ancillary Line Feature
          DNR will provide the entire list of required ancillary layers

                Required Line Editing Functions

                Create Line:

                         Users must be able to create line shapes by selecting a tool from the Map Portal interface. A drop-
                         down list of all "editable" layers will be presented to the user. All edits will occur against this "edit
                         layer".
                         This tool will allow the user to digitize points of inflection and display a preview shape of what will be
                         created in the ArcSDE geodatabase.
                         Users must be able to drag inflection points to new locations once created.
                         Users must be able to insert new inflection points in between existing inflection points.
                         Users must be able to delete inflection points.
                         Users must be able to pan while zooming even if facilitated through a right-click context menu.
                         The user must have the ability to abort the operation after digitization has occurred.

                Line Delete:

                         Users must be able to delete existing lines by selecting a tool from the Map Portal interface. A drop-
                         down list of all "editable" layers will be presented to the user. All edits will occur against this "edit
                         layer".

                         User must have the ability to select and delete line features.

                Split Line by Line:

                         Users must be able to create linear shapes, to be used to split existing lines, by selecting a tool from
                         the Map Portal interface. A drop-down list of all "editable" layers will be presented to the user. All
                         edits will occur against this "edit layer".

                         The newly drawn line will split the selected line. Only one selection will be allowed at a time and a
                         selected shape must be present

                         Users must be presented with 2 dialog text boxes to enter in the Left and Right split polygon labels.
                         It will be assumed that the orientation of left/right will be determined by "walking the line" being
                         digitized.

                Copy Line to Other Ancillary Line Layer:

                         Users need the ability to copy shapes from one layer to another.

                Merge Lines:


WisFIRS RFP R2 GIS Development               Page 33 of 47                                   07/21/2010
                                                   RFP #H-048-08 WisFIRS
                                      Technical Guidance and Specifications Appendices
                                               For R2 Phase GIS Development,
                                                 Public Lands Management

                         Users must be able to merge line shapes by selecting a tool from the Map Portal interface. A drop-
                         down list of all "editable" layers will be presented to the user. All edits will occur against this "edit
                         layer".

                         This tool combines selected shapes into one line. If shapes have coincident boundaries, they will be
                         dissolved together. If shapes do not touch one another, they will become a multi-part line.

                Explode Line:

                         User must be able to perform the fission of multi-part line resulting in multiple unique line records by
                         selecting a tool from the Map Portal interface. A drop-down list of all "editable" layers will be
                         presented to the user. All edits will occur against this "edit layer".

                         The original multi-part shape is destroyed.

                         The newly created records both retain the exact attribution as the parent record.


        7.20 Function Description - Create Ancillary Polygon Feature
          DNR will provide the entire list of required ancillary layers

                The same functions used for editing non-ancillary polygon layers (see above) will be available for editing
                ancillary polygon layers, including Create Polygon Boundaries, Split Poly by Line, Merge Polygons, Create
                Neighbor Polygon, Split Poly by Poly, Polygon Boundary Edits, Polygon Delete, Explode Function, and Copy
                Polygon.




WisFIRS RFP R2 GIS Development               Page 34 of 47                                   07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

        7.21 Function Description - Create Text-based Annotation
          Users will be able to create text-based annotation. Users will be presented with a text box after select the text
          annotation tool. The text will be position at the point of mouse click on the map. The annotation will use a standard
          color and font.

          This annotation will persist as a distinct ancillary layer in the geodatabase.

        7.22 Function Description - Desktop Editing Support
          Users of ESRI’s ArcGIS desktop will be able to upload a limit set of data elements to the WisFIRS SDE instance.
          This content (Stands and Completed Treatments) will be placed in a holding, or staging, area on the server. This
          staging area will be 2 distinct layers in the SDE instance.

          The staging layers will be visible as layers within the Map Portal.

          The upload process will occur through the selection of a Property/Compartment/Stand triplet. Once selected, the
          user will click a button that triggers a push of all shapes associated with that triplet to the central database on the
          staging layer.

        7.23 Function Description - GPS Upload
          Users will have the ability to upload GPS content in a defined format. All uploaded content will be loaded into a
          defined set of layers with standard symbology.


        8.0 GIS OUTPUT

        8.1 Function Description - GIS Export
          Users will be provided with a download tool. This tool will provide options for downloading all features from a given
          layer.

          Additionally, users will be able to download only selected features using a similar tool presented through the
          Selection Results section of the Map Portal.

          Feature data will be made available for download. Files will be packaged and placed in a folder accessible to the
          users. The user will be notified of the path to retrieve the data.

          Data from selections, searches, and analyses will be made available for download.

          The application will support exporting data to the following formats: shapefile and XML for tabular content.

          A standard format will be used for all downloaded content.

          *DNR will provide this projection.




WisFIRS RFP R2 GIS Development                 Page 35 of 47                                 07/21/2010
                                                  RFP #H-048-08 WisFIRS
                                     Technical Guidance and Specifications Appendices
                                              For R2 Phase GIS Development,
                                                Public Lands Management

        8.2 Function Description - Template Report Maps
          Users should be able to print a defined set of Reports that include mapped output.

          Public Map:
              Title
              Property
              Compartment Number
              Township Range and Section
              Compartment Acreage
              County
              Scale
              Created By:
              Date
              North Arrow
              Tabular Data TBD
              Legend

          Field Maps with Cruise Points:
               Cruise Points

          All reports will be delivered in PDF format through SQL Server reporting services. Users will have the ability to
          dynamically include / exclude layers for mapping. Users will be able to type in an absolute scale from the reports
          portal. Users will be given a “preview” map to be included in the report. This map will not be interactive beyond a
          simple Zoom-to-scale option and layer removal / inclusion.

        8.3 Function Description - Orphans Report
          Users will be able to access a live orphans list report for use in hardcopy form.

        8.4 Function Description - Masking for Report Output
          As part of the report creation process, users will be able to choose to mask out features not related to a Property (or
          Order of Designation), or be able to mask based on PLSS geometry.

        8.5 Function Description - GIS Acres Summary reporting
          For each template report requiring summary details about feature area (acreage), area will be summarized for any
          multi-part polygons (either stored as one record or many per business record)




        9.0 GIS ADMINISTRATION

        9.1 Function Description - Uploaded Local Layers
          Users will manage uploaded content through a lightweight administration panel allowing for:
              Content deletion
              Color changes
              Display name changes




WisFIRS RFP R2 GIS Development              Page 36 of 47                                     07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Appendix B – Core Navigation Workflows:
        Zoom In




WisFIRS RFP R2 GIS Development         Page 37 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Zoom Out




WisFIRS RFP R2 GIS Development         Page 38 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Pan




WisFIRS RFP R2 GIS Development         Page 39 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Start Over




WisFIRS RFP R2 GIS Development         Page 40 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Measure




WisFIRS RFP R2 GIS Development         Page 41 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Select by Polygon




WisFIRS RFP R2 GIS Development         Page 42 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Select by Rectangle




WisFIRS RFP R2 GIS Development         Page 43 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Appendix C –Business Workflows
        Completed Treatment Attribution




WisFIRS RFP R2 GIS Development         Page 44 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Archival of Completed Treatment




WisFIRS RFP R2 GIS Development         Page 45 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management



        Pushing of Local Shapes to Staging WisFIRS Area




WisFIRS RFP R2 GIS Development         Page 46 of 47                          07/21/2010
                                              RFP #H-048-08 WisFIRS
                                 Technical Guidance and Specifications Appendices
                                          For R2 Phase GIS Development,
                                            Public Lands Management




WisFIRS RFP R2 GIS Development         Page 47 of 47                          07/21/2010

								
To top