Delimitation Phase

Delimitation Deliverables:

1. Data Schema Design and Documentation Updates
VertiGIS will design the data model required to support delimitation surveys, in the context of the existing CalTrap data model for detection surveys. Where necessary, new tables, views, attributes, and other data objects will be designed and documented. The output of this task will be a full data dictionary of the entire CalTrap database, including all objects for detection trapping and delimitation trapping. Changes made to support delimitation trapping will be highlighted. (80 hours)

2. Initial Application Setup (Mobile)
VertiGIS will begin development on the delimitation application using the detection CalTrap application as its foundation. This initial setup task involves a new application from the existing detection application and making all necessary modifications so it is independent. The subtasks involved include copying and renaming all application components, referencing shared components where appropriate (e.g. Geocortex Workflows), configuring a new ArcGIS web map, etc VertiGIS will separate the detection trapping development environment into its own parallel environment as part of this deliverable. (40 hours)

3. Initial Application Setup (Administration Site)
The delimitation application will have its own administrative site, similar to the administrative site for detection trapping. Like for the mobile application, the administrative site for delimitation trapping will be based on the detection site and will be built using detection as its foundation. The subtasks involved in this deliverable are the same as those to be performed for the mobile site, described above. (40 hours)

4. Data Publication Migration Script Updates
The detection trapping project includes the creation of data scripts to automate publishing the CalTrap data schema and migrating data to new environments. Based on the data design, these scripts will be updated and tested to support the changes introduced for delimitation surveys. (24 hours)

5. Cartography Review and Updates
VertiGIS expects that updates will be required to the cartography (symbology) in the application to support the unique needs of delimitation trapping. Though we will want to keep many of the cartography concepts the same (such as visual indication of traps due for service vs. overdue), different trap density requirements will require different representation to be effectively understood by trappers. (40 hours)

6. Onsite Analysis
Two senior VertiGIS technical analysts and a VertiGIS project manager will conduct a 3-day requirements session onsite at LA County and, ideally, one or more nearby regions. The purpose of the onsite session is to gather requirements specific to delimitation trapping. Preferably, the onsite visit will coincide with a delimitation survey underway that we could observe by riding along with trappers for part of their day (similar to the approach used for the detection trapping analysis). (72 hours)

7. Functional Application Design and Documentation
VertiGIS will produce a document outlining in detail the functional requirements of the delimitation application, including wireframe mock-ups, user interface storyboards, and exception cases. The application design will reflect the capabilities of Geocortex Mobile and Geocortex Workflow, and mock-ups will be constructed using the Geocortex applications where possible for maximum fidelity. (56 hours)

8. Expand Survey Workflow
A workflow specific to delimitation trapping is allowing an administrator to expand a delimitation survey when additional pests are trapped in the survey area. There are a number of different rules that apply for expanding the survey area depending on the type of pest and the area of the state the survey is occurring. A Geocortex Workflow will be developed which guides an administrator through the process of expanding an existing delimitation survey, using pre-defined rules were appropriate and allowing administrator overrides when necessary. (80 hours)

9. Security Updates as Needed
VertiGIS anticipates that authorization settings for the delimitation application will be different than those for detection, with CDFA often assuming responsibility for delimitation trapping in areas which otherwise are county-administered. Though the specific changes are not known at this point, this deliverable reserves time to respond to those changes as they arise and as more information is known about the authorization requirements for delimitation during the course of the project. (40 hours)

10. Cross-County Survey Support
Delimitation surveys may cross county borders, but are still considered the same survey for all intents and purposes. Since detection trapping is county-focused with each survey being part of only one county, changes will need to be made to the application to support single surveys spanning multiple counties. Though it is not known at this point exactly what these changes will entail, this deliverable reserves time to respond to those changes as they become known. (40 hours)

11. Existing Workflow Updates
There are 11 Geocortex Workflows that encapsulate the functionality of detection trapping for both the trapper and the administrator. Though all of these Workflows are likely valid also for delimitation trapping, most of them will require some changes to support delimitation-specific processes. VertiGIS estimates that each Workflow may require an average of 16 hours to modify for delimitation trapping use. We expect that some of the Workflows may require less modification than others (with some perhaps not requiring any modification at all), but others will be more involved. The specific changes required for each Workflow will begin to be defined as part of the design phase, with a more accurate estimate of hourly breakdowns provided at that point. (176 hours)

12. Initial Testing in VertiGIS Environment
VertiGIS will run through all of the test cases for the new and updated functionality which were written prior to development commencing. All defects discovered during this initial internal test phase will be resolved, with test cases being updated as necessary (if changes are required to the tool behavior as a result of the fix). (60 hours)

13. Initial Delivery to Test Server
VertiGIS will deliver the tested application to the LA County test server. As part of delivery, VertiGIS will migrate ArcGIS content such as Web Maps and Geocortex Workflows as necessary. VertiGIS will also deliver the updated data schema and deploy the schema using the deployment script. VertiGIS will perform a ‘smoke test’ of the application once delivered to the LA County test server to ensure it is ready for user acceptance testing. A ‘smoke test’ is a rapid test of the major functions of the application to ensure that it is running correctly in the new infrastructure environment (that is, running as it was in VertiGIS’ development environment). (16 hours)

14. UAT Feedback Changes
During the LA County UAT period, VertiGIS will resolve defects found in the application which fail the agreed-upon test cases (provided to LA County prior to development commencing). Defects of this nature will be resolved by VertiGIS at no charge. Additional usability issues and feature requests which were not covered by the test cases will be prioritized and addressed as part of this UAT Feedback Changes task as time and budget permit. (80 hours)

15. Post-UAT Delivery to Test Server
Following the resolution of issues identified during UAT, VertiGIS will deliver the updated application again to the LA County test server following the same process as with the initial delivery. A ‘smoke test’ will again be performed to ensure it is ready for final validation by LA County. (12 hours)

16. Production Migration Assistance
VertiGIS will assist LA County technical staff with migrating the application from the test to the production environment in preparation for a more comprehensive field test and ultimate rollout statewide to all regions. VertiGIS expects that the migration from test to production will follow a similar process as the migration from VertiGIS’ environment to the LA County environment; that is, ArcGIS content will be migrated in a similar manner and scripts will be used to create and migrate data content. (24 hours)
The Production Migration Assistance task includes time for VertiGIS to assist remotely in advance of the production roll out as well as time to assist LA County onsite during the same visit as the administrator training.

17. Administrator Training and ‘Train the Trainer’
VertiGIS will train administrative staff on the use of the application and will train representatives of LA County (and others as appropriate) during a ‘Train the Trainer’ session to equip trainees with the ability to then train supervisors and trappers. This task includes some time to prepare the lesson plan and deliver the training onsite at LA County. (32 hours)
VertiGIS anticipates that the onsite training may be performed during the same visit as for the Production Migration Assistance.

18. Documentation Updates to ‘As-Built’ Status
Following deployment of the application to the LA County production environment, VertiGIS will update the functional and technical documentation to reflect the final (as-built) state of the application – including connections to live LA County ArcGIS and database resources as necessary. (32 hours)

19. Technical Project Administration
Technical project administration tasks, as necessary, as described in the Technical Project Administration section of this proposal. (32 hours)

20. Project Management
The project manager will monitor the progress and budget burn for the project. They will provide status updates and reports to the client, including identified risks and mitigations, on an agreed-upon schedule. The project manager will also be responsible for capturing any change requests and generally ensuring the project runs smoothly. (188 hours)

21. Mid-project demos (20 hours)

Delimitation Estimated Time Schedule:
Total estimated time: 1,124 hours approximately 141 workdays (7 months) that is dedicated to the project which will involve design, development, and implementation.) The entirety of the delimitation project will span a period of 7 months.

Milestone 1
6. Onsite Analysis (Business analysis may be performed remotely, if travel restrictions prevent onsite analysis) (72 Hours)
1. Data Schema Design and Documentation Updates (80 Hours)
7. Functional Design and Documentation (56 Hours)
Total Hours: 208

Milestone 2
4. Data Publication & Migration Script Updates (24 Hours)
5. Cartography Review and Updates (40 Hours)
2. Initial Application Setup (Mobile) (40 Hours)
3. Initial Application Setup (Administrative Site) (40 Hours)
Total Hours: 144

Milestone 3
8. Expand Survey Workflows (80 Hours)
9. Security Updates as Needed (40 Hours)
10. Cross County Survey Support (40 Hours)
11. Existing Workflow Updates A (88 Hours)
Total Hours: 248

Milestone 4
11. Existing Workflow Updates B (88 Hours)
12. Initial Testing in VertiGIS Environment (60 Hours)
13. Initial Delivery to Test Server (16 hours)
Total Hours: 164

Milestone 5
14. UAT Feedback Changes (80 hours)
15. Post-UAT Delivery to Test Server (12 hours)
Total Hours: 52

Milestone 6
16. Production Migration Assistance (24 hours)
17. Administrator Training and ‘Train the Trainer’ (32 hours)
18. Documentation Updates to ‘As-Built’ Status (32 hours)
Total Hours: 88

19. Technical Project Administration (32 hours)
20. Project Management (188 hours)
Divided over all project milestones as dictated by the work
21. Mid-project demos (20 hours)